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: <20170703153635.wpmyvbqjw3sik45d@sirena.org.uk>
Date:   Mon, 3 Jul 2017 16:36:35 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Waldemar Rymarkiewicz <waldemar.rymarkiewicz@...il.com>
Cc:     "Bartholomae, Thomas" <t.bartholomae@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: Where to update regulator register with initial voltage set by HW

On Mon, Jul 03, 2017 at 05:33:03PM +0200, Waldemar Rymarkiewicz wrote:

> I've asked also on TI forum if this is typical to the regulator not to
> determine the startup voltage but still waiting for feedback. Anyway,
> if this is the case I guess a driver is a good place to update
> register before we register to the regulator framework.

It's really unusual to have a device that has the voltage changable by
register write at runtime where the current state can't be read back.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