tree 456fc66eb1e16b2d8b879cdcb2d7d342b29076d8
parent e6f0b08a036734552628ab788ecb528ca53814ab
author Kory Maincent <kory.maincent@bootlin.com> 1710234998 +0100
committer Mark Brown <broonie@kernel.org> 1710251757 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmXwXu0ACgkQJNaLcl1U
 h9Aidgf/SDgl+1i6QnySQuyz7vciAQWLPf+o9+Kzda0xMbAtI8ox4+Zi1tIWEUfE
 7O1EZUnu92IHrnPYQaH7tBA/4LWzwiSWonGICHEqTkWfCOPgRPDY7jh44mtNhUHj
 eS6qTgVAZPqvULO/dpvauJWF2GkcYwitkfHCx1A2685jQR1jyriQ9kgXtXBrboxx
 IrAim+xqImJLcwuy3LhvR7tf+CqrY2+Mw2uzGKb3QBc0i7TcIbLzCfgycjflNfqX
 KJw3+z1qIwM0kHG+Pph+9HKjjfwkGZhYtvRObXlzQR2YhhdZe+4wMVET7TIZIgaQ
 1RghGeXX2i1e5UguOsVoEoQ2O5ttng==
 =mr+c
 -----END PGP SIGNATURE-----

regulator: core: Propagate the regulator state in case of exclusive get

Previously, performing an exclusive get on an already-enabled regulator
resulted in inconsistent state initialization between child and parent
regulators. While the child's counts were updated, its parent's counters
remained unaffected.

Consequently, attempting to disable an already-enabled exclusive regulator
triggered unbalanced disables warnings from its parent regulator.

This commit addresses the issue by propagating the enable state to the
parent regulator using a regulator_enable call. This ensures consistent
state management across the regulator hierarchy, preventing warnings!

Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
Link: https://msgid.link/r/20240312091638.1266167-1-kory.maincent@bootlin.com
Signed-off-by: Mark Brown <broonie@kernel.org>