From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Bjorn Helgaas <bhelgaas@google.com>,
Richard Henderson <rth@twiddle.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
David Howells <dhowells@redhat.com>,
Russell King <linux@arm.linux.org.uk>,
Tony Luck <tony.luck@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Ingo Molnar <mingo@redhat.com>, Michal Simek <monstr@monstr.eu>,
"yasutake.koichi@jp.panasonic.com"
<yasutake.koichi@jp.panasonic.com>,
Chris Zankel <chris@zankel.net>, "Arnd Bergmann" <arnd@arndb.de>,
Krzysztof Halasa <khalasa@piap.pl>,
Phil Edworthy <phil.edworthy@renesas.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Jingoo Han <jg1.han@samsung.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
Simon Horman <horms@verge.net.au>,
"Minghuan Lian" <minghuan.Lian@freescale.com>,
Murali Karicheri <m-karicheri2@ti.com>,
Tanmay Inamdar <tinamdar@apm.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Thierry Reding <thierry.reding@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Will Deacon <Will.Deacon@arm.com>,
Jayachandran C <jchandra@broadcom.com>
Subject: Re: [RFC/RFT PATCH] PCI: move pci_read_bridge_bases to the generic PCI layer
Date: Wed, 27 May 2015 14:48:01 -0500 [thread overview]
Message-ID: <55661F71.3090100@amd.com> (raw)
In-Reply-To: <20150527175447.GA7914@red-moon>
On 5/27/2015 12:54 PM, Lorenzo Pieralisi wrote:
>>> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
>>> > >index 062fee6..335d9f2 100644
>>> > >--- a/drivers/pci/probe.c
>>> > >+++ b/drivers/pci/probe.c
>>> > >@@ -453,7 +453,11 @@ void pci_read_bridge_bases(struct pci_bus *child)
>>> > > struct resource *res;
>>> > > int i;
>>> > >
>>> > >- if (pci_is_root_bus(child)) /* It's a host bus, nothing to read */
>>> > >+ /*
>>> > >+ * If it is not a PCI bridge there is nothing to read
>>> > >+ */
>>> > >+ if (pci_is_root_bus(child) || !dev ||
>>> > >+ !((dev->class >> 8) == PCI_CLASS_BRIDGE_PCI))
>>> > > return;
>>> > >
>>> > > dev_info(&dev->dev, "PCI bridge to %pR%s\n",
>>> > >@@ -1878,6 +1882,11 @@ unsigned int pci_scan_child_bus(struct pci_bus *bus)
>>> > > * all PCI-to-PCI bridges on this bus.
>>> > > */
>>> > > if (!bus->is_added) {
>>> > >+ /*
>>> > >+ * Read and initialize bridge resources.
>>> > >+ */
>>> > >+ pci_read_bridge_bases(bus);
>>> > >+
>>> > > dev_dbg(&bus->dev, "fixups for bus\n");
>>> > > pcibios_fixup_bus(bus);
>>> > > bus->is_added = 1;
>>> > >
>> >
>> >So, I have tested the patch on ARM64 system w/ PROBE_ONLY mode, and
>> >noticed that we are calling pci_read_bridge_bases() after adding the
>> >devices on the slots. This is not soon enough since the downstream
>> >devices still failing to claim resources.
>> >
>> >However, do you think we can move pci_read_bridge_bases() before the
>> >pci_scan_slot() loop?
> Right, how about moving it to pci_scan_bridge() before calling the
> respective pci_scan_child_bus() ? I think it belongs there anyway.
>
> Thanks,
That seems reasonable. I test putting it here in pci_scan_bridge(),
and it works.
....
child = pci_find_bus(pci_domain_nr(bus), secondary);
if (!child) {
child = pci_add_new_bus(bus, dev, secondary);
if (!child)
goto out;
child->primary = primary;
pci_bus_insert_busn_res(child, secondary, subordinate);
child->bridge_ctl = bctl;
pci_read_bridge_bases(child);
}
cmax = pci_scan_child_bus(child);
.....
Thanks,
Suravee
prev parent reply other threads:[~2015-05-27 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 13:14 [RFC/RFT PATCH] PCI: move pci_read_bridge_bases to the generic PCI layer Lorenzo Pieralisi
2015-05-26 12:57 ` Will Deacon
2015-05-26 14:21 ` Lorenzo Pieralisi
2015-05-27 16:42 ` Suravee Suthikulanit
2015-05-27 17:54 ` Lorenzo Pieralisi
2015-05-27 19:48 ` Suravee Suthikulanit [this message]
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=55661F71.3090100@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=Will.Deacon@arm.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=chris@zankel.net \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=horms@verge.net.au \
--cc=jchandra@broadcom.com \
--cc=jejb@parisc-linux.org \
--cc=jg1.han@samsung.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=khalasa@piap.pl \
--cc=kishon@ti.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=m-karicheri2@ti.com \
--cc=minghuan.Lian@freescale.com \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=phil.edworthy@renesas.com \
--cc=ralf@linux-mips.org \
--cc=rth@twiddle.net \
--cc=thierry.reding@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tinamdar@apm.com \
--cc=tony.luck@intel.com \
--cc=yasutake.koichi@jp.panasonic.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