From: Paul Cercueil <paul@crapouillou.net>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
od@zcrc.me, linux-pwm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [PATCH v2 3/6] pwm: jz4740: Apply configuration atomically
Date: Mon, 29 Jul 2019 17:19:23 -0400 [thread overview]
Message-ID: <1564435163.6633.4@crapouillou.net> (raw)
In-Reply-To: <20190724064745.7ghecdpg3gmxsiim@pengutronix.de>
Hi Uwe,
Le mer. 24 juil. 2019 à 2:47, Uwe =?iso-8859-1?q?Kleine-K=F6nig?=
<u.kleine-koenig@pengutronix.de> a écrit :
> Hello Paul,
>
> On Tue, Jul 23, 2019 at 04:46:40PM -0400, Paul Cercueil wrote:
>> Le lun. 22 juil. 2019 à 15:34, Uwe =?iso-8859-1?q?Kleine-K=F6nig?=
>> <u.kleine-koenig@pengutronix.de> a écrit :
>> > On Fri, Jun 07, 2019 at 05:44:07PM +0200, Paul Cercueil wrote:
>> > > - is_enabled = jz4740_timer_is_enabled(pwm->hwpwm);
>> > > - if (is_enabled)
>> > > - jz4740_pwm_disable(chip, pwm);
>> > > + jz4740_pwm_disable(chip, pwm);
>> >
>> > I assume this stops the PWM. Does this complete the currently
>> running
>> > period? How does the PWM behave then? (Does it still drive the
>> output?
>> > If so, on which level?)
>>
>> Some PWM channels work in one mode "TCU1" and others work in
>> "TCU2". The
>> mode in which channels work depends on the version of the SoC.
>>
>> When stopped, the pins of TCU1 channels will be driven to the
>> inactive
>> level (which depends on the polarity). It is unknown whether or not
>> the
>> currently running period is completed. We set a bit to configure for
>> "abrupt shutdown", so I expect that it's not, but somebody would
>> need
>> to hook up a logic analyzer to see what's the exact behaviour with
>> and without that bit.
>
> This might be done even without a logic analyzer. Just do something
> like:
>
> pwm_apply_state(pwm, { .enabled = 1, .period = 5s })
> pwm_apply_state(pwm, { .enabled = 1, .period = 5s, .duty = 5s })
>
> and if that takes less then 5s the period is not completed.
>
> And note that "abrupt shutdown" is a bug.
I remember you asked that already in an older patchset.
The result of this test is that the period is never completed,
independently of the "abrupt shutdown" bit.
Cheers,
-Paul
>> TCU2 channels on the other hand will stop in the middle of a period,
>> leaving the pin hanging at whatever level it was before the stop.
>> That's the rationale behind the trick in commit 6580fd173070 ("pwm:
>> jz4740: Force TCU2 channels to return to their init level").
>
> Strange, but ok.
>
> Best regards
> Uwe
>
> --
> Pengutronix e.K. | Uwe Kleine-König
> |
> Industrial Linux Solutions |
> http://www.pengutronix.de/ |
next prev parent reply other threads:[~2019-07-29 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 15:44 [PATCH v2 0/6] PWM JZ4740 fixes and cleanups Paul Cercueil
2019-06-07 15:44 ` [PATCH v2 1/6] dt-bindings: Remove unused compatible strings Paul Cercueil
2019-07-09 2:04 ` Rob Herring
2019-07-09 3:18 ` Paul Cercueil
2019-07-09 15:46 ` Rob Herring
2019-08-08 8:28 ` Uwe Kleine-König
2019-08-12 23:39 ` Rob Herring
2019-06-07 15:44 ` [PATCH v2 2/6] pwm: jz4740: Remove unused devicetree " Paul Cercueil
2019-08-08 8:24 ` Uwe Kleine-König
2019-06-07 15:44 ` [PATCH v2 3/6] pwm: jz4740: Apply configuration atomically Paul Cercueil
2019-07-22 19:34 ` Uwe Kleine-König
2019-07-23 20:46 ` Paul Cercueil
2019-07-24 6:47 ` Uwe Kleine-König
2019-07-29 21:19 ` Paul Cercueil [this message]
2019-06-07 15:44 ` [PATCH v2 4/6] pwm: jz4740: Drop dependency on MACH_INGENIC Paul Cercueil
2019-06-07 15:44 ` [PATCH v2 5/6] pwm: jz4740: Force TCU2 channels to return to their init level Paul Cercueil
2019-06-07 15:44 ` [PATCH v2 6/6] pwm: jz4740: Use __init_or_module and __exit for .probe and .remove Paul Cercueil
2019-06-08 10:31 ` Paul Cercueil
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=1564435163.6633.4@crapouillou.net \
--to=paul@crapouillou.net \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=od@zcrc.me \
--cc=robh+dt@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