From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/3] ARM: tegra: Enable Venice2 keyboard
Date: Fri, 13 Dec 2013 20:57:09 +0100 [thread overview]
Message-ID: <20131213195707.GD7924@ulmo.nvidia.com> (raw)
In-Reply-To: <52AB3DEB.5020507-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
On Fri, Dec 13, 2013 at 10:03:39AM -0700, Stephen Warren wrote:
> On 12/13/2013 09:24 AM, Thierry Reding wrote:
>
> > diff --git a/arch/arm/boot/dts/tegra124-venice2.dts b/arch/arm/boot/dts/tegra124-venice2.dts
>
> > + linux,keymap = <0x0001007d /* L_META */
> > + 0x0002003b /* F1 */
>
> I don't suppose you could rework these using the MATRIX_KEY() macro, and
> associated header file that provides named keycode constants?
Yes of course. I totally forgot that we have a header with symbolic
constants now.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-13 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 16:24 [PATCH 1/3] ARM: tegra: Add SPI controller nodes for Tegra124 Thierry Reding
[not found] ` <1386951847-6490-1-git-send-email-treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-13 16:24 ` [PATCH 2/3] ARM: tegra: Enable Venice2 keyboard Thierry Reding
[not found] ` <1386951847-6490-2-git-send-email-treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-12-13 17:03 ` Stephen Warren
[not found] ` <52AB3DEB.5020507-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-12-13 19:57 ` Thierry Reding [this message]
2013-12-13 16:24 ` [PATCH 3/3] ARM: tegra: Enable ChromeOS embedded controller Thierry Reding
2013-12-13 19:48 ` [PATCH 1/3] ARM: tegra: Add SPI controller nodes for Tegra124 Stephen Warren
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=20131213195707.GD7924@ulmo.nvidia.com \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.