linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: cros-ec-keyboard: Add LOCK key to keyboard matrix
Date: Mon, 01 Feb 2016 18:16:47 +0100	[thread overview]
Message-ID: <2283417.UbYyfQa1E3@diego> (raw)
In-Reply-To: <1454121504-12683-1-git-send-email-djkurtz@chromium.org>

Hi Daniel,

Am Samstag, 30. Januar 2016, 10:38:24 schrieb Daniel Kurtz:
> From: James Chao <james_chao@asus.com>
> 
> The LOCK key is at KSO9/KSI3 for Chromebook Flip and other devices
> that use the Chrome OS EC keyboard matrix.
> 
> Signed-off-by: James Chao <james_chao@asus.com>
> Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
> Signed-off-by: YH Huang <yh.huang@mediatek.com>

that should probably be a 
	Reviewed-by: YH Huang <yh.huang@mediatek.com>
As I don't see any actual patch handling step by him/her.

Also, you might've included Olof as the keeper of all things ChromeOS when 
sending.

@Olof: this seems to be pretty Veyron-specific for the moment, so I'm inclined 
to pick that up. Please holler if you disagree and want to pick it up yourself 
;-)


Thanks
Heiko

> ---
>  arch/arm/boot/dts/cros-ec-keyboard.dtsi | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/boot/dts/cros-ec-keyboard.dtsi
> b/arch/arm/boot/dts/cros-ec-keyboard.dtsi index 4e42f30c..c045105 100644
> --- a/arch/arm/boot/dts/cros-ec-keyboard.dtsi
> +++ b/arch/arm/boot/dts/cros-ec-keyboard.dtsi
> @@ -55,6 +55,7 @@
>  			MATRIX_KEY(0x03, 0x04, KEY_F5)
>  			MATRIX_KEY(0x03, 0x06, KEY_6)
>  			MATRIX_KEY(0x03, 0x08, KEY_MINUS)
> +			MATRIX_KEY(0x03, 0x09, KEY_F13)
>  			MATRIX_KEY(0x03, 0x0b, KEY_BACKSLASH)
>  			MATRIX_KEY(0x03, 0x0c, KEY_MUHENKAN)

  reply	other threads:[~2016-02-01 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30  2:38 [PATCH] ARM: dts: cros-ec-keyboard: Add LOCK key to keyboard matrix Daniel Kurtz
2016-02-01 17:16 ` Heiko Stübner [this message]
2016-02-02  0:52   ` Olof Johansson
2016-02-01 17:19 ` Doug Anderson
2016-02-11 12:53 ` Heiko Stuebner

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=2283417.UbYyfQa1E3@diego \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.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).