linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <magnus.damm@gmail.com>
To: linux-input@vger.kernel.org
Cc: lethal@linux-sh.org, Magnus Damm <magnus.damm@gmail.com>,
	dmitry.torokhov@gmail.com, linux-sh@vger.kernel.org
Subject: [PATCH 00/03] input: mode 6 patches for sh_keysc
Date: Mon, 08 Feb 2010 15:32:16 +0900	[thread overview]
Message-ID: <20100208063216.2003.84260.sendpatchset@rxone.opensource.se> (raw)

input: mode 6 patches for sh_keysc

[PATCH 01/03] input: break out hw access functions in sh_keysc 
[PATCH 02/03] input: bitmap update for sh_keysc
[PATCH 03/03] input: update sh_keysc driver with mode 6

These patches improve the sh_keysc driver with mode 6 support.

The earlier submitted patch for mode 4 and mode 5 extended the
driver with up to 6 * 7 keys. Mode 6 support included in this
patch set allows up to 7 * 7 keys.

The sh_keysc driver has so far only been used with hardware
where the number of keys can fit in a 32-bit bitmap, but from
mode 4 and up these 32 bits are no longer enough. To address
this proper bitmaps are made use of instead 32-bit integers.

Signed-off-by: Magnus Damm <damm@opensource.se>
---

 drivers/input/keyboard/sh_keysc.c |  155 ++++++++++++++++++++++++-------------
 include/linux/input/sh_keysc.h    |    6 -
 2 files changed, 106 insertions(+), 55 deletions(-)

             reply	other threads:[~2010-02-08  6:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  6:32 Magnus Damm [this message]
2010-02-08  6:32 ` [PATCH 01/03] input: break out hw access functions in sh_keysc Magnus Damm
2010-02-08  6:32 ` [PATCH 02/03] input: bitmap update for sh_keysc Magnus Damm
2010-02-08  7:18   ` Dmitry Torokhov
2010-02-08  7:41     ` Magnus Damm
2010-02-09  1:17       ` Paul Mundt
2010-02-08  6:32 ` [PATCH 03/03] input: update sh_keysc driver with mode 6 Magnus Damm

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=20100208063216.2003.84260.sendpatchset@rxone.opensource.se \
    --to=magnus.damm@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-sh@vger.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).