linux-kernel - Re: [PATCH] acpi/ec: Add device to acpi_ec_no

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <421e737a-bb7c-4d80-bead-407e756bba68@tuxedocomputers.com>
Date: Fri, 9 May 2025 23:38:54 +0200
From: Werner Sembach <wse@...edocomputers.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] acpi/ec: Add device to acpi_ec_no_wakeup qurik


Am 09.05.25 um 22:23 schrieb Rafael J. Wysocki:
> On Fri, May 9, 2025 at 9:49 PM Werner Sembach <wse@...edocomputers.com> wrote:
>>
>> Am 09.05.25 um 21:21 schrieb Rafael J. Wysocki:
>>> On Thu, May 8, 2025 at 1:16 PM Werner Sembach <wse@...edocomputers.com> wrote:
>>>> Add the TUXEDO InfinityBook Pro AMD Gen9 to the acpi_ec_no_wakeup quirk
>>>> list to prevent spurious wakeups.
>>>>
>>>> Signed-off-by: Werner Sembach <wse@...edocomputers.com>
>>>> ---
>>>>    drivers/acpi/ec.c | 6 ++++++
>>>>    1 file changed, 6 insertions(+)
>>>>
>>>> diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
>>>> index 8db09d81918fb..de45a5b59effd 100644
>>>> --- a/drivers/acpi/ec.c
>>>> +++ b/drivers/acpi/ec.c
>>>> @@ -2301,6 +2301,12 @@ static const struct dmi_system_id acpi_ec_no_wakeup[] = {
>>>>                           DMI_MATCH(DMI_PRODUCT_FAMILY, "103C_5336AN HP ZHAN 66 Pro"),
>>>>                   },
>>>>           },
>>>> +       {
>>>> +               // TUXEDO InfinityBook Pro AMD Gen9
>>>> +               .matches = {
>>>> +                       DMI_MATCH(DMI_BOARD_NAME, "GXxHRXx"),
>>>> +               },
>>>> +       },
>>>>           { },
>>>>    };
>>>>
>>>> --
>>> Applied as 6.16 material, thanks!
>> Forgot to add cc stable but i guess i will just wait till it reaches mainline
>> and then send it manually?
> I can add a "stable" tag to it, but it won't apply to older kernels
> anyway because the table has grown recently.
>
> It's better to send manually when it gets merged I think.
ok