Nexus Embedded Platform 1.0.0
Statically assembled reusable embedded mechanisms
Loading...
Searching...
No Matches
nx_user_io_result_t Struct Reference

Distinguish admission, cleanup retention and possible effect. More...

#include <user_io_broker.h>

Data Fields

nx_result_t result
nx_result_t cleanup_result
bool accepted
bool retained
bool device_effect_possible

Detailed Description

Distinguish admission, cleanup retention and possible effect.

Note
accepted means at least one memory pin was acquired. On retained=true the exact kernel call slot and user address space remain borrowed. device_effect_possible is set before a WRITE provider call; an error cannot authorize replay. result describes admission/device execution; cleanup_result separately describes the most recent release attempt. This is software responsibility, not physical pin evidence.

Definition at line 56 of file user_io_broker.h.

Field Documentation

◆ accepted

bool nx_user_io_result_t::accepted

Definition at line 59 of file user_io_broker.h.

◆ cleanup_result

nx_result_t nx_user_io_result_t::cleanup_result

Definition at line 58 of file user_io_broker.h.

◆ device_effect_possible

bool nx_user_io_result_t::device_effect_possible

Definition at line 61 of file user_io_broker.h.

◆ result

nx_result_t nx_user_io_result_t::result

Definition at line 57 of file user_io_broker.h.

◆ retained

bool nx_user_io_result_t::retained

Definition at line 60 of file user_io_broker.h.


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