From: Samuel Ortiz <sameo@linux.intel.com>
To: Sourav Poddar <sourav.poddar@ti.com>
Cc: 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,
b-cousson@ti.com, balbi@ti.com, santosh.shilimkar@ti.com
Subject: Re: [PATCHv3 1/4] mfd: smsc: Add support for smsc gpio io/keypad driver
Date: Mon, 1 Oct 2012 14:03:43 +0200 [thread overview]
Message-ID: <20121001120343.GG12231@sortiz-mobl> (raw)
In-Reply-To: <1349089282-22105-1-git-send-email-sourav.poddar@ti.com>
Hi Sourav,
On Mon, Oct 01, 2012 at 04:31:22PM +0530, Sourav Poddar wrote:
> smsc ece1099 is a keyboard scan or gpio expansion device.
> The patch create keypad and gpio expander child for this
> multi function smsc driver.
>
> Tested on omap5430 evm with 3.6-rc6 custom kernel.
>
> Cc: Samuel Ortiz <sameo@linux.intel.com>
> Cc: Benoit Cousson <b-cousson@ti.com>
> Cc: Felipe Balbi <balbi@ti.com>
> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
> ---
> Changes since v2:
> - Change the cache type, max register assignment
> - remove of_device_table, since i2c based device gets
> probed according to i2c_device_id through dt.
> - Modify the remove function
> - Minor return patch cleanups.
> Documentation/smsc_ece1099.txt | 56 ++++++++++++++++++++
> drivers/mfd/Kconfig | 12 ++++
> drivers/mfd/Makefile | 1 +
> drivers/mfd/smsc-ece1099.c | 113 ++++++++++++++++++++++++++++++++++++++++
> include/linux/mfd/smsc.h | 109 ++++++++++++++++++++++++++++++++++++++
> 5 files changed, 291 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/smsc_ece1099.txt
> create mode 100644 drivers/mfd/smsc-ece1099.c
> create mode 100644 include/linux/mfd/smsc.h
Applied with a warning fix for the !CONFIG_OF case.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2012-10-01 12:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 11:01 [PATCHv3 1/4] mfd: smsc: Add support for smsc gpio io/keypad driver Sourav Poddar
[not found] ` <1349089282-22105-1-git-send-email-sourav.poddar-l0cyMroinI0@public.gmane.org>
2012-10-01 11:30 ` ABRAHAM, KISHON VIJAY
2012-10-01 11:44 ` Mark Brown
[not found] ` <20121001114454.GA9170-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-10-01 11:53 ` ABRAHAM, KISHON VIJAY
2012-10-01 12:09 ` Mark Brown
2012-10-01 15:24 ` ABRAHAM, KISHON VIJAY
2012-10-02 12:38 ` Mark Brown
[not found] ` <20121002123856.GX4360-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-10-02 12:43 ` Felipe Balbi
2012-10-02 12:58 ` Mark Brown
[not found] ` <20121002125819.GY4360-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-10-02 13:44 ` Felipe Balbi
2012-10-02 19:12 ` ABRAHAM, KISHON VIJAY
2012-10-01 12:03 ` Samuel Ortiz [this message]
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=20121001120343.GG12231@sortiz-mobl \
--to=sameo@linux.intel.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 \
--cc=sourav.poddar@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).