2.2 BSP Rel. 1.0 for PPMC-275 Programmer's Guide

API Call Reference List of APIs
ISR Connection
Interrupt Handling
This stage fills each driver's ISR data structure with the information
regarding the connected user ISR. The Interrupt Controller
driver decides which user ISR to connect to which data structure
according to its enumerated macro that defines the interrupt cause
distribution (High or Low Cause registers).
When an interrupt is pending, the connected driver's ISR (connected
in initialization phase) is invoked to search its data structure
for the interrupt cause which initiated the interrupt. After the
initiating interrupt has been identified, the appropriate user ISR is
invoked.
External Interface Data Structure
The external interface data structure is provided here.
ENUM GT_INT_CAUSE {The list of High and Low Interrupt causes (Total of 64 causes)}
This enumerator creates the Global Cause register out of Main
High and Low Interrupt Cause registers. When the High Cause
register is first, each interrupt cause is represented by an integer.
To hook a C routine to the MV Interrupt Controller, use this enum
type to describe the MV cause that you would like to hook to (this
is done for improved code readability).
CAUSE DISTRIBUTOR
MACROS
CPU INT[0/1]* MASK
SELECTION
This driver defines Cause distribution macros. Each MV-64360
interrupt pin is represented by a macro (or two). This macro
defines which cause bits are active in each interrupt pin:
· CPU_INT_HIGH_CAUSE CPU interrupt pin
· CPU_INT_LOW_CAUSE CPU interrupt pin
For example:
#define CPU_INT_LOW_CAUSE (cause >=00 && cause