mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Markus Schneider-Pargmann <msp@baylibre.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
	Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>, Judith Mendez <jm@ti.com>,
	Daniel Schultz <d.schultz@phytec.de>, Andrew Davis <afd@ti.com>,
	Siddharth Vadapalli <s-vadapalli@ti.com>,
	Paresh Bhagat <p-bhagat@ti.com>, Bryan Brattlof <bb@ti.com>,
	Jai Luthra <jai.luthra@ideasonboard.com>,
	Devarsh Thakkar <devarsht@ti.com>,
	Beleswar Padhi <b-padhi@ti.com>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	Stefano Radaelli <stefano.radaelli21@gmail.com>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Vishal Mahaveer <vishalm@ti.com>,
	Kevin Hilman <khilman@baylibre.com>,
	Sebin Francis <sebin.francis@ti.com>,
	Kendall Willis <k-willis@ti.com>, Akashdeep Kaur <a-kaur@ti.com>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH v8 9/9] arm64: dts: ti: Add wkup R5F nodes to pre-ram bootphase
Date: Wed, 16 Sep 2026 12:40:17 +0200	[thread overview]
Message-ID: <20260916104017.GA284106@francesco-nb> (raw)
In-Reply-To: <DLGNWF2DSXZI.7WRJZRZLGW8@baylibre.com>

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.

Francesco


  reply	other threads:[~2026-09-16 10:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 12:39 [PATCH v8 0/9] arm64: dts: ti: Split wkup R5F memory region for IO+DDR resume Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 1/9] arm64: dts: ti: k3-am62a-phycore-som: Fix wkup R5F memory region size Markus Schneider-Pargmann (TI)
2026-09-03 14:52   ` Andrew Davis
2026-09-03 15:20   ` Bryan Brattlof
2026-09-03 12:39 ` [PATCH v8 2/9] arm64: dts: ti: k3-am62d2-evm: " Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 3/9] arm64: dts: ti: k3-am62a7-sk: " Markus Schneider-Pargmann (TI)
2026-09-03 15:34   ` Bryan Brattlof
2026-09-03 12:39 ` [PATCH v8 4/9] arm64: dts: ti: k3-am62p-verdin: " Markus Schneider-Pargmann (TI)
2026-09-11  5:16   ` Francesco Dolcini
2026-09-03 12:39 ` [PATCH v8 5/9] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 6/9] arm64: dts: ti: var-som-am62p: " Markus Schneider-Pargmann (TI)
2026-09-11 12:00   ` Stefano Radaelli
2026-09-03 12:39 ` [PATCH v8 7/9] arm64: dts: ti: k3-am62a: Split r5f memory region Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 8/9] arm64: dts: ti: k3-am62p: " Markus Schneider-Pargmann (TI)
2026-09-03 12:39 ` [PATCH v8 9/9] arm64: dts: ti: Add wkup R5F nodes to pre-ram bootphase Markus Schneider-Pargmann (TI)
2026-09-11  5:24   ` Francesco Dolcini
2026-09-16 10:17     ` Markus Schneider-Pargmann
2026-09-16 10:40       ` Francesco Dolcini [this message]
2026-09-16 16:07         ` Markus Schneider-Pargmann
2026-09-11  7:42   ` Nishanth Menon
2026-09-16 10:22     ` Markus Schneider-Pargmann
2026-09-11  2:07 ` [PATCH v8 0/9] arm64: dts: ti: Split wkup R5F memory region for IO+DDR resume Bryan Brattlof
2026-09-16 20:52 ` Kendall Willis

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=20260916104017.GA284106@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=a-kaur@ti.com \
    --cc=afd@ti.com \
    --cc=b-padhi@ti.com \
    --cc=bb@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=d.schultz@phytec.de \
    --cc=devarsht@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=francesco.dolcini@toradex.com \
    --cc=hnagalla@ti.com \
    --cc=jai.luthra@ideasonboard.com \
    --cc=jm@ti.com \
    --cc=justinstitt@google.com \
    --cc=k-willis@ti.com \
    --cc=khilman@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=msp@baylibre.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=nm@ti.com \
    --cc=p-bhagat@ti.com \
    --cc=robh@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=sebin.francis@ti.com \
    --cc=stefano.radaelli21@gmail.com \
    --cc=vigneshr@ti.com \
    --cc=vishalm@ti.com \
    /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

all inboxes | Powered by JetHome®