Physical drivers have their own API, which is accessed by the device
manager. The following sections describe the API and the functionality
provided by the physical driver.
Physical Device Driver API Description
The API into a physical device driver is similar to the API between the
device manager and the application in that there is a function in the
physical driver API that maps to each function in the device manager API,
except for
adi_dev_Init
and are defined in the device manager include file (
The physical device driver functions are encapsulated in a structure called
ADI_DEV_PDD_ENTRY_POINT
structure. The application passes the address of this structure to the device
manager as part of the
turn, uses this data structure to call the individual routines in the physical
driver. This mechanism allows multiple physical drivers to exist in the
same system without causing name space conflicts.
There are five functions in the physical driver API. These functions are
described in the sections that follow. The API functions include:
•
adi_pdd_Open
•
adi_pdd_Close
•
adi_pdd_Read
•
adi_pdd_Write
out the device
•
adi_pdd_Control
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
. These functions are all prefixed with
. Each physical driver exports an entry point
function call. The device manager, in
adi_dev_Open
– Opens a device for use
– Closes a device
– Provides buffers for reception of data from a device
– Provides buffers containing data for transmission
– Configures the device
Device Driver Manager
adi_pdd
).
adi_dev.h
10-47
Need help?
Do you have a question about the VisualDSP++ 5.0 and is the answer not in the manual?