regmap: Make regmap-mmio usable from atomic contexts
authorLars-Peter Clausen <lars@metafoo.de>
Fri, 24 May 2013 08:29:22 +0000 (10:29 +0200)
committerHuang, Tao <huangtao@rock-chips.com>
Tue, 17 Mar 2015 12:12:30 +0000 (20:12 +0800)
commit55f7b1a4c080a90d2e7bef6272a08f5eb4307a21
tree92382d882d5e061f5f9a60ac48bc48ef0b2c2b91
parent48e2666fada1cbcecad234a38d1639606eb129f1
regmap: Make regmap-mmio usable from atomic contexts

regmap-mmio uses a spinlock with spin_lock() and spin_unlock() for locking.
To be able to use the regmap API from different contexts (atomic vs non-atomic),
without the risk of race conditions, we need to use spin_lock_irqsave() and
spin_lock_irqrestore() instead. A new field, the spinlock_flags field, is added
to regmap struct to store the flags between regmap_{,un}lock_spinlock(). The
spinlock_flags field itself is also protected by the spinlock.

Thanks to Stephen Warren for the suggestion of this particular solution.

Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Reviewed-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
(cherry picked from commit 92ab1aab59c61b3e05200b9aa0e05ab770059142)
drivers/base/regmap/internal.h
drivers/base/regmap/regmap.c