X86 platform drivers
 help / color / mirror / Atom feed
From: "Rahul Chandra" <rahul@chandra.net>
To: "Antheas Kapenekakis" <lkml@antheas.dev>
Cc: platform-driver-x86@vger.kernel.org,
	ilpo.jarvinen@linux.intel.com, 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:54:53 -0400	[thread overview]
Message-ID: <1e1-68c90980-99-13ea166@216761407> (raw)
In-Reply-To: <CAGwozwFaB9YMKqc1tbmRvjjAZLZRZJKKEjYFDH38EbdeBRvWmA@mail.gmail.com>

On Tuesday, September 16, 2025 02:50 EDT, Antheas Kapenekakis <lkml@antheas.dev> wrote:

> On Tue, 16 Sept 2025 at 08:46, Rahul Chandra <rahul@chandra.net> wrote:
> >
> > Added some cc's
> >
> > *Note I have a UX8406CA (the 2025 Arrowlake model, I assume it is the same on the MA)
> 
> I must have mistakenly thought that the important code on both devices
> is 0x5F. Perhaps on the duo is 0x5D instead or it emits events on
> both. Can you verify which codes are used on the Duo?
> 
weird,
scankey -s reports
0xe0 0x73  0xe0 0xf3, the 0xe0 is for the extended scancode set but I'm confused on the other 2 codes. the WLAN quirk definitely worked before (I submitted the patch for it for the CA)


-- 
Rahul


  parent reply	other threads:[~2025-09-16  6:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16  6:45 [PATCH v2 1/2] platform/x86: asus-wmi: Remove extra keys from ignore_key_wlan quirk Rahul Chandra
2025-09-16  6:50 ` Antheas Kapenekakis
2025-09-16  6:50   ` Antheas Kapenekakis
2025-09-16  6:54   ` Rahul Chandra [this message]
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-68c90980-99-13ea166@216761407 \
    --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