linux/drivers/gpu/drm/amd
Leo (Sunpeng) Li 0bc9706db3 drm/amd/display: Use new DRM API where possible
To conform to DRM's new API, we should not be accessing a DRM object's
internal state directly. Rather, the DRM for_each_old/new_* iterators,
and drm_atomic_get_old/new_* interface should be used.

This is an ongoing process. For now, update the DRM-facing atomic
functions, where the atomic state object is given.

Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Signed-off-by: Leo (Sunpeng) Li <sunpeng.li@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
2017-10-17 10:42:55 +10:00
..
acp drm: amd: remove broken include path 2017-03-14 19:19:44 -04:00
amdgpu Merge branch 'drm-next-4.15-dc' of git://people.freedesktop.org/~agd5f/linux into drm-next 2017-10-09 11:21:15 +10:00
amdkfd Linux 4.14-rc3 2017-10-03 09:35:04 +10:00
display drm/amd/display: Use new DRM API where possible 2017-10-17 10:42:55 +10:00
include Merge branch 'drm-next-4.15-dc' of git://people.freedesktop.org/~agd5f/linux into drm-next 2017-10-09 11:21:15 +10:00
lib drm/amd/chash: Fix typo 2017-09-28 16:03:29 -04:00
powerplay drm/amd/powerplay: fix mclk can't switch on Tonga 2017-10-06 17:43:51 -04:00
scheduler drm/amd/sched: fix deadlock caused by unsignaled fences of deleted jobs 2017-10-06 17:44:32 -04:00