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 1/5] net: dsa: microchip: Add fallback Micrel compatibles
Date: Fri, 30 Oct 2026 04:54:22 +0000 [thread overview]
Message-ID: <sashiko-outbox-190440@kernel.org> (raw)
In-Reply-To: <20260516-ks8995-to-ksz8-v1-1-70d0ef4aa5f4@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Driver binding conflict due to duplicated compatible strings
--
commit 602050a194c8c1c059a85fb34c0d360b801f20f8
Author: Linus Walleij <linusw@kernel.org>
net: dsa: microchip: Add fallback Micrel compatibles
Because of forking paths when Micrel was acquired by Microchip,
two devices also exist with the micrel,* prefix bindings.
Add these to the KSZ SPI driver so users can use the more capable
driver.
> diff --git a/drivers/net/dsa/microchip/ksz_spi.c b/drivers/net/dsa/microchip/ksz_spi.c
> index d8001734b0574..c38eda65aaf24 100644
> --- a/drivers/net/dsa/microchip/ksz_spi.c
> +++ b/drivers/net/dsa/microchip/ksz_spi.c
> @@ -224,6 +224,21 @@ static void ksz_spi_shutdown(struct spi_device *spi)
> }
>
> static const struct of_device_id ksz_dt_ids[] = {
> + /*
> + * Legacy Micrel bindings. In 2015 Microchip acquired
> + * Micrel which is the originator of the KSZ series, and
> + * devices branded for Micrel already existed, as well as
> + * some device tree bindings. These two products are identical
> + * to the same Microchip products.
> + */
> + {
> + .compatible = "micrel,ksz8864",
> + .data = &ksz_switch_chips[KSZ8864]
> + },
> + {
> + .compatible = "micrel,ksz8795",
> + .data = &ksz_switch_chips[KSZ8795]
> + },
Does this create a driver binding conflict since these exact compatible
strings are actively claimed by ks8995_spi_of_match[] in
drivers/net/dsa/ks8995.c?
Having two drivers claim the same hardware ID without mutual Kconfig
exclusion leads to a non-deterministic driver binding race, breaking
bisectability.
While later commits in the series resolve this (commit "net: dsa:
microchip: Support Microchip KSZ8995XA / KS8995XA" adds the Kconfig
dependency, and commit "net: dsa: ks8995: Delete surplus driver"
removes the old driver), shouldn't the mutual exclusion be introduced
in this patch to ensure the commit history remains fully bisectable?
> {
> .compatible = "microchip,ksz8463",
> .data = &ksz_switch_chips[KSZ8463]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260516-ks8995-to-ksz8-v1-0-70d0ef4aa5f4@kernel.org?part=1
next prev parent reply other threads:[~2026-10-30 4:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 23:16 [PATCH 0/5] net: dsa: microchip: Add support for KSZ8995XA/KS8995XA Linus Walleij
2026-05-15 23:16 ` [PATCH 1/5] net: dsa: microchip: Add fallback Micrel compatibles Linus Walleij
2026-10-30 4:54 ` sashiko-bot [this message]
2026-05-15 23:16 ` [PATCH 2/5] dt-bindings: net: dsa: microchip: Add KSZ8995XA Linus Walleij
2026-05-17 8:42 ` Krzysztof Kozlowski
2026-05-17 10:39 ` Linus Walleij
2026-05-15 23:16 ` [PATCH 3/5] net: dsa: tag_ks8995: Add the KS8995 tag handling Linus Walleij
2026-10-30 4:54 ` sashiko-bot
2026-05-15 23:16 ` [PATCH 4/5] net: dsa: microchip: Support Microchip KSZ8995XA / KS8995XA Linus Walleij
2026-05-15 23:16 ` [PATCH 5/5] net: dsa: ks8995: Delete surplus driver Linus Walleij
2026-05-16 15:04 ` [PATCH 0/5] net: dsa: microchip: Add support for KSZ8995XA/KS8995XA Linus Walleij
2026-05-18 22:52 ` Jakub Kicinski
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-190440@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.