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:	Tue, 10 Sep 2013 11:45:41 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Mark Brown <broonie@...nel.org>
CC:	Laxman Dewangan <ldewangan@...dia.com>, rob.herring@...xeda.com,
	mark.rutland@....com, rob@...dley.net, devicetree@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	lgirdwood@...il.com
Subject: Re: [PATCH 2/2] regulator: core: add support for configuring turn-on
 time through constraints

On 09/10/2013 11:38 AM, Mark Brown wrote:
> On Tue, Sep 10, 2013 at 11:34:13AM -0600, Stephen Warren wrote:
> 
>> I notice there's a regulator-ramp-delay property, already documented
>> right above this new property. Is this a conflicting usage of the same
>> term, or should that existing property just be used in this case too?
> 
> That's for a ramp between two voltages rather than the on/off voltage,
> though I had forgotten about it.  Hrm.  enable-ramp-delay?

Sounds reasonable. It's a little long but regulator-enable-ramp-delay
might be better since all the common regulator properties to date are
named regulator-xxx.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