https://github.com/torvalds/linux
Revision cf7fc75523b32a9a119a466dcff325f1fda38c7d authored by Yongqiang Sun on 09 December 2020, 21:56:51 UTC, committed by Alex Deucher on 23 December 2020, 20:01:53 UTC
[Why]
there is some garbage showing up during reboot test.
Reason:
SMU might handle display driver msg defered and driver will send
next msg to SMU after 10ms timeout, once SMU FW handle previous msg,
parameters are changed to next one, which result in a wrong value be programmed.

[How]
Extend timeout to 2s so SMU will have enough time to handle driver msg.

Signed-off-by: Yongqiang Sun <yongqiang.sun@amd.com>
Acked-by: Bindu Ramamurthy <bindu.r@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
1 parent e8e91f9
History
Tip revision: cf7fc75523b32a9a119a466dcff325f1fda38c7d authored by Yongqiang Sun on 09 December 2020, 21:56:51 UTC
drm/amd/display: change SMU repsonse timeout to 2s.
Tip revision: cf7fc75
File Mode Size
devfs -rw-r--r-- 472 bytes
dv1394 -rw-r--r-- 664 bytes
ip_queue -rw-r--r-- 310 bytes
net_dma -rw-r--r-- 339 bytes
o2cb -rw-r--r-- 449 bytes
raw1394 -rw-r--r-- 664 bytes
sysfs-bus-nfit -rw-r--r-- 809 bytes
sysfs-class-rfkill -rw-r--r-- 499 bytes
sysfs-kernel-fadump_release_opalcore -rw-r--r-- 346 bytes
sysfs-kernel-uids -rw-r--r-- 697 bytes
video1394 -rw-r--r-- 752 bytes

back to top