From: sashiko-bot@kernel.org
To: "Joseph Telaak" <joseph@telaak.dev>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH net-next v2 1/2] dt-bindings: net: dsa: lantiq,gswip: add reset-gpios
Date: Mon, 09 Nov 2026 23:00:21 +0000 [thread overview]
Message-ID: <sashiko-outbox-205780@kernel.org> (raw)
In-Reply-To: <20261108-mxl-gsw1xx-reset-v2-1-46c1da093893@telaak.dev>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] dt-bindings: net: dsa: lantiq,gswip: split GSW1xx into separate
schema
--
commit cbde9490cffae75d1433f9bd1e4ef36f7a9097cd
Author: Joseph Telaak <joseph@telaak.dev>
dt-bindings: net: dsa: lantiq,gswip: add reset-gpios
This commit adds the reset-gpios property to the lantiq,gswip binding for
standalone GSW1xx switches and disallows it for SoC-integrated variants.
> diff --git a/Documentation/devicetree/bindings/net/dsa/lantiq,gswip.yaml b/Documentation/devicetree/bindings/net/dsa/lantiq,gswip.yaml
> index 49af5573e452d..9a74ea2a6dcdd 100644
> --- a/Documentation/devicetree/bindings/net/dsa/lantiq,gswip.yaml
> +++ b/Documentation/devicetree/bindings/net/dsa/lantiq,gswip.yaml
> @@ -40,6 +40,11 @@ properties:
> - const: mdio
> - const: mii
>
> + reset-gpios:
> + maxItems: 1
> + description:
> + GPIO connected to the hardware reset input of a standalone switch.
> +
> mdio:
> $ref: /schemas/net/mdio.yaml#
> unevaluatedProperties: false
> @@ -173,6 +178,7 @@ allOf:
> mdio:
> required:
> - compatible
> + reset-gpios: false
> else:
> properties:
> reg:
[Severity: Low]
Would it make sense to split the standalone MDIO-connected GSW1xx switches
into a separate binding schema instead of adding another conditional
override here?
The SoC-integrated MMIO switches and standalone MDIO switches sit on
different buses and already use the allOf if-then-else block to constrain
or disallow reg, reg-names, mdio, and gphy-fw between the two families.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261108-mxl-gsw1xx-reset-v2-0-46c1da093893@telaak.dev?part=1
next prev parent reply other threads:[~2026-11-09 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 22:59 [PATCH net-next v2 0/2] net: dsa: mxl-gsw1xx: reset the switch through reset-gpios Joseph Telaak via B4 Relay
2026-11-08 22:59 ` [PATCH net-next v2 1/2] dt-bindings: net: dsa: lantiq,gswip: add reset-gpios Joseph Telaak via B4 Relay
2026-11-09 23:00 ` sashiko-bot [this message]
2026-11-08 22:59 ` [PATCH net-next v2 2/2] net: dsa: mxl-gsw1xx: reset the switch through reset-gpios Joseph Telaak via B4 Relay
2026-11-09 23:00 ` sashiko-bot
2026-11-09 23:37 ` netdev-bot+sashiko
2026-11-09 23:45 ` Joseph Telaak
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=sashiko-outbox-205780@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joseph@telaak.dev \
--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