From: Daniel Golle <daniel@makrotopia.org>
To: Hauke Mehrtens <hauke@hauke-m.de>, 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>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Chen Minqiang <ptpt52@gmail.com>, Xinfa Deng <xinfa.deng@gl-inet.com>
Subject: [PATCH net-next v2 0/6] net: dsa: lantiq: add support for Intel GSW150
Date: Thu, 15 Jan 2026 00:56:29 +0000 [thread overview]
Message-ID: <cover.1768438019.git.daniel@makrotopia.org> (raw)
The Intel GSW150 Ethernet Switch (aka. Lantiq PEB7084) is the predecessor of
MaxLinear's GSW1xx series of switches. It shares most features, but has a
slightly different port layout and different MII interfaces.
Adding support for this switch to the mxl-gsw1xx driver is quite trivial.
---
Changes since initial submission:
* add patch fixing node naming convention for dt-bindings
* introduce GSWIP_MAX_PORTS macro
* don't assert SGMII PCS reset in case chip doesn't have SGMII
* use case ranges in phylink_get_caps
Daniel Golle (6):
dt-bindings: net: dsa: lantiq,gswip: use correct node name
dt-bindings: net: dsa: lantiq,gswip: add Intel GSW150
net: dsa: lantiq: allow arbitrary MII registers
net: dsa: lantiq: clean up phylink_get_caps switch statement
net: dsa: mxl-gsw1xx: only setup SerDes PCS if it exists
net: dsa: mxl-gsw1xx: add support for Intel GSW150
.../bindings/net/dsa/lantiq,gswip.yaml | 6 +-
drivers/net/dsa/lantiq/lantiq_gswip.c | 42 ++++--
drivers/net/dsa/lantiq/lantiq_gswip.h | 6 +-
drivers/net/dsa/lantiq/lantiq_gswip_common.c | 27 +---
drivers/net/dsa/lantiq/mxl-gsw1xx.c | 139 ++++++++++++++----
drivers/net/dsa/lantiq/mxl-gsw1xx.h | 2 +
6 files changed, 149 insertions(+), 73 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-15 0:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 0:56 Daniel Golle [this message]
2026-01-15 0:56 ` [PATCH net-next v2 1/6] dt-bindings: net: dsa: lantiq,gswip: use correct node name Daniel Golle
2026-01-15 19:59 ` Rob Herring (Arm)
2026-01-15 0:56 ` [PATCH net-next v2 2/6] dt-bindings: net: dsa: lantiq,gswip: add Intel GSW150 Daniel Golle
2026-01-15 20:00 ` Rob Herring (Arm)
2026-01-15 0:57 ` [PATCH net-next v2 3/6] net: dsa: lantiq: allow arbitrary MII registers Daniel Golle
2026-01-15 1:40 ` Daniel Golle
2026-01-15 10:06 ` Vladimir Oltean
2026-01-15 0:57 ` [PATCH net-next v2 4/6] net: dsa: lantiq: clean up phylink_get_caps switch statement Daniel Golle
2026-01-15 0:57 ` [PATCH net-next v2 5/6] net: dsa: mxl-gsw1xx: only setup SerDes PCS if it exists Daniel Golle
2026-01-15 0:58 ` [PATCH net-next v2 6/6] net: dsa: mxl-gsw1xx: add support for Intel GSW150 Daniel Golle
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=cover.1768438019.git.daniel@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hauke@hauke-m.de \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=ptpt52@gmail.com \
--cc=robh@kernel.org \
--cc=xinfa.deng@gl-inet.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.