From: Douglas Anderson <dianders@chromium.org>
To: broonie@kernel.org
Cc: linux-arm-msm@vger.kernel.org, bjorn.andersson@linaro.org,
collinsd@codeaurora.org, swboyd@chromium.org,
Douglas Anderson <dianders@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] regulator: core: Improve regulator_summary
Date: Thu, 16 Aug 2018 13:28:00 -0700 [thread overview]
Message-ID: <20180816202803.250079-1-dianders@chromium.org> (raw)
The first two patches in this series are useful for those who want to
see the load requested by regulator consumers and also what opmode
they're running in (these two concepts are sometimes linked).
The third patch adds some missing locking for regulator_summary.
All three patches could be applied separately but some rebasing would
be required since the patches touch much of the same code.
Changes in v2:
- No longer consider consumers that don't call regulator_set_load().
Douglas Anderson (3):
regulator: core: Add the opmode to regulator_summary
regulator: core: Add consumer-requested load in regulator_summary
regulator: core: Add locking to debugfs regulator_summary
drivers/regulator/core.c | 78 ++++++++++++++++++++++++----------------
1 file changed, 48 insertions(+), 30 deletions(-)
--
2.18.0.865.gffc8e1a3cd6-goog
next reply other threads:[~2018-08-16 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 20:28 Douglas Anderson [this message]
2018-08-16 20:28 ` [PATCH v2 1/3] regulator: core: Add the opmode to regulator_summary Douglas Anderson
2018-08-16 20:28 ` [PATCH v2 2/3] regulator: core: Add consumer-requested load in regulator_summary Douglas Anderson
2018-08-16 20:28 ` [PATCH v2 3/3] regulator: core: Add locking to debugfs regulator_summary Douglas Anderson
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=20180816202803.250079-1-dianders@chromium.org \
--to=dianders@chromium.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=collinsd@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.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).