[PATCH V5 0/2] firmware: ti_sci: zero the secure_hdr in do_xfer

[Dhruva Gole]

This series adds a fix to make the initial 4 bytes of the secure_hdr to be 0 as per the protocol requirement as of now.
Also, inorder to provide a little more context to people add a comment to explain why secure calls are made from uboot

For context, please refer to the discussion from the first patch here:
https://lore.kernel.org/all/20240124101558.184411-1-d-gole@ti.com/

Boot tested for sanity on AM62x SK and J721S2:
https://gist.github.com/DhruvaG2000/9ca35d1261e8b30f1c2d4a514b9cd941

Changelog:

v4 --> v5
Pick Nishanth's review and also s/sizeof(var)/sizeof(*var) in 1/2

v3 --> v4
Improve commit message in 1/2 and add comment in 2/2

v2 --> v3
Address Kamlesh's comment on v2: use sizeof(struct ti_sci_secure_msg_hdr)

v1 --> v2
Rebased on top of latest master branch

Cc: Nishanth Menon <nm at ti.com>
Cc: Tom Rini <trini at konsulko.com>
Cc: Neha Francis <n-francis at ti.com>
Cc: Manorit Chawdhry <m-chawdhry at ti.com>
Cc: Vignesh Raghavendra <vigneshr at ti.com>
Cc: Kamlesh Gurudasani <kamlesh at ti.com>
Cc: Andrew Davis <afd at ti.com>

Dhruva Gole (2):
  firmware: ti_sci: fix the secure_hdr in do_xfer
  firmware: ti_sci: Add comment explaining the is_secure code

 drivers/firmware/ti_sci.c | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)


base-commit: d5c0c990c3128401810514c66b41b386096d206e
prerequisite-patch-id: 2ed0c527b6ebf850744d9ff0eca0300a125f7796
-- 
2.34.1