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 v5 3/3] arm64: dts: rockchip: rk356x: Add eDP controller and phy nodes
Date: Tue, 10 Nov 2026 08:31:57 +0000 [thread overview]
Message-ID: <sashiko-outbox-206627@kernel.org> (raw)
In-Reply-To: <20261110074533.4052196-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 39d000ce8ae0719491fd06506c51a275929fc4ce
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, eDP PHY child node, and eDP controller
nodes to rk356x-base.dtsi for the RK3568/RK3566 SoCs.
> 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 dropped from the parent
edp_phy_grf node (and from rockchip,rk3568-edp-phy-grf.yaml in commit
"dt-bindings: phy: Add rockchip,rk3568-edp-phy") now that the child
edp_phy node claims and enables PCLK_EDPPHY_GRF directly?
> @@ -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@fe0c0000 node pass dtbs_check or probe when enabled?
"rockchip,rk3568-edp" is not documented in
Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
or matched in rockchip_dp_dt_ids[]. In addition, the binding requires
rockchip,grf and rockchip_dp_of_probe() fails with -ENODEV when that
property is absent:
drivers/gpu/drm/rockchip/analogix_dp-rockchip.c:rockchip_dp_of_probe() {
...
dp->grf = syscon_regmap_lookup_by_phandle(np, "rockchip,grf");
if (IS_ERR(dp->grf))
return dev_err_probe(dev, PTR_ERR(dp->grf),
"failed to get rockchip,grf property\n");
...
}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110074533.4052196-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
prev parent reply other threads:[~2026-11-10 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 7:45 [PATCH v5 0/3] Add eDP support for RK3568 Damon Ding
2026-11-10 7:45 ` [PATCH v5 1/3] dt-bindings: phy: Add rockchip,rk3568-edp-phy Damon Ding
2026-11-10 8:01 ` sashiko-bot
2026-11-10 18:50 ` Rob Herring (Arm)
2026-11-10 7:45 ` [PATCH v5 2/3] phy: rockchip: Add support for Naneng eDP phy Damon Ding
2026-11-10 7:45 ` [PATCH v5 3/3] arm64: dts: rockchip: rk356x: Add eDP controller and phy nodes Damon Ding
2026-11-10 8:31 ` sashiko-bot [this message]
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-206627@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox