From: Simon Horman <horms@verge.net.au>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-input@vger.kernel.org, lethal@linux-sh.org,
dmitry.torokhov@gmail.com, linux-sh@vger.kernel.org
Subject: Re: [PATCH] input: sh_keysc: 8x8 MODE_6 fix
Date: Wed, 15 Jun 2011 23:12:18 +0000 [thread overview]
Message-ID: <20110615231211.GC28947@verge.net.au> (raw)
In-Reply-To: <20110615143340.21798.61858.sendpatchset@t400s>
On Wed, Jun 15, 2011 at 11:33:40PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> The MODE_6 support in sh_keysc.c is incorrect without
> this patch. According to the data sheet for G4, AP4 and
> AG5 KEYSC MODE_6 is 8x8 keys. Bump up MAXKEYS to 64 too.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
Reviewed-by: Simon Horman <horms@verge.net.au>
Do we also need to update the platform data for ag5evm
which is currently using SH_KEYSC_MODE_6 but with 49
entries in its keysc_platdata.keycodes ?
> ---
>
> drivers/input/keyboard/sh_keysc.c | 2 +-
> include/linux/input/sh_keysc.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> --- 0001/drivers/input/keyboard/sh_keysc.c
> +++ work/drivers/input/keyboard/sh_keysc.c 2011-06-15 17:59:27.000000000 +0900
> @@ -32,7 +32,7 @@ static const struct {
> [SH_KEYSC_MODE_3] = { 2, 4, 7 },
> [SH_KEYSC_MODE_4] = { 3, 6, 6 },
> [SH_KEYSC_MODE_5] = { 4, 6, 7 },
> - [SH_KEYSC_MODE_6] = { 5, 7, 7 },
> + [SH_KEYSC_MODE_6] = { 5, 8, 8 },
> };
>
> struct sh_keysc_priv {
> --- 0001/include/linux/input/sh_keysc.h
> +++ work/include/linux/input/sh_keysc.h 2011-06-15 17:48:05.000000000 +0900
> @@ -1,7 +1,7 @@
> #ifndef __SH_KEYSC_H__
> #define __SH_KEYSC_H__
>
> -#define SH_KEYSC_MAXKEYS 49
> +#define SH_KEYSC_MAXKEYS 64
>
> struct sh_keysc_info {
> enum { SH_KEYSC_MODE_1, SH_KEYSC_MODE_2, SH_KEYSC_MODE_3,
>
next prev parent reply other threads:[~2011-06-15 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 14:33 [PATCH] input: sh_keysc: 8x8 MODE_6 fix Magnus Damm
2011-06-15 23:12 ` Simon Horman [this message]
2011-06-16 0:57 ` Magnus Damm
2011-06-18 9:52 ` Dmitry Torokhov
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=20110615231211.GC28947@verge.net.au \
--to=horms@verge.net.au \
--cc=dmitry.torokhov@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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