devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 17:16:57 +0100	[thread overview]
Message-ID: <3216426.Mh6RI2rZIc@diego> (raw)
In-Reply-To: <f5f3dd36-0f90-47dd-bc12-1e2f0207fe7d@collabora.com>

Am Donnerstag, 6. März 2025, 16:53:48 MEZ schrieb Dmitry Osipenko:
> On 3/6/25 16:06, Heiko Stübner wrote:
> > 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>
> >> ---

> >> +	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?
> 
> HDMI RX controller is a part of the SoC, it's not specific to a
> particular board. If you meaning move it into rock5b.dts, then we
> definitely shouldn't do it. It's like moving PCIe controller node into a
> board DT :)

sorry, should've been clearer. I meant the pinctrl.
There are two sets of pins hdmim0-rx and hdmim1-rx which one is used is
board specific.

Can you check if "most" boards use the M1 variant?

Rationale being, that if we know that most boards use the same set of
pins, it's likely ok to just have the minority boards override it.

Heiko




  reply	other threads:[~2025-03-06 16:17 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
2025-03-06 15:53     ` Dmitry Osipenko
2025-03-06 16:16       ` Heiko Stübner [this message]
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=3216426.Mh6RI2rZIc@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).