From: Benedikt Spranger <b.spranger@linutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vasilij Strassheim <v.strassheim@linutronix.de>,
Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Russell King <linux@armlinux.org.uk>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org,
Martin Kaistra <martin.kaistra@linutronix.de>
Subject: Re: [PATCH 2/4] dt-bindings: net: dsa: Add SoC-e switch IP and DSA bindings
Date: Wed, 5 Aug 2026 16:27:05 +0200 [thread overview]
Message-ID: <20260805162705.1a3467ea@mitra> (raw)
In-Reply-To: <9f8ac30b-6579-4e48-abe3-823302a3da0e@lunn.ch>
Am Wed, 5 Aug 2026 15:53:59 +0200
schrieb Andrew Lunn <andrew@lunn.ch>:
> So i suspect you will need to support integration specific
> compatibles.
Me too. But for *now* things are, better seem to be, simple. The aim is
not to plug forseeable future development.
> One way to consider this. Look at your FPGA design. Delete the
> licensed core. What do you have left? Does it need software to drive
> it?
The minimal IP core is an unmanaged switch. No need for a DSA driver
here. The IP core profides a MDIO bus, therefor a MDIO driver would be
good. The version register in combination with some feature register
can be determined to get the needed information to configure the DSA
driver, or in the minimal case to return -ENODEV.
Thats, why I suggest to have a compatible string, which reflects the
register layout needed to determine the switch configuration:
1) Read the version register
2) Upon the version read the feature register
3) Be happy and configure the switch.
Regards
Bene
next prev parent reply other threads:[~2026-08-05 14:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 16:36 [PATCH 0/4] net: dsa: Add SoC-e DSA driver Vasilij Strassheim
2026-07-29 16:36 ` [PATCH 1/4] dt-bindings: vendor-prefixes: Add soce Vasilij Strassheim
2026-07-30 8:50 ` Krzysztof Kozlowski
2026-08-03 16:03 ` Vasilij Strassheim
2026-07-29 16:36 ` [PATCH 2/4] dt-bindings: net: dsa: Add SoC-e switch IP and DSA bindings Vasilij Strassheim
2026-07-29 17:11 ` Andrew Lunn
2026-08-03 15:29 ` Vasilij Strassheim
2026-08-03 16:35 ` Andrew Lunn
2026-08-05 12:33 ` Vasilij Strassheim
2026-07-29 18:07 ` Rob Herring (Arm)
2026-08-03 15:47 ` Vasilij Strassheim
2026-07-30 8:56 ` Krzysztof Kozlowski
2026-08-03 16:15 ` Vasilij Strassheim
2026-08-03 16:43 ` Andrew Lunn
2026-08-05 12:40 ` Vasilij Strassheim
2026-08-05 12:53 ` Andrew Lunn
2026-08-05 13:17 ` Vasilij Strassheim
2026-08-05 13:32 ` Benedikt Spranger
2026-08-05 13:53 ` Andrew Lunn
2026-08-05 14:27 ` Benedikt Spranger [this message]
2026-08-06 13:35 ` Andrew Lunn
2026-08-06 15:25 ` Benedikt Spranger
2026-08-04 6:25 ` Krzysztof Kozlowski
2026-08-05 13:03 ` Vasilij Strassheim
2026-07-30 8:56 ` Krzysztof Kozlowski
2026-08-03 16:16 ` Vasilij Strassheim
2026-07-29 16:36 ` [PATCH 3/4] net: dsa: Add support for SoC-e SDSA tags Vasilij Strassheim
2026-07-29 17:22 ` Andrew Lunn
2026-08-03 15:37 ` Vasilij Strassheim
2026-08-03 16:46 ` Andrew Lunn
2026-08-05 12:47 ` Vasilij Strassheim
2026-07-29 16:36 ` [PATCH 4/4] net: dsa: soce: Add initial driver support for MRS switches Vasilij Strassheim
2026-07-29 17:31 ` Andrew Lunn
2026-08-03 15:40 ` Vasilij Strassheim
2026-07-29 20:05 ` Andrew Lunn
2026-08-03 16:01 ` Vasilij Strassheim
2026-08-03 16:49 ` Andrew Lunn
2026-08-05 12:48 ` Vasilij Strassheim
2026-07-30 9:01 ` Krzysztof Kozlowski
2026-08-03 16:23 ` Vasilij Strassheim
2026-07-29 16:56 ` [PATCH 0/4] net: dsa: Add SoC-e DSA driver Andrew Lunn
2026-08-03 15:22 ` Vasilij Strassheim
2026-08-03 16:32 ` Andrew Lunn
2026-08-05 12:28 ` Vasilij Strassheim
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=20260805162705.1a3467ea@mitra \
--to=b.spranger@linutronix.de \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=martin.kaistra@linutronix.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=v.strassheim@linutronix.de \
/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