Re: [PATCH net-next v9 0/4] net: dsa: initial support for MaxLinear MxL862xx switches

[Vladimir Oltean <olteanv@gmail.com>]

On Tue, Jan 27, 2026 at 09:37:40PM +0000, Daniel Golle wrote:
> This series adds very basic DSA support for the MaxLinear MxL86252
> (5 PHY ports) and MxL86282 (8 PHY ports) switches.
> 
> MxL862xx integrates a firmware running on an embedded processor (running
> Zephyr RTOS). Host interaction uses a simple netlink-like API transported
> over MDIO/MMD.
> 
> This series includes only what's needed to pass traffic between user
> ports and the CPU port: relayed MDIO to internal PHYs, basic port
> enable/disable, and CPU-port special tagging.
> Follow up series will bring bridge, VLAN, ... offloading,

I'm surprised the Kconfig help text says:

	  These switches have two 10GE SerDes interfaces, one typically
	  used as CPU port.

yet only PHY_INTERFACE_MODE_INTERNAL is set in phylink supported_interfaces.
You're also not making any mention of future SerDes support. What's up
with that, how do the SerDes ports currently work and how are they
described? (as internal?!)

> and support for using a 802.1Q-based special tag instead of the
> proprietary 8-byte tag.

Why is that?

Another (related) question. You have this comment in tag_mxl862xx.c:

	/* switch firmware expects ports to be counted starting from 1 */

from which I don't completely understand how is the firmware involved
(does it process the tags?). Would the expectation also apply to the
802.1Q based tagger?

What's the real story behind port index 0? Does it really not exist, or
is it some attempt to hide an internal port that's not supposed to be used?

If the latter, I guess something like the snippet below (seen in
arch/arm64/boot/dts/freescale/fsl-lx2160a-bluebox3.dts) would simplify
the driver by a bit:

	ethernet-switch@0 {
		...
		ethernet-ports {
			...
			/* Microcontroller port */
			port@0 {
				reg = <0>;
				status = "disabled";
			};