From: Richard Purdie <rpurdie@rpsys.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: Further document parameters for blink_set()
Date: Mon, 22 Jun 2009 14:51:30 +0100 [thread overview]
Message-ID: <1245678690.10200.13.camel@dax.rpnet.com> (raw)
In-Reply-To: <20090621063936.GA1656@ucw.cz>
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@opensource.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
prev parent reply other threads:[~2009-06-22 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 13:17 Mark Brown
2009-06-21 6:39 ` Pavel Machek
2009-06-22 13:51 ` Richard Purdie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1245678690.10200.13.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®