- 26 Sep, 2017 40 commits
-
-
Dave Airlie authored
DAL has defines for things, and it doesn't even use them itself. Signed-off-by:
Dave Airlie <airlied@redhat.com> Reviewed-by:
Tony Cheng <Tony.Cheng@amd.com> Reviewed-by:
Harry Wentland <Harry.Wentland@amd.com> Reviewed-by:
Edward O'Callaghan <funfunctor@folklore1984.net> Signed-off-by:
Alex Deucher <alexander.deucher@amd.com>
-
Dave Airlie authored
These aren't needed, and aren't really used in too many places. Signed-off-by:
-
Joshua Aberback authored
- pass full asic_id info into bw_calc_init instead of only version enum - 64-bit Polaris11 needs an extra microsecond of dmif_urgent_latency - add helper to convert from asic_id.family to bw_calc version enum Signed-off-by:
Joshua Aberback <Joshua.Aberback@amd.com> Reviewed-by:
-
Joshua Aberback authored
Signed-off-by:
-
Hersen Wu authored
1. remove the sleep mechanism while set_blank true from the timing generator. Since Hw sequencer is the one that manages the flow he will be responsible for wait for blanck in a critical places. Signed-off-by:
Leon Elazar <leon.elazar@amd.com> Reviewed-by:
-
Leon Elazar authored
blank/unblanck functionality apply_ctx_for_surface will update planes visibility by manipulating Blender and CRTC HW modules. Signed-off-by:
Dmytro Laktyushkin <Dmytro.Laktyushkin@amd.com> Reviewed-by:
-
Arindam Nath authored
Since during suspend, the cursor registers are cleared, once the system resumes back, the cursor remains disabled. cursor_set_attributes() only sets the cursor attributes along with cursor size and surface address, but does not enable the cursor back on. We need to save the current cursor location so that we can resume back to the same location. This is done in dm_crtc_cursor_move(), where we save the current cursor location into cursor_x and cursor_y. Later during resume we use these same values to set the cursor position along with cursor attributes. Signed-off-by:
Arindam Nath <arindam.nath@amd.com> Reviewed-by:
-
Xiangliang Yu authored
Virtualization don't need the dc, disable it. Signed-off-by:
Xiangliang Yu <Xiangliang.Yu@amd.com> Reviewed-by:
Christian König <christian.koenig@amd.com> Reviewed-by:
Monk Liu <Monk.Liu@amd.com> Signed-off-by:
-
Yongqiang Sun authored
Signed-off-by:
Yongqiang Sun <yongqiang.sun@amd.com> Acked-by:
-
Tony Cheng authored
Signed-off-by:
-
Tony Cheng authored
Signed-off-by:
-
Yongqiang Sun authored
In case of programing info frame to some monitors don't support HDR, it will result in black screen or corruption when unplug monitor. By checking hdr flag to avoid unnecessary setting for monitors don't support HDR. Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Andrey Grodzovsky authored
Problem: MST topology discovery was started before fbdev init causing kernel panic on boot. Fix: Defer MST to late init hook, after fbdev strucutres already initilized. v2: Add explicit late_init hook function in DAL. v3: Change signature of detect_mst_link_for_all_connectors from void* to drm_dev* Signed-off-by:
Andrey Grodzovsky <Andrey.Grodzovsky@amd.com> Reviewed-by:
-
Hersen Wu authored
Signed-off-by:
Hersen Wu <hersenxs.wu@amd.com> Reviewed-by:
-
Roman Li authored
For dpms usecase we need to set surface transfer function regardless of gamma set flag. Signed-off-by:
Roman Li <Roman.Li@amd.com> Reviewed-by:
-
Tony Cheng authored
- also fix YCbCr420 supported on Polaris and up Signed-off-by:
-
Tony Cheng authored
- remove unnecessary feature flags - remove wireless and VGA validation Signed-off-by:
-
Hersen Wu authored
Signed-off-by:
-
Zeyu Fan authored
Signed-off-by:
Zeyu Fan <Zeyu.Fan@amd.com> Reviewed-by:
-
Harry Wentland authored
Signed-off-by:
-
Tony Cheng authored
Signed-off-by:
Anthony Koo <Anthony.Koo@amd.com> Acked-by:
-
Anthony Koo authored
Assume we have two monitors, and monitor 0 is unplugged. This shifts the internal state of index 1 to index 0 by memcpy. This means there are two copies of the gamma pointer previously owned by state[1]. When hotplug occurs, this re-assigns the new display with state[1], which has some garbage left over from before, including the gamma pointer. We should correctly clear unused states and re-initialize correctly. Also, due to async nature of the hotplug and other events like commit, we also need to safe guard against sink that has been removed. Signed-off-by:
Aric Cyr <Aric.Cyr@amd.com> Reviewed-by:
-
Hersen Wu authored
Signed-off-by:
-
Yongqiang Sun authored
Signed-off-by:
-
Hersen Wu authored
Signed-off-by:
-
Harry Wentland authored
It might blow up. Signed-off-by:
-
Tony Cheng authored
Signed-off-by:
-
Tony Cheng authored
Signed-off-by:
-
Andrew Wong authored
- Add HDR metadata struct - Add register programming calculations - Added HDR metadata to surface and update_surface - Add HDR info packet programming for DP port Signed-off-by:
Andrew Wong <andrew.wong1@amd.com> Reviewed-by:
-
Tony Cheng authored
Signed-off-by:
Jordan Lazare <Jordan.Lazare@amd.com> Acked-by:
-
Andrey Grodzovsky authored
Signed-off-by:
-
Andrey Grodzovsky authored
Signed-off-by:
-
Yongqiang Sun authored
Signed-off-by:
-
Yongqiang Sun authored
Signed-off-by:
-
Harry Wentland authored
Signed-off-by:
-
Yongqiang Sun authored
Signed-off-by:
-
