- 26 Sep, 2017 2 commits
-
-
Rex Zhu authored
ConfigurableTDP do not exist from Fiji. so only use in previous ASIC. Reviewed-by:
Alex Deucher <alexander.deucher@amd.com> Signed-off-by:
Rex Zhu <Rex.Zhu@amd.com> Signed-off-by:
-
Rex Zhu authored
This ports support for CI asics (Bonaire, Hawaii) to the powerplay smumgr v2: warning fix (Alex) v3: squash in fix for thermal (Tom) Reviewed-by:
-
- 19 Sep, 2017 13 commits
-
-
Rex Zhu authored
Signed-off-by:
-
Rex Zhu authored
Signed-off-by:
-
Rex Zhu authored
Reviewed-by:
-
Rex Zhu authored
put amd_pm_funcs table in struct powerplay for all asics. Signed-off-by:
-
Rex Zhu authored
Reviewed-by:
-
Rex Zhu authored
renamed amdgpu_dpm_funcs and moved to amd_shared.h so can shared with powerplay. Reviewed-by:
-
Rex Zhu authored
delete functiontable related codes Reviewed-by:
-
Rex Zhu authored
use function points instand of function table. Reviewed-by:
-
Rex Zhu authored
1. add function points instand of creat function tables 2. implement stop dpm tasks for CZ/ST Reviewed-by:
-
Rex Zhu authored
add function point start_thermal_controller in hwmgr, delete thermal function table and related functions Reviewed-by:
-
Tom St Denis authored
Signed-off-by:
Tom St Denis <tom.stdenis@amd.com> Reviewed-by:
-
Arnd Bergmann authored
The structure returned from r600_audio_status() is only partially initialized, and older gcc versions (4.3 and 4.4) warn about this: drivers/gpu/drm/radeon/r600_hdmi.c: In function 'r600_audio_status': drivers/gpu/drm/radeon/r600_hdmi.c:108: error: 'status.id' is used uninitialized in this function drivers/gpu/drm/radeon/r600_hdmi.c:108: error: 'status.connected' is used uninitialized in this function drivers/gpu/drm/radeon/r600_hdmi.c:108: error: 'status.offset' is used uninitialized in this function This is harmless and surprisingly correct in C99, as the caller only accesses the fields that got initialized, so newer compilers don't warn about it, but initializing the entire structure feels like the right thing to do here and avoids the warning. Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
-
Alex Deucher authored
So it gets picked up properly by the kernel. Reviewed-by:
Junwei Zhang <Jerry.Zhang@amd.com> Signed-off-by:
-
- 13 Sep, 2017 16 commits
-
-
Allen Pais authored
Signed-off-by:
Allen Pais <allen.lkml@gmail.com> Signed-off-by:
-
Tom St Denis authored
Reviewed-by:
-
Christian König authored
We need to free the reservation object before we take the BO from the delayed delete list. Signed-off-by:
Monk Liu <monk.liu@amd.com> Signed-off-by:
-
Christian König authored
We adjusted the BO flags for USWC handling, but those never took effect because the placement was passed in instead of generated inside this function. v2: better commit message Signed-off-by:
-
Christian König authored
Nobody is actually using this and it causes a bunch of unused and buggy code. Signed-off-by:
-
Christian König authored
This always allocated on PAGE_SIZE alignment. Signed-off-by:
-
Michel Dänzer authored
Fixes crash when trying to unload the radeon module before the fbdev framebuffer was initialized, which can happen since the DRM fbdev helper code supports deferred setup. Acked-by:
Michel Dänzer <michel.daenzer@amd.com> Signed-off-by:
-
Michel Dänzer authored
Fixes crash when trying to unload the amdgpu module before the fbdev framebuffer was initialized, which can happen since the DRM fbdev helper code supports deferred setup. Acked-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Christian König authored
There is no guarantee that the last BO_VA actually needed an update. Additional to that all command submissions must wait for moved BOs to be cleared, not just the first one. v2: Don't overwrite any newer fence. Signed-off-by:
Chunming Zhou <david1.zhou@amd.com> Signed-off-by:
-
- 12 Sep, 2017 9 commits
-
-
Himanshu Jha authored
call to memset to assign 0 value immediately after allocating memory with kzalloc is unnecesaary as kzalloc allocates the memory filled with 0 value. Semantic patch used to resolve this issue: @@ expression e,e2; constant c; statement S; @@ e = kzalloc(e2, c); if(e == NULL) S - memset(e, 0, e2); Signed-off-by:
Himanshu Jha <himanshujha199640@gmail.com> Signed-off-by:
-
Alex Deucher authored
Was only being assigned for vega10. Reviewed-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
-
