Thread (18 messages) 18 messages, 4 authors, 2012-05-23

[PATCH v5 1/4] regulator: helper routine to extract regulator_init_data

From: Mark Brown <hidden>
Date: 2011-12-04 15:54:41
Also in: linux-devicetree, linux-omap, lkml

On Sun, Dec 04, 2011 at 06:51:23PM +0530, Thomas Abraham wrote:
For regulators that are not turned on by bootloader, and which require
'apply_uV' constraint, is there any alternative for turning on the
regulator when using dt?
If the regulator isn't software managed then always_on covers this - the
regulator core will enable any always_on regulators that haven't been
enabled already.
 	/* do we need to apply the constraint voltage */
-	if (rdev->constraints->apply_uV &&
-	    rdev->constraints->min_uV == rdev->constraints->max_uV) {
+	if ((rdev->constraints->apply_uV &&
+	    rdev->constraints->min_uV == rdev->constraints->max_uV) ||
+		(!rdev->constraints->boot_on && rdev->constraints->always_on)) {
 		ret = _regulator_do_set_voltage(rdev,
 						rdev->constraints->min_uV,
 						rdev->constraints->max_uV);
I'm not sure I understand the intended logic there.  Voltage constraints
and enable/disable constraints are orthogonal here.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help