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.
Any hardware that shares VPD registers with multiple functions has
been suffering these problems forever. The hangs result in the log
message:
vpd r/w failed. This is likely a firmware bug on this device.
Both read and write data corruption are also possible during
overlapping accesses in addition to hangs.
Signed-off-by: Mark Rustad <mark.d.rustad@xxxxxxxxx>
---
Changes in V2:
- Corrected a spelling error in a log message
- Added checks to see that the referenced function 0 is reasonable
Changes in V3:
- Don't leak a device reference
- Check that function 0 has VPD
- Make a helper for the function 0 checks
- Moved a multifunction check to the quirk patch
Changes in V4:
- Provide a more extensive commit log for patch 1
---
Mark 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 | 61 +++++++++++++++++++++++++++++++++++++++++++++++++-
drivers/pci/quirks.c | 9 +++++++
include/linux/pci.h | 2 ++
3 files changed, 71 insertions(+), 1 deletion(-)
--
Mark Rustad, Network Division, Intel Corporation
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
