FDE only use one ice keyslot on gen3, the remains used by FBE. For
the ufs crypto layer, it needs to support FBE and FDE request concurrently.
Test cases:
1. LV host FDE OTA and basic test validated pass
2. LA container FBE OTA and basic test validated pass.
Change-Id: Ic0c6e0f9d39d351c1095f531f1fa8bd2a8e614b7
Signed-off-by: jianshu <quic_jianshu@quicinc.com>
UFS/EMMC crypto driver pass the appropriate storage type to
the underlying common, hwkm and tz driver which then set the
storage type to make the SCM call to TZ.
Test:
Validated the FBE v2, FBE v1 on both UFS and EMMC targets.
Change-Id: I0e5dcd678cff9ea5dfd70956684e809a37839372
Signed-off-by: Yuvaraj Ranganathan <quic_yrangana@quicinc.com>
Currently we check the UFS state before programming keys.
Ideas is that key programming to ICE should allow to continue
only when in operational or suspend/resume state.
To achieve this, it is better to have a reset_in_progress flag
that is set and unset only when needed than checking the UFS state
as some innocuous states might be missed.
Change-Id: I79f36737c0637d51fe26db196b8f9a8a70b9b802
Signed-off-by: Gaurav Kashyap <quic_gaurkash@quicinc.com>
Add support in UFS to exercise data encryption using
wrapped keys.
Change-Id: I2239658e75bd4a54d8a6386badf97de21fe2bbef
Signed-off-by: Gaurav Kashyap <quic_gaurkash@quicinc.com>
