]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
platform/x86: fujitsu: Convert laptop driver to a platform one
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>
Tue, 17 Mar 2026 19:44:38 +0000 (20:44 +0100)
committerIlpo Järvinen <ilpo.jarvinen@linux.intel.com>
Wed, 18 Mar 2026 12:06:06 +0000 (14:06 +0200)
commit6da22b031a3cf995d6488500a5edae07cae3df2d
tree4e5ae74e6f27f39f3b2e41691aa5dbbbfd59fc79
parentd5c9212ccfaa7bd453bf4b198eb19937f5deb58b
platform/x86: fujitsu: Convert laptop driver to a platform one

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 main part of the Fujitsu laptop driver
from an ACPI driver to a platform one.

After this change, the subordinate LED and input devices will be
registered under the platform device used for driver binding instead of
its ACPI companion.

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>
Acked-by: Jonathan Woithe <jwoithe@just42.net>
Link: https://patch.msgid.link/10818905.nUPlyArG6x@rafael.j.wysocki
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
drivers/platform/x86/fujitsu-laptop.c