drm/omap: Add support for drm_bridge
Hook up drm_bridge support in the omapdrm driver. Despite the recent extensive preparation work, this is a rather intrusive change, as the management of outputs needs to be adapted through the driver to handle both omap_dss_device and drm_bridge. Connector creation is skipped when using a drm_bridge, as the bridge creates the connector internally. This creates issues with systems that split connector operations (such as modes retrieval and hot-plug detection) across different bridges. These systems can't be supported using drm_bridge for now (their support through the omap_dss_device infrastructure is not affected), this will be fixed in subsequent changes. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com> Tested-by: Sebastian Reichel <sebastian.reichel@collabora.com> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
This commit is contained in:

committed by
Tomi Valkeinen

parent
163f7a3578
commit
79107f274b
@@ -666,7 +666,7 @@ struct drm_crtc *omap_crtc_init(struct drm_device *dev,
|
||||
&omap_crtc_funcs, NULL);
|
||||
if (ret < 0) {
|
||||
dev_err(dev->dev, "%s(): could not init crtc for: %s\n",
|
||||
__func__, pipe->display->name);
|
||||
__func__, pipe->output->name);
|
||||
kfree(omap_crtc);
|
||||
return ERR_PTR(ret);
|
||||
}
|
||||
|
Reference in New Issue
Block a user