From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v1 3/4] platform/x86: xo15-ebook: Register ACPI notify handler directly
Date: Mon, 11 May 2026 19:44:06 +0300 (EEST) [thread overview]
Message-ID: <de73ccd5-15c4-4836-d63e-4bb3138310d7@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0hAKEiy3JVP4w+wX-P3XxiVddVXt36zqqRdtPLnnmnYnw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3978 bytes --]
On Mon, 11 May 2026, Rafael J. Wysocki wrote:
> On Mon, May 11, 2026 at 6:17 PM Ilpo Järvinen
> <ilpo.jarvinen@linux.intel.com> wrote:
> >
> > On Mon, 11 May 2026, Rafael J. Wysocki wrote:
> >
> > > On Mon, May 11, 2026 at 3:59 PM Ilpo Järvinen
> > > <ilpo.jarvinen@linux.intel.com> wrote:
> > > >
> > > > On Fri, 8 May 2026, Rafael J. Wysocki wrote:
> > > >
> > > > > 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/x86/xo15-ebook.c | 19 ++++++++++++++-----
> > > > > 1 file changed, 14 insertions(+), 5 deletions(-)
> > > > >
> > > > > diff --git a/drivers/platform/x86/xo15-ebook.c b/drivers/platform/x86/xo15-ebook.c
> > > > > index 616f4bb3461a..8af1b9078db8 100644
> > > > > --- a/drivers/platform/x86/xo15-ebook.c
> > > > > +++ b/drivers/platform/x86/xo15-ebook.c
> > > > > @@ -57,16 +57,15 @@ static int ebook_send_state(struct acpi_device *device)
> > > > > return 0;
> > > > > }
> > > > >
> > > > > -static void ebook_switch_notify(struct acpi_device *device, u32 event)
> > > > > +static void ebook_switch_notify(acpi_handle handle, u32 event, void *data)
> > > > > {
> > > > > switch (event) {
> > > > > case ACPI_FIXED_HARDWARE_EVENT:
> > > > > case XO15_EBOOK_NOTIFY_STATUS:
> > > > > - ebook_send_state(device);
> > > > > + ebook_send_state(data);
> > > > > break;
> > > > > default:
> > > > > - acpi_handle_debug(device->handle,
> > > > > - "Unsupported event [0x%x]\n", event);
> > > > > + acpi_handle_debug(handle, "Unsupported event [0x%x]\n", event);
> > > > > break;
> > > > > }
> > > > > }
> > > > > @@ -123,6 +122,11 @@ static int ebook_switch_add(struct acpi_device *device)
> > > > > if (error)
> > > > > goto err_free_input;
> > > > >
> > > > > + error = acpi_dev_install_notify_handler(device, ACPI_DEVICE_NOTIFY,
> > > > > + ebook_switch_notify, device);
> > > > > + if (error)
> > > > > + goto err_unregister_input;
> > > > > +
> > > > > ebook_send_state(device);
> > > > >
> > > > > if (device->wakeup.flags.valid) {
> > > > > @@ -139,6 +143,10 @@ static int ebook_switch_add(struct acpi_device *device)
> > > > > err_free_button:
> > > > > kfree(button);
> > > > > return error;
> > > > > +
> > > > > +err_unregister_input:
> > > > > + input_unregister_device(input);
> > > > > + goto err_free_button;
> > > >
> > > > The end result would be much simpler if there would be patch 5 to convert
> > > > to devm_*().
> > >
> > > Well, I can add one.
> > >
> > > Do you want me to resend an update of the series for this?
> >
> > Ah, right. I took these now to review-ilpo-next.
> >
> > (I was initially thinking of making a little bit different suggestion
> > which would have required changes to these patches but then realized it
> > was better to just add the devm_*() conversion after these).
>
> So I guess I'll prepare a follow-up patch for the devm_ conversion.
>
> Note though that there's no devm_ counterpart of
> acpi_dev_install_notify_handler() ATM, so I may need to add one while
> at it.
While adding it will be able to remove acpi_dev_remove_notify_handler()
call from ebook_switch_remove(), there's no such call in rollbacks for
ebook_switch_probe() so it wouldn't be strictly required.
But it certainly wouldn't hurt to have one for other drivers.
--
i.
next prev parent reply other threads:[~2026-05-11 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 17:38 [PATCH v1 0/4] platform/x86: xo15-ebook: Bind to a platform device instead of an ACPI one Rafael J. Wysocki
2026-05-08 17:40 ` [PATCH v1 1/4] platform/x86: xo15-ebook: Fix wakeup source and GPE handling Rafael J. Wysocki
2026-05-08 17:41 ` [PATCH v1 2/4] platform/x86: xo15-ebook: Fix formatting of labels Rafael J. Wysocki
2026-05-08 17:43 ` [PATCH v1 3/4] platform/x86: xo15-ebook: Register ACPI notify handler directly Rafael J. Wysocki
2026-05-11 13:59 ` Ilpo Järvinen
2026-05-11 14:43 ` Rafael J. Wysocki
2026-05-11 16:13 ` Ilpo Järvinen
2026-05-11 16:37 ` Rafael J. Wysocki
2026-05-11 16:44 ` Ilpo Järvinen [this message]
2026-05-11 17:02 ` Rafael J. Wysocki
2026-05-08 17:44 ` [PATCH v1 4/4] platform/x86: xo15-ebook: Convert ACPI driver to a platform one 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=de73ccd5-15c4-4836-d63e-4bb3138310d7@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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