pwm: berlin: Ensure configuring period and duty_cycle isn't wrongly skipped

As the last call to berlin_pwm_apply() might have exited early if
state->enabled was false, the values for period and duty_cycle stored in
pwm->state might not have been written to hardware and it must be
ensured that they are configured before enabling the PWM.

Fixes: 30dffb42fc ("pwm: berlin: Implement .apply() callback")
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
This commit is contained in:
Uwe Kleine-König 2021-07-01 10:27:54 +02:00 committed by Thierry Reding
parent 25f70b8f3d
commit 7d6d4aaf28
1 changed files with 3 additions and 6 deletions

View File

@ -190,12 +190,9 @@ static int berlin_pwm_apply(struct pwm_chip *chip, struct pwm_device *pwm,
return 0; return 0;
} }
if (state->period != pwm->state.period ||
state->duty_cycle != pwm->state.duty_cycle) {
err = berlin_pwm_config(chip, pwm, state->duty_cycle, state->period); err = berlin_pwm_config(chip, pwm, state->duty_cycle, state->period);
if (err) if (err)
return err; return err;
}
if (!enabled) if (!enabled)
return berlin_pwm_enable(chip, pwm); return berlin_pwm_enable(chip, pwm);