On Sun, Jan 18, 2015 at 04:29:02PM +0100, Hans de Goede wrote: > On 18-01-15 13:35, Mark Brown wrote: > >Right, but that's not what regulator-boot-on actually means (and I'm not > >sure why you would think it would TBH) > Well, the meaning of regulator-boot-on is not clearly defined really, to > begin we need with fixing that, currently all the bindings file says is: > - regulator-boot-on: bootloader/firmware enabled regulator If that meant anything about what to do with the regulator at runtime it would say so - it means exactly what it says. > One could easily argue that the bootloader likely has a good reason to turn > the regulator on, and that unless there is a specific driver which claims > the regulator and thus knows what to do with it it is best left alone ... That's an excessively big stretch; it doesn't reflect the reality that the bootloader is often just leaving the settings it found on initial power up alone nor the general quality of implementation concerns one often sees with bootloaders. A big use case for this feature is that there is a fairly large class of systems where the bootloader can't be relied on.
Attachment:
signature.asc
Description: Digital signature
