From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH] Input: Add keycodes for touchpad on/off keys
Date: Mon, 8 Nov 2010 23:39:54 -0800 [thread overview]
Message-ID: <20101109073953.GA14177@core.coreip.homeip.net> (raw)
In-Reply-To: <1289220130.5418.109.camel@novo.hadess.net>
On Mon, Nov 08, 2010 at 12:42:10PM +0000, Bastien Nocera wrote:
> Some laptops will have a "touchpad toggle" soft button, which
> expects user-space to turn off the touchpad themselves, some
> other devices will do this in hardware, but send key events telling
> us that the touchpad has been turned off/on.
>
> KEY_TOUCHPAD_ON/KEY_TOUCHPAD_OFF will be used by user-space to
> show a popup with the status of the touchpad.
>
> Signed-Off-By: Bastien Nocera <hadess@hadess.net>
> ---
> include/linux/input.h | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/input.h b/include/linux/input.h
> index 896a922..46dca75 100644
> --- a/include/linux/input.h
> +++ b/include/linux/input.h
> @@ -545,6 +545,10 @@ struct input_absinfo {
> #define KEY_CONTEXT_MENU 0x1b6 /* GenDesc - system context menu */
> #define KEY_MEDIA_REPEAT 0x1b7 /* Consumer - transport control */
>
> +#define KEY_TOUCHPAD_TOGGLE 0x1b8 /* Ask user-space to switch the touchpad off */
Just off or is it true toggle?
> +#define KEY_TOUCHPAD_ON 0x1b9 /* Tell user-space touchpad is now on */
> +#define KEY_TOUCHPAD_OFF 0x1ba /* As above but off */
I do not like the idea that keycodes are limited to signalling the
state. Either they can also request the transition to given state or we
need to find some other way to communicate the state.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2010-11-09 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 12:42 [PATCH] Input: Add keycodes for touchpad on/off keys Bastien Nocera
2010-11-09 7:39 ` Dmitry Torokhov [this message]
2010-11-09 11:13 ` Bastien Nocera
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=20101109073953.GA14177@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
/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).