From: sashiko-bot@kernel.org
To: "Damon Ding" <damon.ding@rock-chips.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v11 2/3] arm64: dts: rockchip: Add missing hclk for RK3588 eDP1
Date: Fri, 05 Jun 2026 02:36:19 +0000 [thread overview]
Message-ID: <20260605023619.C10061F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260605022305.3058853-3-damon.ding@rock-chips.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incorrect clock name "hclk" is used instead of "grf", which violates the DT binding schema and prevents the eDP driver from explicitly managing the clock.
--
commit a1adb5c9bb9ba76654d07ba8c6320c7edf51f41b
Author: Damon Ding <damon.ding@rock-chips.com>
arm64: dts: rockchip: Add missing hclk for RK3588 eDP1
This commit adds the required HCLK_VO1 bus clock to the RK3588 eDP1 node.
It intends to manage the clock explicitly instead of relying on implicit
enabling via the GRF phandle reference.
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi b/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi
> index a2640014ee042..b251bb129cdbf 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi
> @@ -285,8 +285,8 @@ hdmi1_out: port@1 {
> edp1: edp@fded0000 {
> compatible = "rockchip,rk3588-edp";
> reg = <0x0 0xfded0000 0x0 0x1000>;
> - clocks = <&cru CLK_EDP1_24M>, <&cru PCLK_EDP1>;
> - clock-names = "dp", "pclk";
> + clocks = <&cru CLK_EDP1_24M>, <&cru PCLK_EDP1>, <&cru HCLK_VO1>;
> + clock-names = "dp", "pclk", "hclk";
[Severity: Medium]
Should this clock name be "grf" instead of "hclk"?
According to the device tree binding schema for rockchip,analogix-dp, the
third clock name is expected to be "grf".
The driver looks up this clock using devm_clk_get_optional(dev, "grf"). If
"hclk" is used here, the driver will fail to find it, receive a NULL
pointer, and won't explicitly enable the clock as intended by this patch.
> interrupts = <GIC_SPI 164 IRQ_TYPE_LEVEL_HIGH 0>;
> phys = <&hdptxphy1>;
> phy-names = "dp";
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260605022305.3058853-1-damon.ding@rock-chips.com?part=2
next prev parent reply other threads:[~2026-06-05 2:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 2:23 [PATCH v11 0/3] Add eDP support for RK3576 Damon Ding
2026-06-05 2:23 ` Damon Ding
2026-06-05 2:23 ` [PATCH v11 1/3] arm64: dts: rockchip: Add missing hclk for RK3588 eDP0 Damon Ding
2026-06-05 2:23 ` Damon Ding
2026-06-05 2:38 ` sashiko-bot
2026-06-05 2:23 ` [PATCH v11 2/3] arm64: dts: rockchip: Add missing hclk for RK3588 eDP1 Damon Ding
2026-06-05 2:23 ` Damon Ding
2026-06-05 2:36 ` sashiko-bot [this message]
2026-06-05 2:23 ` [PATCH v11 3/3] arm64: dts: rockchip: Add eDP node for RK3576 Damon Ding
2026-06-05 2:23 ` Damon Ding
2026-06-05 2:38 ` sashiko-bot
2026-06-15 12:33 ` [PATCH v11 0/3] Add eDP support " Damon Ding
2026-06-15 12:33 ` Damon Ding
2026-06-15 13:01 ` Heiko Stübner
2026-06-15 13:01 ` Heiko Stübner
2026-06-15 13:32 ` Damon Ding
2026-06-15 13:32 ` 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=20260605023619.C10061F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=damon.ding@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.