| 2021-12-07 19:03:33 |
Alex Hung |
bug |
|
|
added bug |
| 2021-12-07 19:03:38 |
Alex Hung |
linux (Ubuntu): assignee |
|
Alex Hung (alexhung) |
|
| 2021-12-07 19:03:47 |
Alex Hung |
linux (Ubuntu): status |
New |
Fix Committed |
|
| 2021-12-07 19:03:50 |
Alex Hung |
linux (Ubuntu): status |
Fix Committed |
In Progress |
|
| 2021-12-07 19:11:38 |
Alex Hung |
description |
[Impact]
On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller.
In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance.
[Fix]
To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments.
The patches were cherry-picked from 5.16rc3.
[Test]
This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button
[Where problems could occur]
Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. |
[Impact]
On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller.
In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance.
[Fix]
To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments.
The patches were cherry-picked from 5.16rc3.
[Test]
This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button
[Where problems could occur]
Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. |
|
| 2021-12-07 19:12:19 |
Alex Hung |
description |
[Impact]
On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller.
In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance.
[Fix]
To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments.
The patches were cherry-picked from 5.16rc3.
[Test]
This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button
[Where problems could occur]
Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. |
[Impact]
On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller.
In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance.
[Fix]
To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments.
The patches were cherry-picked from 5.16rc3.
[Test]
This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses.
[Where problems could occur]
Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. |
|
| 2021-12-08 00:49:02 |
Alex Hung |
bug |
|
|
added subscriber Canonical Hardware Enablement |
| 2021-12-08 00:49:07 |
Alex Hung |
tags |
|
amd oem-priority originate-from-1950332 |
|
| 2021-12-10 20:00:23 |
Alex Hung |
nominated for series |
|
Ubuntu Focal |
|
| 2021-12-10 20:00:23 |
Alex Hung |
bug task added |
|
linux (Ubuntu Focal) |
|
| 2021-12-10 20:01:40 |
Alex Hung |
linux (Ubuntu Focal): status |
New |
Invalid |
|
| 2021-12-10 20:05:05 |
Alex Hung |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2021-12-10 20:05:08 |
Alex Hung |
hwe-next: importance |
Undecided |
Medium |
|
| 2021-12-10 20:05:47 |
Alex Hung |
affects |
linux (Ubuntu Focal) |
linux-oem-5.14 (Ubuntu Focal) |
|
| 2021-12-10 20:06:04 |
Alex Hung |
linux-oem-5.14 (Ubuntu Focal): status |
Invalid |
In Progress |
|
| 2021-12-14 00:41:24 |
Ubuntu Kernel Bot |
tags |
amd oem-priority originate-from-1950332 |
amd oem-priority originate-from-1950332 verification-needed-focal |
|
| 2021-12-14 02:25:11 |
Alex Hung |
tags |
amd oem-priority originate-from-1950332 verification-needed-focal |
amd oem-priority originate-from-1950332 verification-done-focal |
|
| 2021-12-14 13:05:48 |
Kai-Chuan Hsieh |
attachment added |
|
suspend-success.log https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1953540/+attachment/5547548/+files/suspend-success.log |
|
| 2021-12-16 14:50:03 |
Launchpad Janitor |
linux-oem-5.14 (Ubuntu Focal): status |
In Progress |
Fix Released |
|
| 2021-12-16 15:49:16 |
Alex Hung |
linux-oem-5.14 (Ubuntu): status |
In Progress |
Fix Released |
|
| 2022-09-02 12:06:14 |
Timo Aaltonen |
hwe-next: status |
New |
Fix Released |
|
