From: Mario Limonciello <superm1@kernel.org>
To: Antheas Kapenekakis <lkml@antheas.dev>
Cc: mario.limonciello@amd.com, rafael@kernel.org,
Xino JS1 Ni <nijs1@lenovo.com>,
linux-acpi@vger.kernel.org,
"derekjohn.clark@gmail.com" <derekjohn.clark@gmail.com>
Subject: Re: [PATCH] ACPI: EC: Set ec_no_wakeup for Lenovo Go S
Date: Tue, 1 Apr 2025 07:29:51 -0500 [thread overview]
Message-ID: <1eb121e5-c0d3-49a8-9579-6ea5543ad4f9@kernel.org> (raw)
In-Reply-To: <CAGwozwEoCc_nRodt2=6R5K5UOzhW+5Gx1uLS3H3ON4ZS_12gBg@mail.gmail.com>
>> Here are tags for linking to your patch development to be picked up.
>>
>> Link:
>> https://github.com/bazzite-org/patchwork/commit/95b93b2852718ee1e808c72e6b1836da4a95fc63
>> Co-developed-by: Antheas Kapenekakis <lkml@antheas.dev>
>> Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
>
I don't believe that b4 will pick these up, so I will send out a v2 with
them and mark this patch as superceded in patchwork so that Rafael
doesn't have to pull everything out of this thread manually.
>
> And to avoid having this conversation again, there is another Legion
> Go S [3] patch you nacked and froze the testing for, so you could go
> on the manhunt for the real cause of this one. But it will probably be
> needed and you will find that as you get TDP controls going. So if you
> want me to prepare that in a timely manner, because that one actually
> needs rewriting to be posted, now is the time to say so.
Can you please propose what you have in mind on the mailing lists to
discuss? It's relatively expensive (in the unit of tech debt) to add
quirk infrastructure and so we need to make sure it is the right solution.
Derek is working on CPU coefficient tuning in a completely separate
driver. If there are issues with that, I would generally prefer the
fixes to be in that driver.
>
> Antheas
>
> [1] https://github.com/bazzite-org/kernel-bazzite/releases/tag/6.12.12-201
> [2] https://gitlab.com/evlaV/linux-integration/-/commit/6c5a3a96be9b061f07bf9a1bcc33156c932ddf67
> [3] https://gitlab.freedesktop.org/drm/amd/-/issues/3929#note_2764760
>
>>> Not that I am content with it, which you might have noticed with my
>>> absence in the amd/drm issue tracker.
>>>
>>> So, was it the touchscreen after all? Did you verify this by tweaking
>>> its firmware?
>>
>> Yes it's the touchscreen causing this issue. It was confirmed by a
>> hardware rework.
>>
>>>
>>> Antheas
>>>
>>> [1] https://github.com/bazzite-org/patchwork/commit/95b93b2852718ee1e808c72e6b1836da4a95fc63
>>>
>>>
>>>> Thanks,
>>>>
>>>>>>
>>>>>>> Cc: Xino JS1 Ni <nijs1@lenovo.com>
>>>>>>> Reported-by: Antheas Kapenekakis <lkml@antheas.dev>
>>>>>>> Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3929
>>>>>>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>>>>>>> ---
>>>>>>> drivers/acpi/ec.c | 28 ++++++++++++++++++++++++++++
>>>>>>> 1 file changed, 28 insertions(+)
>>>>>>>
>>>>>>> diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
>>>>>>> index 8db09d81918fb..3c5f34892734e 100644
>>>>>>> --- a/drivers/acpi/ec.c
>>>>>>> +++ b/drivers/acpi/ec.c
>>>>>>> @@ -2301,6 +2301,34 @@ static const struct dmi_system_id acpi_ec_no_wakeup[] = {
>>>>>>> DMI_MATCH(DMI_PRODUCT_FAMILY, "103C_5336AN HP ZHAN 66 Pro"),
>>>>>>> },
>>>>>>> },
>>>>>>> + /*
>>>>>>> + * Lenovo Legion Go S; touchscreen blocks HW sleep when woken up from EC
>>>>>>> + * https://gitlab.freedesktop.org/drm/amd/-/issues/3929
>>>>>>> + */
>>>>>>> + {
>>>>>>> + .matches = {
>>>>>>> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
>>>>>>> + DMI_MATCH(DMI_PRODUCT_NAME, "83L3"),
>>>>>>> + }
>>>>>>> + },
>>>>>>> + {
>>>>>>> + .matches = {
>>>>>>> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
>>>>>>> + DMI_MATCH(DMI_PRODUCT_NAME, "83N6"),
>>>>>>> + }
>>>>>>> + },
>>>>>>> + {
>>>>>>> + .matches = {
>>>>>>> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
>>>>>>> + DMI_MATCH(DMI_PRODUCT_NAME, "83Q2"),
>>>>>>> + }
>>>>>>> + },
>>>>>>> + {
>>>>>>> + .matches = {
>>>>>>> + DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
>>>>>>> + DMI_MATCH(DMI_PRODUCT_NAME, "83Q3"),
>>>>>>> + }
>>>>>>> + },
>>>>>>> { },
>>>>>>> };
>>>>>>>
>>>>>>> --
>>>>>>> 2.43.0
>>>>>>>
>>>>
>>
next prev parent reply other threads:[~2025-04-01 12:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 20:44 [PATCH] ACPI: EC: Set ec_no_wakeup for Lenovo Go S Mario Limonciello
2025-03-31 20:51 ` Antheas Kapenekakis
2025-03-31 20:53 ` Antheas Kapenekakis
2025-03-31 20:55 ` Mario Limonciello
2025-03-31 21:16 ` Antheas Kapenekakis
2025-04-01 2:40 ` Mario Limonciello
2025-04-01 9:01 ` Antheas Kapenekakis
2025-04-01 12:29 ` Mario Limonciello [this message]
2025-04-01 12:45 ` Antheas Kapenekakis
2025-04-01 14:09 ` Mario Limonciello
2025-04-01 15:03 ` Antheas Kapenekakis
2025-04-01 15:24 ` Mario Limonciello
2025-04-01 18:39 ` Antheas Kapenekakis
2025-04-01 20:54 ` Mario Limonciello
2025-04-01 22:06 ` Antheas Kapenekakis
2025-04-02 19:19 ` Mario Limonciello
2025-04-02 20:37 ` Antheas Kapenekakis
2025-04-03 19:56 ` Mario Limonciello
2025-04-01 14:16 ` Xino Ni
2025-04-01 14:46 ` Antheas Kapenekakis
2025-04-01 14:58 ` Xino Ni
2025-04-01 15:05 ` Antheas Kapenekakis
2025-04-01 12:47 ` Antheas Kapenekakis
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=1eb121e5-c0d3-49a8-9579-6ea5543ad4f9@kernel.org \
--to=superm1@kernel.org \
--cc=derekjohn.clark@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=mario.limonciello@amd.com \
--cc=nijs1@lenovo.com \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.