| author | Madan Srinivas <madans@ti.com> | |
| Mon, 4 May 2020 03:51:06 +0000 (23:51 -0400) | ||
| committer | Sivaraj R <sivaraj@ti.com> | |
| Tue, 12 May 2020 19:26:28 +0000 (14:26 -0500) | ||
| commit | a535ce635b64ed0ac63c8f758a889411df9b866d | |
| tree | 75cee70e4d62a4589d8dff7028ed748fc7602133 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 90536b04f39a3340cb7a08114a4e09a8a3be7248 | commit | diff |
PDK-5733: SBL: Updates SBL_IsSysfwEnc to use devicetype
In older sysfw releases, there was no way to tell whether the SYSFW was
encrypted or not, without parsing the sysfw to check if it was dual
signed.
After SYSFW Rel 2019.11, it is possible to read the device type from SoC
registers - this enables a faster way to determine if the sysfw is
encrypted or clear text.
This patch updates the SBL_IsSysfwEnc to return that the sysfw is clear
text, only if the device type is GP.
Signed-off-by: Madan Srinivas <madans@ti.com>
In older sysfw releases, there was no way to tell whether the SYSFW was
encrypted or not, without parsing the sysfw to check if it was dual
signed.
After SYSFW Rel 2019.11, it is possible to read the device type from SoC
registers - this enables a faster way to determine if the sysfw is
encrypted or clear text.
This patch updates the SBL_IsSysfwEnc to return that the sysfw is clear
text, only if the device type is GP.
Signed-off-by: Madan Srinivas <madans@ti.com>
| packages/ti/boot/sbl/soc/k3/sbl_sci_client.c | diff | blob | history | |
| packages/ti/boot/sbl/soc/k3/sbl_sci_client.h | diff | blob | history |