On Thu, Oct 13, 2016 at 10:46:34AM -0400, David Miller wrote:
> From: Zach Brown
> Date: Tue, 11 Oct 2016 15:26:20 -0500
>
> > From: Josh Cartwright
> >
> > Create an option CONFIG_LED_TRIGGER_PHY (default n), which will
> > create a set of led triggers for each instantiated PHY device. There
> Do you have suggestions on how to better handle the choice of the array size
> and the speeds?
phydev->supported lists the speeds this phy supports.
Andrew
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject
From: Zach Brown
Date: Thu, 13 Oct 2016 10:42:46 -0500
> Do you have suggestions on how to better handle the choice of the array size
> and the speeds?
All of the speed values are simply the rate in bits per second.
There is therefore no reason you can't just print the raw value and
scale it to
From: Zach Brown
Date: Tue, 11 Oct 2016 15:26:20 -0500
> From: Josh Cartwright
>
> Create an option CONFIG_LED_TRIGGER_PHY (default n), which will
> create a set of led triggers for each instantiated PHY device. There is
> one LED trigger per link-speed, per-phy.
>
> This allows for a user to
From: Josh Cartwright
Create an option CONFIG_LED_TRIGGER_PHY (default n), which will
create a set of led triggers for each instantiated PHY device. There is
one LED trigger per link-speed, per-phy.
This allows for a user to configure their system to allow a set of LEDs
to represent link state
