All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 01/17] leds: create a trigger for CPU activity
Date: Wed, 6 Jul 2011 14:35:01 +0100	[thread overview]
Message-ID: <20110706133501.GY8286@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAMPhdO9QmCpGFB8fd5Rp-a0iAv1ByA962FZKOwc59R86OTpxAQ@mail.gmail.com>

On Wed, Jul 06, 2011 at 09:16:47PM +0800, Eric Miao wrote:
> On Wed, Jul 6, 2011 at 8:34 PM, Bryan Wu <bryan.wu@canonical.com> wrote:
> > + ? ? ? switch (ledevt) {
> > + ? ? ? case CPU_LED_START:
> > + ? ? ? case CPU_LED_IDLE_START:
> > + ? ? ? ? ? ? ? /* Will turn the LED on, max brightness */
> > + ? ? ? ? ? ? ? if (trigdata->led)
> > + ? ? ? ? ? ? ? ? ? ? ? led_set_brightness(trigdata->led,
> > + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?trigdata->led->max_brightness);
> > + ? ? ? ? ? ? ? break;
> > +
> > + ? ? ? case CPU_LED_STOP:
> > + ? ? ? case CPU_LED_IDLE_END:
> > + ? ? ? case CPU_LED_HALTED:
> > + ? ? ? ? ? ? ? /* Will turn the LED off */
> > + ? ? ? ? ? ? ? if (trigdata->led)
> > + ? ? ? ? ? ? ? ? ? ? ? led_set_brightness(trigdata->led, LED_OFF);
> > + ? ? ? ? ? ? ? break;
> > +
> > + ? ? ? default:
> > + ? ? ? ? ? ? ? /* Will leave the LED as it is */
> > + ? ? ? ? ? ? ? break;
> > + ? ? ? }
> > +}
> 
> I'm a bit worrying about the LED brightness hardcoded here, what if
> a platform requires different behavior, e.g. LED_OFF when IDLE_START.

Indeed - there are platforms (Netwinder, Assabet etc) which use LED=ON
to mean that the system is not idle - and also turn the LED on when
halted.

