Merge tag 'regulator-v6.8' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie...

Pull regulator updates from Mark Brown:
 "The main updates for this release are around monitoring of regulators,
  largely for error handling purposes. We allow the stream of regulator
  events to be seen by userspace as netlink events and allow system
  integrators to describe individual regulators as system critical with
  information on how long the system is expected to last on error. The
  system level error handling is very much about best effort problem
  mitigation rather than providing something fully robust, the initial
  drive was to provide a mechanism for trying to avoid initiating any
  new writes to flash once we notice the power going out.

  Otherwise it's very quiet, mainly several new Qualcomm devices.

   - Support for marking regulators as system critical and providing
     information on how long the system might last with those regulators
     in a failure state, hooked into the existing critical shutdown
     error handling.

   - Optional support for generating netlink events for events, there
     are use cases for system monitoring UIs and error handling.

   - A command line option to leave unused controllable regulators
     enabled, useful for debugging. We already only disable regulators
     we were explicitly given permission to control.

   - Support for Quacomm MP5496, PM8010 and PM8937"

* tag 'regulator-v6.8' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator: (31 commits)
  regulator: event: Ensure atomicity for sequence number
  uapi: regulator: Fix typo
  regulator: Reuse LINEAR_RANGE() in REGULATOR_LINEAR_RANGE()
  dt-bindings: regulator: qcom,usb-vbus-regulator: clean up example
  regulator: qcom_smd: Add LDO5 MP5496 regulator
  regulator: qcom-rpmh: add support for pm8010 regulators
  regulator: dt-bindings: qcom,rpmh: add compatible for pm8010
  regulator: qcom-rpmh: extend to support multiple linear voltage ranges
  regulator: wm8350: Convert to platform remove callback returning void
  regulator: virtual: Convert to platform remove callback returning void
  regulator: userspace-consumer: Convert to platform remove callback returning void
  regulator: uniphier: Convert to platform remove callback returning void
  regulator: stm32-vrefbuf: Convert to platform remove callback returning void
  regulator: db8500-prcmu: Convert to platform remove callback returning void
  regulator: bd9571mwv: Convert to platform remove callback returning void
  regulator: arizona-ldo1: Convert to platform remove callback returning void
  regulator: event: Add regulator netlink event support
  regulator: event: Add regulator netlink event support
  regulator: stpmic1: Fix kernel-doc notation warnings
  regulator: palmas: remove redundant initialization of pointer pdata
  ...

diff --combined Documentation/admin-guide/kernel-parameters.txt
index 8a01b8112f0bfb80ba4fe5faf10a240660033b81,825159394da2aa3e077388ed0a64ef601310b28d..e0891ac76ab32742904cff6c3a3483fdcdd6b5c5
--- 1/Documentation/admin-guide/kernel-parameters.txt
--- 2/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@@ -970,17 -970,17 +970,17 @@@
                        buddy allocator. Bigger value increase the probability
                        of catching random memory corruption, but reduce the
                        amount of memory for normal system use. The maximum
 -                      possible value is MAX_ORDER/2.  Setting this parameter
 -                      to 1 or 2 should be enough to identify most random
 -                      memory corruption problems caused by bugs in kernel or
 -                      driver code when a CPU writes to (or reads from) a
 -                      random memory location. Note that there exists a class
 -                      of memory corruptions problems caused by buggy H/W or
 -                      F/W or by drivers badly programming DMA (basically when
 -                      memory is written at bus level and the CPU MMU is
 -                      bypassed) which are not detectable by
 -                      CONFIG_DEBUG_PAGEALLOC, hence this option will not help
 -                      tracking down these problems.
 +                      possible value is MAX_PAGE_ORDER/2.  Setting this
 +                      parameter to 1 or 2 should be enough to identify most
 +                      random memory corruption problems caused by bugs in
 +                      kernel or driver code when a CPU writes to (or reads
 +                      from) a random memory location. Note that there exists
 +                      a class of memory corruptions problems caused by buggy
 +                      H/W or F/W or by drivers badly programming DMA
 +                      (basically when memory is written at bus level and the
 +                      CPU MMU is bypassed) which are not detectable by
 +                      CONFIG_DEBUG_PAGEALLOC, hence this option will not
 +                      help tracking down these problems.
  
        debug_pagealloc=
                        [KNL] When CONFIG_DEBUG_PAGEALLOC is set, this parameter
@@@ -4136,7 -4136,7 +4136,7 @@@
                        [KNL] Minimal page reporting order
                        Format: <integer>
                        Adjust the minimal page reporting order. The page
 -                      reporting is disabled when it exceeds MAX_ORDER.
 +                      reporting is disabled when it exceeds MAX_PAGE_ORDER.
  
        panic=          [KNL] Kernel behaviour on panic: delay <timeout>
                        timeout > 0: seconds before rebooting
@@@ -5544,6 -5544,13 +5544,13 @@@
                        print every Nth verbose statement, where N is the value
                        specified.
  
+       regulator_ignore_unused
+                       [REGULATOR]
+                       Prevents regulator framework from disabling regulators
+                       that are unused, due no driver claiming them. This may
+                       be useful for debug and development, but should not be
+                       needed on a platform with proper driver support.
+ 
        relax_domain_level=
                        [KNL, SMP] Set scheduler's default relax_domain_level.
                        See Documentation/admin-guide/cgroup-v1/cpusets.rst.