From: "Rahul Chandra" <rahul@chandra.net>
To: platform-driver-x86@vger.kernel.org
Cc: ilpo.jarvinen@linux.intel.com, lkml@antheas.dev,
mathieu@fenniak.net, corentin.chary@gmail.com, luke@ljones.dev
Subject: Re: [PATCH v2 1/2] platform/x86: asus-wmi: Remove extra keys from ignore_key_wlan quirk
Date: Tue, 16 Sep 2025 02:45:34 -0400 [thread overview]
Message-ID: <1e1-68c90780-93-13ea166@216760021> (raw)
Added some cc's
*Note I have a UX8406CA (the 2025 Arrowlake model, I assume it is the same on the MA)
--
Rahul
On Tuesday, September 16, 2025 02:36 EDT, "Rahul Chandra" <rahul@chandra.net> wrote:
> On Monday, August 25, 2025 07:30 EDT, Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> wrote:
>
> > On Fri, 08 Aug 2025 17:47:09 +0200, Antheas Kapenekakis wrote:
> >
> > > Currently, the ignore_key_wlan quirk applies to keycodes 0x5D, 0x5E, and
> > > 0x5F. However, the relevant code for the Asus Zenbook Duo is only 0x5F.
> > > Since this code is emitted by other Asus devices, such as from the Z13
> > > for its ROG button, remove the extra codes before expanding the quirk.
> > >
> > > For the Duo devices, which are the only ones that use this quirk, there
> > > should be no effect.
> > >
> > > [...]
> >
> >
> > Thank you for your contribution, it has been applied to my local
> > review-ilpo-fixes branch. Note it will show up in the public
> > platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
> > local branch there, which might take a while.
> >
> > The list of commits applied:
> > [1/2] platform/x86: asus-wmi: Remove extra keys from ignore_key_wlan quirk
> > commit: cf3940ac737d05c85395f343fe33a3cfcadb47db
> > [2/2] platform/x86: asus-wmi: Fix ROG button mapping, tablet mode on ASUS ROG Z13
>
>
> Hi, with these commits on the branch the "Airplane Mode on detach/attach" bug comes back (The bug the quirk was intended to fix) . I think the Duo emits 0x5D (toggle, because it deactivates and activates on attach/detach) however I have not confirmed this. This is a regression from the previous patch and I propose that we either revert the commit or fix the keycode. I am not submitting a patch because I don't know if 5D is used for a different purpose on the ROG devices, can someone confirm?
>
> --
> Rahul
>
>
next reply other threads:[~2025-09-16 6:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 6:45 Rahul Chandra [this message]
2025-09-16 6:50 ` [PATCH v2 1/2] platform/x86: asus-wmi: Remove extra keys from ignore_key_wlan quirk Antheas Kapenekakis
2025-09-16 6:50 ` Antheas Kapenekakis
2025-09-16 6:54 ` Rahul Chandra
2025-09-16 6:56 ` Rahul Chandra
2025-09-16 6:57 ` Antheas Kapenekakis
2025-09-16 7:06 ` Rahul Chandra
2025-09-16 7:08 ` Rahul Chandra
2025-09-16 7:11 ` Antheas Kapenekakis
2025-09-16 7:15 ` Rahul Chandra
2025-09-16 7:17 ` Antheas Kapenekakis
2025-09-16 7:23 ` Rahul Chandra
2025-09-16 7:26 ` Antheas Kapenekakis
2025-09-16 7:37 ` Rahul Chandra
2025-09-16 7:40 ` Antheas Kapenekakis
-- strict thread matches above, loose matches on Subject: below --
2025-08-08 15:47 Antheas Kapenekakis
2025-08-08 15:49 ` Antheas Kapenekakis
2025-08-25 11:30 ` Ilpo Järvinen
2025-09-16 6:36 ` Rahul Chandra
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=1e1-68c90780-93-13ea166@216760021 \
--to=rahul@chandra.net \
--cc=corentin.chary@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lkml@antheas.dev \
--cc=luke@ljones.dev \
--cc=mathieu@fenniak.net \
--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