- 06 Dec, 2017 37 commits
-
-
Harry Wentland authored
Signed-off-by:
Harry Wentland <harry.wentland@amd.com> Reviewed-by:
Tony Cheng <Tony.Cheng@amd.com> Acked-by:
Alex Deucher <alexander.deucher@amd.com>
-
Harry Wentland authored
Trying to align with kernel coding style and make it a bit more readable. Signed-off-by:
-
Yongqiang Sun authored
There are different code to disable front end, it is difficult to debug and adding new process. This refactor makes all disable front end call the same functions. Signed-off-by:
Yongqiang Sun <yongqiang.sun@amd.com> Reviewed-by:
-
Tony Cheng authored
Signed-off-by:
-
Yue Hin Lau authored
Signed-off-by:
Yue Hin Lau <Yuehin.Lau@amd.com> Reviewed-by:
-
Tony Cheng authored
Signed-off-by:
-
Yue Hin Lau authored
Signed-off-by:
Eric Bernstein <Eric.Bernstein@amd.com> Acked-by:
-
Eric Bernstein authored
Added a function to blank data using OPP DPG. Clean up code to prepare for pseudocode review with HW. Signed-off-by:
-
Tony Cheng authored
Signed-off-by:
-
Dmytro Laktyushkin authored
This saves us about 5000 reg writes per full update. This translates to about 40000 writes over the course of single eDP bootup. Signed-off-by:
Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com> Reviewed-by:
-
Andrew Jiang authored
dc_link is at a higher level than link_encoder, and we only want higher-level components to be able to access lower-level ones, not the other way around. Signed-off-by:
Andrew Jiang <Andrew.Jiang@amd.com> Reviewed-by:
-
Harry Wentland authored
Previous code threw a warning about misleading indentation Signed-off-by:
Mikita Lipski <Mikita.Lipski@amd.com> Acked-by:
-
Yongqiang Sun authored
Clear OPTC underflow status when init_hw. Signed-off-by:
-
Yongqiang Sun authored
Signed-off-by:
-
Eric Yang authored
Signed-off-by:
Eric Yang <Eric.Yang2@amd.com> Reviewed-by:
-
Yue Hin Lau authored
Signed-off-by:
-
Eric Bernstein authored
Also move some register definitions to common DCN regs. Signed-off-by:
-
Tony Cheng authored
Signed-off-by:
-
Yue Hin Lau authored
no logic change Signed-off-by:
-
Charlene Liu authored
Signed-off-by:
Charlene Liu <charlene.liu@amd.com> Reviewed-by:
Anthony Koo <Anthony.Koo@amd.com> Acked-by:
-
Yue Hin Lau authored
following the naming convention with correct prefix Signed-off-by:
-
Yue Hin Lau authored
dcn version of update_dchub now uses hubbub instead of hwseq Signed-off-by:
-
Colin Ian King authored
Variable pf2vf_ver is assigned but never read, it is redundant and hence can be removed. Cleans up clang warning: drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c:310:3: warning: Value stored to 'pf2vf_ver' is never read Reivewed-by:
Horace Chen <horace.chen@amd.com> Signed-off-by:
Colin Ian King <colin.king@canonical.com> Signed-off-by:
-
Piotr Redlewski authored
When UVD bo is created, its size is based on the information from firmware header (ucode_size_bytes). The same value should be be used when programming UVD mc controller offsets, otherwise it can happen that (mmUVD_VCPU_CACHE_OFFSET2 + mmUVD_VCPU_CACHE_SIZE2) will point AMDGPU_GPU_PAGE_SIZE bytes after the UVD bo end. Second issue is that when programming the mmUVD_VCPU_CACHE_SIZE0 register, AMDGPU_UVD_FIRMWARE_OFFSET should be taken into account. If it isn't, (mmUVD_VCPU_CACHE_OFFSET2 + mmUVD_VCPU_CACHE_SIZE2) will always point AMDGPU_UVD_FIRMWARE_OFFSET bytes after the UVD bo end. v2: move firmware size calculation into macro definition v3: align firmware size to the gpu page size Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
Piotr Redlewski <predlewski@gmail.com> Signed-off-by:
-
Mikita Lipski authored
This feature synchronizes multiple displays with various timings to a display with the highest refresh rate it is enabled if edid caps flag multi_display_sync is set to one There are limitations on refresh rates allowed that can be synchronized. That would prevent from underflow and other potential corruptions. Multi display synchronization is using the same functions as timing_sync in order to minimize redunduncy and decision to disable synchronization is based on trigger parametre set in DM Feature is developed for DCN1 and DCE11 Signed-off-by:
-
Andrey Grodzovsky authored
Validates BO size against each requested domain's total memory. v2: Make GTT size check a MUST to allow fall back to GTT. Rmove redundant NULL check. Signed-off-by:
Andrey Grodzovsky <andrey.grodzovsky@amd.com> Reviewed-by:
-
Christian König authored
It's pointless to have the same value twice, just always use max_pfn. Signed-off-by:
-
Christian König authored
Not sure what that should originally been good for, but it doesn't seem to make any sense any more. Signed-off-by:
-
Chunming Zhou authored
Otherwise, they could be optimized by scheduled fence. Signed-off-by:
Chunming Zhou <david1.zhou@amd.com> Reviewed-by:
-
Xiangliang.Yu authored
Do ring clear before ring test, otherwise compute ring test will fail after gpu resetting. Still can't find the root cause, just workaround it. Signed-off-by:
Xiangliang.Yu <Xiangliang.Yu@amd.com> Acked-by:
Monk Liu <Monk.Liu@amd.com> Signed-off-by:
-
Christian König authored
Just another alias for ttm_bo_unreserve. Signed-off-by:
Michel Dänzer <michel.daenzer@amd.com> Signed-off-by:
-
Christian König authored
Consistently use the reservation object wrappers instead of accessing the ww_mutex directly. Additional to that use the reservation object wrappers directly instead of calling __ttm_bo_reserve with fixed parameters. v2: fix typo Signed-off-by:
-
Christian König authored
Instead of having a confusing wrapper or call the underlying ww_mutex function directly. Signed-off-by:
-
Christian König authored
Needed for the next patch and makes the code quite a bit easier to understand. Signed-off-by:
-
Chunming Zhou authored
Signed-off-by:
-
Chunming Zhou authored
We must remove the fence callback. Signed-off-by:
-
Pixel Ding authored
Retry at drm_dev_register instead of amdgpu_device_init. Reviewed-by:
Pixel Ding <Pixel.Ding@amd.com> Signed-off-by:
-
- 04 Dec, 2017 3 commits
-
-
Harry Wentland authored
We no longer set the framebuffer address here so this is now dead code. Signed-off-by:
-
Monk Liu authored
if app close CTX right after IB submit, gpu recover will fail to find out the entity behind this guilty job thus lead to no job skipping for this guilty job. to fix this corner case just move the increasement of job->karma out of the entity iteration. v2: only do karma increasment if bad->s_priority != KERNEL because we always consider KERNEL job be correct and always want to recover an unfinished kernel job (sometimes kernel job is interrupted by VF FLR or other GPU hang event) Signed-off-by:
-
Monk Liu authored
Signed-off-by:
-
