Re: [PATCH v4 1/9] regulator: core: Add "enable and wait" functions
Mark Brown <[email protected]>
| Newsgroups | org.infradead.lists.linux-mediatek,dev.linux.lists.chrome-platform,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-i2c,org.kernel.vger.linux-input,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Aug 11, 2026 at 08:20:01PM +0800, Chen-Yu Tsai wrote: > In device power sequencing and initialization use cases, it is common > for the driver to enable the regulator and then wait for a certain > period of time to pass before continuing. Please don't bury core changes for subsystems in the middle of random other serieses, this is the first time I've seen this. :( > One case in particular is not optimized yet: a regulator left on either > by hardware reset default or by the bootloader, but does not have the > "regulator-boot-on" property set. As the enable timestamp only gets > updated when enabled by a consumer or by the core, the first enablement > always needs to wait. Just take a timestamp during registration if the regulator is enabled, we check if it's enabled anyway so we may as well take that as the last time the enable happened.
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmp7GNoACgkQJNaLcl1U h9BeJwf+NkLsGljQXwokTuIRv+ig4jdUnALSbb8+0ZIRrZ+96sNEkwqEODMFToii m8eaYIc5o7+PoXbWo0li99AO3IoZAw8otyweKMS8qGabP4EmHx4RQlRtmT5EB8GN KKPHgVNpuTTrP8/pNacCVJUZ2keDYA98Mqugtuxo14y9ZOp4HKevYQvXdimF1sXM 43lEEtZJ/tnW/FlDVUtljN42u51I1ly4Tc2SUvquTs1V5sOJGEFvAftOVMTQWZeb dGPhAbqkevlNFnoQqIGB/9AeSYm8PpMRwVbveoDgBKXYMiHKpxokg2Vib+LH/6rn wYimUcQhuqXcIN2eQrOr0HIWPeB9Qg== =2Up9 -----END PGP SIGNATURE-----