On Friday 06 March 2009, Mark Brown wrote: > > Later, I found out that in set_machine_constraints(),ops->enable() is > > being called if the boot_on flag is set. What is the purpose of doing > > this? Since the regulator is already enabled, why we are calling the > > ops->enable() to do the same again? In my opinion, regulator_enable() > > This ensures that the regulator is actually turned on. Previously > boot_on was equivalent to always_on and there was no way for a machine > driver to turn a regulator on at startup so the semantics of boot_on > were changed slightly to be usable to switch a regulator on at boot. The boot_on semantics are kind of odd then ... What I thought they meant: Bootloader turned this on. What you describe above: Kernel turn this on during startup. Versus normal behavior: Consumer turns it on, as needed. I wouldn't have thought there would be a need for that second case, since the board-specific init code can just define a consumer that turns it on if that's what it needs. - Dave -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
