From: "Kumar, Udit" <u-kumar1@ti.com>
To: Swamil Jain <s-jain1@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <tomi.valkeinen@ideasonboard.com>
Cc: <devarsht@ti.com>, <praneeth@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<u-kumar1@ti.com>
Subject: Re: [PATCH v4 2/2] arm64: dts: ti: k3-am62l3-evm: Add HDMI support
Date: Sun, 6 Sep 2026 19:14:34 +0530 [thread overview]
Message-ID: <d2c7a82f-0121-4f30-abad-dd8032fc5106@ti.com> (raw)
In-Reply-To: <20260811130822.2324438-3-s-jain1@ti.com>
On 8/11/2026 6:38 PM, Swamil Jain wrote:
> From: Devarsh Thakkar <devarsht@ti.com>
>
> Add the SII9022 HDMI bridge and HDMI connector nodes, along with the
> DPI pinmux configuration connecting VOUT0 to the bridge. Enable the DSS
> and hook up its DPI output port to the SII9022 bridge input, and the
> bridge output to the HDMI connector.
>
> Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
> Signed-off-by: Swamil Jain <s-jain1@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am62l3-evm.dts | 95 ++++++++++++++++++++++++
> 1 file changed, 95 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62l3-evm.dts b/arch/arm64/boot/dts/ti/k3-am62l3-evm.dts
> index 84a0cfaaf196..477de9de07e8 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62l3-evm.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am62l3-evm.dts
> @@ -44,6 +44,18 @@ usr: button-usr {
> };
> };
>
> + hdmi0: connector-hdmi {
> + compatible = "hdmi-connector";
> + label = "hdmi";
> + type = "a";
> +
> + port {
> + hdmi_connector_in: endpoint {
> + remote-endpoint = <&sii9022_out>;
> + };
> + };
> + };
> +
> leds {
> compatible = "gpio-leds";
> pinctrl-names = "default";
> @@ -192,6 +204,38 @@ exp2: gpio@23 {
> bootph-all;
> };
>
> + sii9022: bridge-hdmi@3b {
> + compatible = "sil,sii9022";
> + reg = <0x3b>;
> + interrupt-parent = <&exp1>;
> + interrupts = <20 IRQ_TYPE_EDGE_FALLING>;
> + #sound-dai-cells = <0>;
> + sil,i2s-data-lanes = < 0 >;
> + pinctrl-names = "default";
> + pinctrl-0 = <&dpi_pins_default>;
I think, dss is right place for pin mux, similar to
https://elixir.bootlin.com/linux/v7.2.2/source/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board-infotainment.dtso#L153
> + bootph-all;
> +
[..]
next prev parent reply other threads:[~2026-09-06 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 13:08 [PATCH v4 0/2] Add DSS support for AM62L SoC Swamil Jain
2026-08-11 13:08 ` [PATCH v4 1/2] arm64: dts: ti: k3-am62l-main: Add DSS & DSI related nodes Swamil Jain
2026-08-11 13:08 ` [PATCH v4 2/2] arm64: dts: ti: k3-am62l3-evm: Add HDMI support Swamil Jain
2026-09-06 13:44 ` Kumar, Udit [this message]
2026-08-21 9:02 ` [PATCH v4 0/2] Add DSS support for AM62L SoC Tomi Valkeinen
2026-09-03 9:16 ` Swamil Jain
2026-09-06 13:38 ` Kumar, Udit
2026-09-13 15:04 ` Swamil Jain
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=d2c7a82f-0121-4f30-abad-dd8032fc5106@ti.com \
--to=u-kumar1@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=s-jain1@ti.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=vigneshr@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