From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PATCH 0/2] regulator: stepping set voltage for regmap users
Date: Mon, 10 Dec 2018 16:10:22 +0100 [thread overview]
Message-ID: <20181210151024.3906-1-brgl@bgdev.pl> (raw)
I'm working on a regulator driver for a PMIC whose programming manual
suggests manual ramping of the regulator output voltage one step at a
time (when the regulator is enabled).
Initially I wanted to simply put it into the driver but noticed that
some other modules (e.g. rk808) seem to be doing the same and could
potentially benefit from putting this helper into the regulator core
code.
The first patch makes _regulator_is_enabled() available to regulator
code outside core.c. The second provides the helper described above.
If accepted this will be used in a driver submitted for review after
the 4.21 merge window.
Bartosz Golaszewski (2):
regulator: make _regulator_is_enabled() available in internal.h
regulator: provide regulator_set_voltage_sel_regmap_step() helper
drivers/regulator/core.c | 3 +-
drivers/regulator/helpers.c | 48 ++++++++++++++++++++++++++++++++
drivers/regulator/internal.h | 1 +
include/linux/regulator/driver.h | 2 ++
4 files changed, 52 insertions(+), 2 deletions(-)
--
2.19.1
next reply other threads:[~2018-12-10 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 15:10 Bartosz Golaszewski [this message]
2018-12-10 15:10 ` [PATCH 1/2] regulator: make _regulator_is_enabled() available in internal.h Bartosz Golaszewski
2018-12-10 15:10 ` [PATCH 2/2] regulator: provide regulator_set_voltage_sel_regmap_step() helper Bartosz Golaszewski
2018-12-10 15:41 ` Mark Brown
2018-12-11 10:55 ` Bartosz Golaszewski
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=20181210151024.3906-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).