From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>,
lee.jones@linaro.org, sameo@linux.intel.com, broonie@kernel.org,
linus.walleij@linaro.org, akpm@linux-foundation.org
Cc: devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
rtc-linux@googlegroups.com, rob.herring@calxeda.com,
mark.rutland@arm.com, pawel.moll@arm.com, rob@landley.net,
ijc+devicetree@hellion.org.uk, grant.likely@linaro.org,
Florian Lobmaier <florian.lobmaier@ams.com>
Subject: Re: [PATCH V5 1/3] mfd: add support for ams AS3722 PMIC
Date: Wed, 09 Oct 2013 10:13:28 -0600 [thread overview]
Message-ID: <525580A8.5050902@wwwdotorg.org> (raw)
In-Reply-To: <1381321761-8898-2-git-send-email-ldewangan@nvidia.com>
On 10/09/2013 06:29 AM, Laxman Dewangan wrote:
> The ams AS3722 is a compact system PMU suitable for mobile phones,
> tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
> controller, 11 LDOs, RTC, automatic battery, temperature and
> over-current monitoring, 8 GPIOs, ADC and a watchdog.
>
> Add MFD core driver for the AS3722 to support core functionality.
OK, I think the binding here is about clear enough, so the binding,
Acked-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2013-10-09 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 12:29 [PATCH V5 0/3] Add AMS AS3722 mfd, pincontrol and RTC driver Laxman Dewangan
2013-10-09 12:29 ` [PATCH V5 1/3] mfd: add support for ams AS3722 PMIC Laxman Dewangan
2013-10-09 16:13 ` Stephen Warren [this message]
2013-10-21 11:18 ` Laxman Dewangan
2013-10-22 6:58 ` Lee Jones
2013-10-09 12:29 ` [PATCH V5 2/3] pincntrl: add support for ams AS3722 pin control driver Laxman Dewangan
2013-10-09 12:29 ` [PATCH V5 3/3] drivers/rtc/rtc-as3722: add RTC driver Laxman Dewangan
2013-10-10 22:24 ` Andrew Morton
2013-10-10 22:47 ` Mark Brown
2013-10-11 8:08 ` [rtc-linux] " Linus Walleij
2013-10-21 11:14 ` Laxman Dewangan
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=525580A8.5050902@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.lobmaier@ams.com \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.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).