From: Heiko Stuebner <heiko@sntech.de>
To: heiko@sntech.de
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, quentin.schulz@cherry.de,
andy.yan@rock-chips.com, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
cn.liweihao@gmail.com, Heiko Stuebner <heiko.stuebner@cherry.de>
Subject: [PATCH 4/9] arm64: dts: rockchip: Add power-domain to RK3368 DSI controller
Date: Mon, 20 Oct 2025 10:25:03 +0200 [thread overview]
Message-ID: <20251020082508.3636511-5-heiko@sntech.de> (raw)
In-Reply-To: <20251020082508.3636511-1-heiko@sntech.de>
From: Heiko Stuebner <heiko.stuebner@cherry.de>
The DSI controller is also part of the VIO power-domain and it
definitly needs to be on when accessing it to no cause SError
faults, so add the power-domain property to it.
Fixes: 5023d0cd6183 ("arm64: dts: rockchip: Add DSI for RK3368")
Signed-off-by: Heiko Stuebner <heiko.stuebner@cherry.de>
---
arch/arm64/boot/dts/rockchip/rk3368.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3368.dtsi b/arch/arm64/boot/dts/rockchip/rk3368.dtsi
index 8f0216203241..5b2cbb3003b6 100644
--- a/arch/arm64/boot/dts/rockchip/rk3368.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3368.dtsi
@@ -896,6 +896,7 @@ mipi_dsi: dsi@ff960000 {
clock-names = "pclk";
phys = <&dphy>;
phy-names = "dphy";
+ power-domains = <&power RK3368_PD_VIO>;
resets = <&cru SRST_MIPIDSI0>;
reset-names = "apb";
rockchip,grf = <&grf>;
--
2.47.2
next prev parent reply other threads:[~2025-10-20 8:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 8:24 [PATCH 0/9] Gernal RK3368 HDMI support and 2 outputs for RK3368-Lion Heiko Stuebner
2025-10-20 8:25 ` [PATCH 1/9] dt-bindings: display: rockchip: dw-hdmi: Add compatible for RK3368 HDMI Heiko Stuebner
2025-10-20 17:18 ` Conor Dooley
2025-10-20 8:25 ` [PATCH 2/9] drm/rockchip: hdmi: add RK3368 controller variant Heiko Stuebner
2025-10-20 8:25 ` [PATCH 3/9] soc: rockchip: grf: Add select correct PWM implementation on RK3368 Heiko Stuebner
2025-10-20 8:25 ` Heiko Stuebner [this message]
2025-10-20 8:25 ` [PATCH 5/9] arm64: dts: rockchip: Add power-domain to RK3368 VOP controller Heiko Stuebner
2025-10-20 8:25 ` [PATCH 6/9] arm64: dts: rockchip: Use phandle for i2c_lvds_blc on rk3368-lion haikou Heiko Stuebner
2025-10-20 8:25 ` [PATCH 7/9] arm64: dts: rockchip: Add HDMI node to RK3368 Heiko Stuebner
2025-10-20 8:25 ` [PATCH 8/9] arm64: dts: rockchip: Enable HDMI output on RK3368-Lion-Haikou Heiko Stuebner
2025-10-20 8:25 ` [PATCH 9/9] arm64: dts: rockchip: Add the Video-Demo overlay for Lion Haikou Heiko Stuebner
2025-10-20 10:23 ` [PATCH 0/9] Gernal RK3368 HDMI support and 2 outputs for RK3368-Lion Diederik de Haas
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=20251020082508.3636511-5-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=cn.liweihao@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko.stuebner@cherry.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=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
--cc=tzimmermann@suse.de \
/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