From: sashiko-bot@kernel.org
To: "Linus Walleij" <linusw@kernel.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH net-next v9 3/4] net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA
Date: Mon, 07 Sep 2026 07:48:45 +0000 [thread overview]
Message-ID: <20260907074846.37C861F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260906-ks8995-to-ksz8-v9-3-8d8815a91bd8@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing polling loop or delay after triggering self-clearing PHY soft reset.
--
commit 702792aed3ea3d1bc269d8039fc614882297cc87
Author: Linus Walleij <linusw@kernel.org>
net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA
This patch adds support for the Microchip KSZ8995XA switch to the KSZ
driver, handling its specific port configurations, priority levels, and
packet-size semantics.
> diff --git a/drivers/net/dsa/microchip/ksz8.c b/drivers/net/dsa/microchip/ksz8.c
> --- a/drivers/net/dsa/microchip/ksz8.c
> +++ b/drivers/net/dsa/microchip/ksz8.c
[ ... ]
> @@ -253,7 +254,17 @@ static int ksz8463_reset_switch(struct ksz_device *dev)
>
> static int ksz8_reset_switch(struct ksz_device *dev)
> {
> - if (ksz_is_ksz88x3(dev)) {
> + if (ksz_is_ksz8995xa(dev)) {
> + unsigned int port;
> +
> + /* The KSZ8995XA switch itself cannot be reset by software, but
> + * often boot loaders have fun with ports, so reset them. This
> + * reset bit is self-clearing.
> + */
> + for (port = 0; port < dev->info->port_cnt; port++)
> + ksz_port_cfg(dev, port, REG_PORT_STATUS_3,
> + PORT_PHY_SOFT_RESET, true);
[Severity: Medium]
Is a delay or polling loop needed here after asserting the self-clearing
reset bit?
If the PHY requires time to complete its soft reset, subsequent register
configurations performed by ksz8_setup() immediately after returning from
ksz8_reset_switch() might be ignored or cause hardware state issues.
> + } else if (ksz_is_ksz88x3(dev)) {
> /* reset switch */
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260906-ks8995-to-ksz8-v9-0-8d8815a91bd8@kernel.org?part=3
next prev parent reply other threads:[~2026-09-07 7:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 7:48 [PATCH net-next v9 0/4] net: dsa: microchip: Add support for KSZ8995XA/KS8995XA Linus Walleij
2026-09-06 7:48 ` [PATCH net-next v9 1/4] dt-bindings: net: dsa: microchip: Add KSZ8995XA Linus Walleij
2026-09-08 3:49 ` netdev-bot+sashiko
2026-09-06 7:48 ` [PATCH net-next v9 2/4] net: dsa: tag_ks8995: Add the KS8995 tag handling Linus Walleij
2026-09-08 3:49 ` netdev-bot+sashiko
2026-09-06 7:48 ` [PATCH net-next v9 3/4] net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA Linus Walleij
2026-09-07 7:48 ` sashiko-bot [this message]
2026-09-08 3:49 ` netdev-bot+sashiko
2026-09-08 8:52 ` Linus Walleij
2026-09-06 7:48 ` [PATCH net-next v9 4/4] net: dsa: ks8995: Delete surplus driver Linus Walleij
2026-09-08 3:49 ` netdev-bot+sashiko
2026-09-08 9:18 ` Linus Walleij
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=20260907074846.37C861F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linusw@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 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.