public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Joris Vaisvila <joey@tinyisr.com>
To: netdev@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>, 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>,
	Joris Vaisvila <joey@tinyisr.com>
Subject: [RFC 0/2 net-next] net: dsa: MT7628 embedded switch initial support
Date: Sat, 28 Feb 2026 20:52:40 +0200	[thread overview]
Message-ID: <20260228185242.800836-1-joey@tinyisr.com> (raw)

Hello,

This RFC adds initial support for the basic functionality needed to
operate the MT7628 embedded switch.

The driver configures the switch to isolate each port and does not
offload any bridge functions, so all of the forwarding is done in
software. Bridge and VLAN offloading are possible but omitted to
simplify this initial patch set.

The special tag currently overlaps some functionality with tag_8021q,
but it enables precise TX handling and (more) precise RX handling for
future VLAN offloading.

Tested on MT7628AN with 5 100mbps ports. All 5 ports were tested for
correct forwarding with two devices.

# Request for comments:

- What would be an acceptable way to present the undocumented phy init
  in mt7628_vendor_phys_init and switch_init?

- Should I aim to set all register default values for general switch
  config or is relying on the documented switch reset state acceptable?

- I am also looking for any and all feedback on the architecture and
  coding style of this driver.

Thank you for your time and feedback.

Joris Vaisvila (2):
  net: dsa: initial MT7628 special tag driver
  net: dsa: initial support for MT7628 embedded switch

 drivers/net/dsa/Kconfig  |   6 +
 drivers/net/dsa/Makefile |   1 +
 drivers/net/dsa/mt7628.c | 567 +++++++++++++++++++++++++++++++++++++++
 include/net/dsa.h        |   2 +
 net/dsa/Kconfig          |   6 +
 net/dsa/Makefile         |   1 +
 net/dsa/tag_mt7628.c     |  85 ++++++
 7 files changed, 668 insertions(+)
 create mode 100644 drivers/net/dsa/mt7628.c
 create mode 100644 net/dsa/tag_mt7628.c

-- 
2.53.0


             reply	other threads:[~2026-02-28 18:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 18:52 Joris Vaisvila [this message]
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

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=20260228185242.800836-1-joey@tinyisr.com \
    --to=joey@tinyisr.com \
    --cc=andrew@lunn.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox