From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Himanshu Bhavani <himanshu.bhavani@siliconsignals.io>,
"amelie.delaunay@foss.st.com" <amelie.delaunay@foss.st.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Marc Kleine-Budde" <mkl@pengutronix.de>,
"Leonard Göhrs" <l.goehrs@pengutronix.de>,
"Marek Vasut" <marex@denx.de>, "David Jander" <david@protonic.nl>,
"Roan van Dijk" <roan@protonic.nl>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/2] ARM: dts: stm32: add support of stm32mp157f-dk2 board
Date: Tue, 27 May 2025 17:18:46 +0200 [thread overview]
Message-ID: <6b9ad1a0-4f7d-498e-ac0d-49ac41a2532b@foss.st.com> (raw)
In-Reply-To: <PN0P287MB201936022C3BF4389C7BF8B79A64A@PN0P287MB2019.INDP287.PROD.OUTLOOK.COM>
Hi Himanshu
On 5/27/25 08:36, Himanshu Bhavani wrote:
> Hi Alexandre,
>
>> Hi Himanshu
>>
>> On 5/24/25 12:03, Himanshu Bhavani wrote:
>>> STM32MP157F is similar to the STM32MP157C, so reuse the existing
>>> stm32mp157c-dk2.dts as a base for the STM32MP157F-DK2 board.
>>>
>>> Datasheet: https://www.st.com/resource/en/data_brief/stm32mp157f-dk2.pdf
>>> Signed-off-by: Himanshu Bhavani <himanshu.bhavani@siliconsignals.io>
>>> ---
>>> arch/arm/boot/dts/st/Makefile | 3 ++-
>>> arch/arm/boot/dts/st/stm32mp157f-dk2.dts | 15 +++++++++++++++
>>> 2 files changed, 17 insertions(+), 1 deletion(-)
>>> create mode 100644 arch/arm/boot/dts/st/stm32mp157f-dk2.dts
>>>
>>> diff --git a/arch/arm/boot/dts/st/Makefile b/arch/arm/boot/dts/st/Makefile
>>> index 60d55516f723..38179638e5eb 100644
>>> --- a/arch/arm/boot/dts/st/Makefile
>>> +++ b/arch/arm/boot/dts/st/Makefile
>>> @@ -70,7 +70,8 @@ dtb-$(CONFIG_ARCH_STM32) += \
>>> stm32mp157c-lxa-tac-gen2.dtb \
>>> stm32mp157c-odyssey.dtb \
>>> stm32mp157c-osd32mp1-red.dtb \
>>> - stm32mp157c-phycore-stm32mp1-3.dtb
>>> + stm32mp157c-phycore-stm32mp1-3.dtb \
>>> + stm32mp157f-dk2.dtb
>>> dtb-$(CONFIG_ARCH_U8500) += \
>>> ste-snowball.dtb \
>>> ste-hrefprev60-stuib.dtb \
>>> diff --git a/arch/arm/boot/dts/st/stm32mp157f-dk2.dts b/arch/arm/boot/dts/st/stm32mp157f-dk2.dts
>>> new file mode 100644
>>> index 000000000000..ab406b2c44c1
>>> --- /dev/null
>>> +++ b/arch/arm/boot/dts/st/stm32mp157f-dk2.dts
>>> @@ -0,0 +1,15 @@
>>> +// SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
>>> +/*
>>> + * Copyright (C) 2025 Silicon Signals Pvt. Ltd.
>>> + *
>>> + * Author: Himanshu Bhavani <himanshu.bhavani@siliconsignals.io>
>>> + */
>>> +
>>> +/dts-v1/;
>>> +
>>> +#include "stm32mp157c-dk2.dts"
>>
>> In this case what is the aim of this series if you just use stm32mp157C
>> devicetree ?
>
> This patch series aims to add support for the STM32MP157F board device
> tree. The primary motivation is to ensure that users working with the
> STM32MP157F variant have a reference DTS available. Currently, no such
> device tree exists, even though the STM32MP157F and STM32MP157C are
> largely similar.
>
>> ST people (mainly Amélie) are preparing a full support of
>> STM32MP157F-DK2 leveraging the F variant compare to the C variant.
>> Series will be sent this week.
>
> If ST is working on a dedicated DTS for the F variant, it's likely they are starting
> from the C variant as a base, this is exactly the approach I’ve taken here. At this
> stage, I have not included an SCMI-based version of the board since it hasn't
> been tested yet.
Please have a look on:
https://lore.kernel.org/all/20250527-stm32mp157f-dk2-v1-0-8aef885a4928@foss.st.com/
The idea is to have the same approach than for STM32MP13 and STM32MP25
relying on SCMI and preparing the add of F variant feature: DVFS/cpufreq.
regards
alex
> Please let me know if you have any further suggestions.
>
>
> Best Regards,
> Himanshu
>
>> Regards
>> Alex
>>
>>> +
>>> +/ {
>>> + model = "STMicroelectronics STM32MP157F-DK2 Discovery Board";
>>> + compatible = "st,stm32mp157f-dk2", "st,stm32mp157";
>>> +};
next prev parent reply other threads:[~2025-05-27 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-24 10:03 [PATCH v1 0/2] add support of stm32mp157f-dk2 board Himanshu Bhavani
2025-05-24 10:03 ` [PATCH v1 1/2] ARM: dts: stm32: " Himanshu Bhavani
2025-05-26 7:27 ` Alexandre TORGUE
2025-05-27 6:36 ` Himanshu Bhavani
2025-05-27 15:18 ` Alexandre TORGUE [this message]
2025-05-24 10:03 ` [PATCH v1 2/2] dt-bindings: arm: stm32: add STM32MP157F-DK2 board compatible Himanshu Bhavani
2025-05-26 15:26 ` Conor Dooley
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=6b9ad1a0-4f7d-498e-ac0d-49ac41a2532b@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=himanshu.bhavani@siliconsignals.io \
--cc=krzk+dt@kernel.org \
--cc=l.goehrs@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=mkl@pengutronix.de \
--cc=o.rempel@pengutronix.de \
--cc=roan@protonic.nl \
--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).