diff options
author | Kai-Heng Feng <kai.heng.feng@canonical.com> | 2022-05-17 07:37:38 +0300 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2022-07-05 23:43:30 +0300 |
commit | 6cd514e58f12b211d638dbf6f791fa18d854f09c (patch) | |
tree | 4d0534177c4249a9d20a3b997723c7a54324d33c /drivers/pci/pci-bridge-emul.c | |
parent | 5e69a33c5cec019dd8ca46e31749c6dc78f7cbf3 (diff) | |
download | linux-6cd514e58f12b211d638dbf6f791fa18d854f09c.tar.xz |
PCI: Clear PCI_STATUS when setting up device
We are seeing Master Abort bit is set on Intel I350 ethernet device and its
root port right after boot, probably happened during BIOS phase:
00:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) (prog-if 00 [Normal decode])
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
6e:00.0 Ethernet controller [0200]: Intel Corporation I350 Gigabit Network Connection [8086:1521] (rev 01)
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
The Master Abort bit is cleared after S3.
Since there's no functional impact found, clear the PCI_STATUS to treat it
anew at setting up.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215989
Link: https://lore.kernel.org/r/20220517043738.2308499-1-kai.heng.feng@canonical.com
Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'drivers/pci/pci-bridge-emul.c')
0 files changed, 0 insertions, 0 deletions