mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard GENOUD <richard.genoud@bootlin.com>
To: "Rob Herring (Arm)" <robh@kernel.org>, Nishanth Menon <nm@ti.com>
Cc: Tero Kristo <kristo@kernel.org>, Beleswar Padhi <b-padhi@ti.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Abhash Kumar <a-kumar2@ti.com>, Udit Kumar <u-kumar1@ti.com>,
	Thomas Richard <thomas.richard@bootlin.com>,
	Gregory CLEMENT <gregory.clement@bootlin.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	devicetree@vger.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v3 1/6] dt-bindings: remoteproc: k3-r5f: Add Jacinto LPM memory region
Date: Wed, 19 Aug 2026 15:58:40 +0200	[thread overview]
Message-ID: <ba9f69a4-3ddb-4f64-b031-02c0d2de0f1c@bootlin.com> (raw)
In-Reply-To: <178423118332.1182230.16969278384286286126.robh@kernel.org>

Le 16/07/2026 à 21:48, Rob Herring (Arm) a écrit :
> 
> On Fri, 03 Jul 2026 16:37:12 +0200, Richard Genoud (TI) wrote:
>> Declare a carveout memory region to store LPM metadata on Jacinto
>> devices.
>>
>> For Jacinto devices, this memory region is needed for saving ATF context
>> and the certificate information of ATF and OPTEE and DM image. This LPM
>> metadata area is firewalled to be accessed only by TIFS.
>>
>> U-Boot R5 SPL/TIFS will use this area to save and restore:
>> - ATF context
>> - ATF certificate information
>> - OPTEE certificate information
>> - DM image (which has been copied in memory at boot time by U-Boot
>> R5-SPL)
>>
>> At resume, U-Boot R5 SPL is executed and detects that the board is
>> resuming (with a flag set in the PMIC), then it:
>> - brings out of retention the DDR
>> - retrieves the LPM memory region from DTS
>> - authenticates certificates from LPM memory region and applies firewalls
>> - asks TIFS to restore TFA and its own minimal context
>> - starts TFA on remote proc
>> - loads back DM image from memory and jumps to DM
>>
>> https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/pm/lpm.html#lpm-msg-lpm-save-addr
>>
>> NB: This memory region is not part of DM memory (which is not retained
>> at suspend)
>>
>> Signed-off-by: Richard Genoud (TI) <richard.genoud@bootlin.com>
>> ---
>>   .../bindings/remoteproc/ti,k3-r5f-rproc.yaml   | 18 +++++++++++++++---
>>   1 file changed, 15 insertions(+), 3 deletions(-)
>>
> 
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> 
> Seems like sashiko raises a legit issue, but that's a kernel issue and
> not my problem if your board crashes.
Thanks for raising this.

Indeed, Sashiko is right.
Using no-map; doesn't prevent from direct mapping through 
devm_ioremap_resource_wc().

Nishanth: Would it be acceptable for Sitara if we skip 
devm_ioremap_resource_wc() for lpm-metadata?
Or should we use a different name for Jacinto, like
firewalled-lpm-metadata?

Regards,
Richard

> 
> Rob


  reply	other threads:[~2026-08-19 13:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 14:37 [PATCH v3 0/6] dts: ti: k3-j7: Reserve memory for LPM metadata Richard Genoud (TI)
2026-07-03 14:37 ` [PATCH v3 1/6] dt-bindings: remoteproc: k3-r5f: Add Jacinto LPM memory region Richard Genoud (TI)
2026-07-16 19:48   ` Rob Herring (Arm)
2026-08-19 13:58     ` Richard GENOUD [this message]
2026-07-03 14:37 ` [PATCH v3 2/6] arm64: dts: ti: k3-j7200-ti-ipc-firmware: Reserve memory for LPM metadata Richard Genoud (TI)
2026-07-03 14:37 ` [PATCH v3 3/6] arm64: dts: ti: k3-j721s2-ti-ipc-firmware: " Richard Genoud (TI)
2026-07-03 14:37 ` [PATCH v3 4/6] arm64: dts: ti: k3-j784s4-ti-ipc-firmware: " Richard Genoud (TI)
2026-07-03 14:37 ` [PATCH v3 5/6] arm64: dts: ti: k3-j722s-ti-ipc-firmware: " Richard Genoud (TI)
2026-07-03 14:37 ` [PATCH v3 6/6] arm64: dts: ti: k3-j742s2-ti-ipc-firmware: " Richard Genoud (TI)

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=ba9f69a4-3ddb-4f64-b031-02c0d2de0f1c@bootlin.com \
    --to=richard.genoud@bootlin.com \
    --cc=a-kumar2@ti.com \
    --cc=b-padhi@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas.richard@bootlin.com \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@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®