On Thu, Jul 22, 2021 at 12:45:06AM +0200, Pavel Machek wrote:
> Hi!
>
> > Also, function is totally unclear. The whole reason we want to use
> > Linux LEDs is triggers, and it is the selected trigger which
> > determines the function.
>
> Usually, yes. But "function" is what _manufacturer_ wanted LED to
> mean
So you are saying the function should be the reset default of the PHY,
or MAC?
> > Colour is also an issue. The IGC Ethernet controller has no idea what
> > colour the LEDs are in the RG-45 socket. And this is generic to
> > Ethernet MAC and PHY chips. The data sheets never mention colour.
>
> Maybe datasheet does not mention color, but the LED _has_ color.
Sure it does, but the driver is for the LED controller, not the
LED. The controller does not care what colour the LED is. At least for
this application.
> > might know the colour in DT (and maybe ACPI) systems where you have
> > specific information about the board. But in for PCIe card, USB
> > dongles, etc, colour is unknown.
>
> Not.. really. You don't know from chip specificiations, but you should
> know the color as soon as you have USB IDs (because they should tell
> you exact hardware).
No. All it tells you is what the controller is. The dongle manufacture
can pair any RJ-45 socket with the controller, and it is the RJ-45
socket which provides the LED.
> And I believe same is true for PCIe cards.
Also not true. The PCIe IDs tell you the controller. What RJ-45 socket
is connected is up to the board manufacture.
> Anyway, you can leave the color field empty if you don't know.
That is the more likely case.
Andrew
