Skip to contentSkip to conversation

pwm: pxa: Fixes for enable/disable transitions

PATCH Superseded Doug Brown 2 participants 15 messages Oct 3, 2022 – Nov 13, 2022

Subsystems (2)

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore

Doug Brown

author
#0 lore raw

v2 cover pwm: pxa: Fixes for enable/disable transitions

I ran into a couple of problems while getting this driver working on the PXA168. It wouldn't always activate properly when I turned it on, and it wouldn't always deactivate properly when I turned it off. These patches fix issues with the clock enable/disable transitions.

With these patches applied, the driver works flawlessly with my use cases on the PXA168. I don't have any other PXAxxx devices to test with.

Changes since v1:

- Remove pxa_pwm_enable and pxa_pwm_disable.
- Reorganize pxa_pwm_apply based on Uwe's suggestions.
- Enable this driver with ARCH_MMP for the PXA168.
- Add delay after clock is disabled (and inhibit brief on/off blips).

After applying the first round of suggested fixes, I discovered (while using it as a PWM backlight) that I was once again being affected by the "too quick" on->off->on transitions, which resulted in silent failure. Hopefully this isn't too crazy, but I fixed it by adding a delay to allow the last period to finish after the clock is requested to be disabled. When you turn the clock off, it stays latched on until the period finishes (because PWMCR_SD is not set). If you try to turn it back on during this time, the request is ignored and it shuts off anyway. Waiting a full period before attempting to start the clock again avoids the problem.

I also inhibited register setup if PWM is already disabled and staying disabled in an attempt to avoid unnecessary brief on/off "blips".

Doug Brown (5):
pwm: pxa: Remove pxa_pwm_enable/disable
pwm: pxa: Set duty cycle to 0 when disabling PWM
pwm: pxa: Remove clk enable/disable from pxa_pwm_config
pwm: pxa: Wait for final PWM period to finish
pwm: pxa: Enable for MMP platform

 drivers/pwm/Kconfig   |  2 +-
 drivers/pwm/pwm-pxa.c | 64 ++++++++++++++++++++++---------------------
 2 files changed, 34 insertions(+), 32 deletions(-)
Signature · 1 line
2.34.1
author
#1 lore raw

PATCH v2 1/5 pwm: pxa: Remove pxa_pwm_enable/disable

These functions are only acting as wrappers for clk_prepare_enable and clk_disable_unprepare now, so remove them to simplify the driver.

---
 drivers/pwm/pwm-pxa.c | 19 +++----------------
 1 file changed, 3 insertions(+), 16 deletions(-)
drivers/pwm/pwm-pxa.c +3 -16
index 0bcaa58c6a91..0ac052652c62 100644
@@ -101,23 +101,10 @@ static int pxa_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm,
 	return 0;
 }
 
-static int pxa_pwm_enable(struct pwm_chip *chip, struct pwm_device *pwm)
-{
-	struct pxa_pwm_chip *pc = to_pxa_pwm_chip(chip);
-
-	return clk_prepare_enable(pc->clk);
-}
-
-static void pxa_pwm_disable(struct pwm_chip *chip, struct pwm_device *pwm)
-{
-	struct pxa_pwm_chip *pc = to_pxa_pwm_chip(chip);
-
-	clk_disable_unprepare(pc->clk);
-}
-
 static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
 			 const struct pwm_state *state)
 {
+	struct pxa_pwm_chip *pc = to_pxa_pwm_chip(chip);
 	int err;
 
 	if (state->polarity != PWM_POLARITY_NORMAL)
@@ -125,7 +112,7 @@ static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
 
 	if (!state->enabled) {
 		if (pwm->state.enabled)
-			pxa_pwm_disable(chip, pwm);
+			clk_disable_unprepare(pc->clk);
 
 		return 0;
 	}
@@ -135,7 +122,7 @@ static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
 		return err;
 
 	if (!pwm->state.enabled)
-		return pxa_pwm_enable(chip, pwm);
+		return clk_prepare_enable(pc->clk);
 
 	return 0;
 }
Signature · 1 line
2.34.1
Reviewed-by on v2 1/5
#2 lore raw

Re: [PATCH v2 1/5] pwm: pxa: Remove pxa_pwm_enable/disable

