Mbed TLS v4.1.1
Loading...
Searching...
No Matches
psa_xof_operation_s Struct Reference

#include <crypto_struct.h>

Collaboration diagram for psa_xof_operation_s:

Data Fields

unsigned int private_id
unsigned requires_context: 1
unsigned allows_context: 1
unsigned active: 1
unsigned has_context: 1
unsigned has_input: 1
unsigned has_output: 1
psa_driver_xof_context_t private_ctx

Detailed Description

Definition at line 88 of file crypto_struct.h.

Field Documentation

◆ active

unsigned psa_xof_operation_s::active

Definition at line 105 of file crypto_struct.h.

◆ allows_context

unsigned psa_xof_operation_s::allows_context

Definition at line 102 of file crypto_struct.h.

◆ has_context

unsigned psa_xof_operation_s::has_context

Definition at line 106 of file crypto_struct.h.

◆ has_input

unsigned psa_xof_operation_s::has_input

Definition at line 107 of file crypto_struct.h.

◆ has_output

unsigned psa_xof_operation_s::has_output

Definition at line 108 of file crypto_struct.h.

◆ private_ctx

psa_driver_xof_context_t psa_xof_operation_s::private_ctx

Definition at line 110 of file crypto_struct.h.

◆ private_id

unsigned int psa_xof_operation_s::private_id

Unique ID indicating which driver got assigned to do the operation. Since driver contexts are driver-specific, swapping drivers halfway through the operation is not supported. ID values are auto-generated in psa_driver_wrappers.h. ID value zero means the context is not valid or not assigned to any driver (i.e. the driver context is not active, in use).

Definition at line 98 of file crypto_struct.h.

◆ requires_context

unsigned psa_xof_operation_s::requires_context

Definition at line 101 of file crypto_struct.h.


The documentation for this struct was generated from the following file: