From: Amelie Delaunay <amelie.delaunay@foss.st.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Amelie Delaunay <amelie.delaunay@foss.st.com>,
Himanshu Bhavani <himanshu.bhavani@siliconsignals.io>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v2 6/7] dt-bindings: arm: stm32: add STM32MP157F-DK2 board compatible
Date: Tue, 3 Jun 2025 11:02:12 +0200 [thread overview]
Message-ID: <20250603-stm32mp157f-dk2-v2-6-5be0854a9299@foss.st.com> (raw)
In-Reply-To: <20250603-stm32mp157f-dk2-v2-0-5be0854a9299@foss.st.com>
From: Himanshu Bhavani <himanshu.bhavani@siliconsignals.io>
Add the "st,stm32mp157f-dk2" compatible string to the STM32 SoC
bindings. The MP157F is functionally similar to the MP157C.
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Signed-off-by: Himanshu Bhavani <himanshu.bhavani@siliconsignals.io>
Signed-off-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
---
Documentation/devicetree/bindings/arm/stm32/stm32.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/stm32/stm32.yaml b/Documentation/devicetree/bindings/arm/stm32/stm32.yaml
index 408532504a24d5e570c738b16de30dcf8deead6a..ad144c02eb7edf4fc2191ab0af244342dcaa59d5 100644
--- a/Documentation/devicetree/bindings/arm/stm32/stm32.yaml
+++ b/Documentation/devicetree/bindings/arm/stm32/stm32.yaml
@@ -121,6 +121,7 @@ properties:
- st,stm32mp157a-dk1-scmi
- st,stm32mp157c-dk2
- st,stm32mp157c-dk2-scmi
+ - st,stm32mp157f-dk2
- const: st,stm32mp157
- items:
--
2.25.1
next prev parent reply other threads:[~2025-06-03 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 9:02 [PATCH v2 0/7] Introduce STM32MP157F-DK2 board Amelie Delaunay
2025-06-03 9:02 ` [PATCH v2 1/7] ARM: dts: stm32: fullfill diversity with OPP for STM32M15xF SOCs Amelie Delaunay
2025-06-03 9:02 ` [PATCH v2 2/7] ARM: dts: stm32: use 'typec' generic name for stusb1600 on stm32mp15xx-dkx Amelie Delaunay
2025-06-03 9:02 ` [PATCH v2 3/7] dt-bindings: regulator: Add STM32MP15 SCMI regulator identifiers Amelie Delaunay
2025-06-25 18:39 ` Rob Herring (Arm)
2025-06-03 9:02 ` [PATCH v2 4/7] ARM: dts: stm32: use internal regulators bindings for MP15 scmi variants Amelie Delaunay
2025-06-03 9:02 ` [PATCH v2 5/7] ARM: dts: stm32: optee async notif interrupt " Amelie Delaunay
2025-06-03 9:02 ` Amelie Delaunay [this message]
2025-06-03 9:02 ` [PATCH v2 7/7] ARM: dts: stm32: add stm32mp157f-dk2 board support Amelie Delaunay
2025-07-04 9:29 ` [PATCH v2 0/7] Introduce STM32MP157F-DK2 board 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=20250603-stm32mp157f-dk2-v2-6-5be0854a9299@foss.st.com \
--to=amelie.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=himanshu.bhavani@siliconsignals.io \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).