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 1/3] dt-bindings: phy: Add rockchip,rk3568-edp-phy
Date: Tue, 10 Nov 2026 08:01:11 +0000 [thread overview]
Message-ID: <sashiko-outbox-206554@kernel.org> (raw)
In-Reply-To: <20261110074533.4052196-2-damon.ding@rock-chips.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] dt-bindings: soc: rockchip: leftover clocks in
rk3568-edp-phy-grf schema
--
commit 9b91012944140ff14ec2e2563f712e212d1da630
Author: Damon Ding <damon.ding@rock-chips.com>
dt-bindings: phy: Add rockchip,rk3568-edp-phy
This commit adds Device Tree binding schemas for the RK3568 eDP
transmitter PHY and its parent eDP PHY GRF syscon node.
> diff --git a/Documentation/devicetree/bindings/soc/rockchip/rockchip,rk3568-edp-phy-grf.yaml b/Documentation/devicetree/bindings/soc/rockchip/rockchip,rk3568-edp-phy-grf.yaml
> new file mode 100644
> index 0000000000000..852420798f06a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/rockchip/rockchip,rk3568-edp-phy-grf.yaml
> @@ -0,0 +1,80 @@
[ ... ]
> +properties:
> + compatible:
> + items:
> + - const: rockchip,rk3568-edp-phy-grf
> + - const: syscon
> + - const: simple-mfd
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 1
> +
> + ranges: true
> +
> +patternProperties:
> + "^phy@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/phy/rockchip,rk3568-edp-phy.yaml#
> + unevaluatedProperties: false
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - "#address-cells"
> + - "#size-cells"
> + - ranges
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/rk3568-cru.h>
> +
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + 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";
> + #phy-cells = <0>;
> + };
> + };
> + };
[Severity: Medium]
Should clocks be dropped from properties, required, and the parent
syscon@fdcb0000 example node in rockchip,rk3568-edp-phy-grf.yaml?
The child rockchip,rk3568-edp-phy schema now owns and requires the apb
clock (PCLK_EDPPHY_GRF). Requiring clocks on the parent syscon node as
well causes dtbs_check failures unless device trees duplicate
PCLK_EDPPHY_GRF on both the parent syscon and the child PHY node.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110074533.4052196-1-damon.ding@rock-chips.com?part=1
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 v5 1/3] dt-bindings: phy: Add rockchip,rk3568-edp-phy
Date: Tue, 10 Nov 2026 08:01:11 +0000 [thread overview]
Message-ID: <sashiko-outbox-206554@kernel.org> (raw)
In-Reply-To: <20261110074533.4052196-2-damon.ding@rock-chips.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] dt-bindings: soc: rockchip: leftover clocks in
rk3568-edp-phy-grf schema
--
commit 9b91012944140ff14ec2e2563f712e212d1da630
Author: Damon Ding <damon.ding@rock-chips.com>
dt-bindings: phy: Add rockchip,rk3568-edp-phy
This commit adds Device Tree binding schemas for the RK3568 eDP
transmitter PHY and its parent eDP PHY GRF syscon node.
> diff --git a/Documentation/devicetree/bindings/soc/rockchip/rockchip,rk3568-edp-phy-grf.yaml b/Documentation/devicetree/bindings/soc/rockchip/rockchip,rk3568-edp-phy-grf.yaml
> new file mode 100644
> index 0000000000000..852420798f06a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/rockchip/rockchip,rk3568-edp-phy-grf.yaml
> @@ -0,0 +1,80 @@
[ ... ]
> +properties:
> + compatible:
> + items:
> + - const: rockchip,rk3568-edp-phy-grf
> + - const: syscon
> + - const: simple-mfd
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 1
> +
> + ranges: true
> +
> +patternProperties:
> + "^phy@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/phy/rockchip,rk3568-edp-phy.yaml#
> + unevaluatedProperties: false
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - "#address-cells"
> + - "#size-cells"
> + - ranges
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/rk3568-cru.h>
> +
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + 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";
> + #phy-cells = <0>;
> + };
> + };
> + };
[Severity: Medium]
Should clocks be dropped from properties, required, and the parent
syscon@fdcb0000 example node in rockchip,rk3568-edp-phy-grf.yaml?
The child rockchip,rk3568-edp-phy schema now owns and requires the apb
clock (PCLK_EDPPHY_GRF). Requiring clocks on the parent syscon node as
well causes dtbs_check failures unless device trees duplicate
PCLK_EDPPHY_GRF on both the parent syscon and the child PHY node.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110074533.4052196-1-damon.ding@rock-chips.com?part=1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-11-10 8:01 UTC|newest]
Thread overview: 19+ 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 ` Damon Ding
2026-11-10 7:45 ` Damon Ding
2026-11-10 7:45 ` [PATCH v5 1/3] dt-bindings: phy: Add rockchip,rk3568-edp-phy Damon Ding
2026-11-10 7:45 ` Damon Ding
2026-11-10 7:45 ` Damon Ding
2026-11-10 8:01 ` sashiko-bot [this message]
2026-11-10 8:01 ` sashiko-bot
2026-11-10 18:50 ` Rob Herring (Arm)
2026-11-10 18:50 ` Rob Herring (Arm)
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 ` Damon Ding
2026-11-10 7:45 ` 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 7:45 ` Damon Ding
2026-11-10 7:45 ` Damon Ding
2026-11-10 8:31 ` sashiko-bot
2026-11-10 8:31 ` sashiko-bot
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-206554@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.