Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Christian Marangi" <ansuelsmth@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v11 10/12] dt-bindings: net: pcs: Document support for Airoha Ethernet PCS
Date: Sat, 08 Aug 2026 13:13:56 +0000	[thread overview]
Message-ID: <20260808131356.9DC3A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260807131301.192060-11-ansuelsmth@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing `minItems` and `maxItems` constraints in `if-then` blocks for `reg` and `reg-names` allow incomplete device tree nodes to silently pass validation.
--

--- Patch [10]: [PATCH net-next v11 10/12] dt-bindings: net: pcs: Document support for Airoha Ethernet PCS ---
commit d59fd3ae8fb2709a26756c96f02e5d3905143b5a
Author: Christian Marangi <ansuelsmth@gmail.com>

dt-bindings: net: pcs: Document support for Airoha Ethernet PCS

This patch documents support for Airoha Ethernet PCS for AN7581 SoC.
It adds a new physical coding sublayer provider binding for the various
Serdes ports (10BASE-R, USXGMII, 2500BASE-X, 1000BASE-X, SGMII).

> diff --git a/Documentation/devicetree/bindings/net/pcs/airoha,pcs.yaml b/Documentation/devicetree/bindings/net/pcs/airoha,pcs.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/pcs/airoha,pcs.yaml
[ ... ]
> +allOf:
> +  - if:
> +      properties:
> +        compatible:
> +          contains:
> +            enum:
> +              - airoha,an7581-pcs-eth
> +              - airoha,an7581-pcs-pon
> +
> +    then:
> +      properties:
> +        reg:
> +          items:
> +            - description: PCS MAC reg
> +            - description: HSGMII AN reg
> +            - description: HSGMII PCS reg
> +            - description: MULTI SGMII reg
> +            - description: USXGMII reg
> +            - description: HSGMII rate adaption reg
> +            - description: PCS Analog register
> +            - description: PCS PMA (Physical Medium Attachment) register

[Severity: Medium]
Should this allOf conditional block for eth/pon also specify minItems: 8 and
maxItems: 8 for the reg and reg-names arrays?

Because the top-level schema defines minItems: 6 and maxItems: 15, defining
an items list here without explicit length constraints means a device tree
providing only 6 registers will silently pass validation for this variant.

[ ... ]
> +  - if:
> +      properties:
> +        compatible:
> +          contains:
> +            const: airoha,an7581-pcs-pcie
> +
> +    then:
> +      properties:
> +        reg:
> +          items:
> +            - description: PCS MAC 0 reg
> +            - description: HSGMII AN 0 reg
> +            - description: HSGMII PCS 0 reg
> +            - description: MULTI SGMII 0 reg
> +            - description: USXGMII 0 reg
> +            - description: HSGMII rate adaption 0 reg
> +            - description: PCS MAC 1 reg
> +            - description: HSGMII AN 1 reg
> +            - description: HSGMII PCS 1 reg
> +            - description: MULTI SGMII 1 reg
> +            - description: USXGMII 1 reg
> +            - description: HSGMII rate adaption 1 reg
> +            - description: PCS Analog register
> +            - description: PCS PMA (Physical Medium Attachment) 0 register
> +            - description: PCS PMA (Physical Medium Attachment) 1 register

[Severity: Medium]
Similarly, does this pcie allOf conditional block need a minItems: 15
constraint to ensure all required registers are present?

Without minItems constraints on reg and reg-names, any array length between
the top-level 6 and 15 will pass validation, allowing incomplete device tree
nodes to be accepted.

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

  reply	other threads:[~2026-08-08 13:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 13:12 [PATCH net-next v11 00/12] net: pcs: Introduce support for fwnode PCS Christian Marangi
2026-08-07 13:12 ` [PATCH net-next v11 01/12] net: phylink: keep and use MAC supported_interfaces in phylink struct Christian Marangi
2026-08-07 13:12 ` [PATCH net-next v11 02/12] net: phylink: introduce internal phylink PCS handling Christian Marangi
2026-08-08 13:13   ` sashiko-bot
2026-08-09 17:25   ` Andrew Lunn
2026-08-07 13:12 ` [PATCH net-next v11 03/12] net: pcs: implement Firmware node support for PCS driver Christian Marangi
2026-08-07 20:29   ` Randy Dunlap
2026-08-07 20:49     ` Christian Marangi
2026-08-08 13:13   ` sashiko-bot
2026-08-07 13:12 ` [PATCH net-next v11 04/12] net: phylink: save phylink instance fwnode on phylink_create Christian Marangi
2026-08-08 13:13   ` sashiko-bot
2026-08-09 17:29   ` Andrew Lunn
2026-08-07 13:12 ` [PATCH net-next v11 05/12] net: phylink: support PCS provider release Christian Marangi
2026-08-08 13:13   ` sashiko-bot
2026-08-07 13:12 ` [PATCH net-next v11 06/12] net: phylink: support late PCS provider attach Christian Marangi
2026-08-08 13:13   ` sashiko-bot
2026-08-09 17:35   ` Andrew Lunn
2026-08-07 13:12 ` [PATCH net-next v11 07/12] net: Document PCS subsystem Christian Marangi
2026-08-08 13:13   ` sashiko-bot
2026-08-07 13:12 ` [PATCH net-next v11 08/12] MAINTAINERS: add myself as PCS subsystem maintainer Christian Marangi
2026-08-07 13:12 ` [PATCH net-next v11 09/12] net: phylink: add .pcs_link_down PCS OP Christian Marangi
2026-08-08 13:13   ` sashiko-bot
2026-08-07 13:12 ` [PATCH net-next v11 10/12] dt-bindings: net: pcs: Document support for Airoha Ethernet PCS Christian Marangi
2026-08-08 13:13   ` sashiko-bot [this message]
2026-08-07 13:12 ` [PATCH net-next v11 11/12] net: pcs: airoha: add PCS driver for Airoha AN7581 SoC Christian Marangi
2026-08-08 13:13   ` sashiko-bot
2026-08-07 13:12 ` [PATCH net-next v11 12/12] net: airoha: add phylink support Christian Marangi
2026-08-08 13:13   ` sashiko-bot
2026-08-09 17:44 ` [PATCH net-next v11 00/12] net: pcs: Introduce support for fwnode PCS Andrew Lunn
2026-08-09 17:49   ` Christian Marangi
2026-08-09 20:43     ` Andrew Lunn
2026-08-09 20:59       ` Christian Marangi

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=20260808131356.9DC3A1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ansuelsmth@gmail.com \
    --cc=conor+dt@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox