ACK: [SRU][P][PATCH 0/1] System could not hit hardware sleep state with specific panel with AMD KRK/STX under DC mode

Tim Whisonant tim.whisonant at canonical.com
Wed Apr 2 02:00:50 UTC 2025


On Tue, Apr 01, 2025 at 03:38:47PM +0800, En-Wei Wu wrote:
> BugLink: https://bugs.launchpad.net/bugs/2103480
> 
> [Impact]
> On Dell platform, the system with specific panel and AMD KRK/STX under 
> DC mode could not enter hardware sleep state. The root cause is that 
> the HPD interrupt triggers HW register write and thus prevents the HW 
> from sleeping, this causes the system not to be able to enter s2idle.
> 
> [Fix]
> Cherry-pick this patch from linux-next fixes the issue:
> 
> 50e0bae34fa6 drm/amd/display: Add and use new dm_prepare_suspend() callback
> 
> [Test Plan]
> 1. Install the Ubuntu image
> 
> 2. Use AMD amd_s2idle.py script to check if the system can enter the hardware sleep state. 
> The script is available at: 
> https://web.git.kernel.org/pub/scm/linux/kernel/git/superm1/amd-debug-tools.git/tree/amd_s2idle.py
> 
> [Where problems could occur]
> The backported patch "drm/amd/display: Add and use new dm_prepare_suspend() 
> callback" modifies the order in which the display and other IP blocks are 
> turned off during suspend. This change might introduce regressions, 
> particularly if any components rely on the original suspend sequence.
> 
> Mario Limonciello (1):
>   drm/amd/display: Add and use new dm_prepare_suspend() callback
> 
>  .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 25 ++++++++++++++++---
>  1 file changed, 21 insertions(+), 4 deletions(-)
> 
> -- 
> 2.43.0
> 

Acked-by: Tim Whisonant <tim.whisonant at canonical.com>



More information about the kernel-team mailing list