From: Tang Chen <tangchen@cn.fujitsu.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: lenb@kernel.org, yinghai@kernel.org, jiang.liu@huawei.com,
izumi.taku@jp.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add PNP0A08 into acpi_pci_roots array.
Date: Thu, 18 Oct 2012 13:52:21 +0800 [thread overview]
Message-ID: <507F9915.2080409@cn.fujitsu.com> (raw)
In-Reply-To: <CAErSpo6ehw1JHMyE27MuX2VR89+1zC48QJe9Udih88N-W-73Wg@mail.gmail.com>
On 10/18/2012 11:55 AM, Bjorn Helgaas wrote:
> On Wed, Oct 17, 2012 at 8:22 PM, Tang Chen<tangchen@cn.fujitsu.com> wrote:
>> acpi_pci_roots array doesn't include PNP0A08, which is PCI Express
>> Root Bridge.
>
> You need to explain why this change is necessary. PNP0A08 devices
> will have a PNP0A03 _CID, so the driver already claims PNP0A08 devices
> because the _CID matches.
Hi Bjorn,
Here is my reason, but just my personal opinion. :)
1) There is no code to handle a pcie host bridge hotplug in kernel now.
And when this happens, pci host bridge related code will be
executed, which makes me think that PNP0A03 and PNP0A08 are seen as
the same devices. At least for now they are.
So, acpi_pci_roots doesn't include PNP0A08 seems a little strange to
me.
2) When I was reading Liu Jiang's "ACPI based hotplug framework"
patches, I happened to see that he defined the following:
static char *acpihp_dev_pcihb_ids[] = {
"PNP0A03",
"PNP0A08",
NULL
};
And also, Lu Yinghai defined the following in his own patch:
static const struct acpi_device_id root_device_ids[] = {
{"PNP0A03", 0},
{"PNP0A08", 0},
{NULL, 0}
};
I think all these arraies should represent the same things, and we
need only one of them.
For now, it is root_device_ids[] in drivers/acpi/pci_root.c.
Well, all above is my own opinion. And you are right, even if we don't
change it, there won't be any problem.
Thanks. :)
>
>> Signed-off-by: Tang Chen<tangchen@cn.fujitsu.com>
>> ---
>> drivers/acpi/pci_root.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/acpi/pci_root.c b/drivers/acpi/pci_root.c
>> index 037b59c..dedc4d6 100644
>> --- a/drivers/acpi/pci_root.c
>> +++ b/drivers/acpi/pci_root.c
>> @@ -56,6 +56,7 @@ static int acpi_pci_root_start(struct acpi_device *device);
>>
>> static const struct acpi_device_id root_device_ids[] = {
>> {"PNP0A03", 0},
>> + {"PNP0A08", 0},
>> {"", 0},
>> };
>> MODULE_DEVICE_TABLE(acpi, root_device_ids);
>> --
>> 1.7.1
>>
>
prev parent reply other threads:[~2012-10-18 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 2:22 [PATCH] Add PNP0A08 into acpi_pci_roots array Tang Chen
2012-10-18 3:55 ` Bjorn Helgaas
2012-10-18 5:52 ` Tang Chen [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=507F9915.2080409@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=bhelgaas@google.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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).