Quoted 5 lines · Doug Brown

These functions are only acting as wrappers for clk_prepare_enable and clk_disable_unprepare now, so remove them to simplify the driver.

Thanks
Uwe

Signature · 2 lines
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |
author
#3 lore raw

PATCH v2 2/5 pwm: pxa: Set duty cycle to 0 when disabling PWM

In reply to Doug Brown

When disabling PWM, the duty cycle needs to be set to 0. This prevents the previous duty cycle from showing up momentarily when the clock is re-enabled next time, and also prevents the output pin from being stuck high when the clock is disabled.

Because the clock has to be running in order to configure the duty cycle, unconditionally enable it early in pxa_pwm_apply and account for the correct enable count at the end.

---
 drivers/pwm/pwm-pxa.c | 25 ++++++++++++++++---------
 1 file changed, 16 insertions(+), 9 deletions(-)
drivers/pwm/pwm-pxa.c +16 -9
index 0ac052652c62..9ee9b41d62b8 100644
@@ -105,24 +105,31 @@ static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
 			 const struct pwm_state *state)
 {
 	struct pxa_pwm_chip *pc = to_pxa_pwm_chip(chip);
+	u64 duty_cycle;
 	int err;
 
 	if (state->polarity != PWM_POLARITY_NORMAL)
 		return -EINVAL;
 
-	if (!state->enabled) {
-		if (pwm->state.enabled)
-			clk_disable_unprepare(pc->clk);
+	err = clk_prepare_enable(pc->clk);
+	if (err)
+		return err;
 
-		return 0;
-	}
+	duty_cycle = state->enabled ? state->duty_cycle : 0;
 
-	err = pxa_pwm_config(chip, pwm, state->duty_cycle, state->period);
-	if (err)
+	err = pxa_pwm_config(chip, pwm, duty_cycle, state->period);
+	if (err) {
+		clk_disable_unprepare(pc->clk);
 		return err;
+	}
+
+	if (state->enabled && !pwm->state.enabled)
+		return 0;
+
+	clk_disable_unprepare(pc->clk);
 
-	if (!pwm->state.enabled)
-		return clk_prepare_enable(pc->clk);
+	if (!state->enabled && pwm->state.enabled)
+		clk_disable_unprepare(pc->clk);
 
 	return 0;
 }
Signature · 1 line
2.34.1
Reviewed-by on v2 2/5
#4 lore raw

Re: [PATCH v2 2/5] pwm: pxa: Set duty cycle to 0 when disabling PWM

Quoted 47 lines · Doug Brown

When disabling PWM, the duty cycle needs to be set to 0. This prevents the previous duty cycle from showing up momentarily when the clock is re-enabled next time, and also prevents the output pin from being stuck high when the clock is disabled.

Because the clock has to be running in order to configure the duty cycle, unconditionally enable it early in pxa_pwm_apply and account for the correct enable count at the end.

---
 drivers/pwm/pwm-pxa.c | 25 ++++++++++++++++---------
 1 file changed, 16 insertions(+), 9 deletions(-)
