public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Sangyun Kim <sangyun.kim@snu.ac.kr>
Subject: [GIT PULL] pwm: Changes for 7.1-rc1
Date: Thu, 23 Apr 2026 09:32:44 +0200	[thread overview]
Message-ID: <aenGN5inmayPlloE@monoceros> (raw)

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

Hello Linus,

the following changes since commit aa8f35172ab66c57d4355a8c4e28d05b44c938e3:

  pwm: th1520: fix `CLIPPY=1` warning (2026-03-29 09:37:13 +0200)

(= pwm/for-7.1-rc1) are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git tags/pwm/fixes-7.1-rc1

for you to fetch changes up to 68637b68afcc3cb4d56aca14a3a1d1b47b879369:

  pwm: atmel-tcb: Cache clock rates and mark chip as atomic (2026-04-22 07:24:33 +0200)

While writing the tag text I thought about splitting the "mark chip as
atomic" part of Sangyun's fix into a separate change for the next merge
window. But it's still early in the development cycle and I don't expect
problems here, so I kept the change as it was tested. Also the patch is
a bit unelegant as it results in keeping a clock on during the lifetime
of the driver; I expect this to be addressed in one of the next
development cycles. Compared to the sleep-in-atomic this is a very minor
annoyance and I don't want to delay the fix because of that.

The pwm-stm fix is in next for a week already, the atmel-tcb fix is only
contained since next-20260422 with no problem reports.

Thanks for pulling this into your tree at your convenience,
Uwe

----------------------------------------------------------------
pwm: Two driver fixes

After having added some more code to libpwm checking the pwm rounding
rules for the userspace interface I spotted an issue in the pwm-stm32
driver where in some cases involving inverted polarity the wrong
hardware settings for the duty offset are chosen. I think it has little
practical effect because the duty offset is in most cases an artificial
property of the output waveform. Still it's relevant to get this fixed
because this driver serves as a reference implementation for the still
young waveform API.

The second fix addresses a sleep-in-atomic issue in the pwm-atmel-tcb
driver.

----------------------------------------------------------------
Sangyun Kim (1):
      pwm: atmel-tcb: Cache clock rates and mark chip as atomic

Uwe Kleine-König (1):
      pwm: stm32: Fix rounding issue for requests with inverted polarity

 drivers/pwm/pwm-atmel-tcb.c | 38 ++++++++++++++++++++++++++++++++++----
 drivers/pwm/pwm-stm32.c     | 22 ++++++++++++----------
 2 files changed, 46 insertions(+), 14 deletions(-)

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

             reply	other threads:[~2026-04-23  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  7:32 Uwe Kleine-König [this message]
2026-04-23 16:18 ` [GIT PULL] pwm: Changes for 7.1-rc1 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-04-13  8:22 Uwe Kleine-König
2026-04-15 22:01 ` pr-tracker-bot

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=aenGN5inmayPlloE@monoceros \
    --to=ukleinek@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=sangyun.kim@snu.ac.kr \
    --cc=torvalds@linux-foundation.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