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:	Thu, 7 Jul 2016 11:31:36 -0700
From:	Doug Anderson <dianders@...omium.org>
To:	Aleksandr Frid <afrid@...dia.com>
Cc:	Laxman Dewangan <ldewangan@...dia.com>,
	Mark Brown <broonie@...nel.org>,
	Boris Brezillon <boris.brezillon@...e-electrons.com>,
	Lee Jones <lee.jones@...aro.org>,
	Brian Norris <briannorris@...omium.org>,
	"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
	Heiko Stuebner <heiko@...ech.de>,
	Thierry Reding <thierry.reding@...il.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] regulator: pwm: Fix regulator ramp delay for
 continuous mode

Hi,

On Thu, Jul 7, 2016 at 11:23 AM, Aleksandr Frid <afrid@...dia.com> wrote:
> Hi,
>
>>>
> In that case we should probably add a new PWM regulator property and not abuse the existing one.  Maybe you use "pwm-regulator-settle-us"
> or something?
>>>
> Looks reasonable to me.
>
>>>
> actually the right thing is probably to implement 'regulator-ramp-delay' as doing several small steps in that case
>>>
> Ramp delay uV/us  is not a "real" metric for some PWM regulators with exponential transition -- as opposite to fixed slew-rate linear transition on other regulators. So splitting transition into multiple steps to implement artificial  (in this case) metric seems questionable.

In the case that you don't need multiple steps then don't specify a
regulator-ramp-delay, just a pwm-regulator-settle-us.

...the suggestion for multiple steps is because (so I'm told) it helps
avoid overshoot or undershoot problems.  In general the whole point of
ramping a regulator slowly is to avoid overshoot or undershoot
problems.  The "regulator-ramp-delay" property in Linux is a little
odd because it sort of "describes" the ramp delay and sort of "sets"
the ramp delay.  Many PMICs allow you to set how fast the regulator
will ramp and this property is used to specify how the register in the
PMIC should be set.  However, it is also used as the actual delay in
Linux.


-Doug

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