linux-kernel - Re: [PATCH] regulator: Fix machine constraints apply for min_uV != max

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]

Date:	Fri, 3 Sep 2010 15:54:20 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Jarkko Nikula <jhnikula@...il.com>
Cc:	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...mlogic.co.uk>
Subject: Re: [PATCH] regulator: Fix machine constraints apply for min_uV !=
 max_uV

On Fri, Sep 03, 2010 at 04:43:49PM +0300, Jarkko Nikula wrote:
> Constraints are not applied until both min_uV and max_uV are the same. This
> looks like a typo in the test.
> 
> Signed-off-by: Jarkko Nikula <jhnikula@...il.com>

This is deliberate behaviour, apply_uV can only be used with a fixed
voltage at startup in order to avoid issues with handover from the
bootloader if we suddenly drop the supply voltage on a device which has
not yet been claimed by a driver.  The expectation is that if the
voltage can vary then something that understands the hardware state
needs to be involved in maintaining the voltage.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/