From: Hermes Wu via B4 Relay <devnull+Hermes.wu.ite.com.tw@kernel.org>
To: Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Pet.Weng@ite.com.tw, Kenneth.Hung@ite.com.tw,
Hermes Wu <Hermes.Wu@ite.com.tw>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Hermes Wu <Hermes.wu@ite.com.tw>
Subject: [PATCH v4 1/2] dt-bindings: display: bridge: Add ITE IT6162 MIPI DSI to HDMI bridge
Date: Thu, 19 Mar 2026 14:37:11 +0800 [thread overview]
Message-ID: <20260319-upstream-6162-v4-1-7268483ef03d@ite.com.tw> (raw)
In-Reply-To: <20260319-upstream-6162-v4-0-7268483ef03d@ite.com.tw>
From: Hermes Wu <Hermes.wu@ite.com.tw>
Add device tree binding documentation for the ITE IT6162 MIPI DSI to
HDMI 2.0 bridge chip. The IT6162 is an I2C-controlled bridge that
supports the following configurations:
- Single MIPI DSI input: up to 4K @ 30Hz
- Dual MIPI DSI input (combined): up to 4K @ 60Hz
The chip also supports up to 8-channel audio output via 4 I2S data
channels.
Signed-off-by: Hermes Wu <Hermes.wu@ite.com.tw>
---
Changes in v4:
- Drop ite,support-hdcp
- Drop endpoint properties already in video-interfaces.yaml
- Fix data-lanes in example with <0 1 2 3>
- Add blanking line in example before endpoint subnode starts
- Add reset-gpio and power controls to required
Changes in v3:
- Fix lane-polarities: remove $ref redefinition, allow via video-interfaces.yaml
- Improve ite,support-hdcp description to clarify FW-based HDCP behavior
- Remove descriptions repeating schema constraints
- Remove stray comment in ports required section
- Fix data-lanes spacing in example: <1 2 3 4>
- Add missing newline at end of file
- Add missing change log that Reviewed-by tag was drop in V2.
Changes in V2:
- Drop Reviewed-by tag due to DT bindings changed.
- Add property "ite,spport-hdcp" to enable HDCP
- Add property "lane-polarities" and "clock-noncontinuous" for DSI
setting
---
.../bindings/display/bridge/ite,it6162.yaml | 169 +++++++++++++++++++++
1 file changed, 169 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/bridge/ite,it6162.yaml b/Documentation/devicetree/bindings/display/bridge/ite,it6162.yaml
new file mode 100644
index 0000000000000000000000000000000000000000..d1d8a92825d253ecfa67cb1e793d372e4011b4d4
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/ite,it6162.yaml
@@ -0,0 +1,169 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/display/bridge/ite,it6162.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: ITE IT6162 MIPI DSI to HDMI 2.0 Bridge
+
+maintainers:
+ - Hermes Wu <Hermes.Wu@ite.com.tw>
+
+description: |
+ The ITE IT6162 is a high-performance, low-power HDMI bridge that converts
+ 2 MIPI DSI signals to 1 HDMI 2.0 output. It supports dual MIPI D-PHY 2.0
+ links up to 10 Gbps each (20 Gbps total), compatible with DSI-2 v2.0.
+
+ The HDMI transmitter supports resolutions up to 4Kx2K@60Hz and is compliant
+ with HDMI 2.0 specifications.
+
+ For audio, it supports up to 8-channel LPCM via I2S (multi-line or TDM mode),
+ with optional S/PDIF or DSD (for SACD). Audio sampling rates up to 192 kHz
+ are supported.
+
+allOf:
+ - $ref: /schemas/sound/dai-common.yaml#
+
+properties:
+ compatible:
+ const: ite,it6162
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+ reset-gpios:
+ maxItems: 1
+
+ ivdd-supply:
+ description: Core voltage supply
+
+ ovdd-supply:
+ description: I/O voltage supply
+
+ ovdd1833-supply:
+ description: Flexible I/O voltage supply (1.8V domain)
+
+ "#sound-dai-cells":
+ const: 0
+
+ ports:
+ $ref: /schemas/graph.yaml#/properties/ports
+
+ properties:
+ port@0:
+ $ref: /schemas/graph.yaml#/$defs/port-base
+ unevaluatedProperties: false
+ description: Input port for MIPI DSI-0
+
+ properties:
+ endpoint:
+ $ref: /schemas/media/video-interfaces.yaml#
+ unevaluatedProperties: false
+ required:
+ - data-lanes
+
+ port@1:
+ $ref: /schemas/graph.yaml#/$defs/port-base
+ unevaluatedProperties: false
+ description: Input port for MIPI DSI-1
+
+ properties:
+ endpoint:
+ $ref: /schemas/media/video-interfaces.yaml#
+ unevaluatedProperties: false
+ required:
+ - data-lanes
+
+ port@2:
+ $ref: /schemas/graph.yaml#/properties/port
+ description: Audio input port
+
+ port@3:
+ $ref: /schemas/graph.yaml#/properties/port
+ description: HDMI output port
+
+ required:
+ - port@1
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - reset-gpios
+ - ivdd-supply
+ - ovdd-supply
+ - ovdd1833-supply
+ - ports
+
+unevaluatedProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ bridge@58 {
+ compatible = "ite,it6162";
+ reg = <0x58>;
+
+ #sound-dai-cells = <0>;
+
+ interrupt-parent = <&pio>;
+ interrupts = <128 IRQ_TYPE_LEVEL_LOW>;
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&it6162_pins>;
+
+ reset-gpios = <&pio 127 GPIO_ACTIVE_LOW>;
+
+ ivdd-supply = <&pp1000_hdmi_x>;
+ ovdd-supply = <&pp3300_vio28_x>;
+ ovdd1833-supply = <&pp1800_vcamio_x>;
+
+ ports {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ port@0 {
+ reg = <0>;
+
+ it6162_dsi0: endpoint {
+ data-lanes = <0 1 2 3>;
+ remote-endpoint = <&dsi_0_out>;
+ };
+ };
+
+ port@1 {
+ reg = <1>;
+
+ it6162_dsi1: endpoint {
+ data-lanes = <0 1 2 3>;
+ remote-endpoint = <&dsi_1_out>;
+ };
+ };
+
+ port@2 {
+ reg = <2>;
+
+ it6162_audio_in: endpoint {
+ remote-endpoint = <&i2s0_out>;
+ };
+ };
+
+ port@3 {
+ reg = <3>;
+
+ it6162_hdmi_out: endpoint {
+ remote-endpoint = <&hdmi_connector_in>;
+ };
+ };
+ };
+ };
+ };
--
2.34.1
next prev parent reply other threads:[~2026-03-19 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 6:37 [PATCH v4 0/2] Add ITE IT6162 MIPI DSI to HDMI bridge driver Hermes Wu via B4 Relay
2026-03-19 6:37 ` Hermes Wu via B4 Relay [this message]
2026-03-19 8:56 ` [PATCH v4 1/2] dt-bindings: display: bridge: Add ITE IT6162 MIPI DSI to HDMI bridge Krzysztof Kozlowski
2026-03-21 18:39 ` Claude review: " Claude Code Review Bot
2026-03-19 6:37 ` [PATCH v4 2/2] drm/bridge: Add ITE IT6162 MIPI DSI to HDMI bridge driver Hermes Wu via B4 Relay
2026-03-21 18:39 ` Claude review: " Claude Code Review Bot
2026-03-21 18:39 ` Claude review: " Claude Code Review 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=20260319-upstream-6162-v4-1-7268483ef03d@ite.com.tw \
--to=devnull+hermes.wu.ite.com.tw@kernel.org \
--cc=Hermes.Wu@ite.com.tw \
--cc=Kenneth.Hung@ite.com.tw \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Pet.Weng@ite.com.tw \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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