summaryrefslogtreecommitdiff
path: root/Kbuild
diff options
context:
space:
mode:
authorMark Rustad <mark.d.rustad@intel.com>2015-07-13 11:40:02 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2015-09-21 10:10:48 -0700
commitdbabc222f96398c3c25a2f9da404aa21dda68bc3 (patch)
tree5d4b8ff1e5c05a18b4765054037a6c6c8cf99661 /Kbuild
parent2aeb4858fa61583bb4b01c9b4ab84b273573eafc (diff)
downloadlwn-dbabc222f96398c3c25a2f9da404aa21dda68bc3.tar.gz
lwn-dbabc222f96398c3c25a2f9da404aa21dda68bc3.zip
PCI: Add dev_flags bit to access VPD through function 0
commit 932c435caba8a2ce473a91753bad0173269ef334 upstream. Add a dev_flags bit, PCI_DEV_FLAGS_VPD_REF_F0, to access VPD through function 0 to provide VPD access on other functions. This is for hardware devices that provide copies of the same VPD capability registers in multiple functions. Because the kernel expects that each function has its own registers, both the locking and the state tracking are affected by VPD accesses to different functions. On such devices for example, if a VPD write is performed on function 0, *any* later attempt to read VPD from any other function of that device will hang. This has to do with how the kernel tracks the expected value of the F bit per function. Concurrent accesses to different functions of the same device can not only hang but also corrupt both read and write VPD data. When hangs occur, typically the error message: vpd r/w failed. This is likely a firmware bug on this device. will be seen. Never set this bit on function 0 or there will be an infinite recursion. Signed-off-by: Mark Rustad <mark.d.rustad@intel.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Acked-by: Alexander Duyck <alexander.h.duyck@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions