Interrupt Manager Termination - Analog Devices VisualDSP++ 5.0 Service Manual

The
ADI_INT_SECONDARY_MEMORY
memory (in bytes) required to support a single secondary handler. Thus,
the application should provide to the initialization function "
ADI_INT_SECONDARY_MEMORY
handlers that are supported.
Another parameter passed to the initialization function is the parameter
that the interrupt manager passes to the
function. This value depends upon the operating environment of the
application. See the
information.
When called, the initialization function initializes its internal data struc-
tures and returns. No changes are made to the CEC or SIC during
initialization. After initialization, any other interrupt manager API
functions may be called.

Interrupt Manager Termination

When the functionality of the interrupt manager is no longer required, the
application can call the termination function of the interrupt manager,
adi_int_Terminate()
never call the termination function.
When called, the termination function unhooks all interrupt handlers,
masking off (disabling) all interrupts the that the interrupt manager was
controlling. After calling the termination function, any memory provided
to the initialization function may be reused by the application. No other
interrupt manager functions can be called after termination. If interrupt
manager services are required after the termination function is called, the
application must reinitialize interrupt manager services by calling the
adi_pwr_Init
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
, where "
adi_int_EnterCriticalRegion
. Many applications operate in an endless loop and
function.
macro is defined to be the amount of
" is the number of secondary
n
adi_int_EnterCriticalRegion()
Interrupt Manager
" times
n
function for more
2-5