kernel/linux.git/drivers/gpu/drm/amd/amdgpu/jpeg_v2_5.c, branch linux-7.0.yLinux kernel stable tree (mirror)https://git.radix-linux.su/kernel/linux.git/atom?h=linux-7.0.y2026-05-23T11:09:31+00:00drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring2026-05-23T11:09:31+00:00Yinjie Yaoyinjie.yao@amd.com2026-04-27T15:46:10+00:00urn:sha1:694fe016969c5e5a24b9e0ef7c1307eedec8ddf8
[ Upstream commit 79405e774ede411c6b47ed41c651e40b92de64a2 ]
JPEG rings do not support 64-bit user fence writes, reject CS
submissions with user fences.
Fixes: 14f43e8f88c5 ("drm/amdgpu: move JPEG2.5 out from VCN2.5")
Reviewed-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Yinjie Yao <yinjie.yao@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
(cherry picked from commit 3216a7f4e2642bda5fd14f57586e835ae9202587)
Signed-off-by: Sasha Levin <sashal@kernel.org>
drm/amdgpu/jpeg: Move parse_cs to amdgpu_jpeg.c2025-09-09T20:18:08+00:00Sathishkumar Ssathishkumar.sundararaju@amd.com2025-08-19T10:41:01+00:00urn:sha1:28f75f9bcc7da7da12e5dae2ae8d8629a2b2e42e
Rename jpeg_v2_dec_ring_parse_cs to amdgpu_jpeg_dec_parse_cs
and move it to amdgpu_jpeg.c as it is shared among jpeg versions.
Signed-off-by: Sathishkumar S <sathishkumar.sundararaju@amd.com>
Reviewed-by: Leo Liu <leo.liu@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: move reset support type checks into the caller2025-07-17T16:36:56+00:00Alex Deucheralexander.deucher@amd.com2025-07-15T15:55:05+00:00urn:sha1:6ac55eab4fc41e0ea80f9064945e4340f13d8b5c
Rather than checking in the callbacks, check if the reset
type is supported in the caller.
Reviewed-by: Lijo Lazar <lijo.lazar@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu/jpeg: clean up reset type handling2025-07-16T20:17:16+00:00Alex Deucheralexander.deucher@amd.com2025-07-15T15:37:56+00:00urn:sha1:82a7c94fcecd104fa70766caaf6423e84bf588cb
Make the handling consistent with other IPs and across
JPEG versions.
Reviewed-by: Sathishkumar S <sathishkumar.sundararaju@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu/jpeg2.5: re-emit unprocessed state on ring reset2025-07-16T20:15:19+00:00Alex Deucheralexander.deucher@amd.com2025-05-29T19:22:01+00:00urn:sha1:bb7928f9fc697294a0026b1a2e28386aa762d001
Re-emit the unprocessed state after resetting the queue.
Reviewed-by: Sathishkumar S <sathishkumar.sundararaju@amd.com>
Tested-by: Sathishkumar S <sathishkumar.sundararaju@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: clean up jpeg reset functions2025-07-16T20:10:01+00:00Alex Deucheralexander.deucher@amd.com2025-07-11T17:31:14+00:00urn:sha1:e3f15cfd8b5dce72d3517c85b7eb6f6633905f6e
Make them consistent and use the reset flags.
Reviewed-by: Sathishkumar S <sathishkumar.sundararaju@amd.com>
Acked-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: move scheduler wqueue handling into callbacks2025-06-30T15:58:22+00:00Alex Deucheralexander.deucher@amd.com2025-06-16T21:45:05+00:00urn:sha1:38b20968f3d8a603a979ac50ff6cf3553e0b3daf
Move the scheduler wqueue stopping and starting into
the ring reset callbacks. On some IPs we have to reset
an engine which may have multiple queues. Move the wqueue
handling into the backend so we can handle them as needed
based on the type of reset available.
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: move force completion into ring resets2025-06-30T15:57:29+00:00Alex Deucheralexander.deucher@amd.com2025-05-29T16:58:53+00:00urn:sha1:2dee58ca471dae05c473270d0fb74efe01a78ccb
Move the force completion handling into each ring
reset function so that each engine can determine
whether or not it needs to force completion on the
jobs in the ring.
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: update ring reset function signature2025-06-30T15:57:16+00:00Alex Deucheralexander.deucher@amd.com2025-06-05T20:12:08+00:00urn:sha1:787e2ce10fdce2b95a9ad81cc244ef22b0c200fe
Going forward, we'll need more than just the vmid. Add the
guilty amdgpu_fence.
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drm/amdgpu: update the handle ptr in is_idle2025-02-25T16:43:58+00:00Sunil Khatrisunil.khatri@amd.com2025-02-19T18:10:52+00:00urn:sha1:7dc340540363a008cee1e160e8f2a4f034f196d4
Update the *handle to amdgpu_ip_block ptr for all
functions pointers of is_idle.
Signed-off-by: Sunil Khatri <sunil.khatri@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>