summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/tasks.py
diff options
context:
space:
mode:
authorDanijel Slivka <danijel.slivka@amd.com>2024-07-05 15:15:32 +0300
committerAlex Deucher <alexander.deucher@amd.com>2024-07-10 17:12:37 +0300
commit708f220567d4a398ee1553ee6519f7e73ae5ed6c (patch)
tree9b15d455fc98f45b1e8c8b31392c3f29d9675508 /scripts/gdb/linux/tasks.py
parentd02ddefc7eedaa6394279bad522c70fd5d63e163 (diff)
downloadlinux-708f220567d4a398ee1553ee6519f7e73ae5ed6c.tar.xz
drm/amd/pm: Ignore initial value in smu response register
Why: If the reg mmMP1_SMN_C2PMSG_90 is being written to during amdgpu driver load or driver unload, subsequent amdgpu driver load will fail at smu_hw_init. The default of mmMP1_SMN_C2PMSG_90 register at a clean environment is 0x1 and if value differs from expected, amdgpu driver load will fail. How to fix: Ignore the initial value in smu response register before the first smu message is sent,if smc in SMU_FW_INIT state, just proceed further to send the message. If register holds an unexpected value after smu message was sent set, smc_state to SMU_FW_HANG state and no further smu messages will be sent. v2: Set SMU_FW_INIT state at the start of smu hw_init/resume. Check smc_fw_state before sending smu message if in hang state skip sending message. Set SMU_FW_HANG only in case unexpected value is detected Signed-off-by: Danijel Slivka <danijel.slivka@amd.com> Reviewed-by: Kenneth Feng <kenneth.feng@amd.com> Reviewed-by: Lijo Lazar <lijo.lazar@amd.com> Reviewed-by: Asad Kamal <asad.kamal@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'scripts/gdb/linux/tasks.py')
0 files changed, 0 insertions, 0 deletions