[PATCH v3 02/10] dt-bindings: display: bridge: thc63lvd1024: Document dual-link operation
Kieran Bingham
kieran.bingham at ideasonboard.com
Fri Jun 7 22:15:06 UTC 2019
Hi Laurent,
On 28/05/2019 15:12, Laurent Pinchart wrote:
> The THC63LVD1024 LVDS decoder can operate in two modes, single-link or
> dual-link. In dual-link mode both input ports are used to carry even-
> and odd-numbered pixels separately. Document this in the DT bindings,
> along with the related rules governing port and usage.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas at ideasonboard.com>
> Reviewed-by: Jacopo Mondi <jacopo+renesas at jmondi.org>
> Reviewed-by: Rob Herring <robh at kernel.org>
> Tested-by: Jacopo Mondi <jacopo+renesas at jmondi.org>
> ---
> .../bindings/display/bridge/thine,thc63lvd1024.txt | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt b/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt
> index 37f0c04d5a28..d17d1e5820d7 100644
> --- a/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt
> +++ b/Documentation/devicetree/bindings/display/bridge/thine,thc63lvd1024.txt
> @@ -28,6 +28,12 @@ Optional video port nodes:
> - port at 1: Second LVDS input port
> - port at 3: Second digital CMOS/TTL parallel output
>
> +The device can operate in single-link mode or dual-link mode. In single-link
> +mode, all pixels are received on port at 0, and port at 1 shall not contain any
> +endpoint. In dual-link mode, even-numbered pixels are received on port at 0 and
> +odd-numbered pixels on port at 1, and both port at 0 and port at 1 shall contain
> +endpoints.
> +
Your cover letter details 4 different modes of operation for this part.
Do you anticipate the other combinations {Single-in, dual-out; dual-in,
dual-out} being supported? Perhaps that would be defined by the relevant
endpoints being connected or not ?
You state that in dual-link mode, both port at 0, and port at 1 shall contain
endpoints, so that implies that you only expect to support dual-in with
the 'dual-link' property. If that is correct, should it be stated
explicitly?
Otherwise,
Reviewed-by: Kieran Bingham <kieran.bingham+renesas at ideasonboard.com>
> Example:
> --------
>
>
--
Regards
--
Kieran
More information about the dri-devel
mailing list