Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: "Uwe Kleine-König" <ukleinek@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Fabio Estevam" <festevam@gmail.com>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"Clark Wang" <xiaoning.wang@nxp.com>, "Jun Li" <jun.li@nxp.com>,
	pratikmanvar09@gmail.com
Subject: Re: [PATCH 3/3] pwm: imx27: workaround of the pwm output bug when decrease the duty cycle
Date: Fri, 12 Jul 2024 10:40:55 -0400	[thread overview]
Message-ID: <ZpFAd+Mp2JFnaPet@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <78119193-98b7-446f-82d6-37884a5b03ad@gmx.net>

On Fri, Jul 12, 2024 at 08:26:17AM +0200, Stefan Wahren wrote:
> Hi Frank,
> 
> Am 11.07.24 um 23:08 schrieb Frank Li:
> > From: Clark Wang <xiaoning.wang@nxp.com>
> > 
> > When the SAR FIFO is empty, the write value is directly applied to SAR even
> > though the current period is not over. If the new SAR value is less than
> > the old one and the counter is greater than the new SAR value, the current
> > period will not flip the level. This result in a pulse with a 100% duty
> > cycle.
> > 
> > Write the old SAR value before updating the new duty cycle to SAR. This
> > avoids writing the new value into an empty FIFO.
> > 
> > This only resolves the issue when the PWM period is longer than 2us
> > (or <500KHz) because write register is not quick enough when PWM period is
> > very short.
> > 
> > Reviewed-by: Jun Li <jun.li@nxp.com>
> > Signed-off-by: Clark Wang <xiaoning.wang@nxp.com>
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> the same patch has been submitted from other people in the past and they
> received many review comments [1], [2].
> 
> Can you please explain which version of the patch this is and does it
> address any review comments?

Thank, I am not realize someone already submitted before. I fixed some by
common senses. Let me double check to make sure to fix all. 

Frank

> 
> Best regards
> 
> [1] -
> https://lore.kernel.org/linux-pwm/20211220073130.1429723-1-xiaoning.wang@nxp.com/
> [2] -
> https://lore.kernel.org/linux-pwm/20231229063013.1786-1-pratikmanvar09@gmail.com/

      reply	other threads:[~2024-07-12 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 21:08 [PATCH 0/3] pwm: imx: add 32k clock for 8qm/qxp and workaround a chip issue Frank Li
2024-07-11 21:08 ` [PATCH 1/3] dt-bindings: pwm: imx: Add compatible string imx8qxp-mipi-pwm Frank Li
2024-07-12 14:09   ` Rob Herring
2024-07-11 21:08 ` [PATCH 2/3] pwm: imx27: Add 32k clock for pwm in i.MX8QXP MIPI subsystem Frank Li
2024-07-12 14:06   ` Rob Herring
2024-07-11 21:08 ` [PATCH 3/3] pwm: imx27: workaround of the pwm output bug when decrease the duty cycle Frank Li
2024-07-12  6:26   ` Stefan Wahren
2024-07-12 14:40     ` Frank Li [this message]

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=ZpFAd+Mp2JFnaPet@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --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=wahrenst@gmx.net \
    --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