[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <871qiz5iqt.fsf@meer.lwn.net>
Date: Mon, 29 May 2023 08:12:42 -0600
From: Jonathan Corbet <corbet@....net>
To: Bagas Sanjaya <bagasdotme@...il.com>,
Christian Marangi <ansuelsmth@...il.com>,
Pavel Machek <pavel@....cz>, Lee Jones <lee@...nel.org>,
Andrew Lunn <andrew@...n.ch>,
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 v3 03/13] Documentation: leds: leds-class:
Document new Hardware driven LEDs APIs
Bagas Sanjaya <bagasdotme@...il.com> writes:
>> + - hw_control_get_device:
>> + return the device associated with the LED driver in
>> + hw control. A trigger might use this to match the
>> + returned device from this function with a configured
>> + device for the trigger as the source for blinking
>> + events and correctly enable hw control.
>> + (example a netdev trigger configured to blink for a
>> + particular dev match the returned dev from get_device
>> + to set hw control)
>> +
>> + Return a device or NULL if nothing is currently attached.
> Returns a device name?
The return type of this function is struct device * - how would you
expect it to return a name?
jon
Powered by blists - more mailing lists