linux-kernel - [PATCH v2 0/3] regulator: core: Improve regulator

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20180816202803.250079-1-dianders@chromium.org>
Date:   Thu, 16 Aug 2018 13:28:00 -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 v2 0/3] regulator: core: Improve regulator_summary

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