[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180814170617.100087-1-dianders@chromium.org>
Date: Tue, 14 Aug 2018 10:06:13 -0700
From: Douglas Anderson <dianders@...omium.org>
To: broonie@...nel.org
Cc: linux-arm-msm@...r.kernel.org, bjorn.andersson@...aro.org,
collinsd@...eaurora.org, swboyd@...omium.org,
Douglas Anderson <dianders@...omium.org>,
Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH 0/4] regulator: core: A few useful patches for regulators that need load set
These patches ought to be useful for those people who need to work
with regulator drivers where regulator_set_load() is important. The
first patch in this series actually implements real functionality.
After that patch then devices whose drivers don't know to call
regulator_set_load() are more likely to work. The rest of the patches
just work on regulator_summary to try to make it so we can confirm
that the first patch works.
Douglas Anderson (4):
regulator: core: If consumers don't call regulator_set_load() assume
max
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 | 98 ++++++++++++++++++++++++------------
drivers/regulator/internal.h | 1 +
2 files changed, 66 insertions(+), 33 deletions(-)
--
2.18.0.865.gffc8e1a3cd6-goog
Powered by blists - more mailing lists