From: Antonio Borneo <antonio.borneo@foss.st.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-gpio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Antonio Borneo <antonio.borneo@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Fabien Dessenne <fabien.dessenne@foss.st.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: [RESEND PATCH v2 0/5] STM32 pinctrl: Add mux function RSVD
Date: Tue, 10 Jun 2025 17:23:04 +0200 [thread overview]
Message-ID: <20250610152309.299438-1-antonio.borneo@foss.st.com> (raw)
This v2 is a subset of the v1, split-out to simplify the review.
This subset:
- introduces the pinctrl mux function RSVD,
- adds two use cases requiring RSVD,
- minor re-format of the dt-bindings.
Changes v1 -> v2 subset:
- rebased on v6.16-rc1,
- added use cases of the new mux function RSVD,
- added Reviewed-by: on 2/5 (former 04/14 in v1),
- added commit to re-format the dt-bindings,
- Link to v1: https://lore.kernel.org/lkml/20241022155658.1647350-1-antonio.borneo@foss.st.com/
Antonio Borneo (3):
ARM: dts: stm32: Add pinmux for CM4 leds pins
ARM: dts: stm32: Add leds for CM4 on stm32mp15xx-ed1 and
stm32mp15xx-dkx
dt-bindings: pinctrl: stm32: Add missing blank lines
Fabien Dessenne (2):
pinctrl: stm32: Handle RSVD pin configuration
dt-bindings: pinctrl: stm32: Add RSVD mux function
.../bindings/pinctrl/st,stm32-pinctrl.yaml | 25 +++++++++++++++++++
arch/arm/boot/dts/st/stm32mp15-pinctrl.dtsi | 14 +++++++++++
arch/arm/boot/dts/st/stm32mp157c-ed1.dts | 2 ++
arch/arm/boot/dts/st/stm32mp15xx-dkx.dtsi | 2 ++
drivers/pinctrl/stm32/pinctrl-stm32.c | 9 +++++++
drivers/pinctrl/stm32/pinctrl-stm32.h | 3 ++-
include/dt-bindings/pinctrl/stm32-pinfunc.h | 1 +
7 files changed, 55 insertions(+), 1 deletion(-)
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
--
2.34.1
next reply other threads:[~2025-06-10 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 15:23 Antonio Borneo [this message]
2025-06-10 15:23 ` [RESEND PATCH v2 1/5] pinctrl: stm32: Handle RSVD pin configuration Antonio Borneo
2025-06-10 15:23 ` [RESEND PATCH v2 2/5] dt-bindings: pinctrl: stm32: Add RSVD mux function Antonio Borneo
2025-06-10 15:23 ` [RESEND PATCH v2 3/5] ARM: dts: stm32: Add pinmux for CM4 leds pins Antonio Borneo
2025-06-10 15:23 ` [RESEND PATCH v2 4/5] ARM: dts: stm32: Add leds for CM4 on stm32mp15xx-ed1 and stm32mp15xx-dkx Antonio Borneo
2025-06-10 15:23 ` [RESEND PATCH v2 5/5] dt-bindings: pinctrl: stm32: Add missing blank lines Antonio Borneo
2025-06-25 19:52 ` Rob Herring (Arm)
2025-07-03 22:04 ` Linus Walleij
2025-06-18 9:26 ` [RESEND PATCH v2 0/5] STM32 pinctrl: Add mux function RSVD Linus Walleij
2025-09-03 13:56 ` Alexandre TORGUE
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=20250610152309.299438-1-antonio.borneo@foss.st.com \
--to=antonio.borneo@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabien.dessenne@foss.st.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).