diff options
| author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2026-03-14 14:43:33 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-03-18 05:06:19 +0300 |
| commit | 6829f90906aaed1e4781742b96822031d5c2bd85 (patch) | |
| tree | dd2017621adafdde043799f59bdea723edf0eb88 /include/linux | |
| parent | eb9744e2c5d06e7007f47dd5853f7c50be189176 (diff) | |
| download | linux-6829f90906aaed1e4781742b96822031d5c2bd85.tar.xz | |
ptp: vmw: 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 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/ [1]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
Link: https://patch.msgid.link/12883468.O9o76ZdvQC@rafael.j.wysocki
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions
