diff options
| author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2026-03-14 12:57:23 +0100 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2026-04-07 21:06:59 +0200 |
| commit | 112b2f978afee7df725cda74a94802f919c61564 (patch) | |
| tree | 3cc03994b586ebf6bb714bb2a6051c9f8514e9af /include/asm-mips/sgi/git@git.tavy.me:linux.git | |
| parent | a56a658f2492ae70ca5e9db980b0af3aceb7b5b8 (diff) | |
ACPI: PAD: xen: 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 Xen ACPI processor aggregator device
(PAD) 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>
Link: https://patch.msgid.link/8683270.T7Z3S40VBb@rafael.j.wysocki
Diffstat (limited to 'include/asm-mips/sgi/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions
