From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Adam Belay <abelay@mit.edu>
Subject: [PATCH v2 0/7] resource, PNPACPI: add bus number and window support
Date: Fri, 05 Mar 2010 10:47:21 -0700 [thread overview]
Message-ID: <20100305174656.21946.93874.stgit@bob.kio> (raw)
These patches add a new resource type, IORESOURCE_BUS, a new resource flag,
IORESOURCE_WINDOW, and PNPACPI support that uses them.
IORESOURCE_BUS is for PCI bus number ranges. For bridge devices, ACPI reports
secondary bus number ranges in _CRS descriptors, but we currently ignore them.
Adding this resource type will allow us to handle those descriptors in PNPACPI.
IORESOURCE_WINDOW is also for bridges: ACPI reports the regions that the bridge
forwards to its secondary bus. We have _CRS parsing code in pci_root.c that
handles these window descriptors, but PNPACPI currently ignores them. Adding
this flag bit will allow PNPACPI to deal with the windows correctly.
No drivers use bus or window resources yet, but ultimately, I would like to
drop the _CRS parsing code from pci_root.c and rely on PNPACPI to do it for us.
The current effect of this series is to change /sys/bus/pnp/.../resources (and
"lspnp -v" output) from this:
00:00 PNP0a03 PCI bus
state = active
to something like this:
00:00 PNP0a03 PCI bus
state = active
bus 0x0-0x0
io 0x0-0xcff window
io 0x0-0x2cfe window
io 0x3b0-0x3bb window
io 0x3c0-0x3df window
mem 0xf5d00000-0xf6ffffff window
mem disabled
mem 0xa0000-0xbffff window
Changes from v1 to v2:
- Add close quote in vsprintf SPECIAL comment (Randy Dunlap).
---
Bjorn Helgaas (7):
resource: expand IORESOURCE_TYPE_BITS to make room for bus resource type
vsprintf: clarify comments for printf_spec flags
vsprintf: move %pR resource printf_specs off the stack
resource: add bus number support
resource: add window support
PNPACPI: add window support
PNPACPI: add bus number support
drivers/pnp/base.h | 3 ++
drivers/pnp/interface.c | 7 +++--
drivers/pnp/pnpacpi/rsparser.c | 49 ++++++++++++++++++++++----------
drivers/pnp/resource.c | 27 +++++++++++++++++
drivers/pnp/support.c | 4 ++-
include/linux/ioport.h | 18 ++++++------
lib/vsprintf.c | 62 +++++++++++++++++++++++++---------------
7 files changed, 119 insertions(+), 51 deletions(-)
next reply other threads:[~2010-03-05 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 17:47 Bjorn Helgaas [this message]
2010-03-05 17:47 ` [PATCH v2 1/7] resource: expand IORESOURCE_TYPE_BITS to make room for bus resource type Bjorn Helgaas
2010-03-05 17:47 ` [PATCH v2 2/7] vsprintf: clarify comments for printf_spec flags Bjorn Helgaas
2010-03-05 17:47 ` [PATCH v2 3/7] vsprintf: move %pR resource printf_specs off the stack Bjorn Helgaas
2010-03-05 17:47 ` [PATCH v2 4/7] resource: add bus number support Bjorn Helgaas
2010-03-05 17:47 ` [PATCH v2 5/7] resource: add window support Bjorn Helgaas
2010-03-05 17:47 ` [PATCH v2 6/7] PNPACPI: " Bjorn Helgaas
2010-03-05 17:47 ` [PATCH v2 7/7] PNPACPI: add bus number support Bjorn Helgaas
2010-03-06 19:50 ` [PATCH v2 0/7] resource, PNPACPI: add bus number and window support Linus Torvalds
2010-03-08 19:19 ` 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=20100305174656.21946.93874.stgit@bob.kio \
--to=bjorn.helgaas@hp.com \
--cc=abelay@mit.edu \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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