linux-kernel - Re: [PATCH 2/2] regulator: core: Ensure we are at least in bounds for our constraints

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <56F0624C.8010004@gmail.com>
Date:	Mon, 21 Mar 2016 23:06:20 +0200
From:	Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>
To:	Mark Brown <broonie@...nel.org>,
	Liam Girdwood <lgirdwood@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] regulator: core: Ensure we are at least in bounds for
 our constraints

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@...il.com>
> Signed-off-by: Mark Brown <broonie@...nel.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@...il.com>

Thanks,
Ivo