[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6474b526.050a0220.baa3e.31c1@mx.google.com>
Date: Mon, 29 May 2023 16:09:39 +0200
From: Christian Marangi <ansuelsmth@...il.com>
To: Jonathan Corbet <corbet@....net>
Cc: Bagas Sanjaya <bagasdotme@...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
On Mon, May 29, 2023 at 08:12:42AM -0600, Jonathan Corbet wrote:
> 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?
>
Just to clarify, a device name can't be returned. Not every device have
a name and such name can be changed. An example is network device where
you can change the name of the interface.
Using the device prevents all of this problem.
--
Ansuel
Powered by blists - more mailing lists