aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/pwm/core.c
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@baylibre.com>2025-07-08 19:18:01 +0200
committerUwe Kleine-König <ukleinek@kernel.org>2025-09-15 11:39:44 +0200
commitb871d093f1caebeb39b12136a33e7529b8fdea50 (patch)
tree509e9d8ec8ddaa3ea8f1602005ed640495b281e5 /drivers/pwm/core.c
parentpwm: Disable PWM_DEBUG check for disabled states (diff)
downloadlinux-b871d093f1caebeb39b12136a33e7529b8fdea50.tar.gz
linux-b871d093f1caebeb39b12136a33e7529b8fdea50.zip
pwm: Check actual period and duty_cycle for ignored polarity test
When a lowlevel driver configures the wrong period that might (historically) be ok if the emitted signal has a 100% relative duty_cycle as that just corresponds to rounding down the duty_cycle to 0 which is an allowed thing to do for a lowlevel driver. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com> Link: https://lore.kernel.org/r/bc511c0250ea2f6390e4209ab1ea9c08a3c18612.1751994988.git.u.kleine-koenig@baylibre.com Signed-off-by: Uwe Kleine-König <ukleinek@kernel.org>
Diffstat (limited to 'drivers/pwm/core.c')
-rw-r--r--drivers/pwm/core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
index d5d2dfbe4ade..2570ad6a7f59 100644
--- a/drivers/pwm/core.c
+++ b/drivers/pwm/core.c
@@ -536,7 +536,7 @@ static void pwm_apply_debug(struct pwm_device *pwm,
}
if (s2.polarity != state->polarity &&
- state->duty_cycle < state->period)
+ s2.duty_cycle < s2.period)
dev_warn(pwmchip_parent(chip), ".apply ignored .polarity\n");
if (last->polarity == state->polarity &&