From: Bjorn Helgaas <bhelgaas@google.com>
To: linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/2] Infrastructure for Vendor-Specific extended capabilities
Date: Fri, 24 Aug 2012 15:26:13 -0600 [thread overview]
Message-ID: <CAErSpo5KZZkoc=GfWUPmVQJAx8uA8v-v2YPp_8Y=LU5PU9Ga6g@mail.gmail.com> (raw)
In-Reply-To: <20120713215258.21756.42132.stgit@bhelgaas.mtv.corp.google.com>
On Fri, Jul 13, 2012 at 3:57 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> This adds pci_find_next_ext_capability(), analogous to
> pci_find_next_capability(), which allows drivers to iterate through
> multiple capabilities of the same type.
I applied these patches to my "next" branch.
> Many devices include multiple Vendor-Specific extended capabilities, for
> example:
>
> 00:00.0 Host bridge: Intel Corporation Sandy Bridge DMI2 (rev 06)
> Capabilities: [100 v1] Vendor Specific Information: ID=0002 Rev=0 Len=00c <?>
> Capabilities: [144 v1] Vendor Specific Information: ID=0004 Rev=1 Len=03c <?>
> Capabilities: [1d0 v1] Vendor Specific Information: ID=0003 Rev=1 Len=00a <?>
> Capabilities: [280 v1] Vendor Specific Information: ID=0004 Rev=2 Len=018 <?>
>
>
> ---
>
> Bjorn Helgaas (2):
> PCI: add pci_find_next_ext_capability()
> PCI: add Vendor-Specific Extended Capability header info
>
>
> drivers/pci/pci.c | 40 ++++++++++++++++++++++++++++++----------
> include/linux/pci.h | 3 +--
> include/linux/pci_regs.h | 6 ++++++
> 3 files changed, 37 insertions(+), 12 deletions(-)
>
> --
> Bjorn
prev parent reply other threads:[~2012-08-24 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 21:57 [PATCH 0/2] Infrastructure for Vendor-Specific extended capabilities Bjorn Helgaas
2012-07-13 21:57 ` [PATCH 1/2] PCI: add pci_find_next_ext_capability() Bjorn Helgaas
2012-07-13 21:57 ` [PATCH 2/2] PCI: add Vendor-Specific Extended Capability header info Bjorn Helgaas
2012-08-24 21:26 ` Bjorn Helgaas [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='CAErSpo5KZZkoc=GfWUPmVQJAx8uA8v-v2YPp_8Y=LU5PU9Ga6g@mail.gmail.com' \
--to=bhelgaas@google.com \
--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.