From: Thierry Reding <thierry.reding@gmail.com>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Maarten ter Huurne <maarten@treewalker.org>
Subject: Re: [PATCH 1/4] pwm: jz4740: Make disable operation compatible with TCU2 mode
Date: Wed, 28 Mar 2018 00:25:00 +0200 [thread overview]
Message-ID: <20180327222459.GF28163@mithrandir> (raw)
In-Reply-To: <20180106165843.3461-1-paul@crapouillou.net>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
On Sat, Jan 06, 2018 at 05:58:40PM +0100, Paul Cercueil wrote:
> From: Maarten ter Huurne <maarten@treewalker.org>
>
> On the JZ4750 and later SoCs, channel 1 and 2 operate in a different
> way (TCU2 mode) as the other channels. If a TCU2 mode counter is
> stopped before its PWM functionality is disabled, the output is not
> guaranteed to return to the initial level.
>
> Signed-off-by: Maarten ter Huurne <maarten@treewalker.org>
> ---
> drivers/pwm/pwm-jz4740.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Applied patches 1-4, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-03-27 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 16:58 [PATCH 1/4] pwm: jz4740: Make disable operation compatible with TCU2 mode Paul Cercueil
[not found] ` <20180106165843.3461-1-paul-icTtO2rgO2OTuSrc4Mpeew@public.gmane.org>
2018-01-06 16:58 ` [PATCH 2/4] pwm: pwm-jz4740: Implement set_polarity Paul Cercueil
2018-03-17 20:46 ` Paul Cercueil
2018-01-06 16:58 ` [PATCH 3/4] pwm: jz4740: Add support for devicetree Paul Cercueil
[not found] ` <20180106165843.3461-3-paul-icTtO2rgO2OTuSrc4Mpeew@public.gmane.org>
2018-01-19 19:44 ` Rob Herring
2018-01-06 16:58 ` [PATCH 4/4] pwm: jz4740: Enable for all Ingenic SoCs Paul Cercueil
2018-03-27 22:25 ` 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=20180327222459.GF28163@mithrandir \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=maarten@treewalker.org \
--cc=mark.rutland@arm.com \
--cc=paul@crapouillou.net \
--cc=robh+dt@kernel.org \
/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).