Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
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 0/4] regulator: core: A few useful patches for regulators that need load set
Date:   Tue, 14 Aug 2018 10:06:13 -0700
Message-Id: <20180814170617.100087-1-dianders@chromium.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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