All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org,
	linux-pci@vger.kernel.org
Subject: [PATCH v3 0/2] pci_root: track downstream bus range
Date: Tue, 09 Mar 2010 15:53:20 -0700	[thread overview]
Message-ID: <20100309225211.27167.54296.stgit@bob.kio> (raw)

These patches keep track of both the beginning and end of the bus number
range under a PCI host bridge (previously we only kept the beginning) and
make that range available to the arch code, which will need it to support
the _CBA mechanism for reporting MMCONFIG regions.

These apply on the acpi-test tree.

---

Bjorn Helgaas (2):
      ACPI: pci_root: save downstream bus range
      ACPI: pci_root: pass acpi_pci_root to arch-specific scan


 arch/ia64/pci/pci.c         |    5 +++
 arch/x86/pci/acpi.c         |    5 +++
 drivers/acpi/pci_root.c     |   67 ++++++++++++++++++++++++++-----------------
 include/acpi/acpi_bus.h     |    2 +
 include/acpi/acpi_drivers.h |    3 +-
 5 files changed, 50 insertions(+), 32 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org,
	linux-pci@vger.kernel.org
Subject: [PATCH v3 0/2] pci_root: track downstream bus range
Date: Tue, 09 Mar 2010 22:53:20 +0000	[thread overview]
Message-ID: <20100309225211.27167.54296.stgit@bob.kio> (raw)

These patches keep track of both the beginning and end of the bus number
range under a PCI host bridge (previously we only kept the beginning) and
make that range available to the arch code, which will need it to support
the _CBA mechanism for reporting MMCONFIG regions.

These apply on the acpi-test tree.

---

Bjorn Helgaas (2):
      ACPI: pci_root: save downstream bus range
      ACPI: pci_root: pass acpi_pci_root to arch-specific scan


 arch/ia64/pci/pci.c         |    5 +++
 arch/x86/pci/acpi.c         |    5 +++
 drivers/acpi/pci_root.c     |   67 ++++++++++++++++++++++++++-----------------
 include/acpi/acpi_bus.h     |    2 +
 include/acpi/acpi_drivers.h |    3 +-
 5 files changed, 50 insertions(+), 32 deletions(-)

             reply	other threads:[~2010-03-09 22:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 22:53 Bjorn Helgaas [this message]
2010-03-09 22:53 ` [PATCH v3 0/2] pci_root: track downstream bus range Bjorn Helgaas
2010-03-09 22:53 ` [PATCH v3 1/2] ACPI: pci_root: save " Bjorn Helgaas
2010-03-09 22:53   ` Bjorn Helgaas
2010-03-10  9:50   ` Kenji Kaneshige
2010-03-10  9:50     ` Kenji Kaneshige
2010-03-10 16:15     ` Bjorn Helgaas
2010-03-10 16:15       ` Bjorn Helgaas
2010-03-09 22:53 ` [PATCH v3 2/2] ACPI: pci_root: pass acpi_pci_root to arch-specific scan Bjorn Helgaas
2010-03-09 22:53   ` [PATCH v3 2/2] ACPI: pci_root: pass acpi_pci_root to arch-specific Bjorn Helgaas
2010-03-10  9:51   ` [PATCH v3 2/2] ACPI: pci_root: pass acpi_pci_root to arch-specific scan Kenji Kaneshige
2010-03-10  9:51     ` [PATCH v3 2/2] ACPI: pci_root: pass acpi_pci_root to arch-specific Kenji Kaneshige

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=20100309225211.27167.54296.stgit@bob.kio \
    --to=bjorn.helgaas@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-pci@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.