Messages in this thread | | | Date | Mon, 23 Sep 2019 11:14:31 -0700 | From | Mark Brown <> | Subject | Re: [PATCH 1/3] regulator: core: fix boot-on regulators use_count usage |
| |
On Mon, Sep 23, 2019 at 11:02:26AM -0700, Doug Anderson wrote:
> I will freely admit my ignorance here, but I've always been slightly > confused by the "always-on" vs. "boot-on" distinction...
> The bindings say:
> regulator-always-on: > description: boolean, regulator should never be disabled
> regulator-boot-on: > description: bootloader/firmware enabled regulator
> For 'boot-on' that's a bit ambiguous about what it means. The > constraints have a bit more details:
Boot on means that it's powered on when the kernel starts, it's for regulators that we can't read back the status of.
> ...but then that begs the question of why we have two attributes? > Maybe this has already been discussed before and someone can point me > to a previous discussion? We should probably make it more clear in > the bindings and/or the constraints.
boot-on just refers to the status at boot, we can still turn those regulators off later on if we want to. [unhandled content-type:application/pgp-signature] | |