Using The Device Manager; Device Manager Overview - Analog Devices VisualDSP++ 5.0 Service Manual

Using the Device Manager

No dynamic memory allocation is used in the device driver model or
system services. Static memory allocation has been kept to a minimum,
and the vast majority of all data memory required is passed into the device
driver model and system services by the client or application. This allows
the user to determine the amount of memory allocated (and from which
memory space) and the device driver model and system services to use.
Using the Device Manager
The device manager provides the access point into the device driver
model. The device manager presents the device manager API to the
application or client.

Device Manager Overview

The device manager API consists of these functions:
•
adi_dev_Init
•
adi_dev_Terminate
•
adi_dev_Open
•
adi_dev_Control
•
adi_dev_Read
ers to a device
•
adi_dev_Write
buffers to a device
•
adi_pdd_Close
In addition to the API functions into the device manager, the application
provides the device manager with a callback function. Often, the device
manager or physical driver encounters an event that needs to be passed to
10-6
– Provides data and initializes the device manager
- Frees data and closes the device manager
– Opens the device for use
– Sets and detects device specific parameters
– Reads data from a device or queues reception buff-
– Writes data to a device or queues transmission
– Closes the device
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors