[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200910203923.GA19655@ucw.cz>
Date: Thu, 10 Sep 2020 22:39:23 +0200
From: Pavel Machek <pavel@....cz>
To: Andrew Lunn <andrew@...n.ch>
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
Hi!
> > We already have different support for blinking in LED subsystem. Lets use that.
>
> You are assuming we have full software control of the LED, we can turn
> it on and off. That is not always the case. But there is sometimes a
> mode which the hardware blinks the LED.
Please see "timer" trigger support in the LED subsystem. We already
have hardware-accelerated blinking for the LEDs, and phy LEDs should
use same mechanism.
> Being able to blink the LED is useful: ethtool(1): -p --identify
...and yes, it should work for ethtool, too.
See leds-ss4200.c: nasgpio_led_set_blink() for an example. (But it may
not be good example).
Best regards,
Pavel
Powered by blists - more mailing lists