From: Mark D Rustad <mark.d.rustad@intel.com>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org
Subject: [PATCH V2 0/2] pci: Provide a flag to access VPD through function 0
Date: Tue, 02 Jun 2015 17:10:06 -0700 [thread overview]
Message-ID: <20150603000645.71269.26134.stgit@mdrustad-wks.jf.intel.com> (raw)
Many multi-function devices provide shared registers in extended
config space for accessing VPD. The behavior of these registers
means that the state must be tracked and access locked correctly
for accesses not to hang or worse. One way to meet these needs is
to always perform the accesses through function 0, thereby using
the state tracking and mutex that already exists.
To provide this behavior, add a dev_flags bit to indicate that this
should be done. This bit can then be set for any non-zero function
that needs to redirect such VPD access to function 0. Do not set
this bit on the zero function or there will be an infinite recursion.
The second patch uses this new flag to invoke this behavior on all
multi-function Intel Ethernet devices.
Signed-off-by: Mark Rustad <mark.d.rustad@intel.com>
---
Changes in V2:
- Corrected a spelling error in a log message
- Added checks to see that the referenced function 0 is reasonable
---
Mark D Rustad (2):
pci: Add dev_flags bit to access VPD through function 0
pci: Add VPD quirk for Intel Ethernet devices
drivers/pci/access.c | 48 +++++++++++++++++++++++++++++++++++++++++++++++-
drivers/pci/quirks.c | 9 +++++++++
2 files changed, 56 insertions(+), 1 deletion(-)
--
Mark Rustad, Network Division, Intel Corporation
next reply other threads:[~2015-06-03 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 0:10 Mark D Rustad [this message]
2015-06-03 0:10 ` [PATCH V2 1/2] pci: Add dev_flags bit to access VPD through function 0 Mark D Rustad
2015-06-03 2:28 ` [Intel-wired-lan] " Alexander Duyck
2015-06-03 16:16 ` Rustad, Mark D
2015-06-03 0:10 ` [PATCH V2 2/2] pci: Add VPD quirk for Intel Ethernet devices Mark D Rustad
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=20150603000645.71269.26134.stgit@mdrustad-wks.jf.intel.com \
--to=mark.d.rustad@intel.com \
--cc=bhelgaas@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@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).