From: "Rafael J. Wysocki" <rafael@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Hans de Goede <hansg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
platform-driver-x86@vger.kernel.org
Subject: [PATCH v1 2/2] platform/x86: intel/smartconnect: Convert ACPI driver to a platform one
Date: Sat, 28 Feb 2026 16:28:19 +0100 [thread overview]
Message-ID: <24282289.6Emhk5qWAg@rafael.j.wysocki> (raw)
In-Reply-To: <8692017.NyiUUSuA9g@rafael.j.wysocki>
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
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 Intel Smart Connect disabling 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>
---
drivers/platform/x86/intel/smartconnect.c | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/drivers/platform/x86/intel/smartconnect.c b/drivers/platform/x86/intel/smartconnect.c
index 31019a1a6d5e..4d866b6366d6 100644
--- a/drivers/platform/x86/intel/smartconnect.c
+++ b/drivers/platform/x86/intel/smartconnect.c
@@ -5,22 +5,24 @@
#include <linux/acpi.h>
#include <linux/module.h>
+#include <linux/platform_device.h>
MODULE_DESCRIPTION("Intel Smart Connect disabling driver");
MODULE_LICENSE("GPL");
-static int smartconnect_acpi_init(struct acpi_device *acpi)
+static int smartconnect_acpi_probe(struct platform_device *pdev)
{
+ acpi_handle handle = ACPI_HANDLE(&pdev->dev);
unsigned long long value;
acpi_status status;
- status = acpi_evaluate_integer(acpi->handle, "GAOS", NULL, &value);
+ status = acpi_evaluate_integer(handle, "GAOS", NULL, &value);
if (ACPI_FAILURE(status))
return -EINVAL;
if (value & 0x1) {
- dev_info(&acpi->dev, "Disabling Intel Smart Connect\n");
- status = acpi_execute_simple_method(acpi->handle, "SAOS", 0);
+ dev_info(&pdev->dev, "Disabling Intel Smart Connect\n");
+ status = acpi_execute_simple_method(handle, "SAOS", 0);
}
return 0;
@@ -32,13 +34,12 @@ static const struct acpi_device_id smartconnect_ids[] = {
};
MODULE_DEVICE_TABLE(acpi, smartconnect_ids);
-static struct acpi_driver smartconnect_driver = {
- .name = "intel_smart_connect",
- .class = "intel_smart_connect",
- .ids = smartconnect_ids,
- .ops = {
- .add = smartconnect_acpi_init,
+static struct platform_driver smartconnect_driver = {
+ .probe = smartconnect_acpi_probe,
+ .driver = {
+ .name = "intel_smart_connect",
+ .acpi_match_table = smartconnect_ids,
},
};
-module_acpi_driver(smartconnect_driver);
+module_platform_driver(smartconnect_driver);
--
2.51.0
next prev parent reply other threads:[~2026-02-28 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 15:26 [PATCH v1 0/2] platform/x86: intel: Bind to platform devices instead of ACPI ones Rafael J. Wysocki
2026-02-28 15:27 ` [PATCH v1 1/2] platform/x86: intel/rst: Convert ACPI driver to a platform one Rafael J. Wysocki
2026-02-28 15:28 ` Rafael J. Wysocki [this message]
2026-03-09 14:58 ` [PATCH v1 0/2] platform/x86: intel: Bind to platform devices instead of ACPI ones Ilpo Järvinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24282289.6Emhk5qWAg@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®