Persistent Memory Interface Data Types

Data Types needed for interfacing with persistent memory. More...

Data Structures
struct	pstorage_module_param_t
	Struct containing module registration context. More...

Typedefs
typedef void(*	pstorage_ntf_cb_t )(pstorage_handle_t *p_handle, uint8_t op_code, uint32_t result, uint8_t *p_data, uint32_t data_len)
	Persistent storage operation completion callback function type. More...

Detailed Description

Data Types needed for interfacing with persistent memory.

Typedef Documentation

typedef void(* pstorage_ntf_cb_t)(pstorage_handle_t *p_handle, uint8_t op_code, uint32_t result, uint8_t *p_data, uint32_t data_len)

Persistent storage operation completion callback function type.

The persistent storage operation completion callback is used by the interface to report success or failure of a flash operation. Since data is not copied for a store operation, a callback is an indication that the resident memory can now be reused or freed.

Parameters

[in]	handle	Identifies the module and block for the callback that is received.
[in]	op_code	Identifies the operation for the event that is notified.
[in]	result	Identifies the result of a flash access operation. NRF_SUCCESS implies operation succeeded.

Note

Unmanaged (abnormal behaviour) error codes from the SoftDevice flash access API are forwarded as is and are expected to be handled by the application. For details refer to the implementation file and corresponding SoftDevice flash API documentation.

Parameters

[in]	p_data	Identifies the application data pointer. For a store operation, this points to the resident source of application memory that the application can now free or reuse. When there is a clear operation, this is NULL since no application pointer is needed for this operation.
[in]	data_len	Length data the application provided for the operation.