A change of behaviour could be fairly disasterous too.  Eg, some people
use Netwinders in a stand-alone mode, and getting the LED behaviour correct
is _critical_ as it is the only display that some people may see - and
they may use that display to decide whether they can pull the power after
shutdown.  Changing it may mean that they end up pulling the power while
the system is still alive.

  reply	other threads:[~2011-07-06 13:35 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 12:34 [PATCH 00/17] Introduce a led trigger for CPU activity Bryan Wu
2011-07-06 12:34 ` [PATCH 01/17] leds: create a " Bryan Wu
2011-07-06 13:16   ` Eric Miao
2011-07-06 13:35     ` Russell King - ARM Linux [this message]
2011-07-06 14:11       ` Nicolas Pitre
2011-07-07 12:58     ` Bryan Wu
2011-07-06 12:34 ` [PATCH 02/17] arm: at91: convert old leds drivers to gpio_led and led_trigger drivers Bryan Wu
2011-07-06 12:34 ` [PATCH 03/17] mach-realview: retire custom LED code Bryan Wu
2011-07-10  9:27   ` Russell King - ARM Linux
2011-07-11 14:13     ` Bryan Wu
2011-07-06 12:34 ` [PATCH 04/17] mach-versatile: " Bryan Wu
2011-07-10  9:28   ` Russell King - ARM Linux
2011-07-11 14:02     ` Bryan Wu
2011-07-12 11:12       ` Linus Walleij
2011-07-06 12:34 ` [PATCH 05/17] mach-ks8695: remove leds driver, since nobody use it Bryan Wu
2011-07-08 20:23   ` Andrew Victor
2011-07-11 11:11     ` Sergei Shtylyov
2011-07-11 13:48       ` Bryan Wu
2011-07-11 14:00         ` Nicolas Pitre
2011-07-11 14:07           ` Bryan Wu
2011-07-11 14:30             ` Andrew Victor
2011-07-06 12:34 ` [PATCH 06/17] mach-shark: retire custom LED code Bryan Wu
2011-07-10  9:30   ` Russell King - ARM Linux
2011-07-11 14:19     ` Bryan Wu
2011-07-06 12:34 ` [PATCH 07/17] mach-orion5x: convert custom LED code to gpio_led and LED CPU trigger Bryan Wu
2011-07-06 14:05   ` Nicolas Pitre
2011-07-06 12:34 ` [PATCH 08/17] mach-integrator: retire custom LED code Bryan Wu
2011-07-10  9:33   ` Russell King - ARM Linux
2011-07-19 16:20     ` Linus Walleij
2011-07-06 12:34 ` [PATCH 09/17] mach-clps711x: retire custom LED code of P720T machine Bryan Wu
2011-07-06 12:34 ` [PATCH 10/17] mach-ebsa110: retire custom LED code Bryan Wu
2011-07-10  9:36   ` Russell King - ARM Linux
2011-07-06 12:34 ` [PATCH 11/17] mach-footbridge: " Bryan Wu
2011-07-10  9:37   ` Russell King - ARM Linux
2011-07-11 14:25     ` Bryan Wu
2011-07-06 12:34 ` [PATCH 12/17] mach-pxa: " Bryan Wu
2011-07-10  9:37   ` Russell King - ARM Linux
2011-07-11 14:28     ` Bryan Wu
2011-07-06 12:34 ` [PATCH 13/17] plat-samsung: remove including old leds event API header file Bryan Wu
2011-07-06 12:34 ` [PATCH 14/17] mach-pnx4008: " Bryan Wu
2011-07-06 12:34 ` [PATCH 15/17] mach-omap1: retire custom LED code Bryan Wu
2011-07-07 14:29   ` Tony Lindgren
2011-07-06 12:34 ` [PATCH 16/17] mach-sa1100: " Bryan Wu
2011-07-06 14:04   ` Jochen Friedrich
2011-07-07 13:40     ` Bryan Wu
2011-07-07 16:23       ` Jochen Friedrich
2011-07-08  3:00         ` Bryan Wu
2011-07-08 16:10           ` Jochen Friedrich
2011-07-08 17:07             ` Russell King - ARM Linux
2011-07-10  9:24   ` Russell King - ARM Linux
2011-07-11  8:28     ` Jochen Friedrich
2011-07-11 14:38       ` Bryan Wu
2011-07-11 14:36     ` Bryan Wu
2011-07-11 21:09       ` Russell King - ARM Linux
2011-07-11 21:52         ` Arnd Bergmann
2011-07-12  0:31           ` Bryan Wu
2011-07-12  7:30             ` Russell King - ARM Linux
2011-07-12 12:52               ` Arnd Bergmann
2011-07-06 12:34 ` [PATCH 17/17] ARM: use new LEDS CPU trigger stub to replace old one Bryan Wu
2011-07-06 14:26   ` Arnd Bergmann
2011-07-06 13:13 ` [PATCH 00/17] Introduce a led trigger for CPU activity Eric Miao
2011-07-06 13:16   ` Russell King - ARM Linux
2011-07-06 13:19     ` Eric Miao
2011-07-06 13:47     ` Nicolas Pitre
2011-07-07 12:54     ` Bryan Wu
2011-08-03  9:34 [PATCH v2 00/17] Introduce a led trigger for CPU activity and consolidate LED driver in ARM Bryan Wu
2011-08-03  9:34 ` [PATCH 01/17] leds: create a trigger for CPU activity Bryan Wu
2011-08-03 10:23   ` Michał Mirosław
2011-08-04  9:18     ` Bryan Wu
2011-08-03 10:28   ` Jamie Iles
2011-08-03 15:22     ` Linus Walleij
2011-08-03 15:30       ` Jamie Iles
2011-08-03 16:02         ` Jochen Friedrich
2011-08-03 16:12         ` Linus Walleij
2011-08-05  9:48           ` Bryan Wu

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=20110706133501.GY8286@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.