From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: "Daniel Mack" <daniel@zonque.org>,
"Haojian Zhuang" <haojian.zhuang@gmail.com>,
"Robert Jarzmik" <robert.jarzmik@free.fr>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Duje Mihanović" <duje.mihanovic@skole.hr>
Cc: "Hervé Codina" <herve.codina@bootlin.com>,
linux-pwm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: [PATCH v2 0/3] pwm: pxa: Use #pwm-cells = <3>
Date: Thu, 6 Feb 2025 13:06:24 +0100 [thread overview]
Message-ID: <cover.1738842938.git.u.kleine-koenig@baylibre.com> (raw)
Hello,
this series' goal is to soften the special device-tree binding of
marvel,pxa-pwm devices. This is the only binding that doesn't pass the
line index as first parameter.
Here the #pwm-cells value is bumped from 1 to 3, keeping compatibility
with the old binding.
The motivation for this was that Hervé sent a patch introducing pwm
nexus nodes which don't work nicely with the marvel,pxa-pwm
particularities.
Changes since (implicit) v1, available at
https://lore.kernel.org/linux-pwm/cover.1738777221.git.u.kleine-koenig@baylibre.com:
- Use #pwm-cells = <3> also in the binding example (*sigh*), pointed
out by Rob
- Add review, ack and test tags by Hervé Codina, Conor Dooley, Duje
Mihanović and Daniel Mack. Thanks!
I intend to take the first patch via my pwm tree. Assuming the pxa and
device tree maintainers and bots are happy now: Dear pxa maintainers,
please tell if I should take the whole series via pwm, or if you want to
take patches #2 and #3. If the latter: Do you want to delay application
or should I provide an immutable branch for patch #1?
Best regards
Uwe
Uwe Kleine-König (3):
pwm: Add upgrade path to #pwm-cells = <3> for users of
of_pwm_single_xlate()
dt-bindings: pwm: marvell,pxa-pwm: Update to use #pwm-cells = <3>
ARM: dts: pxa: Use #pwm-cells = <3> for marvell,pxa-pwm devices
.../devicetree/bindings/pwm/marvell,pxa-pwm.yaml | 5 ++---
arch/arm/boot/dts/intel/pxa/pxa25x.dtsi | 4 ++--
arch/arm/boot/dts/intel/pxa/pxa27x.dtsi | 8 ++++----
.../dts/intel/pxa/pxa300-raumfeld-controller.dts | 2 +-
arch/arm/boot/dts/intel/pxa/pxa3xx.dtsi | 8 ++++----
drivers/pwm/core.c | 16 ++++++++++++++++
6 files changed, 29 insertions(+), 14 deletions(-)
base-commit: 2014c95afecee3e76ca4a56956a936e23283f05b
--
2.47.1
next reply other threads:[~2025-02-06 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 12:06 Uwe Kleine-König [this message]
2025-02-06 12:06 ` [PATCH v2 1/3] pwm: Add upgrade path to #pwm-cells = <3> for users of of_pwm_single_xlate() Uwe Kleine-König
2025-02-06 12:06 ` [PATCH v2 2/3] dt-bindings: pwm: marvell,pxa-pwm: Update to use #pwm-cells = <3> Uwe Kleine-König
2025-02-11 16:16 ` Rob Herring
2025-02-06 12:06 ` [PATCH v2 3/3] ARM: dts: pxa: Use #pwm-cells = <3> for marvell,pxa-pwm devices Uwe Kleine-König
2025-02-10 18:31 ` [PATCH v2 0/3] pwm: pxa: Use #pwm-cells = <3> Uwe Kleine-König
2025-02-11 16:12 ` Rob Herring
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.1738842938.git.u.kleine-koenig@baylibre.com \
--to=u.kleine-koenig@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=duje.mihanovic@skole.hr \
--cc=haojian.zhuang@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--cc=robh@kernel.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