From: Stefan Roese <sr@denx.de>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/4xx: Workaround for PPC440EPx/GRx PCI_28 Errata
Date: Thu, 12 Jun 2008 16:24:13 +0200 [thread overview]
Message-ID: <200806121624.13577.sr@denx.de> (raw)
In-Reply-To: <20080611104549.45836929@zod.rchland.ibm.com>
On Wednesday 11 June 2008, Josh Boyer wrote:
> The 440EPx/GRx chips don't support PCI MRM commands. Drivers determine
> this by looking for a zero value in the PCI cache line size register.
> However, some drivers write to this register upon initialization. This can
> cause MRMs to be used on these chips, which may cause deadlocks on PLB4.
>
> The workaround implemented here introduces a new indirect_type flag, called
> PPC_INDIRECT_TYPE_BROKEN_MRM. This is set in the pci_controller structure
> in the pci fixup function for 4xx PCI bridges by determining if the bridge
> is compatible with 440EPx/GRx. The flag is checked in the
> indirect_write_config function, and forces any writes to the
> PCI_CACHE_LINE_SIZE register to be zero, which will disable MRMs for these
> chips.
>
> A similar workaround has been tested by AMCC on various PCI cards, such as
> the Silicon Image ATA card and Intel E1000 GIGE card. Hangs were seen with
> the Silicon Image card, and MRMs were seen on the bus with a PCI analyzer.
> With the workaround in place, the card functioned properly and only Memory
> Reads were seen on the bus with the analyzer.
>
> Signed-off-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Acked-by: Stefan Roese <sr@denx.de>
I manually applied your patch (since it doesn't apply clean as discussed on
IRC) and tested it on my Sequoia with a modified PCI USB driver changing
PCI_CACHE_LINE_SIZE.
Best regards,
Stefan
next prev parent reply other threads:[~2008-06-12 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 14:45 [PATCH] powerpc/4xx: Workaround for PPC440EPx/GRx PCI_28 Errata Josh Boyer
2008-06-12 14:24 ` Stefan Roese [this message]
2008-06-12 20:36 ` Josh Boyer
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=200806121624.13577.sr@denx.de \
--to=sr@denx.de \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).