linux-kernel - Re: [PATCH v2 6/6] arm64: dts: st: Add boot phase tags for STMicroelectronics mp2 boards

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <87e037a6-3f5f-411c-b029-83f26f5d5bc8@foss.st.com>
Date: Thu, 8 Jan 2026 18:10:48 +0100
From: Patrice CHOTARD <patrice.chotard@...s.st.com>
To: Alexandre TORGUE <alexandre.torgue@...s.st.com>, Rob Herring
	<robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
	<conor+dt@...nel.org>, Maxime Coquelin <mcoquelin.stm32@...il.com>, "Patrick
 Delaunay" <patrick.delaunay@...s.st.com>
CC: <devicetree@...r.kernel.org>, <linux-stm32@...md-mailman.stormreply.com>,
	<linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 6/6] arm64: dts: st: Add boot phase tags for
 STMicroelectronics mp2 boards



On 1/8/26 17:16, Alexandre TORGUE wrote:
> Hi Patrice
> 
> On 11/14/25 18:26, Patrice Chotard wrote:
>> The bootph-all flag was introduced in dt-schema
>> (dtschema/schemas/bootph.yaml) to define node usage across
>> different boot phases.
>>
>> To ensure SD boot, timer, gpio, syscfg, clock and uart nodes need to be
>> present in all boot stages, so add missing bootph-all phase flag
>> to these nodes to support SD boot.
>>
>> Signed-off-by: Patrice Chotard <patrice.chotard@...s.st.com>
>> ---
>>   arch/arm64/boot/dts/st/stm32mp211.dtsi     |  7 +++++++
>>   arch/arm64/boot/dts/st/stm32mp215f-dk.dts  |  1 +
>>   arch/arm64/boot/dts/st/stm32mp231.dtsi     | 22 ++++++++++++++++++++++
>>   arch/arm64/boot/dts/st/stm32mp235f-dk.dts  | 11 +++++++++++
>>   arch/arm64/boot/dts/st/stm32mp251.dtsi     | 26 ++++++++++++++++++++++++++
>>   arch/arm64/boot/dts/st/stm32mp255.dtsi     |  3 ++-
>>   arch/arm64/boot/dts/st/stm32mp257f-dk.dts  | 11 +++++++++++
>>   arch/arm64/boot/dts/st/stm32mp257f-ev1.dts | 11 +++++++++++
>>   8 files changed, 91 insertions(+), 1 deletion(-)
>>
> 
> ....
> 
>> diff --git a/arch/arm64/boot/dts/st/stm32mp251.dtsi b/arch/arm64/boot/dts/st/stm32mp251.dtsi
>> index a8e6e0f77b83..f6576304f42f 100644
>> --- a/arch/arm64/boot/dts/st/stm32mp251.dtsi
>> +++ b/arch/arm64/boot/dts/st/stm32mp251.dtsi
>> @@ -66,6 +66,7 @@ optee: optee {
> 
> ...
> 
> 
>>                 ltdc: display-controller@...10000 {
>> +                bootph-all;
>>                   compatible = "st,stm32mp251-ltdc";
>>                   reg = <0x48010000 0x400>;
>>                   interrupts = <GIC_SPI 158 IRQ_TYPE_LEVEL_HIGH>,
>> @@ -1577,6 +1585,7 @@ ltdc: display-controller@...10000 {
>>                   clock-names = "lcd", "bus";
>>                   resets = <&rcc LTDC_R>;
>>                   access-controllers = <&rifsc 80>;
>> +                bootph-all;
> 
> duplicate property = build issue.

Argh, sorry, i didn't see this issue as i only build for 32 bits platforms ....

I resent a v3 ASAP.

Thanks
Patrice


> 
> 
>>                   status = "disabled";
>>               };
>>   
> 
>