diff options
| author | Chen Li <chenli@uniontech.com> | 2021-06-04 16:43:02 +0800 |
|---|---|---|
| committer | Sasha Levin <sashal@kernel.org> | 2021-06-30 08:49:34 -0400 |
| commit | 959f053a01c4e65e2d12dff4d0da393970de67da (patch) | |
| tree | 9f149b5feb234bd0ef4edafaea6e953ea0c88e8b /kernel/trace/trace_clock.c | |
| parent | fbedbc8fb1dc2bc0545523ff6d6792d697a17ba9 (diff) | |
radeon: use memcpy_to/fromio for UVD fw upload
[ Upstream commit ab8363d3875a83f4901eb1cc00ce8afd24de6c85 ]
I met a gpu addr bug recently and the kernel log
tells me the pc is memcpy/memset and link register is
radeon_uvd_resume.
As we know, in some architectures, optimized memcpy/memset
may not work well on device memory. Trival memcpy_toio/memset_io
can fix this problem.
BTW, amdgpu has already done it in:
commit ba0b2275a678 ("drm/amdgpu: use memcpy_to/fromio for UVD fw upload"),
that's why it has no this issue on the same gpu and platform.
Signed-off-by: Chen Li <chenli@uniontech.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'kernel/trace/trace_clock.c')
0 files changed, 0 insertions, 0 deletions