linux-kernel - Re: [PATCH] leds: Further document parameters for blink

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1245678690.10200.13.camel@dax.rpnet.com>
Date:	Mon, 22 Jun 2009 14:51:30 +0100
From:	Richard Purdie <rpurdie@...ys.net>
To:	Pavel Machek <pavel@....cz>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] leds: Further document parameters for blink_set()

On Sun, 2009-06-21 at 08:39 +0200, Pavel Machek wrote:
> On Thu 2009-06-11 14:17:48, Mark Brown wrote:
> > The documentation for the parameters of blink_set() was a bit hard
> > to find so put some where I'd expected to find it.
> > 
> > Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> > ---
> >  include/linux/leds.h |    4 +++-
> >  1 files changed, 3 insertions(+), 1 deletions(-)
> > 
> > diff --git a/include/linux/leds.h b/include/linux/leds.h
> > index 376fe07..c7f0b14 100644
> > --- a/include/linux/leds.h
> > +++ b/include/linux/leds.h
> > @@ -45,7 +45,9 @@ struct led_classdev {
> >  	/* Get LED brightness level */
> >  	enum led_brightness (*brightness_get)(struct led_classdev *led_cdev);
> >  
> > -	/* Activate hardware accelerated blink */
> > +	/* Activate hardware accelerated blink, delays are in
> > +	 * miliseconds and if none is provided then a sensible default
> > +	 * should be chosen. */
> >  	int		(*blink_set)(struct led_classdev *led_cdev,
> >  				     unsigned long *delay_on,
> >  				     unsigned long *delay_off);
> 
> What a strange calling convention. Does it return data in
> *delay_on/off ?

It was done so the caller could find out what timings the underlying
hardware decided to chose if it couldn't match the timings specified
exactly. This should be better documented and I'll take care of that.

Cheers,

Richard

-- 
Richard Purdie
Intel Open Source Technology Centre

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/