From: Thierry Reding <thierry.reding@gmail.com>
To: Paul Kocialkowski <contact@paulk.fr>
Cc: linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] pwm: twl: Reliably disable TWL6030 PWMs
Date: Mon, 5 Sep 2016 07:14:46 +0200 [thread overview]
Message-ID: <20160905051446.GA3532@ulmo.ba.sec> (raw)
In-Reply-To: <1459277745-16878-1-git-send-email-contact@paulk.fr>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Tue, Mar 29, 2016 at 08:55:45PM +0200, Paul Kocialkowski wrote:
> The current TWL6030 code for the TWL PWM driver does not reliably disable the
> PWM output, as tested with LEDs. The previous commit to that driver introduced
> that regression.
>
> However, it does make sense to disable the PWM clock after resetting the PWM,
> but for some obscure reason, doing it all at once simply doesn't work.
>
> The TWL6030 datasheet mentions that PWMs have to be disabled in two distinct
> steps. However, clearing the clock enable bit in a second step (after issuing a
> reset first) does not work.
>
> The only approach that works is the one that was in place before the previous
> commit to the driver. It consists in enabling the PWM clock after issuing a
> reset. This is what TI kernel trees and production code seem to be using.
>
> However, adding an extra step to disable the PWM clock seems to work reliably,
> despite looking quite odd.
>
> Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
> ---
> drivers/pwm/pwm-twl.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2016-09-05 5:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 18:55 [PATCH] pwm: twl: Reliably disable TWL6030 PWMs Paul Kocialkowski
2016-07-11 10:55 ` Thierry Reding
2016-07-12 13:18 ` Peter Ujfalusi
2016-09-05 5:14 ` Thierry Reding [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=20160905051446.GA3532@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=contact@paulk.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).