Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linus.walleij@linaro.org
Cc: andrew@lunn.ch, vivien.didelot@savoirfairelinux.com,
	f.fainelli@gmail.com, netdev@vger.kernel.org,
	openwrt-devel@lists.openwrt.org, lede-dev@lists.infradead.org,
	juhosg@openwrt.org
Subject: Re: [PATCH 3/3 v2] net: dsa: Add Vitesse VSC73xx DSA router driver
Date: Wed, 04 Jul 2018 11:32:40 +0900 (KST)	[thread overview]
Message-ID: <20180704.113240.652641829194832375.davem@davemloft.net> (raw)
In-Reply-To: <20180630111731.19551-3-linus.walleij@linaro.org>

From: Linus Walleij <linus.walleij@linaro.org>
Date: Sat, 30 Jun 2018 13:17:31 +0200

> This adds a DSA driver for:
> 
> Vitesse VSC7385 SparX-G5 5-port Integrated Gigabit Ethernet Switch
> Vitesse VSC7388 SparX-G8 8-port Integrated Gigabit Ethernet Switch
> Vitesse VSC7395 SparX-G5e 5+1-port Integrated Gigabit Ethernet Switch
> Vitesse VSC7398 SparX-G8e 8-port Integrated Gigabit Ethernet Switch
> 
> These switches have a built-in 8051 CPU and can download and execute
> firmware in this CPU. They can also be configured to use an external
> CPU handling the switch in a memory-mapped manner by connecting to
> that external CPU's memory bus.
> 
> This driver (currently) only takes control of the switch chip over
> SPI and configures it to route packages around when connected to a
> CPU port. The chip has embedded PHYs and VLAN support so we model it
> using DSA as a best fit so we can easily add VLAN support and maybe
> later also exploit the internal frame header to get more direct
> control over the switch.
> 
> The four built-in GPIO lines are exposed using a standard GPIO chip.
> 
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Update .get_strings() and .get_sset_count() to match the signature
>   with the new argument for sset type.
> - Drop DSA trailer select from Kconfig.
> - Use MII_* namespace definitions instead of hard-coded hex
>   values and calls to read into the PHY: instead use the genphy
>   decoded link state already present in the phydev.
> - Drop extraneous port number check in .enable() and .disable(),
>   this should not happen.
> - Move the GPIO chip set-up into a separate function.
> - Add some missing static in front of a counter function.
> - Drop the bool flags in the state container, use some macros with
>   the chipid to identify model instead like IS_VSC739X().
> - Check phydev->interface() for configuring the CPU port into
>   RGMII mode.

Applied.

  reply	other threads:[~2018-07-04  2:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 11:17 [PATCH 1/3 v2] net: dsa: Add DT bindings for Vitesse VSC73xx switches Linus Walleij
2018-06-30 11:17 ` [PATCH 2/3 v2] net: phy: vitesse: Add support for VSC73xx Linus Walleij
2018-07-04  2:32   ` David Miller
2018-06-30 11:17 ` [PATCH 3/3 v2] net: dsa: Add Vitesse VSC73xx DSA router driver Linus Walleij
2018-07-04  2:32   ` David Miller [this message]
2018-07-04  2:32 ` [PATCH 1/3 v2] net: dsa: Add DT bindings for Vitesse VSC73xx switches David Miller

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=20180704.113240.652641829194832375.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=juhosg@openwrt.org \
    --cc=lede-dev@lists.infradead.org \
    --cc=linus.walleij@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=vivien.didelot@savoirfairelinux.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