CHRP ISA Interrupt Controller Device Binding
CHRP(TM) ISA Interrupt Controller
Device Binding to
IEEE 1275-1994
Standard for Boot (Initialization,
Configuration) Firmware
Revision: 1.1 Unapproved DRAFT
August 19,1996
Table of Contents
This document specifies the application of Open Firmware to the PowerPC Common Hardware Reference Platform (CHRPTM) ISA interrupt controller, including device-specific requirements and practices for initialization, properties, and methods. This device shall be a child of an ISA or EISA Bus Node.
Revision 1.0 Unapproved DRAFT May 21, 1996 Initial revision. Jordan Brown, Sunsoft and John Kingman, IBM editors
Revision 1.1 Unapproved DRAFT August 19, 1996 Added "reserved-interrupts" property.
This Open Firmware System binding standard shall be used in conjunction with the following publications. When the following standards are superseded by an approved revision, the revision shall apply.
- [1]
- IEEE Std 1275-1994 Standard for Boot (Initialization, Configuration) Firmware, Core Practices and Requirements.
- [2]
- Core Errata, IEEE P1275.7/D4.
- [3]
- ISA/EISA/ISA-PnP binding to: IEEE Std 1275-1994, Standard for Boot (Initialization, Configuration) Firmware.
- [4]
- PowerPC Microprocessor Common Hardware Reference Platform: I/O Device Reference. This document describes the PowerPC Common Hardware Reference Platform (CHRPTM) System Standard I/O Devices; hardware registers, register locations, and hardware attributes.
- [5]
- Open Firmware Recommended Practice: Interrupt Mapping.
- [6]
- Open Firmware Recommended Practice: Generic Names.
- [7]
- PowerPC Microprocessor Common Hardware Reference Platform binding to: IEEE Std 1275-1994, Standard for Boot (Initialization, Configuration) Firmware.
EISA: Extended Industry Standard Architecture
ISA: Industry Standard Architecture
The ISA interrupt controller is essentially a set of two cascaded 8259 interrupt controllers. Their interrupt lines may be set as edge or level sensitive.
None.
As specified in [1], [3] and [7], with the following additions or modifications.
"name" S
Standard property name, specifies the generic name of the device.
The meaning of this property is as defined in Open Firmware core document [1], as modified by the Generic Names Recommended Practice [6]. The value for nodes described by this specification shall be "interrupt-controller".
"device_type" S
Standard property name to define the device's implemented interface.
The meaning of this property is as defined in the Open Firmware core document [1]. The value for nodes described by this specification shall be "interrupt-controller".
"compatible" S
Standard property name, specifies device names with which this device is compatible.
The meaning of this property is as defined in Open Firmware, as modified by the Generic Names Recommended Practice [6]. As described in those documents, the entries are a list of device names with which this device is compatible, starting with the name of the device itself and progressing through successively less precise and possibly less functional compatible devices.
The compatible property shall include "chrp,iic."
Additional entries may be supplied, at their appropriate position in the list, to describe devices with which this device is compatible.
"reg" S
Standard property name to define the package's registers.
The meaning of this property is as defined in the Open Firmware core document [1]. It describes the device's register set. The values which shall be assigned to this property are explained in the ISA/EISA/ISA-PnP binding[3] and the I/O Device Reference[4]
"reserved-interrupts" S
Standard property name to define reserved interrupts.
prop-encoded-array: An integer array, encoded with encode-int.
The value of this property shall be a list of ISA interrupts which cannot be assigned due to cascading, wiring, or other reasons. Only the irq# part of the property is pertinent to this use.
None.
As specified in [1] and [3], without addition or modification.
As specified in [1] and [3], without addition or modification.
None.
None.
None.
For devices not selected as Open Firmware's "console input device" or "console output device" device, most of the initial state is typically undefined. This device shall have all interrupts disabled when the client is started.
Refer to [4] for more information on the state of this device when the client is started.
For devices not selected as Open Firmware's "console input device" or "console output device" device, there is no requirement. Typically, this device is unsuitable for use as an Open Firmware console input or console output device.