Re: [PATCH] input: extend EV_LED

On 2/11/07, Németh Márton <[email protected]> wrote:

Extend EV_LED handling code so that it can handle not
only two states (on/off) but also others. For example
a LED can blink using hardware acceleration. The code
changed so that it is similar to the code at EV_SND.

Hi,

I am not sure we would need this, could you explain what are you
trying to use input leds for?

Generally speaking leds within input subsystem are supposed to be very
simple on/off objects, mostly for reporting state of input devices
(keyboards), I am not even sure that LED_MAIL and LED_CHARGING make
much sense here. For more compex objects(blinking/different
colors/different brightness) we have a separate LED subsystem
(drivers/leds).

--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] input: extend EV_LED
    • From: Németh Márton <[email protected]>

• References:
  • [PATCH] input: extend EV_LED
    • From: Németh Márton <[email protected]>

• Prev by Date: [PATCH 2/3] fs/: Move eCryptfs & Unionfs config options into a sub-menu
• Next by Date: Re: [PATCH 3/7] containers (V7): Add generic multi-subsystem API to containers
• Previous by thread: [PATCH] input: extend EV_LED
• Next by thread: Re: [PATCH] input: extend EV_LED
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]