- 13 Sep, 2017 14 commits
-
-
Christian König authored
We need to free the reservation object before we take the BO from the delayed delete list. Signed-off-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Monk Liu <monk.liu@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
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 <tom.stdenis@amd.com> 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:
-
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 26 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:
Junwei Zhang <Jerry.Zhang@amd.com> Signed-off-by:
-
Tom St Denis authored
Signed-off-by:
Rex Zhu <Rex.Zhu@amd.com> 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:
-
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
Replace and cleanup lengthy phm_cap_enabled() sequences with PP_CAP. Signed-off-by:
-
Tom St Denis authored
To replace common lengthy sequence that would create really long lines all over. Signed-off-by:
-
Tom St Denis authored
Start using new CGS bitmask macros. 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
All users of a VM must always wait for updates with always valid BOs to be completed. v2: remove debugging leftovers, rename struct member Signed-off-by:
Roger He <Hongbo.He@amd.com> Reviewed-by:
Felix Kuehling <Felix.Kuehling@amd.com> Signed-off-by:
-
Evan Quan authored
- v2: share code with CHIP_VEGA10 case Signed-off-by:
Evan Quan <evan.quan@amd.com> Reviewed-by:
Huang Rui <ray.huang@amd.com> Signed-off-by:
-
Evan Quan authored
Otherwise, the ring will fail to create on next resume. Signed-off-by:
-
Evan Quan authored
- v2: reuse the ring stop api in ring destory Signed-off-by:
-
Evan Quan authored
- fw_size in psp_v10_0_prep_cmd_buf is wrongly set as 0 - fixed the wrong calculation of psp_write_ptr_reg in psp_v10_0_cmd_submit Signed-off-by:
-
Christian König authored
Just some cleanup. Signed-off-by:
-
Christian König authored
Just some cleanup. Signed-off-by:
-
Christian König authored
This is quite controversial because it adds another lock which is held during page table updates, but I don't see much other option. v2: allow multiple updates to be in flight at the same time v3: simplify the patch, take the read side only once v4: correctly fix rebase conflict Signed-off-by:
-
