From: Detlev Casanova <detlev.casanova@collabora.com>
To: heiko@sntech.de, Andy Yan <andyshrk@163.com>
Cc: krzk+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH v3 1/3] arm64: dts: rockchip: Add vop for rk3576
Date: Tue, 04 Mar 2025 12:15:41 -0500 [thread overview]
Message-ID: <12619358.O9o76ZdvQC@earth> (raw)
In-Reply-To: <20241231095728.253943-2-andyshrk@163.com>
Hi andy,
On Tuesday, 31 December 2024 04:57:18 EST Andy Yan wrote:
> From: Andy Yan <andy.yan@rock-chips.com>
>
> Add VOP and VOP_MMU found on rk3576.
>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>
> ---
>
> Changes in v3:
> - Split from
> https://lore.kernel.org/linux-rockchip/3330586.aeNJFYEL58@diego/T/#t
>
> arch/arm64/boot/dts/rockchip/rk3576.dtsi | 68 ++++++++++++++++++++++++
> 1 file changed, 68 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3576.dtsi
> b/arch/arm64/boot/dts/rockchip/rk3576.dtsi index 436232ffe4d1..130d11a2cc89
> 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3576.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3576.dtsi
> @@ -393,6 +393,11 @@ opp-950000000 {
> };
> };
>
> + display_subsystem: display-subsystem {
> + compatible = "rockchip,display-subsystem";
> + ports = <&vop_out>;
> + };
> +
> firmware {
> scmi: scmi {
> compatible = "arm,scmi-smc";
> @@ -826,6 +831,69 @@ gpu: gpu@27800000 {
> status = "disabled";
> };
>
> + vop: vop@27d00000 {
> + compatible = "rockchip,rk3576-vop";
> + reg = <0x0 0x27d00000 0x0 0x3000>, <0x0 0x27d05000
0x0 0x1000>;
> + reg-names = "vop", "gamma-lut";
> + interrupts = <GIC_SPI 342 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 379 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 380 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 381 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "vop-sys",
> + "vop-vp0",
> + "vop-vp1",
> + "vop-vp2";
These need to be renamed without the 'vop-' prefix.
> + clocks = <&cru ACLK_VOP>,
> + <&cru HCLK_VOP>,
> + <&cru DCLK_VP0>,
> + <&cru DCLK_VP1>,
> + <&cru DCLK_VP2>;
> + clock-names = "aclk",
> + "hclk",
> + "dclk_vp0",
> + "dclk_vp1",
> + "dclk_vp2";
> + iommus = <&vop_mmu>;
> + power-domains = <&power RK3576_PD_VOP>;
> + rockchip,grf = <&sys_grf>;
> + rockchip,pmu = <&pmu>;
> + status = "disabled";
> +
> + vop_out: ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + vp0: port@0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0>;
> + };
> +
> + vp1: port@1 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <1>;
> + };
> +
> + vp2: port@2 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <2>;
> + };
> + };
> + };
> +
> + vop_mmu: iommu@27d07e00 {
> + compatible = "rockchip,rk3576-iommu",
"rockchip,rk3568-iommu";
> + reg = <0x0 0x27d07e00 0x0 0x100>, <0x0 0x27d07f00
0x0 0x100>;
> + interrupts = <GIC_SPI 342 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cru ACLK_VOP>, <&cru HCLK_VOP>;
> + clock-names = "aclk", "iface";
> + #iommu-cells = <0>;
> + power-domains = <&power RK3576_PD_VOP>;
> + status = "disabled";
> + };
> +
> qos_hdcp1: qos@27f02000 {
> compatible = "rockchip,rk3576-qos", "syscon";
> reg = <0x0 0x27f02000 0x0 0x20>;
Regards,
Detlev
next prev parent reply other threads:[~2025-03-04 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 9:57 [PATCH v3 0/3] Add display subsystem dt node on rk3576 Andy Yan
2024-12-31 9:57 ` [PATCH v3 1/3] arm64: dts: rockchip: Add vop for rk3576 Andy Yan
2025-03-04 17:15 ` Detlev Casanova [this message]
2024-12-31 9:57 ` [PATCH v3 2/3] arm64: dts: rockchip: Add hdmi " Andy Yan
2025-03-04 17:17 ` Detlev Casanova
2024-12-31 9:57 ` [PATCH v3 3/3] arm64: dts: rockchip: Enable hdmi display on sige5 Andy Yan
2024-12-31 12:57 ` [PATCH v3 0/3] Add display subsystem dt node on rk3576 Rob Herring (Arm)
2025-03-04 14:47 ` Sebastian Reichel
2025-03-04 21:16 ` Heiko Stübner
2025-03-05 2:55 ` Andy Yan
2025-03-04 21:14 ` Heiko Stuebner
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=12619358.O9o76ZdvQC@earth \
--to=detlev.casanova@collabora.com \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).