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>

diff --git a/drivers/base/regmap/regmap-debugfs.c b/drivers/base/regmap/regmap-debugfs.c
index 975719bc345008a4d396c72b5b1e160c50b8d2a8..8772fb77e6ed3fbe2c88d9b70389c7bd7608c818 100644 (file)
--- 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)