On Thu, Feb 27, 2025 at 04:40:04PM +0100, Christophe Parant wrote:
Modifications following new PHYTEC stm32mp15x SoM and board device tree
naming.
Why?
It's an ABI, so you are stuck with the names. It's just a unique
identifier, so it's really not important what the string is.
quoted hunk ↗ jump to hunk
Signed-off-by: Christophe Parant <redacted>
---
Documentation/devicetree/bindings/arm/stm32/stm32.yaml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/stm32/stm32.yaml b/Documentation/devicetree/bindings/arm/stm32/stm32.yaml
index b6c56d4ce6b9..11b3f59ac550 100644
--- a/Documentation/devicetree/bindings/arm/stm32/stm32.yaml
+++ b/Documentation/devicetree/bindings/arm/stm32/stm32.yaml
@@ -169,10 +169,11 @@ properties:
- const: seeed,stm32mp157c-odyssey-som
- const: st,stm32mp157
- - description: Phytec STM32MP1 SoM based Boards
+ - description: Phytec STM32MP15x SoM based Boards
items:
- - const: phytec,phycore-stm32mp1-3
- - const: phytec,phycore-stm32mp157c-som
+ - enum:
+ - phytec,stm32mp157c-phyboard-sargas-rdk
+ - const: phytec,stm32mp157c-phycore-som
- const: st,stm32mp157
- description: ST STM32MP257 based Boards--
2.34.1