Command Ids; Callback Events; Return Codes - Analog Devices VisualDSP++ 5.0 Service Manual

Device Manager Design

Command IDs

The next section in the
are defined by the device manager. These command IDs are passed to the
device manager via the
Physical drivers can add any number of additional command IDs that are
relevant to their particular device. Physical drivers begin adding their own
command IDs starting with the enumeration start value for the driver.
Also included in this section is a data structure defining a configuration
command pair. This is provided as a convenience—it allows clients to pass
a table of commands into the
being forced to call the
"adi_dev_Control" on page

Callback Events

The next section in the
events. When an event occurs, the client's callback function is invoked
and passed the enumeration of the event that occurred.
The device manager defines some common events. Similar to command
IDs, physical drivers can add their own callback events beginning with the
enumeration start value for the driver.

Return Codes

The next section in the
codes. All API functions within the device manager return a code,
indicating the results of the function call.
The device manager defines some typical return codes. Similar to
command IDs and callback events, physical drivers can add their own
return codes beginning with the enumeration start value for the driver.
10-32
file enumerates the command IDs that
adi_dev.h
function.
adi_dev_Control
adi_dev_Control
adi_dev_Control
10-59).
file contains enumerations for callback
adi_dev.h
file contains enumerations for return
adi_dev.h
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
function, rather than
function for each command (see