[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180206165009.GJ12679@lunn.ch>
Date: Tue, 6 Feb 2018 17:50:09 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Sven Van Asbroeck <thesven73@...il.com>
Cc: Sven Van Asbroeck <svendev@...x.com>, Woojung.Huh@...rochip.com,
Tristram.Ha@...rochip.com, f.fainelli@...il.com,
helmut.buchsbaum@...il.com, Maarten.Blomme@...r.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
netdev@...r.kernel.org
Subject: Re: [PATCH v1 0/1] spi_ks8995: use regmap to access chip registers.
On Tue, Feb 06, 2018 at 11:41:14AM -0500, Sven Van Asbroeck wrote:
> On Tue, Feb 6, 2018 at 11:14 AM, Andrew Lunn <andrew@...n.ch> wrote:
> > Rather than invest time in this driver, it would be better to look
> > into writing a DSA driver.
>
> Thank you Andrew. I know little of DSA, but at first sight it appears to
> be a _very_ complicated beast for a switch PHY which only
> needs a few static register settings applied to it on startup, and has
> no further Linux interaction?
Hi Sven
If you want to treat it as a dumb switch, then a simple driver is
sufficient. But it can do a lot more. Do you need spanning tree, or
are you happy for your network to collapse if there is a loop? Do you
want access to statistics? Know if links are up/down? VLAN support?
Save some power by enabling EEE? DSA will give you these features.
And a DSA driver does not need to be complex. You can start simple,
and add more features later.
Andrew
Powered by blists - more mailing lists