From: wangyijing@huawei.com (Yijing Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH Part1 v11 5/5] PCI: iproc: Use pci_scan_root_bus() instead of pci_create_root_bus()
Date: Wed, 29 Apr 2015 09:08:55 +0800 [thread overview]
Message-ID: <55402F27.3080204@huawei.com> (raw)
In-Reply-To: <553FB772.1000202@broadcom.com>
>> @@ -210,10 +210,10 @@ int iproc_pcie_setup(struct iproc_pcie *pcie)
>>
>> pcie->sysdata.private_data = pcie;
>>
>> - bus = pci_create_root_bus(pcie->dev, 0, &iproc_pcie_ops,
>> + bus = pci_scan_root_bus(pcie->dev, 0, &iproc_pcie_ops,
>> &pcie->sysdata, pcie->resources);
>> if (!bus) {
>> - dev_err(pcie->dev, "unable to create PCI root bus\n");
>> + dev_err(pcie->dev, "unable to scan PCI root bus\n");
>> ret = -ENOMEM;
>> goto err_power_off_phy;
>> }
>
> iproc_pcie_check_link is called here by using the 'bus' structure
> returned from pci_create_root_bus. In iproc_pcie_check_link, we
> configure root bus class to PCI_CLASS_BRIDGE_PCI and validate to ensure
> a stable link between RC and EP can be detected.
Oh, I got it. Thanks for your explanation.
>
>> @@ -227,7 +227,6 @@ int iproc_pcie_setup(struct iproc_pcie *pcie)
>>
>> iproc_pcie_enable(pcie);
>
> Here we enable INTx support for our RC controller.
>
>>
>> - pci_scan_child_bus(bus);
>
> Here, if pci_scan_child_bus is moved to before iproc_pcie_check_link, I
> don't think it would work (although I have not tested this).
>
> An alternative is to use a dummy bus structure to feed into
> iproc_pcie_check_link, and call iproc_pcie_check_link and
> iproc_pcie_enable before pci_scan_root_bus. But the reason I put the
> link check code in between pci_create_root_bus and pci_scan_child_bus
> was to avoid using a dummy bus structure, :)
Maybe we could refactor this by add a new pci_host_bridge_ops in the later patch.
>
>> pci_assign_unassigned_bus_resources(bus);
>> pci_fixup_irqs(pci_common_swizzle, of_irq_parse_and_map_pci);
>> pci_bus_add_devices(bus);
>>
>
> Thanks,
>
> Ray
>
> .
>
--
Thanks!
Yijing
next prev parent reply other threads:[~2015-04-29 1:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 7:01 [PATCH Part1 v11 0/5] Some cleanup for pcie host drivers Yijing Wang
2015-04-28 7:01 ` [PATCH Part1 v11 1/5] PCI: mvebu: Use pci_common_init_dev() to simplify code Yijing Wang
2015-05-27 0:11 ` Bjorn Helgaas
2015-04-28 7:01 ` [PATCH Part1 v11 2/5] PCI: tegra: Remove redundant tegra_pcie_scan_bus() Yijing Wang
2015-04-28 7:01 ` [PATCH Part1 v11 3/5] PCI: designware: Use pci_scan_root_bus() for simplicity Yijing Wang
2015-04-28 8:15 ` Lucas Stach
2015-05-27 0:12 ` Bjorn Helgaas
2015-04-28 7:01 ` [PATCH Part1 v11 4/5] PCI: xgene: Use pci_scan_root_bus() instead of pci_create_root_bus() Yijing Wang
2015-05-27 15:47 ` Bjorn Helgaas
2015-05-27 17:21 ` Tanmay Inamdar
2015-06-16 18:49 ` Bjorn Helgaas
2015-04-28 7:01 ` [PATCH Part1 v11 5/5] PCI: iproc: " Yijing Wang
2015-04-28 16:38 ` Ray Jui
2015-04-29 1:08 ` Yijing Wang [this message]
2015-04-29 1:12 ` Yijing Wang
2015-05-14 8:32 ` [PATCH Part1 v11 0/5] Some cleanup for pcie host drivers Yijing Wang
2015-05-27 16:45 ` 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=55402F27.3080204@huawei.com \
--to=wangyijing@huawei.com \
--cc=linux-arm-kernel@lists.infradead.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).