E PRELIMINARY 82093AA I/O ADVANCED PROGRAMMABLE INTERRUPT CONTROLLER (IOAPIC) Provides Multiprocessor Interrupt (cid:190)(cid:190) 3 General Purpose Interrupts Management (cid:190)(cid:190) Independently Programmable for (cid:190)(cid:190) Dynamic Interrupt Distribution- Edge/Level Sensitivity Interrupts Routing Interrupt to the Lowest (cid:190)(cid:190) Each Interrupt Can Be Programmed Priority Processor to Respond to Active High or Low (cid:190)(cid:190) Software Programmable Control of Inputs Interrupt Inputs X-Bus Interface (cid:190)(cid:190) Off Loads Interrupt Related Traffic (cid:190)(cid:190) CS For Flexible Decode of the From the Memory Bus IOAPIC Device. 24 Programmable Interrupts (cid:190)(cid:190) Index Register Interface for (cid:190)(cid:190) 13 ISA Interrupts Supported Optimum Memory Usage (cid:190)(cid:190) 4 PCI Interrupts Registers are 32-Bit Wide to Match (cid:190)(cid:190) 1 Interrupt/SMI# Rerouting the PCI to Host Bridge Architecture (cid:190)(cid:190) 2 Motherboard Interrupts Package 64-Pin PQFP (cid:190)(cid:190) 1 Interrupt Used for INTR Input The 82093AA I/O Advanced Programmable Interrupt Controller (IOAPIC) provides multi-processor interrupt management and incorporates both static and dynamic symmetric interrupt distribution across all processors. In systems with multiple I/O subsystems, each subsystem can have its own set of interrupts. Each interrupt pin is individually programmable as either edge or level triggered. The interrupt vector and interrupt steering information can be specified per interrupt. An indirect register accessing scheme optimizes the memory space needed to access the IOAPIC’s internal registers. To increase system flexibility when assigning memory space usage, the The IOAPIC’s 2-register memory space is re-locatable. D[7:0] AIPC APCID[1:0] D/I# Bus A[1:0] APCICLK RD# System Interface WR# Bus CS# Interface APCID[1:0] APCIREQ# Interrupt APICACK1# APCICLK Controller APICACK2# APCICLK Clock RESET And Test TESTIN# CLK Reset IOA_BLK Figure 1. IOAPIC Simplified Block Diagram Information in this document is provided in connection with Intel products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document or by the sale of Intel products. Except as provided in Intel’s Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. Intel products are not intended for use in medical, life saving, or life sustaining applications. Intel retains the right to make changes to specifications and product descriptions at any time, without notice. The 82093AA IOAPIC may contain design defects or errors known as errata. Current characterized errata are available on request. Third-party brands and names are the property of their respective owners. © INTEL CORPORATION 1996 May 1996 Order Number: 290566-001 (cid:190)(cid:190) E 82093AA (IOAPIC) CONTENTS PAGE 1.0. OVERVIEW......................................................................................................................................................3 2.0. SIGNAL DESCRIPTION..................................................................................................................................5 2.1. System Bus Signals......................................................................................................................................5 2.2. Clock and Reset Signals...............................................................................................................................6 2.3. APIC Bus Interface.......................................................................................................................................6 2.4. Interrupt Signals............................................................................................................................................6 2.5. Test and Power Signals................................................................................................................................7 3.0. REGISTER DESCRIPTION.............................................................................................................................8 3.1. Memory Mapped Registers for Accessing IOAPIC Registers......................................................................9 3.1.1. IOREGSEL—I/O REGISTER SELECT REGISTER.............................................................................9 3.1.2. IOWIN—I/O WINDOW REGISTER.......................................................................................................9 3.2. IOAPIC Registers.........................................................................................................................................9 3.2.1. IOAPICID—IOAPIC IDENTIFICATION REGISTER.............................................................................9 3.2.2. IOAPICVER—IOAPIC VERSION REGISTER....................................................................................10 3.2.3. IOAPICARB—IOAPIC ARBITRATION REGISTER............................................................................10 3.2.4. IOREDTBL[23:0]—I/O REDIRECTION TABLE REGISTERS............................................................11 4.0. FUNCTIONAL DESCRIPTION......................................................................................................................14 4.1. INTIN23/SMI# and SMIOUT# Functionality................................................................................................14 5.0. PINOUT AND PACKAGE SPECIFICATIONS..............................................................................................15 5.1. Pinout Specifications...................................................................................................................................15 5.2. Package Specifications...............................................................................................................................17 6.0. TESTABILITY.................................................................................................................................................18 6.1. Tri-State Of All Output Pins.........................................................................................................................18 6.2. Drive 1’s to all the output pins.....................................................................................................................18 6.3. Drive 0’s to all the output pins.....................................................................................................................19 6.4. NAND Tree.................................................................................................................................................19 2 PRELIMINARY E 82093AA (IOAPIC) 1.0. OVERVIEW While the standard ISA Compatible interrupt controller (located in the PIIX3) is intended for use in a uni- processor system, the I/O Advanced Programmable Interrupt Controller (IOAPIC) can be used in either a uni- processor or multi-processor system. The IOAPIC provides multi-processor interrupt management and incorporates both static and dynamic symmetric interrupt distribution across all processors. In systems with multiple I/O subsystems, each subsystem can have its own set of interrupts. In a uni-processor system, the IOAPIC's dedicated interrupt bus can reduce interrupt latency over the standard interrupt controller (i.e., the latency associated with the propagation of the interrupt acknowledge cycle across multiple busses using the standard interrupt controller approach). Interrupts can be controlled by the standard ISA Compatible interrupt controller in the PIIX3, the IOAPIC unit, or mixed mode where both the standard ISA Compatible Interrupt Controller and IOAPIC are used. The selection of which controller responds to an interrupt is determined by how the interrupt controllers are programmed. Note that it is the programmer's responsibility to make sure that the same interrupt input signal is not handled by both interrupt controllers. At the system level, APIC consists of two parts (Figure 2.0)—one residing in the I/O subsystem (called the IOAPIC) and the other in the CPU (called the Local APIC). The local APIC and the IOAPIC communicate over a dedicated APIC bus. The IOAPIC bus interface consists of two bi-directional data signals (APICD[1:0]) and a clock input (APICCLK). The CPU's Local APIC Unit contains the necessary intelligence to determine whether or not its processor should accept interrupts broadcast on the APIC bus. The Local Unit also provides local pending of interrupts, nesting and masking of interrupts, and handles all interactions with its local processor (e.g., the INTR/INTA/EOI protocol). The Local Unit further provides inter-processor interrupts and a timer, to its local processor. The register level interface of a processor to its local APIC is identical for every processor. The IOAPIC Unit consists of a set of interrupt input signals, a 24-entry by 64-bit Interrupt Redirection Table, programmable registers, and a message unit for sending and receiving APIC messages over the APIC bus. I/O devices inject interrupts into the system by asserting one of the interrupt lines to the IOAPIC. The IOAPIC selects the corresponding entry in the Redirection Table and uses the information in that entry to format an interrupt request message. Each entry in the Redirection Table can be individually programmed to indicate edge/level sensitive interrupt signals, the interrupt vector and priority, the destination processor, and how the processor is selected (statically or dynamically). The information in the table is used to transmit a message to other APIC units (via the APIC bus). The IOAPIC contains a set of programmable registers. Two of the registers (I/O Register Select and I/O Window Registers) are located in the CPU's memory space and are used to indirectly access the other APIC registers as described in Section 3.0, Register Description. The Version Register provides the implementation version of the IOAPIC. The IOAPIC ID Register is programmed with an ID value that serves as a physical name of the IOAPIC. This ID is loaded into the ARB ID Register when the IOAPIC ID Register is written and is used during bus arbitration. NOTE The interrupt number or the vector does not imply a particular priority for being sent. The IOAPIC continually polls the 24 interrupts in a rotating fashion, one at a time. The pending interrupt polled first is the one sent. PRELIMINARY 3 E 82093AA (IOAPIC) Processor Processor Local APIC RESET RESET Local APIC LINTIN0 LINTIN1 SMI# LINTIN0 LINTIN1 SMI# NMI LINTIN1 LINTIN0 SMI RESET Host-to-PCI Bridge APIC Bus APICACK2# RESET PCI Bus SMIOUT# CS# I/O APIC Unit APICREQ# APICACK1# PIIX3 INTIN23/SMI# INTIN[2,13,22] INTR MIRQ[1:0] IRQ[1,2:7,8#,9:12,14,15] MIRQ[1:0] ISA Bus APIC_SYS Figure 2. I/O And Local APIC Units 4 PRELIMINARY E 82093AA (IOAPIC) 2.0. SIGNAL DESCRIPTION This section contains a detailed description of each signal. The signals are arranged in function groups according to their interface. Note that the “#” symbol at the end of a signal name indicates that the active, or asserted state occurs when the signal is at a low voltage level. When “#” is not present after the signal name, the signal is asserted when at the high voltage level. The terms' assertion and negation are used extensively. This is done to avoid confusion when working with a mixture of ‘active-low’ and ‘active-high’ signals. The term assert, or assertion indicates that a signal is active, independent of whether that level is represented by a high or low voltage. The term negate, or negation indicates that a signal is inactive. The following notations are used to describe the signal and type: I Input pin O Output pin ST Schmitt Trigger Input pin OD Open Drain Output pin. This requires a pull-up to the VCC of the processor core I/OD Bi-directional Input withOpen Drain Output pin. I/O Bi-directional Input/Output pin 2.1. System Bus Signals Signal Name Type Description D[7:0] I/O DATA: D[7:0] contain the data when writing to or reading from internal IOAPIC registers. These signals are outputs when reading data from the IOAPIC and they are inputs when writing data to the IOAPIC. These signals are tri-stated during reset. D/I# I DATA/INDEX#: This input selects whether the I/O Register Select (IOREGSEL) Register or I/O Window (IOWIN) Register is accessed. All internal IOAPIC registers are accessed with an indexing scheme. When the D/I# pin is low, the IOREGSEL Register is accessed. When the D/I# pin is high, the data becomes available from the register pointed to by the index register. Typically, this signal is connected to SA4 on the ISA bus (i.e., IOREGSEL Register is at 00h and IOWIN Register is at 10h). A[1:0] I ADDRESS: The IOAPIC is a 32 bit device with an 8 bit ISA interface. A[1:0] steer the data byte to the correct 8 bit location within the 32 bit register. Typically, these input signals are connected to SA[1:0] of the ISA bus. RD# I READ STROBE: RD# causes the IOAPIC to respond by driving internal register data onto the D[7:0] pins. Typically this pin is connected to the MEMRD# signal on the ISA bus. WR# I WRITE STROBE: When this signal transitions from low to high, the data present on the IOAPIC’s D[7:0] signals are written to an internal register. Typically, this signal is connected to the MEMWR# signal on the ISA bus. CS# I CHIP SELECT: This active low input selects the IOAPIC as the target of the current read or write transaction. PRELIMINARY 5 E 82093AA (IOAPIC) Signal Name Type Description APICREQ# O APIC REQUEST: APICREQ# is asserted prior to the APIC sending an interrupt message over the APIC data bus. This is the request part of a handshake that insures system level buffer coherency prior to sending an interrupt over the APIC bus. This signal is tri-stated during reset. This signal has an internal pull-up resistor. APICACK1# I APIC ACKNOWLEDGE 1: This signal is the acknowledge part of the handshake indicating that the APIC can send the interrupt message over the APIC bus. This signal is typically connected to the PIIX3. APICACK2# I APIC ACKNOWLEDGE 2: This signal is the second half of the acknowledge handshake indicating that the APIC can send the interrupt message over the APIC bus. This signal is typically connected to the host-to-PCI bridge and along with APICREQ# and APICACK1# makes up the complete buffer coherency protocol cycles. If the system does not have a host-to-PCI bridge, this signal can be tied low. 2.2. Clock and Reset Signals Signal Name Type Description PCICLK I PCI CLOCK: This signal is used to synchronize and strobe the data buffer status signals (APICREQ#, APICACK1#, and APICACK2#). This signal is typically connect to the PCI clock. RESET I RESET: RESET initializes the IOAPIC’s internal logic and sets the register bits to their default value. 2.3. APIC Bus Interface Signal Name Type Description APICD[1:0] I/OD APIC DATA: These signals are used to send and receive data over the APIC bus. These signals are tri-stated during reset and must be pulled up to the appropriate VCC levels of the CPU. APICCLK I APIC CLOCK: The input signal is used to determine when valid data is being sent over the APIC bus. 2.4. Interrupt Signals Signal Name Type Description INTIN0 ST Interrupt Input 0: This signal is connected to the redirection table entry 0. Typically, this signal may be connected to the INTR on the PIIX3 to communicate the status of IRQ0 and IRQ13 interrupts. Note that the IRQ0 and IRQ13 interrupts are embedded in the PIIX3 and are not available to the rest of the system. INTIN1 ST Interrupt Input 1: INTIN1 is connected to the redirection table entry 1. Typically, this signal will be connected to the keyboard interrupt (IRQ1). 6 PRELIMINARY E 82093AA (IOAPIC) Signal Name Type Description INTIN2 ST Interrupt Input 2: This signal is connected to the redirection table entry 2. If IRQ0 interrupt is available in hardware, it is connected to this pin. INTIN[3:11, ST Interrupt Inputs 3 through 11, 14 and 15: These signals are connected to 14,15] the redirection table entries 3:11, 14 & 15. Typically, these signals are connected to the ISA interrupts IRQ[3:7,8#,9:11,14:15] respectively. INTIN12 ST Interrupt Input 12: This signal is connected to the redirection table entry 12. Typically, this signal will be connected to the mouse interrupt (IRQ12/M). INTIN13 ST Interrupt input 13: This signal is connected to the redirection table entry 13. If IRQ13 interrupt is available in hardware, it is connected to this signal. If IRQ13 is not available, it is routed through the INTR interrupt and this signal becomes INTIN13 (redirection table entry 13). INTIN[16:19] ST Interrupt inputs 16 through 19: These signals are connected to the redirection table entries [16:19]. Typically, these signals are connected to the PCI interrupts (PIRQ[0:3]). The steering of the PCI IRQs to the ISA IRQs is accomplished in the IOAPIC by setting the PCI redirection table entry to the correct ISA interrupt vector. INTIN[20:21] ST Interrupt inputs 20 and 21: These signals are connected to the redirection table entries 20 and 21. Typically, these signals are connected to the motherboard interrupts (MIRQ[0:1]). These pins could be used for the NMI and INIT signals or just general purpose interrupts. INTIN22 ST Interrupt input 22: This signal is connect to the redirection table entry 22. This signal is a general purpose interrupt. INTIN23/ ST Interrupt input 23: This signal is connected to the redirection table entry 23. SMI# This input has a special feature for the SMI# interrupt routing. If the Mask bit is not set, the signal is a normal interrupt input that is sent over the APIC bus just like all the other interrupts. When the Mask bit is set, the INTIN23/SMI# input is routed through the IOAPIC to the SMIOUT# output signal. SMIOUT# OD SMI OUTPUT: This signal is an output in response to the SMI# input when the MASK bit for the redirection table entry number 23 is set. If the MASK bit is not set, the redirection table can be setup to deliver an SMI# over the APIC bus. 2.5. Test and Power Signals Pin Name Type Description TESTIN# I TEST INPUT: This active-low input is used to invoke test modes. TESTIN# should be pulled high during normal operation. VCC VCC POWER PIN: 5V – 10%. GND GROUND POWER PIN: PRELIMINARY 7 E 82093AA (IOAPIC) 3.0. REGISTER DESCRIPTION The IOAPIC is addressed with a CS# and the D/I# pin. The PIIX3 decodes the IOAPIC in memory space and sends a CS# to the IOAPIC device, when it is selected. The D/I# pin selects between the IOREGSEL Register (D/I#=0) and the IOWIN Register (D/I#=1). Typically, D/I# is connected to SA4 on the ISA bus (i.e., IOREGSEL Register is at 00h and IOWIN Register is at 10h). The IOAPIC registers are accessed by an indirect addressing scheme using two registers (IOREGSEL and IOWIN) that are located in the CPU's memory space (memory address specified by the APICBASE Register located in the PIIX3). These two registers are re-locateable (via the APICBASE Register) as shown in Table 3.1. In the IOAPIC only the IOREGSEL and IOWIN Registers are directly accesable in the memory address space. To reference an IOAPIC register, a byte memory write that the PIIX3 decodes for the IOAPIC loads the IOREGSEL Register with an 8-bit value that specifies the IOAPIC register (address offset in Table 3.2) to be accessed. The IOWIN Register is then used to read/write the desired data from/to the IOAPIC register specified by bits [7:0] of the IOREGSEL Register. The IOWIN Register must be accessed as a Dword quantity. The IOREGSEL and IOWIN Registers (Table 3.1) can be relocated via the APIC Base Address Relocation Register in the PIIX3 and are aligned on 128 bit boundaries. All APIC registers are accessed using 32 bit loads and stores. This implies that to modify a field (e.g., bit, byte) in any register, the whole 32 bit register must be read, the field modified, and the 32 bits written back. In addition, registers that are described as 64 bits wide are accessed as multiple independent 32 bit registers. Table 1. Memory Mapped Registers For Accessing IOAPIC Registers Memory Address Mnemonic Register Name Access D/I# SIgnal FEC0 xy00h IOREGSEL I/O Register Select (index) R/W 0 FEC0 xy10h IOWIN I/O Window (data) R/W 1 NOTES: xy are determined by the x and y fields in the APIC Base Address Relocation Register located in the PIIX3. Range for x = 0-Fh and the range for y = 0,4,8,Ch. Table 2. IOAPIC Registers Address Offset Mnemonic Register Name Access 00h IOAPICID IOAPIC ID R/W 01h IOAPICVER IOAPIC Version RO 02h IOAPICARB IOAPIC Arbitration ID RO 10- 3Fh IOREDTBL[0:23] Redirection Table (Entries 0-23) (64 bits each) R/W NOTES: Address Offset is determined by I/O Register Select Bits [7:0]. 8 PRELIMINARY E 82093AA (IOAPIC) 3.1. Memory Mapped Registers for Accessing IOAPIC Registers 3.1.1. IOREGSEL—I/O REGISTER SELECT REGISTER Memory Address: FEC0 xy00h (xy=See APICBASE Register in the PIIX3) Default Value: 00h Attribute: Read/Write This register selects the IOAPIC Register to be read/written. The data is then read from or written to the selected register through the IOWIN Register. Bit Description 31:8 Reserved. 7:0 APIC Register Address—R/W. Bits [7:0] specify the IOAPIC register to be read/written via the IOWIN Register. 3.1.2. IOWIN—I/O WINDOW REGISTER Memory Address: FEC0 xy10h (xy=See APICBASE Register in PIIX3) Default Value: 00h Attribute: Read/Write This register is used to write to and read from the register selected by the IOREGSEL Register. Readability/writability is determined by the IOAPIC register that is currently selected. Bit Description 31:0 APIC Register Data—R/W. Memory references to this register are mapped to the APIC register specified by the contents of the IOREGSEL Register. 3.2. IOAPIC Registers 3.2.1. IOAPICID—IOAPIC IDENTIFICATION REGISTER Address Offset: 00h Default Value: 00h Attribute: Read/Write This register contains the 4-bit APIC ID. The ID serves as a physical name of the IOAPIC. All APIC devices using the APIC bus should have a unique APIC ID. The APIC bus arbitration ID for the I/O unit is also writtten during a write to the APICID Register (same data is loaded into both). This register must be programmed with the correct ID value before using the IOAPIC for message transmission. Bit Description 31:28 Reserved. 27:24 IOAPIC Identification—R/W. This 4 bit field contains the IOAPIC identification. 23:0 Reserved. PRELIMINARY 9 E 82093AA (IOAPIC) 3.2.2. IOAPICVER—IOAPIC VERSION REGISTER Address Offset: 01h Default Value: 00170011h Attribute: Read Only The IOAPIC Version Register identifies the APIC hardware version. Software can use this to provide compatibility between different APIC implementations and their versions. In addition, this register provides the maximum number of entries in the I/O Redirection Table. Bit Descriptions 31:24 Reserved. 23:16 Maximum Redirection Entry—RO. This field contains the entry number (0 being the lowest entry) of the highest entry in the I/O Redirection Table. The value is equal to the number of interrupt input pins for the IOAPIC minus one. The range of values is 0 through 239. For this IOAPIC, the value is 17h. 15:8 Reserved. 7:0 APIC VERSION—RO. This 8 bit field identifies the implementation version. The version number assigned to the IOAPIC is 11h. 3.2.3. IOAPICARB—IOAPIC ARBITRATION REGISTER Address Offset: 02h Default Value: 0000_0000h Attribute: Read Only The APICARB Register contains the bus arbitration priority for the IOAPIC. This register is loaded when the IOAPIC ID Register is written. The APIC uses a one wire arbitration to win bus ownership. A rotating priority scheme is used for arbitration. The winner of the arbitration becomes the lowest priority agent and assumes an arbitration ID of 0. All other agents, except the agent whose arbitration ID is 15, increment their arbitration IDs by one. The agent whose ID was 15 takes the winner's arbitration ID and increments it by one. Arbitration IDs are changed (incremented or asssumed) only for messages that are transmitted successfully (except, in the case of low priority messages where Arbitration ID is changed even if message was not successfully transmitted). A message is transmitted successfully if no checksum error or acceptance error is reported for that message. The APICARB Register is always loaded with IOAPIC ID during a "level triggered INIT with de-assert" message. Bit Description 31:28 Reserved. 27:24 IOAPIC Identification—R/W. This 4 bit field contains the IOAPIC Arbitration ID. 23:0 Reserved. 10 PRELIMINARY