Date: Tue, 22 Sep 2009 21:11:01 +0200
From: Arjan van de Ven <arjan@infradead.org>
To: gabe@blackfam.net
Cc: gabebblack@gmail.com, linux-kernel@vger.kernel.org,
       linux-pci@vger.kernel.org, jbarnes@virtuousgeek.org
Subject: Re: TI PCIe-PCI bridge quirks
Message-ID: <20090922211101.076e9763@infradead.org>
In-Reply-To: <8a15eb2b0909221201k70b9e9darc6fda53f87bfae29@mail.gmail.com>
References: <8a15eb2b0909221201k70b9e9darc6fda53f87bfae29@mail.gmail.com>
Organization: Intel
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1205
Lines: 31

On Tue, 22 Sep 2009 14:01:06 -0500
Gabe Black <gabebblack@gmail.com> wrote:

> Hi,
> 
> The TI XIO2000A/XIO2200A PCIe-PCI bridge (VID: 104C, DID: 8231)
> erroneously handles fast back-to-back transfers on its subordinate bus
> segment.  The behavior is seen when there are multiple devices
> downstream and transfers from both devices result in a fast b2b
> transfer.  This confuses the PCIe-PCI bridge and results in data
> corruption.
> 
> One way to work around the buggy bridge would be to disable fast b2b
> transfers on any device on the subordinate bus-segment by writing the
> appropriate bits in the device's pci-configspace command register.
> 
> Are there any suggestions on how this might be handled?  Should this
> be addressed in the kernel?

sounds like this is worth a PCI quirk in the kernel...


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/