From: Florian Fainelli <f.fainelli@gmail.com>
To: Prasanna Vengateshan <prasanna.vengateshan@microchip.com>,
andrew@lunn.ch, olteanv@gmail.com, netdev@vger.kernel.org,
robh+dt@kernel.org
Cc: kuba@kernel.org, vivien.didelot@gmail.com, davem@davemloft.net,
UNGLinuxDriver@microchip.com, Woojung.Huh@microchip.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next 0/8] net: dsa: microchip: DSA driver support for LAN937x switch
Date: Thu, 28 Jan 2021 09:55:58 -0800 [thread overview]
Message-ID: <bb729a8b-0ea1-e05d-f410-ed049e793d04@gmail.com> (raw)
In-Reply-To: <20210128064112.372883-1-prasanna.vengateshan@microchip.com>
On 1/27/2021 10:41 PM, Prasanna Vengateshan wrote:
> LAN937x is a Multi-Port 100BASE-T1 Ethernet Physical Layer switch
> compliant with the IEEE 802.3bw-2015 specification. The device
> provides 100 Mbit/s transmit and receive capability over a single
> Unshielded Twisted Pair (UTP) cable. LAN937x is successive revision
> of KSZ series switch. This series of patches provide the DSA driver
> support for Microchip LAN937X switch and it configures through
> SPI interface.
>
> This driver shares some of the functions from KSZ common
> layer.
>
> The LAN937x switch series family consists of following SKUs:
> LAN9370:
> - 4 T1 Phys
> - 1 RGMII port
> LAN9371:
> - 3 T1 Phys & 1 TX Phy
> - 2 RGMII ports
> LAN9372:
> - 5 T1 Phys & 1 TX Phy
> - 2 RGMII ports
> LAN9373:
> - 5 T1 Phys
> - 2 RGMII & 1 SGMII port
> LAN9374:
> - 6 T1 Phys
> - 2 RGMII ports
>
> More support will be added at a later stage.
It is great to see a new switch from Microchip being submitted for
review. One thing that has bothered me as a DSA maintainer before though
is that we have seen Microchip contribute new DSA drivers which are
always welcome, however the maintenance and bug fixing of these drivers
was spotty, thus leading to external contributors to take on the tasks
of fixing bugs. Do you have a stronger commitment now to stay involved
with reviewing/fixing bugs affecting Microchip DSA drivers and to a
larger extent the framework itself?
Could you also feed back to your hardware organization to settle on a
tag format that is not a snowflake? Almost *every* switch you have has a
different tagging format, this is absurd. All other vendors in tree have
been able to settle on at most 2 or 3 different tagging formats over
their switching product life span (for some vendors this dates back 20
years ago).
I will provide a more detailed review later on.
>
> Prasanna Vengateshan (8):
> dt-bindings: net: dsa: dt bindings for microchip lan937x
> net: dsa: microchip: add tag handling for Microchip LAN937x
> net: dsa: microchip: add DSA support for microchip lan937x
> net: dsa: microchip: add support for phylink management
> net: dsa: microchip: add support for ethtool port counters
> net: dsa: microchip: add support for port mirror operations
> net: dsa: microchip: add support for fdb and mdb management
> net: dsa: microchip: add support for vlan operations
>
> .../bindings/net/dsa/microchip,lan937x.yaml | 115 ++
> MAINTAINERS | 1 +
> drivers/net/dsa/microchip/Kconfig | 12 +
> drivers/net/dsa/microchip/Makefile | 5 +
> drivers/net/dsa/microchip/ksz_common.h | 1 +
> drivers/net/dsa/microchip/lan937x_dev.c | 895 ++++++++++++++
> drivers/net/dsa/microchip/lan937x_dev.h | 79 ++
> drivers/net/dsa/microchip/lan937x_main.c | 1037 +++++++++++++++++
> drivers/net/dsa/microchip/lan937x_reg.h | 955 +++++++++++++++
> drivers/net/dsa/microchip/lan937x_spi.c | 104 ++
> include/net/dsa.h | 2 +
> net/dsa/Kconfig | 4 +-
> net/dsa/tag_ksz.c | 74 ++
> 13 files changed, 3282 insertions(+), 2 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/dsa/microchip,lan937x.yaml
> create mode 100644 drivers/net/dsa/microchip/lan937x_dev.c
> create mode 100644 drivers/net/dsa/microchip/lan937x_dev.h
> create mode 100644 drivers/net/dsa/microchip/lan937x_main.c
> create mode 100644 drivers/net/dsa/microchip/lan937x_reg.h
> create mode 100644 drivers/net/dsa/microchip/lan937x_spi.c
>
--
Florian
next prev parent reply other threads:[~2021-01-28 17:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 6:41 Prasanna Vengateshan
2021-01-28 6:41 ` [PATCH net-next 1/8] dt-bindings: net: dsa: dt bindings for microchip lan937x Prasanna Vengateshan
2021-01-30 2:02 ` Vladimir Oltean
2021-02-10 11:46 ` Prasanna Vengateshan Varadharajan
2021-02-10 18:57 ` Andrew Lunn
2021-02-09 19:35 ` Rob Herring
2021-01-28 6:41 ` [PATCH net-next 2/8] net: dsa: tag_ksz: add tag handling for Microchip LAN937x Prasanna Vengateshan
2021-01-28 18:03 ` Andrew Lunn
2021-01-30 2:27 ` Vladimir Oltean
2021-02-10 11:55 ` Prasanna Vengateshan Varadharajan
2021-01-28 6:41 ` [PATCH net-next 3/8] net: dsa: microchip: add DSA support for microchip lan937x Prasanna Vengateshan
2021-01-29 1:07 ` Andrew Lunn
2021-02-05 12:48 ` Prasanna Vengateshan Varadharajan
2021-02-05 13:27 ` Andrew Lunn
2021-03-15 6:25 ` Prasanna Vengateshan Varadharajan
2021-01-28 6:41 ` [PATCH net-next 4/8] net: dsa: microchip: add support for phylink management Prasanna Vengateshan
2021-01-29 1:12 ` Andrew Lunn
2021-01-28 6:41 ` [PATCH net-next 5/8] net: dsa: microchip: add support for ethtool port counters Prasanna Vengateshan
2021-01-28 6:41 ` [PATCH net-next 6/8] net: dsa: microchip: add support for port mirror operations Prasanna Vengateshan
2021-01-28 6:41 ` [PATCH net-next 7/8] net: dsa: microchip: add support for fdb and mdb management Prasanna Vengateshan
2021-01-28 6:41 ` [PATCH net-next 8/8] net: dsa: microchip: add support for vlan operations Prasanna Vengateshan
2021-01-28 17:55 ` Florian Fainelli [this message]
2021-01-30 2:09 ` [PATCH net-next 0/8] net: dsa: microchip: DSA driver support for LAN937x switch Vladimir Oltean
2021-02-02 1:25 ` Woojung.Huh
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=bb729a8b-0ea1-e05d-f410-ed049e793d04@gmail.com \
--to=f.fainelli@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=prasanna.vengateshan@microchip.com \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@gmail.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
Powered by JetHome