From: Lee Jones <lee.jones@linaro.org>
To: Alban Bedel <alban.bedel@avionic-design.de>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH v2 2/2] regulator: tps6586x: Add support for the TPS658640
Date: Tue, 20 May 2014 13:14:39 +0100 [thread overview]
Message-ID: <20140520121439.GK24991@lee--X1> (raw)
In-Reply-To: <1400580843-29484-2-git-send-email-alban.bedel@avionic-design.de>
> The TPS658640 has a different set of output voltage for most LDO and
> the RTC LDO isn't settable. This chip also report 2 different version
> ID, as the datasheet doesn't list the possible values the second ID
> has simply been named TPS658640v2.
>
> Signed-off-by: Alban Bedel <alban.bedel@avionic-design.de>
> ---
> v2: Fixed the number of bits for the voltage selection of LDO_RTC
> Removed superflous whitspace after the tps658640_regulator array
> ---
> drivers/mfd/tps6586x.c | 4 ++++
> drivers/regulator/tps6586x-regulator.c | 36 ++++++++++++++++++++++++++++++++++
> include/linux/mfd/tps6586x.h | 2 ++
> 3 files changed, 42 insertions(+)
MFD parts look okay to me.
Mark can you tag the branch and ping it over to me please?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-05-20 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 10:14 [PATCH v2 1/2] regulator: tps6586x: Prepare supporting fixed regulators Alban Bedel
2014-05-20 10:14 ` [PATCH v2 2/2] regulator: tps6586x: Add support for the TPS658640 Alban Bedel
2014-05-20 12:14 ` Lee Jones [this message]
2014-05-26 15:54 ` Mark Brown
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=20140520121439.GK24991@lee--X1 \
--to=lee.jones@linaro.org \
--cc=alban.bedel@avionic-design.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome