PSP_VMBX_POLLING_LIMIT too big
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: asad.kamal@xxxxxxx
- Subject: PSP_VMBX_POLLING_LIMIT too big
- From: Mario Limonciello <mario.limonciello@xxxxxxx>
- Date: Tue, 28 Nov 2023 10:21:04 -0600
- Cc: lijo.lazar@xxxxxxx, "amd-gfx@xxxxxxxxxxxxxxxxxxxxx" <amd-gfx@xxxxxxxxxxxxxxxxxxxxx>
- User-agent: Mozilla Thunderbird
Hi,
In amd-staging-drm-next 46fe6312082c ("drm/amdgpu: update retry times
for psp BL wait") and upstream a11156ff6f41 ("drm/amdgpu: update retry
times for psp BL wait") the number of loops for
psp_v13_0_wait_for_bootloader() to try again increased significantly.
It went from 10 loops to 20k loops. Essentially this means that the
function can "effectively" no longer fail.
I've got an issue I'm looking at where runtime resume for a dGPU fails,
and because of this change the system gets stuck in a never ending busy
loop instead of cleanly returning an error code to the caller. The
outcome is the system appears hung while the 20k loops run instead of
just the dGPU failing to resume.
Is this 20k value really required? Or can we reduce it back to
something more manageable?
Thanks,
[Index of Archives]
[Linux USB Devel]
[Linux Audio Users]
[Yosemite News]
[Linux Kernel]
[Linux SCSI]