From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: extend EV_LED
Date: Mon, 12 Feb 2007 13:31:52 -0500 [thread overview]
Message-ID: <d120d5000702121031o1ea5ff20lf4e0946c8c1e2980@mail.gmail.com> (raw)
In-Reply-To: <45CEE9AB.2020208@freemail.hu>
On 2/11/07, Németh Márton <nm127@freemail.hu> 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
next prev parent reply other threads:[~2007-02-12 18:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-11 10:02 [PATCH] input: extend EV_LED Németh Márton
2007-02-12 18:31 ` Dmitry Torokhov [this message]
2007-02-14 19:06 ` Németh Márton
2007-02-14 19:49 ` Dmitry Torokhov
2007-02-14 23:51 ` Németh Márton
2007-02-15 17:40 ` Pavel Machek
2007-02-15 22:47 ` Németh Márton
2007-02-15 23:09 ` Richard Purdie
2007-02-15 23:24 ` Pavel Machek
2007-02-15 23:36 ` Richard Purdie
2007-02-16 3:12 ` Henrique de Moraes Holschuh
2007-02-18 11:05 ` Richard Purdie
2007-02-18 14:42 ` Henrique de Moraes Holschuh
2007-02-18 7:45 ` Németh Márton
2007-02-18 8:07 ` Willy Tarreau
2007-02-18 11:12 ` Richard Purdie
2007-02-16 14:04 ` Pavel Machek
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=d120d5000702121031o1ea5ff20lf4e0946c8c1e2980@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=nm127@freemail.hu \
/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).