From: Wu Zhangjin <wuzhangjin@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: akpm@linux-foundation.org, linux-mips@linux-mips.org,
linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"Rafael J . Wysocki" <rjw@sisk.pl>,
zhangfx@lemote.com, linux-laptop@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH v9 8/8] Loongson: YeeLoong: add input/hotkey driver
Date: Fri, 11 Dec 2009 10:47:40 +0800 [thread overview]
Message-ID: <1260499660.3193.17.camel@falcon.domain.org> (raw)
In-Reply-To: <e6d590fa37e6003dd482918fdef02c1fc127d6c8.1260281599.git.wuzhangjin@gmail.com>
On Tue, 2009-12-08 at 22:15 +0800, Wu Zhangjin wrote:
> From: Wu Zhangjin <wuzhangjin@gmail.com>
>
> This patch adds Hotkey Driver, which will do related actions for The
> hotkey event(/sys/class/input) and report the corresponding input keys
> to the user-space applications.
>
> [NOTE:
>
> This patch is based on the sparse keymap library in:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input next
>
> of Dmitry Torokhov. that sparse keymap support is also queued for
> 2.6.33. Before the above branch is pulled by linus, this patch is not
> appliable.]
>
[...]
> +
> +/* yeeloong_wifi_handler may be implemented in the wifi driver */
> +sci_handler yeeloong_wifi_handler;
> +EXPORT_SYMBOL(yeeloong_wifi_handler);
> +
Because we have reported the KEY_WLAN to user-space and If we provide
the standard rfkill interfaces too, there is no need to handle the Fn+F5
event in kernel space, will remove the above three lines the following
related source code.
> +static void do_event_action(int event)
> +{
> + sci_handler handler;
> + int reg, status;
> + struct key_entry *ke;
> +
> + reg = 0;
> + handler = NULL;
> +
> + switch (event) {
[...]
> + case EVENT_WLAN:
> + /* We use 2 to indicate it as a switch */
> + status = 2;
> + handler = yeeloong_wifi_handler;
> + break;
Will remove it and send the this patch as v10 later.
Best Regards,
Wu Zhangjin
prev parent reply other threads:[~2009-12-11 2:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 14:15 [PATCH v9 0/8] Loongson: YeeLoong: add platform drivers Wu Zhangjin
[not found] ` <cover.1260281599.git.wuzhangjin@gmail.com>
2009-12-08 14:15 ` [PATCH v9 1/8] MIPS: add subdirectory for platform extension drivers Wu Zhangjin
2009-12-08 14:15 ` [PATCH v9 2/8] Loongson: YeeLoong: add platform driver Wu Zhangjin
2009-12-08 14:15 ` [PATCH v9 3/8] Loongson: YeeLoong: add backlight driver Wu Zhangjin
2009-12-08 14:15 ` [PATCH v9 4/8] Loongson: YeeLoong: add battery driver Wu Zhangjin
2009-12-08 14:15 ` [PATCH v9 5/8] Loongson: YeeLoong: add hardware monitoring driver Wu Zhangjin
2009-12-08 15:02 ` Pavel Machek
2009-12-09 10:59 ` Wu Zhangjin
2009-12-08 14:15 ` [PATCH v9 6/8] Loongson: YeeLoong: add video output driver Wu Zhangjin
2009-12-08 14:15 ` [PATCH v9 7/8] Loongson: YeeLoong: add suspend support Wu Zhangjin
2009-12-08 14:15 ` [PATCH v9 8/8] Loongson: YeeLoong: add input/hotkey driver Wu Zhangjin
2009-12-11 2:47 ` Wu Zhangjin [this message]
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=1260499660.3193.17.camel@falcon.domain.org \
--to=wuzhangjin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-laptop@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=pavel@ucw.cz \
--cc=ralf@linux-mips.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
--cc=zhangfx@lemote.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
all inboxes | Powered by JetHome®