From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nathan Lynch <ntl@pobox.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [RFC/PATCH] remove gratuitous reads from maple pci config space methods
Date: Thu, 09 Aug 2007 10:55:33 +1000 [thread overview]
Message-ID: <1186620933.938.211.camel@localhost.localdomain> (raw)
In-Reply-To: <20070809005044.GD10114@localdomain>
On Wed, 2007-08-08 at 19:50 -0500, Nathan Lynch wrote:
> The maple pci configuration space write methods read the written
> location immediately after the write is performed, presumably in order
> to flush the write. However, configuration space writes are not
> allowed to be posted, making these reads gratuitous. Furthermore,
> this behavior potentially causes us to violate the PCI PM spec when
> changing between e.g. D0 and D3 states, because a delay of up to 10ms
> may be required before the OS accesses configuration space after the
> write which initiates the transition. It definitely causes a system
> hang for me with a Broadcom 5721 PCIE network adapter, which is fixed
> by this change.
>
> Remove the gratuitous reads from u3_agp_write_config,
> u3_ht_write_config, and u4_pcie_write_config.
>
> Signed-off-by: Nathan Lynch <ntl@pobox.com>
Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
Thanks ! Care to fix powermac too ? :-)
Cheers,
Ben.
> ---
> arch/powerpc/platforms/maple/pci.c | 9 ---------
> 1 files changed, 0 insertions(+), 9 deletions(-)
>
> diff --git a/arch/powerpc/platforms/maple/pci.c b/arch/powerpc/platforms/maple/pci.c
> index 2542403..b095eaa 100644
> --- a/arch/powerpc/platforms/maple/pci.c
> +++ b/arch/powerpc/platforms/maple/pci.c
> @@ -169,15 +169,12 @@ static int u3_agp_write_config(struct pci_bus *bus, unsigned int devfn,
> switch (len) {
> case 1:
> out_8(addr, val);
> - (void) in_8(addr);
> break;
> case 2:
> out_le16(addr, val);
> - (void) in_le16(addr);
> break;
> default:
> out_le32(addr, val);
> - (void) in_le32(addr);
> break;
> }
> return PCIBIOS_SUCCESSFUL;
> @@ -268,15 +265,12 @@ static int u3_ht_write_config(struct pci_bus *bus, unsigned int devfn,
> switch (len) {
> case 1:
> out_8(addr, val);
> - (void) in_8(addr);
> break;
> case 2:
> out_le16(addr, val);
> - (void) in_le16(addr);
> break;
> default:
> out_le32(addr, val);
> - (void) in_le32(addr);
> break;
> }
> return PCIBIOS_SUCCESSFUL;
> @@ -376,15 +370,12 @@ static int u4_pcie_write_config(struct pci_bus *bus, unsigned int devfn,
> switch (len) {
> case 1:
> out_8(addr, val);
> - (void) in_8(addr);
> break;
> case 2:
> out_le16(addr, val);
> - (void) in_le16(addr);
> break;
> default:
> out_le32(addr, val);
> - (void) in_le32(addr);
> break;
> }
> return PCIBIOS_SUCCESSFUL;
next prev parent reply other threads:[~2007-08-09 0:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 0:50 [RFC/PATCH] remove gratuitous reads from maple pci config space methods Nathan Lynch
2007-08-09 0:55 ` Benjamin Herrenschmidt [this message]
2007-08-09 1:04 ` Nathan Lynch
2007-08-09 1:14 ` Benjamin Herrenschmidt
2007-08-09 20:03 ` Olof Johansson
2007-08-09 3:05 ` David Gibson
2007-08-09 4:16 ` Nathan Lynch
2007-08-09 4:18 ` David Gibson
2007-08-09 10:40 ` Segher Boessenkool
2007-08-09 21:24 ` Nathan Lynch
2007-08-10 17:58 ` Segher Boessenkool
2007-08-11 23:41 ` Benjamin Herrenschmidt
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=1186620933.938.211.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--cc=paulus@samba.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).