On Sat, Mar 14, 2026 at 12:43:33PM +0100, Rafael J. Wysocki wrote:

From: "Rafael J. Wysocki" <redacted>

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 PTP VMware 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/ (local) [1]
Signed-off-by: Rafael J. Wysocki <redacted>

Reviewed-by: Simon Horman <horms@kernel.org>