FAILED: patch "[PATCH] i2c: qcom-cci: drop custom suspend/resume and rely on runtime" failed to apply to 6.12-stable tree
Subsystems (3)
[email protected]
maintainerThe patch below does not apply to the 6.12-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
To reproduce the conflict and resubmit, you may use the following commands:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.12.y
git checkout FETCH_HEAD
git cherry-pick -x b08c9857aa1f5f3a81d375d6d4bb1d8b92f22ebc
# <resolve conflicts, build, test, etc.>
git commit -s
git send-email --to '<[email protected]>' --in-reply-to '2026080542-curse-dispersed-597e@gregkh' --subject-prefix 'PATCH 6.12.y' 'HEAD^..'
Possible dependencies:
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From b08c9857aa1f5f3a81d375d6d4bb1d8b92f22ebc Mon Sep 17 00:00:00 2001
From: Wenmeng Liu <[email protected]>
Date: Thu, 25 Jun 2026 17:42:45 +0800
Subject: [PATCH] i2c: qcom-cci: drop custom suspend/resume and rely on runtime
PM helpers
cci_resume() unconditionally calls cci_resume_runtime() regardless of the runtime PM state.
If the device is already runtime-suspended before system suspend, the clock is re-enabled while runtime_status remains RPM_SUSPENDED. As a result, pm_request_autosuspend() does not arm the timer, leaving the clock permanently enabled.
drivers/i2c/busses/i2c-qcom-cci.c +1 -17
@@ -492,24 +492,8 @@ static int __maybe_unused cci_resume_runtime(struct device *dev)return 0 ; } -static int __maybe_unused cci_suspend (struct device *dev) -{ -if (!pm_runtime_suspended (dev)) -return cci_suspend_runtime (dev); - -return 0 ; -} - -static int __maybe_unused cci_resume (struct device *dev) -{ -cci_resume_runtime (dev); -pm_request_autosuspend (dev); - -return 0 ; -} -static const struct dev_pm_ops qcom_cci_pm = { - SET_SYSTEM_SLEEP_PM_OPS(cci_suspend, cci_resume) + SET_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend, pm_runtime_force_resume)SET_RUNTIME_PM_OPS (cci_suspend_runtime, cci_resume_runtime,NULL ) };
Sasha Levin
maintainerPATCH 1/3 i2c: imx: make controller available until system suspend_noirq() and from resume_noirq()
From: Carlos Song <[email protected]>
[ Upstream commit 358025ac091e5a54f9819b33ee9c7cb07c55ee5d ]
Put runtime PM to resume state between suspend() and suspend_noirq(), resume_noirq() and resume(), because some I2C devices need the controller on to perform communication during this period.
The controller can't be woken up once runtime pm is disabled and in runtime autosuspended state.
The problem can be easily reproduced on the I.MX8MQ platform:
the PMIC needs to be used to enable regulator when the system resumes. When the PMIC uses the I2C controller, I2C runtime pm has not been enabled, so in i2c xfer(), pm_runtime_resume_and_get() will return an error, which causes data transfer to fail. Therefore, regulators cannot be enabled and system resume hangs.
Here is resume error log:
[ 53.888902] galcore 38000000.gpu3d: PM: calling genpd_resume_noirq @ 529, parent: platform [ 53.897203] i2c_imx_xfer, pm_runtime_resume_and_get is -13 [ 53.902713] imx-pgc imx-pgc-domain.5: failed to enable regulator: -EACCES [ 53.909518] galcore 38000000.gpu3d: PM: genpd_resume_noirq returned 0 after 12331 usecs [ 53.917545] mxc_hantro 38300000.vpu: PM: calling genpd_resume_noirq @ 529, parent: soc@0 [ 53.925659] i2c_imx_xfer, pm_runtime_resume_and_get is -13 [ 53.931157] imx-pgc imx-pgc-domain.6: failed to enable regulator: -EACCES
I.MX8MQ system resume normally after applying the fix. Here is resume log:
[ 71.068807] galcore 38000000.gpu3d: PM: calling genpd_resume_noirq @ 530, parent: platform [ 71.077103] i2c_imx_xfer, pm_runtime_resume_and_get is 0 [ 71.083578] galcore 38000000.gpu3d: PM: genpd_resume_noirq returned 0 after 6490 usecs [ 71.091526] mxc_hantro 38300000.vpu: PM: calling genpd_resume_noirq @ 530, parent: soc@0 [ 71.099638] i2c_imx_xfer, pm_runtime_resume_and_get is 0 [ 71.106091] mxc_hantro 38300000.vpu: PM: genpd_resume_noirq returned 0 after 6458 usecs
Stable-dep-of: b08c9857aa1f ("i2c: qcom-cci: drop custom suspend/resume and rely on runtime PM helpers")
--- drivers/i2c/busses/i2c-imx.c | 39 +++++++++++++++++++++++++++++++++++- 1 file changed, 38 insertions(+), 1 deletion(-)
drivers/i2c/busses/i2c-imx.c +38 -1
@@ -1512,7 +1512,8 @@ static int i2c_imx_probe(struct platform_device *pdev) goto rpm_disable;/* Request IRQ */ - ret =request_irq (irq, i2c_imx_isr,IRQF_SHARED , pdev->name, i2c_imx); + ret =request_irq (irq, i2c_imx_isr,IRQF_SHARED |IRQF_NO_SUSPEND , + pdev->name, i2c_imx);if (ret) {dev_err (&pdev->dev,"can't claim irq %d\n" , irq); goto rpm_disable;
@@ -1620,7 +1621,43 @@ static int i2c_imx_runtime_resume(struct device *dev)return ret; } +static int i2c_imx_suspend (struct device *dev) +{ +/* +* Some I2C devices may need the I2C controller to remain active +* during resume_noirq() or suspend_noirq(). If the controller is +* autosuspended, there is no way to wake it up once runtime PM is +* disabled (in suspend_late()). +* +* During system resume, the I2C controller will be available only +* after runtime PM is re-enabled (in resume_early()). However, this +* may be too late for some devices. +* +* Wake up the controller in the suspend() callback while runtime PM +* is still enabled. The I2C controller will remain available until +* the suspend_noirq() callback (pm_runtime_force_suspend()) is +* called. During resume, the I2C controller can be restored by the +* resume_noirq() callback (pm_runtime_force_resume()). +* +* Finally, the resume() callback re-enables autosuspend, ensuring +* the I2C controller remains available until the system enters +* suspend_noirq() and from resume_noirq(). +*/ +return pm_runtime_resume_and_get (dev); +} + +static int i2c_imx_resume (struct device *dev) +{ +pm_runtime_mark_last_busy (dev); +pm_runtime_put_autosuspend (dev); + +return 0 ; +} +static const struct dev_pm_ops i2c_imx_pm_ops = { + NOIRQ_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend, + pm_runtime_force_resume) + SYSTEM_SLEEP_PM_OPS(i2c_imx_suspend, i2c_imx_resume)RUNTIME_PM_OPS (i2c_imx_runtime_suspend, i2c_imx_runtime_resume,NULL ) };
Signature · 1 line
2.53.0
Sasha Levin
maintainerPATCH 2/3 i2c: Remove redundant pm_runtime_mark_last_busy() calls
From: Sakari Ailus <[email protected]>
[ Upstream commit ae11e08c3d0c78d08dac4cea30bf39ede2130b03 ]
pm_runtime_put_autosuspend(), pm_runtime_put_sync_autosuspend(), pm_runtime_autosuspend() and pm_request_autosuspend() now include a call to pm_runtime_mark_last_busy(). Remove the now-reduntant explicit call to pm_runtime_mark_last_busy().
Stable-dep-of: b08c9857aa1f ("i2c: qcom-cci: drop custom suspend/resume and rely on runtime PM helpers")
--- drivers/i2c/busses/i2c-qcom-cci.c | 1 - 1 file changed, 1 deletion(-)
drivers/i2c/busses/i2c-qcom-cci.c +0 -1
@@ -509,7 +509,6 @@ static int __maybe_unused cci_suspend(struct device *dev)static int __maybe_unused cci_resume (struct device *dev) {cci_resume_runtime (dev); -pm_runtime_mark_last_busy (dev);pm_request_autosuspend (dev);return 0 ;
Signature · 1 line
2.53.0
Re: [PATCH 6.12.y 2/3] i2c: Remove redundant pm_runtime_mark_last_busy() calls
Hi Sasha,
Quoted 9 lines · Sasha Levin
From: Sakari Ailus <[email protected]>
[ Upstream commit
ae11e08c3d0c78d08dac4cea30bf39ede2130b03]
pm_runtime_put_autosuspend(),pm_runtime_put_sync_autosuspend(),pm_runtime_autosuspend()andpm_request_autosuspend()now include a call topm_runtime_mark_last_busy(). Remove the now-reduntant explicit call topm_runtime_mark_last_busy().
Quoted 5 lines
Signed-off-by Sakari Ailus <[email protected]>Acked-by Andi Shyti <[email protected]>Signed-off-by Wolfram Sang <[email protected]>Stable-dep-of:
b08c9857aa1f("i2c: qcom-cci: drop custom suspend/resume and rely on runtime PM helpers")Signed-off-by Sasha Levin <[email protected]>
Please don't.
The patch adding pm_runtime_mark_last_busy() call to pm_request_autosuspend() was merged in 6.17 so before this version the explicit pm_runtime_mark_last_busy() calls are not redundant.
Signature · 3 lines
Kind regards, Sakari Ailus
Sasha Levin
maintainerRe: [PATCH 6.12.y 2/3] i2c: Remove redundant pm_runtime_mark_last_busy() calls
Quoted 5 lines
Please don't.
The patch adding
pm_runtime_mark_last_busy()call topm_request_autosuspend()was merged in 6.17 so before this version the explicitpm_runtime_mark_last_busy()calls are not redundant.
You're right, thanks for catching it. Nothing from that series was queued anywhere, so there is nothing to drop.
Signature · 2 lines
Thanks, Sasha
Sasha Levin
maintainerPATCH 3/3 i2c: qcom-cci: drop custom suspend/resume and rely on runtime PM helpers
In reply to Sasha LevinFrom: Wenmeng Liu <[email protected]>
[ Upstream commit b08c9857aa1f5f3a81d375d6d4bb1d8b92f22ebc ]
cci_resume() unconditionally calls cci_resume_runtime() regardless of the runtime PM state.
If the device is already runtime-suspended before system suspend, the clock is re-enabled while runtime_status remains RPM_SUSPENDED. As a result, pm_request_autosuspend() does not arm the timer, leaving the clock permanently enabled.
--- drivers/i2c/busses/i2c-qcom-cci.c | 18 +----------------- 1 file changed, 1 insertion(+), 17 deletions(-)
drivers/i2c/busses/i2c-qcom-cci.c +1 -17
@@ -498,24 +498,8 @@ static int __maybe_unused cci_resume_runtime(struct device *dev)return 0 ; } -static int __maybe_unused cci_suspend (struct device *dev) -{ -if (!pm_runtime_suspended (dev)) -return cci_suspend_runtime (dev); - -return 0 ; -} - -static int __maybe_unused cci_resume (struct device *dev) -{ -cci_resume_runtime (dev); -pm_request_autosuspend (dev); - -return 0 ; -} -static const struct dev_pm_ops qcom_cci_pm = { - SET_SYSTEM_SLEEP_PM_OPS(cci_suspend, cci_resume) + SET_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend, pm_runtime_force_resume)SET_RUNTIME_PM_OPS (cci_suspend_runtime, cci_resume_runtime,NULL ) };
Signature · 1 line
2.53.0