- 14 Jul, 2017 40 commits
-
-
Huang Rui authored
Signed-off-by:
Huang Rui <ray.huang@amd.com> Acked-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Junwei Zhang <Jerry.Zhang@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Huang Rui authored
Signed-off-by:
-
Huang Rui authored
Signed-off-by:
-
Shaoyun Liu authored
nbio hdp flush routine are called within atomic context. Avoid use KIQ when write to the HDP_MEM_COHERENCY_FLUSH_CNTL register since this register has its own VF copy Signed-off-by:
Shaoyun Liu <Shaoyun.Liu@amd.com> Reviewed-by:
-
Shaoyun Liu authored
Signed-off-by:
-
Monk Liu authored
for SR-IOV, we must keep the pipeline-sync in the protection of COND_EXEC, otherwise the command consumed by CPG is not consistent when world switch triggerd, e.g.: world switch hit and the IB frame is skipped so the fence won't signal, thus CP will jump to the next DMAframe's pipeline-sync command, and it will make CP hang foever. after pipelin-sync moved into COND_EXEC the consistency can be guaranteed Signed-off-by:
Monk Liu <Monk.Liu@amd.com> Reviewed-by:
-
Rex Zhu authored
Signed-off-by:
Rex Zhu <Rex.Zhu@amd.com> Reviewed-by:
-
Rex Zhu authored
Signed-off-by:
-
Rex Zhu authored
Signed-off-by:
-
Rex Zhu authored
Signed-off-by:
-
Evan Quan authored
Signed-off-by:
Evan Quan <evan.quan@amd.com> Reviewed-by:
-
Evan Quan authored
Signed-off-by:
-
Ken Wang authored
Certain MC registers need a delay after writing them to properly update in the init sequence. Signed-off-by:
Ken Wang <Ken.Wang@amd.com> Reviewed-by:
-
Alex Deucher authored
Check the atom scratch registers to see if asic_init is complete or not. Reviewed-by:
-
Alex Deucher authored
Now that we use a pointer to the scratch reg start offset, most of the functions were duplicated. Acked-by:
-
Alex Deucher authored
Align with the atomfirmware code. Acked-by:
-
Arvind Yadav authored
ttm_place are not supposed to change at runtime. All functions working with ttm_place provided by <drm/ttm/ttm_placement.h> work with const ttm_place. So mark the non-const structs as const. Reviewed-by:
Arvind Yadav <arvind.yadav.cs@gmail.com> Signed-off-by:
-
Arvind Yadav authored
drm_prop_enum_lists are not supposed to change at runtime. All functions working with drm_prop_enum_list provided by <drm/drm_property.h> work with const drm_prop_enum_list. So mark the non-const structs as const. File size before: text data bss dec hex filename 18276 384 0 18660 48e4 drivers/gpu/drm/radeon/radeon_display.o File size After adding 'const': text data bss dec hex filename 18660 0 0 18660 48e4 drivers/gpu/drm/radeon/radeon_display.o Reviewed-by:
-
Arvind Yadav authored
ttm_place are not supposed to change at runtime. All functions working with ttm_place provided by <drm/ttm/ttm_placement.h> work with const ttm_place. So mark the non-const structs as const. File size before: text data bss dec hex filename 9235 344 136 9715 25f3 drivers/gpu/drm/radeon/radeon_ttm.o File size After adding 'const': text data bss dec hex filename 9267 312 136 9715 25f3 drivers/gpu/drm/radeon/radeon_ttm.o Reviewed-by:
-
Christian König authored
Otherwise the upper bits are lost. Signed-off-by:
Alex Xie <AlexBin.Xie@amd.com> Reviewed-by:
-
Christian König authored
That is already fixed. Signed-off-by:
-
Nicolai Hähnle authored
This makes it easier to correlate amd_sched_job with with other trace points that don't log the job pointer. v2: don't print the sched_job pointer (Andres) Signed-off-by:
Nicolai Hähnle <nicolai.haehnle@amd.com> Reviewed-by:
Andres Rodriguez <andresx7@gmail.com> Reviewed-by:
-
Hawking Zhang authored
Signed-off-by:
Hawking Zhang <Hawking.Zhang@amd.com> Reviewed-by:
-
Huang Rui authored
Signed-off-by:
-
Christian König authored
This avoids binding them later on. v2: fix typo in function name Signed-off-by:
Felix Kuehling <Felix.Kuehling@amd.com>
-
Christian König authored
No need to do this on every round. Signed-off-by:
-
Christian König authored
This allows us to flush the system VM here. Signed-off-by:
-
Christian König authored
This allows us to queue IBs which needs an up to date system domain as well. Signed-off-by:
-
Christian König authored
Overwriting still used ring content has a low probability to cause problems, not writing at all has 100% probability to cause problems. Signed-off-by:
-
Christian König authored
Keep them where they belong. Signed-off-by:
-
Gustavo A. R. Silva authored
Add function header comment to make it clear that local variable sw_cg is used for debugging and it should not be removed. Addresses-Coverity-ID: 1198635 Cc: Alex Deucher <alexdeucher@gmail.com> Signed-off-by:
Gustavo A. R. Silva <garsilva@embeddedor.com> Signed-off-by:
-
Kent Russell authored
This was updated to 512 and the description update got missed Signed-off-by:
Kent Russell <kent.russell@amd.com> Reviewed-by:
-
ozeng authored
With previous golden settings, compute task can't use reserved LDS (32K) on CU0 and CU1. On 64K LDS system, if compute work group allocate more than 32K LDS, then it can't be dispatched to CU0 and CU1 because of the reservation. This enables compute task to use reserved LDS on CU0 and CU1. Signed-off-by:
Oak Zeng <Oak.Zeng@amd.com> Acked-by:
-
Christian König authored
Otherwise we trigger a bunch of WARN_ONs when this is called. Signed-off-by:
-
Christian König authored
Stop spreading the code over all GMC generations. Signed-off-by:
-
Gavin Wan authored
This feature works for SRIOV enviroment. For non-SRIOV enviroment, the trans_error function does nothing. The error information includes error_code (16bit), error_flags(16bit) and error_data(64bit). Since there are not many errors, we keep the errors in an array and transfer all errors to Host before amdgpu initialization function (amdgpu_device_init) exit. Signed-off-by:
Gavin Wan <Gavin.Wan@amd.com> Reviewed-by:
-
Mario Kleiner authored
With instantaneous high precision vblank timestamping that updates at leading edge of vblank, a cooked hw vblank counter which increments at leading edge of vblank, and reliable page flip execution and completion at leading edge of vblank, we should meet the requirements for fast/immediate vblank irq disable/enable. Testing on Linux-4.12-rc5 + drm-next on a Radeon R9 380 Tonga Pro (DCE 10) with timing measurement equipment indicates this works fine, so allow immediate vblank disable for power saving. For debugging in case of unexpected trouble, booting with kernel cmdline option drm.vblankoffdelay=0 (or echo 0 > /sys/module/drm/parameters/vblankoffdelay) would keep vblank irqs permanently on to approximate old behavior. Reviewed-by:
Michel Dänzer <michel.daenzer@amd.com> Signed-off-by:
Mario Kleiner <mario.kleiner.de@gmail.com> Cc: Alex Deucher <alexander.deucher@amd.com> Cc: Michel Dänzer <michel.daenzer@amd.com> Signed-off-by:
-
Mario Kleiner authored
With instantaneous high precision vblank timestamping that updates at leading edge of vblank, a cooked hw vblank counter which increments at leading edge of vblank, and reliable page flip execution and completion at leading edge of vblank, we should meet the requirements for fast/immediate vblank irq disable/enable. Testing on Linux-4.12-rc5 + drm-next on a Radeon HD 5770 (DCE 4) with timing measurement equipment indicates this works fine, so allow immediate vblank disable for power saving. For debugging in case of unexpected trouble, booting with kernel cmdline option drm.vblankoffdelay=0 (or echo 0 > /sys/module/drm/parameters/vblankoffdelay) would keep vblank irqs permanently on to approximate old behavior. Reviewed-and-Tested-by:
-
Alex Deucher authored
These are no longer needed now that we use the fb_location programmed by the vbios. Acked-by:
-
Alex Deucher authored
Not used. Reviewed-by:
-
