tree eca3fa61e4a71f60ae4b04d0aea8d4970e5bd433
parent 705e2a905a0407c3fffb248b43c8d7d1de6b4e51
author Steve Twiss <stwiss.opensource@diasemi.com> 1551193199 +0000
committer Mark Brown <broonie@kernel.org> 1552489798 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQFHBAABCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlyJHUYTHGJyb29uaWVA
 a2VybmVsLm9yZwAKCRAk1otyXVSH0FJZB/92Q+gGn+VR71mDi2kKfB27ZRt7Gt9+
 JxohEJoKmWw1xOrepJd28ZuS+RyWVpioe//NHhM4XgnOBsfIro4y1NqsNCW7BHds
 S/anEOK8hNd+s3D2t9BaWVO87BckRK+tCj0MhMXBBKYYUWX4hVYWCEhMXRYqZID5
 f6PRK/DxuedX/YGxJqiimlRoy5LpYaZMbxYWYjwcuck1pG2mE00tfIosnNJrSlfs
 71Uep/xyXntoo7ZBc4+I7RgbuxklTEAtQn72nZRs/0rtpOSAOT++f2SQ2MlTXW7t
 yz7qFWRxN2lEi+WHk3+z6bQ3y04tssd3K0rQvs4z/8NvzzSPwQOEvctU
 =O3Yx
 -----END PGP SIGNATURE-----

regulator: da9055: Fix notifier mutex lock warning

The mutex for the regulator_dev must be controlled by the caller of
the regulator_notifier_call_chain(), as described in the comment
for that function.

Failure to mutex lock and unlock surrounding the notifier call results
in a kernel WARN_ON_ONCE() which will dump a backtrace for the
regulator_notifier_call_chain() when that function call is first made.
The mutex can be controlled using the regulator_lock/unlock() API.

Fixes: f6130be652d0 ("regulator: DA9055 regulator driver")
Suggested-by: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
Signed-off-by: Mark Brown <broonie@kernel.org>