Re: [PATCH v5 3/4] regulator: qcom-rpmh: readback voltage/bypass/mode/status set during bootup
Mark Brown <[email protected]> Sat, 1 Aug 2026 00:39:39 +0100
| Newsgroups | org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Jul 30, 2026 at 01:40:05PM +0530, Kamal Wadhwa wrote: > On Thu, Jul 30, 2026 at 12:11:26AM +0100, Mark Brown wrote: > > It's certainly much less likely to be an issue. There's some similar > > issues around enables for exclusive regulatorss though, and I wouldn't > > discount lower voltages being an issue (off the top of my head I've got > > a feeling MMC needs to lower voltages to up clock rates but I could be > > misremembering the use case). Whole thing is a massive can of worms, > > that's why it's not been addressed :/ > Do you think allowing this behaviour via a new regulator DT prop like > `regulator-hold-on-boot` to allow per-regulator control.. rather then applying to > all the regulators which are ON at boot.. may help address some of those concerns? Possibly, though it's all feeling very implementation and not really DT. > IMHO, from the design point of view it has to be either allowing all the requests > OR allow only the up-ing of the voltage/mode till all clients are up, may be needed. Like I say I'm not sure anything survives special cases well.
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmptMjsACgkQJNaLcl1U h9C+7Qf/UgPH6g7uthgryPWeBlsDMUXqJjxltaEYFigMu58pUrYZQSUFfvZIR1So LzhKmYdxO4yJ5ie2J/BuajcxkgHEi1ORDXX3uxelvUQru66IkajMEIHMky3p+L/F hc0RBkA7M3cL+ZN/ONylL46bV9dVdQortyRcbl/kwgHYLXeTgEJ1mZG0cPJUxA28 RGg4RW4WOMcM/YlMz9a3ZuPoWqMwKfbRgcE+SgBzhrsUCDVjRrRwpt3FR++m7nld V1X7kAlbZ7fvk101X3BsR5U74Wl8DvunEkAH+hyJSyN7/B0T5IHhQld9ykTeaEnX o/epgI/SbkZi83EIf8NFI/HFAvYl5w== =ObXl -----END PGP SIGNATURE-----