tree ed69815234f8c8d62564c9d196048a6f6b399987
parent c3271e760c64b91e5184a5dccb1ec0e3b2f13d6e
author Mohamed Omar Asaker <mohamed.omarasaker@arm.com> 1675902160 +0000
committer Rui Miguel Silva <rui.silva@linaro.org> 1682275671 +0100

psa_ipc: tf-m v1.7 alignment crypto iovec definitions and SIDs

align psa_ipc_crypto_pack_iovec with TF-M v1.7 and propagate changes
across psa_ipc functions. More accurately change sfn_id to function_id

Few psa crypto operations have different in/out_vec expectations
fix the differences between psa crypto client in TS and psa crypto
service in TF-M v1.7 (sha: b725a1346cdb9ec75b1adcdc4c84705881e8fd4e):

operations:
- aead_generate_nonce: TFM service doesn't expect op_handle in in_vec
- aead_update: TFM service doesn't expect op_handle in in_vec
- cipher_generate_iv: TFM service doesn't expect op_handle in in_vec
- cipher_update: TFM service doesn't expect op_handle in in_vec
- hash_clone: TFM service expects target_op_handle in the in_vec
              rationale is target_op_handle according to the spec
              must be initialized and not active. and since hash_clone
              manipulates it. hence, target_op_handle should be passed
              as input and output.

Change the PSA Crypto SIDs to match the values of the PSA Crypto SID
definitions in TF-M v1.7.

Signed-off-by: Mohamed Omar Asaker <mohamed.omarasaker@arm.com>
Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
Change-Id: Ic4887f22a91489661e144c6fd2ac440f56705f55