diff options
| author | Bjorn Helgaas <bhelgaas@google.com> | 2023-03-07 15:38:16 -0600 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-03-09 17:32:34 +0100 |
| commit | 8efc52743ecb5c69d2e4faba965a3e14418c2494 (patch) | |
| tree | 9a935fbdca2cc838dfb5fb68c0d81a36f6e8760e /drivers/fpga/zynqmp-fpga.c | |
| parent | b085dbf6c955c34f735cac433f8551832138e154 (diff) | |
| download | linux-8efc52743ecb5c69d2e4faba965a3e14418c2494.tar.gz linux-8efc52743ecb5c69d2e4faba965a3e14418c2494.tar.bz2 linux-8efc52743ecb5c69d2e4faba965a3e14418c2494.zip | |
misc: alcor_pci: Use PCI core to manage ASPM instead of open-coding
"priv->ext_config_dev_aspm" was never set to a non-zero value. Therefore,
alcor_pci_aspm_ctrl(priv, 1) did nothing, and alcor_pci_aspm_ctrl(priv, 0)
always disabled ASPM in the device and the upstream bridge.
The driver disabled ASPM in alcor_pci_probe() and alcor_resume(), so it's
possible the device doesn't work well when ASPM is enabled.
Remove all the ASPM-related code and replace the alcor_pci_aspm_ctrl(0)
calls with pci_disable_link_state(pdev, PCIE_LINK_STATE_L0S |
PCIE_LINK_STATE_L1), which asks the PCI core to disable ASPM.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Reviewed-by: Oleksij Rempel <o.rempel@pengutronix.de>
Link: https://lore.kernel.org/r/20230307213816.886308-1-helgaas@kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/fpga/zynqmp-fpga.c')
0 files changed, 0 insertions, 0 deletions