From: Sourav Poddar <sourav.poddar@ti.com>
To: dmitry.torokhov@gmail.com, sourav.poddar@ti.com,
linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Cc: balbi@ti.com
Subject: [PATCH 0/2] Omap keypad cleanup and omap5 support
Date: Fri, 16 Mar 2012 19:56:27 +0530 [thread overview]
Message-ID: <1331907989-11891-1-git-send-email-sourav.poddar@ti.com> (raw)
The series consists of two patches.
Patch1 of the series makes omap4 keypad independent of the
architecture by moving platform_data to <linux/platform_data>
Patch2 add support for omap5 onchip keypad.
Tested on omap4430sdp using 3.3-rc6.
Tested on omap5 board using 3.1 custom kernel.
Felipe Balbi (1):
input: keypad: move platform_data to <linux/platform_data>
G, Manjunath Kondaiah (1):
Input: omap-keypad: dynamically handle register offsets
arch/arm/mach-omap2/board-4430sdp.c | 1 +
arch/arm/mach-omap2/devices.c | 1 +
arch/arm/plat-omap/include/plat/omap4-keypad.h | 9 --
drivers/input/keyboard/Kconfig | 7 +-
drivers/input/keyboard/omap4-keypad.c | 124 +++++++++++++++++++-----
include/linux/platform_data/omap4-keypad.h | 13 +++
6 files changed, 118 insertions(+), 37 deletions(-)
create mode 100644 include/linux/platform_data/omap4-keypad.h
next reply other threads:[~2012-03-16 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 14:26 Sourav Poddar [this message]
2012-03-16 14:26 ` [PATCH 1/2] input: keypad: move platform_data to <linux/platform_data> Sourav Poddar
2012-03-16 16:36 ` Dmitry Torokhov
2012-03-16 21:08 ` Felipe Balbi
2012-03-17 5:36 ` Dmitry Torokhov
2012-03-16 14:26 ` [PATCH 2/2] Input: omap-keypad: dynamically handle register offsets Sourav Poddar
2012-03-17 5:47 ` Dmitry Torokhov
[not found] ` <CAKdam54CudK-BoeAfOMrcHk51D9QsUbPhh5=Rqw5_ERCu2BpKA@mail.gmail.com>
2012-03-19 8:33 ` Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2012-03-16 13:39 [PATCH 0/2] Omap keypad cleanup and omap5 support Sourav Poddar
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=1331907989-11891-1-git-send-email-sourav.poddar@ti.com \
--to=sourav.poddar@ti.com \
--cc=balbi@ti.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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).