All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Damon Ding" <damon.ding@rock-chips.com>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org, vkoul@kernel.org,
	neil.armstrong@linaro.org, olteanv@gmail.com
Subject: Re: [PATCH v6 3/4] arm64: dts: rockchip: rk356x: Add eDP controller and phy nodes
Date: Sat, 14 Nov 2026 08:55:19 +0000	[thread overview]
Message-ID: <sashiko-outbox-214312@kernel.org> (raw)
In-Reply-To: <20261114083339.600986-4-damon.ding@rock-chips.com>

Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [Medium] arm64: dts: rockchip: rk3568-edp lacks binding/driver match
  and rockchip,grf
- [Low] arm64: dts: rockchip: rk356x: duplicate PCLK_EDPPHY_GRF clock in
  edp_phy_grf
--

commit f7a9ae47dd93488d5a85b663ab5846186e851cbe
Author: Damon Ding <damon.ding@rock-chips.com>

arm64: dts: rockchip: rk356x: Add eDP controller and phy nodes

This commit adds the eDP PHY GRF syscon, child eDP PHY, and eDP
controller device tree nodes to rk356x-base.dtsi for RK3566 and RK3568.

> diff --git a/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi b/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> index 1a4562df20ee5..e3f370cad5d51 100644
> --- a/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> @@ -402,6 +402,24 @@ usb2phy1_grf: syscon@fdca8000 {
>  		reg = <0x0 0xfdca8000 0x0 0x8000>;
>  	};
>  
> +	edp_phy_grf: syscon@fdcb0000 {
> +		compatible = "rockchip,rk3568-edp-phy-grf", "syscon", "simple-mfd";
> +		reg = <0x0 0xfdcb0000 0x0 0x8000>;
> +		clocks = <&cru PCLK_EDPPHY_GRF>;
> +		ranges = <0x0 0x0 0xfdcb0000 0x100>;
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +
> +		edp_phy: phy@0 {
> +			compatible = "rockchip,rk3568-edp-phy";
> +			reg = <0x0 0x100>;
> +			clocks = <&pmucru XIN_OSC0_EDPPHY_G>, <&cru PCLK_EDPPHY_GRF>;
> +			clock-names = "ref", "apb";

[Severity: Low]
Should clocks = <&cru PCLK_EDPPHY_GRF> be removed from the parent
edp_phy_grf node (and from rockchip,rk3568-edp-phy-grf.yaml)?

The changelog states that PCLK_EDPPHY_GRF was moved from the parent
syscon node to the child PHY node, and rockchip_edp_phy_probe() maps its
own MMIO window and enables the "apb" clock directly on edp_phy without
using the parent syscon.

[ ... ]

> @@ -878,6 +896,33 @@ hdmi_out: port@1 {
>  		};
>  	};
>  
> +	edp: edp@fe0c0000 {
> +		compatible = "rockchip,rk3568-edp";
> +		reg = <0x0 0xfe0c0000 0x0 0x10000>;
> +		clocks = <&pmucru XIN_OSC0_EDPPHY_G>, <&cru PCLK_EDP_CTRL>, <&cru HCLK_VO>;
> +		clock-names = "dp", "pclk", "hclk";
> +		interrupts = <GIC_SPI 18 IRQ_TYPE_LEVEL_HIGH>;
> +		phys = <&edp_phy>;
> +		phy-names = "dp";
> +		power-domains = <&power RK3568_PD_VO>;
> +		resets = <&cru SRST_EDP_24M>, <&cru SRST_P_EDP_CTRL>;
> +		reset-names = "dp", "apb";
> +		status = "disabled";

[Severity: Medium]
Can the edp node pass dtbs_check or probe when enabled on a board?

"rockchip,rk3568-edp" is not documented in
Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
or matched by rockchip_dp_dt_ids[] in
drivers/gpu/drm/rockchip/analogix_dp-rockchip.c.  In addition, the node
omits the required rockchip,grf property, which causes
rockchip_dp_of_probe() -> syscon_regmap_lookup_by_phandle(np,
"rockchip,grf") to fail with -ENODEV.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261114083339.600986-1-damon.ding@rock-chips.com?part=3

WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Damon Ding" <damon.ding@rock-chips.com>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org, vkoul@kernel.org,
	neil.armstrong@linaro.org, olteanv@gmail.com
Subject: Re: [PATCH v6 3/4] arm64: dts: rockchip: rk356x: Add eDP controller and phy nodes
Date: Sat, 14 Nov 2026 08:55:19 +0000	[thread overview]
Message-ID: <sashiko-outbox-214312@kernel.org> (raw)
In-Reply-To: <20261114083339.600986-4-damon.ding@rock-chips.com>

Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [Medium] arm64: dts: rockchip: rk3568-edp lacks binding/driver match
  and rockchip,grf
- [Low] arm64: dts: rockchip: rk356x: duplicate PCLK_EDPPHY_GRF clock in
  edp_phy_grf
--

commit f7a9ae47dd93488d5a85b663ab5846186e851cbe
Author: Damon Ding <damon.ding@rock-chips.com>

arm64: dts: rockchip: rk356x: Add eDP controller and phy nodes

This commit adds the eDP PHY GRF syscon, child eDP PHY, and eDP
controller device tree nodes to rk356x-base.dtsi for RK3566 and RK3568.

> diff --git a/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi b/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> index 1a4562df20ee5..e3f370cad5d51 100644
> --- a/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> @@ -402,6 +402,24 @@ usb2phy1_grf: syscon@fdca8000 {
>  		reg = <0x0 0xfdca8000 0x0 0x8000>;
>  	};
>  
> +	edp_phy_grf: syscon@fdcb0000 {
> +		compatible = "rockchip,rk3568-edp-phy-grf", "syscon", "simple-mfd";
> +		reg = <0x0 0xfdcb0000 0x0 0x8000>;
> +		clocks = <&cru PCLK_EDPPHY_GRF>;
> +		ranges = <0x0 0x0 0xfdcb0000 0x100>;
> +		#address-cells = <1>;
> +		#size-cells = <1>;
> +
> +		edp_phy: phy@0 {
> +			compatible = "rockchip,rk3568-edp-phy";
> +			reg = <0x0 0x100>;
> +			clocks = <&pmucru XIN_OSC0_EDPPHY_G>, <&cru PCLK_EDPPHY_GRF>;
> +			clock-names = "ref", "apb";

[Severity: Low]
Should clocks = <&cru PCLK_EDPPHY_GRF> be removed from the parent
edp_phy_grf node (and from rockchip,rk3568-edp-phy-grf.yaml)?

The changelog states that PCLK_EDPPHY_GRF was moved from the parent
syscon node to the child PHY node, and rockchip_edp_phy_probe() maps its
own MMIO window and enables the "apb" clock directly on edp_phy without
using the parent syscon.

[ ... ]

> @@ -878,6 +896,33 @@ hdmi_out: port@1 {
>  		};
>  	};
>  
> +	edp: edp@fe0c0000 {
> +		compatible = "rockchip,rk3568-edp";
> +		reg = <0x0 0xfe0c0000 0x0 0x10000>;
> +		clocks = <&pmucru XIN_OSC0_EDPPHY_G>, <&cru PCLK_EDP_CTRL>, <&cru HCLK_VO>;
> +		clock-names = "dp", "pclk", "hclk";
> +		interrupts = <GIC_SPI 18 IRQ_TYPE_LEVEL_HIGH>;
> +		phys = <&edp_phy>;
> +		phy-names = "dp";
> +		power-domains = <&power RK3568_PD_VO>;
> +		resets = <&cru SRST_EDP_24M>, <&cru SRST_P_EDP_CTRL>;
> +		reset-names = "dp", "apb";
> +		status = "disabled";

[Severity: Medium]
Can the edp node pass dtbs_check or probe when enabled on a board?

"rockchip,rk3568-edp" is not documented in
Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
or matched by rockchip_dp_dt_ids[] in
drivers/gpu/drm/rockchip/analogix_dp-rockchip.c.  In addition, the node
omits the required rockchip,grf property, which causes
rockchip_dp_of_probe() -> syscon_regmap_lookup_by_phandle(np,
"rockchip,grf") to fail with -ENODEV.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261114083339.600986-1-damon.ding@rock-chips.com?part=3

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  reply	other threads:[~2026-11-14  8:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14  8:33 [PATCH v6 0/4] Add eDP support for RK3568 Damon Ding
2026-11-14  8:33 ` Damon Ding
2026-11-14  8:33 ` Damon Ding
2026-11-14  8:33 ` [PATCH v6 1/4] dt-bindings: phy: Add rockchip,rk3568-edp-phy Damon Ding
2026-11-14  8:33   ` Damon Ding
2026-11-14  8:33   ` Damon Ding
2026-11-14  8:45   ` sashiko-bot
2026-11-14  8:45     ` sashiko-bot
2026-11-14  8:33 ` [PATCH v6 2/4] phy: rockchip: Add support for Naneng eDP phy Damon Ding
2026-11-14  8:33   ` Damon Ding
2026-11-14  8:33   ` Damon Ding
2026-11-14  8:33 ` [PATCH v6 3/4] arm64: dts: rockchip: rk356x: Add eDP controller and phy nodes Damon Ding
2026-11-14  8:33   ` Damon Ding
2026-11-14  8:33   ` Damon Ding
2026-11-14  8:55   ` sashiko-bot [this message]
2026-11-14  8:55     ` sashiko-bot
2026-11-14  8:33 ` [PATCH v6 4/4] MAINTAINERS: Add entry for Rockchip eDP phy Damon Ding
2026-11-14  8:33   ` Damon Ding
2026-11-14  8:33   ` Damon Ding

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=sashiko-outbox-214312@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=damon.ding@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=olteanv@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.