[PATCH 31/60] drm/omap: Add infrastructure to support drm_bridge local to DSS outputs

Tomi Valkeinen tomi.valkeinen at ti.com
Tue Aug 13 07:44:55 UTC 2019

On 07/07/2019 21:19, Laurent Pinchart wrote:
> In order to support drm_bridge-based pipeline, the internal HDMI
> encoders will need to expose the EDID read operation through the
> drm_bridge API, and thus to expose a drm_bridge instance corresponding
> to the encoder. The HDMI encoders are however handled as omap_dss_device
> instances, which conflicts with this requirement.
> In order to move forward with the drm_bridge transition, add support for
> creating drm_bridge instances local to DSS outputs. If a local bridge is
> passed to the omapdss_device_init_output() function, it is used as the
> first bridge in the chain, and the omap_dss_device.next_bridge field is
> set to the next bridge for the use of the internal encoders' bridges.
> Signed-off-by: Laurent Pinchart <laurent.pinchart at ideasonboard.com>

Reviewed-by: Tomi Valkeinen <tomi.valkeinen at ti.com>


Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

More information about the dri-devel mailing list