From: Joe Perches <joe@perches.com>
To: "Gaël PORTAY" <g.portay@overkiz.com>
Cc: Rob Landley <rob@landley.net>, Bryan Wu <cooloney@gmail.com>,
Richard Purdie <rpurdie@rpsys.net>,
"Milo(Woogyom) Kim" <milo.kim@ti.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [RFC PATCH] led: add Cycle LED trigger.
Date: Thu, 20 Jun 2013 11:12:54 -0700 [thread overview]
Message-ID: <1371751974.2146.21.camel@joe-AO722> (raw)
In-Reply-To: <51C2CF0B.1010007@overkiz.com>
On Thu, 2013-06-20 at 11:44 +0200, Gaël PORTAY wrote:
> On 19/06/2013 00:05, Joe Perches wrote:
> > On Tue, 2013-06-18 at 18:24 +0200, Gaël PORTAY wrote:
> >> Currently, none of available triggers supports playing with the LED brightness
> >> level. The cycle trigger provides a way to define custom brightness cycle.
[]
> > I think maybe this is a userspace thing,
[]
> About the kernel/user space discussion, I'd rather keep the cycle
> trigger implementation in the kernel space,
> because it implies brightness change every 10-100ms or less. This leads
> to lots of context switches, and I'm not
> even sure the user space can handle such timings accurately.
Hi Gaël
No big concern other than maybe that's best done
in user space. Try it. If it doesn't work well,
then send the kernel patch with a description why
it doesn't work well in user-space.
cheers, Joe
next prev parent reply other threads:[~2013-06-20 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 16:24 Gaël PORTAY
2013-06-18 22:05 ` Joe Perches
2013-06-20 9:44 ` Gaël PORTAY
2013-06-20 17:58 ` Bryan Wu
2013-06-27 13:00 ` Gaël PORTAY
2013-06-20 18:12 ` Joe Perches [this message]
2013-06-22 11:26 ` Pavel Machek
2013-06-22 16:43 ` Sebastian Reichel
2013-06-22 19:45 ` Pavel Machek
2013-06-27 13:40 ` Gaël PORTAY
2013-06-23 9:53 ` Pavel Machek
2013-06-22 19:51 ` Geert Uytterhoeven
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=1371751974.2146.21.camel@joe-AO722 \
--to=joe@perches.com \
--cc=cooloney@gmail.com \
--cc=g.portay@overkiz.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=milo.kim@ti.com \
--cc=rob@landley.net \
--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
all inboxes | Powered by JetHome®