linux-kernel - Re: [PATCH] Input notifier support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 28 Feb 2009 14:30:05 -0800
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Kyungmin Park <kmpark@...radead.org>
Cc:	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
	Trilok Soni <soni.trilok@...il.com>
Subject: Re: [PATCH] Input notifier support

Hi Kyungmin,

On Wed, Feb 25, 2009 at 01:47:30PM +0900, Kyungmin Park wrote:
> Some hardware doesn't connected with key button and led. In this case
> key should be connected with led by software. Of course each application
> can control it however it's too big burden to application programmer.
> 
> So add input notifier and then use it at other frameworks such as led.
> Of course, other input device can use this one.
> 
> Any commnets are welcome.
> 

I don't think we need to do the notifier route. It is very easy to add
another input handler in style of rfkill-input or apm-power that would
listen to events from all ungrabbed input devices and act accordingly.
Your LED trigger example should work very well if implemented as another
input handler.

Thanks.

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