From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: linux-pwm@vger.kernel.org
Cc: Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
Vladimir Zapolskiy <vz@mleia.com>,
Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
linux-riscv@lists.infradead.org, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
linux-sunxi@lists.linux.dev
Subject: [PATCH 0/8] pwm: Drop local locking in several drivers
Date: Tue, 24 Jun 2025 20:15:36 +0200 [thread overview]
Message-ID: <cover.1750788649.git.u.kleine-koenig@baylibre.com> (raw)
Hello,
some time ago the pwm core implemented additional locking to protect
lowlevel driver callbacks against driver removal. A side effect is that
.apply() and .get_state() are serialized. This allows to drop some
locking that is now superfluous due to the core's locking.
I identified a few drivers that are affected; these are cleaned up
accordingly here.
Best regards
Uwe
Uwe Kleine-König (8):
pwm: atmel: Drop driver local locking
pwm: clps711x: Drop driver local locking
pwm: fsl-ftm: Drop driver local locking
pwm: lpc18xx-sct: Drop driver local locking
pwm: microchip-core: Drop driver local locking
pwm: sti: Drop driver local locking
pwm: sun4i: Drop driver local locking
pwm: twl-led: Drop driver local locking
drivers/pwm/pwm-atmel.c | 12 --------
drivers/pwm/pwm-clps711x.c | 8 ------
drivers/pwm/pwm-fsl-ftm.c | 28 +++++-------------
drivers/pwm/pwm-lpc18xx-sct.c | 14 ---------
drivers/pwm/pwm-microchip-core.c | 17 +----------
drivers/pwm/pwm-sti.c | 23 ++++-----------
drivers/pwm/pwm-sun4i.c | 10 -------
drivers/pwm/pwm-twl-led.c | 49 +++++---------------------------
8 files changed, 21 insertions(+), 140 deletions(-)
base-commit: f817b6dd2b62d921a6cdc0a3ac599cd1851f343c
--
2.49.0
next reply other threads:[~2025-06-24 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 18:15 Uwe Kleine-König [this message]
2025-06-24 18:15 ` [PATCH 1/8] pwm: atmel: Drop driver local locking Uwe Kleine-König
2025-06-24 18:15 ` [PATCH 2/8] pwm: clps711x: " Uwe Kleine-König
2025-06-24 18:15 ` [PATCH 3/8] pwm: fsl-ftm: " Uwe Kleine-König
2025-06-24 18:15 ` [PATCH 4/8] pwm: lpc18xx-sct: " Uwe Kleine-König
2025-06-24 18:22 ` Vladimir Zapolskiy
2025-06-24 18:15 ` [PATCH 5/8] pwm: microchip-core: " Uwe Kleine-König
2025-06-24 18:15 ` [PATCH 6/8] pwm: sti: " Uwe Kleine-König
2025-06-24 18:15 ` [PATCH 7/8] pwm: sun4i: " Uwe Kleine-König
2025-06-24 18:15 ` [PATCH 8/8] pwm: twl-led: " Uwe Kleine-König
2025-07-01 7:57 ` [PATCH 0/8] pwm: Drop local locking in several drivers Uwe Kleine-König
2025-08-10 21:12 ` patchwork-bot+linux-riscv
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.1750788649.git.u.kleine-koenig@baylibre.com \
--to=u.kleine-koenig@baylibre.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=nicolas.ferre@microchip.com \
--cc=samuel@sholland.org \
--cc=vz@mleia.com \
--cc=wens@csie.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).