On Thu, Sep 10, 2020 at 08:24:34PM +0200, Pavel Machek wrote:
> On Thu 2020-09-10 15:15:41, Andrew Lunn wrote:
> > 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@xxxxxx>
> > >
> > > 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.
>
> Well, this should really go to the sysfs documenation. Not sure what
> to do with DT.
In DT you can set how you want the LED to blink by default. I expect
that will be the most frequent use cases, and nearly nobody will
change it at runtime.
> But perhaps driver can set reasonable defaults without DT input?
Generally the driver will default to the hardware reset blink
pattern. There are a few PHY drivers which change this at probe, but
not many. The silicon defaults are pretty good.
Andrew
