[PATCH v1 0/7] platform/x86: toshiba: Bind to platform devices instead of ACPI ones

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

Hi All,

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 conversion of the platform x86 Toshiba drivers.

Patch [1/7] relocates a function in the toshiba_acpi driver to avoid having
to add a forward declaration of it subsequently.

Patch [2/7] updates the toshiba_acpi 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.

Patch [3/7] converts the toshiba_acpi driver to using struct platform_driver
for device binding.

Patch [4/7] updates the toshiba_bluetooth 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.

Patch [5/7] converts the toshiba_bluetooth driver to using struct
platform_driver for device binding.

Patch [6/7] updates the toshiba_haps 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.

Patch [7/7] converts the toshiba_haps driver to using struct platform_driver
for device binding.

Thanks!