* [PATCH] dt-bindings: display: dsi-controller: add bridge to patternProperties
@ 2025-08-22 18:23 Harikrishna Shenoy
2025-08-26 22:52 ` Rob Herring
0 siblings, 1 reply; 2+ messages in thread
From: Harikrishna Shenoy @ 2025-08-22 18:23 UTC (permalink / raw)
To: maarten.lankhorst, mripard, tzimmermann, airlied, simona, robh,
krzk+dt, conor+dt, linus.walleij, dri-devel, devicetree
This patch extends the binding schema by adding a new `bridge@[0-3]` to
represent any bridge devices attached as DSI peripheral.
Signed-off-by: Harikrishna Shenoy <h-shenoy@ti.com>
---
.../bindings/display/dsi-controller.yaml | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/dsi-controller.yaml b/Documentation/devicetree/bindings/display/dsi-controller.yaml
index 67ce10307ee0..d7ca700070a9 100644
--- a/Documentation/devicetree/bindings/display/dsi-controller.yaml
+++ b/Documentation/devicetree/bindings/display/dsi-controller.yaml
@@ -73,6 +73,24 @@ patternProperties:
required:
- reg
+ "^bridge@[0-3]$":
+ description: Bridge connected to the DSI link
+ type: object
+
+ properties:
+ reg:
+ minimum: 0
+ maximum: 3
+ description:
+ The virtual channel number of a DSI peripheral. Must be in the range
+ from 0 to 3, as DSI uses a 2-bit addressing scheme. Some DSI
+ peripherals respond to more than a single virtual channel. In that
+ case the reg property can take multiple entries, one for each virtual
+ channel that the peripheral responds to.
+
+ required:
+ - reg
+
additionalProperties: true
examples:
--
2.34.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] dt-bindings: display: dsi-controller: add bridge to patternProperties
2025-08-22 18:23 [PATCH] dt-bindings: display: dsi-controller: add bridge to patternProperties Harikrishna Shenoy
@ 2025-08-26 22:52 ` Rob Herring
0 siblings, 0 replies; 2+ messages in thread
From: Rob Herring @ 2025-08-26 22:52 UTC (permalink / raw)
To: Harikrishna Shenoy
Cc: maarten.lankhorst, mripard, tzimmermann, airlied, simona, krzk+dt,
conor+dt, linus.walleij, dri-devel, devicetree
On Fri, Aug 22, 2025 at 11:53:52PM +0530, Harikrishna Shenoy wrote:
> This patch extends the binding schema by adding a new `bridge@[0-3]` to
Use imperative mood. See submitting-patches.rst.
> represent any bridge devices attached as DSI peripheral.
>
> Signed-off-by: Harikrishna Shenoy <h-shenoy@ti.com>
> ---
> .../bindings/display/dsi-controller.yaml | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/dsi-controller.yaml b/Documentation/devicetree/bindings/display/dsi-controller.yaml
> index 67ce10307ee0..d7ca700070a9 100644
> --- a/Documentation/devicetree/bindings/display/dsi-controller.yaml
> +++ b/Documentation/devicetree/bindings/display/dsi-controller.yaml
> @@ -73,6 +73,24 @@ patternProperties:
> required:
> - reg
>
> + "^bridge@[0-3]$":
Rather than duplicating all this, just change
the above entry to: '^(panel|bridge)@[0-3]$'
> + description: Bridge connected to the DSI link
> + type: object
> +
> + properties:
> + reg:
> + minimum: 0
> + maximum: 3
> + description:
> + The virtual channel number of a DSI peripheral. Must be in the range
> + from 0 to 3, as DSI uses a 2-bit addressing scheme. Some DSI
> + peripherals respond to more than a single virtual channel. In that
> + case the reg property can take multiple entries, one for each virtual
> + channel that the peripheral responds to.
> +
> + required:
> + - reg
> +
> additionalProperties: true
>
> examples:
> --
> 2.34.1
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-08-26 22:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-08-22 18:23 [PATCH] dt-bindings: display: dsi-controller: add bridge to patternProperties Harikrishna Shenoy
2025-08-26 22:52 ` Rob Herring
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).