From: Vasilij Strassheim <v.strassheim@linutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: 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 0/4] net: dsa: Add SoC-e DSA driver
Date: Mon, 03 Aug 2026 17:22:35 +0200 [thread overview]
Message-ID: <8a5ec5c7d76d634293bd8c78a078d536ed516c08.camel@linutronix.de> (raw)
In-Reply-To: <50e4f195-f810-470b-b05a-97f622e6efc4@lunn.ch>
On Wed, 2026-07-29 at 18:56 +0200, Andrew Lunn wrote:
> On Wed, Jul 29, 2026 at 06:36:53PM +0200, Vasilij Strassheim wrote:
> > Add initial support for the DSA driver for SoC-e FPGA-based (IP core)
> > Ethernet switches.
>
> Let me start with a dumb question. Is this a true soft core switch,
> which is synthesised and running in the FPGA? Or is it hardware at the
> edge of the FPGA SoC?
I should have made that clearer right away. This is a true soft-core
switch that is synthesized and runs in AMD FPGAs.
I have a version in which both the MAC and the switch are synthesized
in FPGA, and two hardware PHYs are connected to the switch. The switch
provides an MDIO bus for the PHYs.
>
> If it is synthesised, do we have to deal with different synthesis
> options? Are there registers which indicate what these options are?
While setting up the switch, users will need to explore various
synthesis options. Once it's up and running, it should be possible to
load a preconfigured bitstream into the FPGA without having to deal with
these options in the DSA driver. The device Tree should then match the
configuration.
However, users are provided with instructions and a user-space
library/software from SoC-e to check and adjust the options if necessary.
DSA tagging, for example, is one of the synthesis options. If this option
is not active, the DSA driver will not work.
> Where as if it is fixed hardware in the SoC we don't need to worry so
> much about variations, it is fixed at the SoC level.
>
> > There are different variants of the SoC-e switch IP, which can be
> > additionally configured at runtime with proprietary userspace software.
>
> What sort of configuration?
Different kinds e.g. general interface configuration, traffic
management, redundancy, ...
Most of them are listed on the product page:
https://soc-e.com/products/10m-100m-1g-managed-redundant-switch-mrs/
DSA integration can stay as lean as possible to support only basic
functionality for different variants and versions of the switch.
>
> Andrew
Thanks,
Vasilij
next prev parent reply other threads:[~2026-08-03 15:22 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
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 [this message]
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=8a5ec5c7d76d634293bd8c78a078d536ed516c08.camel@linutronix.de \
--to=v.strassheim@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=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 \
/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