diff options
| author |   Bartosz Golaszewski <brgl@bgdev.pl> | 2017-12-06 15:26:21 +0100 |
|---|---|---|
| committer |   Mark Brown <broonie@kernel.org> | 2017-12-06 15:30:02 +0000 |
| commit | c9b41fcf272b4926b373d21c2b83dfe374313780 (patch) | |
| tree | f65469c68d6f4bc64c9365a42e482f1e9b54fc8e /Kconfig | |
| parent | Linux 4.15-rc1 (diff) | |
| download | linux-dev-c9b41fcf272b4926b373d21c2b83dfe374313780.tar.xz linux-dev-c9b41fcf272b4926b373d21c2b83dfe374313780.zip | |
regmap: allow to disable all locking mechanisms
We have a use case in the at24 EEPROM driver (recently converted to
using regmap instead of raw i2c/smbus calls) where we read from/write
to the regmap in a loop, while protecting the entire loop with
a mutex.
Currently this implicitly makes us use two mutexes - one in the driver
and one in regmap. While browsing the code for similar use cases I
noticed a significant number of places where locking *seems* redundant.
Allow users to completely disable any locking mechanisms in regmap
config.
Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions