Device Manager Design
adi_dev_Open Functional Description
The
adi_dev_Open
reference information, see
Processing begins by finding a free
control the device. The address of that data structure is stored in the cli-
ent-provided location as the handle to the device.
The
ADI_DEV_DEVICE
mation describing the device.
Once the
ADI_DEV_DEVICE
the
adi_pdd_Open
executes, doing whatever it needs to do to open the device it controls. If
the physical driver fails to open the device, the device manager frees up the
ADI_DEV_DEVICE
device back to the application. Note that because the return code values
can be extended by the physical device, the return code can be as specific
as possible as to why the device failed to open.
If the physical device opens correctly, the device manager interrogates the
physical device to determine whether it is supported by peripheral DMA.
The device manager saves this information in the
structure.
adi_dev_Close Functional Description
The
adi_dev_Close
is no longer needed. For detailed reference information, see
Close" on page
After the device handle is validated, assuming error checking is enabled,
the function calls the
terminate dataflow. Once dataflow is terminated, any DMA channels that
were opened for the device are closed. The
10-36
function is used to open a device for use. For detailed
"adi_dev_Open" on page
structure is initialized and populated with the infor-
structure is initialized, the device manager calls
function of the physical driver. The physical driver then
structure and returns the return code from the physical
function is called by the application when the device
10-58.
adi_pdd_Control
VisualDSP++ 5.0 Device Drivers and System
data structure used to
ADI_DEV_DEVICE
ADI_DEV_DEVICE
function of the physical driver to
adi_pdd_Close
Services Manual for Blackfin Processors
10-61.
"adi_dev_
function of the
Need help?
Do you have a question about the VisualDSP++ 5.0 and is the answer not in the manual?