English
Language : 

82371AB Datasheet, PDF (205/284 Pages) Intel Corporation – PCI-TO-ISA / IDE XCELERATOR PIIX4
E
82371AB (PIIX4)
synthesizer. The Host clocks stop running in this state. The processor does not snoop host bus cycles and
system designers must ensure that no host cycles to main memory are executed by other system masters. To
exit this state, PIIX4 negates the CPU_STP# signal. Again, PIIX4 loads the Fast Burst Timer with the
[CPU_LCK] value and count down allowing time for the processor PLL to lock. After the timer expires, PIIX4
negates
the
SUS_STAT1#
signal,
the
SLP#
signal,
and
ZZ
signal
(if applicable), and STP_CLK#.
System Throttle Control: If the system has been placed into the Stop Grant or Quick Start states and
[THT_EN] bit is set, PIIX4 toggles the STPCLK# signal and ZZ signal (if [ZZ_EN] set) with a period of 244 µs
(approximately eight 32-kHz clock periods) and a programmable duty cycle. This system toggles between full-
speed operation and the Stop Grant or Quick Start state. The duty cycle can be set in 12.5% increments by
programming the [THTL_DTY] bits in the Processor Control (P_CNTRL) register. This emulates a reduced
frequency Host clock, resulting in associated power savings.
Thermal Throttle Control: If the THRM# signal is asserted for greater than 2 seconds and the system is not in
a Stop Clock, Sleep, or Deep Sleep state, PIIX4 automatically starts toggling the STPCLK# signal and ZZ signal
(if [ZZ_EN] set) with a period of 244 µs and a programmable Duty Cycle. This system toggles between full-
speed operation and the Stop Grant State. The Duty Cycle can be set in 12.5% increments by programming the
[THRM_DTY] bits in the Count B (CNTB) register. The functionality of thermal throttling is independent of
[THRM_EN] bit, which is used to enable events for other power management functions. The [THRM_DTY] field
must be programmed by the BIOS. This emulates a reduced frequency Host clock, resulting in reduced power
and thermal output. When the THRM# signal is negated, the system returns to clock control previously in use.
Stop Break and Burst Execution: Once the hardware has been placed into a clock control state, it can be
restored to full operation by system hardware or software. Software can restore the system to full operation by
clearing the [CC_EN] bit. Hardware events can be enabled to return the system to a non-clock controlled
condition. If the [BRST_EN] bit is reset, these events are called Stop Break Events. Alternatively, if the
[BRST_EN] bit is set, these events are called Burst Events.
Stop Break events completely return the system to non-clock controlled state. To restore clock control, software
must set the desired clock control configuration and again perform a read from LVL2 or LVL3 registers to initiate
the control.
Burst events cause the reload of a Burst timer, which begins to count down from its loaded value. While the timer
is counting, the system returns to full clock operation. Once the burst timer expires, the system automatically
returns to the clock controlled state. PIIX4 provides two different burst timers, a fast burst timer (which generates
a short count) and a slow burst timer (which generates a longer count).
Care must be taken before placing the system into a LVL2 or LVL3 state when the [BRST_EN] bit is set. Prior to
LVL2 or LVL3 register read, software must ensure that no external burst events are active and only
Device 3 idle timer should be enabled as a burst event. The Device 3 idle timer is then enabled with all reload
events disabled. The LVL2 or LVL3 register read is performed placing the system into a LVL2 or LVL3 clock
control condition. The Device 3 idle timer will then generate a burst event upon expiration. During this first burst,
the desired burst events are then enabled. Failure to follow this procedure may cause the PIIX4 to miss LVL2 or
LVL3 register reads.
The thermal throttle state is not affected by [CC_EN] bit settings, nor are any hardware Stop Break or Burst
events.
Stop Break events are the logical “OR” of Fast Burst and Slow Burst Events. If the [BRST_EN] bit is high, the
Burst events reload their associated burst timer. When the [BRST_EN] bit is low, these events generate
a Stop Break event. The Fast Burst and Slow Burst timer and burst event programming information is
shown on next page.
PRELIMINARY
205
4/9/97 2:23 PM PIIX4aDS
INTEL CONFIDENTIAL
(until publication date)