From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, Alex Chiang <achiang@hp.com>,
Shaohua Li <shaohua.li@intel.com>
Subject: Re: [PATCH 1/5] ACPI: pci_root: check _CRS, then _BBN for downstream bus number
Date: Fri, 19 Jun 2009 12:35:58 +0900 [thread overview]
Message-ID: <4A3B079E.1070903@jp.fujitsu.com> (raw)
In-Reply-To: <20090618204647.15850.97454.stgit@bob.kio>
Bjorn Helgaas wrote:
> To find a host bridge's downstream bus number, we currently look at _BBN
> first. If _BBN returns a bus number we've already seen, we conclude that
> _BBN was wrong and look for a bus number in _CRS.
>
> However, the spec[1] (figure 5-5 and the example in sec 9.12.1) and an ACPI
> FAQ[2] suggest that the OS should use _CRS to discover the bus number
> range, and that _BBN is really intended to bootstrap _CRS methods that
> reference PCI opregions.
>
> This patch makes us always look at _CRS first. If _CRS doesn't supply a
> bus number, we look at _BBN. If _BBN doesn't exist, we default to zero.
> This makes the behavior consistent regardless of device discovery order.
> Previously, if A and B had duplicate _BBNs and we found A first, we'd only
> look at B's _CRS, whereas if we found B first, we'd only look at A's _CRS.
>
> I'm told that Windows discovers host bridge bus numbers using _CRS, so
> it should be fairly safe to rely on this BIOS functionality.
>
> This patch also removes two misleading messages: we printed the "Wrong _BBN
> value, reboot and use option 'pci=noacpi'" message before looking at _CRS,
> so we would likely find the bus number in _CRS, the system would work fine,
> and the user would be confused. The "PCI _CRS %d overrides _BBN 0" message
> incorrectly assumes _BBN was zero, and it's useless anyway because we
> print the segment/bus number a few lines later.
Though it might be very stupid question, can I ask you a question?
Is minimum value of PCI bus number range reported by _CRS always
equal to the bus number of the PCI root bus? I glanced over the
specs, but I could not confirm it.
Thanks,
Kenji Kaneshige
>
> References:
> [1] http://www.acpi.info/DOWNLOADS/ACPIspec30b.pdf
> [2] http://www.acpi.info/acpi_faq.htm _BBN/_CRS discussion
> http://download.microsoft.com/download/9/8/f/98f3fe47-dfc3-4e74-92a3-088782200fe7/TWAR05005_WinHEC05.ppt (slide 17)
> http://bugzilla.kernel.org/show_bug.cgi?id=1662 ASUS PR-DLS
> http://bugzilla.kernel.org/show_bug.cgi?id=1127 ASUS PR-DLSW
> http://bugzilla.kernel.org/show_bug.cgi?id=1741 ASUS PR-DLS533
>
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> Reviewed-by: Alex Chiang <achiang@hp.com>
> CC: Shaohua Li <shaohua.li@intel.com>
> CC: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
> ---
> drivers/acpi/pci_root.c | 54 ++++++++++++++---------------------------------
> 1 files changed, 16 insertions(+), 38 deletions(-)
>
> diff --git a/drivers/acpi/pci_root.c b/drivers/acpi/pci_root.c
> index f341b07..7847732 100644
> --- a/drivers/acpi/pci_root.c
> +++ b/drivers/acpi/pci_root.c
> @@ -470,12 +470,12 @@ static int __devinit acpi_pci_root_add(struct acpi_device *device)
> {
> int result = 0;
> struct acpi_pci_root *root = NULL;
> - struct acpi_pci_root *tmp;
> acpi_status status = AE_OK;
> unsigned long long value = 0;
> acpi_handle handle = NULL;
> struct acpi_device *child;
> u32 flags, base_flags;
> + int bus;
>
>
> if (!device)
> @@ -523,46 +523,24 @@ static int __devinit acpi_pci_root_add(struct acpi_device *device)
> /*
> * Bus
> * ---
> - * Obtained via _BBN, if exists, otherwise assumed to be zero (0).
> + * Check _CRS first, then _BBN. If no _BBN, default to zero.
> */
> - status = acpi_evaluate_integer(device->handle, METHOD_NAME__BBN, NULL,
> - &value);
> - switch (status) {
> - case AE_OK:
> - root->id.bus = (u16) value;
> - break;
> - case AE_NOT_FOUND:
> - ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Assuming bus 0 (no _BBN)\n"));
> - root->id.bus = 0;
> - break;
> - default:
> - ACPI_EXCEPTION((AE_INFO, status, "Evaluating _BBN"));
> - result = -ENODEV;
> - goto end;
> - }
> -
> - /* Some systems have wrong _BBN */
> - list_for_each_entry(tmp, &acpi_pci_roots, node) {
> - if ((tmp->id.segment == root->id.segment)
> - && (tmp->id.bus == root->id.bus)) {
> - int bus = 0;
> - acpi_status status;
> -
> - printk(KERN_ERR PREFIX
> - "Wrong _BBN value, reboot"
> - " and use option 'pci=noacpi'\n");
> -
> - status = try_get_root_bridge_busnr(device->handle, &bus);
> - if (ACPI_FAILURE(status))
> - break;
> - if (bus != root->id.bus) {
> - printk(KERN_INFO PREFIX
> - "PCI _CRS %d overrides _BBN 0\n", bus);
> - root->id.bus = bus;
> - }
> - break;
> + status = try_get_root_bridge_busnr(device->handle, &bus);
> + if (ACPI_SUCCESS(status))
> + root->id.bus = bus;
> + else {
> + status = acpi_evaluate_integer(device->handle, METHOD_NAME__BBN, NULL, &value);
> + if (ACPI_SUCCESS(status))
> + root->id.bus = (u16) value;
> + else if (status == AE_NOT_FOUND)
> + root->id.bus = 0;
> + else {
> + ACPI_EXCEPTION((AE_INFO, status, "Evaluating _BBN"));
> + result = -ENODEV;
> + goto end;
> }
> }
> +
> /*
> * Device & Function
> * -----------------
>
>
>
next prev parent reply other threads:[~2009-06-19 3:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 20:46 [PATCH 0/5] PCI root bridge: get bus info from _CRS Bjorn Helgaas
2009-06-18 20:46 ` [PATCH 1/5] ACPI: pci_root: check _CRS, then _BBN for downstream bus number Bjorn Helgaas
2009-06-19 3:35 ` Kenji Kaneshige [this message]
2009-06-18 20:46 ` [PATCH 2/5] ACPI: pci_root: simplify acpi_pci_root_add() control flow Bjorn Helgaas
2009-06-18 20:46 ` [PATCH 3/5] ACPI: pci_root: use driver data rather than list lookup Bjorn Helgaas
2009-06-18 20:47 ` [PATCH 4/5] ACPI: pci_root: simplify list traversals Bjorn Helgaas
2009-06-18 20:47 ` [PATCH 5/5] ACPI: pci_root: remove unused dev/fn information Bjorn Helgaas
2009-06-20 4:10 ` [PATCH 0/5] PCI root bridge: get bus info from _CRS Len Brown
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=4A3B079E.1070903@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=achiang@hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=shaohua.li@intel.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