summaryrefslogtreecommitdiffstats
path: root/drivers/base/regmap
diff options
context:
space:
mode:
authorMark Brown <broonie@opensource.wolfsonmicro.com>2013-05-09 14:35:49 +0100
committerMark Brown <broonie@opensource.wolfsonmicro.com>2013-05-12 19:01:39 +0400
commitf9e464a566a1c3c9b71558e5523288b5432c3e3f (patch)
treebe50d4e5a7edb42bc05a8803aa7dcff898aa9ed1 /drivers/base/regmap
parent68e850d80df934b9c9c15d8a0956512cb3b6f1fc (diff)
downloadlinux-f9e464a566a1c3c9b71558e5523288b5432c3e3f.tar.gz
linux-f9e464a566a1c3c9b71558e5523288b5432c3e3f.tar.bz2
linux-f9e464a566a1c3c9b71558e5523288b5432c3e3f.zip
regmap: debugfs: Don't mark lockdep as broken due to debugfs write
A register write to hardware is reasonably unlikely to cause locking dependency issues, the reason we're tainting is that unexpected changes in the hardware configuration may confuse drivers. Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Diffstat (limited to 'drivers/base/regmap')
-rw-r--r--drivers/base/regmap/regmap-debugfs.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/base/regmap/regmap-debugfs.c b/drivers/base/regmap/regmap-debugfs.c
index 975719bc3450..8772fb77e6ed 100644
--- a/drivers/base/regmap/regmap-debugfs.c
+++ b/drivers/base/regmap/regmap-debugfs.c
@@ -281,7 +281,7 @@ static ssize_t regmap_map_write_file(struct file *file,
return -EINVAL;
/* Userspace has been fiddling around behind the kernel's back */
- add_taint(TAINT_USER, LOCKDEP_NOW_UNRELIABLE);
+ add_taint(TAINT_USER, LOCKDEP_STILL_OK);
ret = regmap_write(map, reg, value);
if (ret < 0)