From: Pet Weng <pet.weng@ite.com.tw>
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>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Hermes Wu <hermes.Wu@ite.com.tw>,
Kenneth Hung <kenneth.Hung@ite.com.tw>,
Pet Weng <pet.weng@ite.com.tw>,
Jau-chih Tseng <jau-chih.tseng@ite.com.tw>,
Pin-yen Lin <treapking@google.com>
Subject: [PATCH v8 1/2] dt-binding: display: Add ITE IT61620 MIPI DSI to HDMI bridge
Date: Fri, 20 Mar 2026 15:50:41 +0800 [thread overview]
Message-ID: <20260320-it61620-0714-v8-1-0e70271cf5a9@ite.com.tw> (raw)
In-Reply-To: <20260320-it61620-0714-v8-0-0e70271cf5a9@ite.com.tw>
This chip receives MIPI DSI input and outputs HDMI, and is commonly
connected to SoCs via I2C and DSI.
IT61620 is a variant of IT6162.
The main differences are listed below
- IT61620 supports only a single MIPI DSI input port, while IT6162 supports
dual MIPI DSI ports.
- IT61620 does not include the internal MCU present in IT6162.
Because of these architectural differences, IT61620 uses a separate compatible
string even though the external interfaces and bindings are largely similar.
Signed-off-by: Pet Weng <pet.weng@ite.com.tw>
---
.../bindings/display/bridge/ite,it61620.yaml | 151 +++++++++++++++++++++
1 file changed, 151 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/bridge/ite,it61620.yaml b/Documentation/devicetree/bindings/display/bridge/ite,it61620.yaml
new file mode 100644
index 0000000000000000000000000000000000000000..8cbab1b55da9e9155dce9cf91addb8fb89382e07
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/bridge/ite,it61620.yaml
@@ -0,0 +1,151 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/display/bridge/ite,it61620.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: ITE IT61620 MIPI DSI to HDMI Bridge
+
+maintainers:
+ - Pet Weng <pet.weng@ite.com.tw>
+
+description: |
+ The ITE IT61620 is a high-performance, low-power HDMI bridge that converts
+ MIPI DSI input to HDMI 1.4b TMDS output. It supports up to 4 lanes of MIPI
+ D-PHY 2.0 input at 2.5Gbps per lane (10Gbps total), compatible with DSI-2
+ v2.0.
+
+ The HDMI transmitter side supports up to 4Kx2K@30Hz resolutions, and is
+ compliant with HDMI 1.4b and HDCP 1.4.
+
+ For audio, the IT61620 supports up to 8-channel LPCM via I2S (multi-line or
+ TDM mode), with optional S/PDIF or DSD (for SACD). It supports audio
+ sampling rates up to 192kHz.
+
+ IT61620 is a variant of IT6162.
+ The main differences are listed below
+ - IT61620 supports only a single MIPI DSI input port, while IT6162 supports
+ dual MIPI DSI ports.
+ - IT61620 does not include the internal MCU present in IT6162.
+
+ Because of these architectural differences, IT61620 uses a separate compatible
+ string even though the external interfaces and bindings are largely similar.
+
+allOf:
+ - $ref: /schemas/sound/dai-common.yaml#
+
+properties:
+ compatible:
+ const: ite,it61620
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+ reset-gpios:
+ maxItems: 1
+
+ ivdd-supply:
+ description: core voltage
+
+ ovdd-supply:
+ description: I/O voltage
+
+ ovdd1833-supply:
+ description: flexible I/O voltage
+
+ "#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
+
+ properties:
+ endpoint:
+ $ref: /schemas/media/video-interfaces.yaml#
+ unevaluatedProperties: false
+ required:
+ - data-lanes
+
+ port@1:
+ $ref: /schemas/graph.yaml#/properties/port
+ description: Output port for HDMI output
+
+ port@2:
+ $ref: /schemas/graph.yaml#/properties/port
+ description: Audio input port (I2S)
+
+ required:
+ - port@0
+ - 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,it61620";
+ reg = <0x58>;
+ #sound-dai-cells = <0>;
+ interrupt-parent = <&pio>;
+ interrupts = <128 IRQ_TYPE_LEVEL_LOW>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&it61620_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>;
+ it61620_dsi_in: endpoint {
+ data-lanes = <0 1 2 3>;
+ remote-endpoint = <&dsi_out>;
+ };
+ };
+
+ port@1 {
+ reg = <1>;
+ it61620_hdmi_out: endpoint {
+ remote-endpoint = <&hdmi_connector_in>;
+ };
+ };
+
+ port@2 {
+ reg = <2>;
+ it61620_audio_in: endpoint {
+ remote-endpoint = <&i2s0_out>;
+ };
+ };
+ };
+ };
+ };
--
2.34.1
next prev parent reply other threads:[~2026-03-20 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 7:50 [PATCH v8 0/2] Add ITE IT61620 MIPI DSI to HDMI bridge driver Pet Weng
2026-03-20 7:50 ` Pet Weng [this message]
2026-03-21 10:10 ` [PATCH v8 1/2] dt-binding: display: Add ITE IT61620 MIPI DSI to HDMI bridge Krzysztof Kozlowski
2026-03-21 17:53 ` Claude review: " Claude Code Review Bot
2026-03-20 7:50 ` [PATCH v8 2/2] drm/bridge: Add ITE IT61620 MIPI DSI to HDMI bridge driver Pet Weng
2026-03-21 17:53 ` Claude review: " Claude Code Review Bot
2026-03-21 10:08 ` [PATCH v8 0/2] " Krzysztof Kozlowski
2026-03-21 17:53 ` 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=20260320-it61620-0714-v8-1-0e70271cf5a9@ite.com.tw \
--to=pet.weng@ite.com.tw \
--cc=Laurent.pinchart@ideasonboard.com \
--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=hermes.Wu@ite.com.tw \
--cc=jau-chih.tseng@ite.com.tw \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kenneth.Hung@ite.com.tw \
--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=treapking@google.com \
--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