From: "Rafael J. Wysocki" <rafael@kernel.org>
To: chrome-platform@lists.linux.dev
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Benson Leung <bleung@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Enric Balletbo i Serra <eballetbo@kernel.org>,
Ravi Chandra Sadineni <ravisadineni@chromium.org>
Subject: [PATCH v1 5/6] platform/chrome: wilco_ec: event: Register ACPI notify handler
Date: Wed, 04 Mar 2026 19:45:12 +0100 [thread overview]
Message-ID: <886338398.0ifERbkFSE@rafael.j.wysocki> (raw)
In-Reply-To: <2274474.Mh6RI2rZIc@rafael.j.wysocki>
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To facilitate subsequent conversion of the driver to a platform one,
make it install an ACPI notify handler directly instead of using
a .notify() callback in struct acpi_driver.
No intentional functional impact.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
drivers/platform/chrome/wilco_ec/event.c | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/drivers/platform/chrome/wilco_ec/event.c b/drivers/platform/chrome/wilco_ec/event.c
index 743cd4839bff..f4500dd05f93 100644
--- a/drivers/platform/chrome/wilco_ec/event.c
+++ b/drivers/platform/chrome/wilco_ec/event.c
@@ -253,14 +253,16 @@ static int enqueue_events(struct acpi_device *adev, const u8 *buf, u32 length)
/**
* event_device_notify() - Callback when EC generates an event over ACPI.
- * @adev: The device that the event is coming from.
+ * @handle: ACPI handle of the device that the event is coming from.
* @value: Value passed to Notify() in ACPI.
+ * @data: Notify handler data.
*
* This function will read the events from the device and enqueue them.
*/
-static void event_device_notify(struct acpi_device *adev, u32 value)
+static void event_device_notify(acpi_handle handle, u32 value, void *data)
{
struct acpi_buffer event_buffer = { ACPI_ALLOCATE_BUFFER, NULL };
+ struct acpi_device *adev = data;
union acpi_object *obj;
acpi_status status;
@@ -489,8 +491,16 @@ static int event_device_add(struct acpi_device *adev)
if (error)
goto free_dev_data;
+ /* Install an ACPI notify handler. */
+ error = acpi_dev_install_notify_handler(adev, ACPI_DEVICE_NOTIFY,
+ event_device_notify, adev);
+ if (error)
+ goto free_cdev;
+
return 0;
+free_cdev:
+ cdev_device_del(&dev_data->cdev, &dev_data->dev);
free_dev_data:
hangup_device(dev_data);
free_minor:
@@ -502,6 +512,8 @@ static void event_device_remove(struct acpi_device *adev)
{
struct event_device_data *dev_data = adev->driver_data;
+ acpi_dev_remove_notify_handler(adev, ACPI_DEVICE_NOTIFY,
+ event_device_notify);
cdev_device_del(&dev_data->cdev, &dev_data->dev);
ida_free(&event_ida, MINOR(dev_data->dev.devt));
hangup_device(dev_data);
@@ -519,7 +531,6 @@ static struct acpi_driver event_driver = {
.ids = event_acpi_ids,
.ops = {
.add = event_device_add,
- .notify = event_device_notify,
.remove = event_device_remove,
},
};
--
2.51.0
next prev parent reply other threads:[~2026-03-04 18:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 18:41 [PATCH v1 0/6] platform/chrome: Bind drivers to platform devices instead of ACPI ones Rafael J. Wysocki
2026-03-04 18:42 ` [PATCH v1 1/6] platform/chrome: Convert ChromeOS privacy-screen driver to platform Rafael J. Wysocki
2026-03-04 18:43 ` [PATCH v1 2/6] platform/chrome: chromeos_tbmc: Drop wakeup source on remove Rafael J. Wysocki
2026-03-05 15:29 ` Tzung-Bi Shih
2026-03-05 15:30 ` Rafael J. Wysocki
2026-03-04 18:43 ` [PATCH v1 3/6] platform/chrome: chromeos_tbmc: Register ACPI notify handler Rafael J. Wysocki
2026-03-04 18:44 ` [PATCH v1 4/6] platform/chrome: chromeos_tbmc: Convert to a platform driver Rafael J. Wysocki
2026-03-05 15:29 ` Tzung-Bi Shih
2026-03-05 15:34 ` Rafael J. Wysocki
2026-03-05 15:50 ` Tzung-Bi Shih
2026-03-05 15:52 ` Rafael J. Wysocki
2026-03-04 18:45 ` Rafael J. Wysocki [this message]
2026-03-04 18:45 ` [PATCH v1 6/6] platform/chrome: wilco_ec: event: " Rafael J. Wysocki
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=886338398.0ifERbkFSE@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®