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: <CAHKzcEP32km_B3iqO-8TwyQ4Gybdc17DN-Po+L7JzxoDG9vQsg@mail.gmail.com>
Date:   Mon, 3 Jul 2017 17:33:03 +0200
From:   Waldemar Rymarkiewicz <waldemar.rymarkiewicz@...il.com>
To:     Mark Brown <broonie@...nel.org>
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 3 July 2017 at 17:11, Mark Brown <broonie@...nel.org> wrote:
> On Fri, Jun 30, 2017 at 12:26:52PM +0000, Bartholomae, Thomas wrote:
>> Hi Mark,
>
>> The problem is that our used regulator TPS65273V from TI do not have
>> the possibility to read the current voltage defined by the HW, means
>> by the circuit of the regulator.  In this case the register holding
>> the voltage to be set later by software has a reset value which is
>> normally the min value the regulator can support. This value can be
>> out of the range of the supported rail. Therefore before the regulator
>> gets registered this register needs to be set with a 'good' value.  I
>> assume the only practicable solution will be that we initialize this
>> voltage register in the boot code where we also set the CPU frequency.
>
> You probably need platform data to tell the kernelw hat teh startup
> value is.

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.

Thanks Mark for your feedback.

/Waldek

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