drivers/pwm/pwm-pxa.c +9 -7
index 0ac052652c62..9ee9b41d62b8 100644
@@ -105,24 +105,31 @@ static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
 			 const struct pwm_state *state)
 {
 	struct pxa_pwm_chip *pc = to_pxa_pwm_chip(chip);
+	u64 duty_cycle;
 	int err;
 
 	if (state->polarity != PWM_POLARITY_NORMAL)
 		return -EINVAL;
 
-	if (!state->enabled) {
-		if (pwm->state.enabled)
-			clk_disable_unprepare(pc->clk);
+	err = clk_prepare_enable(pc->clk);
+	if (err)
+		return err;
 
-		return 0;
-	}
+	duty_cycle = state->enabled ? state->duty_cycle : 0;
 
-	err = pxa_pwm_config(chip, pwm, state->duty_cycle, state->period);
-	if (err)
+	err = pxa_pwm_config(chip, pwm, duty_cycle, state->period);
+	if (err) {
+		clk_disable_unprepare(pc->clk);
 		return err;
+	}

drivers/pwm/pwm-pxa.c static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm, · line 132

Quoted 10 lines
drivers/pwm/pwm-pxa.c +7 -2
+
+	if (state->enabled && !pwm->state.enabled)
+		return 0;
+
+	clk_disable_unprepare(pc->clk);
 
-	if (!pwm->state.enabled)
-		return clk_prepare_enable(pc->clk);
+	if (!state->enabled && pwm->state.enabled)
+		clk_disable_unprepare(pc->clk);

Best regards
Uwe

Signature · 2 lines
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |
author
#5 lore raw

Re: [PATCH v2 2/5] pwm: pxa: Set duty cycle to 0 when disabling PWM

Hi Uwe,

Quoted 7 lines · Uwe Kleine-König
Quoted 4 lines · Doug Brown

When disabling PWM, the duty cycle needs to be set to 0. This prevents the previous duty cycle from showing up momentarily when the clock is re-enabled next time, and also prevents the output pin from being stuck high when the clock is disabled.

It appears I messed up when writing the commit message for this patch, because I did some more testing today with raw register writes and the output pin definitely doesn't get stuck high when I disable the clock -- no matter where we are in the PWM cycle. Either way, it still makes sense to set the duty cycle to 0 first. Just wanted you to know that I'm not changing the patch at all -- just the commit message -- on v3, so I'm not carrying over your Reviewed-by tag on v3 of this patch. Sorry about that!

Doug

author
#6 lore raw

PATCH v2 3/5 pwm: pxa: Remove clk enable/disable from pxa_pwm_config

In reply to Doug Brown

Now that pxa_pwm_apply always enables the clock first, there is no need for pxa_pwm_config to do any clock enabling/disabling.

---
 drivers/pwm/pwm-pxa.c | 9 ---------
 1 file changed, 9 deletions(-)
drivers/pwm/pwm-pxa.c +0 -9
index 9ee9b41d62b8..cf4d22c91929 100644
@@ -64,7 +64,6 @@ static int pxa_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm,
 	unsigned long long c;
 	unsigned long period_cycles, prescale, pv, dc;
 	unsigned long offset;
-	int rc;
 
 	offset = pwm->hwpwm ? 0x10 : 0;
 
@@ -86,18 +85,10 @@ static int pxa_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm,
 	else
 		dc = mul_u64_u64_div_u64(pv + 1, duty_ns, period_ns);
 
-	/* NOTE: the clock to PWM has to be enabled first
-	 * before writing to the registers
-	 */
-	rc = clk_prepare_enable(pc->clk);
-	if (rc < 0)
-		return rc;
-
 	writel(prescale, pc->mmio_base + offset + PWMCR);
 	writel(dc, pc->mmio_base + offset + PWMDCR);
 	writel(pv, pc->mmio_base + offset + PWMPCR);
 
-	clk_disable_unprepare(pc->clk);
 	return 0;
 }
 
Signature · 1 line
2.34.1
Reviewed-by on v2 3/5
#7 lore raw

Re: [PATCH v2 3/5] pwm: pxa: Remove clk enable/disable from pxa_pwm_config

Quoted 28 lines · Doug Brown

Now that pxa_pwm_apply always enables the clock first, there is no need for pxa_pwm_config to do any clock enabling/disabling.

---
 drivers/pwm/pwm-pxa.c | 9 ---------
 1 file changed, 9 deletions(-)
drivers/pwm/pwm-pxa.c +0 -5
index 9ee9b41d62b8..cf4d22c91929 100644
@@ -64,7 +64,6 @@ static int pxa_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm,
 	unsigned long long c;
 	unsigned long period_cycles, prescale, pv, dc;
 	unsigned long offset;
-	int rc;
 
 	offset = pwm->hwpwm ? 0x10 : 0;
 
@@ -86,18 +85,10 @@ static int pxa_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm,
 	else
 		dc = mul_u64_u64_div_u64(pv + 1, duty_ns, period_ns);
 
-	/* NOTE: the clock to PWM has to be enabled first
-	 * before writing to the registers
-	 */
-	rc = clk_prepare_enable(pc->clk);

drivers/pwm/pwm-pxa.c static int pxa_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm, · line 93

Quoted 10 lines
drivers/pwm/pwm-pxa.c +0 -4
-	if (rc < 0)
-		return rc;
-
 	writel(prescale, pc->mmio_base + offset + PWMCR);
 	writel(dc, pc->mmio_base + offset + PWMDCR);
 	writel(pv, pc->mmio_base + offset + PWMPCR);
 
