From: Sriramakrishnan <srk@ti.com>
To: linux-omap@vger.kernel.org, linux-input@vger.kernel.org
Cc: Sriramakrishnan <srk@ti.com>
Subject: [PATCH 0/3] Add support for TCA6416 based Keypad driver.
Date: Thu, 25 Feb 2010 18:44:58 +0530 [thread overview]
Message-ID: <1267103701-23823-1-git-send-email-srk@ti.com> (raw)
AM3517 EVM with APPS board includes keys interfaced to TCA6416 IO expander.
User keys are connected as GPIO lines to TCA6416 IO expander. Unlike the
case with generic gpio-keypad driver individual keys do not generate an
interrupt event. Hence we implement a simple keypad driver(based on gpio-keys)
that registers as direct I2C client.
The implementation has been tested on AM3517 EVM with the driver tested
in polling mode.
Sriramakrishnan (3):
TCA6416 keypad : Implement keypad driver for keys interfaced to
TCA6416
AM3517 EVM : Enable TCA6416 keypad
AM3517: Board hookup for TCA6416 keypad driver.
arch/arm/configs/am3517_evm_defconfig | 15 ++-
arch/arm/mach-omap2/board-am3517evm.c | 48 ++++-
drivers/input/keyboard/Kconfig | 17 ++
drivers/input/keyboard/Makefile | 1 +
drivers/input/keyboard/tca6416-keypad.c | 355 +++++++++++++++++++++++++++++++
include/linux/tca6416_keypad.h | 30 +++
6 files changed, 460 insertions(+), 6 deletions(-)
create mode 100755 drivers/input/keyboard/tca6416-keypad.c
create mode 100755 include/linux/tca6416_keypad.h
next reply other threads:[~2010-02-25 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 13:14 Sriramakrishnan [this message]
2010-02-25 13:14 ` [PATCH 1/3] TCA6416 keypad : Implement keypad driver for keys interfaced to TCA6416 Sriramakrishnan
2010-02-25 13:15 ` [PATCH 2/3] AM3517 EVM : Enable TCA6416 keypad Sriramakrishnan
2010-02-25 13:15 ` [PATCH 3/3] AM3517: Board hookup for TCA6416 keypad driver Sriramakrishnan
2010-02-25 18:47 ` [PATCH 1/3] TCA6416 keypad : Implement keypad driver for keys interfaced to TCA6416 Felipe Balbi
2010-02-26 8:28 ` Dmitry Torokhov
2010-02-26 14:43 ` Govindarajan, Sriramakrishnan
2010-02-27 9:00 ` Dmitry Torokhov
2010-03-05 15:06 ` Govindarajan, Sriramakrishnan
2010-02-27 18:57 ` Anirudh Ghayal
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=1267103701-23823-1-git-send-email-srk@ti.com \
--to=srk@ti.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-omap@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).