summaryrefslogtreecommitdiffstats
path: root/virt/kvm
diff options
context:
space:
mode:
authorBjorn Helgaas <bhelgaas@google.com>2018-06-25 16:49:06 -0500
committerBjorn Helgaas <helgaas@kernel.org>2018-06-26 15:38:28 -0500
commitb03799b0cb35dbc39e89602b1203863e2a6e06bf (patch)
treef10cea12b88a5092de432a85ee8564fb8efc2f8b /virt/kvm
parent6f6f42466d902c92f21b46a45e6af22d1d663607 (diff)
downloadlinux-b03799b0cb35dbc39e89602b1203863e2a6e06bf.tar.bz2
PCI: shpchp: Separate existence of SHPC and permission to use it
The shpchp driver registers for all PCI bridge devices. Its probe method should fail if either (1) the bridge doesn't have an SHPC or (2) the OS isn't allowed to use it (the platform firmware may be operating the SHPC itself). Separate these two tests into: - A new shpc_capable() that looks for the SHPC hardware and is applicable on all systems (ACPI and non-ACPI), and - A simplified acpi_get_hp_hw_control_from_firmware() that we call only when we already know an SHPC exists and there may be ACPI methods to either request permission to use it (_OSC) or transfer control to the OS (OSHP). acpi_get_hp_hw_control_from_firmware() is implemented when CONFIG_ACPI=y, but does nothing if the current platform doesn't support ACPI. Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions