[PATCH] pwm: imx-tpm: reset counter if CMOD is 0
Laurentiu Mihalcea
laurentiumihalcea111 at gmail.com
Tue Jul 1 15:01:47 PDT 2025
From: Laurentiu Mihalcea <laurentiu.mihalcea at nxp.com>
As per the i.MX93 TRM, section 67.3.2.1 "MOD register update", the value
of the TPM counter does NOT get updated when writing MOD.MOD unless
SC.CMOD != 0. Therefore, with the current code, assuming the following
sequence:
1) pwm_disable()
2) pwm_apply_might_sleep() /* period is changed here */
3) pwm_enable()
and assuming only one channel is active, if CNT.COUNT is higher than the
MOD.MOD value written during the pwm_apply_might_sleep() call then, when
re-enabling the PWM during pwm_enable(), the counter will end up resetting
after UINT32_MAX - CNT.COUNT + MOD.MOD cycles instead of MOD.MOD cycles as
normally expected.
Fix this problem by forcing a reset of the TPM counter before MOD.MOD is
written.
Signed-off-by: Laurentiu Mihalcea <laurentiu.mihalcea at nxp.com>
---
drivers/pwm/pwm-imx-tpm.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/drivers/pwm/pwm-imx-tpm.c b/drivers/pwm/pwm-imx-tpm.c
index 7ee7b65b9b90..30f271826aed 100644
--- a/drivers/pwm/pwm-imx-tpm.c
+++ b/drivers/pwm/pwm-imx-tpm.c
@@ -204,6 +204,19 @@ static int pwm_imx_tpm_apply_hw(struct pwm_chip *chip,
val |= FIELD_PREP(PWM_IMX_TPM_SC_PS, p->prescale);
writel(val, tpm->base + PWM_IMX_TPM_SC);
+ /*
+ * VERY IMPORTANT: if CMOD is set to 0 then writing
+ * MOD will NOT reset the value of the TPM counter.
+ *
+ * Therefore, if CNT.COUNT > MOD.MOD, the counter will reset
+ * after UINT32_MAX - CNT.COUNT + MOD.MOD cycles, which is
+ * incorrect.
+ *
+ * To avoid this, we need to force a reset of the
+ * counter before writing the new MOD value.
+ */
+ if (!cmod)
+ writel(0x0, tpm->base + PWM_IMX_TPM_CNT);
/*
* set period count:
* if the PWM is disabled (CMOD[1:0] = 2b00), then MOD register
--
2.34.1
More information about the linux-arm-kernel
mailing list