From: Yijing Wang <wangyijing@huawei.com>
To: Daniel Axtens <dja@axtens.net>
Cc: Liviu Dudau <liviu@dudau.co.uk>,
x86@kernel.org, linux-ia64@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Marc Zyngier <marc.zyngier@arm.com>,
linux-pci@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org,
Jiang Liu <jiang.liu@linux.intel.com>,
linux-m68k@lists.linux-m68k.org, Tony Luck <tony.luck@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Yinghai Lu <yinghai@kernel.org>,
linux-alpha@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Russell King <linux@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 19/30] powerpc/pci: Use pci_scan_host_bridge() for simplicity
Date: Thu, 26 Mar 2015 09:17:10 +0800 [thread overview]
Message-ID: <55135E16.6060909@huawei.com> (raw)
In-Reply-To: <1427321631.2575.3.camel@axtens.net>
On 2015/3/26 6:13, Daniel Axtens wrote:
> Hi Yijing,
>
> I wasn't quite sure I understood your comments, so I was trying to apply
> your patch series and test it, but patch 3 doesn't apply cleanly to
> 4.0-rc5 or master. Can you respin the series?
Hi Daniel,
Could you pull the series from Bjorn's git tree ? The URL is
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci/enumeration-yw8
Thanks!
Yijing.
>
> Thanks,
> Daniel
>
>
>> Hi Daniel, thanks for your review and comments. We want to make a generic pci_host_bridge,
>> which would hold the common host information, for example, pci domain is common info for
>> pci host bridge, this series saved domain in pci_host_bridge, then we no need to
>> extract out domain by pci_bus->sysdata by platform specific pci_domain_nr().
>> Also we store the sysdata in pci_host_bridge, and pci_bus_to_host() is the platform
>> interface, I think use the common interface would be better.
>>
>>>> +
>>>> + /* Get probe mode and perform scan */
>>>> + if (hose->dn && ppc_md.pci_probe_mode)
>>>> + mode = ppc_md.pci_probe_mode(bus);
>>>> +
>>>> + pr_debug(" probe mode: %d\n", mode);
>>>> + if (mode == PCI_PROBE_DEVTREE)
>>>> + of_scan_bus(hose->dn, bus);
>>>> +
>>>> + if (mode == PCI_PROBE_NORMAL) {
>>>> + pci_bus_update_busn_res_end(bus, 255);
>>>> + hose->last_busno = pci_scan_child_bus(bus);
>>>> + pci_bus_update_busn_res_end(bus, hose->last_busno);
>>>> + }
>>>> +
>>>> + return pci_bus_child_max_busnr(bus);
>>>> +}
>>>> +
>>> I'm having trouble convincing myself that this patch covers every
>>> variation within our PCI implementations. In particular, there's a
>>> stanza in of_scan_pci_bridge in kernel/pci_of_scan.c that's almost
>>> identical to this function. Does that implementation need to be cleaned
>>> up and replaced with this function too?
>>>
>>
>> This is a pci_host_bridge_ops hook function, which would be called in
>> PCI core, and after applied this series, we only need to call pci_scan_host_bridge()
>> to scan pci devices, and this function is also extracted from the pcibios_scan_phb(),
>> it's not the redundant code.
>>
>>>
>>>> @@ -1641,9 +1655,9 @@ void pcibios_scan_phb(struct pci_controller *hose)
>>>> ppc_md.pcibios_fixup_phb(hose);
>>>>
>>>> /* Configure PCI Express settings */
>>>> - if (bus && !pci_has_flag(PCI_PROBE_ONLY)) {
>>>> + if (host->bus && !pci_has_flag(PCI_PROBE_ONLY)) {
>>>> struct pci_bus *child;
>>>> - list_for_each_entry(child, &bus->children, node)
>>>> + list_for_each_entry(child, &host->bus->children, node)
>>>> pcie_bus_configure_settings(child);
>>>> }
>>>> }
>>> Two things: Firstly, the function uses hose throughout, not host.
>>> Secondly, you're not deleting the bus variable: what's the purpose of
>>> this change?
>>
>> host is the common pci_host_bridge which is created by PCI core for pci host bridge driver,
>> the hose is the platform data used in powerpc. The purpose of the patch/series is to simplify
>> pci enumeration interface, and try to reduce the weak functions which were used to setup pci bus/devices
>> during PCI enumeration.
>>
>>>
>>> Regards,
>>> Daniel
>>>
>>
>>
>
--
Thanks!
Yijing
next prev parent reply other threads:[~2015-03-26 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427168064-8657-1-git-send-email-wangyijing@huawei.com>
2015-03-24 3:34 ` [PATCH v8 19/30] powerpc/pci: Use pci_scan_host_bridge() for simplicity Yijing Wang
2015-03-24 23:58 ` Daniel Axtens
2015-03-25 7:42 ` Yijing Wang
2015-03-25 22:13 ` Daniel Axtens
2015-03-26 1:17 ` Yijing Wang [this message]
2015-03-26 5:19 ` Daniel Axtens
2015-03-26 6:20 ` Yijing Wang
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=55135E16.6060909@huawei.com \
--to=wangyijing@huawei.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=dja@axtens.net \
--cc=geert@linux-m68k.org \
--cc=gxt@mprc.pku.edu.cn \
--cc=jiang.liu@linux.intel.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liviu@dudau.co.uk \
--cc=marc.zyngier@arm.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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).