public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Mark Brown <broonie@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] regulator: core: Ensure we are at least in bounds for our constraints
Date: Mon, 21 Mar 2016 23:06:20 +0200	[thread overview]
Message-ID: <56F0624C.8010004@gmail.com> (raw)
In-Reply-To: <1458587912-32665-2-git-send-email-broonie@kernel.org>

Hi,

On 21.03.2016 21:18, Mark Brown wrote:
> Currently we only attempt to set the voltage during constraints
> application if an exact voltage is specified.  Extend this so that if
> the currently set voltage for the regualtor is outside the bounds set in

regulator

> constraints we will move the voltage to the nearest constraint, raising
> to the minimum or lowering to the maximum as needed.  This ensures that
> drivers can probe without the hardware being driven out of spec.
>
> Reported-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
>
> Untested so far, will give it a spin later/tomorrow.
>
>   drivers/regulator/core.c | 32 +++++++++++++++++++++++++-------
>   1 file changed, 25 insertions(+), 7 deletions(-)
>

Patch 1 does not apply cleanly on 4.5-rc5, so I applied it by hand, 
however, you may add:

Tested-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>

Thanks,
Ivo

  reply	other threads:[~2016-03-21 21:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 19:18 [PATCH 1/2] regulator: core: Always flag voltage constraints as appliable Mark Brown
2016-03-21 19:18 ` [PATCH 2/2] regulator: core: Ensure we are at least in bounds for our constraints Mark Brown
2016-03-21 21:06   ` Ivaylo Dimitrov [this message]
2016-03-24  6:11     ` Krzysztof Kozlowski
2016-03-24  7:18       ` Krzysztof Kozlowski
2016-03-26 23:50         ` Bjorn Andersson
2016-03-27  9:08           ` Mark Brown
2016-03-28 16:16             ` Bjorn Andersson
2016-03-29 12:00             ` Geert Uytterhoeven
2016-03-29 14:58               ` Mark Brown
2016-03-29 18:05                 ` Geert Uytterhoeven
2016-03-29 18:27                   ` Mark Brown
2016-03-30  9:07                     ` Haibo Chen
2016-03-30 15:25                       ` Mark Brown
2016-03-23 13:43   ` Applied "regulator: core: Ensure we are at least in bounds for our constraints" to the regulator tree Mark Brown
2016-03-23 13:43 ` Applied "regulator: core: Always flag voltage constraints as appliable" " 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=56F0624C.8010004@gmail.com \
    --to=ivo.g.dimitrov.75@gmail.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --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