From: Andrew Lunn <andrew@lunn.ch>
To: Vasilij Strassheim <v.strassheim@linutronix.de>
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 3/4] net: dsa: Add support for SoC-e SDSA tags
Date: Wed, 29 Jul 2026 19:22:38 +0200 [thread overview]
Message-ID: <df7e7e04-80fc-4b80-9afd-0e9bc14a759f@lunn.ch> (raw)
In-Reply-To: <20260729-devel-vstrassheim-soce-dsa-ml-v1-3-be569dae1b20@linutronix.de>
> @@ -98,6 +98,12 @@ config NET_DSA_TAG_EDSA
> Say Y or M if you want to enable support for tagging frames for the
> Marvell switches which use EtherType DSA headers.
>
> +config NET_DSA_TAG_SDSA
> + tristate "Tag driver for SoC-e switches using EtherType SDSA headers"
> + help
> + Say Y or M if you want to enable support for tagging frames for the
> + SoC-e switches.
> +
These entries are sorted, so it probably should be between
NET_DSA_TAG_RZN1_A5PSW and NET_DSA_TAG_LAN9303.
> @@ -23,6 +23,7 @@ dsa_core-y += \
> obj-$(CONFIG_NET_DSA_TAG_AR9331) += tag_ar9331.o
> obj-$(CONFIG_NET_DSA_TAG_BRCM_COMMON) += tag_brcm.o
> obj-$(CONFIG_NET_DSA_TAG_DSA_COMMON) += tag_dsa.o
> +obj-$(CONFIG_NET_DSA_TAG_SDSA) += tag_sdsa.o
> obj-$(CONFIG_NET_DSA_TAG_GSWIP) += tag_gswip.o
Also sorted, and this is the wrong spot.
> +#define SDSA_HLEN 8
> +
> +#define SDSA_NAME "sdsa"
Does SDSA mean anything? Or have you taken net/dsa/tag_dsa.c, and just
changed edsa to sdsa?
> +static struct sk_buff *sdsa_xmit(struct sk_buff *skb, struct net_device *dev)
> +{
> + struct dsa_port *dp = dsa_user_to_port(dev);
> + u8 *sdsa_header;
> +
> + if (skb_cow_head(skb, SDSA_HLEN) < 0)
> + return NULL;
> +
> + skb_push(skb, SDSA_HLEN);
> + dsa_alloc_etype_header(skb, SDSA_HLEN);
> +
> + /* Construct the FROM_CPU DSA tag. */
Is FROM_CPU a concept for this device? Are there other types of tag?
> + sdsa_header = dsa_etype_header_pos_tx(skb);
> + sdsa_header[0] = (ETH_P_SDSA >> 8) & 0xff;
> + sdsa_header[1] = ETH_P_SDSA & 0xff;
> + sdsa_header[2] = 0x00; /* reserved */
> + sdsa_header[3] = 0x00; /* reserved */
> + sdsa_header[4] = FIELD_PREP(SDSA_TAG_FRAME_TYPE_MASK, 1) |
> + FIELD_PREP(SDSA_TAG_PORT_HI_MASK, dp->index >> 5);
> + sdsa_header[5] = FIELD_PREP(SDSA_TAG_PORT_MASK, dp->index);
> + sdsa_header[6] = 0x00; /* VLAN not supported */
> + sdsa_header[7] = 0x00; /* VLAN not supported */
> +
> + return skb;
> +}
> +
> +static struct sk_buff *sdsa_rcv(struct sk_buff *skb, struct net_device *dev)
> +{
> + u8 *sdsa_header;
> + int source_port;
> + u8 frame_type;
> +
> + if (unlikely(!pskb_may_pull(skb, SDSA_HLEN)))
> + return NULL;
> +
> + sdsa_header = dsa_etype_header_pos_rx(skb);
> +
> + /* Check that the frame type is TO_CPU. */
> + frame_type = FIELD_GET(SDSA_TAG_FRAME_TYPE_MASK, sdsa_header[4]);
> + if (frame_type != 0)
#define for TO_CPU?
Andrew
next prev parent reply other threads:[~2026-07-29 17:22 UTC|newest]
Thread overview: 11+ 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-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-07-29 18:07 ` Rob Herring (Arm)
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 [this message]
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-07-29 20:05 ` Andrew Lunn
2026-07-29 16:56 ` [PATCH 0/4] net: dsa: Add SoC-e DSA driver Andrew Lunn
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=df7e7e04-80fc-4b80-9afd-0e9bc14a759f@lunn.ch \
--to=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 \
--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