From: Lee Jones <lee.jones@linaro.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org,
Kyungmin Park <kyungmin.park@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Tomasz Figa <t.figa@samsung.com>,
Anton Vorontsov <anton@enomsg.org>
Subject: Re: [PATCH part2 5/6] regulator: max14577: Implement SUSPEND mode for MAX77836 LDO-s
Date: Mon, 28 Apr 2014 12:14:57 +0100 [thread overview]
Message-ID: <20140428111457.GQ21279@lee--X1> (raw)
In-Reply-To: <1398264640-12122-6-git-send-email-k.kozlowski@samsung.com>
On Wed, 23 Apr 2014, Krzysztof Kozlowski wrote:
> The MAX77836 LDO regulators support low power mode. In this mode the
> maximum load current is 5 mA and the quiescent supply current is 1.5 uA.
>
> This patch adds support for mode REGULATOR_MODE_STANDBY (and NORMAL) to
> LDO regulators by implementing the set_mode() and get_mode() operations.
> However the necessary regulator constraints (valid modes) are not parsed
> by of_regulator_match() so the driver adds them manually to the
> regulator init_data.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Cc: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> drivers/regulator/max14577.c | 61 ++++++++++++++++++++++++++++++++++--
> include/linux/mfd/max14577-private.h | 2 ++
For the MFD changes:
Acked-by: Lee Jones <lee.jones@linaro.org>
--
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-04-28 11:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 14:50 [PATCH part2 0/6] charger/mfd: max14577: Part 2 of adding support for MAX77836 Krzysztof Kozlowski
2014-04-23 14:50 ` [PATCH part2 1/6] charger: max14577: Add support for MAX77836 charger Krzysztof Kozlowski
2014-04-23 14:50 ` [PATCH part2 2/6] regulator/mfd: max14577: Export symbols for calculating charger current Krzysztof Kozlowski
2014-04-24 12:48 ` Mark Brown
2014-04-25 13:45 ` Krzysztof Kozlowski
2014-04-25 14:16 ` Mark Brown
2014-04-23 14:50 ` [PATCH part2 3/6] charger: max14577: Configure battery-dependent settings from DTS Krzysztof Kozlowski
2014-04-23 14:50 ` [PATCH part2 4/6] power: max17040: Add ID for MAX77836 Fuel Gauge block Krzysztof Kozlowski
2014-04-23 14:50 ` [PATCH part2 5/6] regulator: max14577: Implement SUSPEND mode for MAX77836 LDO-s Krzysztof Kozlowski
2014-04-28 11:14 ` Lee Jones [this message]
2014-05-01 18:19 ` Mark Brown
2014-05-05 8:47 ` Krzysztof Kozlowski
2014-04-23 14:50 ` [PATCH part2 6/6] devicetree: mfd: max14577: Add device tree bindings document Krzysztof Kozlowski
2014-05-06 7:38 ` [PATCH part2 0/6] charger/mfd: max14577: Part 2 of adding support for MAX77836 Krzysztof Kozlowski
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=20140428111457.GQ21279@lee--X1 \
--to=lee.jones@linaro.org \
--cc=anton@enomsg.org \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=k.kozlowski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sameo@linux.intel.com \
--cc=t.figa@samsung.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