public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Max Hsu <max.hsu@sifive.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Samuel Holland <samuel.holland@sifive.com>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	Thomas Gleixner <tglx@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH 1/5] dt-bindings: net: macb: Add SiFive FU740-C000 support
Date: Fri, 20 Feb 2026 09:29:28 +0000	[thread overview]
Message-ID: <20260220-repeal-glitter-acb73cc75564@spud> (raw)
In-Reply-To: <20260220-fu740-v1-1-c8af54130c58@sifive.com>

[-- Attachment #1: Type: text/plain, Size: 2642 bytes --]

On Fri, Feb 20, 2026 at 04:27:05PM +0800, Max Hsu wrote:
> Add the SiFive FU740-C000 ethernet controller compatible string to the
> Cadence MACB binding documentation.
> 
> The FU740 ethernet controller uses the same GEMGXL management block as
> the FU540, which is tightly coupled with the Cadence MACB IP. This
> follows the SiFive IP versioning scheme which requires SoC-specific
> compatible strings for proper hardware identification.

Your rationale for this change is misguided, as this is not a SiFive IP,
so that document does not apply. On the other hand, the general rules
for devicetrees require this so this just means a change in the
rationale provided.

> 
> Signed-off-by: Max Hsu <max.hsu@sifive.com>
> ---
>  Documentation/devicetree/bindings/net/cdns,macb.yaml | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/net/cdns,macb.yaml b/Documentation/devicetree/bindings/net/cdns,macb.yaml
> index cb14c35ba996..b46dde1da170 100644
> --- a/Documentation/devicetree/bindings/net/cdns,macb.yaml
> +++ b/Documentation/devicetree/bindings/net/cdns,macb.yaml
> @@ -63,6 +63,7 @@ properties:
>            - mobileye,eyeq5-gem        # Mobileye EyeQ5 SoCs
>            - raspberrypi,rp1-gem       # Raspberry Pi RP1 gigabit ethernet interface
>            - sifive,fu540-c000-gem     # SiFive FU540-C000 SoC
> +          - sifive,fu740-c000-gem     # SiFive FU740-C000 SoC

I don't think this is right, since it is identical to the one on the
fu540 (as evidenced by how it has worked until now and the contents of
your driver change). I think you should add the fu740 with a fallback to
the fu540, like the devices from Microchip that fall back to the
microchip,sama7g5-gem. The rest of the changes to the driver and binding
can then be dropped as they'll be redundant.

Thanks,
Conor.

pw-bot: changes-requested

>  
>        - items:
>            - enum:
> @@ -74,7 +75,7 @@ properties:
>      minItems: 1
>      items:
>        - description: Basic register set
> -      - description: GEMGXL Management block registers on SiFive FU540-C000 SoC
> +      - description: GEMGXL Management block registers on SiFive FU540/FU740 SoCs
>  
>    interrupts:
>      minItems: 1
> @@ -181,7 +182,9 @@ allOf:
>          properties:
>            compatible:
>              contains:
> -              const: sifive,fu540-c000-gem
> +              enum:
> +                - sifive,fu540-c000-gem
> +                - sifive,fu740-c000-gem
>      then:
>        properties:
>          reg:
> 
> -- 
> 2.43.0
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-02-20  9:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20  8:27 [PATCH 0/5] riscv: dts: sifive: fu740: Fix compatible strings per IP versioning Max Hsu
2026-02-20  8:27 ` [PATCH 1/5] dt-bindings: net: macb: Add SiFive FU740-C000 support Max Hsu
2026-02-20  9:29   ` Conor Dooley [this message]
2026-02-20 18:42     ` Max Hsu
2026-02-20  8:27 ` [PATCH 2/5] dt-bindings: interrupt-controller: Add SiFive FU740-C000 PLIC Max Hsu
2026-02-20  9:23   ` Conor Dooley
2026-02-20 18:49     ` Max Hsu
2026-02-20 22:33       ` Conor Dooley
2026-02-20  8:27 ` [PATCH 3/5] net: macb: Add support for SiFive FU740-C000 Max Hsu
2026-02-20 13:13   ` Andrew Lunn
2026-02-20 18:35     ` Max Hsu
2026-02-20 22:00       ` Conor Dooley
2026-02-20  8:27 ` [PATCH 4/5] riscv: dts: sifive: fu740: Use correct ethernet compatible string Max Hsu
2026-02-20  8:27 ` [PATCH 5/5] riscv: dts: sifive: fu740: Use correct PLIC " Max Hsu

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=20260220-repeal-glitter-acb73cc75564@spud \
    --to=conor@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=andrew+netdev@lunn.ch \
    --cc=aou@eecs.berkeley.edu \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=max.hsu@sifive.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=pabeni@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=samuel.holland@sifive.com \
    --cc=tglx@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