drm/amdgpu: Avoid jpeg v5.0.1 poison irq call trace on sriov guest

Sriov guest side doesn't init ras feature hence the poison irq shouldn't
be put during hw fini

Signed-off-by: Mangesh Gadre <Mangesh.Gadre@amd.com>
Reviewed-by: Hawking Zhang <Hawking.Zhang@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

diff --git a/drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_1.c b/drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_1.c
index a2d781898767ea4ca41303ebb478fe1e9c95509f..47bde62b39099fb88e3b8d301f184039a95af5ef 100644 (file)
--- a/drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_1.c
+++ b/drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_1.c
@@ -315,7 +315,7 @@ static int jpeg_v5_0_1_hw_fini(struct amdgpu_ip_block *ip_block)
                        ret = jpeg_v5_0_1_set_powergating_state(ip_block, AMD_PG_STATE_GATE);
        }
 
-       if (amdgpu_ras_is_supported(adev, AMDGPU_RAS_BLOCK__JPEG))
+       if (amdgpu_ras_is_supported(adev, AMDGPU_RAS_BLOCK__JPEG) && !amdgpu_sriov_vf(adev))
                amdgpu_irq_put(adev, &adev->jpeg.inst->ras_poison_irq, 0);
 
        return ret;