| #
383c821c |
| 03-Feb-2026 |
Govindraj Raja <govindraj.raja@arm.com> |
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 susp
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
show more ...
|
| #
9b1350de |
| 06-Jan-2026 |
Abhash Kumar Jha <a-kumar2@ti.com> |
feat(k3): choose PLAT_CLUSTER_DEVICE_START_ID depending on the SoC
The CLUSTER_DEVICE_START_ID denotes the device id of the A-core cluster.
It is utilized when powering off the entire cluster.
The
feat(k3): choose PLAT_CLUSTER_DEVICE_START_ID depending on the SoC
The 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 when
suspend-to-ram is enabled.
Query the JTAG_ID to get the SoC part number and choose the
CLUSTER_DEVICE_START_ID_AM65X when AM65X SoC is detected, else use
the 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.html
Link: [2] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j721e/devices.html
Link: [3] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j721s2/devices.html
Link: [4] https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/am65x_sr2/devices.html
Change-Id: Idcd47c94e06996e8c1d68b49f13d4d693e95b17d
Signed-off-by: Abhash Kumar Jha <a-kumar2@ti.com>
show more ...
|
| #
e76a0fc4 |
| 06-Jan-2026 |
Abhash Kumar Jha <a-kumar2@ti.com> |
feat(k3): add SoC detection support
Implement SoC detection by reading the part number from the JTAG_ID
register. The part number is used to determine the appropriate cluster
start ID for the SoC.
feat(k3): add SoC detection support
Implement SoC detection by reading the part number from the JTAG_ID
register. The part number is used to determine the appropriate cluster
start 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: Ie97e123627b562edf34e7ff3839f6ceb8b0bbd8b
Signed-off-by: Abhash Kumar Jha <a-kumar2@ti.com>
show more ...
|