From: Quentin Schulz <quentin.schulz@cherry.de>
To: Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: Re: [PATCH 1/2] arm64: dts: rockchip: add HDMI support to rk3588-tiger-haikou
Date: Thu, 24 Oct 2024 15:46:54 +0200 [thread overview]
Message-ID: <1f98c2e8-79e6-4b11-9007-ef2ae1499b5a@cherry.de> (raw)
In-Reply-To: <20241024133240.1737647-1-heiko@sntech.de>
Hi Heiko,
On 10/24/24 3:32 PM, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@cherry.de>
>
> The Haikou baseboard has an hdmi output port, which is connected
> via the Q7 connector to the hdmi0 controller of the rk3588.
>
> Add the necessary plumbing to enable it using the recently merged
> hdmi-qp controller.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@cherry.de>
> ---
> .../boot/dts/rockchip/rk3588-tiger-haikou.dts | 50 +++++++++++++++++++
> 1 file changed, 50 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-tiger-haikou.dts b/arch/arm64/boot/dts/rockchip/rk3588-tiger-haikou.dts
> index e4b7a0a4444b..e3596341b816 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-tiger-haikou.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-tiger-haikou.dts
> @@ -5,6 +5,7 @@
>
> /dts-v1/;
> #include <dt-bindings/input/input.h>
> +#include <dt-bindings/soc/rockchip,vop2.h>
> #include "rk3588-tiger.dtsi"
>
> / {
> @@ -61,6 +62,17 @@ switch-lid-btn-n {
> };
> };
>
> + hdmi-con {
> + compatible = "hdmi-connector";
> + type = "a";
> +
> + port {
> + hdmi_con_in: endpoint {
> + remote-endpoint = <&hdmi0_out_con>;
> + };
> + };
> + };
> +
> i2s3-sound {
> compatible = "simple-audio-card";
> simple-audio-card,format = "i2s";
> @@ -155,6 +167,29 @@ &gmac0 {
> status = "okay";
> };
>
> +&hdmi0 {
> + /* No CEC on Haikou */
> + pinctrl-names = "default";
> + pinctrl-0 = <&hdmim0_tx0_hpd &hdmim1_tx0_scl &hdmim1_tx0_sda>;
The pinctrl for HDMI is fixed on Tiger so we should rather have this in
Tiger DTSI.
Why we have those defined in Haikou as well downstream is because we do
not have CEC routed on Haikou, but it is exposed by Tiger on Q7
connector, so basically, the point is the pinctrl-0 in Haikou is a
subset of the one in Tiger.
So please have the following in rk3588-tiger.dtsi as well:
pinctrl-0 = <&hdmim1_tx0_cec &hdmim0_tx0_hpd &hdmim1_tx0_scl
&hdmim1_tx0_sda>;
It'd be nice to have HDMI audio as well, but one thing after the other I
guess :)
> + status = "okay";
> +};
> +
> +&hdmi0_in {
BTW, I'm not very happy with this naming.
There is an HDMI-RX controller on RK3588 as well, which is routed on
Tiger, so this will be unnecessarily confusing: "which one REALLY is the
HDMI input".
Maybe hdmitx0_in would have made more sense. Anyway, I'm too late to the
party :)
Cheers,
Quentin
prev parent reply other threads:[~2024-10-24 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 13:32 Heiko Stuebner
2024-10-24 13:32 ` [PATCH 2/2] arm64: dts: rockchip: add HDMI support to rk3588-jaguar Heiko Stuebner
2024-10-24 13:46 ` Quentin Schulz [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=1f98c2e8-79e6-4b11-9007-ef2ae1499b5a@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=devicetree@vger.kernel.org \
--cc=heiko.stuebner@cherry.de \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®