aboutsummaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/omapdrm/omap_crtc.c
diff options
context:
space:
mode:
authorLaurent Pinchart <[email protected]>2018-09-23 14:13:15 +0300
committerTomi Valkeinen <[email protected]>2019-03-18 11:42:13 +0200
commita4e26525cacb5154a0e00415aa3f889ee5d295db (patch)
tree1ff1393bb5eb901ce58685732d7477a6b3cf2f8d /drivers/gpu/drm/omapdrm/omap_crtc.c
parentce69aac84fe322ab5e1f91224dc15d1957ded75c (diff)
drm/omap: Refactor initialization sequence
The omapdrm driver initialization procedure starts by connecting all available pipelines, gathering related information (such as output and display DSS devices, and DT aliases), sorting them by alias, and finally creates all the DRM/KMS objects. When using DRM bridges instead of DSS devices, we will need to attach to the bridges before getting the aliases. As attaching to bridges requires an encoder object, we have to reorganize the initialization sequence to create encoders before getting aliases and sorting the pipelines. Signed-off-by: Laurent Pinchart <[email protected]> Reviewed-by: Sebastian Reichel <[email protected]> Tested-by: Sebastian Reichel <[email protected]> Signed-off-by: Tomi Valkeinen <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/omapdrm/omap_crtc.c')
0 files changed, 0 insertions, 0 deletions