From: "Heiko Stübner" <heiko@sntech.de>
To: Shreeya Patel <shreeya.patel@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
jose.abreu@synopsys.com, nelson.costa@synopsys.com,
shawn.wen@rock-chips.com, nicolas.dufresne@collabora.com,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>
Cc: kernel@collabora.com, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, Tim Surber <me@timsurber.de>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Diederik de Haas <didi.debian@cknow.org>
Subject: Re: [PATCH v14 1/3] arm64: dts: rockchip: Add device tree support for HDMI RX Controller
Date: Thu, 06 Mar 2025 14:06:40 +0100 [thread overview]
Message-ID: <9489391.T7Z3S40VBb@diego> (raw)
In-Reply-To: <20250306072842.287142-2-dmitry.osipenko@collabora.com>
Hi Dmitry,
Am Donnerstag, 6. März 2025, 08:28:40 MEZ schrieb Dmitry Osipenko:
> From: Shreeya Patel <shreeya.patel@collabora.com>
>
> Add device tree support for Synopsys DesignWare HDMI RX
> Controller.
>
> Reviewed-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> Tested-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> Co-developed-by: Dingxian Wen <shawn.wen@rock-chips.com>
> Signed-off-by: Dingxian Wen <shawn.wen@rock-chips.com>
> Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com>
> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> ---
> .../dts/rockchip/rk3588-base-pinctrl.dtsi | 14 +++++
> .../arm64/boot/dts/rockchip/rk3588-extra.dtsi | 57 +++++++++++++++++++
> 2 files changed, 71 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-base-pinctrl.dtsi b/arch/arm64/boot/dts/rockchip/rk3588-base-pinctrl.dtsi
> index 7f874c77410c..2d4b9986a177 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-base-pinctrl.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-base-pinctrl.dtsi
> @@ -594,6 +594,20 @@ hdmim0_tx1_hpd: hdmim0-tx1-hpd {
> /* hdmim0_tx1_hpd */
> <1 RK_PA6 5 &pcfg_pull_none>;
> };
> +
> + /omit-if-no-ref/
> + hdmim1_rx: hdmim1-rx {
> + rockchip,pins =
> + /* hdmim1_rx_cec */
> + <3 RK_PD1 5 &pcfg_pull_none>,
> + /* hdmim1_rx_scl */
> + <3 RK_PD2 5 &pcfg_pull_none_smt>,
> + /* hdmim1_rx_sda */
> + <3 RK_PD3 5 &pcfg_pull_none_smt>,
> + /* hdmim1_rx_hpdin */
> + <3 RK_PD4 5 &pcfg_pull_none>;
> + };
> +
what's the reason for duplicating these pinctrl entries?
The base-pinctrl already contains a separate set of pins (and also a
variant for the m0 set of pins), so why not check and use the already
existing ones:
hdmim1_rx_cec: hdmim1-rx-cec {
rockchip,pins =
/* hdmim1_rx_cec */
<3 RK_PD1 5 &pcfg_pull_none>;
};
hdmim1_rx_hpdin: hdmim1-rx-hpdin {
rockchip,pins =
/* hdmim1_rx_hpdin */
<3 RK_PD4 5 &pcfg_pull_none>;
};
hdmim1_rx_scl: hdmim1-rx-scl {
rockchip,pins =
/* hdmim1_rx_scl */
<3 RK_PD2 5 &pcfg_pull_none>;
};
hdmim1_rx_sda: hdmim1-rx-sda {
rockchip,pins =
/* hdmim1_rx_sda */
<3 RK_PD3 5 &pcfg_pull_none>;
};
Having multiple sets (even with differeing settings) will cause confusion
later on.
> /omit-if-no-ref/
> hdmim1_rx_cec: hdmim1-rx-cec {
> rockchip,pins =
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi b/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi
> index 4a950907ea6f..b7d06f93c8ce 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi
> @@ -135,6 +159,39 @@ i2s10_8ch: i2s@fde00000 {
> status = "disabled";
> };
>
> + hdmi_receiver: hdmi_receiver@fdee0000 {
> + compatible = "rockchip,rk3588-hdmirx-ctrler", "snps,dw-hdmi-rx";
> + reg = <0x0 0xfdee0000 0x0 0x6000>;
> + power-domains = <&power RK3588_PD_VO1>;
> + rockchip,grf = <&sys_grf>;
> + rockchip,vo1-grf = <&vo1_grf>;
> + interrupts = <GIC_SPI 177 IRQ_TYPE_LEVEL_HIGH 0>,
> + <GIC_SPI 178 IRQ_TYPE_LEVEL_HIGH 0>,
> + <GIC_SPI 179 IRQ_TYPE_LEVEL_HIGH 0>;
> + interrupt-names = "cec", "hdmi", "dma";
> + clocks = <&cru ACLK_HDMIRX>,
> + <&cru CLK_HDMIRX_AUD>,
> + <&cru CLK_CR_PARA>,
> + <&cru PCLK_HDMIRX>,
> + <&cru CLK_HDMIRX_REF>,
> + <&cru PCLK_S_HDMIRX>,
> + <&cru HCLK_VO1>;
> + clock-names = "aclk",
> + "audio",
> + "cr_para",
> + "pclk",
> + "ref",
> + "hclk_s_hdmirx",
> + "hclk_vo1";
> + resets = <&cru SRST_A_HDMIRX>, <&cru SRST_P_HDMIRX>,
> + <&cru SRST_HDMIRX_REF>, <&cru SRST_A_HDMIRX_BIU>;
> + reset-names = "axi", "apb", "ref", "biu";
> + memory-region = <&hdmi_receiver_cma>;
> + pinctrl-0 = <&hdmim1_rx>;
> + pinctrl-names = "default";
hmm, this might be better living in the board dts?
Heiko
next prev parent reply other threads:[~2025-03-06 13:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 7:28 [PATCH v14 0/3] Enable HDMI RX controller on RK3588 Dmitry Osipenko
2025-03-06 7:28 ` [PATCH v14 1/3] arm64: dts: rockchip: Add device tree support for HDMI RX Controller Dmitry Osipenko
2025-03-06 13:06 ` Heiko Stübner [this message]
2025-03-06 15:53 ` Dmitry Osipenko
2025-03-06 16:16 ` Heiko Stübner
2025-03-06 16:24 ` Dmitry Osipenko
2025-03-06 7:28 ` [PATCH v14 2/3] arm64: dts: rockchip: Enable HDMI receiver on rock-5b Dmitry Osipenko
2025-03-06 13:07 ` Heiko Stübner
2025-03-06 7:28 ` [PATCH v14 3/3] arm64: defconfig: Enable Synopsys HDMI receiver Dmitry Osipenko
2025-03-06 9:26 ` [PATCH v14 0/3] Enable HDMI RX controller on RK3588 Heiko Stübner
2025-03-06 9:41 ` Hans Verkuil
2025-03-06 9:44 ` Heiko Stübner
2025-03-06 13:09 ` (subset) " Heiko Stuebner
2025-03-06 17:47 ` Rob Herring (Arm)
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=9489391.T7Z3S40VBb@diego \
--to=heiko@sntech.de \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=dmitry.osipenko@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=jose.abreu@synopsys.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=me@timsurber.de \
--cc=nelson.costa@synopsys.com \
--cc=nicolas.dufresne@collabora.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=shawn.wen@rock-chips.com \
--cc=shreeya.patel@collabora.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;
as well as URLs for NNTP newsgroup(s).