- 06 Dec, 2017 40 commits
-
-
Monk Liu authored
for gart_ram_alloc/free, they are never used in driver thus ripe them out totally. for gart_vram_pin/unpin, they are not needed becuase we can use bo_creat_kernel/free to replace the original manual way in the gart_vram_alloc/free, thus gart_vram_pin/unpin can also be riped out. Signed-off-by:
Monk Liu <Monk.Liu@amd.com> Reviewed-by:
Christian König <christian.koenig@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Monk Liu authored
Signed-off-by:
-
Michel Dänzer authored
This can be triggered by userspace, e.g. trying to allocate too large a BO, so it shouldn't log anything by default. Callers need to handle failure anyway. Reviewed-by:
Michel Dänzer <michel.daenzer@amd.com> Signed-off-by:
-
Roger He authored
keep consistency with threshold of swapout Reviewed-by:
Roger He <Hongbo.He@amd.com> Signed-off-by:
-
David Panariti authored
Make initialization code check the ECC related registers, which are initialized by the VBIOS, to see if ECC is present and initialized and DRM_INFO() the result. Signed-off-by:
David Panariti <David.Panariti@amd.com> Reviewed-by:
-
David Panariti authored
Add header files with ECC related definitions (MASKs, SHIFTs, DEFAULTs and OFFSETS). Signed-off-by:
-
Christian König authored
Deleted BOs with the same reservation object can be reaped even if they can't be reserved. v2: rebase and we still need to remove/add the BO from/to the LRU. v3: fix remove/add one more time, cleanup the logic a bit v4: we should still check if the eviction is valuable v5: add comment suggested by Michel Signed-off-by:
-
Alex Deucher authored
Use the cached values rather than hardcoding it. Acked-by:
-
Alex Deucher authored
Use the cached values rather than hardcoding it. Acked-by:
-
Alex Deucher authored
Use the cached values rather than hardcoding it. Acked-by:
-
Leo (Sunpeng) Li authored
on stream_for_cursor. Initialize to NULL. Signed-off-by:
Leo (Sunpeng) Li <sunpeng.li@amd.com> Reviewed-by:
Harry Wentland <Harry.Wentland@amd.com> Signed-off-by:
-
Harry Wentland authored
We still require the update_plane_addr call in commit_planes_for_stream. Signed-off-by:
Tony Cheng <Tony.Cheng@amd.com> Acked-by:
-
Tony Cheng authored
Signed-off-by:
-
Christian König authored
Needed for the next patch. v2: actually predicate all unlocks v3: add some cleanups suggested by Michel. Signed-off-by:
-
Harry Wentland authored
There's no need to have this as a vtable. The vtable was initially used for stream_adjust_vmin_vmax but the condition checked here (set_drr) is always true, hence we don't need to assign this dynamically anymore. Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Yongqiang Sun authored
for video scaling changes, Reduce reg access count from 1044 to 447, duration time from 4.6ms to 3ms. Signed-off-by:
Yongqiang Sun <yongqiang.sun@amd.com> Reviewed-by:
-
Leo (Sunpeng) Li authored
'struct mpc *mpc' is not used. Signed-off-by:
-
Andrew Jiang authored
This allows us to properly clear and set the update flags for all cases. Signed-off-by:
Andrew Jiang <Andrew.Jiang@amd.com> Reviewed-by:
-
Andrew Jiang authored
Also initialize this to 64 for all ASICs. Signed-off-by:
-
Arun Pandey authored
Signed-off-by:
Arun Pandey <Arun.Pandey@amd.com> Reviewed-by:
Charlene Liu <Charlene.Liu@amd.com> Acked-by:
-
Tony Cheng authored
plane update prior to stream enablement is there to recombine pipe in case we need free pipe for new display. need to pass in new state or we will just re-applyingwhat we already have Signed-off-by:
-
Andrew Jiang authored
This way, we can know exactly what triggered the update type we're looking at, and we can simplify the logic for determining what exactly needs to be updated in the future. Also allow a dst rect size increase to go through a medium update, since that does not require us to increase clock or bandwidth. Signed-off-by:
-
Andrew Jiang authored
We shouldn't be able to get a non-visible plane into DC anymore. Signed-off-by:
-
Leo (Sunpeng) Li authored
The fail goto is incorrect. It will incorrectly release the dc_states on stream programming failure. Signed-off-by:
-
Leo (Sunpeng) Li authored
This is a follow-up to the following change: Yongqiang Sun: Program front end first when set mode. Due to pipe-splitting features, how we handle stream enabling and disabling needs to change. In the case of pipe split disable, two planes need to be combined back into the same stream. This needs to be done before any stream programming happens. The previous patch addresses this, but breaks cross-platform compatibility. It's not guaranteed that a dc commit will be called separately to program planes and streams. Therefore, we handle the combined commit case by doing plane programming both before and after stream programming, to handle pipe split disable and plane enable respectively. Signed-off-by:
-
Leo (Sunpeng) Li authored
When disabling pipe splitting, we need to make sure we disable both planes used. This should be done for Linux as well. Signed-off-by:
-
Yongqiang Sun authored
In case of update type is medium, optimize squence, reduce programing time. Signed-off-by:
-
Roman Li authored
also simplifying syntax and removing unused variable in dce110_apply_ctx_for_surface() Signed-off-by:
Roman Li <Roman.Li@amd.com> Reviewed-by:
-
Yongqiang Sun authored
Power on one plane after disable all the planes, for a hw bug work around to resolve stutter efficiency issue. Signed-off-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com> Reviewed-by:
-
Andrew Jiang authored
Make it so that differing dcc and plane size fields don't necessarily result in a full update, along with upscaling modes. This allows us to save some unnecessary full updates. Signed-off-by:
-
Andrew Jiang authored
Signed-off-by:
-
Eric Yang authored
output signal used to be a public member to be used by DM to override the stream signal. Now since there is no longer separation between public and private part of stream, they are combined. The overriding was not working properly as well, which is addressed by this change Signed-off-by:
Eric Yang <Eric.Yang2@amd.com> Reviewed-by:
-
Harry Wentland authored
Signed-off-by:
Anthony Koo <Anthony.Koo@amd.com> Acked-by:
-
Harry Wentland authored
Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Harry Wentland authored
arr_points[1] and [2] were duplicated. Remove the extra one. If we ever need more points we can add them but the current state of affairs is confusing. Signed-off-by:
-
Tony Cheng authored
Signed-off-by:
-
