linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@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 10:03:39 -0700	[thread overview]
Message-ID: <52AB3DEB.5020507@wwwdotorg.org> (raw)
In-Reply-To: <1386951847-6490-2-git-send-email-treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

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?

  parent reply	other threads:[~2013-12-13 17:03 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 [this message]
     [not found]         ` <52AB3DEB.5020507-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-12-13 19:57           ` Thierry Reding
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=52AB3DEB.5020507@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@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 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).