On 3/24/2025 11:30 AM, Herbert Xu wrote: > On Mon, Mar 24, 2025 at 09:26:20AM +0000, Gaurav Jain wrote: >> >> I discussed the same with Horia. data loaded into or stored from caam_ctx is message data which is regarded as byte strings. > > So is it big endian? > Yes, running message length is big endian, possibly unaligned. >> Also, we want to understand why it is needed? as this data is interpreted by caam internally. > > I'm trying to make all drivers export their hash state in a format > that is compatible with the generic implementation. That way if > there is a memory allocation error, we could just fall back to the > generic algorithm even if we are in the middle of a hash. > > Obviously if you export then you'd need to import as well. So I > need to be able to import a generic hash state into caam and continue > from there. > Thanks for the explanation. Let us know if help is needed wrt. converting to / from caam_export_state (caam-specific hash state). Horia