[PATCH v2 0/6] platform/chrome: Bind drivers to platform devices instead of ACPI ones

["Rafael J. Wysocki" <rafael@kernel.org>]

Hi All,

This is a v2 of

https://lore.kernel.org/linux-acpi/2274474.Mh6RI2rZIc@rafael.j.wysocki/

addressing review comments on patches [2/6] and [4/6].

The series description below still applies.

This series is part of a larger effort to switch over all drivers using
the struct acpi_driver interface to the more common struct platform_driver
interface and eliminate the former.  The background is explained in
Documentation/driver-api/acpi/acpi-drivers.rst and in the changelog of
the patch that introduced the above document:

https://lore.kernel.org/all/2396510.ElGaqSPkdT@rafael.j.wysocki/

The bottom line is that the kernel would be better off without struct
acpi_driver and so it is better to get rid of it.

This series carries out driver conversions of Chrome platform drivers.

Patche [1/6] converts the ChromeOS privacy screen driver to using struct
platform_driver for device binding.

Patche [2/6] fixes a wakeup source object leak on remove in the
chromeos_tbmc driver.

Patch [3/6] updates the chromeos_tbmc driver to install an ACPI notify
handler by itself instead of using the .notify() callback from struct
acpi_driver, which is requisite for the driver conversion.

Patche [4/6] converts the chromeos_tbmc driver to using struct platform_driver
for device binding.

Patch [5/6] updates the wilco_ec-event driver to install an ACPI notify
handler by itself instead of using the .notify() callback from struct
acpi_driver, which is requisite for the driver conversion.

Patche [6/6] converts the wilco_ec-event driver to using struct platform_driver
for device binding.

Thanks!