From: Christian Hewitt <christianshewitt@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Benjamin Valentin <benpicco@googlemail.com>,
Sean Young <sean@mess.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Cc: Christian Hewitt <christianshewitt@gmail.com>
Subject: [PATCH 0/7] media: rc: Add keymaps for common STB/SBC devices
Date: Thu, 15 Aug 2019 18:59:10 +0400 [thread overview]
Message-ID: <1565881157-14644-1-git-send-email-christianshewitt@gmail.com> (raw)
This series submits keymaps for a number of Android STB/SBC devices that
are regularly used with the Kodi mediacentre distro LibreELEC.
Keymaps list buttons in rows, top-down, to aid visual comparison against
devices. It's common for users of other no-name Android boxes to try a
number of keymaps trying to find one that works and this reduces some of
the guesswork. If the assigned key differs from the marked key, e.g.
where Android 'mouse' buttons have been given a more useful purpose, the
keymap has been commented.
Christian Hewitt (7):
media: rc: add keymap for Amediatech X96-MAX remote
media: rc: add keymap for Khadas VIM/EDGE remote
media: rc: add keymap for Tanix TX3 mini remote
media: rc: add keymap for Tanix TX5 max remote
media: rc: add keymap for WeTek Hub remote
media: rc: add keymap for WeTeK Play 2 remote
media: rc: add keymap for HardKernel ODROID remote
drivers/media/rc/keymaps/Makefile | 7 +++
drivers/media/rc/keymaps/rc-khadas.c | 56 +++++++++++++++++
drivers/media/rc/keymaps/rc-odroid.c | 51 ++++++++++++++++
drivers/media/rc/keymaps/rc-tanix-tx3mini.c | 79 ++++++++++++++++++++++++
drivers/media/rc/keymaps/rc-tanix-tx5max.c | 71 +++++++++++++++++++++
drivers/media/rc/keymaps/rc-wetek-hub.c | 55 +++++++++++++++++
drivers/media/rc/keymaps/rc-wetek-play2.c | 95 +++++++++++++++++++++++++++++
drivers/media/rc/keymaps/rc-x96max.c | 85 ++++++++++++++++++++++++++
include/media/rc-map.h | 7 +++
9 files changed, 506 insertions(+)
create mode 100644 drivers/media/rc/keymaps/rc-khadas.c
create mode 100644 drivers/media/rc/keymaps/rc-odroid.c
create mode 100644 drivers/media/rc/keymaps/rc-tanix-tx3mini.c
create mode 100644 drivers/media/rc/keymaps/rc-tanix-tx5max.c
create mode 100644 drivers/media/rc/keymaps/rc-wetek-hub.c
create mode 100644 drivers/media/rc/keymaps/rc-wetek-play2.c
create mode 100644 drivers/media/rc/keymaps/rc-x96max.c
--
2.7.4
next reply other threads:[~2019-08-15 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 14:59 Christian Hewitt [this message]
2019-08-15 14:59 ` [PATCH 1/7] media: rc: add keymap for Amediatech X96-MAX remote Christian Hewitt
2019-08-15 14:59 ` [PATCH 2/7] media: rc: add keymap for Khadas VIM/EDGE remote Christian Hewitt
2019-08-15 14:59 ` [PATCH 3/7] media: rc: add keymap for Tanix TX3 mini remote Christian Hewitt
2019-08-15 14:59 ` [PATCH 4/7] media: rc: add keymap for Tanix TX5 max remote Christian Hewitt
2019-08-15 14:59 ` [PATCH 5/7] media: rc: add keymap for WeTek Hub remote Christian Hewitt
2019-08-15 14:59 ` [PATCH 6/7] media: rc: add keymap for WeTeK Play 2 remote Christian Hewitt
2019-08-15 14:59 ` [PATCH 7/7] media: rc: add keymap for HardKernel ODROID remote Christian Hewitt
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=1565881157-14644-1-git-send-email-christianshewitt@gmail.com \
--to=christianshewitt@gmail.com \
--cc=benpicco@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sean@mess.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®