UPSTREAM: regulator: core: remove lockdep assert from suspend_prepare
authorTero Kristo <t-kristo@ti.com>
Mon, 18 Apr 2016 11:49:53 +0000 (14:49 +0300)
committerHuang, Tao <huangtao@rock-chips.com>
Thu, 22 Sep 2016 12:12:28 +0000 (20:12 +0800)
commitc1834e4eb46756c7bdf6a92b27830f04922772dd
treef28558541f5be803fd59cbfba24015a88a57d500
parent05b41faf3f6c5d537b7d7914870c8f628bc467ac
UPSTREAM: regulator: core: remove lockdep assert from suspend_prepare

suspend_prepare can be called during regulator init time also, where
the mutex is not locked yet. This causes a false lockdep warning.
To avoid the problem, remove the lockdep assertion from the function
causing the issue. An alternative would be to lock the mutex during
init, but this would cause other problems (some APIs used during init
will attempt to lock the mutex also, causing deadlock.)

Change-Id: I4a4367f3ebc9c7a00d6a08b547f2cebecd600483
Signed-off-by: Tero Kristo <t-kristo@ti.com>
Reported-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Huang, Tao <huangtao@rock-chips.com>
(cherry picked from commit 07c5c3ad98926dc15d31aa86de62fd4170f2a745)
drivers/regulator/core.c