From: Hans de Goede <hdegoede@redhat.com>
To: "Thomas Weißschuh" <thomas@t-8ch.de>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "open list:X86 PLATFORM DRIVERS"
<platform-driver-x86@vger.kernel.org>,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
Goswami Sanket <Sanket.Goswami@amd.com>
Subject: Re: [PATCH 0/4] Add a workaround for Framework 13 spurious IRQ1
Date: Mon, 18 Dec 2023 13:11:01 +0100 [thread overview]
Message-ID: <53d6933e-e5e8-4db1-b2e3-b931dc8bf0bd@redhat.com> (raw)
In-Reply-To: <85397fdb-b093-4c03-8613-3815352f2b2c@t-8ch.de>
Hi All,
On 12/12/23 21:19, Thomas Weißschuh wrote:
> On 2023-12-11 22:50:02-0600, Mario Limonciello wrote:
>> The 13" Framework laptop EC emits a spurious keyboard interrupt on every
>> resume from hardware sleep. When a user closes the lid on an already
>> suspended system this causes the system to wake up.
>>
>> This series adjusts the previous Cezanne quirk (which has a much different
>> root cause) to be able to apply to other systems too. The Framework 13"
>> system is added to the list it will apply to.
>>
>> Mario Limonciello (4):
>> platform/x86/amd/pmc: Move platform defines to header
>> platform/x86/amd/pmc: Only run IRQ1 firmware version check on Cezanne
>> platform/x86/amd/pmc: Move keyboard wakeup disablement detection to
>> pmc-quirks
>> platform/x86/amd/pmc: Disable keyboard wakeup on AMD Framework 13
>>
>> drivers/platform/x86/amd/pmc/pmc-quirks.c | 20 ++++++++++++++
>> drivers/platform/x86/amd/pmc/pmc.c | 33 +++++++++--------------
>> drivers/platform/x86/amd/pmc/pmc.h | 12 +++++++++
>> 3 files changed, 45 insertions(+), 20 deletions(-)
>
> For the full series:
>
> Reviewed-by: Thomas Weißschuh <linux@weissschuh.net>
> Tested-by: Thomas Weißschuh <linux@weissschuh.net> # on AMD Framework 13
>
> The device now only wakes up when opening the lid.
Thomas, thank you for the review and testing.
The series looks good to me too:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Ilpo, do you plan on sending out one more fixes pull-req for 6.7
and if yes, can you add this series to that; or shall I merge
this into for-next so that it gets included in 6.8-rc1 ?
Regards,
Hans
next prev parent reply other threads:[~2023-12-18 12:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 4:50 [PATCH 0/4] Add a workaround for Framework 13 spurious IRQ1 Mario Limonciello
2023-12-12 4:50 ` [PATCH 1/4] platform/x86/amd/pmc: Move platform defines to header Mario Limonciello
2023-12-12 4:50 ` [PATCH 2/4] platform/x86/amd/pmc: Only run IRQ1 firmware version check on Cezanne Mario Limonciello
2023-12-18 12:59 ` Ilpo Järvinen
2023-12-18 13:01 ` Ilpo Järvinen
2023-12-12 4:50 ` [PATCH 3/4] platform/x86/amd/pmc: Move keyboard wakeup disablement detection to pmc-quirks Mario Limonciello
2023-12-12 4:50 ` [PATCH 4/4] platform/x86/amd/pmc: Disable keyboard wakeup on AMD Framework 13 Mario Limonciello
2023-12-12 20:19 ` [PATCH 0/4] Add a workaround for Framework 13 spurious IRQ1 Thomas Weißschuh
2023-12-18 12:11 ` Hans de Goede [this message]
2023-12-18 12:42 ` Ilpo Järvinen
2023-12-18 13:25 ` Hans de Goede
2023-12-18 13:10 ` 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=53d6933e-e5e8-4db1-b2e3-b931dc8bf0bd@redhat.com \
--to=hdegoede@redhat.com \
--cc=Sanket.Goswami@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=thomas@t-8ch.de \
/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