From: Kyungmin Park <kmpark@infradead.org>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
dmitry.torokhov@gmail.com
Subject: Re: [PATCH] Input notifier support
Date: Wed, 25 Feb 2009 18:55:58 +0900 [thread overview]
Message-ID: <9c9fda240902250155p107fb657wafcd4aa92f7e093d@mail.gmail.com> (raw)
In-Reply-To: <5d5443650902250003g7df7093bn59e0fc052ffb6ed@mail.gmail.com>
Hi,
On Wed, Feb 25, 2009 at 5:03 PM, Trilok Soni <soni.trilok@gmail.com> wrote:
> Hi Kyungmin,
>
> On Wed, Feb 25, 2009 at 10:17 AM, Kyungmin Park <kmpark@infradead.org> 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.
>>
>
> I am not able to understand this.
it's simple there's one led and it's for key input. so when there's
key input, it's blink. that's all
>
>> So add input notifier and then use it at other frameworks such as led.
>> Of course, other input device can use this one.
>
> If it is just LED, then you may write some led-input-trigger?
Please see the LED key input trigger patch.
Thank you,
Kyungmin Park
next prev parent reply other threads:[~2009-02-25 9:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 4:47 [PATCH] Input notifier support Kyungmin Park
2009-02-25 8:03 ` Trilok Soni
2009-02-25 9:55 ` Kyungmin Park [this message]
2009-02-26 7:01 ` Trilok Soni
2009-02-27 2:11 ` Kyungmin Park
2009-02-27 12:35 ` Trilok Soni
2009-02-28 22:30 ` Dmitry Torokhov
2009-02-28 23:34 ` Andi Kleen
2009-03-01 0:42 ` Dmitry Torokhov
2009-03-01 2:52 ` Kyungmin Park
2009-03-01 3:07 ` Dmitry Torokhov
2009-03-01 3:16 ` Kyungmin Park
2009-03-01 6:29 ` Dmitry Torokhov
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=9c9fda240902250155p107fb657wafcd4aa92f7e093d@mail.gmail.com \
--to=kmpark@infradead.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soni.trilok@gmail.com \
/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).