linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Pavel Machek <pavel@ucw.cz>, Joe Xue <lgxue@hotmail.com>,
	"cooloney@gmail.com" <cooloney@gmail.com>,
	"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 22:45:01 +0000	[thread overview]
Message-ID: <1388184301.11527.29.camel@ted> (raw)
In-Reply-To: <20131227181349.475abe88@alan.etchedpixels.co.uk>

On Fri, 2013-12-27 at 18:13 +0000, One Thousand Gnomes wrote:
> > Well, this one will be really smaller. And yes, it will make some
> > memory non-swappable, but I believe with triggers and infrastructure
> > for N900 (and similar) it will be worth it.
> 
> Ah yes thats such a major proportion of platforms
> 
> > Plus, it will actually save CPU cycles, and thus significant power.
> 
> All of which will be totally wiped out if you bump all the millions of
> x86 server boxes in the world up by one page of kernel space and cause a
> few disk I/Os

FWIW the LED subsystem was designed to take advantage of kernel modules.
If you don't use a given trigger, it needn't be in memory, loaded or
even built at all. If something changed there which made that not
possible, that would be rather sad.

I agree with you that we shouldn't bump the kernel size unnecessarily
but I don't think triggers should do so. I actually think the kernel
could do with going on a diet and at least made so you can untangle more
of the pieces you don't want/need.

Cheers,

Richard


  parent reply	other threads:[~2013-12-27 22:45 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
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 [this message]
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=1388184301.11527.29.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=cooloney@gmail.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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 \
    /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).