From: "Rolf Eike Beer" <eike-kernel@sf-tec.de>
To: "Prarit Bhargava" <prarit@redhat.com>
Cc: "Matthew Wilcox" <matthew@wil.cx>,
"Don Dutile" <ddutile@redhat.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"James Paradis" <jparadis@redhat.com>,
linux-pci@vger.kernel.org, mstowe@redhat.com,
jbarnes@virtuousgeek.org
Subject: Re: [PATCH] pci: Workaround Stratus broken PCIE hierarchy
Date: Tue, 15 Nov 2011 17:08:10 +0100 [thread overview]
Message-ID: <af06626e34e32043e3c4974290270ec1.squirrel@webmail.sf-mail.de> (raw)
In-Reply-To: <4EC28B93.1060101@redhat.com>
> Trying [v2]....
>
>
> pci: Workaround Stratus broken PCIE hierarchy
>
> Stratus systems have a hierarchy that includes a PCIE Downstream bridge
> connected to a PCIE Upstream bridge and a PCI Downstream bridge. The
> system
> boots with this wrong hierarchy into a crippled mode (USB doesn't work,
> network doesn't work ...). Avoiding the Downstream bridge check in
> only_one_child() causes all the bridges to be enumerated and the system
> to function properly.
>
> Unfortunately this hardware is currently available so we should at least
> keep it functional.
>
> [v2]
> - ddutile@redhat.com requested drivers/pci/quirks.c code
> - matthew@will.cx requested that dmi_name_in_vendors() be called only once
> with a static var check
> - added a kernel parameter to enable scanning of all PCIE devices.
>
> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 6f45a73..f478bd5 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -3589,6 +3589,9 @@ static int __init pci_setup(char *str)
> pcie_bus_config = PCIE_BUS_PERFORMANCE;
> } else if (!strncmp(str, "pcie_bus_peer2peer", 18)) {
> pcie_bus_config = PCIE_BUS_PEER2PEER;
> + } else if (!strncmp(str, "pcie_scan_all", 13)) {
> + printk(KERN_ERR HW_ERR "PCIE: Scanning all devices.\n");
> + pcie_scan_all = 1;
> } else {
> printk(KERN_ERR "PCI: Unknown option `%s'\n",
> str);
To scan all devices isn't an error, is it? The user has requested this, so
KERN_INFO should be enough.
Eike
next prev parent reply other threads:[~2011-11-15 16:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 14:00 [PATCH] pci: Workaround Stratus broken PCIE hierarchy Prarit Bhargava
2011-11-10 14:31 ` Matthew Wilcox
2011-11-10 16:50 ` Don Dutile
2011-11-11 17:41 ` James Paradis
2011-11-11 19:13 ` Don Dutile
2011-11-11 20:29 ` Bjorn Helgaas
2011-11-11 20:35 ` Don Dutile
2011-11-14 14:44 ` Prarit Bhargava
2011-11-14 18:14 ` Matthew Wilcox
2011-11-14 19:50 ` Prarit Bhargava
2011-11-15 20:16 ` Matthew Wilcox
2011-11-15 15:56 ` Prarit Bhargava
2011-11-15 16:08 ` Rolf Eike Beer [this message]
2011-11-15 18:14 ` Bjorn Helgaas
2011-11-15 18:25 ` Prarit Bhargava
2011-11-15 21:08 ` James Paradis
2011-11-15 21:52 ` Myron Stowe
2011-11-15 22:14 ` James Paradis
2011-11-15 20:15 ` Matthew Wilcox
2011-11-16 16:53 ` Prarit Bhargava
2011-11-17 0:18 ` Prarit Bhargava
2011-11-15 21:53 ` James Paradis
2011-11-15 22:27 ` James Paradis
2011-11-15 23:07 ` Don Dutile
-- strict thread matches above, loose matches on Subject: below --
2012-04-25 17:56 Prarit Bhargava
2012-04-25 23:35 ` Bjorn Helgaas
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=af06626e34e32043e3c4974290270ec1.squirrel@webmail.sf-mail.de \
--to=eike-kernel@sf-tec.de \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jparadis@redhat.com \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mstowe@redhat.com \
--cc=prarit@redhat.com \
/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).