dGPUs connected to Intel systems configured for suspend to idle
will not have the power rails cut at suspend and resetting the GPU
may lead to problematic behaviors.
Fixes: e25443d2765f4 ("drm/amdgpu: add a dev_pm_ops prepare callback (v2)")
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1879
Reviewed-by: Alex Deucher <email address hidden>
Signed-off-by: Mario Limonciello <email address hidden>
Signed-off-by: Alex Deucher <email address hidden>
(cherry picked from commit e55a3aea418269266d84f426b3bd70794d3389c8)
Signed-off-by: You-Sheng Yang <email address hidden>
5c2046d...
by
Mario Limonciello <email address hidden>
drm/amd: Only run s3 or s0ix if system is configured properly
This will cause misconfigured systems to not run the GPU suspend
routines.
* In APUs that are properly configured system will go into s2idle.
* In APUs that are intended to be S3 but user selects
s2idle the GPU will stay fully powered for the suspend.
* In APUs that are intended to be s2idle and system misconfigured
the GPU will stay fully powered for the suspend.
* In systems that are intended to be s2idle, but AMD dGPU is also
present, the dGPU will go through S3
Signed-off-by: Mario Limonciello <email address hidden>
Reviewed-by: Alex Deucher <email address hidden>
Signed-off-by: Alex Deucher <email address hidden>
(cherry picked from commit 04ef860469fda6a646dc841190d05b31fae68e8c)
Signed-off-by: You-Sheng Yang <email address hidden>
c391924...
by
Mario Limonciello <email address hidden>
drm/amd: add support to check whether the system is set to s3
On some OEM setups users can configure the BIOS for S3 or S2idle.
When configured to S3 users can still choose 's2idle' in the kernel by
using `/sys/power/mem_sleep`. Before commit 6dc8265f9803 ("drm/amdgpu:
always reset the asic in suspend (v2)"), the GPU would crash. Now when
configured this way, the system should resume but will use more power.
As such, adjust the `amdpu_acpi_is_s0ix function` to warn users about
potential power consumption issues during their first attempt at
suspending.
Reported-by: Bjoren Dasse <email address hidden>
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1824
Reviewed-by: Alex Deucher <email address hidden>
Signed-off-by: Mario Limonciello <email address hidden>
Signed-off-by: Alex Deucher <email address hidden>
(cherry picked from commit a6ed2035878e5ad2e43ed175d8812ac9399d6c40)
Signed-off-by: You-Sheng Yang <email address hidden>
1fd115a...
by
Pratik Vishwakarma <email address hidden>
The patch was in upstream as commit d60cd06331a3 "PM: ACPI: reboot: Use
S5 for reboot", but later got reverted by commit 9d3fcb28f9b9 because
reboot caused kernel panic on one system.
The most likely culprit is driver's reboot notifier callback and/or
shutdown callback didn't handle reboot properly. However, the affected
user didn't plan to find the root cause and just wanted a simple revert.
This patch is however quite important for many ACPI based system, as
many reboot stress woe can be addressed by it.
