| Message ID | 20230530165900.47502-1-nm@ti.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | arm64: dts: ti: Add additional secproxy instances | expand |
Hi Nishanth Menon, On Tue, 30 May 2023 11:58:53 -0500, Nishanth Menon wrote: > This series introduces secure proxies meant for usage with bootloaders > and firmware components in the SoC for all K3 SoCs. AM64x SoC is an odd > case here as the single instance of secure proxy is dual use for both > ROM and general purpose. All other SoCs have independent instances that > is used for firmware and bootloader communication. > > Nitin had posted [1] to address one of the SoCs (AM62), I am cleaning > that patch a bit in this series. > > [...] I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/7] arm64: dts: ti: k3-am62-main: Add sa3_secproxy commit: 7450aa5153af55a0c63785a6917e35a989a4fdf5 [2/7] arm64: dts: ti: k3-am62a-main: Add sa3_secproxy commit: f7d3b11cacd1fc9596444e89209b80800d20ea22 [3/7] arm64: dts: ti: k3-am65-mcu: Add mcu_secproxy commit: 84debc33b529cae428f29b1eb21ccc05c8b47a16 [4/7] arm64: dts: ti: k3-j7200-mcu: Add mcu_secproxy commit: c4e43f5aef9731c480789dcb044d261f894a102e [5/7] arm64: dts: ti: k3-j721e-mcu: Add mcu_secproxy commit: 753904da7072646666fa17a5030ef2be871a385a [6/7] arm64: dts: ti: k3-j721s2-mcu-wakeup: Add sa3_secproxy and mcu_sec_proxy commit: 77f622cb8633c020a78cfb8b7d3d73ba3eaf0a44 [7/7] arm64: dts: ti: k3-j784s4-mcu-wakeup: Add sa3_secproxy and mcu_sec_proxy commit: 389ad7111ddd99a05c75bc7d4f480a0526761d06 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] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git -- Vignesh
Hi, This series introduces secure proxies meant for usage with bootloaders and firmware components in the SoC for all K3 SoCs. AM64x SoC is an odd case here as the single instance of secure proxy is dual use for both ROM and general purpose. All other SoCs have independent instances that is used for firmware and bootloader communication. Nitin had posted [1] to address one of the SoCs (AM62), I am cleaning that patch a bit in this series. Nishanth Menon (6): arm64: dts: ti: k3-am62a-main: Add sa3_secproxy arm64: dts: ti: k3-am65-mcu: Add mcu_secproxy arm64: dts: ti: k3-j7200-mcu: Add mcu_secproxy arm64: dts: ti: k3-j721e-mcu: Add mcu_secproxy arm64: dts: ti: k3-j721s2-mcu-wakeup: Add sa3_secproxy and mcu_sec_proxy arm64: dts: ti: k3-j784s4-mcu-wakeup: Add sa3_secproxy and mcu_sec_proxy Nitin Yadav (1): arm64: dts: ti: k3-am62-main: Add sa3_secproxy arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 15 ++++++++++ arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 15 ++++++++++ arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 15 ++++++++++ .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 15 ++++++++++ .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 15 ++++++++++ .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 30 +++++++++++++++++++ .../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 30 +++++++++++++++++++ 7 files changed, 135 insertions(+) [1] https://lore.kernel.org/all/20230519113434.1024206-3-n-yadav@ti.com/