From: Stephen Boyd <stephen.boyd@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Georgi Djakov <georgi.djakov@linaro.org>,
David Collins <collinsd@codeaurora.org>
Subject: [PATCH v2 0/2] Proper slewing delays for qcom spmi regulators
Date: Wed, 30 Mar 2016 18:57:48 -0700 [thread overview]
Message-ID: <1459389470-29365-1-git-send-email-stephen.boyd@linaro.org> (raw)
This patch series adds proper slewing delays for qcom spmi regulators
by adding more slewing attributes for other types of regulators besides
FT SMPS and then making all the regulator ops selector based so that
the delays actually take place in the regulator core.
I've tested this by confirming we get proper delays when changing voltages
on PM8916's S2 ULT SMPS regulator and also confirmed the voltage values
by reading raw SPMI registers to confirm voltages are switching correctly.
Changes since v1:
* Second patch is new to make first patch actually do something
Stephen Boyd (2):
regulator: qcom_spmi: Add slewing delays for all SMPS types
regulator: qcom_spmi: Only use selector based regulator ops
drivers/regulator/qcom_spmi-regulator.c | 218 ++++++++++++++++++++------------
1 file changed, 137 insertions(+), 81 deletions(-)
--
2.8.0.rc4
next reply other threads:[~2016-03-31 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 1:57 Stephen Boyd [this message]
2016-03-31 1:57 ` [PATCH v2 1/2] regulator: qcom_spmi: Add slewing delays for all SMPS types Stephen Boyd
2016-03-31 1:57 ` [PATCH v2 2/2] regulator: qcom_spmi: Only use selector based regulator ops Stephen Boyd
2016-04-15 10:18 ` Rajendra Nayak
2016-04-15 17:44 ` [PATCH] regulator: qcom_spmi: Always return a selector when asked Stephen Boyd
2016-04-18 13:10 ` Applied "regulator: qcom_spmi: Always return a selector when asked" to the regulator tree 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=1459389470-29365-1-git-send-email-stephen.boyd@linaro.org \
--to=stephen.boyd@linaro.org \
--cc=broonie@kernel.org \
--cc=collinsd@codeaurora.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-arm@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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).