On Fri 2019-08-16 14:27:28, Matthias Kaehlcke wrote: > On Fri, Aug 16, 2019 at 10:13:42PM +0200, Pavel Machek wrote: > > On Tue 2019-08-13 12:11:47, Matthias Kaehlcke wrote: > > > Add a .config_led hook which is called by the PHY core when > > > configuration data for a PHY LED is available. Each LED can be > > > configured to be solid 'off, solid 'on' for certain (or all) > > > link speeds or to blink on RX/TX activity. > > > > > > Signed-off-by: Matthias Kaehlcke <mka@xxxxxxxxxxxx> > > > > THis really needs to go through the LED subsystem, > > Sorry, I used what get_maintainers.pl threw at me, I should have > manually cc-ed the LED list. > > > and use the same userland interfaces as the rest of the system. > > With the PHY maintainers we discussed to define a binding that is > compatible with that of the LED one, to have the option to integrate > it with the LED subsystem later. The integration itself is beyond the > scope of this patchset. Yes, I believe the integration is neccessary. Using same binding is neccessary for that, but not sufficient. For example, we need compatible trigger names, too. So... I'd really like to see proper integration is possible before we merge this. Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
