Table 13. hmac_pad_req valid descriptors (opid), 6 aes requests, 1 aesa_crypt_req – Freescale Semiconductor SEC2SWUG User Manual
Page 19
SEC 2.0 Reference Device Driver User’s Guide, Rev. 0
Freescale Semiconductor
PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE
19
Individual Request Type Descriptions
4.6 AES Requests
4.6.1 AESA_CRYPT_REQ
COMMON_REQ_PREAMBLE
unsigned long keyBytes; /* 16, 24, or 32 bytes */
unsigned char *keyData;
unsigned long inIvBytes; /* 0 or 16 bytes */
unsigned char *inIvData;
unsigned long inBytes; /* multiple of 8 bytes */
unsigned char *inData;
unsigned char *outData; /* output length = input length */
unsigned long outCtxBytes; /* 0 or 8 bytes */
unsigned char *outCtxData;
NUM_AESA_CRYPT_DESC
defines the number of descriptors within the
DPD_AESA_CRYPT_GROUP
that use this
request.
DPD_AESA_CRYPT_GROUP
(0x6000) defines the group for all descriptors within this request.
Table 13. HMAC_PAD_REQ Valid Descriptors (opId)
Descriptors
Value
Function Description
DPD_SHA256_LDCTX_HMAC_ULCTX
0x4A00
Load context, then use an SHA-256 hash algorithm,
then store the resulting HMAC context
DPD_MD5_LDCTX_HMAC_ULCTX
0x4A01
Load context, then use an MD5 hash algorithm, then
store the resulting HMAC context
DPD_SHA_LDCTX_HMAC_ULCTX
0x4A02
Load context, then use an SHA-1 hash algorithm,
then store the resulting HMAC context
DPD_SHA256_LDCTX_HMAC_PAD_ULCTX
0x4A03
Load context, then use an SHA-256 IDGS hash
algorithm, then store the resulting padded HMAC
context
DPD_MD5_LDCTX_HMAC_PAD_ULCTX
0x4A04
Load context, then use an MD5 IDGS hash algorithm,
then store the resulting padded HMAC context
DPD_SHA_LDCTX_HMAC_PAD_ULCTX
0x4A05
Load context, then use an SHA-1 IDGS hash
algorithm, then store the resulting padded HMAC
context