Adi_Pdd_Read Functional Description - Analog Devices VisualDSP++ 5.0 Service Manual

•
ADI_DEV_CMD_GET_PERIPHERAL_DMA_SUPPORT
or
FALSE
device is supported by peripheral DMA, the
function is also prepared to respond to the following command
IDs:
•
ADI_DEV_CMD_GET_INBOUND_DMA_PMAP_ID
the DMA peripheral map (PMAP) ID for the given device
•
ADI_DEV_CMD_GET_OUTBOUND_DMA_PMAP_ID
the DMA peripheral map (PMAP) ID for the given device
In most cases, the
structed similarly to a C-style switch statement. Each command that the
physical driver cares about, including the required command IDs listed
above and any additional command IDs created by the physical driver
itself, have an entry in the statement. If the physical driver receives a com-
mand ID that it does not understand, it typically returns the
RESULT_NOT_SUPPORTED

adi_pdd_Read Functional Description

The
adi_pdd_Read
the application calling the
buffers with inbound data that is received from the device. With all API
functions, if error checking is enabled, the routine validates the physical
driver handle upon entry into the function. For detailed reference infor-
mation, see "adi_pdd_Read Functional Description" on page
For devices that are supported by peripheral DMA, the device manager
manages all buffer queueing and reception. As a result, if the device is
supported by peripheral DMA, the
by the device manager and no functionality need be provided by this
routine. This greatly simplifies device drivers for devices that are sup-
ported by processor DMA. Physical drivers that are supported by
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
if the device is supported by peripheral DMA. If the
adi_pdd_Control
return code.
function is called by the device manager in response to
adi_dev_Read
Device Driver Manager
– Responds with
adi_pdd_Control
function of the physical driver is con-
function. Its purpose is to fill
function is never called
adi_pdd_Read
TRUE
– Responds with
– Responds with
ADI_DEV_
10-53.
10-53