From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: [PATCH 0/7] PCI, PNP: print resources consistently
Date: Tue, 06 Oct 2009 15:33:24 -0600 [thread overview]
Message-ID: <20091006213259.4272.68068.stgit@bob.kio> (raw)
These enhance %pR so we can print resource types and flags more easily.
This doesn't really add anything (other than a couple new messages
about host bridge apertures), but hopefully it will make things more
consistent and a bit easier to debug. Sample change (with "pci=use_crs"):
-pci 0000:00:03.0: reg 10 32bit mmio: [0xf6000000-0xf6ffffff]
-pci 0000:00:03.0: reg 14 io port: [0x2400-0x24ff]
-pci 0000:00:03.0: reg 18 32bit mmio: [0xf5ff0000-0xf5ff0fff]
-pci 0000:00:03.0: reg 30 32bit mmio pref: [0x000000-0x01ffff]
+pci_root PNP0A03:00: host bridge window: [io 0x0000-0x0cff]
+pci_root PNP0A03:00: host bridge window: [io 0x0000-0x2cfe]
+pci_root PNP0A03:00: host bridge window: [io 0x03b0-0x03bb]
+pci_root PNP0A03:00: host bridge window: [io 0x03c0-0x03df]
+pci_root PNP0A03:00: host bridge window: [mem 0xf5d00000-0xf6ffffff]
+pci_root PNP0A03:00: host bridge window: [mem 0x000a0000-0x000bffff]
+pci 0000:00:03.0: reg 10: [mem 0xf6000000-0xf6ffffff]
+pci 0000:00:03.0: reg 14: [io 0x2400-0x24ff]
+pci 0000:00:03.0: reg 18: [mem 0xf5ff0000-0xf5ff0fff]
+pci 0000:00:03.0: reg 30: [mem 0x00000000-0x0001ffff pref]
---
Bjorn Helgaas (7):
vsprintf: fix io/mem resource width
vsprintf: add %pR support for IRQ and DMA resources
vsprintf: add %pRt, %pRf to print struct resource details
PCI: print resources consistently with %pRt
x86/PCI: print resources consistently with %pRt
ia64/PCI: print resources consistently with %pRt
PNP: print resources consistently with %pRt
arch/ia64/pci/pci.c | 21 +++++++++---
arch/x86/pci/acpi.c | 14 ++++++--
arch/x86/pci/i386.c | 12 +++----
drivers/pci/pci.c | 4 +-
drivers/pci/probe.c | 26 +++++----------
drivers/pci/setup-bus.c | 9 ++---
drivers/pci/setup-res.c | 28 +++++++---------
drivers/pnp/quirks.c | 12 ++-----
drivers/pnp/resource.c | 10 ++----
drivers/pnp/support.c | 43 +++----------------------
drivers/pnp/system.c | 14 ++++----
lib/vsprintf.c | 80 ++++++++++++++++++++++++++++++++++++++---------
12 files changed, 138 insertions(+), 135 deletions(-)
--
Bjorn
next reply other threads:[~2009-10-06 21:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 21:33 Bjorn Helgaas [this message]
2009-10-06 21:33 ` [PATCH 1/7] vsprintf: fix io/mem resource width Bjorn Helgaas
2009-10-26 20:40 ` Jesse Barnes
2009-10-06 21:33 ` [PATCH 2/7] vsprintf: add %pR support for IRQ and DMA resources Bjorn Helgaas
2009-10-06 21:33 ` [PATCH 3/7] vsprintf: add %pRt, %pRf to print struct resource details Bjorn Helgaas
2009-10-06 21:33 ` [PATCH 4/7] PCI: print resources consistently with %pRt Bjorn Helgaas
2009-10-06 21:33 ` [PATCH 5/7] x86/PCI: " Bjorn Helgaas
2009-10-07 18:43 ` Yinghai Lu
2009-10-07 19:15 ` Bjorn Helgaas
2009-10-09 21:14 ` Len Brown
2009-10-10 15:36 ` Bjorn Helgaas
2009-10-06 21:33 ` [PATCH 6/7] ia64/PCI: " Bjorn Helgaas
2009-10-06 21:34 ` [PATCH 7/7] PNP: " Bjorn Helgaas
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=20091006213259.4272.68068.stgit@bob.kio \
--to=bjorn.helgaas@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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 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).