mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-14 08:57:58 +00:00
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>
This commit is contained in:
parent
0c4e36d65f
commit
c59720c5f4
1 changed files with 6 additions and 0 deletions
|
@ -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;
|
||||
|
|
Loading…
Reference in a new issue