[PATCH v6 2/2] drm/bridge: lvds-codec: Add support for LVDS data mapping select

Sam Ravnborg sam at ravnborg.org
Sun Oct 10 16:02:44 UTC 2021


Hi Marek,
On Sun, Oct 10, 2021 at 04:49:19PM +0200, Marek Vasut wrote:
> Decoder input LVDS format is a property of the decoder chip or even
> its strapping. Handle data-mapping the same way lvds-panel does. In
> case data-mapping is not present, do nothing, since there are still
> legacy bindings which do not specify this property.
> 
> Reviewed-by: Laurent Pinchart <laurent.pinchart at ideasonboard.com>
> Signed-off-by: Marek Vasut <marex at denx.de>
> Cc: Laurent Pinchart <laurent.pinchart at ideasonboard.com>
> Cc: Sam Ravnborg <sam at ravnborg.org>
Reviewed-by: Sam Ravnborg <sam at ravnborg.org>
> To: dri-devel at lists.freedesktop.org
> ---
> V2: - Move the data-mapping to endpoint
> V3: - Rebase on V2 submitted a while ago, reinstate changelog
>     - Use .atomic_get_input_bus_fmts for the decoder, separate funcs for encoder
> V4: - No change
> V5: - Move the data-mapping property to port at 0 , decoder LVDS input
>     - Add RB from Laurent
> V6: - Turn missing data-mapping into warning, since the driver does
>       continue in legacy probing mode without it.

I assume you will apply the patches.

	Sam


More information about the dri-devel mailing list