lkml.org 
[lkml]   [2022]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH v2 1/1] pinctrl: amd: Add dynamic debugging for active GPIOs
On Thu, Oct 13, 2022 at 3:47 PM Mario Limonciello
<mario.limonciello@amd.com> wrote:

> Some laptops have been reported to wake up from s2idle when plugging
> in the AC adapter or by closing the lid. This is a surprising
> behavior that is further clarified by commit cb3e7d624c3ff ("PM:
> wakeup: Add extra debugging statement for multiple active IRQs").
>
> With that commit in place the following interaction can be seen
> when the lid is closed:
>
> [ 28.946038] PM: suspend-to-idle
> [ 28.946083] ACPI: EC: ACPI EC GPE status set
> [ 28.946101] ACPI: PM: Rearming ACPI SCI for wakeup
> [ 28.950152] Timekeeping suspended for 3.320 seconds
> [ 28.950152] PM: Triggering wakeup from IRQ 9
> [ 28.950152] ACPI: EC: ACPI EC GPE status set
> [ 28.950152] ACPI: EC: ACPI EC GPE dispatched
> [ 28.995057] ACPI: EC: ACPI EC work flushed
> [ 28.995075] ACPI: PM: Rearming ACPI SCI for wakeup
> [ 28.995131] PM: Triggering wakeup from IRQ 9
> [ 28.995271] ACPI: EC: ACPI EC GPE status set
> [ 28.995291] ACPI: EC: ACPI EC GPE dispatched
> [ 29.098556] ACPI: EC: ACPI EC work flushed
> [ 29.207020] ACPI: EC: ACPI EC work flushed
> [ 29.207037] ACPI: PM: Rearming ACPI SCI for wakeup
> [ 29.211095] Timekeeping suspended for 0.739 seconds
> [ 29.211095] PM: Triggering wakeup from IRQ 9
> [ 29.211079] PM: Triggering wakeup from IRQ 7
> [ 29.211095] ACPI: PM: ACPI non-EC GPE wakeup
> [ 29.211095] PM: resume from suspend-to-idle
>
> * IRQ9 on this laptop is used for the ACPI SCI.
> * IRQ7 on this laptop is used for the GPIO controller.
>
> What has occurred is when the lid was closed the EC woke up the
> SoC from it's deepest sleep state and the kernel's s2idle loop
> processed all EC events. When it was finished processing EC events,
> it checked for any other reasons to wake (break the s2idle loop).
>
> The IRQ for the GPIO controller was active so the loop broke, and
> then this IRQ was processed. This is not a kernel bug but it is
> certainly a surprising behavior, and to better debug it we should
> have a dynamic debugging message that we can enact to catch it.
>
> Acked-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
> Acked-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> v1->v2:
> * Use PIN_IRQ_PENDING instead
> * Add Acks

Patch applied!

Yours,
Linus Walleij

\
 
 \ /
  Last update: 2022-10-17 12:19    [W:0.054 / U:0.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site