mirror of https://github.com/torvalds/linux.git
d3c2872ae3
In all cases in which a struct acpi_driver is used for binding a driver to an ACPI device object, a corresponding platform device is created by the ACPI core and that device is regarded as a proper representation of underlying hardware. Accordingly, a struct platform_driver should be used by driver code to bind to that device. There are multiple reasons why drivers should not bind directly to ACPI device objects [1]. Overall, it is better to bind drivers to platform devices than to their ACPI companions, so convert the ChromeOS privacy-screen ACPI driver to a platform one. While this is not expected to alter functionality, it changes sysfs layout and so it will be visible to user space. Link: https://lore.kernel.org/all/2396510.ElGaqSPkdT@rafael.j.wysocki/ [1] Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Link: https://lore.kernel.org/r/1963835.tdWV9SEqCh@rafael.j.wysocki Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org> |
||
|---|---|---|
| .. | ||
| arm64 | ||
| chrome | ||
| cznic | ||
| goldfish | ||
| loongarch | ||
| mellanox | ||
| mips | ||
| olpc | ||
| raspberrypi | ||
| surface | ||
| wmi | ||
| x86 | ||
| Kconfig | ||
| Makefile | ||