Tzung-Bi Shih 56ab29ec6f pinctrl: mediatek: use spin lock in mtk_rmw
Commit 42a46434e9b1 ("pinctrl: add lock in mtk_rmw function.") uses
mutex lock in mtk_rmw.  However the function is possible called from
atomic context.

For example call trace:
  mutex_lock+0x28/0x64
  mtk_rmw+0x38/0x80
  [snip]
  max98357a_daiops_trigger+0x8c/0x9c
  soc_pcm_trigger+0x5c/0x10c

The max98357a_daiops_trigger() could run in either atomic or non-atomic
context.  As a result, dmesg shows some similar messages: "BUG: sleeping
function called from invalid context at kernel/locking/mutex.c:254".

Uses spin lock in mtk_rmw instead.

Fixes: 42a46434e9b1 ("pinctrl: add lock in mtk_rmw function.")
Signed-off-by: Tzung-Bi Shih <tzungbi@google.com>
Link: https://lore.kernel.org/r/20210419093449.3125704-1-tzungbi@google.com
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
2021-04-22 01:53:29 +02:00
..
2021-02-26 09:41:03 -08:00
2021-02-24 10:25:37 -08:00
2021-03-04 12:51:57 -08:00
2021-02-22 14:44:39 -08:00
2021-02-23 15:05:10 -08:00
2021-03-29 12:20:07 +02:00
2021-02-22 10:05:12 -08:00
2021-02-22 14:27:07 -08:00
2021-02-22 09:52:55 -08:00
2021-02-28 15:48:25 -08:00
2021-03-05 12:26:24 -08:00
2021-02-15 15:41:56 +01:00
2021-02-25 09:56:08 -08:00
2021-03-04 11:24:47 -08:00
2021-02-24 10:25:37 -08:00
2021-02-24 09:35:54 -08:00
2021-02-24 10:25:37 -08:00
2021-02-25 09:56:08 -08:00
2021-02-22 10:31:29 -08:00
2021-02-25 12:23:49 -08:00
2021-02-22 09:29:42 -08:00
2021-02-26 14:16:06 -08:00
2021-02-22 14:34:00 -08:00
2021-02-28 11:51:20 -08:00
2021-02-24 10:25:37 -08:00
2021-02-25 10:17:31 -08:00
2021-02-24 10:43:40 -08:00
2021-02-25 12:21:08 -08:00
2021-02-25 12:10:22 -08:00
2021-02-26 10:04:45 -08:00