diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2015-04-24 02:18:01 +0200 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2015-04-24 02:18:01 +0200 |
commit | 7d284352f9cbc032f2294024b1a6b5c06765c246 (patch) | |
tree | e972852cb7a632f230e05bba3eb1eabfa399c431 /MAINTAINERS | |
parent | 4c533c801d1c9b5c38458a0e7516e0cf50643782 (diff) | |
download | op-kernel-dev-7d284352f9cbc032f2294024b1a6b5c06765c246.zip op-kernel-dev-7d284352f9cbc032f2294024b1a6b5c06765c246.tar.gz |
ACPI / scan: Add a scan handler for PRP0001
If the special PRP0001 device ID is present in the given device's list
of ACPI/PNP IDs and the device has a valid "compatible" property in
the _DSD, it should be enumerated using the default mechanism,
unless some scan handlers match the IDs preceding PRP0001 in the
device's list of ACPI/PNP IDs. In addition to that, no scan handlers
matching the IDs following PRP0001 in that list should be attached
to the device.
To make that happen, define a scan handler that will match PRP0001
and trigger the default enumeration for the matching devices if the
"compatible" property is present for them.
Since that requires the check for platform_id and device->handler
to be removed from acpi_default_enumeration(), move the fallback
invocation of acpi_default_enumeration() to acpi_bus_attach()
(after it's checked if there's a matching ACPI driver for the
device), which is a better place to call it, and do the platform_id
check in there too (device->handler is guaranteed to be unset at
the point where the function is looking for a matching ACPI driver).
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Darren Hart <dvhart@linux.intel.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions