]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
platform/chrome: wilco_ec: event: Convert to a platform driver
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>
Thu, 5 Mar 2026 19:46:19 +0000 (20:46 +0100)
committerTzung-Bi Shih <tzungbi@kernel.org>
Fri, 6 Mar 2026 04:35:07 +0000 (04:35 +0000)
commit27d58498f690ab39140678df918155a597b3a17a
treee3de7e72fe0dcbd9f691d010475905c3f9f4fd5b
parent25a06b7a3224161cf4b27049bea93cac21136460
platform/chrome: wilco_ec: event: Convert to a platform driver

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 Wilco Embedded Controller event
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/
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Link: https://lore.kernel.org/r/9600287.CDJkKcVGEf@rafael.j.wysocki
Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org>
drivers/platform/chrome/wilco_ec/event.c