From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Will Deacon <will.deacon@arm.com>,
Jayachandran C <jchandra@broadcom.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
"Liviu Dudau" <Liviu.Dudau@arm.com>,
Ming Lei <ming.lei@canonical.com>
Subject: Re: [PATCH v2 1/2] PCI: generic: remove dependency on hw_pci
Date: Wed, 13 May 2015 07:47:42 -0500 [thread overview]
Message-ID: <555347EE.6050502@amd.com> (raw)
In-Reply-To: <554ADCE0.8020603@amd.com>
Hi Bjorn,
Somehow, I didn't get your reply email from the ML. So, I've captured
your questions here, please see my reply below.
On 5/6/2015 10:32 PM, Suravee Suthikulanit wrote:
> Hi All,
>
> I tested this patch series on the AMD Seattle w/o PCI_PROBE_ONLY mode
> and that works fine. However, w/ PCI_PROBE_ONLY, I also run into the
> resource not claimed issue (no surprise here).
>
> So, I tried porting the pcibios_claim_one_bus() from
> arch/alpha/kernel/pci.c as Lorenzo suggested, plus the a small change in
> pci_claim_resource(), and it seems to work w/ PCI_PROBE_ONLY. (Please
> see example patch below.)
>
> The additional while loop is needed in the pci_claim_resource() since I
> need to reference back to the resource in the root bus, which are
> defined from the DT node. Does this sounds like a reasonable approach?
>
> diff --git a/drivers/pci/host/pci-host-generic.c
> b/drivers/pci/host/pci-host-generic.c
> index e9cc559..0dfa23d 100644
> --- a/drivers/pci/host/pci-host-generic.c
> +++ b/drivers/pci/host/pci-host-generic.c
> @@ -261,7 +261,10 @@ static int gen_pci_probe(struct platform_device *pdev)
> if (!pci_has_flag(PCI_PROBE_ONLY)) {
> pci_bus_size_bridges(bus);
> pci_bus_assign_resources(bus);
> + } else {
> + pci_claim_one_bus(bus);
> }
> +
> pci_bus_add_devices(bus);
>
> /* Configure PCI Express settings */
> diff --git a/drivers/pci/setup-res.c b/drivers/pci/setup-res.c
> index 232f925..d4b43b3 100644
> --- a/drivers/pci/setup-res.c
> +++ b/drivers/pci/setup-res.c
> @@ -109,6 +109,7 @@ int pci_claim_resource(struct pci_dev *dev, int
> resource)
> {
> struct resource *res = &dev->resource[resource];
> struct resource *root, *conflict;
> + struct pci_dev *pdev = dev;
>
> if (res->flags & IORESOURCE_UNSET) {
> dev_info(&dev->dev, "can't claim BAR %d %pR: no address
> assigned\n",
> @@ -116,7 +117,18 @@ int pci_claim_resource(struct pci_dev *dev, int
> resource)
> return -EINVAL;
> }
>
> - root = pci_find_parent_resource(dev, res);
> + while (pdev) {
> + root = pci_find_parent_resource(pdev, res);
> + if (root)
> + break;
> +
> + if (pci_has_flag(PCI_PROBE_ONLY) &&
> + !pci_is_root_bus(pdev->bus))
> + pdev = pdev->bus->self;
> + else
> + break;
> + }
> +
> if (!root) {
> dev_info(&dev->dev, "can't claim BAR %d %pR: no compatible
> bridge window\n",
> resource, res);
[From Bjorn]
I don't understand this new loop. Apparently you have a device BAR, and
the upstream bridge doesn't have a window that contains the BAR? That
sounds like a problem with the upstream bridge resources.
Do you have an example that would make this more concrete, e.g., a host
bridge, P2P bridge(s), and endpoint with their resources?
[Suravee]
Here is the information you were asking for. This information is setup
from the FW. In the PCI bridge (00:02.1), I see the prefetchable memory
behind bridge is already setup.
OUTPUT from lspci -tv:
-[0000:00]-+-00.0 Advanced Micro Devices, Inc. [AMD] Device 1a00
+-02.0 Advanced Micro Devices, Inc. [AMD] Device 1a01
\-02.1 PCI Bridge -[01]--+-00.0 Intel Corporation 82599ES
10-Gigabit SFI/SFP+ Network Connection
\-00.1 Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection
OUTPUT from lspci -vvv:
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1a00
Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1a00
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1a01
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 1a02
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00fff000-00000fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: 0000007fffe00000-0000007fffffffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
.......
01:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
Subsystem: Intel Corporation Ethernet Server Adapter X520-2
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 46
Region 0: Memory at 7fffe80000 (64-bit, prefetchable) [size=512K]
Region 2: I/O ports at 0020 [size=32]
Region 4: Memory at 7ffff04000 (64-bit, prefetchable) [size=16K]
.......
01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
Subsystem: Intel Corporation Ethernet Server Adapter X520-2
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 47
Region 0: Memory at 7fffe00000 (64-bit, prefetchable) [size=512K]
Region 2: I/O ports at 0000 [size=32]
Region 4: Memory at 7ffff00000 (64-bit, prefetchable) [size=16K]
........
Thanks,
Suravee
next prev parent reply other threads:[~2015-05-13 12:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 2:02 [PATCH v2 1/2] PCI: generic: remove dependency on hw_pci Jayachandran C
2015-05-05 2:02 ` [PATCH v2 2/2] PCI: generic: add arm64 support Jayachandran C
2015-05-05 15:53 ` [PATCH v2 1/2] PCI: generic: remove dependency on hw_pci Will Deacon
2015-05-05 15:58 ` Arnd Bergmann
2015-05-05 16:03 ` Lorenzo Pieralisi
2015-05-06 14:18 ` Lorenzo Pieralisi
2015-05-06 15:18 ` Bjorn Helgaas
2015-05-07 3:32 ` Suravee Suthikulanit
2015-05-12 13:34 ` Bjorn Helgaas
2015-05-12 16:34 ` Lorenzo Pieralisi
2015-05-12 19:20 ` Bjorn Helgaas
2015-05-13 12:47 ` Suravee Suthikulanit [this message]
2015-05-13 13:54 ` Bjorn Helgaas
2015-05-13 15:05 ` Suravee Suthikulanit
2015-05-13 15:11 ` Bjorn Helgaas
[not found] ` <20150512000746.GA31418@jayachandranc.netlogicmicro.com>
2015-05-19 23:09 ` Bjorn Helgaas
2015-05-20 17:29 ` Will Deacon
2015-05-20 20:46 ` Bjorn Helgaas
[not found] ` <20150521063729.GB31418@jayachandranc.netlogicmicro.com>
2015-05-26 9:59 ` Will Deacon
2015-05-26 10:38 ` Arnd Bergmann
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=555347EE.6050502@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=jchandra@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=ming.lei@canonical.com \
--cc=will.deacon@arm.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).