From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: linux-input@vger.kernel.org
Cc: linux-usb@vger.kernel.org, Oliver Neukum <oliver@neukum.org>,
Chris Healy <chealy@imsco-us.com>
Subject: [PATCH 1/3] Input: add new keycodes for passenger control units
Date: Mon, 18 Feb 2013 11:05:55 -0800 [thread overview]
Message-ID: <1361214357-21205-2-git-send-email-dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <1361214357-21205-1-git-send-email-dmitry.torokhov@gmail.com>
Entertainment systems used in aircraft need additional keycodes for their
Passenger Control Units, so let's add them.
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
---
include/uapi/linux/input.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/uapi/linux/input.h b/include/uapi/linux/input.h
index 54a3b49..e6d9609 100644
--- a/include/uapi/linux/input.h
+++ b/include/uapi/linux/input.h
@@ -702,6 +702,11 @@ struct input_keymap_entry {
#define KEY_CAMERA_LEFT 0x219
#define KEY_CAMERA_RIGHT 0x21a
+#define KEY_ATTENDANT_ON 0x21b
+#define KEY_ATTENDANT_OFF 0x21c
+#define KEY_ATTENDANT_TOGGLE 0x21d /* Attendant call on or off */
+#define KEY_LIGHTS_TOGGLE 0x21e /* Reading light on or off */
+
#define BTN_TRIGGER_HAPPY 0x2c0
#define BTN_TRIGGER_HAPPY1 0x2c0
#define BTN_TRIGGER_HAPPY2 0x2c1
--
1.7.11.7
next prev parent reply other threads:[~2013-02-18 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 19:05 [PATCH 0/3] Introduce driver for IMS PCU devices Dmitry Torokhov
2013-02-18 19:05 ` Dmitry Torokhov [this message]
2013-02-18 19:05 ` [PATCH 2/3] Input: add IMS Passenger Control Unit driver Dmitry Torokhov
2013-02-18 19:05 ` [PATCH 3/3] USB: cdc-acm - blacklist IMS PCU device Dmitry Torokhov
[not found] ` <1361214357-21205-4-git-send-email-dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-02-18 19:10 ` Greg KH
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=1361214357-21205-2-git-send-email-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=chealy@imsco-us.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.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).