- 13 Oct, 2023 40 commits
-
-
Alex Hung authored
This reverts commit 30a24318. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
Alex Hung <alex.hung@amd.com> Reviewed-by:
Harry Wentland <harry.wentland@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Alex Hung authored
This reverts commit ca2b37a1. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit 5d918018. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Yifan Zhang authored
smu_check_fw_version is called in smu hw init, thus smu if version and version are garenteed to be stored in smu context. No need to call smu_cmn_get_smc_version again after system boot up. Signed-off-by:
Yifan Zhang <yifan1.zhang@amd.com> Reviewed-by:
Kenneth Feng <kenneth.feng@amd.com> Signed-off-by:
-
Ma Jun authored
Add reset option for fan_ctrl interfaces on the smu v13.0.7 User can use command "echo r > interface_name" to reset the interface to boot value Signed-off-by:
Ma Jun <Jun.Ma2@amd.com> Acked-by:
-
Ma Jun authored
Add reset option for fan_ctrl interfaces. For example: User can use the "echo r > acoustic_limit_rpm_threshold" command to reset acoustic_limit_rpm_threshold to boot value Signed-off-by:
-
Alex Hung authored
This reverts commit a5f9523c. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit 01aaeb8c. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit cd1a4bc2. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit c6d3c7b6. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit 8a307777. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit 58c3b334. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit 5b89d2cc. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit f6893fcb. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit 428542d9. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit b79a00a4. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit 77a66faa. [WHY & HOW] The writeback series cause a regression in thunderbolt display. Signed-off-by:
-
Alex Hung authored
This reverts commit c4c182b5. After this was commit PCON and USB4 issues were observed. A new fix will be submitted instead. Signed-off-by:
-
Asad Kamal authored
Expose ras table version & schema info to sysfs v2: Updated schema to get poison support info from ras context, removed asic specific checks Signed-off-by:
Asad Kamal <asad.kamal@amd.com> Reviewed-by:
Lijo Lazar <lijo.lazar@amd.com> Signed-off-by:
-
Lijo Lazar authored
PSP OS updates the version information in register. On APUs with PSPv13, PSP OS will already be loaded with SBIOS. Hence use the version register instead of using information in driver binary header. Signed-off-by:
Yang Wang <kevinyang.wang@amd.com> Reviewed-by:
Hawking Zhang <Hawking.Zhang@amd.com> Signed-off-by:
-
Bob Zhou authored
Recently, the driver introduce DML2 for future ASIC support. But, some ASIC's hubbub pointer is null before calling. It cause the below null pointer issue, so add null check to fix it. BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:dc_create_resource_pool+0xc1/0x2c0 [amdgpu] Call Trace: <TASK> ? show_regs.cold+0x1a/0x1f ? __die_body+0x20/0x70 ? __die+0x2b/0x37 ? page_fault_oops+0x136/0x2c0 ? do_user_addr_fault+0x303/0x660 ? exc_page_fault+0x77/0x170 ? asm_exc_page_fault+0x27/0x30 ? dc_create_resource_pool+0xc1/0x2c0 [amdgpu] ? dc_create_resource_pool+0x243/0x2c0 [amdgpu] dc_create+0x23f/0x6b0 [amdgpu] ? dmi_matches+0xa3/0x200 amdgpu_dm_init+0x2bd/0x22a0 [amdgpu] Fixes: 7966f319 ("drm/amd/display: Introduce DML2") Signed-off-by:
Bob Zhou <bob.zhou@amd.com> Acked-by:
-
Lang Yu authored
Program vcn_doorbell_range with vcn_ring0_1. Signed-off-by:
Lang Yu <Lang.Yu@amd.com> Reviewed-by:
Veerabadhran Gopalakrishnan <Veerabadhran.Gopalakrishnan@amd.com> Signed-off-by:
-
Mario Limonciello authored
As dc_set_power_state() no longer allocates memory, it's not necessary to have return types and check return code as it can't fail anymore. Change it back to `void`. Reviewed-by:
Mario Limonciello <mario.limonciello@amd.com> Signed-off-by:
-
Mario Limonciello authored
If there is memory pressure at suspend time then dynamically allocating a large structure as part of DC suspend code will fail. Instead re-use the same structures and clear all members except those that should be maintained. Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2362Acked-by:
-
Mario Limonciello authored
drm_atomic_helper_suspend() can return PTR_ERR(), in which case the error gets stored into `dm->cached_state`. This can cause failures during resume. Catch the error during suspend and fail the suspend instead. Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2362Acked-by:
Christian König <christian.koenig@amd.com> Acked-by:
-
Mario Limonciello authored
amdgpu_uvd_suspend() allocates memory and copies objects into that allocated memory. This fails under memory pressure. Instead move majority of this code into a prepare step when swap can still be allocated. Reviewed-by:
-
Mario Limonciello authored
If any IP blocks allocate memory during their hw_fini() sequence this can cause the suspend to fail under memory pressure. Introduce a new phase that IP blocks can use to allocate memory before suspend starts so that it can potentially be evicted into swap instead. Reviewed-by:
-
Mario Limonciello authored
Linux PM core has a prepare() callback run before suspend. If the system is under high memory pressure, the resources may need to be evicted into swap instead. If the storage backing for swap is offlined during the suspend() step then such a call may fail. So move this step into prepare() to move evict majority of resources and update all non-pmops callers to call the same callback. Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2362Reviewed-by:
-
Li Ma authored
Add CG support for GFX/MC/HDP/ATHUB/IH/BIF. Add PG support for GFX. Signed-off-by:
Li Ma <li.ma@amd.com> Signed-off-by:
-
Lang Yu authored
Power up/down UMSCH by SMU. Signed-off-by:
Leo Liu <leo.liu@amd.com> Acked-by:
-
Lang Yu authored
Add ppt callback to power up/down UMSCH. v2: squash in updates (Alex) Signed-off-by:
-
Lang Yu authored
Powerup VPE by SMU. Signed-off-by:
-
Li Ma authored
add smu 14 into the IP discovery list. Signed-off-by:
-
Kenneth Feng authored
Add initial swSMU support for smu 14 series ASIC. v2: squash in build fixes and updates (Li Ma) fix warnings (Alex) v3: squash in updates (Alex) v4: squash in updates (Alex) v5: squash in avg/current power updates (Alex) Signed-off-by:Likun Gao <Likun.Gao@amd.com> Signed-off-by:
-
Li Ma authored
Add initial smu v14_0_0 pmfw if file v2: squash in updates (Alex) Signed-off-by:
-
Li Ma authored
Add initial smu v14_0_0 ppsmc file v2: squash in updates (Alex) v3: squash in updates (Alex) Signed-off-by:
-
Li Ma authored
Add initial smu v14_0_0 driver if file v2: squash in updates (Alex) v3: update interface (Alex) Signed-off-by:
-
Lang Yu authored
VCN 4.0.5 uses DLDO. Signed-off-by:
-
Lang Yu authored
These changes are missed in rebase. Signed-off-by:
-
Lijo Lazar authored
IP discovery region has increased to > 8K on some SOCs.Maximum reserve size is upto 12K, but not used. For now increase to 10K. Signed-off-by:
-
