devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Clemens Gruber <clemens.gruber@pqgruber.com>
Cc: linux-pwm@vger.kernel.org,
	Thierry Reding <thierry.reding@gmail.com>,
	Sven Van Asbroeck <TheSven73@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 1/8] pwm: pca9685: Switch to atomic API
Date: Sat, 17 Apr 2021 21:51:50 +0200	[thread overview]
Message-ID: <20210417195150.5fdcpxfbasp4y264@pengutronix.de> (raw)
In-Reply-To: <20210415121455.39536-1-clemens.gruber@pqgruber.com>

[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]

On Thu, Apr 15, 2021 at 02:14:48PM +0200, Clemens Gruber wrote:
> The switch to the atomic API goes hand in hand with a few fixes to
> previously experienced issues:
> - The duty cycle is no longer lost after disable/enable (previously the
>   OFF registers were cleared in disable and the user was required to
>   call config to restore the duty cycle settings)
> - If one sets a period resulting in the same prescale register value,
>   the sleep and write to the register is now skipped
> - Previously, only the full ON bit was toggled in GPIO mode (and full
>   OFF cleared if set to high), which could result in both full OFF and
>   full ON not being set and on=0, off=0, which is not allowed according
>   to the datasheet
> - The OFF registers were reset to 0 in probe, which could lead to the
>   forbidden on=0, off=0. Fixed by resetting to POR default (full OFF)
> 
> Signed-off-by: Clemens Gruber <clemens.gruber@pqgruber.com>

(I sent my ack to v8 before, but indeed this was the version I intended
to ack)

Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>


-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2021-04-17 19:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 12:14 [PATCH v9 1/8] pwm: pca9685: Switch to atomic API Clemens Gruber
2021-04-15 12:14 ` [PATCH v9 2/8] pwm: pca9685: Support hardware readout Clemens Gruber
2021-04-17 19:57   ` Uwe Kleine-König
2021-04-15 12:14 ` [PATCH v9 3/8] pwm: pca9685: Improve runtime PM behavior Clemens Gruber
2021-04-15 12:14 ` [PATCH v9 4/8] dt-bindings: pwm: Support new PWM_USAGE_POWER flag Clemens Gruber
2021-04-15 12:14 ` [PATCH v9 5/8] pwm: core: " Clemens Gruber
2021-04-15 12:14 ` [PATCH v9 6/8] pwm: pca9685: " Clemens Gruber
2021-04-15 12:14 ` [PATCH v9 7/8] pwm: pca9685: Restrict period change for enabled PWMs Clemens Gruber
2021-04-17 19:58   ` Uwe Kleine-König
2021-04-15 12:14 ` [PATCH v9 8/8] pwm: pca9685: Add error messages for failed regmap calls Clemens Gruber
2021-04-17 19:59   ` Uwe Kleine-König
2021-04-17 19:51 ` Uwe Kleine-König [this message]
2021-04-22 11:39   ` [PATCH v9 1/8] pwm: pca9685: Switch to atomic API Clemens Gruber
2021-04-23 16:46     ` Thierry Reding

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=20210417195150.5fdcpxfbasp4y264@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=TheSven73@gmail.com \
    --cc=clemens.gruber@pqgruber.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=thierry.reding@gmail.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).