From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Heiko Stuebner" <heiko@sntech.de>
Cc: <quentin.schulz@cherry.de>, <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/3] arm64: dts: rockchip: add mipi dcphy nodes to rk3588
Date: Wed, 06 Nov 2024 14:43:36 +0100 [thread overview]
Message-ID: <D5F525WYXDO1.3I92CTU67RVF6@cknow.org> (raw)
In-Reply-To: <20241106123758.423584-2-heiko@sntech.de>
[-- Attachment #1: Type: text/plain, Size: 2696 bytes --]
On Wed Nov 6, 2024 at 1:37 PM CET, Heiko Stuebner wrote:
> From: Heiko Stuebner <heiko.stuebner@cherry.de>
>
> Add the two MIPI-DC-phy nodes to the RK3588, that will be used by the
> DSI2 controllers and hopefully in some future also for camera input.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@cherry.de>
> ---
> arch/arm64/boot/dts/rockchip/rk3588-base.dtsi | 42 +++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-base.dtsi b/arch/arm64/boot/dts/rockchip/rk3588-base.dtsi
> index 51ba7563f7d0..8c95c56e8097 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-base.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-base.dtsi
> @@ -576,6 +576,16 @@ sys_grf: syscon@fd58c000 {
> reg = <0x0 0xfd58c000 0x0 0x1000>;
> };
>
> + mipidcphy0_grf: syscon@fd5e8000 {
> + compatible = "rockchip,rk3588-dcphy-grf", "syscon";
> + reg = <0x0 0xfd5e8000 0x0 0x4000>;
> + };
> +
> + mipidcphy1_grf: syscon@fd5ec000 {
> + compatible = "rockchip,rk3588-dcphy-grf", "syscon";
> + reg = <0x0 0xfd5ec000 0x0 0x4000>;
> + };
> +
> vop_grf: syscon@fd5a4000 {
> compatible = "rockchip,rk3588-vop-grf", "syscon";
> reg = <0x0 0xfd5a4000 0x0 0x2000>;
> @@ -2878,6 +2888,38 @@ usbdp_phy0: phy@fed80000 {
> status = "disabled";
> };
>
> + mipidcphy0: phy@feda0000 {
> + compatible = "rockchip,rk3588-mipi-dcphy";
> + reg = <0x0 0xfeda0000 0x0 0x10000>;
> + rockchip,grf = <&mipidcphy0_grf>;
> + clocks = <&cru PCLK_MIPI_DCPHY0>,
> + <&cru CLK_USBDPPHY_MIPIDCPPHY_REF>;
> + clock-names = "pclk", "ref";
> + resets = <&cru SRST_M_MIPI_DCPHY0>,
> + <&cru SRST_P_MIPI_DCPHY0>,
> + <&cru SRST_P_MIPI_DCPHY0_GRF>,
> + <&cru SRST_S_MIPI_DCPHY0>;
> + reset-names = "m_phy", "apb", "grf", "s_phy";
> + #phy-cells = <0>;
> + status = "disabled";
> + };
> +
> + mipidcphy1: phy@fedb0000 {
> + compatible = "rockchip,rk3588-mipi-dcphy";
> + reg = <0x0 0xfedb0000 0x0 0x10000>;
> + rockchip,grf = <&mipidcphy1_grf>;
> + clocks = <&cru PCLK_MIPI_DCPHY1>,
> + <&cru CLK_USBDPPHY_MIPIDCPPHY_REF>;
> + clock-names = "pclk", "ref";
> + resets = <&cru SRST_M_MIPI_DCPHY1>,
> + <&cru SRST_P_MIPI_DCPHY1>,
> + <&cru SRST_P_MIPI_DCPHY1_GRF>,
> + <&cru SRST_S_MIPI_DCPHY1>;
> + reset-names = "m_phy", "apb", "grf", "s_phy";
> + #phy-cells = <0>;
> + status = "disabled";
> + };
No power-domains property?
RK3588 TRM v1.0 part 1 page 1097 has ALIVE(PD_BUS) for
MIPI_DC_PHY0~MIPI_DC_PHY1
Cheers,
Diederik
> +
> combphy0_ps: phy@fee00000 {
> compatible = "rockchip,rk3588-naneng-combphy";
> reg = <0x0 0xfee00000 0x0 0x100>;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-06 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 12:37 [PATCH 0/3] arm64: dts: rockchip: add and enable DSI2 on rk3588 Heiko Stuebner
2024-11-06 12:37 ` [PATCH 1/3] arm64: dts: rockchip: add mipi dcphy nodes to rk3588 Heiko Stuebner
2024-11-06 13:43 ` Diederik de Haas [this message]
2024-11-06 13:56 ` Diederik de Haas
2024-11-06 12:37 ` [PATCH 2/3] arm64: dts: rockchip: add dsi controller nodes on rk3588 Heiko Stuebner
2024-11-06 12:37 ` [PATCH 3/3] arm64: dts: rockchip: add overlay for tiger-haikou video-demo adapter Heiko Stuebner
2024-11-06 13:18 ` Quentin Schulz
2024-11-27 9:46 ` Heiko Stübner
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=D5F525WYXDO1.3I92CTU67RVF6@cknow.org \
--to=didi.debian@cknow.org \
--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 \
--cc=quentin.schulz@cherry.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