From: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
To: Armin Wolf <W_Armin@gmx.de>, <corentin.chary@gmail.com>,
<luke@ljones.dev>, <denis.benato@linux.dev>
Cc: <hansg@kernel.org>, <ilpo.jarvinen@linux.intel.com>,
<platform-driver-x86@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <royclark086@gmail.com>
Subject: Re: [PATCH] platform/x86: asus-laptop: Fix ACPI event handling
Date: Mon, 31 Aug 2026 14:10:41 +0200 [thread overview]
Message-ID: <0ebc889d-766f-4bf0-b590-51be61cc9a8d@intel.com> (raw)
In-Reply-To: <20260830235058.324140-1-W_Armin@gmx.de>
On 8/31/2026 1:50 AM, Armin Wolf wrote:
> The event codes inside asus_keymap[] span a wide range from 0x02
> till 0xC5, but using ACPI_DEVICE_NOTIFY prevents us from receiving
> event codes below 0x80.
>
> Fix this by using ACPI_ALL_NOTIFY instead.
>
> Fixes: 378500dc1313 ("platform/x86: asus-laptop: Register ACPI notify handler directly")
> Reported-by: Mo Jun <royclark086@gmail.com>
> Closes: https://bugs.debian.org/1146124
> Tested-by: Mo Jun <royclark086@gmail.com>
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
Thanks for taking care of this!
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/platform/x86/asus-laptop.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/asus-laptop.c b/drivers/platform/x86/asus-laptop.c
> index 449addd1ac7a..79a575d0f5b4 100644
> --- a/drivers/platform/x86/asus-laptop.c
> +++ b/drivers/platform/x86/asus-laptop.c
> @@ -1882,7 +1882,7 @@ static int asus_acpi_probe(struct platform_device *pdev)
> if (result && result != -ENODEV)
> goto fail_pega_rfkill;
>
> - result = acpi_dev_install_notify_handler(device, ACPI_DEVICE_NOTIFY,
> + result = acpi_dev_install_notify_handler(device, ACPI_ALL_NOTIFY,
> asus_acpi_notify, asus);
> if (result)
> goto fail_pega_rfkill;
> @@ -1912,7 +1912,7 @@ static void asus_acpi_remove(struct platform_device *pdev)
> {
> struct asus_laptop *asus = platform_get_drvdata(pdev);
>
> - acpi_dev_remove_notify_handler(asus->device, ACPI_DEVICE_NOTIFY,
> + acpi_dev_remove_notify_handler(asus->device, ACPI_ALL_NOTIFY,
> asus_acpi_notify);
> asus_backlight_exit(asus);
> asus_rfkill_exit(asus);
next prev parent reply other threads:[~2026-08-31 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 23:50 Armin Wolf
2026-08-31 12:10 ` Wysocki, Rafael J [this message]
2026-08-31 16:45 ` Ilpo Järvinen
2026-08-31 19:22 ` Armin Wolf
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=0ebc889d-766f-4bf0-b590-51be61cc9a8d@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=W_Armin@gmx.de \
--cc=corentin.chary@gmail.com \
--cc=denis.benato@linux.dev \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=royclark086@gmail.com \
/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®