From: Marek Vasut <marex@denx.de>
To: Frank Li <Frank.Li@nxp.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
festevam@gmail.com, francesco@dolcini.it, imx@lists.linux.dev,
jun.li@nxp.com, kernel@pengutronix.de, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
p.zabel@pengutronix.de, pratikmanvar09@gmail.com,
robh@kernel.org, s.hauer@pengutronix.de, shawnguo@kernel.org,
ukleinek@kernel.org, xiaoning.wang@nxp.com
Subject: Re: [PATCH v4 1/1] pwm: imx27: workaround of the pwm output bug when decrease the duty cycle
Date: Mon, 9 Sep 2024 22:19:59 +0200 [thread overview]
Message-ID: <cceb5ece-3aba-45d1-a5e3-3419245f345b@denx.de> (raw)
In-Reply-To: <20240909193855.2394830-1-Frank.Li@nxp.com>
On 9/9/24 9:38 PM, Frank Li wrote:
[...]
> + * Use __raw_writel() to minimize the interval between two writes to
> + * the SAR register to increase the fastest pwm frequency supported.
> + *
> + * When the PWM period is longer than 2us(or <500KHz), this workaround
> + * can solve this problem. No software workaround is available If PMW
PWM , typo
> + * period is shorter than IO write.
> + */
> + c = clkrate * 1500;
> + do_div(c, NSEC_PER_SEC);
> +
> + local_irq_save(flags);
> + val = FIELD_GET(MX3_PWMSR_FIFOAV, readl_relaxed(imx->mmio_base + MX3_PWMSR));
> + if (duty_cycles < imx->duty_cycle && val < MX3_PWMSR_FIFOAV_2WORDS) {
> + val = readl_relaxed(imx->mmio_base + MX3_PWMCNR);
> + if ((val + c >= duty_cycles && val < imx->duty_cycle) ||
> + /*
> + * If counter is close to period, controller may roll over
> + * when next IO write.
> + */
> + val + c >= period_cycles)
> + writel_relaxed(imx->duty_cycle, reg_sar);
Maybe use imx->mmio_base + MX3_PWMSAR instead of reg_sar here, to be
consistent with imx->mmio_base + MX3_PWMSR above ?
> + }
> + writel_relaxed(duty_cycles, reg_sar);
Same here
> + local_irq_restore(flags);
> +
> writel(period_cycles, imx->mmio_base + MX3_PWMPR);
[...]
Looks good otherwise, thanks !
next prev parent reply other threads:[~2024-09-09 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 19:38 Frank Li
2024-09-09 20:19 ` Marek Vasut [this message]
2024-09-10 7:53 ` Uwe Kleine-König
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=cceb5ece-3aba-45d1-a5e3-3419245f345b@denx.de \
--to=marex@denx.de \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco@dolcini.it \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pratikmanvar09@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=ukleinek@kernel.org \
--cc=xiaoning.wang@nxp.com \
/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
all inboxes | Powered by JetHome®