[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200910131541.GD3316362@lunn.ch>
Date: Thu, 10 Sep 2020 15:15:41 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Pavel Machek <pavel@....cz>
Cc: Marek Behún <marek.behun@....cz>,
netdev@...r.kernel.org, linux-leds@...r.kernel.org,
Dan Murphy <dmurphy@...com>,
Ondřej Jirman <megous@...ous.com>,
Russell King <linux@...linux.org.uk>,
linux-kernel@...r.kernel.org,
Matthias Schiffer <matthias.schiffer@...tq-group.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH net-next + leds v2 6/7] net: phy: marvell: add support
for LEDs controlled by Marvell PHYs
On Thu, Sep 10, 2020 at 02:23:41PM +0200, Pavel Machek wrote:
> On Wed 2020-09-09 18:25:51, Marek Behún wrote:
> > This patch adds support for controlling the LEDs connected to several
> > families of Marvell PHYs via the PHY HW LED trigger API. These families
> > are: 88E1112, 88E1121R, 88E1240, 88E1340S, 88E1510 and 88E1545. More can
> > be added.
> >
> > This patch does not yet add support for compound LED modes. This could
> > be achieved via the LED multicolor framework.
> >
> > Settings such as HW blink rate or pulse stretch duration are not yet
> > supported.
> >
> > Signed-off-by: Marek Behún <marek.behun@....cz>
>
> I suggest limiting to "useful" hardware modes, and documenting what
> those modes do somewhere.
I think to keep the YAML DT verification happy, they will need to be
listed in the marvell PHY binding documentation.
Andrew
Powered by blists - more mailing lists