From: netdev-bot+sashiko@kernel.org
To: spolack+git@mailbox.org
Cc: andrew+netdev@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, f.fainelli@gmail.com,
javen_xu@realsil.com.cn, chad@monroe.io, vladimir.oltean@nxp.com,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] dt-bindings: net: realtek,rtl82xx: Document RTL8261C/D PHYs
Date: Thu, 24 Sep 2026 10:21:10 +0000 [thread overview]
Message-ID: <179024527018.2160803.7990695653777964500@kernel.org> (raw)
In-Reply-To: <20260921161817.565185-2-spolack+git@mailbox.org>
Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.
Low priority / nit picks for your consideration:
- [Low] Concern (validated as FALSE POSITIVE / resolved inside the
series): the binding enables rx-polarity/tx-polarity(-names) for…
- [Low] The new unconditional `- $ref: /schemas/phy/phy-common-
props.yaml#` in…
- [Low] Concern (validated as FALSE POSITIVE / resolved inside the
series): the binding permits a `leds` node for ethernet-phy-…
- [Low] The commit message states the leds node is allowed for the new
parts "the way it is already allowed for the RTL8221B", but the only…
- [Low] Concern (validated as FALSE POSITIVE): the binding references
phy-common-props.yaml wholesale for the RTL8261C/D compatibles without…
--
dt-bindings: net: realtek,rtl82xx: Document RTL8261C/D PHYs
Adds the three compatible strings for the RTL8261C/D family, allows a leds
node for them, and references phy-common-props.yaml so the tx-polarity and
rx-polarity properties can be used on those parts. A second example using
inverted SerDes polarity and one LED is added.
Two questions below, one about the changelog and one about the schema.
> These parts drive four LEDs from the VEND2 LED register block, so allow
> the leds node for them the way it is already allowed for the RTL8221B.
[Severity: Low]
Is the reference to the RTL8221B here correct? The only compatible that
was exempted from "leds: false" before this patch is
ethernet-phy-id001c.c916, and in drivers/net/phy/realtek/realtek_main.c
the PHY_ID_MATCH_EXACT(0x001cc916) entry carries:
.name = "RTL8211F Gigabit Ethernet",
The RTL8221B ids are RTL_8221B_VB_CG (0x001cc849) and RTL_8221B_VM_CG
(0x001cc84a), i.e. compatibles ethernet-phy-id001c.c849 and
ethernet-phy-id001c.c84a, and those are still forced to "leds: false" by
this binding both before and after the patch.
Should the message name the RTL8211F instead?
> diff --git a/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml b/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml
> index 07b39ef1fc624..b21efcb9b2551 100644
> --- a/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml
> +++ b/Documentation/devicetree/bindings/net/realtek,rtl82xx.yaml
[ ... ]
> @@ -74,15 +77,35 @@ unevaluatedProperties: false
>
> allOf:
> - $ref: ethernet-phy.yaml#
> + - $ref: /schemas/phy/phy-common-props.yaml#
[Severity: Low]
This $ref is unconditional, so all six properties defined in
phy-common-props.yaml become evaluated for every compatible in this
binding, not just the three new ones. Besides the four polarity
properties, phy-common-props.yaml also defines:
tx-p2p-microvolt:
description:
Transmit amplitude voltages in microvolts, peak-to-peak. ...
tx-p2p-microvolt-names:
Since the restriction block below only sets the polarity properties to
false, does this now let tx-p2p-microvolt and tx-p2p-microvolt-names pass
dt_binding_check on every Realtek PHY compatible listed in this file
(ethernet-phy-id001c.c916, c849, c84a and the rest), where before the
patch "unevaluatedProperties: false" rejected them? There is no reader
for a transmit amplitude property anywhere in
drivers/net/phy/realtek/, so a device tree setting it would be silently
accepted and ignored.
Would adding
tx-p2p-microvolt: false
tx-p2p-microvolt-names: false
alongside the polarity entries, or moving the $ref under an
RTL8261-only branch, be preferable?
> - if:
> not:
> properties:
> compatible:
> contains:
> - const: ethernet-phy-id001c.c916
> + enum:
> + - ethernet-phy-id001c.c898
> + - ethernet-phy-id001c.c899
> + - ethernet-phy-id001c.c89a
> + - ethernet-phy-id001c.c916
> then:
> properties:
> leds: false
> + - if:
> + not:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - ethernet-phy-id001c.c898
> + - ethernet-phy-id001c.c899
> + - ethernet-phy-id001c.c89a
> + then:
> + properties:
> + rx-polarity: false
> + rx-polarity-names: false
> + tx-polarity: false
> + tx-polarity-names: false
[ ... ]
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260921161817.565185-1-spolack%2Bgit%40mailbox.org
next prev parent reply other threads:[~2026-09-24 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 16:18 [PATCH net-next 0/3] net: phy: realtek: SerDes lane polarity and LEDs for RTL8261C/D Simon Polack
2026-09-21 16:18 ` [PATCH net-next 1/3] dt-bindings: net: realtek,rtl82xx: Document RTL8261C/D PHYs Simon Polack
2026-09-24 10:21 ` netdev-bot+sashiko [this message]
2026-09-21 16:18 ` [PATCH net-next 2/3] net: phy: realtek: apply SerDes lane polarity on RTL8261C/D Simon Polack
2026-09-24 10:21 ` netdev-bot+sashiko
2026-09-21 16:18 ` [PATCH net-next 3/3] net: phy: realtek: add LED support for RTL8261C/D Simon Polack
2026-09-24 10:21 ` 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=179024527018.2160803.7990695653777964500@kernel.org \
--to=netdev-bot+sashiko@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chad@monroe.io \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=javen_xu@realsil.com.cn \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=spolack+git@mailbox.org \
--cc=vladimir.oltean@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®