summaryrefslogtreecommitdiffstats
path: root/include/acpi
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2023-01-10 18:58:05 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2023-01-17 12:52:11 +0100
commit28a35ac2f5f8719a6451932d7ab6b6b3d264a3aa (patch)
tree44e73ea004a8a0da9d39367a1426aae85e286f2a /include/acpi
parent5dc4c995db9eb45f6373a956eb1f69460e69e6d4 (diff)
downloadlinux-28a35ac2f5f8719a6451932d7ab6b6b3d264a3aa.tar.gz
linux-28a35ac2f5f8719a6451932d7ab6b6b3d264a3aa.tar.bz2
linux-28a35ac2f5f8719a6451932d7ab6b6b3d264a3aa.zip
ACPI: PNP: Introduce list of known non-PNP devices
In some cases, PNP device IDs from acpi_pnp_device_ids[] are returned by _CID for devices for which matching platform drivers are present in the kernel and should be bound to them. However, the IDs coming from _CID cause the PNP scan handler to attach to those devices which prevents platform device objects from being created for them. Address this by introducing a list of known non-PNP device IDs into acpi_pnp.c such that if a device ID is there in that list, it cannot be attached to by the PNP scan handler and add the platform runtime update and telemetry device IDs to that list to start with. Reported-by: Chen Yu <yu.c.chen@intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Tested-by: Zhang Yang <Yang5.zhang@intel.com>
Diffstat (limited to 'include/acpi')
0 files changed, 0 insertions, 0 deletions