[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dc8c8a5b-8922-4c0e-95d8-7914ea6272d3@lunn.ch>
Date: Mon, 29 May 2023 19:07:36 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Christian Marangi <ansuelsmth@...il.com>
Cc: Pavel Machek <pavel@....cz>, Lee Jones <lee@...nel.org>,
Jonathan Corbet <corbet@....net>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, linux-leds@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [net-next PATCH v4 03/13] Documentation: leds: leds-class:
Document new Hardware driven LEDs APIs
On Mon, May 29, 2023 at 06:32:33PM +0200, Christian Marangi wrote:
> Document new Hardware driven LEDs APIs.
>
> Some LEDs can be programmed to be driven by hardware. This is not
> limited to blink but also to turn off or on autonomously.
> To support this feature, a LED needs to implement various additional
> ops and needs to declare specific support for the supported triggers.
>
> Add documentation for each required value and API to make hw control
> possible and implementable by both LEDs and triggers.
>
> Signed-off-by: Christian Marangi <ansuelsmth@...il.com>
Reviewed-by: Andrew Lunn <andrew@...n.ch>
Andrew
Powered by blists - more mailing lists