From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jani Nikula <ext-jani.1.nikula@nokia.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] Input: add new keycodes useful in mobile devices
Date: Fri, 23 Oct 2009 00:13:15 -0700 [thread overview]
Message-ID: <20091023071315.GA3986@core.coreip.homeip.net> (raw)
In-Reply-To: <72a6deb76f693b5e50dbfe150154e7a4724d0568.1256200562.git.ext-jani.1.nikula@nokia.com>
Hi Jani,
On Thu, Oct 22, 2009 at 12:32:20PM +0300, Jani Nikula wrote:
> From: Jani Nikula <ext-jani.1.nikula@nokia.com>
>
> Signed-off-by: Jani Nikula <ext-jani.1.nikula@nokia.com>
> ---
> include/linux/input.h | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/input.h b/include/linux/input.h
> index 0ccfc30..3c246b1 100644
> --- a/include/linux/input.h
> +++ b/include/linux/input.h
> @@ -595,6 +595,8 @@ struct input_absinfo {
> #define KEY_NUMERIC_STAR 0x20a
> #define KEY_NUMERIC_POUND 0x20b
>
> +#define KEY_CAMERA_FOCUS 0x210
I believe that this has already been discussed and I am OK with adding
such keycode, as long and there are in-kernel users.
> +
> /* We avoid low common keys in module aliases so they don't get huge. */
> #define KEY_MIN_INTERESTING KEY_MUTE
> #define KEY_MAX 0x2ff
> @@ -677,6 +679,9 @@ struct input_absinfo {
> #define SW_LINEOUT_INSERT 0x06 /* set = inserted */
> #define SW_JACK_PHYSICAL_INSERT 0x07 /* set = mechanical switch set */
> #define SW_VIDEOOUT_INSERT 0x08 /* set = inserted */
> +#define SW_CAMERA_LENSE_COVER 0x09 /* set = lense covered */
> +#define SW_KEYPAD_SLIDE 0x0a /* set = keypad slide out */
> +#define SW_PROXIMITY 0x0b /* set = proximity sensor covered */
Don't quite like the name for this one, any alternatives?
> #define SW_MAX 0x0f
> #define SW_CNT (SW_MAX+1)
>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2009-10-23 7:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 9:32 [RFC PATCH 0/1] new keycodes Jani Nikula
2009-10-22 9:32 ` [RFC PATCH 1/1] Input: add new keycodes useful in mobile devices Jani Nikula
2009-10-23 7:13 ` Dmitry Torokhov [this message]
2009-10-26 14:43 ` Jani Nikula
2009-10-27 16:20 ` Dmitry Torokhov
2009-10-30 13:38 ` [PATCH 0/3] new input keycodes, gpio-keys for RX-51 Jani Nikula
2009-10-30 13:38 ` [PATCH 1/3] Input: add new keycodes useful in mobile devices Jani Nikula
2009-10-30 13:38 ` [PATCH 2/3] ARM OMAP3: RX-51 board: add initialization of gpio keys Jani Nikula
2009-10-30 13:38 ` [PATCH 3/3] ARM OMAP3: rx51_defconfig: enable support for " Jani Nikula
2009-10-30 17:44 ` Tony Lindgren
2009-10-30 17:43 ` [PATCH 2/3] ARM OMAP3: RX-51 board: add initialization of " Tony Lindgren
2009-10-30 21:41 ` [PATCH 1/3] Input: add new keycodes useful in mobile devices James Mastros
2009-11-04 15:13 ` [PATCH v2 0/2] new input keycodes, gpio-keys for RX-51 Jani Nikula
2009-11-04 15:13 ` [PATCH v2 1/2] Input: add new keycodes useful in mobile devices Jani Nikula
2009-11-04 15:13 ` [PATCH v2 2/2] ARM OMAP3: RX-51 board: add initialization of gpio keys Jani Nikula
2009-11-06 7:40 ` [PATCH v2 0/2] new input keycodes, gpio-keys for RX-51 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=20091023071315.GA3986@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=ext-jani.1.nikula@nokia.com \
--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).