Table of Contents
Advertisement
Interrupt Processing
Interrupt Processing
The following sections describe interrupt processing.
Global Enabling/Disabling of Interrupts
General-purpose interrupts can be globally disabled with the
instruction and re-enabled with the
are only available in Supervisor mode. Reset, NMI, emulation, and excep-
tion events cannot be globally disabled. Globally disabling interrupts
clears
IMASK[15:5]
CLI R5;
/* place critical instructions here */
STI R5;
See "Enable Interrupts" and "Disable Interrupts" in
Event Management."
When multiple instructions need to be atomic or are too time-critical to
be delayed by an interrupt, disable the general-purpose interrupts, but be
sure to re-enable them at the conclusion of the code sequence.
Servicing Interrupts
The Core Event Controller (CEC) has a single interrupt queueing element
per event—a bit in the
an interrupt rising edge is detected (which takes two core clock cycles) and
cleared when the respective
cates that the event vector has entered the core pipeline. At this point, the
CEC recognizes and queues the next rising edge event on the correspond-
ing interrupt input. The minimum latency from the rising edge transition
of the general-purpose interrupt to the
clock cycles. However, the latency can be much higher, depending on the
core's activity level and state.
4-48
ADSP-BF53x/BF56x Blackfin Processor Programming Reference
after saving
IMASK
/* save IMASK to R5 and mask all */
/* restore IMASK from R5 again */
register. The appropriate
ILAT
IPEND
instruction, both of which
STI Dreg
's current state.
Chapter 16, "External
register bit is set. The
output assertion is three core
IPEND
CLI Dreg
bit is set when
ILAT
bit indi-
IPEND
Advertisement
Table of Contents
