mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shelby Heffron <Shelby.Heffron@garmin.com>
To: <dmitry.torokhov@gmail.com>, <linux-input@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: Shelby Heffron <Shelby.Heffron@garmin.com>
Subject: [PATCH v2] input: Add Marine Navigation Keycodes
Date: Wed, 26 Jan 2022 15:12:24 -0600	[thread overview]
Message-ID: <20220126211224.28590-1-Shelby.Heffron@garmin.com> (raw)
In-Reply-To: <20210622235708.8828-1-matthew.stephenson2@garmin.com>

Add keycodes that are used by marine navigation devices

Signed-off-by: Shelby Heffron <Shelby.Heffron@garmin.com>
---
 include/uapi/linux/input-event-codes.h | 28 ++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h
index 225ec87d4f22..26b6a2f482ab 100644
--- a/include/uapi/linux/input-event-codes.h
+++ b/include/uapi/linux/input-event-codes.h
@@ -660,6 +660,34 @@
 /* Select an area of screen to be copied */
 #define KEY_SELECTIVE_SCREENSHOT	0x27a
 
+/* Toggle the focus in or out */
+#define KEY_FOCUS_TOGGLE		0x27b
+
+/* Move between highlightable items */
+#define KEY_NEXT_HIGHLIGHT		0x27c
+#define KEY_PREVIOUS_HIGHLIGHT		0x27d
+
+/* Toggle Autopilot enagement */
+#define KEY_AUTOPILOT_ENGAGE_TOGGLE	0x27e
+
+/* Navigate Displays */
+#define KEY_NEXT_DISPLAY		0x27f
+#define KEY_PREVIOUS_DISPLAY		0x280
+
+/* Shortcut Keys */
+#define KEY_MARK_WAYPOINT		0x281
+#define KEY_SOS			0x282
+#define KEY_NAV_CHART			0x283
+#define KEY_FISHING_CHART		0x284
+#define KEY_SINGLE_RANGE_RADAR		0x285
+#define KEY_DUAL_RANGE_RADAR		0x286
+#define KEY_RADAR_OVERLAY		0x287
+#define KEY_TRADITIONAL_SONAR		0x288
+#define KEY_CLEARVU_SONAR		0x289
+#define KEY_SIDEVU_SONAR		0x28a
+#define KEY_NAV_INFO			0x28b
+#define KEY_BRIGHTNESS_MENU		0x28c
+
 /*
  * Some keyboards have keys which do not have a defined meaning, these keys
  * are intended to be programmed / bound to macros by the user. For most
-- 
2.32.0


  reply	other threads:[~2022-01-26 21:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 23:57 [PATCH] " Matthew Stephenson
2022-01-26 21:12 ` Shelby Heffron [this message]
2022-02-11  4:47   ` [PATCH v2] " Shelby Heffron
2022-02-17 23:41     ` Shelby Heffron
2022-02-18  7:02   ` Dmitry Torokhov
2022-02-18 20:53     ` Shelby Heffron
2022-03-03 23:28     ` Shelby Heffron
2022-03-11 19:05       ` Shelby Heffron
2022-03-21 13:45       ` Shelby Heffron
2022-04-09  3:38       ` Dmitry Torokhov
2022-03-29  3:40     ` Shelby Heffron
2022-04-05 13:29     ` Shelby Heffron
2022-04-14  1:53   ` [PATCH] [V3] " Shelby Heffron
2022-04-17 20:23     ` 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=20220126211224.28590-1-Shelby.Heffron@garmin.com \
    --to=shelby.heffron@garmin.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®