summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorPraveen Talari <praveen.talari@oss.qualcomm.com>2025-11-10 13:10:41 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-12-12 20:40:21 +0300
commit920aa96ae029954b0ae7ce22e3cf1db1c1970d9f (patch)
tree904a461d01ca9c4d822c56f9ac128044ca6a4104 /scripts/gdb/linux/utils.py
parente7dac681790556c131854b97551337aa8042215b (diff)
downloadlinux-920aa96ae029954b0ae7ce22e3cf1db1c1970d9f.tar.xz
pinctrl: qcom: msm: Fix deadlock in pinmux configuration
[ Upstream commit 1c2e70397b4125022dba80f6111271a37fb36bae ] Replace disable_irq() with disable_irq_nosync() in msm_pinmux_set_mux() to prevent deadlock when wakeup IRQ is triggered on the same GPIO being reconfigured. The issue occurs when a wakeup IRQ is triggered on a GPIO and the IRQ handler attempts to reconfigure the same GPIO's pinmux. In this scenario, msm_pinmux_set_mux() calls disable_irq() which waits for the currently running IRQ handler to complete, creating a circular dependency that results in deadlock. Using disable_irq_nosync() avoids waiting for the IRQ handler to complete, preventing the deadlock condition while still properly disabling the interrupt during pinmux reconfiguration. Suggested-by: Prasad Sodagudi <prasad.sodagudi@oss.qualcomm.com> Signed-off-by: Praveen Talari <praveen.talari@oss.qualcomm.com> Reviewed-by: Bjorn Andersson <andersson@kernel.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions