[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241127151630.GA3515396-robh@kernel.org>
Date: Wed, 27 Nov 2024 09:16:30 -0600
From: Rob Herring <robh@...nel.org>
To: Andrej Picej <andrej.picej@...ik.com>
Cc: andrzej.hajda@...el.com, neil.armstrong@...aro.org, rfoss@...nel.org,
Laurent.pinchart@...asonboard.com, jonas@...boo.se,
jernej.skrabec@...il.com, airlied@...il.com, simona@...ll.ch,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org,
tzimmermann@...e.de, krzk+dt@...nel.org, conor+dt@...nel.org,
shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de,
festevam@...il.com, marex@...x.de, dri-devel@...ts.freedesktop.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/3] dt-bindings: drm/bridge: ti-sn65dsi83: Add optional
property ti,lvds-vcom
On Wed, Nov 27, 2024 at 11:30:29AM +0100, Andrej Picej wrote:
> From: Janine Hagemann <j.hagemann@...tec.de>
>
> Add an optional property to change LVDS output voltage. This depends on
> the connected display specifications. With this property we directly set
> the LVDS_VCOM (0x19) register.
> Better register property mapping would be quite tricky. Please check
> bridge's datasheet for details on how register values set the LVDS
> data lines and LVDS clock output voltage.
>
> Signed-off-by: Janine Hagemann <j.hagemann@...tec.de>
> Signed-off-by: Andrej Picej <andrej.picej@...ik.com>
> ---
> .../bindings/display/bridge/ti,sn65dsi83.yaml | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
> index 48a97bb3e2e0..5b2c0c281824 100644
> --- a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
> +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi83.yaml
> @@ -58,6 +58,12 @@ properties:
> - const: 2
> - const: 3
> - const: 4
> + ti,lvds-vcom:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: LVDS output voltage configuration. This defines
> + LVDS_VCOM (0x19) register value. Check bridge's datasheet for
> + details on how register values set the LVDS data lines and
> + LVDS clock output voltage.
Constraints? 0 - 2^32 are all valid values?
>
> port@1:
> $ref: /schemas/graph.yaml#/$defs/port-base
> @@ -78,6 +84,12 @@ properties:
> - const: 2
> - const: 3
> - const: 4
> + ti,lvds-vcom:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: LVDS output voltage configuration. This defines
> + LVDS_VCOM (0x19) register value. Check bridge's datasheet for
> + details on how register values set the LVDS data lines and
> + LVDS clock output voltage.
Never good to just have 2 copies of the same thing. Move the whole port
schema to a $defs entry and add the property there. Then just $ref it:
port@0:
description: Video port for MIPI DSI Channel-A input
$ref: '#/$defs/dsi-port'
$defs:
dsi-port:
$ref: /schemas/graph.yaml#/$defs/port-base
unevaluatedProperties: false
description: Video port for MIPI DSI inputs
properties:
endpoint:
$ref: /schemas/media/video-interfaces.yaml#
unevaluatedProperties: false
properties:
data-lanes:
description: array of physical DSI data lane indexes.
minItems: 1
items:
- const: 1
- const: 2
- const: 3
- const: 4
Powered by blists - more mailing lists