Adi_Flag_Installcallback - Analog Devices VisualDSP++ 5.0 Service Manual

When using the callback capability of the flag service, the client does not
need to take any other action outside the flag service API. No calls to the
interrupt manager or deferred callback service, other than initialization of
those services, are required.
It is possible for clients to use all capabilities of the flag service and not use
any of the callback capabilities. If callbacks are not used by the client,
no memory need be provided to the flag service's initialization function.

adi_flag_InstallCallback

The
adi_flag_InstallCallback()
a specified flag. In addition to the flag ID, the client provides the inter-
rupt ID that the flag should generate, a wakeup flag, the type of trigger
that generates the callback, the callback function address, a client handle,
and deferred callback service handle. Refer also to
"adi_flag_InstallCallback" on page
Depending on the specific Blackfin processor, programmable flags can
generate any one of several interrupts. (Sometimes the processor is con-
trained as to which flag can generate which interrupt. See the appropriate
Blackfin Hardware Reference for details.) The peripheral ID enumerates
which interrupt the flag generate.s
The wakeup flag indicates whether the processor is woken up from a low
power state should the flag event occur.
The trigger type describes the event that causes the callback to occur.
The following trigger types (all enumerated in the
file) are supported:
• Level high – callback generated when the level is high
• Level low – callback generated when the level is low
• Rising edge – callback generated on the rising edge
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
Programmable Flag Service
function is used to install a callback to
7-26.
adi_flag.h
include
7-7