From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
John Crispin <john@phrozen.org>
Cc: linux-pwm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH v3 0/2] pwm: mediatek: Fix duty and period setting
Date: Mon, 28 Jul 2025 18:00:16 +0200 [thread overview]
Message-ID: <cover.1753717973.git.u.kleine-koenig@baylibre.com> (raw)
Hello,
here comes v3 of the (formerly patch, now) series to fix duty_cycle and
period setting for the mediatek PWM driver.
v2: https://lore.kernel.org/linux-pwm/20250724210041.2513590-2-u.kleine-koenig@baylibre.com
Changes since v2:
- Split changed clock handling into a separate patch (suggested by
AngeloGioacchino)
- Drop
if (err < 0)
return err;
just before an unconditional
return err;
.
I didn't add a R-b for AngeloGioacchino yet, as it felt wrong to do that
for a patch that he didn't see before. So assuming you're happy, please
provide the tag again for this v3.
v1: https://lore.kernel.org/linux-pwm/20250710163705.2095418-2-u.kleine-koenig@baylibre.com
Best regards
Uwe
Uwe Kleine-König (2):
pwm: mediatek: Handle hardware enable and clock enable separately
pwm: mediatek: Fix duty and period setting
drivers/pwm/pwm-mediatek.c | 71 ++++++++++++++++++++------------------
1 file changed, 37 insertions(+), 34 deletions(-)
base-commit: 68b9272ca7ac948b71aba482ef8244dee8032f46
--
2.50.0
next reply other threads:[~2025-07-28 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 16:00 Uwe Kleine-König [this message]
2025-07-28 16:00 ` [PATCH v3 1/2] pwm: mediatek: Handle hardware enable and clock enable separately Uwe Kleine-König
2025-07-28 16:00 ` [PATCH v3 2/2] pwm: mediatek: Fix duty and period setting Uwe Kleine-König
2025-07-29 10:07 ` [PATCH v3 0/2] " AngeloGioacchino Del Regno
2025-07-29 16:11 ` Uwe Kleine-König
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=cover.1753717973.git.u.kleine-koenig@baylibre.com \
--to=u.kleine-koenig@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=john@phrozen.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=matthias.bgg@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).