From: sashiko-bot@kernel.org
To: "Hermes Wu" <Hermes.wu@ite.com.tw>
Cc: robh@kernel.org, devicetree@vger.kernel.org,
media-ci@linuxtv.org, conor+dt@kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: media: add ITE IT6625/IT6626 HDMI bridge binding
Date: Wed, 22 Jul 2026 11:25:15 +0000 [thread overview]
Message-ID: <20260722112516.546351F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260722-upstream-it6625-it6626-v6-1-6117d4d96574@ite.com.tw>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The device tree binding intentionally omits the HDMI input port, violating the fundamental rule that Device Tree describes the physical hardware independent of driver implementation.
--
--- Patch [1]: [PATCH v6 1/2] dt-bindings: media: add ITE IT6625/IT6626 HDMI bridge binding ---
commit e9e6db2f5d5e1b4ac21c4df62354e0ec71117d3a
Author: Hermes Wu <Hermes.wu@ite.com.tw>
dt-bindings: media: add ITE IT6625/IT6626 HDMI bridge binding
This commit documents the devicetree binding for the ITE IT6625/IT6626 HDMI
to MIPI CSI-2 bridge. It exposes two selectable CSI-2 output graph ports,
port@0 and port@1.
> diff --git a/Documentation/devicetree/bindings/media/i2c/ite,it6625.yaml b/Documentation/devicetree/bindings/media/i2c/ite,it6625.yaml
> new file mode 100644
> index 0000000000000..fed732e4428ba
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/ite,it6625.yaml
[ ... ]
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> + properties:
> + port@0:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + unevaluatedProperties: false
> + description: CSI-2 output port MIPI0
[Severity: Medium]
The commit message mentions dropping the HDMI input graph port because the
driver does not use it. Does omitting this input port conflict with the
principle that devicetree schemas should describe the physical hardware
independent of driver implementation?
Because the physical hardware acts as an HDMI bridge, device tree authors
would need a documented port index under properties.ports to accurately link
an upstream HDMI source to the bridge.
Without an explicitly defined input port, will this prevent boards from
accurately describing their video graph topology, potentially leading to
inconsistent or missing routing connections across different devices?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260722-upstream-it6625-it6626-v6-0-6117d4d96574@ite.com.tw?part=1
next prev parent reply other threads:[~2026-07-22 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 11:18 [PATCH v6 0/2] media: i2c: add support for ITE IT6625/IT6626 HDMI to MIPI CSI-2 bridge Hermes Wu via B4 Relay
2026-07-22 11:18 ` Hermes Wu
2026-07-22 11:18 ` [PATCH v6 1/2] dt-bindings: media: add ITE IT6625/IT6626 HDMI bridge binding Hermes Wu via B4 Relay
2026-07-22 11:18 ` Hermes Wu
2026-07-22 11:25 ` sashiko-bot [this message]
2026-07-22 11:18 ` [PATCH v6 2/2] media: i2c: add driver for ITE IT6625/IT6626 Hermes Wu via B4 Relay
2026-07-22 11:18 ` Hermes Wu
2026-07-22 11:31 ` sashiko-bot
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=20260722112516.546351F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Hermes.wu@ite.com.tw \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=media-ci@linuxtv.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.