From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: chrome-platform@lists.linux.dev,
LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <eballetbo@kernel.org>,
Ravi Chandra Sadineni <ravisadineni@chromium.org>
Subject: [PATCH v2 1/6] platform/chrome: Convert ChromeOS privacy-screen driver to platform
Date: Thu, 05 Mar 2026 20:37:54 +0100 [thread overview]
Message-ID: <1963835.tdWV9SEqCh@rafael.j.wysocki> (raw)
In-Reply-To: <6259948.lOV4Wx5bFT@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 ChromeOS privacy-screen 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>
---
v1 -> v2: No changes
---
.../platform/chrome/chromeos_privacy_screen.c | 41 ++++++++-----------
1 file changed, 18 insertions(+), 23 deletions(-)
diff --git a/drivers/platform/chrome/chromeos_privacy_screen.c b/drivers/platform/chrome/chromeos_privacy_screen.c
index bb74ddf9af4a..abc5d189a389 100644
--- a/drivers/platform/chrome/chromeos_privacy_screen.c
+++ b/drivers/platform/chrome/chromeos_privacy_screen.c
@@ -12,6 +12,7 @@
*/
#include <linux/acpi.h>
+#include <linux/platform_device.h>
#include <drm/drm_privacy_screen_driver.h>
/*
@@ -32,11 +33,10 @@ chromeos_privacy_screen_get_hw_state(struct drm_privacy_screen
*drm_privacy_screen)
{
union acpi_object *obj;
- acpi_handle handle;
struct device *privacy_screen =
drm_privacy_screen_get_drvdata(drm_privacy_screen);
+ acpi_handle handle = ACPI_HANDLE(privacy_screen);
- handle = acpi_device_handle(to_acpi_device(privacy_screen));
obj = acpi_evaluate_dsm(handle, &chromeos_privacy_screen_dsm_guid,
PRIV_SCRN_DSM_REVID,
PRIV_SCRN_DSM_FN_GET_STATUS, NULL);
@@ -65,11 +65,9 @@ chromeos_privacy_screen_set_sw_state(struct drm_privacy_screen
enum drm_privacy_screen_status state)
{
union acpi_object *obj = NULL;
- acpi_handle handle;
struct device *privacy_screen =
drm_privacy_screen_get_drvdata(drm_privacy_screen);
-
- handle = acpi_device_handle(to_acpi_device(privacy_screen));
+ acpi_handle handle = ACPI_HANDLE(privacy_screen);
if (state == PRIVACY_SCREEN_DISABLED) {
obj = acpi_evaluate_dsm(handle,
@@ -104,30 +102,28 @@ static const struct drm_privacy_screen_ops chromeos_privacy_screen_ops = {
.set_sw_state = chromeos_privacy_screen_set_sw_state,
};
-static int chromeos_privacy_screen_add(struct acpi_device *adev)
+static int chromeos_privacy_screen_probe(struct platform_device *pdev)
{
struct drm_privacy_screen *drm_privacy_screen =
- drm_privacy_screen_register(&adev->dev,
+ drm_privacy_screen_register(&pdev->dev,
&chromeos_privacy_screen_ops,
- &adev->dev);
+ &pdev->dev);
if (IS_ERR(drm_privacy_screen)) {
- dev_err(&adev->dev, "Error registering privacy-screen\n");
+ dev_err(&pdev->dev, "Error registering privacy-screen\n");
return PTR_ERR(drm_privacy_screen);
}
- adev->driver_data = drm_privacy_screen;
- dev_info(&adev->dev, "registered privacy-screen '%s'\n",
+ platform_set_drvdata(pdev, drm_privacy_screen);
+ dev_info(&pdev->dev, "registered privacy-screen '%s'\n",
dev_name(&drm_privacy_screen->dev));
return 0;
}
-static void chromeos_privacy_screen_remove(struct acpi_device *adev)
+static void chromeos_privacy_screen_remove(struct platform_device *pdev)
{
- struct drm_privacy_screen *drm_privacy_screen = acpi_driver_data(adev);
-
- drm_privacy_screen_unregister(drm_privacy_screen);
+ drm_privacy_screen_unregister(platform_get_drvdata(pdev));
}
static const struct acpi_device_id chromeos_privacy_screen_device_ids[] = {
@@ -136,17 +132,16 @@ static const struct acpi_device_id chromeos_privacy_screen_device_ids[] = {
};
MODULE_DEVICE_TABLE(acpi, chromeos_privacy_screen_device_ids);
-static struct acpi_driver chromeos_privacy_screen_driver = {
- .name = "chromeos_privacy_screen_driver",
- .class = "ChromeOS",
- .ids = chromeos_privacy_screen_device_ids,
- .ops = {
- .add = chromeos_privacy_screen_add,
- .remove = chromeos_privacy_screen_remove,
+static struct platform_driver chromeos_privacy_screen_driver = {
+ .probe = chromeos_privacy_screen_probe,
+ .remove = chromeos_privacy_screen_remove,
+ .driver = {
+ .name = "chromeos_privacy_screen_driver",
+ .acpi_match_table = chromeos_privacy_screen_device_ids,
},
};
-module_acpi_driver(chromeos_privacy_screen_driver);
+module_platform_driver(chromeos_privacy_screen_driver);
MODULE_LICENSE("GPL v2");
MODULE_DESCRIPTION("ChromeOS ACPI Privacy Screen driver");
MODULE_AUTHOR("Rajat Jain <rajatja@google.com>");
--
2.51.0
next prev parent reply other threads:[~2026-03-05 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 19:34 [PATCH v2 0/6] platform/chrome: Bind drivers to platform devices instead of ACPI ones Rafael J. Wysocki
2026-03-05 19:37 ` Rafael J. Wysocki [this message]
2026-03-05 19:39 ` [PATCH v2 3/6] platform/chrome: chromeos_tbmc: Register ACPI notify handler Rafael J. Wysocki
2026-03-05 19:42 ` [PATCH v2 4/6] platform/chrome: chromeos_tbmc: Convert to a platform driver Rafael J. Wysocki
2026-03-05 19:43 ` [PATCH v2 5/6] platform/chrome: wilco_ec: event: Register ACPI notify handler Rafael J. Wysocki
2026-03-05 19:46 ` [PATCH v2 6/6] platform/chrome: wilco_ec: event: Convert to a platform driver Rafael J. Wysocki
2026-03-05 19:47 ` [PATCH v2 2/6] platform/chrome: chromeos_tbmc: Drop wakeup source on remove Rafael J. Wysocki
2026-03-06 4:46 ` [PATCH v2 0/6] platform/chrome: Bind drivers to platform devices instead of ACPI ones Tzung-Bi Shih
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=1963835.tdWV9SEqCh@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=eballetbo@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ravisadineni@chromium.org \
--cc=tzungbi@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®