![](http://datasheet.mmic.net.cn/100000/IBM21P100BGC_datasheet_3492192/IBM21P100BGC_99.png)
IBM21P100BGC
IBM 133 PCI-X Bridge R2.0
ppb20_clock_reset.fm.01
October 15, 2001
Clocking and Reset
6. Clocking and Reset
This section explains the clocking requirements and reset functions of the IBM 133 PCI-X Bridge R2.0.
6.1 Clocking Domains
The IBM 133 PCI-X Bridge R2.0 has two clocking domains, one for the primary interface and one for the
secondary interface. Each interface has its own clock input pin. The primary interface is controlled by the
P_CLK input. The secondary interface and the internal arbiter are controlled by the S_CLK input. The bridge
does not supply the clocks on either interface. The two bus clocks may be run synchronously or asynchro-
nously to one another. The two clock frequencies are independent of each other and each may have any
value allowed by the PCI/PCI-X bus architectures. A spread spectrum clock input is supported for either or
both interfaces within the architectural bounds.
The bridge contains a separate internal phase-locked loop (PLL) circuit for each clocking domain. The PLL for
each interface is employed when its bus is running in the PCI-X mode, as determined by the bus initialization
process described below. When either bus is running in the PCI mode, the respective PLL is bypassed to
allow for any clock frequency from zero to 66 MHz.
6.2 Clock Jitter
Clock jitter is defined as the relationship of one clock edge to a subsequent clock edge, measured at the
same point. If these two edges are separated by one clock cycle, it is called cycle-to-cycle or short term jitter.
If they are separated by hundreds or thousands of cycles, it is called long term jitter. As specified in
long term jitter on each of its clock inputs. Clock jitter introduced by the internal PLLs of the bridge is
accounted for within this maximum specification.
Careful design of the clock generation circuitry is an important factor in determining the speed of the bus. As
indicated in the PCI and PCI-X architectures, all sources of clock jitter must be considered when determining
the bus clock frequency. The minimum and maximum clock period specifications must not be violated for any
single clock cycle. The system clock output period, including all sources of clock period variation such as jitter
and component tolerances, must always be within the minimum and maximum limits defined for the mode in
which the bus is configured. For example, if a specific system clock design has a maximum clock period vari-
ation of 180 ps, then the nominal clock period for the PCI-X 133 range needs to be at least 7.68ns (7.5ns +
0.180ns), making the maximum frequency allowed for this case is just over 130 MHz.
6.3 Mode and Clock Frequency Determination
As explained in Sections 6.2 and 8.9 of the
PCI-X Addendum to the PCI Local Bus Specification, the mode
and frequency range of each bus is determined by the values on its M66EN and PCIXCAP signals when the
bus reset signal is active. Each bus client is then informed of the determination via an initialization pattern that
is broadcast at the de-assertion or rising edge of the reset signal. This process is accomplished on the
secondary interface differently than on the primary interface, due to architectural requirements for PCI-X
bridges. The details for each are given below.