From: "Michal Vokáč" <michal.vokac@ysoft.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Enric Balletbo i Serra" <enric.balletbo@collabora.com>,
linux-pwm@vger.kernel.org, "Adam Ford" <aford173@gmail.com>
Subject: Re: [PATCH 4/4] pwm: imx27: Unconditionally write state to hardware
Date: Mon, 21 Oct 2019 15:49:36 +0200 [thread overview]
Message-ID: <5e129df5-1110-29ea-35ce-4c2274b135fe@ysoft.com> (raw)
In-Reply-To: <20191021105739.1357629-4-thierry.reding@gmail.com>
+Adam
On 21. 10. 19 12:57, Thierry Reding wrote:
> The i.MX driver currently uses a shortcut and doesn't write all of the
> state through to the hardware when the PWM is disabled. This causes an
> inconsistent state to be read back by consumers with the result of them
> malfunctioning.
>
> Fix this by always writing the full state through to the hardware
> registers so that the correct state can always be read back.
Gave it another shot and got expected results.
Tested-by: Michal Vokáč <michal.vokac@ysoft.com>
> Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
> ---
> drivers/pwm/pwm-imx27.c | 120 ++++++++++++++++++++--------------------
> 1 file changed, 59 insertions(+), 61 deletions(-)
>
> diff --git a/drivers/pwm/pwm-imx27.c b/drivers/pwm/pwm-imx27.c
> index 4113d5cd4c62..59d8b1289808 100644
> --- a/drivers/pwm/pwm-imx27.c
> +++ b/drivers/pwm/pwm-imx27.c
> @@ -230,70 +230,68 @@ static int pwm_imx27_apply(struct pwm_chip *chip, struct pwm_device *pwm,
>
> pwm_get_state(pwm, &cstate);
>
> - if (state->enabled) {
> - c = clk_get_rate(imx->clk_per);
> - c *= state->period;
> -
> - do_div(c, 1000000000);
> - period_cycles = c;
> -
> - prescale = period_cycles / 0x10000 + 1;
> -
> - period_cycles /= prescale;
> - c = (unsigned long long)period_cycles * state->duty_cycle;
> - do_div(c, state->period);
> - duty_cycles = c;
> -
> - /*
> - * according to imx pwm RM, the real period value should be
> - * PERIOD value in PWMPR plus 2.
> - */
> - if (period_cycles > 2)
> - period_cycles -= 2;
> - else
> - period_cycles = 0;
> -
> - /*
> - * Wait for a free FIFO slot if the PWM is already enabled, and
> - * flush the FIFO if the PWM was disabled and is about to be
> - * enabled.
> - */
> - if (cstate.enabled) {
> - pwm_imx27_wait_fifo_slot(chip, pwm);
> - } else {
> - ret = pwm_imx27_clk_prepare_enable(chip);
> - if (ret)
> - return ret;
> -
> - pwm_imx27_sw_reset(chip);
> - }
> -
> - writel(duty_cycles, imx->mmio_base + MX3_PWMSAR);
> - writel(period_cycles, imx->mmio_base + MX3_PWMPR);
> -
> - /*
> - * Store the duty cycle for future reference in cases where
> - * the MX3_PWMSAR register can't be read (i.e. when the PWM
> - * is disabled).
> - */
> - imx->duty_cycle = duty_cycles;
> -
> - cr = MX3_PWMCR_PRESCALER_SET(prescale) |
> - MX3_PWMCR_STOPEN | MX3_PWMCR_DOZEN | MX3_PWMCR_WAITEN |
> - FIELD_PREP(MX3_PWMCR_CLKSRC, MX3_PWMCR_CLKSRC_IPG_HIGH) |
> - MX3_PWMCR_DBGEN | MX3_PWMCR_EN;
> -
> - if (state->polarity == PWM_POLARITY_INVERSED)
> - cr |= FIELD_PREP(MX3_PWMCR_POUTC,
> - MX3_PWMCR_POUTC_INVERTED);
> -
> - writel(cr, imx->mmio_base + MX3_PWMCR);
> - } else if (cstate.enabled) {
> - writel(0, imx->mmio_base + MX3_PWMCR);
> + c = clk_get_rate(imx->clk_per);
> + c *= state->period;
>
> - pwm_imx27_clk_disable_unprepare(chip);
> + do_div(c, 1000000000);
> + period_cycles = c;
> +
> + prescale = period_cycles / 0x10000 + 1;
> +
> + period_cycles /= prescale;
> + c = (unsigned long long)period_cycles * state->duty_cycle;
> + do_div(c, state->period);
> + duty_cycles = c;
> +
> + /*
> + * according to imx pwm RM, the real period value should be PERIOD
> + * value in PWMPR plus 2.
> + */
> + if (period_cycles > 2)
> + period_cycles -= 2;
> + else
> + period_cycles = 0;
> +
> + /*
> + * Wait for a free FIFO slot if the PWM is already enabled, and flush
> + * the FIFO if the PWM was disabled and is about to be enabled.
> + */
> + if (cstate.enabled) {
> + pwm_imx27_wait_fifo_slot(chip, pwm);
> + } else {
> + ret = pwm_imx27_clk_prepare_enable(chip);
> + if (ret)
> + return ret;
> +
> + pwm_imx27_sw_reset(chip);
> }
>
> + writel(duty_cycles, imx->mmio_base + MX3_PWMSAR);
> + writel(period_cycles, imx->mmio_base + MX3_PWMPR);
> +
> + /*
> + * Store the duty cycle for future reference in cases where the
> + * MX3_PWMSAR register can't be read (i.e. when the PWM is disabled).
> + */
> + imx->duty_cycle = duty_cycles;
> +
> + cr = MX3_PWMCR_PRESCALER_SET(prescale) |
> + MX3_PWMCR_STOPEN | MX3_PWMCR_DOZEN | MX3_PWMCR_WAITEN |
> + FIELD_PREP(MX3_PWMCR_CLKSRC, MX3_PWMCR_CLKSRC_IPG_HIGH) |
> + MX3_PWMCR_DBGEN;
> +
> + if (state->polarity == PWM_POLARITY_INVERSED)
> + cr |= FIELD_PREP(MX3_PWMCR_POUTC,
> + MX3_PWMCR_POUTC_INVERTED);
> +
> + if (state->enabled)
> + cr |= MX3_PWMCR_EN;
> +
> + writel(cr, imx->mmio_base + MX3_PWMCR);
> +
> + if (!state->enabled && cstate.enabled)
> + pwm_imx27_clk_disable_unprepare(chip);
> +
> return 0;
> }
>
>
next prev parent reply other threads:[~2019-10-21 13:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 10:57 [PATCH 1/4] pwm: Read initial hardware state at request time Thierry Reding
2019-10-21 10:57 ` [PATCH 2/4] pwm: cros-ec: Cache duty cycle value Thierry Reding
2019-10-21 13:48 ` Enric Balletbo i Serra
2019-12-05 7:12 ` Uwe Kleine-König
2019-10-21 10:57 ` [PATCH 3/4] pwm: imx27: Cache duty cycle register value Thierry Reding
2019-10-21 13:46 ` Michal Vokáč
2019-10-21 14:21 ` Adam Ford
2019-10-21 10:57 ` [PATCH 4/4] pwm: imx27: Unconditionally write state to hardware Thierry Reding
2019-10-21 13:49 ` Michal Vokáč [this message]
2019-10-21 14:21 ` Adam Ford
2019-10-21 11:11 ` [PATCH 1/4] pwm: Read initial hardware state at request time Uwe Kleine-König
2019-10-21 14:27 ` Thierry Reding
2019-10-21 13:34 ` Michal Vokáč
2019-10-21 13:46 ` Enric Balletbo i Serra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5e129df5-1110-29ea-35ce-4c2274b135fe@ysoft.com \
--to=michal.vokac@ysoft.com \
--cc=aford173@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox