All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Clemens Gruber <clemens.gruber@pqgruber.com>, linux-pwm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	"Sven Van Asbroeck" <TheSven73@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH 1/4] pwm: core: Support new usage_power setting in PWM state
Date: Fri,  4 Jun 2021 11:44:25 +0200	[thread overview]
Message-ID: <162279984978.1091692.17557126430283544901.b4-ty@gmail.com> (raw)
In-Reply-To: <20210507131845.37605-1-clemens.gruber@pqgruber.com>

On Fri, 7 May 2021 15:18:42 +0200, Clemens Gruber wrote:
> If usage_power is set, the PWM driver is only required to maintain
> the power output but has more freedom regarding signal form.
> 
> If supported, the signal can be optimized, for example to
> improve EMI by phase shifting individual channels.

Applied, thanks!

[1/4] pwm: core: Support new usage_power setting in PWM state
      commit: 9e40ee18a1dc1623a5368d6232aaed52fd29dada
[2/4] pwm: pca9685: Support new usage_power setting in PWM state
      commit: ae16db1fd3a1b8d1713ba6af5cf27be32918d2b8
[3/4] pwm: pca9685: Restrict period change for enabled PWMs
      commit: 6d6e7050276d40b5de97aa950d5d71057f2e2a25
[4/4] pwm: pca9685: Add error messages for failed regmap calls
      commit: 79dd354fe1769ebec695dacfee007eafb1538d0c

Best regards,
-- 
Thierry Reding <thierry.reding@gmail.com>

      parent reply	other threads:[~2021-06-04  9:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 13:18 [PATCH 1/4] pwm: core: Support new usage_power setting in PWM state Clemens Gruber
2021-05-07 13:18 ` [PATCH 2/4] pwm: pca9685: " Clemens Gruber
2021-05-07 13:18 ` [PATCH 3/4] pwm: pca9685: Restrict period change for enabled PWMs Clemens Gruber
2021-05-07 13:18 ` [PATCH 4/4] pwm: pca9685: Add error messages for failed regmap calls Clemens Gruber
2021-05-07 15:03 ` [PATCH 1/4] pwm: core: Support new usage_power setting in PWM state Uwe Kleine-König
2021-05-07 15:47   ` Clemens Gruber
2021-05-07 23:18     ` Uwe Kleine-König
2021-05-31 16:12       ` Clemens Gruber
2021-06-04  9:49         ` Thierry Reding
2021-06-07  6:08           ` Uwe Kleine-König
2021-06-07 14:40             ` Thierry Reding
2021-06-07 18:51               ` Uwe Kleine-König
2021-06-09 20:41                 ` Uwe Kleine-König
2021-06-10 13:11                   ` Thierry Reding
2021-06-21  6:47                     ` PWM-Patches for next merge window [Was: Re: [PATCH 1/4] pwm: core: Support new usage_power setting in PWM] state Uwe Kleine-König
2021-06-25  9:55                       ` PWM-Patches for next merge window Uwe Kleine-König
2021-06-04  9:44 ` 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=162279984978.1091692.17557126430283544901.b4-ty@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=TheSven73@gmail.com \
    --cc=clemens.gruber@pqgruber.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.