From: Tomasz Nowicki <tomasz.nowicki@linaro.org>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [Patch v7 4/7] PCI/ACPI: Add interface acpi_pci_root_create()
Date: Wed, 21 Oct 2015 13:27:33 +0200 [thread overview]
Message-ID: <562776A5.7000303@linaro.org> (raw)
In-Reply-To: <20151021110201.GE3394@e106497-lin.cambridge.arm.com>
On 21.10.2015 13:02, Liviu Dudau wrote:
> On Wed, Oct 21, 2015 at 11:57:53AM +0200, Tomasz Nowicki wrote:
>> On 14.10.2015 08:29, Jiang Liu wrote:
>>> Introduce common interface acpi_pci_root_create() and related data
>>> structures to create PCI root bus for ACPI PCI host bridges. It will
>>> be used to kill duplicated arch specific code for IA64 and x86. It may
>>> also help ARM64 in future.
>>>
>>> Reviewed-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
>>> Tested-by: Tony Luck <tony.luck@intel.com>
>>> Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
>>> Signed-off-by: Liu Jiang <jiang.liu@linux.intel.com>
>>> ---
>>> drivers/acpi/pci_root.c | 204 ++++++++++++++++++++++++++++++++++++++++++++++
>>> include/linux/pci-acpi.h | 24 ++++++
>>> 2 files changed, 228 insertions(+)
>>>
>>
>> [...]
>>
>>> +
>>> +struct pci_bus *acpi_pci_root_create(struct acpi_pci_root *root,
>>> + struct acpi_pci_root_ops *ops,
>>> + struct acpi_pci_root_info *info,
>>> + void *sysdata)
>>> +{
>>> + int ret, busnum = root->secondary.start;
>>> + struct acpi_device *device = root->device;
>>> + int node = acpi_get_node(device->handle);
>>> + struct pci_bus *bus;
>>> +
>>> + info->root = root;
>>> + info->bridge = device;
>>> + info->ops = ops;
>>> + INIT_LIST_HEAD(&info->resources);
>>> + snprintf(info->name, sizeof(info->name), "PCI Bus %04x:%02x",
>>> + root->segment, busnum);
>>> +
>>> + if (ops->init_info && ops->init_info(info))
>>> + goto out_release_info;
>>> + if (ops->prepare_resources)
>>> + ret = ops->prepare_resources(info);
>>> + else
>>> + ret = acpi_pci_probe_root_resources(info);
>>> + if (ret < 0)
>>> + goto out_release_info;
>>> +
>>> + pci_acpi_root_add_resources(info);
>>> + pci_add_resource(&info->resources, &root->secondary);
>>> + bus = pci_create_root_bus(NULL, busnum, ops->pci_ops,
>>> + sysdata, &info->resources);
>>
>> Thank a lot for this cleanup!!
>>
>> I recall you already considered passing segment (domain nr) to
>> pci_create_root_bus, right? Can you please remind me why we gave up on this?
>>
>> I am asking because currently I can not find the way to retrieve domain
>> number from pci_bus_assign_domain_nr (for those platforms which choose
>> PCI_DOMAINS_GENERIC and want to use segment nr from MCFG table) which is the
>> part of pci_create_root_bus.
>
> Not sure I fully understand your question, but pci_bus_assign_domain_nr() will
> put the assigned domain number in bus->domain_nr if you chose PCI_DOMAINS_GENERIC.
> Do you want to override that value with the segment nr from MCFG?
>
Let me give ACPI ARM64 example:
1. We parse MCFG table and get segment nr assigned to root bridge
2. Then PCI host bridge calls acpi_pci_root_create ->
pci_create_root_bus -> pci_bus_assign_domain_nr
3. At this point we cannot get segment nr for ACPI
So I would like to assign MCFG segment nr to bus->domain_nr being in
pci_bus_assign_domain_nr giving we have scenario above.
Thanks,
Tomasz
next prev parent reply other threads:[~2015-10-21 11:27 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 6:29 [Patch v7 0/7] Consolidate ACPI PCI root common code into ACPI core Jiang Liu
2015-10-14 6:29 ` [Patch v7 1/7] ACPI/PCI: Enhance ACPI core to support sparse IO space Jiang Liu
2015-10-14 6:29 ` [Patch v7 2/7] ia64/PCI/ACPI: Use common ACPI resource parsing interface for host bridge Jiang Liu
2015-10-14 6:29 ` [Patch v7 3/7] ia64/PCI: Use common struct resource_entry to replace struct iospace_resource Jiang Liu
2015-10-14 6:29 ` [Patch v7 4/7] PCI/ACPI: Add interface acpi_pci_root_create() Jiang Liu
2015-10-15 20:47 ` Bjorn Helgaas
2015-10-21 9:57 ` Tomasz Nowicki
2015-10-21 11:02 ` Liviu Dudau
2015-10-21 11:27 ` Tomasz Nowicki [this message]
2015-10-21 11:42 ` Lorenzo Pieralisi
2015-10-21 12:16 ` Tomasz Nowicki
2015-10-21 11:48 ` Liviu Dudau
2015-10-21 11:49 ` Jiang Liu
2015-10-21 11:52 ` Liviu Dudau
2015-11-05 14:21 ` Tomasz Nowicki
2015-11-05 18:19 ` Lorenzo Pieralisi
2015-11-06 7:55 ` Jiang Liu
2015-11-06 8:52 ` Jiang Liu
2015-11-06 10:37 ` Tomasz Nowicki
2015-11-06 11:46 ` Jiang Liu
2015-11-06 12:40 ` Tomasz Nowicki
2015-11-06 13:22 ` Jiang Liu
2015-11-06 14:45 ` Lorenzo Pieralisi
2015-11-06 15:32 ` Jiang Liu
2015-11-06 15:44 ` Jiang Liu
2015-11-23 15:23 ` Sinan Kaya
2015-11-09 14:07 ` Tomasz Nowicki
2015-11-09 17:10 ` Lorenzo Pieralisi
2015-11-09 20:09 ` Arnd Bergmann
2015-11-10 5:50 ` Jiang Liu
2015-11-11 17:46 ` Lorenzo Pieralisi
2015-11-11 18:12 ` Liviu Dudau
2015-11-11 20:55 ` Arnd Bergmann
2015-11-12 12:08 ` Lorenzo Pieralisi
2015-11-12 8:43 ` Jiang Liu
2015-11-12 13:21 ` Tomasz Nowicki
2015-11-12 14:04 ` Jiang Liu
2015-11-12 14:45 ` Tomasz Nowicki
2015-11-12 15:05 ` Jiang Liu
2015-11-13 12:57 ` Tomasz Nowicki
2015-11-13 17:03 ` Lorenzo Pieralisi
2015-11-13 17:49 ` Jiang Liu
2015-11-20 10:18 ` Lorenzo Pieralisi
2015-11-27 6:59 ` Tomasz Nowicki
2015-11-06 12:51 ` Lorenzo Pieralisi
2015-11-06 10:18 ` Tomasz Nowicki
2015-11-06 7:51 ` Jiang Liu
2015-10-14 6:29 ` [Patch v7 5/7] ACPI, PCI: Reset acpi_root_dev->domain to 0 when pci_ignore_seg is set Jiang Liu
2015-10-14 6:29 ` [Patch v7 6/7] x86/PCI/ACPI: Use common interface to support PCI host bridge Jiang Liu
2015-10-15 20:46 ` Bjorn Helgaas
2015-10-14 6:29 ` [Patch v7 7/7] ia64/PCI/ACPI: " Jiang Liu
2015-10-15 20:48 ` [Patch v7 0/7] Consolidate ACPI PCI root common code into ACPI core Bjorn Helgaas
2015-10-15 21:49 ` Rafael J. Wysocki
2015-10-16 1:56 ` Jiang Liu
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=562776A5.7000303@linaro.org \
--to=tomasz.nowicki@linaro.org \
--cc=Liviu.Dudau@arm.com \
--cc=bhelgaas@google.com \
--cc=hanjun.guo@linaro.org \
--cc=jiang.liu@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=x86@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).