Changes in soc.h

383c821c76e05b64fc641cf59541793d29185859 - Merge changes from topic "ti-k3-encrypt-and-suspend-support" into integration

Tue, 03 Feb 2026 15:05:07 +0000

Merge changes from topic "ti-k3-encrypt-and-suspend-support" into integration* changes: feat(k3): handle suspend in case of LPM_BOARDCFG_MANAGED feat(ti): add message to encrypt tfa during suspend feat(ti): cache the response for msg_version and query_caps fix(ti): handle null parameter early in query_fw_caps fix(ti): fix invalid parameter in the function comment feat(k3): choose PLAT_CLUSTER_DEVICE_START_ID depending on the SoC feat(k3): add SoC detection support List of files: /rk3399_ARM-atf/plat/ti/k3/include/soc.h

9b1350def9f51e5487fb42f5f041efceb73456f8 - feat(k3): choose PLAT_CLUSTER_DEVICE_START_ID depending on the SoC

Tue, 06 Jan 2026 05:45:35 +0000

feat(k3): choose PLAT_CLUSTER_DEVICE_START_ID depending on the SoCThe CLUSTER_DEVICE_START_ID denotes the device id of the A-core cluster.It is utilized when powering off the entire cluster.The "generic" boards include J7200, J721E, J721S2 and AM65X platforms.PLAT_CLUSTER_DEVICE_START_ID should be 4 instead of 198 on J7200[1],J721E[2] and J721S2[3]. It is 198 only for AM65X[4].This breaks PSCI APIs around cluster control and is exposed whensuspend-to-ram is enabled.Query the JTAG_ID to get the SoC part number and choose theCLUSTER_DEVICE_START_ID_AM65X when AM65X SoC is detected, else usethe PLAT_CLUSTER_DEVICE_START_ID that is defined in the respective"board_def" file.Link: [1] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j7200/devices.htmlLink: [2] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j721e/devices.htmlLink: [3] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j721s2/devices.htmlLink: [4] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/am65x_sr2/devices.htmlChange-Id: Idcd47c94e06996e8c1d68b49f13d4d693e95b17dSigned-off-by: Abhash Kumar Jha List of files: /rk3399_ARM-atf/plat/ti/k3/include/soc.h

e76a0fc4c999529801053177495932ac7a03dbec - feat(k3): add SoC detection support

Tue, 06 Jan 2026 06:05:47 +0000

feat(k3): add SoC detection supportImplement SoC detection by reading the part number from the JTAG_IDregister. The part number is used to determine the appropriate clusterstart ID for the SoC.Note: J742S2 and J784S4 have the same part number and cluster start ID,so they are handled identically without additional logic.Change-Id: Ie97e123627b562edf34e7ff3839f6ceb8b0bbd8bSigned-off-by: Abhash Kumar Jha List of files: /rk3399_ARM-atf/plat/ti/k3/include/soc.h