Hi Francesco,

On Wed Sep 16, 2026 at 12:40 PM CEST, Francesco Dolcini wrote:
> On Wed, Sep 16, 2026 at 12:17:42PM +0200, Markus Schneider-Pargmann wrote:
>> Hi Francesco,
>> 
>> On Fri Sep 11, 2026 at 7:24 AM CEST, Francesco Dolcini wrote:
>> > Hello Markus
>> >
>> > On Thu, Sep 03, 2026 at 02:39:30PM +0200, Markus Schneider-Pargmann (TI) wrote:
>> >> For IO+DDR the wkup_r5fss0_core0 and the
>> >> wkup_r5fss0_core0_lpm_metadata_region need to be accessed before RAM
>> >> setup is done. These are used to read the lpm metadata region in
>> >> which data is stored to resume. This needs to be done before RAM is
>> >> in use to avoid overwriting data.
>> >> 
>> >> Add the bootph-pre-ram flag to the wkup_r5fss0_core0 node in both
>> >> ipc-firmware dtsi files and to the lpm metadata region nodes of the
>> >> AM62A and AM62P boards.
>> >> 
>> >> The board level bootph-pre-ram flag of k3-am62d2-evm.dts becomes
>> >> redundant with the dtsi-wide flag and is dropped.
>> >> 
>> >> Signed-off-by: Markus Schneider-Pargmann (TI) <msp@baylibre.com>
>> > ...
>> >
>> >> diff --git a/arch/arm64/boot/dts/ti/k3-am62p-verdin.dtsi b/arch/arm64/boot/dts/ti/k3-am62p-verdin.dtsi
>> >> index 45ab9d947b3a..8976c0424cd1 100644
>> >> --- a/arch/arm64/boot/dts/ti/k3-am62p-verdin.dtsi
>> >> +++ b/arch/arm64/boot/dts/ti/k3-am62p-verdin.dtsi
>> >> @@ -184,6 +184,7 @@ wkup_r5fss0_core0_lpm_metadata_region: memory@9ca08000 {
>> >>  			compatible = "shared-dma-pool";
>> >>  			reg = <0x00 0x9ca08000 0x00 0x1000>;
>> >>  			no-map;
>> >> +			bootph-pre-ram;
>> >>  		};
>> >
>> > verdin-am62p has the various bootph tags only in the U-Boot dtsi
>> > (k3-am62p5-verdin-wifi-dev-u-boot.dtsi) as of now, I am not convinced it
>> > is a good idea to just add this single one here.
>> 
>> I don't see any bootph-* flags for any of the related memory regions in
>> k3-am62p5-verdin-wifi-dev-u-boot.dtsi. Is it in a different dtsi?
>
> What I meant is that any bootph- property is in
> arch/arm/dts/k3-am6p25-verdin-wifi-dev-u-boot.dtsi 
>
> And I would not start adding spreading this in 2 different places.

As I said, there are 72 bootph- properties in am62p related devicetrees
in the kernel devicetrees. For k3-am62p-verdin*.dts the relevant ones
are probably:

      3 arch/arm64/boot/dts/ti/k3-am62p.dtsi
     14 arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi
      2 arch/arm64/boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi
      2 arch/arm64/boot/dts/ti/k3-am62p-j722s-common-wakeup.dtsi

Also if I understand correctly, it is preferred to get these bootph-
tags into the upstream devicetree:

  https://lore.kernel.org/u-boot/20260903144032.GI1764417@bill-the-cat/

Best
Markus