From: netdev-bot+sashiko@kernel.org
To: markus.stockhausen@gmx.de
Cc: 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, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v4 2/5] dt-bindings: net: realtek,rtl9301-mdio: add clock-frequency
Date: Wed, 16 Sep 2026 13:35:12 +0000 [thread overview]
Message-ID: <178956571230.22033.2648098417803980646@kernel.org> (raw)
In-Reply-To: <20260912130451.3757276-3-markus.stockhausen@gmx.de>
Thank you for your contribution! Sashiko AI review found 2 potential
issue(s) to consider:
Critical: 0 · High: 0 · Medium: 0 · Low: 2
- [Low] Concern (validated as a FALSE POSITIVE, retained only per the
retention policy): 'the binding adds a per-bus clock-frequency…
- [Low] Redundant re-declaration of the common `clock-frequency` property
in Documentation/devicetree/bindings/net/realtek,rtl9301-mdio.yaml.
--
dt-bindings: net: realtek,rtl9301-mdio: add clock-frequency
This documents the MDC frequencies supported by the Realtek Otto switch
MDIO controllers, adding per-family clock-frequency value sets and
describing the shared frequency selector on RTL839x.
> diff --git a/Documentation/devicetree/bindings/net/realtek,rtl9301-mdio.yaml b/Documentation/devicetree/bindings/net/realtek,rtl9301-mdio.yaml
> index 7f5b4897487b2..c5f2289dc0eb2 100644
> --- a/Documentation/devicetree/bindings/net/realtek,rtl9301-mdio.yaml
> +++ b/Documentation/devicetree/bindings/net/realtek,rtl9301-mdio.yaml
> @@ -56,6 +56,9 @@ patternProperties:
> reg:
> maxItems: 1
>
> + clock-frequency:
> + $ref: /schemas/types.yaml#/definitions/uint32
> +
[Severity: Low]
This isn't a bug, but is this declaration needed at all? The mdio-bus
child subschema already does:
'^mdio-bus@[0-3]$':
$ref: mdio.yaml#
and Documentation/devicetree/bindings/net/mdio.yaml already declares the
property:
clock-frequency:
description:
Desired MDIO bus clock frequency in Hz. Values greater than IEEE 802.3
defined 2.5MHz should only be used when all devices on the bus support
the given clock speed.
So the property is already permitted by the referenced schema, and its type
is known to dtschema without an explicit uint32 $ref. Other in-tree
bindings rely on that, for example mscc,miim.yaml uses a bare
"clock-frequency: true" and microchip,pic64hpsc-mdio.yaml declares
clock-frequency with only a default.
The per-family enum blocks added below in the allOf if-then sections are
what actually restrict the accepted values, and those work independently of
this declaration. Could this block be dropped so the common property is
only described in mdio.yaml?
> required:
> - reg
>
[ ... ]
> @@ -77,8 +84,16 @@ allOf:
> - realtek,rtl8381-mdio
> - realtek,rtl8382-mdio
> then:
> + properties:
> + mdio-bus@0:
> + properties:
> + clock-frequency:
> + enum: [2500000, 10000000]
> + default: 2500000
> +
> patternProperties:
> '^mdio-bus@[1-3]$': false
[ ... ]
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260912130451.3757276-1-markus.stockhausen%40gmx.de
next prev parent reply other threads:[~2026-09-16 13:35 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
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 [this message]
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=178956571230.22033.2648098417803980646@kernel.org \
--to=netdev-bot+sashiko@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@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@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