mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Boyd <stephen.boyd@linaro.org>
To: Georgi Djakov <georgi.djakov@linaro.org>,
	"Mark Brown" <broonie@kernel.org>
Cc: linux-arm@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	"David Collins" <collinsd@codeaurora.org>
Subject: Re: [PATCH] regulator: qcom_spmi: Add slewing delays for all SMPS types
Date: Wed, 30 Mar 2016 11:09:33 -0700	[thread overview]
Message-ID: <20160330180933.5175.90898@sboyd-linaro> (raw)
In-Reply-To: <56FBE45B.4030709@linaro.org>

Quoting Georgi Djakov (2016-03-30 07:36:11)
> On 03/30/2016 01:58 AM, Stephen Boyd wrote:
> > Only the FT SMPS type regulators have slewing supported in the
> > driver, but all types of SMPS regulators need the same support.
> > The only difference is that some SMPS regulators don't have a
> > step size and the step delay is typically 20, not 8. Luckily, the
> > step size reads as 0 for the non-FT types, so we can always read
> > that, but we need to detect which type of regulator we're using
> > to figure out what step delay to use. Make these minor
> > adjustments to the slew rate calculations and add support for the
> > delay function to the appropriate regulator ops.
> > 
> > Reported-by: Georgi Djakov <georgi.djakov@linaro.org>
> > Cc: David Collins <collinsd@codeaurora.org>
> > Signed-off-by: Stephen Boyd <stephen.boyd@linaro.org>
> 
> Thanks for the patch! I have verified it by applying this one
> on top: https://lkml.org/lkml/2016/3/30/381
> 
> Tested-by: Georgi Djakov <georgi.djakov@linaro.org>
> 

Thanks for testing. I'll pick up the rest on the other thread.

      reply	other threads:[~2016-03-30 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 22:58 Stephen Boyd
2016-03-29 23:09 ` Mark Brown
2016-03-30 14:36 ` Georgi Djakov
2016-03-30 18:09   ` Stephen Boyd [this message]

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=20160330180933.5175.90898@sboyd-linaro \
    --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

all inboxes | Powered by JetHome®