On Wed, Dec 31, 2025 at 11:06:10PM +0530, Beleswar Padhi wrote: > Some TI K3 SoCs like J721S2, J784S4, and J722S have a HSM (High Security > Module) M4F core in the Wakeup Voltage Domain which could be used to > run secure services like Authentication. Boot flow for HSM M4 core is > different than the general purpose M4F cores, and is as below: > > 1. Request control of HSM M4F remote processor. > 2. Assert Reset on the HSM M4F remote processor. > 3. Request Secure Entity to Authenticate and Load HSM firmware into > core's internal SRAM memory region. For GP device, load the firmware > manually into core's SRAM region. > 4. Deassert Reset on the HSM M4F remote processor. > 5. Release control of HSM M4F remote processor. > > This series adds support to boot HSM M4 core from R5 SPL stage. The HSM > firmware is packed inside the tispl.bin fit image. The firmware is > unpacked into a temporary DDR address which is then used to load HSM > core. The configs to boot HSM M4 core are disabled by default. > > Note: > This series is dependent on the device-tree changes series posted to > Kernel mailing list: > https://lore.kernel.org/all/[email protected]/
I see there's already feedback there and I expect at least a v2, so I'm going to mark this series as RFC. As I expect you'll have to change this, please wait to do v4 until the dts portion is in linux-next. I'll look over this series itself now for high level things, and leave it to TI folks to poke at any specific details, thanks. -- Tom
signature.asc
Description: PGP signature
