aboutsummaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorDhruva Gole <d-gole@ti.com>2024-01-30 20:30:00 +0530
committerTom Rini <trini@konsulko.com>2024-02-06 16:31:06 -0500
commitc59720c5f4c592688d2899b352f446703c968666 (patch)
tree28bf6997a89ecee56bdc8062fe65216e18d58b32 /drivers
parent0c4e36d65f6c25e5016235cc3f1e97c8d237f416 (diff)
downloadu-boot-c59720c5f4c592688d2899b352f446703c968666.zip
u-boot-c59720c5f4c592688d2899b352f446703c968666.tar.gz
u-boot-c59720c5f4c592688d2899b352f446703c968666.tar.bz2
firmware: ti_sci: Add comment explaining the is_secure code
Add a comment to explain the code under is_secure condition of ti_sci_do_xfer. This will help avoid confusion amongst people who may in future touch upon this code. Reviewed-by: Nishanth Menon <nm@ti.com> Signed-off-by: Dhruva Gole <d-gole@ti.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/firmware/ti_sci.c6
1 files changed, 6 insertions, 0 deletions
diff --git a/drivers/firmware/ti_sci.c b/drivers/firmware/ti_sci.c
index b77ac36..ee09218 100644
--- a/drivers/firmware/ti_sci.c
+++ b/drivers/firmware/ti_sci.c
@@ -239,6 +239,12 @@ static int ti_sci_do_xfer(struct ti_sci_info *info,
struct ti_sci_secure_msg_hdr *secure_hdr = (struct ti_sci_secure_msg_hdr *)secure_buf;
int ret;
+ /*
+ * The reason why we need the is_secure code is because of boot R5.
+ * boot R5 starts off in "secure mode" when it hands off from Boot
+ * ROM over to the Secondary bootloader. The initial set of calls
+ * we have to make need to be on a secure pipe.
+ */
if (info->is_secure) {
/* ToDo: get checksum of the entire message */
secure_hdr->checksum = 0;