mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: "Daniel Gibson" <daniel@gibson.sh>,
	"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
	"Hans de Goede" <hansg@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] amd_pmc: Delay s2idle suspend for some devices
Date: Thu, 21 May 2026 14:43:39 -0500	[thread overview]
Message-ID: <d7193b2f-6690-4938-9fbc-401b2ba2e1c0@kernel.org> (raw)
In-Reply-To: <af087465-2487-46dd-bd19-ba6b0790b2f0@gibson.sh>

On 5/21/26 14:13, Daniel Gibson wrote:
> On 21.05.26 16:44, Mario Limonciello wrote:
>> On 5/12/26 15:26, Daniel Gibson wrote:
>>> On some AMD Zen3 and Zen3+-based Lenovo IdeaPad laptops the keyboard and
>>> the lid switch stop working after the first suspend, until rebooted.
>>>
>>> More specifically, they stop sending events when pressing a key or
>>> closing the lid - it's still possible to toggle the capslock- and
>>> numlock-LEDs with an external keyboard or read the lid state at
>>> /proc/acpi/button/lid/LID/state.
>>>
>>> See also https://bugzilla.kernel.org/show_bug.cgi?id=221383
>>>
>>>
>>>    Documentation/arch/x86/amd-debugging.rst  | 30 ++++++++++++
>>>    drivers/platform/x86/amd/pmc/pmc-quirks.c | 39 +++++++++++++++
>>>    drivers/platform/x86/amd/pmc/pmc.c        | 60 +++++++++++++++++++++--
>>>    drivers/platform/x86/amd/pmc/pmc.h        |  1 +
>>>    4 files changed, 127 insertions(+), 3 deletions(-)
>>>
>>
>> Can you see if this series helps your issue instead of quirks?
>>
>> https://lore.kernel.org/linux-acpi/5996185.DvuYhMxLoT@rafael.j.wysocki/
> 
> I tried and it did not help with the issue.
> 

OK thanks for trying, figured it was worth a shot.

> By the way, applying it was a PITA: I downloaded the mbox.gz from
> lore.kernel.org, but it contained the threads messages in reverse, so
> git am tried to apply them in reverse order, which of course didn't work
> very well.. eventually I used `git am -i` to apply one at a time.
> 
> Is that normal or a lore.kernel.org bug or did I do something wrong?
> 

Try using 'b4 shazam' or 'b4 am' next time.  You basically feed a lore 
URL as an argument and it does the rest.

  reply	other threads:[~2026-05-21 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 20:26 Daniel Gibson
2026-05-12 20:26 ` [PATCH v3 1/5] platform/x86/amd/pmc: Check for intermediate wakeup in function Daniel Gibson
2026-05-12 20:26 ` [PATCH v3 2/5] platform/x86/amd/pmc: Delay suspend for some Lenovo Laptops Daniel Gibson
2026-05-12 20:26 ` [PATCH v3 3/5] platform/x86/amd/pmc: Add delay_suspend module parameter Daniel Gibson
2026-05-12 20:26 ` [PATCH v3 4/5] Documentation/arch/x86/amd-debugging: Add example for reset register Daniel Gibson
2026-05-12 20:26 ` [PATCH v3 5/5] Documentation/arch/x86/amd-debugging: Add section about delay_suspend Daniel Gibson
2026-05-21 14:44 ` [PATCH v3 0/5] amd_pmc: Delay s2idle suspend for some devices Mario Limonciello
2026-05-21 19:13   ` Daniel Gibson
2026-05-21 19:43     ` Mario Limonciello [this message]
2026-05-21 20:32       ` Daniel Gibson

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=d7193b2f-6690-4938-9fbc-401b2ba2e1c0@kernel.org \
    --to=superm1@kernel.org \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=daniel@gibson.sh \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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®