From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Graeme Gregory <gg@slimlogic.co.uk>
Cc: linux-kernel@vger.kernel.org, sameo@linux.intel.com, lrg@ti.com,
b-cousson@ti.com, linux-omap@vger.kernel.org
Subject: Re: [PATCHv2 3/4] REGULATOR: regulator driver for Palmas series chips
Date: Tue, 15 May 2012 19:19:25 +0100 [thread overview]
Message-ID: <20120515181921.GE19592@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1337064539-3014-4-git-send-email-gg@slimlogic.co.uk>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
On Tue, May 15, 2012 at 03:48:58PM +0900, Graeme Gregory wrote:
> Palmas has both Switched Mode (SMPS) and Linear (LDO) regulators in it.
> This regulator driver allows software control of these regulators.
>
> The regulators available on Palmas series chips vary depending on the muxing.
> This is handled automatically in the driver by reading the mux info from OTP.
This all looks good modulo the thing with is_enabled() that I mentioned
which I think we can deal with incrementally - I'd apply but it depends
on the MFD header :/ If Samuel is OK with me applying the MFD I'll work
it out in my trees (probably by squashing the pdata into the mfd commit.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-15 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 6:48 [PATCHv2 0/4] Adding support for Palmas PMIC Graeme Gregory
2012-05-15 6:48 ` [PATCHv2 1/4] MFD: palmas PMIC device support Graeme Gregory
2012-05-15 18:14 ` Mark Brown
2012-05-18 9:55 ` Samuel Ortiz
2012-05-18 16:23 ` Mark Brown
2012-05-15 6:48 ` [PATCHv2 2/4] MFD: palmas PMIC device support Kconfig Graeme Gregory
2012-05-15 6:48 ` [PATCHv2 3/4] REGULATOR: regulator driver for Palmas series chips Graeme Gregory
2012-05-15 18:19 ` Mark Brown [this message]
2012-05-15 6:48 ` [PATCHv2 4/4] REGULATOR: regulator for Palmas Kconfig Graeme Gregory
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=20120515181921.GE19592@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=b-cousson@ti.com \
--cc=gg@slimlogic.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.