From: Andy Shevchenko andriy.shevchenko@linux.intel.com
commit ec3decd21380081e3b5de4ba8d85d90a95f201a0 upstream.
It's a repetition of the commit aa58a21ae378 ("gpio: pca953x: disable regmap locking") which states the following:
This driver uses its own locking but regmap silently uses a mutex for all operations too. Add the option to disable locking to the regmap config struct.
Fixes: bcf41dc480b1 ("gpio: pca953x: fix handling of automatic address incrementing") Cc: Uwe Kleine-König u.kleine-koenig@pengutronix.de Signed-off-by: Andy Shevchenko andriy.shevchenko@linux.intel.com Reviewed-by: Uwe Kleine-König u.kleine-koenig@pengutronix.de Signed-off-by: Bartosz Golaszewski bgolaszewski@baylibre.com Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org
--- drivers/gpio/gpio-pca953x.c | 1 + 1 file changed, 1 insertion(+)
--- a/drivers/gpio/gpio-pca953x.c +++ b/drivers/gpio/gpio-pca953x.c @@ -398,6 +398,7 @@ static const struct regmap_config pca953 .writeable_reg = pca953x_writeable_register, .volatile_reg = pca953x_volatile_register,
+ .disable_locking = true, .cache_type = REGCACHE_RBTREE, .max_register = 0x7f, };