Linux-PHY Archive on 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 1/4] dt-bindings: phy: Add rockchip,rk3568-edp-phy
Date: Sat, 14 Nov 2026 08:45:05 +0000	[thread overview]
Message-ID: <sashiko-outbox-214291@kernel.org> (raw)
In-Reply-To: <20261114083339.600986-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 1917cbd8f96871d64c923d3ef4f97c3ee79b14dc
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.

> 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

[ ... ]

> +  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 the parent rockchip,rk3568-edp-phy-grf
schema and example?

The PCLK_EDPPHY_GRF APB clock is now claimed by the child
rockchip,rk3568-edp-phy node, so keeping clocks required on the parent
syscon node either fails dtbs_check when PCLK_EDPPHY_GRF is placed only
on the child PHY node or forces device trees to duplicate the clock on
both nodes.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261114083339.600986-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

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

Thread overview: 7+ 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 ` [PATCH v6 1/4] dt-bindings: phy: Add rockchip,rk3568-edp-phy Damon Ding
2026-11-14  8:45   ` sashiko-bot [this message]
2026-11-14  8:33 ` [PATCH v6 2/4] phy: rockchip: Add support for Naneng eDP phy 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:55   ` sashiko-bot
2026-11-14  8:33 ` [PATCH v6 4/4] MAINTAINERS: Add entry for Rockchip eDP phy 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-214291@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