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 2/4] dt-bindings: net: dsa: Add SoC-e switch IP and DSA bindings
Date: Wed, 05 Aug 2026 14:33:21 +0200 [thread overview]
Message-ID: <55070c3f0b462f35e63b55fdd0e7576da8bc28a2.camel@linutronix.de> (raw)
In-Reply-To: <604ff3d4-2a66-4086-80d3-ce838773b9ed@lunn.ch>
On Mon, 2026-08-03 at 18:35 +0200, Andrew Lunn wrote:
> > There are synthesis options for various management interfaces. MDIO and
> > MMIO are two of them. I only have one variant for the memory-mapped
> > version. For v2, I'll discard everything else and update the
> > documentation accordingly.
>
> Please take a look at the DSA drivers which support multiple
> interfaces.
Thank you for the tip. I think hellcreek and lantiq can serve as
examples. Both are also synthesized switches. Like hellcreek, I will
keep only one interface in the next version.
> You probably want a MMIO driver which creates a regmap, and passes it
> to the core driver. A future MDIO driver can create a regmap and pass
> it to the core driver.
>
> The DT binding should be similarly structured, a .yaml file for the
> core, and a .yaml for the MMIO wrapper.
I think that once I have implemented all the suggestions made so far, a
single DT binding with a .yaml file should be enough. Just like in the
two examples mentioned.
>
> Andrew
Thanks,
Vasilij
next prev parent reply other threads:[~2026-08-05 12:33 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 [this message]
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
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=55070c3f0b462f35e63b55fdd0e7576da8bc28a2.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