-	clk_disable_unprepare(pc->clk);
 	return 0;
 }

Best regards
Uwe

Signature · 2 lines
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |
author
#8 lore raw

PATCH v2 4/5 pwm: pxa: Wait for final PWM period to finish

In reply to Doug Brown

If the clock is turned on too quickly after being turned off, it won't actually turn back on. Work around this problem by waiting for the final period to complete when disabling the PWM. The delay logic is borrowed from the pwm-sun4i driver.

To avoid unnecessary delays, skip the whole config process if the PWM is already disabled and staying disabled.

---
 drivers/pwm/pwm-pxa.c | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
drivers/pwm/pwm-pxa.c +17 -0
index cf4d22c91929..edcef67f7ffe 100644
@@ -17,6 +17,7 @@
 #include <linux/io.h>
 #include <linux/pwm.h>
 #include <linux/of_device.h>
+#include <linux/delay.h>
 
 #include <asm/div64.h>
 
@@ -96,12 +97,16 @@ static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
 			 const struct pwm_state *state)
 {
 	struct pxa_pwm_chip *pc = to_pxa_pwm_chip(chip);
+	unsigned int delay_us;
 	u64 duty_cycle;
 	int err;
 
 	if (state->polarity != PWM_POLARITY_NORMAL)
 		return -EINVAL;
 
+	if (!state->enabled && !pwm->state.enabled)
+		return 0;
+
 	err = clk_prepare_enable(pc->clk);
 	if (err)
 		return err;
@@ -122,6 +127,18 @@ static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
 	if (!state->enabled && pwm->state.enabled)
 		clk_disable_unprepare(pc->clk);
 
+	if (state->enabled)
+		return 0;
+
+	/* Wait for the final PWM period to finish. This prevents it from
+	 * being re-enabled too quickly (which can fail silently).
+	 */
+	delay_us = DIV_ROUND_UP_ULL(state->period, NSEC_PER_USEC);
+	if ((delay_us / 500) > MAX_UDELAY_MS)
+		msleep(delay_us / 1000 + 1);
+	else
+		usleep_range(delay_us, delay_us * 2);
+
 	return 0;
 }
 
Signature · 1 line
2.34.1
#9 lore raw

Re: [PATCH v2 4/5] pwm: pxa: Wait for final PWM period to finish

Quoted 7 lines · Doug Brown

If the clock is turned on too quickly after being turned off, it won't actually turn back on. Work around this problem by waiting for the final period to complete when disabling the PWM. The delay logic is borrowed from the pwm-sun4i driver.

To avoid unnecessary delays, skip the whole config process if the PWM is already disabled and staying disabled.

I wonder if there is some documentation available about this issue. This feels like a workaround without knowledge about the details and so might break at the next opportunity.

drivers/pwm/pwm-pxa.c static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm, · line 135

Quoted 11 lines

[...]

drivers/pwm/pwm-pxa.c +6 -0
@@ -122,6 +127,18 @@ static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
 	if (!state->enabled && pwm->state.enabled)
 		clk_disable_unprepare(pc->clk);
 
+	if (state->enabled)
+		return 0;
+
+	/* Wait for the final PWM period to finish. This prevents it from
+	 * being re-enabled too quickly (which can fail silently).
+	 */

