From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
Cc: 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, mchehab@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
hverkuil@xs4all.nl, sakari.ailus@linux.intel.com,
laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH V3 3/4] media: dt-bindings: ti,ds90ub960: Add support for DS90UB954-Q1
Date: Mon, 22 Dec 2025 13:29:56 +0200 [thread overview]
Message-ID: <07cef607-365f-4c09-a57e-5ddbdfde7027@ideasonboard.com> (raw)
In-Reply-To: <20251219122955.2078270-4-y-abhilashchandra@ti.com>
Hi,
On 19/12/2025 14:29, 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>
> ---
> Changelog:
> Changes in v3:
> - Remove the example added for DS90UB954, as it is just a subset of the DS90UB960 example. (Rob)
>
> .../bindings/media/i2c/ti,ds90ub960.yaml | 113 ++++++++++++------
> 1 file changed, 77 insertions(+), 36 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/ti,ds90ub960.yaml b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub960.yaml
> index cc61604eca37..8e2b82d6dc81 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. The number of ports 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,6 +169,82 @@ $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
> +
> + required:
> + - port@0
> + - port@1
> + - port@2
> +
> + links:
> + properties:
> + link@2: false
> + link@3: false
I can't help but think if this is good or not. In other words, if we
specifically add ports per compatible, why wouldn't we also add
specifically links per compatible? Or, if we just disable links as
above, why don't we do it the same way for ports?
Tomi
next prev parent reply other threads:[~2025-12-22 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 12:29 [PATCH V3 0/4] " Yemike Abhilash Chandra
2025-12-19 12:29 ` [PATCH V3 1/4] media: dt-bindings: ti,ds90ub960: Refactor port definitions Yemike Abhilash Chandra
2025-12-22 10:55 ` Tomi Valkeinen
2025-12-29 23:54 ` Rob Herring (Arm)
2025-12-19 12:29 ` [PATCH V3 2/4] media: i2c: ds90ub960: Use enums for chip type and chip family Yemike Abhilash Chandra
2025-12-22 10:46 ` Tomi Valkeinen
2026-01-06 11:26 ` Jai Luthra
2025-12-19 12:29 ` [PATCH V3 3/4] media: dt-bindings: ti,ds90ub960: Add support for DS90UB954-Q1 Yemike Abhilash Chandra
2025-12-22 11:29 ` Tomi Valkeinen [this message]
2026-01-06 10:06 ` Yemike Abhilash Chandra
2026-01-23 9:54 ` Tomi Valkeinen
2025-12-29 23:58 ` Rob Herring (Arm)
2025-12-19 12:29 ` [PATCH V3 4/4] media: i2c: ds90ub960: " Yemike Abhilash Chandra
2025-12-22 10:46 ` Tomi Valkeinen
2026-01-06 11:34 ` Jai Luthra
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=07cef607-365f-4c09-a57e-5ddbdfde7027@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--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=robh@kernel.org \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®