mbox series

[v5,0/3] AM64: Update the locations of various elements in SRAM

Message ID 20210616171224.24635-1-a-govindraju@ti.com (mailing list archive)
Headers show
Series AM64: Update the locations of various elements in SRAM | expand

Message

Aswath Govindraju June 16, 2021, 5:12 p.m. UTC
The following series of patches,
- Increase the maximum size of TF-A
- Update the location of TF-A due to a limitation for DFU boot
- Indicate reserved locations for DMSC code and secure proxy


Link to corresponding U-Boot series that makes these changes:
- https://patchwork.ozlabs.org/project/uboot/list/?series=249235

changes since v4:
- increased the size of TF-A to 128KB to account for future expansions
- Reworded the commit message of patch 3 to include the U-Boot version in
  which the TF-A has been moved to corresponding location
- picked up Suman anna's reviewed-by for patch 2 

changes since v3:
- fixed the title of patches 1 and 2

changes since v2:
- split the patches into three
- added regions for indicating memory regions reserved for
  dmsc and secure proxy
- moved the TFA location to 0x701c4000


Aswath Govindraju (3):
  arm64: dts: ti: k3-am64-main: Update TF-A's maximum size and node name
  arm64: dts: ti: k3-am64-main: Reserve OCMRAM for DMSC-lite and secure
    proxy communication
  arm64: dts: ti: k3-am64-main: Update the location of TF-A in
    compliance with U-Boot v2021.10

 arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

Comments

Nishanth Menon June 17, 2021, 12:11 a.m. UTC | #1
On Wed, 16 Jun 2021 22:42:21 +0530, Aswath Govindraju wrote:
> The following series of patches,
> - Increase the maximum size of TF-A
> - Update the location of TF-A due to a limitation for DFU boot
> - Indicate reserved locations for DMSC code and secure proxy
> 
> 
> Link to corresponding U-Boot series that makes these changes:
> - https://patchwork.ozlabs.org/project/uboot/list/?series=249235
> 
> [...]

Hi Aswath Govindraju,

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!


NOTE: I updated the $subject of patch #3 to be:
arm64: dts: ti: k3-am64-main: Update TF-A load address to workaround USB DFU
limitation

[1/3] arm64: dts: ti: k3-am64-main: Update TF-A's maximum size and node name
      commit: 263820efa3fb08cc606736b68290d9be9c46e2e5
[2/3] arm64: dts: ti: k3-am64-main: Reserve OCMRAM for DMSC-lite and secure proxy communication
      commit: 454a9d4aaacb89daea350d21628992bb83de649f
[3/3] arm64: dts: ti: k3-am64-main: Update TF-A load address to workaround USB DFU limitation
      commit: 3de27ef12ccb50205e602d92f29d082429aa2964


All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git