Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Christian Marangi" <ansuelsmth@gmail.com>
Cc: linux-phy@lists.infradead.org, conor+dt@kernel.org,
	robh@kernel.org, vkoul@kernel.org, devicetree@vger.kernel.org,
	neil.armstrong@linaro.org, olteanv@gmail.com
Subject: Re: [PATCH v10 1/5] dt-bindings: clock: airoha: Add PHY binding for Serdes port
Date: Thu, 02 Jul 2026 09:48:35 +0000	[thread overview]
Message-ID: <20260702094835.DFDA11F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260702093812.15918-2-ansuelsmth@gmail.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The `#phy-cells` property is implicitly allowed for the `econet,en751221-scu` compatible, contradicting the commit message which states it is exclusive to the Airoha AN7581 SoC.
- [Medium] The `airoha,en7581-scu` variant gains a new PHY provider capability, but `#phy-cells` is not added to its required properties, and the schema example is not updated.
--

commit 6d3a613072b0007e76d5846629212f75c8dfc300
Author: Christian Marangi <ansuelsmth@gmail.com>

dt-bindings: clock: airoha: Add PHY binding for Serdes port

This commit adds the #phy-cells property for Serdes port selection,
specifying that it is currently supported only for the Airoha AN7581 SoC.

> diff --git a/Documentation/devicetree/bindings/clock/airoha,en7523-scu.yaml b/Documentation/devicetree/bindings/clock/airoha,en7523-scu.yaml
> index eb24a5687639e..913ddc16182b8 100644
> --- a/Documentation/devicetree/bindings/clock/airoha,en7523-scu.yaml
> +++ b/Documentation/devicetree/bindings/clock/airoha,en7523-scu.yaml
[ ... ]
> @@ -65,6 +72,8 @@ allOf:
>          reg:
>            minItems: 2
>  
> +        '#phy-cells': false
> +
>    - if:
>        properties:
>          compatible:

[Severity: Medium]
The commit message states that the #phy-cells property is currently supported
only for the Airoha AN7581 SoC. However, looking at the allOf conditional
block:

  - if:
      properties:
        compatible:
          enum:
            - airoha,en7581-scu
            - econet,en751221-scu

Since econet,en751221-scu shares this block and does not explicitly have
'#phy-cells': false like the previous block, does this implicitly allow the
property for it and contradict the commit message?

[Severity: Medium]
Additionally, since the airoha,en7581-scu variant gains a new PHY provider
capability, should #phy-cells be added to its required properties list?

The example for airoha,en7581-scu in the same file is also missing the
property:

      scuclk: clock-controller@1fb00000 {
        compatible = "airoha,en7581-scu";
        reg = <0x0 0x1fb00000 0x0 0x970>;
              #clock-cells = <1>;
              #reset-cells = <1>;
      };

Would it be better to update the schema to mandate the property and update
the example to include #phy-cells = <1> so incomplete device tree nodes do
not silently pass schema validation?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260702093812.15918-1-ansuelsmth@gmail.com?part=1

  reply	other threads:[~2026-07-02  9:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02  9:38 [PATCH v10 0/5] airoha: an7581: USB support Christian Marangi
2026-07-02  9:38 ` [PATCH v10 1/5] dt-bindings: clock: airoha: Add PHY binding for Serdes port Christian Marangi
2026-07-02  9:48   ` sashiko-bot [this message]
2026-07-02  9:38 ` [PATCH v10 2/5] dt-bindings: phy: Add documentation for Airoha AN7581 USB PHY Christian Marangi
2026-07-02  9:54   ` sashiko-bot
2026-07-02  9:38 ` [PATCH v10 3/5] clk: en7523: Add support for selecting the Serdes port in SCU Christian Marangi
2026-07-02  9:38 ` [PATCH v10 4/5] phy: move and rename Airoha PCIe PHY driver to dedicated directory Christian Marangi
2026-07-02 10:14   ` sashiko-bot
2026-07-02  9:38 ` [PATCH v10 5/5] phy: airoha: Add support for Airoha AN7581 USB PHY Christian Marangi
2026-07-02 10:26   ` 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=20260702094835.DFDA11F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ansuelsmth@gmail.com \
    --cc=conor+dt@kernel.org \
    --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