From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Richard Purdie <rpurdie@rpsys.net>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] led-class: always implement blinking
Date: Tue, 21 Sep 2010 21:51:52 +0200 [thread overview]
Message-ID: <1285098712.12764.19.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1285098497.12764.18.camel@jlt3.sipsolutions.net>
On Tue, 2010-09-21 at 21:48 +0200, Johannes Berg wrote:
> Well, this function gets assigned to led_cdev->blink_set(), which is a
> function pointer that takes pass-by-reference arguments. The comment
> there says:
>
> /* Activate hardware accelerated blink, delays are in
> * miliseconds and if none is provided then a sensible default
> * should be chosen. The call can adjust the timings if it can't
> * match the values specified exactly. */
> int (*blink_set)(struct led_classdev *led_cdev,
> unsigned long *delay_on,
> unsigned long *delay_off);
>
> but the software implementation doesn't adjust the timings, of course. I
> suppose the "adjust the timings" was also meant to update the values.
But I should update this and the other documentation ... and also
provide a wrapper, because blink_set() is allowed to fail, in which
software fallback should be used.
johannes
next prev parent reply other threads:[~2010-09-21 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 9:21 Johannes Berg
2010-09-16 12:04 ` Johannes Berg
2010-09-21 19:44 ` Andrew Morton
2010-09-21 19:48 ` Johannes Berg
2010-09-21 19:51 ` Johannes Berg [this message]
2010-09-21 21:24 ` Richard Purdie
2010-09-22 8:56 ` Johannes Berg
2010-09-22 9:45 ` [PATCH v2] " Johannes Berg
2010-09-22 13:53 ` [PATCH v3] " Johannes Berg
2010-09-23 22:35 ` Andrew Morton
2010-09-24 9:29 ` Johannes Berg
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=1285098712.12764.19.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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
Powered by JetHome