From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dmitry Torokhov" Subject: Re: [PATCH] input: extend EV_LED Date: Mon, 12 Feb 2007 13:31:52 -0500 Message-ID: References: <45CEE9AB.2020208@freemail.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <45CEE9AB.2020208@freemail.hu> Content-Disposition: inline Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: =?ISO-8859-1?Q?N=E9meth_M=E1rton?= Cc: linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org List-Id: linux-input@vger.kernel.org On 2/11/07, N=E9meth M=E1rton 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). --=20 Dmitry