always have a buffer in which to store data that is received,
and devices that are opened for outbound or bidirectional
dataflow always have a buffer to transmit out through the
device.
• The system timing is such that the device manager can
acknowledge and service callbacks for a buffer before a call-
back for another buffer on that same device and going in
that same direction (inbound or outbound) is generated.
These conditions can be fairly easily met in most systems.
Static Functions
This section describes the static functions within the device manager that
are used in support of the API functions.
PDDCallback
The
PDDCallback
driver. After error checking the device handle (if error checking is
enabled), the device manager simply passes these events back to the
application.
Note that in this routine (and the
manager calls the client callback function directly, regardless of whether
live callbacks are in effect. It can do this as the physical driver is passed the
handle to the deferred callback service as part of the
function.
As such, if the deferred callback service is in use, the invocation of the
function in the device manager is deferred by the physical
PDDCallback
driver. In this way, the
callback function.
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
function is called in response to events from the physical
DMACallback
PDDCallback
Device Driver Manager
function) the device
adi_pdd_Open
function can directly call the client's
10-41
Need help?
Do you have a question about the VisualDSP++ 5.0 and is the answer not in the manual?