From: Sourav Poddar <sourav.poddar@ti.com>
To: devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
sourav.poddar@ti.com
Cc: b-cousson@ti.com, balbi@ti.com, santosh.shilimkar@ti.com
Subject: [PATCHv2 0/4] Add mfd driver for smsc-ece1099 chip
Date: Wed, 5 Sep 2012 17:05:33 +0530 [thread overview]
Message-ID: <1346844933-24809-1-git-send-email-sourav.poddar@ti.com> (raw)
Add a smsc-ece1099 mfd driver which will work as
keypad scan device or a gpio expander device.
Patch 1 creates the parent mfd driver.
Patch 2 add keypad support. Patch 3 adds dts
support for keypad in omap5 dts file.
Patch 4 add gpio expansion driver for chip (RFC).
Cc: Benoit Cousson <b-cousson@ti.com>
Cc: Felipe Balbi <balbi@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
G, Manjunath Kondaiah (1):
Input: keypad: Add smsc ece1099 keypad driver
Sourav Poddar (3):
mfd: smsc: Add support for smsc gpio io/keypad driver
arm/dts: omap5-evm: Add keypad support
gpio: smscece: Add support for gpio IO expander feature
Documentation/smsc_ece1099.txt | 56 ++++
arch/arm/boot/dts/omap5-evm.dts | 95 +++++++
drivers/gpio/Kconfig | 7 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-smscece.c | 380 ++++++++++++++++++++++++++
drivers/input/keyboard/Kconfig | 11 +
drivers/input/keyboard/Makefile | 1 +
drivers/input/keyboard/smsc-ece1099-keypad.c | 306 +++++++++++++++++++++
drivers/mfd/Kconfig | 12 +
drivers/mfd/Makefile | 1 +
drivers/mfd/smsc-ece1099.c | 110 ++++++++
include/linux/mfd/smsc.h | 111 ++++++++
12 files changed, 1091 insertions(+), 0 deletions(-)
create mode 100644 Documentation/smsc_ece1099.txt
create mode 100644 drivers/gpio/gpio-smscece.c
create mode 100644 drivers/input/keyboard/smsc-ece1099-keypad.c
create mode 100644 drivers/mfd/smsc-ece1099.c
create mode 100644 include/linux/mfd/smsc.h
reply other threads:[~2012-09-05 11:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1346844933-24809-1-git-send-email-sourav.poddar@ti.com \
--to=sourav.poddar@ti.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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;
as well as URLs for NNTP newsgroup(s).