kernel/linux.git/drivers/gpu/drm/amd/amdgpu/amdgpu_vcn.c, branch v5.15.89

drm/amdgpu: enable Vangogh VCN indirect sram mode

2022-12-08T10:28:43+00:00

commit 9a8cc8cabc1e351614fd7f9e774757a5143b6fe8 upstream. So that uses PSP to initialize HW. Fixes: 0c2c02b66c672e ("drm/amdgpu/vcn: add firmware support for dimgrey_cavefish") Signed-off-by: Leo Liu Reviewed-by: James Zhu Signed-off-by: Alex Deucher Cc: stable@vger.kernel.org Signed-off-by: Greg Kroah-Hartman

drm/amdgpu: drop redundant cancel_delayed_work_sync call

2021-08-25T22:15:10+00:00

As those _sw_fini() APIs follow just after _suspend() APIs. And the cancel_delayed_work_sync was already called in latter. Signed-off-by: Evan Quan Reviewed-by: Guchun Chen Signed-off-by: Alex Deucher

drm/amd/amdgpu: Use IP discovery data to determine VCN enablement instead of MMSCH

2021-06-18T21:14:01+00:00

In the past, we use MMSCH to determine whether a VCN is enabled or not. This is not reliable since after a FLR, MMSCH may report junk data. It is better to use IP discovery data. Signed-off-by: Bokun Zhang Signed-off-by: Peng Ju Zhou Reviewed-by: Alex Deucher Signed-off-by: Alex Deucher

drm/amdgpu/vcn: drop gfxoff control for VCN2+

2021-06-10T02:15:02+00:00

Drop disabling of gfxoff during VCN use. This allows gfxoff to kick in and potentially save power if the user is not using gfx for color space conversion or scaling. VCN1.0 had a bug which prevented it from working properly with gfxoff, so we disabled it while using VCN. That said, most apps today use gfx for scaling and color space conversion rather than overlay planes so it was generally in use anyway. This was fixed on VCN2+, but since we mostly use gfx for color space conversion and scaling and rapidly powering up/down gfx can negate the advantages of gfxoff, we left gfxoff disabled. As more applications use overlay planes for color space conversion and scaling, this starts to be a win, so go ahead and leave gfxoff enabled. Note that VCN1.0 uses vcn_v1_0_idle_work_handler() and vcn_v1_0_ring_begin_use() so they are not affected by this patch. Reviewed-by: James Zhu Acked-by: Christian König Reviewed-by: Boyuan Zhang Signed-off-by: Alex Deucher

drm/amdgpu/vcn: add vcn support for yellow carp

2021-06-04T20:03:17+00:00

Add vcn firmware support for yellow carp Signed-off-by: James Zhu Reviewed-by: Leo Liu Reviewed-by: Aaron Liu Acked-by: Huang Rui Signed-off-by: Alex Deucher

Merge drm/drm-next into drm-misc-next

2021-05-22T05:17:05+00:00

Backmerging from drm/drm-next to the patches for AMD devices for v5.14. Signed-off-by: Thomas Zimmermann

drm/amdgpu: Guard against write accesses after device removal

2021-05-20T03:50:28+00:00

This should prevent writing to memory or IO ranges possibly already allocated for other uses after our device is removed. v5: Protect more places wher memcopy_to/form_io takes place Protect IB submissions v6: Switch to !drm_dev_enter instead of scoping entire code with brackets. v7: Drop guard of HW ring commands emission protection since they are in GART and not in MMIO. Signed-off-by: Andrey Grodzovsky Reviewed-by: Alex Deucher Link: https://patchwork.freedesktop.org/patch/msgid/20210512142648.666476-10-andrey.grodzovsky@amd.com

drm/amdgpu: Enable VCN for Beige Goby

2021-05-20T02:40:58+00:00

Enabled VCN support for Beige Goby chip Signed-off-by: Veerabadhran Gopalakrishnan Reviewed-by: Leo Liu Signed-off-by: Alex Deucher

drm/amdgpu: enable dpg indirect sram mode on aldebaran

2021-03-24T02:57:15+00:00

Enable dpg indirect sram mode on aldebaran. Signed-off-by: James Zhu Reviewed-by: Leo Liu Signed-off-by: Alex Deucher

drm/amdgpu: add Aldebaran to the VCN family

2021-03-24T02:53:10+00:00

including firmware support etc. Signed-off-by: James Zhu Reviewed-by: Leo Liu Signed-off-by: Alex Deucher