Please stick to the usual comment style. i.e. put the /* on a line for itself.

Best regards
Uwe

Signature · 2 lines
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |
author
#10 lore raw

Re: [PATCH v2 4/5] pwm: pxa: Wait for final PWM period to finish

Hi Uwe,

Quoted 6 lines · Uwe Kleine-König
Quoted 5 lines · Doug Brown

If the clock is turned on too quickly after being turned off, it won't actually turn back on. Work around this problem by waiting for the final period to complete when disabling the PWM. The delay logic is borrowed from the pwm-sun4i driver.

Quoted 6 lines
Quoted 2 lines

To avoid unnecessary delays, skip the whole config process if the PWM is already disabled and staying disabled.

I wonder if there is some documentation available about this issue. This feels like a workaround without knowledge about the details and so might break at the next opportunity.

Thanks for reviewing! Yes, it does feel like a crazy workaround. I'm not super proud of it. The best documentation I've been able to look at is the PXA168 software manual [1]. Page 502 of the PDF talks about a "graceful shutdown" where turning off the clock enable bit doesn't immediately stop the clock, and instead it waits for the current PWM period to complete first. This driver is currently configuring it for graceful shutdown mode, because the PWMCR_SD bit is not set (page 1257).

I've experimentally determined that if you try to turn the clock back on when a graceful shutdown is still scheduled, it doesn't cancel the graceful shutdown, so the clock ends up off afterward, even though the common clock framework thinks it's still on. The hacky delay in this commit works around that problem. This almost seems like a problem that should be solved on the common clock framework side instead, but it doesn't know what the PWM frequency is so it wouldn't know how long to delay.

Do all the other similar drivers in the kernel do a graceful shutdown like this when they are turned off? If not, a simpler solution would be to start turning on the PWMCR_SD bit instead, so the clock stops immediately (potentially resulting in the final duty cycle being short). I tested that change in place of this commit and it seems to work pretty well, although I can still cause it to fail if I turn my PWM backlight off and back on quickly without a "sleep 0.000001" in between. It feels to me like there are some weird interdependencies between the clock enable bits and the actual PWM controller block, at least in the PXA168, likely due to "graceful shutdown" mode's existence.

What do you think? Turning on the PWMCR_SD bit would be very simple, but it doesn't fully fix the issue in my testing. I'd still be okay with it though, because the only failure case I can reproduce is a minor edge case (plus, I don't love the delay solution).

Quoted 6 lines
Quoted 6 lines

[...]

drivers/pwm/pwm-pxa.c +0 -0
@@ -122,6 +127,18 @@ static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
  	if (!state->enabled && pwm->state.enabled)
  		clk_disable_unprepare(pc->clk);
 
Quoted 9 lines

drivers/pwm/pwm-pxa.c static int pxa_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm, · line 135

Quoted 6 lines
drivers/pwm/pwm-pxa.c +6 -0
+	if (state->enabled)
+		return 0;
+
+	/* Wait for the final PWM period to finish. This prevents it from
+	 * being re-enabled too quickly (which can fail silently).
+	 */

