linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: Joe Xue <lgxue@hotmail.com>,
	"cooloney@gmail.com" <cooloney@gmail.com>,
	"rpurdie@rpsys.net" <rpurdie@rpsys.net>,
	"rob@landley.net" <rob@landley.net>,
	"milo.kim@ti.com" <milo.kim@ti.com>,
	"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] Add the LED burst trigger
Date: Fri, 27 Dec 2013 14:18:26 +0000	[thread overview]
Message-ID: <20131227141826.3fe406e4@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20131227125725.GA21506@amd.pavel.ucw.cz>

> At least nokia N900 actually has "hardware acceleration" for LED
> blinking. (Tiny CPU connected over i2c, able to control 3 LEDs, turing
> complete with something like 20 _bits_ of storage and 30 program
> steps). Apparently, it makes more stable patterns (timing is very hard
> to guarantee from userspace) and better power consumption (no need to
> wake the CPU to blink the LEDs).
> 
> Now, wins from going userspace->kernel will not be too huge. But "If
> the hardware can accelerate it, kernel should offer it even on
> hardware that can not do it, for consistency".

Why ? My x86-64 box can run with 8GB processes, perhaps we should emulate
64bit on a 32bit kernel for consistency ?

It's another waste of resources - pages of memory that would cumulatively
be vastly more efficiently used by user space. Yes the N800 might want a
little driver but the rest belongs in a library and the library can use
accelerators (of any kind) if available, or even things like lightbulbs
via X10 so you can have the big red light in the control room flash if
the machine dies  8)

Alan

  reply	other threads:[~2013-12-27 14:18 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24 14:30 [PATCH] Add the LED burst trigger lgxue
2013-12-25 23:09 ` Pavel Machek
2013-12-26  1:02   ` Joe Xue
2013-12-26 14:26     ` Pavel Machek
2013-12-26 15:02       ` Joe Xue
2013-12-26 16:58         ` Joe Xue
2013-12-27 12:39           ` Rob Landley
2013-12-27 13:05             ` Pavel Machek
2013-12-27  0:31       ` Joe Xue
2013-12-27  9:57         ` Pavel Machek
2013-12-28  2:08           ` Joe Xue
2013-12-28 10:16             ` Pavel Machek
2013-12-28 13:39               ` Joe Xue
2013-12-28 19:26                 ` Pavel Machek
2013-12-29  0:23                   ` Joe Xue
2013-12-29 10:58                     ` Pavel Machek
2013-12-28 18:51               ` Geert Uytterhoeven
2013-12-28 19:29                 ` how to represent sequence of brightnesses in /sys (was Re: [PATCH] Add the LED burst trigger) Pavel Machek
2013-12-28 19:34                   ` Geert Uytterhoeven
2013-12-28 21:25                     ` Pavel Machek
2013-12-28 21:50                       ` Greg KH
2013-12-28 23:50                         ` Pavel Machek
2013-12-29  1:43                           ` Greg KH
2013-12-29 11:21                             ` Pavel Machek
2014-01-03  0:16                               ` Bryan Wu
2014-01-06  0:37                                 ` Pavel Machek
2013-12-27 12:33         ` [PATCH] Add the LED burst trigger Geert Uytterhoeven
2013-12-27 11:57     ` One Thousand Gnomes
2013-12-27 12:57       ` Pavel Machek
2013-12-27 14:18         ` One Thousand Gnomes [this message]
2013-12-27 15:23           ` Pavel Machek
2013-12-27 18:13             ` One Thousand Gnomes
2013-12-27 18:34               ` Geert Uytterhoeven
2013-12-27 19:37               ` Pavel Machek
2013-12-27 22:45               ` Richard Purdie
2013-12-26 11:18 ` Geert Uytterhoeven
2013-12-30  0:15 ` Joe Xue
  -- strict thread matches above, loose matches on Subject: below --
2013-12-26 16:01 lgxue

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=20131227141826.3fe406e4@alan.etchedpixels.co.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=cooloney@gmail.com \
    --cc=lgxue@hotmail.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=pavel@ucw.cz \
    --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;
as well as URLs for NNTP newsgroup(s).