- 26 Sep, 2017 40 commits
-
-
Amy Zhang authored
- Gamma correction is not properly copied to the surface after refactor - Make sure gamma correction is copied with correct retain Signed-off-by:
Amy Zhang <Amy.Zhang@amd.com> Reviewed-by:
Anthony Koo <Anthony.Koo@amd.com> Acked-by:
Harry Wentland <Harry.Wentland@amd.com> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Yongqiang Sun authored
Signed-off-by:
Yongqiang Sun <yongqiang.sun@amd.com> Reviewed-by:
Tony Cheng <Tony.Cheng@amd.com> Acked-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com> Signed-off-by:
-
Andrey Grodzovsky authored
Retain a dc_sink pointer until a new physical pointer arrives in case of new display connected. Signed-off-by:
Andrey Grodzovsky <Andrey.Grodzovsky@amd.com> Reviewed-by:
-
Tony Cheng authored
- dc_update_surfaces_for_target get called in ISR but apply_clk_constraints allocates memory Signed-off-by:
-
Tony Cheng authored
- is_new_pipe_surface should be addressed with pipe idx, not surface idx Signed-off-by:
-
Harry Wentland authored
Currently we never use more than 2 surfaces in all use cases. This avoids pushing dc_commit_surfaces_to_target beyond a stacksize of 1024. Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Harry Wentland authored
Some of those are potential bugs Signed-off-by:
-
Arindam Nath authored
Some functions like dm_bandwidth_update are placeholders for future implementations. Right now, they simply print messages like "DM_NOT_IMPL: dm_bandwidth_update". This message even though informational, sometimes can create some confusion for users. Since these functions are only skeletons for future, we simply remove the rather un-unecessary messages from these functions. Signed-off-by:
Arindam Nath <arindam.nath@amd.com> Reviewed-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Ding Wang authored
Signed-off-by:
Ding Wang <Ding.Wang@amd.com> Reviewed-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Wenjing Liu authored
Refactor the quantization decision to color module. Add the check if non HDMI, default quantization should be rgb full range. Signed-off-by:
Wenjing Liu <Wenjing.Liu@amd.com> Reviewed-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Dmytro Laktyushkin authored
Signed-off-by:
-
Yongqiang Sun authored
Signed-off-by:
-
Tony Cheng authored
- move to new programming style - clean up table to make it obvious what we are programming Signed-off-by:
Zeyu Fan <Zeyu.Fan@amd.com> Acked-by:
-
Roman Li authored
Signed-off-by:
Roman Li <Roman.Li@amd.com> Reviewed-by:
-
Harry Wentland authored
Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Wenjing Liu authored
The issue causes hue adjustment for rgb limited range color space programmed wrong. Update calculation formula for rgb limited range Signed-off-by:
-
Joshua Aberback authored
- we don't yet support 3D timings in DAL3 - somehow a code path was being executed that resulted in HW programming for a 3D timing, which caused 3D displays to show half the desktop in one frame, and the other half of the desktop in the next frame - blocking all 3D timings in timing generator validation until we implement proper 3D timing support Signed-off-by:
Joshua Aberback <Joshua.Aberback@amd.com> Reviewed-by:
-
jimqu authored
temp_flip_context is always same as current_context, and the current_context will be freed in dc_commit_targets(), but temp_flip_context will be used in dc_update_surfaces_for_target(). Signed-off-by:
JimQu <Jim.Qu@amd.com> Reviewed-by:
-
Zeyu Fan authored
Signed-off-by:
Jordan Lazare <Jordan.Lazare@amd.com> Signed-off-by:
-
Zeyu Fan authored
Signed-off-by:
-
Alex Deucher authored
Now that the mc_access functions are gone, we no longer need separate structs for all the different dce families in dm. Signed-off-by: -
Harry Wentland authored
Supported DCE versions: 8.0, 10.0, 11.0, 11.2 v2: rebase against 4.11 Signed-off-by:
-
Harry Wentland authored
This is needed to ensure every single DC commit builds. Reverting this again when it's no longer needed by DC. This reverts commit 98da65d5. Signed-off-by:
-
Alex Deucher authored
It was not clear. The rest of the driver is MIT/X11. Reviewed-by:
Dave Airlie <airlied@redhat.com> Signed-off-by:
-
Samuel Li authored
v2: drop hdp invalidate/flush. v3: honor pgoff during prime mmap. Add a barrier after cpu access. v4: drop begin/end_cpu_access() for now, revisit later. Signed-off-by:
Samuel Li <Samuel.Li@amd.com> Reviewed-by:
-
Rex Zhu authored
Reviewed-by:
Rex Zhu <Rex.Zhu@amd.com> Signed-off-by:
-
Rex Zhu authored
repeated defining in hwmgr.h Reviewed-by:
-