Please stick to the usual comment style. i.e. put the /* on a line for itself.

My bad, thanks for pointing this out. If this comment still exists in the next version of the patch, I'll fix it.

Thanks,
Doug

[1] https://web.archive.org/web/20160428154454/http://www.marvell.com/application-processors/armada-100/assets/armada_16x_software_manual.pdf

#11 lore raw

Re: [PATCH v2 4/5] pwm: pxa: Wait for final PWM period to finish

Hello Doug,

Quoted 31 lines · Doug Brown
Quoted 6 lines · Uwe Kleine-König
Quoted 5 lines · Doug Brown

If the clock is turned on too quickly after being turned off, it won't actually turn back on. Work around this problem by waiting for the final period to complete when disabling the PWM. The delay logic is borrowed from the pwm-sun4i driver.

Quoted 6 lines
Quoted 2 lines

To avoid unnecessary delays, skip the whole config process if the PWM is already disabled and staying disabled.

I wonder if there is some documentation available about this issue. This feels like a workaround without knowledge about the details and so might break at the next opportunity.

Thanks for reviewing! Yes, it does feel like a crazy workaround. I'm not super proud of it. The best documentation I've been able to look at is the PXA168 software manual [1]. Page 502 of the PDF talks about a "graceful shutdown" where turning off the clock enable bit doesn't immediately stop the clock, and instead it waits for the current PWM period to complete first. This driver is currently configuring it for graceful shutdown mode, because the PWMCR_SD bit is not set (page 1257).

I've experimentally determined that if you try to turn the clock back on when a graceful shutdown is still scheduled, it doesn't cancel the graceful shutdown, so the clock ends up off afterward, even though the common clock framework thinks it's still on. The hacky delay in this commit works around that problem. This almost seems like a problem that should be solved on the common clock framework side instead, but it doesn't know what the PWM frequency is so it wouldn't know how long to delay.

Quoted 4 lines

Do all the other similar drivers in the kernel do a graceful shutdown like this when they are turned off? If not, a simpler solution would be to start turning on the PWMCR_SD bit instead, so the clock stops immediately (potentially resulting in the final duty cycle being short).

There are supported hardwares that (only) support immediate shutdown, so consumers cannot rely on a graceful stop anyhow. So I'd say using PWMCR_SD=1 is fine. The documentation suggests that in this case "PWM_OUTx stops after at most one PSCLK_PWM" which might explain that the problem can still be triggered. (i.e. if you reenable before the next PSCLK_PWM cycle.)

BTW, the driver lacks information about how the hardware behaves on disable. The most common cases are

- emits the inactive output
- freezes where it just happens to be (assuming PWMCR_SD=1)

Would you mind testing that and adding a patch to your series? (Look at e.g. drivers/pwm/pwm-sl28cpld.c for the desired format to ease grepping.)

Quoted 11 lines

I tested that change in place of this commit and it seems to work pretty well, although I can still cause it to fail if I turn my PWM backlight off and back on quickly without a "sleep 0.000001" in between. It feels to me like there are some weird interdependencies between the clock enable bits and the actual PWM controller block, at least in the PXA168, likely due to "graceful shutdown" mode's existence.

What do you think? Turning on the PWMCR_SD bit would be very simple, but it doesn't fully fix the issue in my testing. I'd still be okay with it though, because the only failure case I can reproduce is a minor edge case (plus, I don't love the delay solution).

+1 for no love for the delay solution.

Best regards
Uwe

Signature · 2 lines
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |
author
#12 lore raw

Re: [PATCH v2 4/5] pwm: pxa: Wait for final PWM period to finish

Hi Uwe,

Quoted 6 lines · Uwe Kleine-König

There are supported hardwares that (only) support immediate shutdown, so consumers cannot rely on a graceful stop anyhow. So I'd say using PWMCR_SD=1 is fine. The documentation suggests that in this case "PWM_OUTx stops after at most one PSCLK_PWM" which might explain that the problem can still be triggered. (i.e. if you reenable before the next PSCLK_PWM cycle.)

Thanks for taking a look! Your point about PSCLK_PWM does make sense and likely explains how I'm still able to trigger the problem.

Quoted 9 lines

BTW, the driver lacks information about how the hardware behaves on disable. The most common cases are

- emits the inactive output
- freezes where it just happens to be (assuming PWMCR_SD=1)

Would you mind testing that and adding a patch to your series? (Look at e.g. drivers/pwm/pwm-sl28cpld.c for the desired format to ease grepping.)

Will do. I assume you're referring to the "Limitations" section at the top of a lot of the drivers. It appears that this hardware always emits the inactive input when the clock disables -- almost immediately if PWMCR_SD=1, or at the end of the current duty cycle if PWMCR_SD=0.

Doug

author
#13 lore raw

PATCH v2 5/5 pwm: pxa: Enable for MMP platform

In reply to Doug Brown

The PXA168, which is part of the MMP platform, also uses this driver.

---
 drivers/pwm/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pwm/Kconfig +1 -1
index 60d13a949bc5..d0d4caebf12f 100644
@@ -434,7 +434,7 @@ config PWM_PCA9685
 
 config PWM_PXA
 	tristate "PXA PWM support"
-	depends on ARCH_PXA || COMPILE_TEST
+	depends on ARCH_PXA || ARCH_MMP || COMPILE_TEST
 	depends on HAS_IOMEM
 	help
 	  Generic PWM framework driver for PXA.
Signature · 1 line
2.34.1
Acked-by on v2 5/5
#14 lore raw

Re: [PATCH v2 5/5] pwm: pxa: Enable for MMP platform

Quoted 12 lines · Doug Brown

The PXA168, which is part of the MMP platform, also uses this driver.

---
 drivers/pwm/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pwm/Kconfig +0 -0
index 60d13a949bc5..d0d4caebf12f 100644

drivers/pwm/Kconfig config PWM_PCA9685 · line 437

Quoted 5 lines
drivers/pwm/Kconfig +1 -1
@@ -434,7 +434,7 @@ config PWM_PCA9685
 
 config PWM_PXA
 	tristate "PXA PWM support"
-	depends on ARCH_PXA || COMPILE_TEST
+	depends on ARCH_PXA || ARCH_MMP || COMPILE_TEST

Best regards
Uwe

Signature · 2 lines
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |