From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Christian Hewitt <christianshewitt@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Kevin Hilman <khilman@baylibre.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/7] arm64: dts: meson: ir keymap updates
Date: Sun, 25 Aug 2019 21:38:37 +0200 [thread overview]
Message-ID: <CAFBinCD0uhE9Fj1we2MkaTbk7RwtmKh7Fn1C-2nn9wiWqCoNfg@mail.gmail.com> (raw)
In-Reply-To: <1566705688-18442-1-git-send-email-christianshewitt@gmail.com>
On Sun, Aug 25, 2019 at 6:03 AM Christian Hewitt
<christianshewitt@gmail.com> wrote:
>
> This series adds keymaps for several box/board vendor IR remote devices
> to respective device-tree files. The keymaps were submitted in [0] and
> have been queued for inclusion in Linux 5.4.
>
> The Khadas remote change swaps the rc-geekbox keymap for rc-khadas. The
> Geekbox branded remote was only sold for a brief period when VIM(1) was
> a new device. The Khadas branded remote that replaced it exchanged the
> Geekbox full-screen key for an Android mouse button using a different IR
> keycode. The rc-khadas keymap supports the mouse button keycode and maps
> it to KEY_MUTE.
>
> [0] https://patchwork.kernel.org/project/linux-media/list/?series=160309
>
> Christian Hewitt (7):
> arm64: dts: meson-g12b-odroid-n2: add rc-odroid keymap
> arm64: dts: meson-g12a-x96-max: add rc-x96max keymap
> arm64: dts: meson-gxbb-wetek-hub: add rc-wetek-hub keymap
> arm64: dts: meson-gxbb-wetek-play2: add rc-wetek-play2 keymap
> arm64: dts: meson-gxl-s905x-khadas-vim: use rc-khadas keymap
> arm64: dts: meson-gxl-s905w-tx3-mini: add rc-tx3mini keymap
> arm64: dts: meson-gxm-khadas-vim2: use rc-khadas keymap
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-25 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 4:01 [PATCH 0/7] arm64: dts: meson: ir keymap updates Christian Hewitt
2019-08-25 4:01 ` [PATCH 1/7] arm64: dts: meson-g12b-odroid-n2: add rc-odroid keymap Christian Hewitt
2019-08-25 4:01 ` [PATCH 2/7] arm64: dts: meson-g12a-x96-max: add rc-x96max keymap Christian Hewitt
2019-08-25 4:01 ` [PATCH 3/7] arm64: dts: meson-gxbb-wetek-hub: add rc-wetek-hub keymap Christian Hewitt
2019-08-25 4:01 ` [PATCH 4/7] arm64: dts: meson-gxbb-wetek-play2: add rc-wetek-play2 keymap Christian Hewitt
2019-08-25 4:01 ` [PATCH 5/7] arm64: dts: meson-gxl-s905x-khadas-vim: use rc-khadas keymap Christian Hewitt
2019-08-25 4:01 ` [PATCH 6/7] arm64: dts: meson-gxl-s905w-tx3-mini: add rc-tx3mini keymap Christian Hewitt
2019-08-25 4:01 ` [PATCH 7/7] arm64: dts: meson-gxm-khadas-vim2: use rc-khadas keymap Christian Hewitt
2019-08-25 19:38 ` Martin Blumenstingl [this message]
2019-08-27 22:24 ` [PATCH 0/7] arm64: dts: meson: ir keymap updates Kevin Hilman
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=CAFBinCD0uhE9Fj1we2MkaTbk7RwtmKh7Fn1C-2nn9wiWqCoNfg@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).