From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Matti Vaittinen <mazziesaccount@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] regulator: misc fixes
Date: Thu, 16 May 2024 11:52:44 +0300 [thread overview]
Message-ID: <cover.1715848512.git.mazziesaccount@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]
This series adds couple of a bit unrelated fixes/improvements which I
implemented while working to support yet another ROHM PMIC.
Patch1 addresses a potential problem where the voltage selector for
pickable-ranges is used in same fashion as a 'apply-bit'. Eg, when a
regulator voltage is changed so that also the range changes, the effect
of the range and voltage selector change is not taken into account until
the voltage selector is written to hardware. In such case caching the
voltage-selector value will cause the voltage range change to not change
the actual output voltage.
Patch2 is a fix to ROHM bd71818 and bd71879 low-power state specific
voltage settings where some of the voltages were common to many states.
The old behaviour was that changing voltage for one state caused it to
change for all states. This had a potential impact of accidentally
changing the runtime voltage when trying to configure voltage for a
low-power state, potentially hurting the boot-up process.
Patch3 is just a minor print improvement to help pinpointing unsupported
voltage in device-tree.
Series is based on v6.9
---
Matti Vaittinen (3):
regulator: don't cache vsel to ensure voltage setting
regulator: bd71828: Don't overwrite runtime voltages
regulator: rohm-regulator: warn if unsupported voltage is set
drivers/regulator/bd71828-regulator.c | 58 +--------------------------
drivers/regulator/helpers.c | 10 ++++-
drivers/regulator/rohm-regulator.c | 4 ++
3 files changed, 14 insertions(+), 58 deletions(-)
base-commit: a38297e3fb012ddfa7ce0321a7e5a8daeb1872b6
--
2.44.0
--
Matti Vaittinen, Linux device drivers
ROHM Semiconductors, Finland SWDC
Kiviharjunlenkki 1E
90220 OULU
FINLAND
~~~ "I don't think so," said Rene Descartes. Just then he vanished ~~~
Simon says - in Latin please.
~~~ "non cogito me" dixit Rene Descarte, deinde evanescavit ~~~
Thanks to Simon Glass for the translation =]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-05-16 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 8:52 Matti Vaittinen [this message]
2024-05-16 8:53 ` [PATCH 1/3] regulator: don't cache vsel to ensure voltage setting Matti Vaittinen
2024-05-16 11:33 ` Mark Brown
2024-05-16 14:14 ` Matti Vaittinen
2024-05-16 8:54 ` [PATCH 2/3] regulator: bd71828: Don't overwrite runtime voltages Matti Vaittinen
2024-05-16 8:55 ` [PATCH 3/3] regulator: rohm-regulator: warn if unsupported voltage is set Matti Vaittinen
2024-05-16 15:58 ` [PATCH 0/3] regulator: misc fixes Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1715848512.git.mazziesaccount@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox