Russell King 6ac7c54811 drm: ensure atomic messages consistently include the name of the component ... Most DRM messages include three pieces of information: the type of the component (CRTC, ENCODER, CONNECTOR etc), the DRM object ID of the component, and the component name. However, there are some messages which omit the last piece of identifying information. This makes it harder to debug failures when these messages are printed, because the DRM object ID doesn't supply enough information to know which piece of hardware had a problem. Update the atomic modeset code to always print the component name along with the type and DRM object ID. Fixes: 4cba68507c ("drm/atomic-helper: Reject legacy flips on a disabled pipe") Fixes: 8d4d0d700d ("drm/atomic-helper: Print an error if vblank wait times out") Fixes: 5481c8fb1d ("drm/atomic-helper: Check encoder/crtc constraints") Fixes: 99cf4a29fa ("drm/atomic: Add current-mode blob to CRTC state") Fixes: cc4ceb484b ("drm: Global atomic state handling") Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Acked-by: Thierry Reding <treding@nvidia.com> [danvet: Wiggle in conflicting hunk.] Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>		2017-02-14 21:17:42 +01:00
..
drm	drm: ensure atomic messages consistently include the name of the component	2017-02-14 21:17:42 +01:00
host1x	gpu: host1x: Add locking to syncpt	2016-11-11 15:33:13 +01:00
ipu-v3	imx-drm plane update cleanup, YUV formats	2016-11-11 09:31:27 +10:00
vga	vgaarb: use valid dev pointer in vgaarb_info()	2016-11-22 16:40:35 +01:00
Makefile