From: Rob Herring <robh@kernel.org>
To: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
Cc: tomi.valkeinen@ideasonboard.com, mchehab@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, hverkuil@xs4all.nl,
sakari.ailus@linux.intel.com, laurent.pinchart@ideasonboard.com,
hansg@kernel.org, mehdi.djait@linux.intel.com,
ribalda@chromium.org, git@apitzsch.eu,
vladimir.zapolskiy@linaro.org, benjamin.mugnier@foss.st.com,
dongcheng.yan@intel.com, u-kumar1@ti.com, jai.luthra@linux.dev,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 3/4] media: dt-bindings: ti,ds90ub960: Add support for DS90UB954-Q1
Date: Fri, 5 Dec 2025 09:17:37 -0600 [thread overview]
Message-ID: <20251205151737.GB158904-robh@kernel.org> (raw)
In-Reply-To: <20251202102208.80713-4-y-abhilashchandra@ti.com>
On Tue, Dec 02, 2025 at 03:52:07PM +0530, Yemike Abhilash Chandra wrote:
> DS90UB954-Q1 is an FPDLink-III deserializer that is mostly register
> compatible with DS90UB960-Q1. The main difference is that it supports
> half of the RX and TX ports, i.e. 2x FPDLink RX ports and 1x CSI TX
> port. Therefore, add support for DS90UB954 within the existing bindings.
>
> Link: https://www.ti.com/lit/gpn/ds90ub954-q1
> Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
> ---
> .../bindings/media/i2c/ti,ds90ub960.yaml | 300 +++++++++++++++---
> 1 file changed, 264 insertions(+), 36 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/ti,ds90ub960.yaml b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub960.yaml
> index 6a78288aebaa..1ef977c2e479 100644
> --- a/Documentation/devicetree/bindings/media/i2c/ti,ds90ub960.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub960.yaml
> @@ -13,12 +13,10 @@ description:
> The TI DS90UB9XX devices are FPD-Link video deserializers with I2C and GPIO
> forwarding.
>
> -allOf:
> - - $ref: /schemas/i2c/i2c-atr.yaml#
> -
> properties:
> compatible:
> enum:
> + - ti,ds90ub954-q1
> - ti,ds90ub960-q1
> - ti,ds90ub9702-q1
>
> @@ -129,39 +127,6 @@ properties:
> Ports represent FPD-Link inputs to the deserializer and CSI TX outputs from the deserializer.
> Their number is model-dependent.
>
> - properties:
> - port@0:
> - $ref: '#/$defs/FPDLink-input-port'
> - description: FPD-Link input 0
> -
> - port@1:
> - $ref: '#/$defs/FPDLink-input-port'
> - description: FPD-Link input 1
> -
> - port@2:
> - $ref: '#/$defs/FPDLink-input-port'
> - description: FPD-Link input 2
> -
> - port@3:
> - $ref: '#/$defs/FPDLink-input-port'
> - description: FPD-Link input 3
> -
> - port@4:
> - $ref: '#/$defs/CSI2-output-port'
> - description: CSI-2 Output 0
> -
> - port@5:
> - $ref: '#/$defs/CSI2-output-port'
> - description: CSI-2 Output 1
> -
> - required:
> - - port@0
> - - port@1
> - - port@2
> - - port@3
> - - port@4
> - - port@5
> -
> required:
> - compatible
> - reg
> @@ -204,9 +169,86 @@ $defs:
> - data-lanes
> - link-frequencies
>
> +allOf:
> + - $ref: /schemas/i2c/i2c-atr.yaml#
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - ti,ds90ub960-q1
> + - ti,ds90ub9702-q1
> + then:
> + properties:
> + ports:
> + properties:
> + port@0:
> + $ref: '#/$defs/FPDLink-input-port'
> + description: FPD-Link input 0
> +
> + port@1:
> + $ref: '#/$defs/FPDLink-input-port'
> + description: FPD-Link input 1
> +
> + port@2:
> + $ref: '#/$defs/FPDLink-input-port'
> + description: FPD-Link input 2
> +
> + port@3:
> + $ref: '#/$defs/FPDLink-input-port'
> + description: FPD-Link input 3
> +
> + port@4:
> + $ref: '#/$defs/CSI2-output-port'
> + description: CSI-2 Output 0
> +
> + port@5:
> + $ref: '#/$defs/CSI2-output-port'
> + description: CSI-2 Output 1
> +
> + required:
> + - port@0
> + - port@1
> + - port@2
> + - port@3
> + - port@4
> + - port@5
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: ti,ds90ub954-q1
> + then:
> + properties:
> + ports:
> + properties:
> + port@0:
> + $ref: '#/$defs/FPDLink-input-port'
> + description: FPD-Link input 0
> +
> + port@1:
> + $ref: '#/$defs/FPDLink-input-port'
> + description: FPD-Link input 1
> +
> + port@2:
> + $ref: '#/$defs/CSI2-output-port'
> + description: CSI-2 Output 0
Wouldn't making this port@4 be more compatible?
> +
> + required:
> + - port@0
> + - port@1
> + - port@2
> +
> + links:
> + properties:
> + link@2: false
> + link@3: false
> +
> unevaluatedProperties: false
>
> examples:
> + # Example with ds90ub960 Deserializer
> - |
> #include <dt-bindings/gpio/gpio.h>
>
> @@ -406,4 +448,190 @@ examples:
> };
> };
> };
> +
> + # Example with ds90ub954 Deserializer
> + - |
> + #include <dt-bindings/gpio/gpio.h>
I don't think we really need a whole other example for something
that's a subset.
Rob
next prev parent reply other threads:[~2025-12-05 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 10:22 [PATCH V2 0/4] Add support for DS90UB954-Q1 Yemike Abhilash Chandra
2025-12-02 10:22 ` [PATCH V2 1/4] media: dt-bindings: ti,ds90ub960: Refactor port definitions Yemike Abhilash Chandra
2025-12-05 15:11 ` Rob Herring
2025-12-10 9:25 ` Yemike Abhilash Chandra
2025-12-02 10:22 ` [PATCH V2 2/4] media: i2c: ds90ub960: Use enums for chip type and chip family Yemike Abhilash Chandra
2025-12-05 10:46 ` Tomi Valkeinen
2025-12-02 10:22 ` [PATCH V2 3/4] media: dt-bindings: ti,ds90ub960: Add support for DS90UB954-Q1 Yemike Abhilash Chandra
2025-12-05 15:17 ` Rob Herring [this message]
2025-12-10 9:33 ` Yemike Abhilash Chandra
2025-12-02 10:22 ` [PATCH V2 4/4] media: i2c: ds90ub960: " Yemike Abhilash Chandra
2025-12-05 11:10 ` Tomi Valkeinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251205151737.GB158904-robh@kernel.org \
--to=robh@kernel.org \
--cc=benjamin.mugnier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongcheng.yan@intel.com \
--cc=git@apitzsch.eu \
--cc=hansg@kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=jai.luthra@linux.dev \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=u-kumar1@ti.com \
--cc=vladimir.zapolskiy@linaro.org \
--cc=y-abhilashchandra@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).