From: Chris Morgan <macroalpha82@gmail.com>
To: Jimmy Hon <honyuenkwun@gmail.com>
Cc: linux-rockchip@lists.infradead.org, "Heiko Stübner" <heiko@sntech.de>
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Enable HDMI0 and GPU on Indiedroid Nova
Date: Tue, 29 Oct 2024 15:27:22 -0500 [thread overview]
Message-ID: <6721452c.4a0a0220.38161e.8f5c@mx.google.com> (raw)
In-Reply-To: <20241024011454.1611-1-honyuenkwun@gmail.com>
On Wed, Oct 23, 2024 at 08:14:54PM -0500, Jimmy Hon wrote:
> >+ hdmi0-con {
> >+ compatible = "hdmi-connector";
> >+ type = "c";
> This should be type d, the Nova has a micro HDMI port, not a mini HDMI port.
>
>
> >+
> >+&hdmi0 {
> >+ pinctrl-0 = <&hdmim0_rx_hpdin>, <&hdmim0_tx0_scl>,
> >+ <&hdmim0_tx0_sda>, <&hdmim0_tx0_hpd>,
> >+ <&hdmim0_tx0_cec>;
> >+ pinctrl-names = "default";
> >+ status = "okay";
> >+};
> Why is the additional hdmim0_rx_hpdin needed? Is it supposed to represent
> HDMI0_TX_ON_H? I'm curious why this board needs it, when the other boards
> do not.
>
> Jimmy
>
You are correct about the port type, it is type d not type c.
As for the HDMI0_TX_ON_H, that pin is hooked up per the schematic so I
thought it prudent to define it in the device tree as such (this being
one of the very few boards I get to work on with actual schematics).
Thank you,
Chris
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2024-10-29 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 16:41 [PATCH 0/2] Indiedroid Nova Audio/HDMI Updates Chris Morgan
2024-10-23 16:41 ` [PATCH 1/2] arm64: dts: rockchip: correct analog audio name on Indiedroid Nova Chris Morgan
2024-10-23 16:41 ` [PATCH 2/2] arm64: dts: rockchip: Enable HDMI0 and GPU " Chris Morgan
2024-10-23 19:43 ` Heiko Stübner
2024-10-24 1:14 ` Jimmy Hon
2024-10-29 20:27 ` Chris Morgan [this message]
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=6721452c.4a0a0220.38161e.8f5c@mx.google.com \
--to=macroalpha82@gmail.com \
--cc=heiko@sntech.de \
--cc=honyuenkwun@gmail.com \
--cc=linux-rockchip@lists.infradead.org \
/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