From: Armin Wolf <W_Armin@gmx.de>
To: Hans de Goede <hdegoede@redhat.com>,
pespin@espeweb.net, corentin.chary@gmail.com, luke@ljones.dev
Cc: ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] platform/x86: asus-nb-wmi: Ignore unknown event 0xCF
Date: Fri, 29 Nov 2024 20:30:27 +0100 [thread overview]
Message-ID: <d6ab1593-45a0-4688-b281-4f7acfa1d515@gmx.de> (raw)
In-Reply-To: <d48bee72-7cd6-41cd-8d1d-282e8e68269d@redhat.com>
Am 25.11.24 um 10:39 schrieb Hans de Goede:
> Hi,
>
> On 23-Nov-24 11:47 PM, Armin Wolf wrote:
>> On the Asus X541UAK an unknown event 0xCF is emited when the charger
>> is plugged in. This is caused by the following AML code:
>>
>> If (ACPS ())
>> {
>> ACPF = One
>> Local0 = 0x58
>> If (ATKP)
>> {
>> ^^^^ATKD.IANE (0xCF)
>> }
>> }
>> Else
>> {
>> ACPF = Zero
>> Local0 = 0x57
>> }
>>
>> Notify (AC0, 0x80) // Status Change
>> If (ATKP)
>> {
>> ^^^^ATKD.IANE (Local0)
>> }
>>
>> Sleep (0x64)
>> PNOT ()
>> Sleep (0x0A)
>> NBAT (0x80)
>>
>> Ignore the 0xCF event to silence the unknown event warning.
>>
>> Reported-by: Pau Espin Pedrol <pespin@espeweb.net>
>> Closes: https://lore.kernel.org/platform-driver-x86/54d4860b-ec9c-4992-acf6-db3f90388293@espeweb.net
>> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
> Thanks, patch looks good to me:
>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
>
> Regards,
>
> Hans
Any updates on this?
Thanks,
Armin Wolf
>> ---
>> drivers/platform/x86/asus-nb-wmi.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/platform/x86/asus-nb-wmi.c b/drivers/platform/x86/asus-nb-wmi.c
>> index ef04d396f61c..a5933980ade3 100644
>> --- a/drivers/platform/x86/asus-nb-wmi.c
>> +++ b/drivers/platform/x86/asus-nb-wmi.c
>> @@ -623,6 +623,7 @@ static const struct key_entry asus_nb_wmi_keymap[] = {
>> { KE_KEY, 0xC4, { KEY_KBDILLUMUP } },
>> { KE_KEY, 0xC5, { KEY_KBDILLUMDOWN } },
>> { KE_IGNORE, 0xC6, }, /* Ambient Light Sensor notification */
>> + { KE_IGNORE, 0xCF, }, /* AC mode */
>> { KE_KEY, 0xFA, { KEY_PROG2 } }, /* Lid flip action */
>> { KE_KEY, 0xBD, { KEY_PROG2 } }, /* Lid flip action on ROG xflow laptops */
>> { KE_END, 0},
>> --
>> 2.39.5
>>
next prev parent reply other threads:[~2024-11-29 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 22:47 Armin Wolf
2024-11-25 9:39 ` Hans de Goede
2024-11-29 19:30 ` Armin Wolf [this message]
2024-12-02 17:03 ` Ilpo Järvinen
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=d6ab1593-45a0-4688-b281-4f7acfa1d515@gmx.de \
--to=w_armin@gmx.de \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=pespin@espeweb.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
all inboxes | Powered by JetHome®