Analog Devices VisualDSP++ 5.0 Service Manual page 216

Using the Deferred Callback Manager
How this is implemented depends on whether the DCB manager is used
in standalone mode or in conjunction with the deferred calling mecha-
nism supplied by an RTOS. In all cases, API calls to the DCB manager are
the same: a queue is initialized with a call to
are added to the queue via a call to the
The deferred execution of the callbacks is scheduled according to software
priority by the
environment, the DCB manager registers this function as an interrupt
handler routine against the desired IVG level, using the system services
library's interrupt manager module, when the queue is initialized, and an
interrupt raised each time a callback is posted. Since the standalone ver-
sion uses the interrupt manager, the interrupt manager must be initialized
before the DCB manager is initialized.
The following code sample demonstrates the standalone use of one queue
initialized at IVG level 14, which is the lowest IVG level available at appli-
cation level.
As mentioned above, standalone operation requires the initialization of
the interrupt manager prior to initializing the DCB manager. On the
assumption that the sample application requires that only one interrupt
handler be defined per IVG level, initialize the interrupt manager with the
following code:
u32 ne;
adi_int_Init(NULL,0,&ne,NULL);
5-4
adi_dcb_Dispatch_Callbacks
VisualDSP++ 5.0 Device Drivers and System
adi_dcb_Open
adi_dcb_Post
function. In a standalone
Services Manual for Blackfin Processors
, and callbacks
function.