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
Date: Tue, 22 Sep 2009 21:11:01 +0200 [thread overview]
Message-ID: <20090922211101.076e9763@infradead.org> (raw)
In-Reply-To: <8a15eb2b0909221201k70b9e9darc6fda53f87bfae29@mail.gmail.com>
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
next prev parent reply other threads:[~2009-09-22 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 19:01 TI PCIe-PCI bridge quirks Gabe Black
2009-09-22 19:11 ` Arjan van de Ven [this message]
2009-09-22 19:37 ` Gabe Black
2009-09-22 20:07 ` Arjan van de Ven
2009-10-06 0:09 ` Jesse Barnes
2009-10-06 11:32 ` Gabe Black
2009-10-06 14:19 ` [PATCH] TI XIO200a bridge quirk: erroneously reports support for fast b2b transfers Gabe Black
2009-10-06 16:11 ` Jesse Barnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090922211101.076e9763@infradead.org \
--to=arjan@infradead.org \
--cc=gabe@blackfam.net \
--cc=gabebblack@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox