Hi Mark, On 6 January 2012 12:19, Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > On Thu, Jan 05, 2012 at 08:07:53PM +0100, Lars-Peter Clausen wrote: > >> > +- lcd,pwrctrl-min-uV: If a regulator controls the Vcc voltage of the lcd panel, >> > + this property specifies the minimum voltage the regulator should supply. >> > + The value of this property should in in micro-volts. >> > +- lcd,pwrctrl-max-uV: If a regulator controls the Vcc voltage of the lcd panel, >> > + this property specifies the maximum voltage the regulator should limit to >> > + on the Vcc line. The value of this property should in in micro-volts. > >> The min and max voltage should rather be specified through the regulator >> constraints. > > In principle it should be specified in both places to account for shared > supplies though for all practical purposes for an LCD panel I can't see > multiple users sharing the same regulator and varying the voltage at > runtime. It is assumed here that the boot loader as not set the output voltage of the regulator that supports variable voltage ranges. So these values help in setting up the regulator for LCD display. > >> > + if (lcd_enable) { >> > + if ((pd->min_uV || pd->max_uV) && >> > + regulator_set_voltage(lp->regulator, >> > + pd->min_uV, pd->max_uV)) >> > + dev_info(lp->dev, >> > + "regulator voltage set failed\n"); >> > + if (regulator_enable(lp->regulator)) >> > + dev_info(lp->dev, "failed to enable regulator\n"); >> > + } else { >> > + regulator_disable(lp->regulator); >> > + } > >> I think you have to make sure that the regulator enable and disable calls are >> balanced. > > Yes. Ok. I will fix this. > >> > +#ifdef CONFIG_OF > >> I think you can remove all the CONFIG_OF ifdefs, the of API should stub itself out. > > It's reasonably idiomatic to do this if the parsing code is in a > separate function. Thanks for your review Mark. Regards, Thomas. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html