From: Rob Herring <robh@kernel.org>
To: netdev-bot+sashiko@kernel.org
Cc: markus.stockhausen@gmx.de, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
chris.packham@alliedtelesis.co.nz, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v4 1/5] dt-bindings: net: realtek,rtl9301-mdio: restrict MDIO buses by family
Date: Thu, 24 Sep 2026 09:46:22 -0500 [thread overview]
Message-ID: <20260924144622.GA4180569-robh@kernel.org> (raw)
In-Reply-To: <178956571096.22033.1324157422276350284@kernel.org>
On Wed, Sep 16, 2026 at 01:35:10PM +0000, netdev-bot+sashiko@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential
> issue(s) to consider:
>
> Critical: 0 · High: 0 · Medium: 1 · Low: 0
>
> - [Medium] Incomplete constraint: the new per-family `allOf`/`if-then`
> blocks in…
>
> --
>
> dt-bindings: net: realtek,rtl9301-mdio: restrict MDIO buses by family
>
> This adds two per-family conditional blocks to the Realtek Otto MDIO
> controller binding so that mdio-bus child node names are limited to the
> number of buses each family has: one for RTL838x, two for RTL839x and
> four for RTL930x/RTL931x.
>
> > diff --git a/Documentation/devicetree/bindings/net/realtek,rtl9301-mdio.yaml b/Documentation/devicetree/bindings/net/realtek,rtl9301-mdio.yaml
> > index 67e0b23a8470e..7f5b4897487b2 100644
> > --- a/Documentation/devicetree/bindings/net/realtek,rtl9301-mdio.yaml
> > +++ b/Documentation/devicetree/bindings/net/realtek,rtl9301-mdio.yaml
> > @@ -67,6 +67,30 @@ patternProperties:
> >
> > unevaluatedProperties: false
> >
> > +allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - realtek,rtl8380-mdio
> > + - realtek,rtl8381-mdio
> > + - realtek,rtl8382-mdio
> > + then:
> > + patternProperties:
> > + '^mdio-bus@[1-3]$': false
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - realtek,rtl8391-mdio
> > + - realtek,rtl8392-mdio
> > + - realtek,rtl8393-mdio
> > + then:
> > + patternProperties:
> > + '^mdio-bus@[2-3]$': false
>
> [Severity: Medium]
> These two conditionals only reject child node names, but the bus index the
> driver consumes is the child's reg value. Should the same conditionals also
> bound reg?
No. Ideally we would check reg vs. unit-addresses which would prevent
anything out of range and/or mismatched. However, there are gaps in that
checking currently.
Rob
next prev parent reply other threads:[~2026-09-24 14:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 13:04 [PATCH net-next v4 0/5] net: mdio: realtek-rtl9300: add bus frequency handling Markus Stockhausen
2026-09-12 13:04 ` [PATCH net-next v4 1/5] dt-bindings: net: realtek,rtl9301-mdio: restrict MDIO buses by family Markus Stockhausen
2026-09-16 13:35 ` netdev-bot+sashiko
2026-09-24 14:46 ` Rob Herring [this message]
2026-09-12 13:04 ` [PATCH net-next v4 2/5] dt-bindings: net: realtek,rtl9301-mdio: add clock-frequency Markus Stockhausen
2026-09-16 13:35 ` netdev-bot+sashiko
2026-09-24 14:43 ` Rob Herring
2026-09-12 13:04 ` [PATCH net-next v4 3/5] net: mdio: realtek-rtl9300: convert "fwnode" left-overs to "of" Markus Stockhausen
2026-09-14 16:30 ` Andrew Lunn
2026-09-12 13:04 ` [PATCH net-next v4 4/5] net: mdio: realtek-rtl9300: reject duplicate MDIO bus IDs Markus Stockhausen
2026-09-14 16:31 ` Andrew Lunn
2026-09-14 16:44 ` Andrew Lunn
2026-09-16 13:35 ` netdev-bot+sashiko
2026-09-12 13:04 ` [PATCH net-next v4 5/5] net: mdio: realtek-rtl9300: support non-default clock frequencies Markus Stockhausen
2026-09-14 16:47 ` Andrew Lunn
2026-09-16 13:35 ` netdev-bot+sashiko
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=20260924144622.GA4180569-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=markus.stockhausen@gmx.de \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.