[PATCH v2 2/2] pinctrl: qcom: lpass-lpi: Force runtime suspend on system sleep

From: Gopi Chandra Sekhar Reddy Kanala

Date: Wed Nov 18 2026 - 08:38:21 EST


The LPASS LPI pin controllers vote for their LPASS clocks through pm_clk
and only implement runtime PM callbacks. Their consumers, such as the
SoundWire controllers, keep them runtime active through their device
links. If a consumer is active when system suspend starts, or is resumed
during it, the runtime PM usage count the PM core holds from the prepare
phase keeps the pin controller from runtime suspending, and its clock
votes are held for the whole suspend. On Glymur CRD this keeps CX and
DDR from collapsing in s2idle.

Use pm_runtime_force_suspend() and pm_runtime_force_resume() as the
system sleep callbacks in the common dev_pm_ops, so the clocks are
always released at system suspend for all the SoC-specific drivers.
Consumers are suspended before their suppliers, so the pin controller
goes down after them and comes back before them.

Signed-off-by: Gopi Chandra Sekhar Reddy Kanala <gopi.kanala@xxxxxxxxxxxxxxxx>
---
drivers/pinctrl/qcom/pinctrl-lpass-lpi.c | 1 +
1 file changed, 1 insertion(+)

diff --git a/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c b/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c
index 1f1635ec53d7..f693e5101a7b 100644
--- a/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c
+++ b/drivers/pinctrl/qcom/pinctrl-lpass-lpi.c
@@ -612,6 +612,7 @@ void lpi_pinctrl_remove(struct platform_device *pdev)
EXPORT_SYMBOL_GPL(lpi_pinctrl_remove);

EXPORT_GPL_DEV_PM_OPS(lpi_pinctrl_pm_ops) = {
+ SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend, pm_runtime_force_resume)
RUNTIME_PM_OPS(pm_clk_suspend, pm_clk_resume, NULL)
};


--
2.43.0