From: "Joris Vaišvila" <joey@tinyisr.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Daniel Golle <daniel@makrotopia.org>,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
"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>
Subject: Re: [RFC 0/2 net-next] net: dsa: MT7628 embedded switch initial support
Date: Sun, 1 Mar 2026 15:13:28 +0200 [thread overview]
Message-ID: <aaQ15ZLlZRvlqZ3H@archlinux> (raw)
In-Reply-To: <20260301123619.skschp4ioxnevh3u@skbuf>
Hi Vladimir,
Thank you for the feedback.
On Sun, Mar 01, 2026 at 02:36:19PM +0200, Vladimir Oltean wrote:
> I see a slight discrepancy between what the documentation claims the
> hardware does, and what the driver claims it does. The documentation
> seems to say that setting this bit is what allows the vlan->untag bits
> to take effect.
The comment was referencing an accidentally deleted line that enables
double tagging:
/* set up switch for double tagging to simulate vlan unawareness */
regmap_set_bits(esw->regmap, MT7628_ESW_REG_SGC2,
FIELD_PREP(MT7628_ESW_SGC2_DOUBLE_TAG_EN,
MT7628_ESW_PORTS_NOCPU));
I only re-tested untagged traffic before sending this in. Apologies for
that. I will expand my testing procedures to prevent this from happening
again.
> A VLAN-unaware port means that when an ingress packet comes with 802.1Q
> TPID 0x8100 and VID X from the wire, this VLAN header will be ignored by
> the switch, and the PVID of the port will be pushed as an outer tag, for
> any value of X, regardless of whether it is in the VLAN table or not.
> Does it do that?
That is what is intended to happen and it does do that if the
DOUBLE_TAG_EN is properly set. Will be fixed in later revisions.
prev parent reply other threads:[~2026-03-01 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 18:52 [RFC 0/2 net-next] net: dsa: MT7628 embedded switch initial support Joris Vaisvila
2026-02-28 18:52 ` [RFC PATCH 1/2 net-next] net: dsa: initial MT7628 special tag driver Joris Vaisvila
2026-02-28 20:12 ` Andrew Lunn
2026-03-04 22:16 ` Vladimir Oltean
2026-02-28 18:52 ` [RFC PATCH 2/2 net-next] net: dsa: initial support for MT7628 embedded switch Joris Vaisvila
2026-02-28 20:16 ` Andrew Lunn
2026-02-28 20:31 ` Andrew Lunn
2026-03-01 17:23 ` Joris Vaišvila
2026-02-28 23:40 ` [RFC 0/2 net-next] net: dsa: MT7628 embedded switch initial support Vladimir Oltean
2026-03-01 12:00 ` Daniel Golle
2026-03-01 12:36 ` Vladimir Oltean
2026-03-01 13:13 ` Joris Vaišvila [this message]
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=aaQ15ZLlZRvlqZ3H@archlinux \
--to=joey@tinyisr.com \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.