[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070702125618.GA18987@suse.de>
Date: Mon, 2 Jul 2007 14:56:18 +0200
From: Bernhard Walle <bwalle@...e.de>
To: Andi Kleen <ak@...e.de>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Indan Zupancic <indan@....nu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Stephen Hemminger <shemminger@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: blink driver power saving
* Andi Kleen <ak@...e.de> [2007-07-02 14:39]:
>
> > Another option would be for it not use panic_blink. Do your kexec
> > kernels have atkbd support enabled? You could write an new "blink"
> > input handler that would latch to keyboards supporting leds and blink
> > by sending EV_LED events.
>
> Yes that would be probably a better implementation. Also hook something
> for USB keyboards. iirc Bernhard Walle (cc'ed) was looking at that.
The problem is that most distributions use USB as module (in initrd,
or later). If you're able to load modules, you're also able to run a
userspace programs that blinks. That's the way I implemented it in
SUSE now. In my tests it takes about < 5 seconds from the sysrq-c to
the time the first blink. That's ok IMO.
And if a person compiles his kernel manually, he doesn't need keyboard
LED blinking for kdump because he can look at the HDD LED to see what
happens (or serial console). ... :)
I don't know if it's worth to apply a patch that uses the keyboard
interface in the kernel, because there are several small changes
necessary (see patch, that's what my thought was).
Thanks,
Bernhard
View attachment "add_setledstate_global" of type "text/plain" (1083 bytes)
Powered by blists - more mailing lists