Integrated Device Technology, Inc. reserves the right to make changes to its products or specifications at any time, without notice, in order to improve design or performance
and to supply the best possible product. IDT does not assume any responsibility for use of any circuitry described other than the circuitry embodied in an IDT product. The
Company makes no representations that circuitry described herein is free from patent infringement or other rights of third parties which may result from its use. No license is
granted by implication or otherwise under any patent, patent rights or other rights, of Integrated Device Technology, Inc.
GENERAL DISCLAIMER
Code examples provided by IDT are for illustrative purposes only and should not be relied upon for developing applications. Any use of the code examples below is completely
at your own risk. IDT MAKES NO REPRESENT ATIONS OR WARRANTIES OF ANY KIND CONCERNING THE NONINFRINGEMENT, QUALITY, SAFETY OR SUITABILITY
OF THE CODE, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. FURTHER, IDT MAKES NO REPRESENT ATIONS OR WARRANTIES AS TO THE TRUTH, ACCURACY OR COMPLETENESS
OF ANY STATEMENTS, INFORMATION OR MATERIALS CONCERNING CODE EXAMPLES CONTAINED IN ANY IDT PUBLICATION OR PUBLIC DISCLOSURE OR
THAT IS CONTAINED ON ANY IDT INTERNET SITE. IN NO EVENT WILL IDT BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, I NCIDENTAL, INDIRECT, PUNITIVE OR
SPECIAL DAMAGES, HOWEVER THEY MAY ARIS E, AND EVEN IF IDT HAS BEEN PREVIOUSLY ADVISED ABOUT THE POSSIBILITY OF SUCH DAMAGES. The code
examples also may be subject to United States export control laws and may be subject to the export or import laws of other countries and it is your responsibility to comply with
any applicable laws or regulations.
Integrated Device Technology's products are not authorized for use as critical components in life support devices or systems unless a specific written agreement pertaining to
such intended use is executed between the manufacturer and an officer of IDT.
1. Life support devices or systems are devices or systems which (a) are intended for surgical implant into the body or (b) support or sustain life and whose failure to perform,
when properly used in accordance with instructions for use provided in the labeling, can be reasonably expected to result in a significant injury to the user.
2. A critical component is any components of a life support device or system whose failure to perform can be reasonably expected to cause the failure of the life support device
or system, or to affect its safety or effectiveness.
IDT, the IDT logo, and Integrated Device Technology are trademarks or registered trademarks of Integrated Device Technology, Inc.
CODE DISCLAIMER
LIFE SUPPORT POLICY
Page 3
About this Manual
®
Notes
Introduction
This user manual includes hardware and software information on the 89HPES5T5, a member of IDT’s
PRECISE™ family of PCI Express® switching solutions offering the next-generation I/O interconnect standard.
Finding Additional Information
Information not included in this manual such as mechanicals, package pin-outs, and electrical characteristics can be found in the data sheet for this device, which is available from the IDT website (www.idt.com)
as well as through your local IDT sales representative.
Content Summary
Chapter 1, “PES5T5 Device Overview,” provides a complete introduction to the performance capabilities of the 89HPES5T5. Included in this chapter is a summary of features for the device as well as a system
block diagram and pin description.
Chapter 2, “Clocking, Reset, and Initialization,” provides a description of the two differential reference clock inputs that are used internally to generate all of the clocks required by the internal switch logic
and the SerDes.
Chapter 3, “Theory of Operation,” describes the operation of the link feature including polarity inversion, link width negotiation, and lane reversal.
Chapter 4, “Link Operation,” describes the operation of the link feature including polarity inversion,
link width negotiation, and lane reversal.
Chapter 5, “General Purpose I/O,” describes how the 16 General Purpose I/O (GPIO) pins may be
individually configured as general purpose inputs, general purpose outputs, or alternate functions.
Chapter 6, “SMBus Interfaces,” describes the operation of the 2 SMBus interfaces on the PES5T5.
Chapter 7, “Power Management,” describes the power management capability structure located in the
configuration space of each PCI-PCI bridge in the PES5T5.
Chapter 8, “Hot-Plug and Hot-Swap,” describes the behavior of the hot-plug and hot-swap features in
the PES5T5.
Chapter 9, “Configuration Registers,” discusses the base addresses, PCI configuration space, and
registers associated with the PES5T5.
Chapter 10, “JTAG Boundary Scan,” discusses an enhanced JTAG interface, including a system logic
TAP controller, signal definitions, a test data register, an instruction register, and usage considerations.
Signal Nomenclature
To avoid confusion when dealing with a mixture of “active-low” and “active-high” signals, the terms
assertion and negation are used. The term assert or assertion is used to indicate that a signal is active or
true, independent of whether that level is represented by a high or low voltage. The term negate or negation
is used to indicate that a signal is inactive or false.
To define the active polarity of a signal, a suffix will be used. Signals ending with an ‘N’ should be interpreted as being active, or asserted, when at a logic zero (low) level. All other signals (including clocks,
buses and select lines) will be interpreted as being active, or asserted when at a logic one (high) level.
PES5T5 User Manual 1January 28, 2011
Page 4
IDT
Notes
To define buses, the most significant bit (MSB) will be on the left and least significant bit (LSB) will be on
the right. No leading zeros will be included.
Throughout this manual, when describing signal transitions, the following terminology is used. Rising
edge indicates a low-to-high (0 to 1) transition. Falling edge indicates a high-to-low (1 to 0) transition. These
terms are illustrated in Figure 1.
single clock cycle
1234
high-to-low
transition
low-to-high
transition
Figure 1 Signal Transitions
Numeric Representations
To represent numerical values, either decimal, binary, or hexadecimal formats will be used. The binary
format is as follows: 0bDDD, where “D” represents either 0 or 1; the hexadecimal format is as follows:
0xDD, where “D” represents the hexadecimal digit(s); otherwise, it is decimal.
The compressed notation ABC[x|y|z]D refers to ABCxD, ABCyD, and ABCzD.
The compressed notation ABC[x:y]D refers to ABCxD, ABC(x+1)D, ABC(x+2)D,... ABCyD if x < y or to
ABCxD, ABC(x-1)D, ABC(x-2)D,... ABCyD if x > y.
Data Units
The following data unit terminology is used in this document.
In quadwords, bit 63 is always the most significant bit and bit 0 is the least significant bit. In doublewords, bit 31 is always the most significant bit and bit 0 is the least significant bit. In words, bit 15 is always
the most significant bit and bit 0 is the least significant bit. In bytes, bit 7 is always the most significant bit
and bit 0 is the least significant bit.
The ordering of bytes within words is referred to as either “big endian” or “little endian.” Big endian
systems label byte zero as the most significant (leftmost) byte of a word. Little endian systems label byte
zero as the least significant (rightmost) byte of a word.
PES5T5 User Manual 2January 28, 2011
Page 5
IDT
Notes
bit 0bit 31
0123
Address of Bytes within Words: Big Endian
bit 0bit 31
3210
Address of Bytes within Words: Little Endian
Table 2 Example of Byte Ordering for “Big Endian” or “Little Endian” System Definition
Register Terminology
Note: Software in the context of this register terminology refers to modifications made by PCIe
root configuration writes to registers made through the slave SMBus interface, or serial EEPROM
register initialization.
TypeAbbreviationDescription
Hardware InitializedHWINITRegister bits are initialized by firmware or hardware mecha-
nisms such as pin strapping or serial EEPROM. (System firmware hardware initialization is only allowed for system
integrated devices.) Bits are read-only after initialization and can
only be reset (for write-once by firmware) with reset.
Read Only and ClearRCSoftware can read the register/bits with this attribute. Reading
the value will automatically cause the register/bit to be reset to
zero. Writing to a RC location has no effect.
Read Clear and WriteRCWSoftware can read the register/bits with this attribute. Reading
the value will automatically cause the register/bits to be reset to
zero. Writes cause the register/bits to be modified.
ReservedReservedThe value read from a reserved register/bit is undefined. Thus,
software must deal correctly with fields that are reserved. On
reads, software must use appropriate masks to extract the
defined bits and not rely on reserved bits being any particular
value. On writes, software must ensure that the values of
reserved bit positions are preserved. That is, the values of
reserved bit positions must first be read, merged with the new
values for other bit positions and then written back.
Read OnlyROSoftware can only read registers/bits with this attribute. Con-
tents are hardwired to a constant value or are status bits that
may be set and cleared by hardware. Writing to a RO location
has no effect.
Read and WriteRWSoftware can both read and write bits with this attribute.
Table 3 Register Terminology (Sheet 1 of 2)
PES5T5 User Manual3January 28, 2011
Page 6
IDT
Notes
TypeAbbreviationDescription
Read and Write ClearRW1CSoftware can read and write to registers/bits with this attribute.
However, writing a value of zero to a bit with this attribute has no
effect. A RW1C bit can only be set to a value of 1 by a hardware
event. To clear a RW1C bit (i.e., change its value to zero) a
value of one must be written to the location. An RW1C bit is
never cleared by hardware.
Read and Write when
Unlocked
Read Only StickyROSRegisters are read-only and cannot be altered by software. Reg-
Read and Write StickyRWSRegisters are read-write and may be either set or cleared by
RWLSoftware can read the register/bits with this attribute. Writing to
register/bits with this attribute will only cause the value to be
modified if the REGUNLOCK bit in the SWCNTL register is set.
When the REGUNLOCK bit is cleared, writes are ignored and
the register/bits are effectively read-only.
These registers are Sticky as they are preserved across a hot
reset. These bits are not preserved during fundamental reset.
isters are not initialized or modified by hot reset.
When device consumes AUX power, some of these bits maintain their value across fundamental reset and are marked
FRSticky.
software to the desired state. Bits are not initialized or modified
by hot reset.
When device consumes AUX power, some of these bits maintain their value across fundamental reset and are marked
FRSticky.
Read Write-1-to-Clear
Sticky
Write TransientWTThe zero is always read from a bit/field of this type. Writing of a
ZeroZeroA zero register or bit must be written with a value of zero and
RWICSRegisters indicate status when read, a set bit indicating a status
event may be cleared by writing a 1. Writing a 0 to RW1CS bits
has no effect. Bits are not initialized or modified by hot reset.
When device consumes AUX power, some of these bits maintain their value across fundamental reset and are marked
FRSticky.
one is used to qualify the writing of other bits/fields in the same
register.
returns a value of zero when read.
Table 3 Register Terminology (Sheet 2 of 2)
Use of Hypertext
In Chapter 9, Tables 9.2 and 9.3 contain register names and page numbers highlighted in blue under the
Register Definition column. In pdf files, users can jump from this source table directly to the registers by
clicking on the register name in the source table. Each register name in the table is linked directly to the
appropriate register in the register section of the chapter. To return to the source table after having jumped
to the register section, click on the same register name (in blue) in the register section.
Reference Documents
PCI Express Base Specification, Revision 1.1, PCI Special Interest Group.
PCI Power Management Interface Specification, Revision 1.2, PCI Special Interest Group.
PCI to PCI Bridge Architecture Specification, Revision 1.2, PCI Special Interest Group.
SMBus Specification, Revision 2.0.
PES5T5 User Manual 4January 28, 2011
Page 7
IDT
Notes
Revision History
June 5, 2007: Initial Publication.
July 11, 2007: Corrected AERUCS to AERUES in AERCTL register, Chapter 8.
July 16, 2007: Made numerous minor edits throughout manual.
January 23, 2008: In Table 9.2, changed pins PE0RN/RP/TN/TP to read [0] instead of [1:0].
September 24, 2009: In Chapter 3, change made to L2 description in Link States section. Made
numerous changes in Chapter 6, Power. In Chapter 8, Registers, modified description of the LDIS bit in the
PCI Express Link Control register and changed bit field for
[24:16]
.
November 10, 2009: Added a new Chapter 3 called Theory of Operations.
January 28, 2011: ZB silicon added to Table 1.9, Revision ID.
VID - Vendor Identification Register (0x000)...........................................................................................9-11
WAKEUPCNTL - Wakeup Protocol Control Register (0x5CC) ...............................................................9-64
PES5T5 User ManualxiJanuary 28, 2011
Page 20
IDT Register List
Notes
PES5T5 User ManualxiiJanuary 28, 2011
Page 21
Chapter 1
PES5T5 Device Overview
®
Notes
Introduction
The 89HPES5T5 is a member of IDT’s PRECISE™ family of PCI Express switching solutions. The
PES5T5 is an 5-lane, 5-port peripheral chip that performs PCI Express Base switching. It provides connectivity and switching functions between a PCI Express upstream port and up to four downstream ports and
supports switching between downstream ports.
List of Features
High Performance PCI Express Switch
– Five 2.5Gbps PCI Express lanes
– Five switch ports
– Upstream port is x1
– Downstream ports are x1
– Low-latency cut-through switch architecture
– Support for Max Payload Sizes up to 256 bytes
– One virtual channel
– Eight traffic classes
– PCI Express Base Specification Revision 1.1 compliant
Flexible Architecture with Numerous Configuration Options
– Automatic lane reversal on all ports
– Automatic polarity inversion
– Ability to load device configuration from serial EEPROM
Legacy Support
– PCI compatible INTx emulation
– Bus locking
Highly Integrated Solution
– Requires no external components
– Incorporates on-chip internal memory for packet buffering and queueing
– Integrates five 2.5 Gbps embedded SerDes with 8B/10B encoder/decoder (no separate trans-
ceivers needed)
Reliability, Availability, and Serviceability (RAS) Features
– Internal end-to-end parity protection on all TLPs ensures data integrity even in systems that do not
implement end-to-end CRC (ECRC)
– Supports ECRC and Advanced Error Reporting
– Supports PCI Express Native Hot-Plug, Hot-Swap capable I/O
– Compatible with Hot-Plug I/O expanders used on PC motherboards
Power Management
– Utilizes advanced low-power design techniques to achieve low typical power consumption
– Supports PCI Express Power Management Interface specification (PCI-PM 1.2)
– Unused SerDes are disabled.
– Supports Advanced Configuration and Power Interface Specification, Revision 2.0 (ACPI)
supporting active link state
Testability and Debug Features
– Built in Pseudo-Random Bit Stream (PRBS) generator
– Numerous SerDes test modes
– Ability to read and write any internal register via the SMBus
– Ability to bypass link training and force any link into any mode
– Provides statistics and performance counters
PES5T5 User Manual 1 - 1January 28, 2011
Page 22
IDT PES5T5 Device Overview
Notes
11 General Purpose Input/Output Pins
– Each pin may be individually configured as an input or output
– Each pin may be individually configured as an interrupt input
– Some pins have selectable alternate functions
Packaged in a 15mm x 15mm BGA
PES5T5 User Manual1 - 2January 28, 2011
Page 23
IDT PES5T5 Device Overview
System Diagrams
SC
Packet
Memory
Write
Processor
GPIO
Reset
RMT
Hot Plug
Ingress
SMBUS
4-lane
Stack
P
M
PCSPCSPCSPCS
Parser
DL
MAC
Queuing
Structure
Arb
AL
Completion
Processor
Message
Processor
Return Buffer
CSRM
Read
Processor
Egress
Parser
1-lane
Stack
DL
P
M
MAC
PCSPCSPCSPCS
1-lane
Stack
P
M
DL
MAC
1-lane
Stack
P
M
DL
MAC
1-lane
Stack
P
M
DL
MAC
4-Pack SerDes
Figure 1.1 PES5T5 Architectural Block Diagram
4-Pack SerDes
PES5T5 User Manual1 - 3January 28, 2011
Page 24
IDT PES5T5 Device Overview
Notes
Logic Diagram
Reference
Clock
PCI Express
Switch
SerDes Input
Port 0
PCI Express
Switch
SerDes Input
Port 2
PCI Express
Switch
SerDes Input
Port 3
PCI Express
Switch
SerDes Input
Port 4
PCI Express
Switch
SerDes Input
Port 5
Master
SMBus Interface
Slave
SMBus Interface
System
Pins
PEREFCLKP
PEREFCLKN
REFCLKM
PE0RP[0]
PE0RN[0]
PE2RP[0]
PE2RN[0]
PE3RP[0]
PE3RN[0]
PE4RP[0]
PE4RN[0]
PE5RP[0]
PE5RN[0]
MSMBADDR[4:1]
MSMBCLK
MSMBDAT
SSMBADDR[5,3:1]
SSMBCLK
SSMBDAT
MSMBSMODE
CCLKDS
CCLKUS
RSTHALT
PERSTN
SWMODE[2:0]
WAKEN
APWRDISN
PCI Express
PE0TP[0]
PE0TN[0]
PE2TP[0]
PE2TN[0]
PE3TP[0]
PE3TN[0]
PE4TP[0]
PE4TN[0]
PES5T5
PE5TP[0]
PE5TN[0]
11
4
4
3
GPIO[10:0]
JTAG_TCK
JTAG_TDI
JTAG_TDO
JTAG_TMS
JTAG_TRST_N
VDDCORE
V
IO
DD
V
PE
DD
V
APE
DD
V
SS
PE
V
TT
Switch
SerDes Output
Port 0
PCI Express
Switch
SerDes Output
Port 2
PCI Express
Switch
SerDes Output
Port 3
PCI Express
Switch
SerDes Output
Port 4
PCI Express
Switch
SerDes Output
Port 5
General Purpose
I/O
JTAG Pins
Power/Ground
Figure 1.2 PES5T5 Logic Diagram
SSID/SSVID
The PES5T5 contains the mechanisms necessary to implement the PCI-to-PCI bridge Subsystem ID
and Subsystem Vendor ID capability structure. However, in the default configuration the Subsystem ID and
Subsystem Vendor ID capability structure is not enabled. To enable this capability, the SSID and SSVID
fields in the Subsystem ID and Subsystem Vendor ID (SSIDSSVID) register must be initialized with the
appropriate ID values. the Next Pointer (NXTPTR) field in one of the other enhanced capabilities should be
initialized to point to this capability. Finally, the Next Pointer (NXTPTR) of this capability should be adjusted
to point to the next capability if necessary.
PES5T5 User Manual1 - 4January 28, 2011
Page 25
IDT PES5T5 Device Overview
Notes
Device Serial Number Enhanced Capability
The PES5T5 contains the mechanisms necessary to implement the PCI express device serial number
enhanced capability. However, in the default configuration this capability structure is not enabled. To enable
the device serial number enhanced capability, the Serial Number Lower Doubleword (SNUMLDW) and the
Serial Number Upper Doubleword (SNUMUDW) registers should be initialized. The Next Pointer (NXTPTR)
field in one of the other enhanced capabilities should be initialized to point to this capability . Finally, the Next
Pointer (NXTPTR) of this capability should be adjusted to point to the next capability if necessary.
Pin Description
The following tables lists the functions of the pins provided on the PES5T5. Some of the functions listed
may be multiplexed onto the same pin. The active polarity of a signal is defined using a suffix. Signals
ending with an “N” are defined as being active, or asserted, when at a logic zero (low) level. All other signals
(including clocks, buses, and select lines) will be interpreted as being active, or asserted, when at a logic
one (high) level.
SignalTypeName/Description
PE0RP[0]
PE0RN[0]
PE0TP[0]
PE0TN[0]
PE2RP[0]
PE2RN[0]
PE2TP[0]
PE2TN[0]
PE3RP[0]
PE3RN[0]
PE3TP[0]
PE3TN[0]
PE4RP[0]
PE4RN[0]
PE4TP[0]
PE4TN[0]
PE5RP[0]
PE5RN[0]
PE5TP[0]
PE5TN[0]
PEREFCLKP
PEREFCLKN
REFCLKMIPCI Express Reference Clock Mode Select. This signal selects the fre-
IPCI Express Port 0 Serial Data Receive. Differential PCI Express receive
pair for port 0.
OPCI Express Port 0 Serial Data Transmit. Differential PCI Express trans-
mit pair for port 0.
IPCI Express Port 2 Serial Data Receive. Differential PCI Express receive
pair for port 2.
OPCI Express Port 2 Serial Data Transmit. Differential PCI Express trans-
mit pair for port 2.
IPCI Express Port 3 Serial Data Receive. Differential PCI Express receive
pair for port 3.
OPCI Express Port 3 Serial Data Transmit. Differential PCI Express trans-
mit pair for port 3.
IPCI Express Port 4 Serial Data Receive. Differential PCI Express receive
pair for port 4.
OPCI Express Port 4 Serial Data Transmit. Differential PCI Express trans-
mit pair for port 4.
IPCI Express Port 5 Serial Data Receive. Differential PCI Express receive
pair for port 5.
OPCI Express Port 5 Serial Data Transmit. Differential PCI Express trans-
mit pair for port 5.
IPCI Express Reference Clock. Differential reference clock pair input. This
clock is used as the reference clock by on-chip PLLs to generate the clocks
required for the system logic and on-chip SerDes. The frequency of the differential reference clock is determined by the REFCLKM signal.
quency of the reference clock input.
0x0 - 100 MHz
0x1 - 125 MHz
Table 1.1 PCI Express Interface Pins
PES5T5 User Manual1 - 5January 28, 2011
Page 26
IDT PES5T5 Device Overview
Notes
MSMBADDR[4:1]IMaster SMBus Address. These pins determine the SMBus address of the
SSMBADDR[5,3:1]ISlave SMBus Address. These pins determine the SMBus address to
SignalTypeName/Description
serial EEPROM from which configuration information is loaded.
MSMBCLKI/OMaster SMBus Clock. This bidirectional signal is used to synchronize
transfers on the master SMBus.
MSMBDATI/OMaster SMBus Data. This bidirectional signal is used for data on the mas-
ter SMBus.
which the slave SMBus interface responds.
SSMBCLKI/OSlave SMBus Clock. This bidirectional signal is used to synchronize trans-
fers on the slave SMBus.
SSMBDATI/OSlave SMBus Data. This bidirectional signal is used for data on the slave
SMBus.
Table 1.2 SMBus Interface Pins
SignalTypeName/Description
GPIO[0]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
Alternate function pin name: P2RSTN
Alternate function pin type: Output
Alternate function: Reset output for downstream port 2
GPIO[1]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
Alternate function pin name: P4RSTN
Alternate function pin type: Output
Alternate function: Reset output for downstream port 4
GPIO[2]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
Alternate function pin name: IOEXPINTN0
Alternate function pin type: Input
Alternate function: I/O Expander interrupt 0 input
GPIO[3]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
Alternate function pin name: IOEXPINTN1
Alternate function pin type: Input
Alternate function: I/O Expander interrupt 1 input
GPIO[4]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
Alternate function pin name: IOEXPINTN2
Alternate function pin type: Input
Alternate function: I/O Expander interrupt 2 input
GPIO[5]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
GPIO[6]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
Table 1.3 General Purpose I/O Pins (Part 1 of 2)
PES5T5 User Manual1 - 6January 28, 2011
Page 27
IDT PES5T5 Device Overview
Notes
SignalTypeName/Description
GPIO[7]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
Alternate function pin name: GPEN
Alternate function pin type: Output
Alternate function: General Purpose Event (GPE) output
GPIO[8]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
GPIO[9]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
Alternate function pin name: P3RSTN
Alternate function pin type: Output
Alternate function: Reset output for downstream port 3
GPIO[10]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
Alternate function pin name: P5RSTN
Alternate function pin type: Output
Alternate function: Reset output for downstream port 5
GPIO[11]I/OGeneral Purpose I/O.
This pin can be configured as a general purpose I/O pin.
Table 1.3 General Purpose I/O Pins (Part 2 of 2)
SignalTypeName/Description
APWRDISNIAuxiliary Power Disable Input. When this pin is active, it disables the
device from using auxiliary power supply.
CCLKDSICommon Clock Downstream. The assertion of this pin indicates that all
downstream ports are using the same clock source as that provided to
downstream devices.This bit is used as the initial value of the Slot Clock
Configuration bit in all of the Link Status Registers for downstream ports.
The value may be override by modifying the SCLK bit in the downstream
port’s PCIELSTS register.
CCLKUSICommon Clock Upstream. The assertion of this pin indicates that the
upstream port is using the same clock source as the upstream device. This
bit is used as the initial value of the Slot Clock Configuration bit in the Link
Status Register for the upstream port. The value may be overridden by
modifying the SCLK bit in the PA_PCIELSTS register.
MSMBSMODEIMaster SMBus Slow Mode. The assertion of this pin indicates that the
master SMBus should operate at 100 KHz instead of 400 kHz. This value
may not be overridden.
PERSTNIFundamental Reset. Assertion of this signal resets all logic inside the
PES5T5 and initiates a PCI Express fundamental reset.
Table 1.4 System Pins (Part 1 of 2)
PES5T5 User Manual1 - 7January 28, 2011
Page 28
IDT PES5T5 Device Overview
Notes
SignalTypeName/Description
RSTHALTIReset Halt. When this signal is asserted during a PCI Express fundamental
reset, the PES5T5 executes the reset procedure and remains in a reset
state with the Master and Slave SMBuses active. This allows software to
read and write registers internal to the device before normal device operation begins. The device exits the reset state when the RSTHALT bit is
cleared in the PA_SWCTL register by an SMBus master.
SWMODE[2:0]ISwitch Mode. These configuration pins determine the PES5T5 switch
operating mode.
0x0 - Normal switch mode
0x1 - Normal switch mode with Serial EEPROM initialization
0x2 - through 0xF Reserved
WAKENI/OWake Input/Output. The WAKEN signal is an input or output. The WAKEN
signal input/output selection can be made through the WAKEDIR bit setting
in the WAKEUPCNTL register.
Table 1.4 System Pins (Part 2 of 2)
SignalTypeName/Description
JTAG_TCKIJTAG Clock. This is an input test clock used to clock the shifting of data
into or out of the boundary scan logic or JTAG Controller. JTAG_TCK is
independent of the system clock with a nominal 50% duty cycle.
JTAG_TDIIJTAG Data Input. This is the serial data input to the boundary scan logic or
JTAG Controller.
JTAG_TDOOJTAG Data Output. This is the serial data shifted out from the boundary
scan logic or JTAG Controller. When no data is being shifted out, this signal
is tri-stated.
JTAG_TMSIJTAG Mode. The value on this signal controls the test mode select of the
boundary scan logic or JTAG Controller.
JTAG_TRST_NIJTAG Reset. This active low signal asynchronously resets the boundary
scan logic and JTAG TAP Controller. An external pull-up on the board is
recommended to meet the JTAG specification in cases where the tester
can access this signal. However, for systems running in functional mode,
one of the following should occur:
1) actively drive this signal low with control logic
2) statically drive this signal low with an external pull-down on the board
Table 1.5 Test Pins
SignalTypeName/Description
COREICore VDD. Power supply for core logic.
V
DD
V
IOII/O VDD. LVTTL I/O buffer power supply.
DD
PEIPCI Express Digital Power. PCI Express digital power used by the digital
V
DD
power of the SerDes.
V
APEIPCI Express Analog Power. PCI Express analog power used by the PLL
DD
and bias generator.
VTTPEIPCI Express Termination Power.
V
SS
IGround.
Table 1.6 Power and Ground Pins
PES5T5 User Manual1 - 8January 28, 2011
Page 29
IDT PES5T5 Device Overview
Notes
Pin Characteristics
Note: Some input pads of the PES5T5 do not contain internal pull-ups or pull-downs. Unused
inputs should be tied off to appropriate levels. This is especially critical for unused control signal
inputs which, if left floating, could adversely affect operation. Also, any input pin left floating can
cause a slight increase in power consumption.
All vendor ID fields in the device are hardwired to 0x111D which corresponds to Integrated Device Technology, Inc.
Device ID
The PES5T5 device ID is shown in Table 1.8.
PCIe DeviceDevice ID
0x40x803C
Table 1.8 PES5T5 Device ID
Revision ID
The PES5T5 revision ID is shown in Table 1.9.
Revision IDDescription
0x0FCorresponds to ZA silicon
0x0ECorresponds to ZB silicon
Table 1.9 PES5T5 Revision ID
PES5T5 User Manual1 - 10January 28, 2011
Page 31
IDT PES5T5 Device Overview
Notes
JTAG ID
The JTAG ID is:
– Version: Same value as Revision ID. See Table 1.9
– Part number: Same value as base Device ID. See Table 1.8.
– Manufacturer ID: 0x33
– LSB: 0x1
Port Configuration
The PES5T5 supports five ports: one x4 upstream port and four x1 downstream ports. Figure 1.3 illustrates this configuration.
Port 0
x4
Dev. 3
Dev. 0
PCI to PCI
Bridge
PCI to PCI
Bridge
Dev. 4
Dev. 5
PCI to PCI
Bridge
PES5T5
Dev. 2
PCI to PCI
Bridge
Virtual PCI Bus
PCI to PCI
Bridge
Port 2
x1
Port 3
x1
Port 4
x1
Figure 1.3 PES5T5 Port Configuration
Port 5
x1
PES5T5 User Manual1 - 11January 28, 2011
Page 32
IDT PES5T5 Device Overview
Notes
PES5T5 User Manual1 - 12January 28, 2011
Page 33
Chapter 2
Clocking, Reset, and
Initialization
®
Notes
Introduction
The PES5T5 has a differential reference clock input that is used internally to generate all of the clocks
required by the internal switch logic and the SerDes. While not required, it is recommended that both reference clock input pairs be driven from a common clock source. The frequency of the reference clock inputs
may be selected by the Reference Clock Mode Select (REFCLKM) input.
Each of the reference clock differential inputs feeds several on-chip PLLs. Each PLL generates a 2.5
GHz clock which is used by several SerDes lanes and produces a 250 MHz core clock.
Clock Operation
When the CCLKUS and CCLKDS pins are asserted, they indicate that a common clock is being used
between the upstream device and the upstream port, as well as between the downstream devices and the
downstream ports. The Spread Spectrum Clock (SSC) must be disabled when the non-common clock is
used on either the upstream port or downstream port. Figures 2.1 through 2.4 illustrate the operation of the
CCLKUS and CCLKDS clocks using a common clock and a non-common clock.
PES5T5
Root Complex
Hi
Clock Generator
Figure 2.1 Common Clock on Upstream and Downstream (option to enable or disable Spread Spectrum Clock)
PES5T5 User Manual 2 - 1January 28, 2011
Port 0
CCLKUS
REFCLK0
Port 2
...
Port 5
CCLKDS
REFCLK1
EP
...
EP
Hi
Page 34
IDT Clocking, Reset, and InitializationClock Operation
Notes
PES5T5
Root Complex
Low
Clock Generator
Figure 2.2 Non-Common Clock on Upstream; Common Clock on Downstream (must disable Spread Spectrum
Port 0
CCLKUS
REFCLK0
Clock)
PES5T5
Root Complex
Port 0
Port 2
...
Port 5
CCLKDS
REFCLK1
Port 2
...
EP
...
EP
Hi
Clock Generator
EP
...
Port 5
Hi
Clock Generator
Figure 2.3 Common Clock on Upstream; Non-Common Clock on Downstream (must disable Spread Spectrum
CCLKUS
REFCLK0
CCLKDS
REFCLK1
Clock)
EP
Low
Clock Generator
PES5T5 User Manual2 - 2January 28, 2011
Page 35
IDT Clocking, Reset, and InitializationClock Operation
Notes
Port 2
...
Root Complex
PES5T5
Port 0
Port 5
Low
Clock Generator
Figure 2.4 Non-Common Clock on Upstream and Downstream (must disable Spread Spectrum Clock)
CCLKUS
REFCLK0
CCLKDS
REFCLK1
Clock Generator
* May be unique for each EP
EP
...
EP
Low
Clock Generator *
Initialization
A boot configuration vector consisting of the signals listed in Table 2.2 is sampled by the PES5T5 during
a fundamental reset when PERSTN is negated. The boot configuration vector defines essential parameters
for switch operation. Since the boot configuration vector is sampled only during a fundamental reset
sequence, the value of signals which make up the boot configuration vector is ignored during other times
and their state outside of a fundamental reset has no effect on the operation of the PES5T5.
While basic switch operation may be configured using signals in the boot configuration vector , advanced
switch features require configuration via an external serial EEPROM. The external serial EEPROM allows
modification of any bit in any software visible register. See Chapter 6, SMBus Interfaces, for more information on the serial EEPROM.
The external serial EEPROM and slave SMBus interface may be used to override the function of some
of the signals in the boot configuration vector during a fundamental reset. The signals that may be overridden are noted in Table 2.2. The state of all of the boot configuration signals in Table 2.2 sampled during
the most recent cold reset may be determined by reading the SWSTS register.
PES5T5 User Manual2 - 3January 28, 2011
Page 36
IDT Clocking, Reset, and InitializationClock Operation
Notes
Signal
CCLKDSYCommon Clock Downstream. The assertion of this pin
CCLKUSYCommon Clock Upstream. The assertion of this pin indi-
MSMBSMODE NMaster SMBus Slow Mode. The assertion of this pin indi-
REFCLKMNPCI Express Reference Clock Mode Select. These sig-
May Be
Overridden
Description
indicates that all downstream ports are using the same
clock source as that provided to downstream devices.This
pin is used as the initial value of the Slot Clock Configuration bit in all of the Link Status Registers for downstream
ports. The value may be overridden by modifying the SCLK
bit in the downstream port’s PCIELSTS register.
cates that the upstream port is using the same clock source
as the upstream device. This pin is used as the initial value
of the Slot Clock Configuration bit in the Link Status Register for the upstream port. The value may be overridden by
modifying the SCLK bit in the upstream port’s PCIELSTS
register.
cates that the master SMBus should operate at 100 KHz
instead of 400 kHz.
nals select the frequency of the reference clock input.
0x0 - 100 MHz
0x1 - 125 MHz
RSTHALTYReset Halt. When this signal is asserted during a PCI
Express fundamental reset, the PES5T5 executes the reset
procedure and remains in a reset state with the Master and
Slave SMBuses active. This allows software to read and
write registers internal to the device before normal device
operation begins. The device exits the reset state when the
RSTHALT bit is cleared in the SWCTL register through the
SMBus.
The value may be overridden by modifying the RSTHALT
bit in the SWCTL register.
SWMODE[2:0]NSwitch Mode. These configuration pins determine the
PES5T5 switch operating mode.
0x0 -Normal switch mode
0x1 -Normal switch mode with Serial EEPROM initialization
0x2 -Normal switch mode with lower latency
0x3 -Normal switch mode with Serial EEPROM initialization
and lower latency
1
1
0x4 through 0xF - Reserved
APWRDISNYAuxiliary Power Disable. If this signal is tied to logic ‘0’at
the bootup time then the device is disabled to use auxiliary
power and the associated logic on the chip is disabled. All
the FRSticky bit values are reset to the default values.
Table 2.2 Boot Configuration Vector Signals
1.
Device latency is reduced by 8 ns in this mode. This mode should only be enabled when a c ommon clock is used o r when
a non-common clock is used with a maximum payload size less than 2KB.
PES5T5 User Manual2 - 4January 28, 2011
Page 37
IDT Clocking, Reset, and InitializationClock Operation
Notes
Reset
The PES5T5 defines four reset categories: fundamental reset, hot reset, upstream secondary bus reset,
and downstream secondary bus reset.
– A fundamental reset causes all logic in the PES5T5 to be returned to an initial state.
– A hot reset causes all logic in the PES5T5 to be returned to an initial state, but does not cause the
state of register fields denoted as “sticky” to be modified.
– An upstream secondary bus reset causes all devices on the virtual PCI bus to be hot reset except
the upstream port (i.e., upstream PCI to PCI bridge).
– A downstream secondary bus reset causes a hot reset to be propagated on the corresponding
external secondary bus link.
There are two sub-categories of fundamental reset: cold reset and warm reset. A cold reset occurs
following a device being powered on and assertion of PERSTN. A warm reset is a fundamental reset that
occurs without the removal of power.
Fundamental Reset
A fundamental reset may be initiated by any of the following conditions:
– A cold reset initiated by a power-on and the assertion of the PCI Express Reset (PERSTN) input
pin. Refer to the device datasheet for power sequencing requirements.
– A warm reset initiated by the assertion of the PCI Express Reset (PERSTN) input pin while power
is on.
– A warm reset initiated by the writing of a one to the Fundamental Reset (FRST) bit in the Switch
Control (SWCTL) register.
When configured to operate in normal mode, the following reset sequence is executed.
1. Wait for the fundamental reset condition to clear (e.g., negation of PERSTN).
2. On negation of PERSTN, sample the boot configuration signals listed in Table 2.2. If PERSTN was
not asserted, use the previously sampled boot configuration signal values (e.g., when a fundamental
reset is the result of a one being written to the SWCTL register).
Examine the state of the sampled SWMODE[2:0] signals to determine the switch operating
mode.
3. The PLL and SerDes are initialized.
4. Link training begins. While link training is in progress, proceed to step 5.
5. If the Reset Halt (RSTHALT) pin is asserted, the RSTHALT bit in the SWSTS register is set.
6. If the switch operating mode is not a test mode, the reset signal to the PCI Express stacks and associated logic is negated but they are held in a quasi-reset state in which the following actions occur.
All links enter an active link training state within 20ms of the clearing of the fundamental reset
condition.
Within 100 ms of the clearing of the fundamental reset condition, all of the stacks are able to
process configuration transactions and respond to these transactions with a configuration
request retry status completion. All other transactions are ignored.
7. The master SMBus operating frequency is determined.
The state of the MSMBSMODE signal is examined. If it is asserted, then the master SMBus is
initialized to operate at 100 KHz rather than 400 KHz.
8. The slave SMBus is taken out of reset and initialized. The slave SMBus address specified by the
SSMBADDR[5,3:1] pins is used.
9. The master SMBus is taken out of reset and initialized.
10. If the selected switch operating mode is one that requires initialization from the serial EEPROM, then
the contents of the serial EEPROM are read and the appropriate PES5T5 registers are updated.
PES5T5 User Manual2 - 5January 28, 2011
Page 38
IDT Clocking, Reset, and InitializationClock Operation
Notes
If a one is written by the serial EEPROM to the Full Link Retrain (FLRET) bit in any Phy Link
State 0 (PHYLSTATE0) register, then link retraining is initiated on the corresponding port using
the current link parameters.
If an error is detected during loading of the serial EEPROM, then loading of the serial EEPROM
is aborted and the RSTHALT bit is set in the SWCTL register. Error information is recorded in
the SMBUSSTS register.
When serial EEPROM initialization completes or when an error is detected, the DONE bit in the
SMBUSSTS register is set.
11. If the Reset Halt (RSTHALT) bit is set in the SWCTL register, all of the logic is held in a reset state
except the master and slave SMBuses, the control/status registers, and the stacks which continue
to be held in a quasi-reset state and respond to configuration transactions with a retry. The device
remains in this state until the RSTHALT bit is cleared via the slave SMBus. In this mode, an external
agent may read and write any internal control and status registers and may access the external
serial EEPROM via the EEPROMINTF register.
12. Normal device operation begins.
The PCIe base specification indicates that normal operation should begin within 1.0 second after a
fundamental reset of a device. The reset sequence above guarantees that normal operation will begin
within this period as long as the serial EEPROM initialization process completes within 200 ms. Under
normal circumstances, 200 ms is more than adequate to initialize registers in the device even with a Master
SMBus operating frequency of 100 KHz.
Serial EEPROM initialization may cause writes to register fields that initiate side effects such as link
retraining. These side effects are initiated at the point at which the write occurs. Therefore, serial EEPROM
initialization should be structured in a manner so as to ensure proper configuration prior to initiation of these
side effects.
A warm reset initiated by the writing of a one to the Fundamental Reset (FRST) bit in the Switch Control
(SWCTL) register always results in the PES5T5 returning a completion to the requester
reset process begins.
The PES5T5 provides a reset output signal for each downstream port implemented as a GPIO alternate
function. When a fundamental reset occurs, all of the GPIO pins default to GPIO inputs. Therefore, the
downstream port resets are tri-stated. A system designer should use a pull-down on these signals if they
are used as reset outputs.
The operation of a fundamental reset with serial EEPROM initialization (i.e., SWMODE[2:0] = 0x1) is
illustrated in Figure 2.5.
before the warm
PES5T5 User Manual2 - 6January 28, 2011
Page 39
IDT Clocking, Reset, and InitializationClock Operation
Notes
REFCLK
Vdd
PERSTN
Tpvperl
RSTHALT
SerDes
Master SMBus
Slave SMBus
Notes:
1) Reference Clock (REFCLK) not shown to scale.
2) The PES5T5 requires a minimum time for Tperst-clk of 1µs. The PES5T5 requires a minimum time for Tpvperl of 1ms.
3) In a system, the values of Tpvperl and Tperst-clk depend on the mechanical form factor in which the PES5T5 is used. For exam ple,
the PCIe Card Electromechanical Specification, Revision 2.0, specifies minimum values of Tperst-clk=100µs and Tpvperl=100ms.
PLL Reset and LockCDR Reset & LockReady for Normal Operation
20ms max.
11μs
Link Training
1.01 ms max.
ReadyIdleSerial EEPROM Initialization
Ready for Normal Operation
Figure 2.5 Fundamental Reset with Serial EEPROM initialization
Hot Reset
A hot reset may be initiated by any of the following conditions:
– Reception of TS1 ordered-sets on the upstream port indicating a hot reset.
– Data link layer of the upstream port transitions to the DL_Down state.
– Writing a one to the Hot Reset (HRST) bit in the Switch Control (SWCTL) register.
The initiation of a hot reset due to the data link layer of the upstream port transitioning to the DL_Down
state may be disabled by setting the Disable Link Down Hot Reset (DLDHRST) bit in the Switch Control
(SWCTL) register. Other hot reset conditions are unaffected by this bit.
When a hot reset occurs, the following sequence is executed.
1. Each downstream port whose link is up propagates the hot reset by transmitting TS1 ordered sets
with the hot reset bit set.
2. All of the logic associated with the PES5T5 is reset except the PLLs, SerDes, master SMBus interface, and slave SMBus interface.
3. All registers fields in all registers, except those denoted as “sticky” or Read and Write when Unlocked
(i.e, RWL), are reset to their initial value. The value of fields denoted as “sticky” or RWL is preserved
across a hot reset.
4. Link training begins. While link training is in progress, proceed to step 5.
5. The PCI Express stacks and associated logic are held in a quasi-reset state in which the following
actions occur.
All links enter an active link training state within 20ms of the clearing of the hot reset condition.
Within 100 ms of the clearing of the fundamental reset condition, all of the stacks are able to
process configuration transactions and respond to these transactions with a configuration
request retry status completion. All other transactions are ignored.
6. If the selected switch operating mode is one that requires initialization from the serial EEPROM and
the Disable Hot Reset Serial EEPROM Initialization (DHRSTSEI) bit is not set in the Switch Control
(SWCTL) register, then the contents of the serial EEPROM are read and the appropriate PES5T5
registers are updated.
If a one is written by the serial EEPROM to the Full Link Retrain (FLRET) bit in the Phy Link
State 0 (PHYLSTATE0) register, then link retraining is initiated on the corresponding port using
PES5T5 User Manual2 - 7January 28, 2011
Page 40
IDT Clocking, Reset, and InitializationClock Operation
Notes
the current link parameters.
If an error is detected during loading of the serial EEPROM, then loading of the serial EEPROM
is aborted and the RSTHALT bit is set in the SWCTL register. Error information is recorded in
the SMBUSSTS register.
When serial EEPROM initialization completes or when an error is detected, the DONE bit in the
SMBUSSTS register is set.
7. If the Reset Halt (RSTHALT) bit is set in the SWCTL register, all of the logic is held in a reset state
except the master and slave SMBuses. The RSTHALT bit is only set if serial EEPROM initialization
is enabled in step 6.
8. Normal device operation begins.
The operation of the slave SMBus interface is unaffected by a hot reset. Using the slave SMBus to
access a register that is reset by a hot reset causes zero to be returned on a read and written data to be
ignored on writes. A hot reset initiated by the writing of a one to the Hot Reset (HRST) bit in the Switch
Control (SWCTL) register always results in the PES5T5 returning a completion to the requester before the
hot reset process begins.
Upstream Secondary Bus Reset
An upstream secondary bus reset may be initiated by the following condition:
– A one is written to the Secondary Bus Reset (SRESET) bit in the upstream port’s (i.e., port 0)
Bridge Control Register (BCTL).
When an upstream secondary bus reset occurs, the following sequence is executed.
1. Each downstream port whose link is up propagates the reset by transmitting TS1 ordered sets with
the hot reset bit set.
2. All register fields in all registers associated with downstream ports, except those denoted as “sticky”
or Read and Write when Unlocked (i.e, RWL), are reset to their initial value. The value of fields
denoted as “sticky” or RWL is unaffected by an upstream secondary bus reset.
3. All TLPs received from downstream ports and queued in the PES5T5 are discarded.
4. Logic in the stack, application layer, and switch core associated with the downstream ports are
gracefully reset.
5. Wait for the Secondary Bus Reset (SRESET) bit in the upstream port’s Switch Control Register
(SWCTL) to clear.
6. Normal downstream port operation begins.
The operation of the upstream port is unaffected by a secondary bus reset. The link remains up and
Type 0 configuration read and write transactions that target the upstream port complete normally. During an
upstream secondary bus reset, all TLPs destined to the secondary side of the upstream port’s PCI-to-PCI
bridge are treated as unsupported requests.
The operation of the slave SMBus interface is unaffected by an upstream secondary bus reset. Using
the slave SMBus to access a register that is reset by an upstream secondary bus reset causes the
register's default value to be returned on a read and written data to be ignored on writes.
Downstream Secondary Bus Reset
A downstream secondary bus reset may be initiated by the following condition:
– A one is written to the Secondary Bus Reset (SRESET) bit in the port’s (i.e., port 0) Bridge Control
Register (BCTRL).
PES5T5 User Manual2 - 8January 28, 2011
Page 41
IDT Clocking, Reset, and InitializationClock Operation
Notes
When a downstream secondary bus reset occurs, the following sequence is executed.
1. If the corresponding downstream port’s link is up, TS1 ordered sets with the hot reset bit set are
transmitted.
2. All TLPs received from corresponding downstream port and queued in the PES5T5 are discarded.
3. Wait for the Secondary Bus Reset (SRESET) bit in the upstream port’s Switch Control Register
(SWCTL) to clear.
4. Normal downstream port operation begins.
The operation of the upstream port is unaffected by a downstream secondary bus reset. The operation
of other downstream ports is unaffected by a downstream secondary bus reset. During a downstream
secondary bus reset, Type 0 configuration read and write transactions that target the downstream port
complete normally. During a downstream secondary bus reset, all TLPs destined to the secondary side of
the downstream port’s PCI-to-PCI bridge are treated as unsupported requests. The operation of the slave
SMBus interface is unaffected by a downstream secondary bus reset.
Downstream Port Reset Outputs
Individual downstream port reset outputs (P2RSTN through P5RSTN) are provided as GPIO pin alternate functions. Following a fundamental reset, all of the GPIO pins default to GPIO inputs. Therefore, the
downstream port resets are tri-stated. A system designer should use a pull-down on these signals if they
are used as reset outputs. The PES5T5 ensures through hardware that the minimum PxRSTN assertion
pulse width is no less than 200 µs.
Downstream port reset outputs can be configured to operate in one of three modes. These modes are:
power enable controlled reset output, power good controlled reset output, and hot reset controlled output.
The downstream port reset output mode is determined by the Reset Mode (RSTMODE) field in the HotPlug Configuration Control (HPCFGCTL) register.
Power Enable Controlled Reset Output
In this mode, a downstream port reset output state is controlled as a side effect of the slot power being
turned on or off. The operation of this mode is illustrated in Figure 2.6. A downstream port’s slot power is
controlled by the Power Controller Control (PCC) bit in the PCI Express Slot Control (PCIESCTL) register.
PxPEP
PxRSTN
T
PWR2RST
Figure 2.6 Power Enable Controlled Reset Output Mode Operation
T
RST2PWR
While slot power is disabled, the corresponding downstream port reset output is asserted.
When slot power is enabled by writing a zero to the PCC bit, the Port x Power Enable Output (PxPEP) is
asserted and then power to the slot is enabled and the corresponding downstream port reset output is
negated. The time between the assertion of the PxPEP signal and the negation of the PxRSTN signal is
controlled by the value in the Slot Power to Reset Negation (PWR2RST) field in the HPCFGCTL register.
While slot power is enabled, the corresponding downstream port reset output is negated.
When slot power is disabled by writing a one to the PCC bit, the corresponding downstream port reset
output is asserted and then slot power is disabled. The time between the assertion of the PxRSTN signal
and the negation of the PxPEP signal is controlled by the value in the Reset Negation to Slot Power
(RST2PWR) field in the HPCFGCTL register.
PES5T5 User Manual2 - 9January 28, 2011
Page 42
IDT Clocking, Reset, and InitializationClock Operation
Notes
Power Good Controlled Reset Output
As in the Power Enable Controlled Reset mode, in this mode a downstream port reset output state is
controlled as a side effect of slot power being turned on or off. However, the timing in this mode depends on
the power good state of the slot’s power supply. The operation of this mode is illustrated in Figure 2.7.
PxPEP
PxPWRGDN
PxRSTN
T
PWR2RST
Figure 2.7 Power Good Controlled Reset Output Mode Operation
T
RST2PWR
The operation of this mode is similar to that of the Power Enable Controlled Reset mode except that
when power is enabled, the negation of the corresponding port reset output occurs as a result of and after
assertion of the slot’s Power Good (PxPWRGDN) signal is observed. The time between the assertion of the
PxPWRGDN signal and the negation of the PxRSTN signal is controlled by the value in the Slot Power to
Reset Negation (PWR2RST) field in the HPCFGCTL register.
When slot power is disabled by writing a one to the PCC bit, the corresponding downstream port reset
output is asserted and then slot power is disabled. The time between the assertion of the PxRSTN signal
and the negation of the PxPEP signal is controlled by the value in the Reset Negation to Slot Power
(RST2PWR) field in the HPCFGCTL register.
If at any point while a downstream port is not being reset (i.e., PxRSTN is negated) a power fault is
detected (i.e., PxPWRGDN is negated), the corresponding port reset output is immediately asserted. Since
the PxPWRGDN signal is an I/O expander input, it may not be possible to meet a profiled power level
invalid to reset asserted timing specification (i.e., PxPWRGDN to PxRSTN). Systems that require a shorter
time interval may implement this functionality external to the PES5T5.
Hot Reset Controlled Reset Output
In this mode the following conditions cause a downstream port’s reset output to be asserted.
– Hot reset
– Upstream secondary bus reset
– Downstream secondary bus reset
When a downstream port reset output is asserted it remains asserted as long as one of the above conditions persists or 200 µs, whichever is longer.
PES5T5 User Manual2 - 10January 28, 2011
Page 43
Chapter 3
Theory of Operation
®
Notes
Port Interrupts
The upstream port (Port 0) generates legacy interrupts and MSIs to report internal switch errors such as
parity errors and errors in reading configuration registers. Downstream ports support generation of legacy
interrupts and MSIs. The following are sources of downstream port interrupts and MSIs.
– Downstream port’s hot-plug controller
– Link bandwidth notification capability (i.e., assertion of the LBWSTS or LABWSTS bits in the
PCIELSTS register when interrupt notification is enabled for these bits)
When a downstream port is configured to generate INTx messages, only INTA is used. When an
unmasked interrupt condition occurs, then an MSI or interrupt message is generated by the corresponding
port as described in Table 3.1. The removal of the interrupt condition occurs when unmasked status bit(s)
causing the interrupt are masked or cleared.
The PES5T5 assumes that all downstream port generated MSIs are targeted to the root and routes
these transactions to the upstream port. Configuring the address contained in a downstream port’s
MSIADDR and MSIADDRU registers to an address that does not route to the upstream port and generating
an MSI produces undefined results.
Unmasked
Interrupt
Asserted1XMSI message generated
EN bit in
MSICAP
Register
00Assert_INTA message request generated to switch
INTXD bit
in PCICMD
Register
Action
core
01None
Negated1XNone
00Deassert_INTA message request generated to
switch core
01None
Table 3.1 Downstream Port Interrupts
Since memory error reporting via interrupts is an optional capability, the MSI capability structure associated with the upstream port is not by default part of the PCI capability structure link list located in the
upstream port’s configuration space. This capability may be added to the capability structure linked list by
using the serial EEPROM, SMBus or the Root to unlock registers and setting the Next Pointer (NXTPTR)
field in the PCI Power Management Capabilities (PMCAP) register to 0xD0.
Legacy Interrupt Emulation
The PES5T5 supports legacy PCI INTx emulation. Rather than use sideband INTx signals, PCIe defines
two messages that indicate the assertion and negation of an interrupt signal. An Assert_INTx message is
used to signal the assertion of an interrupt signal and an Deassert_INTx message is used to signal its negation.
PES5T5 User Manual 3 - 1January 28, 2011
Page 44
IDT Theory of Operation
Notes
The PES5T5 maintains an aggregated INTx state for each of the four interrupt signals (i.e., A through D)
at each port.
– The value of the INTA, INTB, INTC and INTD aggregated state for the entire switch may be deter-
mined by examining the corresponding field in the upstream port’s Interrupt Status (P0_INTSTS)
register.
– The aggregated INTx state for a downstream port may be determined by reading the corre-
sponding field in the port’s Interrupt Status (Px_INTSTS) register. This re gister contains the aggregated state of interrupts generated by that port (i.e., hot-plug) plus interrupt messages received
from the downstream link partner. The interrupt state reflects the state of interrupts as seen by that
port (i.e., before downstream port interrupts are mapped to upstream port interrupts).
An Assert_INTx message is sent to the root by the upstream port (i.e., port 0), when the aggregated
state of the corresponding interrupt in the upstream port transitions from a negated to an asserted state. A
Deassert_INTx message is sent to the root by the upstream port when the aggregated state of the corresponding interrupt in the upstream port transitions from an asserted to a negated state.
PCI to PCI bridges must map interrupts on the secondary side of the bridge according to the device
number of the device on the secondary side of the bridge. No mapping is performed for the PCI to PCI
bridges corresponding to downstream ports as these ports only connect to device zero. A mapping is
performed for the upstream port (i.e., port 0). This mapping for the PES5T5 is summarized in Table 3.2.
Upstream Port Interrupt (Port 0)
INTAINTBINTCINTD
Downstream
1.
Port X INTy corresponds to external downstream generated INTy interrupts and INTy interrupts generated
by the port.
1
Port
Interrupt
Table 3.2 PES5T5 Downstream to Upstream Port Interrupt Routing
Port 2 INTCPort 2 INTDPort 2 INTAPort 2 INTB
Port 3 INTBPort 3 INTCPort 3 INTDPort 3 INTA
Port 4 INTAPort 4 INTBPort 4 INTCPort 4 INTD
Port 5 INTDPort 5 INTAPort 5 INTBPort 5 INTC
If a Downstream Port goes to DL_Down status, the INTx virtual wires associated with that port are
negated, and the upstream port’s aggregate sate is updated accordingly. This may result in the upstream
port generating a Deassert_Intx message.
PES5T5 User Manual3 - 2January 28, 2011
Page 45
Chapter 4
Link Operation
®
Notes
Introduction
The PES5T5 is a 5 port switch device. The upstream port link width is configured as a x1 link width and
all the downstream ports are also configured as x1 link widths.
Polarity Inversion
Each port of the PES5T5 supports automatic polarity inversion as required by the PCIe specification.
Polarity inversion is a function of the receiver and not the transmitter. The transmitter never inverts its data.
During link training, the receiver examines symbols six through sixteen of the TS1 and TS2 ordered sets for
inversion of the PExAP[n] and PExAN[n] signals. If an inversion is detected, then logic for the receiving lane
automatically inverts received data.
Polarity inversion is a lane and not a link function. Therefore, it is possible for some linked lanes to be
inverted while others are not inverted.
Link Width Negotiation
The PES5T5 supports the optional link variable width negotiation feature for its upstream port as
outlined in the PCIe specification. During link training, upstream port is capable of negotiating to a x1 link
width. The negotiated width of the upstream link may be determined from the Link Width (LW) field in the
PCI Express Link Status (PCIELSTS) register.
The Maximum Link Width (MAXLNKWDTH) field in a port’s PCI Express Link Capabilities (PCIELCAP)
register contains the maximum link width of the port. This field is of RWL type in the upstream port and may
be modified when the REGUNLOCK bit is set in the SWCTL register. Modification of this field allows the
maximum link width of the port to be configured. The new link width takes effect the next time link training
occurs. To force a link width for the upstream port to a smaller width than the default value, the MAXLNKWDTH field could be configured through Serial EEPROM initialization and full link retraining forced.
Link Retraining
Link retraining should not cause either a downstream component or an upstream component to reset or
revert to default values.
Writing a one to the Link Retrain (LRET) bit in the upstream port’s PCI Express Link Control (PCIELCTL)
register when the REGUNLOCK bit is set in the SYSCTL register forces the upstream PCIe link to retrain.
When this occurs the LTSSM transitions directly to the Recovery state.
Writing a one to the Link Retrain (LRET) bit in a downstream port’s PCI Express Link Control
(PCIELCTL) register regardless of the REGUNLOCK bit state in the SYSCTL register forces the downstream PCIe link to retrain. When this occurs the LTSSM transitions directly to the Recovery state.
Writing a one to the Full Link Retrain (FLRET) bit in the Phy Link State 0 (PHYLSTSE 0) register of any
port forces that port’s PCIe link to retrain. When this occurs the LTSSM transitions directly to the Detect
state.
Link Down
When a link goes down, all TLPs received by that port and queued in the switch are discarded and all
TLPs received by other ports and destined to the port whose link is down are treated as Unsupported
Requests (UR). While a downstream link is down, it is possible to perform configuration read and write
operations to the PCI-PCI bridge associated with that link. When a link comes up, flow control credits are
advertised.
PES5T5 User Manual 4 - 1January 28, 2011
Page 46
IDT Link Operation
Notes
Slot Power Limit Support
The Set_Slot_Power_Limit message is used to convey a slot power limit value from a downstream
switch port or root port to the upstream port of a connected device or switch.
Upstream Port
When a Set_Slot_Power_Limit message is received by the upstream switch port, the fields in the
message are written to the PCI Express Device Capabilities (PCIEDCAP) register of that port.
– Byte 0 bits 7:0 of the message payload are written to the Captured Slot Power Limit Scale
(CSPLS) field.
– Byte 1 bits 1:0 of the message payload are written to the Captured Slot Power Limit Value
(CSPLV) field.
Downstream Port
A Set_Slot_Power_Limit message is sent by downstream switch ports when either of the following
events occur.
– A configuration write is performed to the corresponding PCIESCAP register when the link associ-
ated with the downstream port is up.
– A link associated with the downstream port transitions from a non-operational state to an opera-
tional (i.e., up) state.
Link States
The PES5T5 supports the following link states:
– L0
Fully operational link state
– L0s
Automatically entered low power state with shortest exit latency
– L1
Lower power state than L0s
May be automatically entered or directed by software by placing the device in the D3
– L2/L3 Ready
The L2/L3 state is entered after the acknowledgement of a PM_Turn_Off Message
There is no TLP or DLLP communications over a link in this state
– L2
The main power and reference clock are turned off but the auxiliary voltage is turned on. The
PES5T5 only exits this state when fundamental reset is applied (i.e., the PERSTN pin is asserted).
– L3
Link is completely unpowered and off
– Link Down
A transitional link down pseudo-state prior to L0. This pseudo-state is associated with the LTSSM
Detect, Polling, Configuration, Disabled, Loopback, and Hot-Reset states.
hot
state
PES5T5 User Manual4 - 2January 28, 2011
Page 47
IDT Link Operation
Notes
L0sL1
L0
L2/L3 Ready
L2
L3
Fundamental Reset
Hot Reset
Etc.
Link Down
Figure 4.1 PES5T5 ASPM Link Sate Transitions
Active State Power Management
The operation of Active State Power Management (ASPM) is orthogonal to power management. Once
enabled by the ASPM field in the PCI Express Link Control (PCIELCTL) register, ASPM link state transitions are initiated by hardware without software involvement.
The PES5T5 ASPM supports the required L0s state as well as the optional L1 state. The L0s Entry
Timer (L0ET) field in the PCI Power Management Proprietary Control (PMPC) register controls the amount
of time L0s entry conditions must be met before the hardware transitions the link to the L0s state.
– The upstream switch port has the following L0s entry conditions.
The receive lane of all of the switch downstream ports which are not in a low power state (i.e., D3)
and whose link is not down are in the L0s state.
The switch has no TLPs to transmit on the upstream port or there are no available flow control
credits to transmit a TLP.
There are no DLLPs pending for transmission on the upstream port.
– The downstream switch ports have the following L0s entry conditions.
The receive lane of the switch upstream port is in the L0s state.
The switch has no TLPs to transmit on the downstream port or there are no available flow control
credits to transmit a TLP.
There are no DLLPs pending for transmission on the downstream port.
The L1 Entry Timer (L1ET) field in the PCI Power Management Proprietary Control (PMPC) register
controls the amount of time L1 entry conditions must be met before the hardware transitions the link to the
L1 state. If these conditions are met and the link is in the L0 or L0s states, the hardware will request a tran-
PES5T5 User Manual4 - 3January 28, 2011
Page 48
IDT Link Operation
Notes
sition to the L1 state from its link partner. Note that L1 entry requests are only made by the PES5T5
upstream port. If the link partner acknowledges the transition, the L1 state is entered. Otherwise the L0s
state is entered.
– The upstream switch port will only request entry into the L1 state when all of the downstream ports
which are not in a low power state (i.e., D3) and whose link is not down are in the L1 state.
Link Status
Associated with each port is a Port Link Up (PxLINKUPN) status output and a Port Activity (PxACTIVEN) status output. These outputs are provided on I/O expander 4. See section I/O Expanders on page
6-6 for the operation of the I/O expander and the mapping of these status outputs to I/O expander pins.
The PxLINKUPN and PxACTIVEN status outputs may be used to provide a visual indication of system
state and activity or for debug. The PxLINKUPN output is asserted when the PCI Express data link layer is
up (i.e., when the LTSSM is in the L0, L0s, L1 or recovery states). When the data link layer is down, this
output is negated. The PxACTIVEN output is asserted whenever any TLP, other than a vendor defined
message, is transmitted or received on the corresponding port’s link. Whenever a PxACTIVEN output is
asserted, it remains asserted for at least 200 ms. Since an I/O expander output may change no more
frequently than once every 40 ms, this translates into five I/O expander update periods.
PES5T5 User Manual4 - 4January 28, 2011
Page 49
Chapter 5
General Purpose
Inputs/Outputs
®
Notes
Introduction
The PES5T5 has 11 General Purpose I/O (GPIO) pins that may be individually configured as: general
purpose inputs, general purpose outputs, or alternate functions. GPIO pins are controlled by the General
Purpose I/O Function (GPIOFUNC), General Purpose I/O Configuration (GPIOCFG), and General Purpose
I/O Data (GPIOD) registers in the upstream port’s PCI configuration space. As shown in Table 5.1, many
GPIO pins are shared with other on-chip functions. The GPIO Function (GPIOFUNC) register whether a
GPIO bit operates as a general purpose I/O or as the specified alternate function.
GPIO
Pin
0PE2RSTNReset output for downstream port 2Output
1PE4RSTNReset output for downstream port 4Output
2IOEXPINTN0SMBus I/O expander interrupt 0Input
3IOEXPINTN1SMBus I/O expander interrupt 1Input
4IOEXPINTN2SMBus I/O expander interrupt 2Input
7GPENGeneral purpose event outputOutput
9PE3RSTNReset output for downstream port 3Output
10PE5RSTNReset output for downstream port 5Output
Alternate
Function
Pin Name
Alternate Function Description
Alternate
Function
Pin Type
Table 5.1 General Purpose I/O Pin Alternate Function
After reset, all GPIO pins default to the GPIO input function. GPIO pins configured as GPIO inputs are
sampled no more frequently than once every 128 ns and may be treated as asynchronous inputs. When a
GPIO pin is configured to use the GPIO function, the unneeded alternate function associated with the pin is
held in an inactive state by internal logic. Care should be exercised when configuring the GPIO pins as
outputs since an incorrect configuration could cause damage to external components as well as the
PES5T5.
GPIO Configuration
Associated with each GPIO pin is a bit in the GPIOFUNC, GPIOCFG and GPIOD registers.
Table 5.2 summarizes the configuration of GPIO pins.
GPIOFUNCGPIOCFGPin Function
00GPIO input
01GPIO output
1don’t careAlternate function
Table 5.2 GPIO Pin Configuration
PES5T5 User Manual 5 - 1January 28, 2011
Page 50
IDT General Purpose Inputs/Outputs
Notes
GPIO Pin Configured as an Input
When configured as an input in the GPIOCFG register and as a GPIO function in the GPIOFUNC
register, the GPIO pin is sampled and registered in the GPIOD register. The value of the input pin can be
determined at any time by reading the GPIOD register. Note that the value in this register corresponds to
the value of the pin irrespective of whether the pin is configured as a GPIO input, GPIO output, or alternate
function.
GPIO Pin Configured as an Output
When configured as an output in the GPIOCFG register and as a GPIO function in the GPIOFUNC
register, the value in the corresponding bit position of the GPIOD register is driven on the pin. System
designers should treat the GPIO outputs as asynchronous outputs. The actual value of the output pin can
be determined by reading the GPIOD register.
GPIO Pin Configured as an Alternate Function
When configured as an alternate function in the GPIOFUNC register, the pin behaves as described by
the section associated with that function. The value of the alternate function pin can be determined at any
time by reading the GPIOD register.
PES5T5 User Manual5 - 2January 28, 2011
Page 51
IDT General Purpose Inputs/Outputs
PES5T5 User Manual5 - 3January 28, 2011
Page 52
IDT General Purpose Inputs/Outputs
PES5T5 User Manual5 - 4January 28, 2011
Page 53
IDT General Purpose Inputs/Outputs
PES5T5 User Manual5 - 5January 28, 2011
Page 54
IDT General Purpose Inputs/Outputs
Notes
PES5T5 User Manual5 - 6January 28, 2011
Page 55
Chapter 6
SMBus Interfaces
®
Notes
Introduction
The PES5T5 contains two SMBus interfaces. The slave SMBus interface provides full access to all software visible registers in the PES5T5, allowing every register in the device to be read or written by an
external SMBus master. The slave SMBus may a lso be used to initialize the serial EEPROM used for initialization.
The Master SMBus interface provides connection for an optional external serial EEPROM used for
initialization and optional external I/O expanders. Six pins make up each of the two SMBus interfaces.
These pins consist of an SMBus clock pin, an SMBus data pin, and 4 SMBus address pins. As shown in
Figure 6.1, the master and slave SMBuses may be used in a unified or split configuration.
PES5T5
SSMBCLK
SSMBDAT
MSMBCLK
MSMBDAT
Processor
SMBus
Master
Serial
EEPROM
(a) Unified Configuration
Hot-Plug
I/O
Expander
...
Other
SMBus
Devices
PES5T5
SSMBCLK
SSMBDAT
MSMBCLK
MSMBDAT
Processor
SMBus
Master
Serial
EEPROM
...
Hot-Plug
Expander
Other
SMBus
Devices
I/O
(b) Split Configuration
Figure 6.1 SMBus Interface Configuration Examples
In the unified configuration, shown in Figure 6.1(a), the master and slave SMBuses are tied together and
the PES5T5 acts both as an SMBus master as well as an SMBus slave on this bus. This requires that the
external SMBus master or processor that has access to the PES5T5 registers support SMBus arbitration. In
some systems, this external SMBus master interface may be implemented using general purpose I/O pins
on a processor or microcontroller, and thus may not support SMBus arbitration. To support these systems,
PES5T5 User Manual 6 - 1January 28, 2011
Page 56
IDT SMBus Interfaces
Notes
the PES5T5 may be configured to operate in a split configuration as shown in Figure 6.1(b). In the split
configuration, the master and slave SMBuses operate as two independent buses and thus multi-master
arbitration is not required.
Master SMBus Interface
The master SMBus interface is used during a fundamental reset to load configuration values from an
optional serial EEPROM. It is also used to support optional I/O expanders used for hot-plug and other
status signals.
Initialization
Master SMBus initialization occurs during a fundamental reset (see section Fundamental Reset on page
2-5). During a fundamental reset initialization sequence, the state of the Master SMBus Slow Mode
(MSMBSMODE) signal is examined. If this signal is asserted, then the Master SMBus Clock Prescalar
(MSMBCP) field in the SMBus Control (SMBUSCTL) register is initialized to support 100 KHz SMBus operation. If the signal is negated, then the MSMBCP field is initialized for 400 KHz SMBus operation.
Serial EEPROM
During a fundamental or hot reset, an optional serial EEPROM may be used to initialize any software
visible register in the device. Serial EEPROM loading occurs if the Switch Mode (SWMODE[2:0]) field
selects an operating mode that performs serial EEPROM initialization. The address used by the SMBus
interface to access the serial EEPROM is specified by the MSMBADDR[4:1] signals as shown in Table 6.1.
During initialization from the optional serial EEPROM, the master SMBus interface reads configuration
blocks from the serial EEPROM and updates corresponding registers in the PES5T5. Any PES5T5 software visible register in any port may be initialized with values stored in the serial EEPROM. Each software
visible register in the PES5T5 has a CSR system address which is formed by adding the PCI configuration
space offset value of the register to the base address of the configuration space in which the register is
located. Configuration blocks stored in the serial EEPROM use this CSR system address shifted right two
bits (i.e., configuration blocks in the serial EEPROM use doubleword CSR system addresses and not byte
CSR system addresses).
Base addresses for the PCI configuration spaces in the PES5T5 are listed in Chapter 9, Table 9.1, Base
Addresses for Port Configuration Space Registers. Since configuration blocks are used to store only the
value of those registers that are initialized, a serial EEPROM much smaller than the total size of all of the
configuration spaces may be used to initialize the device. Any serial EEPROM compatible with those listed
in Table 6.2 may be used to store the PES5T5 initialization values. Some of these devices are larger than
the total size of all of the PCI configuration spaces in the PES5T5 that may be initialized and thus may not
be fully utilized.
PES5T5 User Manual6 - 2January 28, 2011
Page 57
IDT SMBus Interfaces
Notes
Serial EEPROMSize
24C324 KB
24C648 KB
24C12816 KB
24C25632 KB
24C51264 KB
Table 6.2 PES5T5 Compatible Serial EEPROMs
During serial EEPROM initialization, the master SMBus interface begins reading bytes starting at serial
EEPROM address zero. These bytes are interpreted as configuration blocks and sequential reading of the
serial EEPROM continues until the end of a configuration done block is reached or the serial EEPROM
address rolls over from 0xFFFF to 0x0. All register initialization performed by the serial EEPROM is
performed in double word quantities.
There are three configuration block types that may be stored in the serial EEPROM. The first type is a
single double word initialization sequence. A double word initialization sequence occupies six bytes in the
serial EEPROM and is used to initialize a single double word quantity in the PES5T5. A single double word
initialization sequence consists of three fields and its format is shown in Figure 6.2. The CSR_SYSADDR
field contains the double word CSR system address of the double word to be initialized. The actual CSR
system address, which is a byte address, equals this value with two lower zero bits appended. The next
field is the TYPE field that indicates the type of the configuration block. For single double word initialization
sequence, this value is always 0x0. The final DATA field contains the double word initialization value.
Bit
7
Byte 0CSR_SYSADDR[7:0]
Byte 1
Byte 2DATA[7:0]
Byte 3DATA[15:8]
Byte 4DATA[23:16]
Byte 5DATA[31:24]
TYPE
0x0
5
6
3
4
CSR_SYSADDR[13:8]
2
0
1
Bit
Bit
Bit
Bit
Bit
Bit
Bit
Figure 6.2 Single Double Word Initialization Sequence Format
The second type of configuration block is the sequential double word initialization sequence. It is similar
to a single double word initialization sequence except that it contains a double word count that allows
multiple sequential double words to be initialized in one configuration block.
A sequential double word initialization sequence consists of four required fields and one to 65535
double word initialization data fields. The format of a sequential double word initialization sequence is
shown in Figure 6.3. The CSR_SYSADDR field contains the starting double word CSR system address to
be initialized. The next field is the TYPE field that indicates the type of the configuration block. For sequential double word initialization sequences, this value is always 0x1. The NUMDW field specifies the number
of double words initialized by the configuration block. This is followed by the number of DATA fields specified in the NUMDW field.
PES5T5 User Manual6 - 3January 28, 2011
Page 58
IDT SMBus Interfaces
Notes
Bit
7
Byte 0CSR_SYSADDR[7:0]
Byte 1
Byte 2NUMDW[7:0]
Byte 3NUMDW[15:8]
Byte 4DATA0[7:0]
Byte 5DATA0[15:8]
Byte 6DATA0[23:16]
Byte 7DATA0[31:24]
TYPE
0x1
5
6
3
4
CSR_SYSADDR[13:8]
Bit
Bit
Bit
Bit
Bit
2
0
1
Bit
Bit
...
Byte 4n+4DATAn[7:0]
Byte 4n+ 5DATAn[15:8]
Byte 4n+6DATAn[23:16]
Byte 4n+7DATAn[31:24]
...
Figure 6.3 Sequential Double Word Initialization Sequence Format
The final type of configuration block is the configuration done sequence which is used to signify the end
of a serial EEPROM initialization sequence. If during serial EEPROM initialization, an attempt is made to
initialize a register that is not defined in a configuration space (i.e., not defined in Chapter 9, Configuration
Registers), then the Unmapped Register Initialization Attempt (URIA) bit is set in the SMBUSSTS register
and the write is ignored.
The configuration done sequence consists of two fields and its format is shown in Figure 6.3. The
CHECKSUM field contains the checksum of all of the bytes in all of the fields read from the serial EEPROM
from the first configuration block to the end of this done sequence. The second field is the TYPE field which
is always 0x3 for configuration done sequences.
Bit
Bit
Bit
Bit
Bit
Bit
Bit
Bit
7
Byte 0CHECKSUM[7:0]
Byte 1
0x3
5
6
3
4
ReservedTYPE
(must be zero)
2
0
1
Figure 6.4 Configuration Done Sequence Format
The checksum in the configuration done sequence enables the integrity of the serial EEPROM initialization to be verified. Since uninitialized EEPROMs typically have a value of all ones, initialization from an
uninitialized serial EEPROM will result in a checksum mismatch. The checksum is computed in the
following manner. An 8-bit counter is initialized to zero and the 8-bit sum is computed over the configuration
bytes stored in the serial EEPROM, including the entire contents of the configuration done sequence, with
the checksum field initialized to zero.
1.
This includes the byte containing the TYPE field.
PES5T5 User Manual6 - 4January 28, 2011
1
The 1’s complement of this sum is placed in the checksum field.
Page 59
IDT SMBus Interfaces
Notes
The checksum is verified in the following manner. An 8-bit counter is cleared and the 8-bit sum is
computed over the bytes read from the serial EEPROM, including the entire contents of the configuration
1
done sequence.
The correct result should always be 0xFF (i.e., all ones). Checksum checking may be
disabled by setting the Ignore Checksum Errors (ICHECKSUM) bit in the SMBus Control (SMBUSCTL)
register.
If an error is detected during loading of the serial EEPROM, then loading of the serial EEPROM is
aborted and the RSTHALT bit is set in the SWCTL register. This allows debugging of the error condition via
the slave SMBus interface but prevents normal system operation with a potentially incorrectly initialized
device. Error information is recorded in the SMBUSSTS register. Once serial EEPROM initialization
completes, or when an error is detected, the EEPROM Done (EEPROMDONE) bit is set in the SMBus
Status (SMBUSSTS) register. A summary of possible errors during serial EEPROM initialization and
specific action taken when detected is summarized in Table 6.3.
ErrorAction Taken
Configuration Done Sequence checksum mismatch with that computed by the PES5T5
Serial EERPOM address roll-over from
0xFFFF to 0x0000
Invalid configuration block type
(only invalid type is 0x2)
An unexpected NACK is observed during a
master SMBus transaction
A misplaced START or STOP condition is
detected by the master SMBus interface
- Set RSTHALT bit in SWCTL register
- ICSERR bit is set in the SMBUSSTS register
- Abort initialization, set DONE bit in the SMBUSSTS register
- Set RSTHALT bit in SWCTL register
- ICSERR bit is set in the SMBUSSTS register
- Abort initialization, set DONE bit in the SMBUSSTS register
- Set RSTHALT bit in SWCTL register
- ICSERR bit is set in the SMBUSSTS register
- Abort initialization, set DONE bit in the SMBUSSTS register
- Set RSTHALT bit in SWCTL register
- NAERR bit is set in the SMBUSSTS register
- Abort initialization, set DONE bit in the SMBUSSTS register
- Set RSTHALT bit in SWCTL register
- LAERR bit is set in the SMBUSSTS register
- Abort initialization, set DONE bit in the SMBUSSTS register
- Set RSTHALT bit in SWCTL register
- OTHERERR bit is set in the SMBUSSTS register
- Abort initialization, set DONE bit in the SMBUSSTS register
Table 6.3 Serial EEPROM Initialization Errors
Programming the Serial EEPROM
The serial EEPROM may be programmed prior to board assembly or in-system via the slave SMBus
interface or a PCIe root. Programming the serial EEPROM via the slave SMBus is described in section
Serial EEPROM Read or Write Operation on page 6-15. A PCIe root may read and write the serial
EEPROM by performing configuration read and write transactions to the Serial EEPROM Interface
(EEPROMINTF) register.
To read a byte from the serial EEPROM, the root should configure the Address (ADDR) field in the
EEPROMINTF register with the byte address of the serial EEPROM location to be read and the Operation
(OP) field to “read.” The Busy (BUSY) bit should then be checked. If the EEPROM is not busy, then the read
operation may be initiated by performing a write to the Data (DATA) field. When the serial EEPROM read
operation completes, the Done (DONE) bit in the EEPROMINTF register is set and the busy bit is cleared.
When this occurs, the DATA field contains the byte data of the value read from the serial EEPROM.
1.
This includes the checksum byte as well as the byte that contains the type and reserved field.
PES5T5 User Manual6 - 5January 28, 2011
Page 60
IDT SMBus Interfaces
Notes
To write a byte to the serial EEPROM, the root should configure the ADDR field with the byte address of
the serial EEPROM location to be written and set the OP field to “write.” If the serial EEPROM is not busy
(i.e., the BUSY bit is cleared), then the write operation may be initiated by writing the value to be written to
the DATA field. When the write operation completes, the DONE bit is set and the busy bit is cleared.
Initiating a serial EEPROM read or write operation when the BUSY bit is set produces undefined results.
SMBus errors may occur when accessing the serial EEPROM. If an error occurs, then it is reported in the
SMBus Status (SMBUSSTS) register. Software should check for errors before and after each serial
EEPROM access.
I/O Expanders
The PES5T5 utilizes external SMBus/I2C-bus I/O expanders connected to the master SMBus interface
for hot-plug and port status signals. The PES5T5 is designed to work with Phillips PCA9555 compatible I/O
expanders (i.e., PCA9555, PCA9535, and PCA9539). See the Phillips PCA9555 data sheet for details on
the operation of this device.
An external SMBus I/O expander provides 16 bit I/O pins that may be configured as inputs or outputs.
The PES5T5 supports up to four external I/O expanders. Table 6.4 summarizes the allocation of functions
to I/O expanders. I/O expanders zero and one are used to provide hot-plug I/O signals while I/O expander
four is used to provide link status and activity LED control. I/O expander signals associated with LED
control (i.e., link status and activity) are active low (i.e., driven low when an LED should be turned on). I/O
expander signals associated with hot-plug signals are not inverted.
SMBus I/O
Expander
SectionFunction
0LowerPort 2 hot-plug
UpperPort 4 hot-plug
1LowerPort 3 hot-plug
UpperPort 5 hot-plug
2Lower
UpperPower good inputs
4LowerLink status
UpperLink activity
Table 6.4 I/O Expander Function Allocation
During the PES5T5 initialization the SMBus/I
2
C-bus address allocated to each I/O expander used in that
system configuration should be written to the corresponding IO Expander Address (IOE[0:5]ADDR) field.
The IOE[0:3]ADDR fields are contained in the I/O Expander Address 0 (IOEXPADDR0) register while the
IOE[4:5]ADDR fields are contained in the SMBus I/O Expander Address 1 (IOEXPADDR1) register.
Hot-plug outputs and I/O expanders may be initialized via serial EEPROM. Since the I/O expanders and
serial EEPROM both utilize the master SMBus, no I/O expander transactions are initiated until serial
EEPROM initialization completes.
– Since no I/O expander transactions are initiated until serial EEPROM initialization completes, it is
not possible to toggle a hot-plug output through serial EEPROM initialization (i.e., it is not possible
to cause a 0 -> 1 -> 0 transition or a 1 -> 0 -> 1 transition).
Whenever the value of an IOEXPADDR field is written, SMBus write transactions are issued to the
corresponding I/O expander by the PES5T5 to configure the device. This configuration initializes the direction of each I/O expander signal and sets outputs to their default value. Outputs for ports that are disabled
or are not implemented in that configuration are set to their negated value (e.g., the power indicator is
turned off, the link is down, there is no activity, etc.).
PES5T5 User Manual6 - 6January 28, 2011
Page 61
IDT SMBus Interfaces
Notes
The default value of I/O expander outputs is shown in Table 6.5. Note that this default value may be
modified via serial EEPROM or SMBus configuration prior to SMBus initialization by changing the state of
the PCI Express Slot Control Register (PCIESCTL) or Hot-Plug Configuration Control (HPCFGCTL).
Table 6.5 I/O Expander Default Output Signal Value
Defaul
t Value
The following I/O expander configuration sequence is issued by the PES5T5 to I/O expanders zero and
one (i.e., the ones that contain hot-plug signals).
– Write the default value of the outputs bits on the lower eight I/O expander pins (i.e., I/O-0.0 through
I/O-0.7) to I/O expander register 2.
– Write the default value of the outputs bits on the upper eight I/O expander pins (i.e., I/O-1.0
through I/O-1.7) to I/O expander register 3.
– Write value 0x0 to I/O expander register 4 (no inversion in IO-0)
– Write value 0x0 to I/O expander register 5 (no inversion in IO-1)
– Write the configuration value to select inputs/outputs in the lower eight I/O expander bits (i.e., I/O-
0.0 through I/O-0.7) to I/O expander register 6.
– Write the configuration value to select inputs/outputs in the upper eight I/O expander bits (i.e., I/
O-1.0 through I/O-1.7) to I/O expander register 7.
– Read value of I/O expander register 0 to obtain the current state of the lower eight I/O expander
bits (i.e., I/O-0.0 through I/O-0.7)
– Read value of I/O expander register 1 to obtain the current state of the upper eight I/O expander
bits (i.e., I/O-1.0 through I/O-1.7)
The following I/O expander configuration sequence is issued by the PES5T5 to I/O two (i.e., the one that
contain power good inputs).
– Write the default value of the outputs bits on the lower eight I/O expander pins (i.e., I/O-0.0 through
I/O-0.7) to I/O expander register 2.
– Write value 0x0 to I/O expander register 4 (no inversion in IO-0)
– Write value 0x0 to I/O expander register 5 (no inversion in IO-1)
– Write the configuration value to select inputs/outputs in the lower eight I/O expander bits (i.e., I/O-
0.0 through I/O-0.7) to I/O expander register 6.
– Write the configuration value to select all inputs upper eight I/O expander bits (i.e., I/O-1.0 through
I/O-1.7) to I/O expander register 7.
– Read value of I/O expander register 0 to obtain the current state of the lower eight I/O expander
bits (i.e., I/O-0.0 through I/O-0.7)
– Read value of I/O expander register 1 to obtain the current state of the upper eight I/O expander
bits (i.e., I/O-1.0 through I/O-1.7)
PES5T5 User Manual6 - 7January 28, 2011
Page 62
IDT SMBus Interfaces
Notes
The following I/O expander configuration sequence is issued by the PES5T5 to I/O expander four (i.e.,
the one that contains link up and link activity status).
– Write link up status for all ports to the lower eight I/O expander pins (i.e., I/O-0.0 through I/O-0.7)
to I/O expander register 2.
– Write link activity status for all ports to the upper eight I/O expander pins (i.e., I/O-1.0 through I/O-
1.7) to I/O expander register 3.
– Write value 0x0 to I/O expander register 4 (no inversion in IO-0)
– Write value 0x0 to I/O expander register 5 (no inversion in IO-1)
– Write the configuration value to select all outputs in the lower eight I/O expander bits (i.e., I/O-0.0
through I/O-0.7) to I/O expander register 6.
– Write the configuration value to select all outputs in the upper eight I/O expander bits (i.e., I/O-1.0
through I/O-1.7) to I/O expander register 7.
While the I/O expander is enabled, the PES5T5 maintains the I/O bus expander signals and the
PES5T5 internal view of the hot-plug signals in a consistent state. This means that whenever that I/O bus
expander state and the PES5T5 internal view of the signal state differs, an SMBus transaction is initiated by
the PES5T5 to resolve the state conflict.
– An example of an event that may lead to a state conflict is a hot reset. When a hot reset occurs,
one or more hot-plug register control fields may be re-initialized to its default value. When this
occurs, the internal PES5T5 state of the hot-plug signals is in conflict with the state of I/O
expander hot-plug output signals. In such a situation, the PES5T5 will initiate an SMBus transaction to modify the state of the I/O expander hot-plug outputs.
Each I/O expander has an open drain interrupt output that is asserted when a pin configured as an input
changes state from the value previously read. Each interrupt output from an I/O expander should be
connected to the corresponding PES5T5 I/O expander interrupt input. Since the PES5T5 I/O expander
interrupt inputs are GPIO alternate functions, the corresponding GPIOs should be initialized during configuration to operate in alternate function mode.
Whenever the PES5T5 needs to change the state of an I/O expander signal output, a master SMBus
transaction is initiated to update the state of the I/O expander. This write operation causes the corresponding I/O expander to change the state of its output(s). The PES5T5 will not update the state of an I/O
expander output more frequently than once every 40 milliseconds. This 40 millisecond time interval is
referred to as the I/O expander update period.
Whenever an input to the I/O expander changes state from the value previously read, the interrupt
output of the I/O expander is asserted. This causes the PES5T5 to issue a master SMBus transaction to
read the updated state of the I/O expander inputs. Regardless of the state of the interrupt output of the I/O
expander, the PES5T5 will not issue a master SMBus transaction to read the updated state of the I/O
expander inputs more frequently than once every 40 milliseconds (i.e., the I/O expander update period).
This delay in sampling may be used to eliminate external debounce circuitry.
The I/O expander interrupt request output is negated whenever the input values are read or when the
input pin changes state back to the value previously read. The PES5T5 ensures that I/O expander transactions are initiated on the master SMBus in a fair manner. This guarantees that all I/O expanders have equal
service latencies. Any errors detected during I/O expander SMBus read or write transactions is reflected in
the status bits of the SMBus Status (SMBUSSTS) register.
The I/O Expander Interface (IOEXPINTF) register allows direct testing and debugging of the I/O
expander functionality. The Select (SEL) field in the IOEXPINTF register selects the I/O expander number
on which other fields in the register operate. The I/O Expander Data field in the IOEXPINTF register reflect
the current state, as viewed by the PES5T5, of the I/O expander inputs and outputs selected by the SEL
field.
Writing a one to the Reload I/O Expander Signals (RELOADIOEX) bit in the IOEXPINTF register causes
the PES5T5 to generate SMBus write and read transactions to the I/O expander number selected in the
SEL field. This results in the value of the IOEDATA field being updated to reflect the current state of the
corresponding I/O expander signals. This feature may be used to aid in debugging I/O expander operation.
PES5T5 User Manual6 - 8January 28, 2011
Page 63
IDT SMBus Interfaces
Notes
For example, a user who neglects to configure a GPIO as an alternate function may use this feature to
determine that master SMBus transactions to the I/O expander function properly and that the issue is with
the interrupt logic.
The IO Expander Test Mode (IOEXTM) bit in the IOEXPTINF register allows an I/O expander test mode
to be entered. When this bit is set, the PES5T5 core logic outputs are ignored and the values written to the
I/O expander for output bits are the values in the IOEDATA field. In this mode, the PES5T5 issues a transaction to update the state of the I/O expander whenever a bit corresponding to an I/O expander output
changes state due to a write to the IOEDATA field. Bits in the IOEDATA field that correspond to outputs are
dependent on the I/O expander number selected in the SEL field in the IOEXPINTF register. The outputs for
each I/O expander number are shown in Table 6.6 through 6.9.
System design recommendations:
– I/O expander addresses and default output values may be configured during serial EEPROM
initialization. If I/O expander addresses are configured via the serial EEPROM, the PES5T5 will
initialize the I/O expanders when normal device operation begins following the completion of the
fundamental reset sequence.
– If the I/O expanders are initialized via serial EEPROM, the data value for output signals during the
SMBus initialization sequence will correspond to those at the time the SMBus transactions are
initiated. It is not possible to toggle SMBus I/O expander outputs by modifying data values during
serial EEPROM initialization.
– During a fundamental reset and before the I/O expander outputs are initialized, all I/O expander
output signals default to inputs. Therefore, pull-up or pull-down resistors should be placed on
outputs to ensure that they are held in the desired state during this period.
– All hot-plug data value modifications that correspond to hot-plug outputs result in SMBus transac-
tions. This includes modifications due to upstream secondary bus resets and hot-resets.
– I/O expander outputs are not modified when the device transitions from normal operation to a
fundamental reset. In systems where I/O expander output values must be reset during a fundamental reset, a PCA9539 I/O expander should be used.
I/O-x.y corresponds to the notation used for PCA9555 port x I/O pin y.
I/O Expander 2
SMBus I/O
Expander
Bit
0 (I/O-0.0)
1
1 (I/O-0.1)IReservedTie High
2 (I/O-0.2)IReservedTie High
TypeSignalDescription
IReservedTie High
Table 6.8 I/O Expander 2 Signals (Part 1 of 2)
PES5T5 User Manual6 - 10January 28, 2011
Page 65
IDT SMBus Interfaces
Notes
SMBus I/O
Expander
TypeSignalDescription
Bit
3 (I/O-0.3)IReservedTie High
4 (I/O-0.4)OReservedTie High or Low
5 (I/O-0.5)OReservedTie High or Low
6 (I/O-0.6)OReservedTie High or Low
7 (I/O-0.7)OReservedTie High or Low
8 (I/O-1.0)IReservedTie High
9 (I/O-1.1)IReservedTie High
10 (I/O-1.2)IP2PWRGDNPort 2 power good input
11 (I/O-1.3)IP3PWRGDNPort 3 power good input
12 (I/O-1.4)IP4PWRGDNPort 4 power good input
13 (I/O-1.5)IP5PWRGDNPort 5 power good input
14 (I/O-1.6)OReservedTie High or Low
15 (I/O-1.7)OReservedTie High or Low
Table 6.8 I/O Expander 2 Signals (Part 2 of 2)
1.
I/O-x.y corresponds to the notation used for PCA9555 port x I/O pin y.
I/O Expander 4
SMBus I/O
Expander
Bit
0 (I/O-0.0)
1
1 (I/O-0.1)OReservedTie High or Low
2 (I/O-0.2)OP2LINKUPNPort 2 link up status output
3 (I/O-0.3)OP3LINKUPNPort 3 link up status output
4 (I/O-0.4)OP4LINKUPNPort 4 link up status output
5 (I/O-0.5)OP4LINKUPNPort 5 link up status output
6 (I/O-0.6)OReservedTie High or Low
7 (I/O-0.7)OReservedTie High or Low
8 (I/O-1.0)OP0ACTIVENPort 0 activity output
9 (I/O-1.1)OReservedTie High or Low
10 (I/O-1.2)OP2ACTIVENPort 2 activity output
13 (I/O-1.5)OP5ACTIVENPort 5 activity output
14 (I/O-1.6)OReservedTie High or Low
15 (I/O-1.7)OReservedTie High or Low
Table 6.9 I/O Expander 4 Signals
1.
I/O-x.y corresponds to the notation used for PCA9555 port x I/O pin y.
PES5T5 User Manual6 - 11January 28, 2011
Page 66
IDT SMBus Interfaces
Notes
Slave SMBus Interface
The slave SMBus interface provides the PES5T5 with a configuration, management and debug interface. Using the slave SMBus interface, an external master can read or write any software visible register in
the device.
Initialization
Slave SMBus initialization occurs during a fundamental reset (see section Fundamental Reset on page
2-5). During the fundamental reset initialization sequence, the slave SMBus address is initialized. The
address is specified by the SSMBADDR[5,3:1] signals as shown in Table 6.10.
Table 6.10 Slave SMBus Address When a Static Address is Selected.
SMBus Transactions
The slave SMBus interface responds to the following SMBus transactions initiated by an SMBus master.
See the SMBus 2.0 specification for a detailed description of these transactions.
– Byte and Word Write/Read
– Block Write/Read ( supports block transfer of only 32 bits )
The SMBus Slave Block transfers are limited to 32 bits. If more than one double word is transferred then
only the last double word is written to the configuration register. Initiation of any SMBus transaction other
than those listed above to the slave SMBus interface produces undefined results. Associated with each of
the above transactions is a command code. The command code format for operations supported by the
slave SMBus interface is shown in Figure 6.5 and described in Table 6.11.
Bit
7
Bit
6
Bit
5
Bit
4
Bit
3
Bit
2
Figure 6.5 Slave SMBus Command Code Format
Bit
1
Bit
0
ENDSTARTFUNCTIONSIZEPEC
PES5T5 User Manual6 - 12January 28, 2011
Page 67
IDT SMBus Interfaces
Notes
Bit
Field
0ENDEnd of transaction indicator. Setting both START and END signifies a
1STARTStart of transaction indicator. Setting both START and END signifies
4:2FUNCTIONThis field encodes the type of SMBus operation.
6:5SIZEThis field encodes the data size of the SMBus transaction.
7PECThis bit controls whether packet error checking is enabled for the cur-
NameDescription
single transaction sequence
0 - Current transaction is not the last read or write sequence.
1 - Current transaction is the last read or write sequence.
a single transaction sequence
0 - Current transaction is not the first of a read or write sequence.
1 - Current transaction is the first of a read or write sequence.
0 - CSR register read or write operation
1 - Serial EEPROM read or write operation
2 through 7 - Reserved
0 - Byte
1 - Word
2 - Block
3 - Reserved
rent SMBus transaction.
0 - Packet error checking disabled for the current SMBus transaction.
1 - Packet error checking enabled for the current SMBus transaction.
Table 6.11 Slave SMBus Command Code Fields
The FUNCTION field in the command code indicates if the SMBus operation is a CSR register read/
write or a serial EEPROM read/write operation. Since the format of these transactions is different, the transactions will be described individually in the following sections. If a command is issued while one is already
in progress or if the slave is unable to supply data associated with a command, then the command is
NACKed. This indicates to the master that the transaction should be retried.
CSR Register Read or Write Operation
Table 6.12 indicates the sequence of data as it is presented on the slave SMBus following the byte
address of the Slave SMBus interface.
Byte
Position
0CCODECommand Code. Slave Command Code field described in Table
1BYTCNTByte Count. The byte count field is only transmitted for block type
2CMDCommand. This field encodes fields related to the CSR register read
Field
NameDescription
6.11.
SMBus transactions. SMBus word and byte accesses do not contain
this field. The byte count field indicates the number of bytes following
the byte count field when performing a write or setting up for a read.
The byte count field is also used when returning data to indicate the
number of following bytes (including status). Note that the byte count
field does not include the PEC byte if PEC is enabled.
or write operation.
Table 6.12 CSR Register Read or Write Operation Byte Sequence
PES5T5 User Manual6 - 13January 28, 2011
Page 68
IDT SMBus Interfaces
Notes
Byte
Position
Field
NameDescription
3ADDRLAddress Low. Lower 8-bits of the doubleword CSR system address
of register to access.
4ADDRUAddress Upper. Upper 6-bits of the doubleword CSR system
address of register to access. Bits 6 and 7 in the byte must be zero
and are ignored by the hardware.
5DATALLData Lower. Bits [7:0] of data doubleword.
6DATALMData Lower Middle. Bits [15:8] of data doubleword.
7DATAUMData Upper Middle. Bits [23:16] of data doubleword.
8DATAUUData Upper. Bits [31:24] of data doubleword.
Table 6.12 CSR Register Read or Write Operation Byte Sequence
The format of the CMD field is shown in Figure 6.6 and described in Table 6.13.
Bit
7
Bit
6
Bit
5
Bit
4
Bit
3
Bit
2
Bit
1
Figure 6.6 CSR Register Read or Write CMD Field Format
Bit
0
BELLBELMWERRBEUMBEUUOPRERR0
Bit
Field
NameTypeDescription
0BELLRead/WriteByte Enable Lower. When set, the byte enable for bits [7:0] of the
data word is enabled.
1BELMRead/WriteByte Enable Lower Middle. When set, the byte enable for bits [15:8]
of the data word is enabled.
2BEUMRead/WriteByte Enable Upper Middle. When set, the byte enable for bits
[23:16] of the data word is enabled.
3BEUURead/WriteByte Enable Upper. When set, the byte enable for bits [31:24] of the
data word is enabled.
4OPRead/WriteCSR Operation. This field encodes the CSR operation to be per-
formed.
0 - CSR write
1 - CSR read
50 0Reserved. Must be zero.
6RERRRead-Only
and Clear
Read Error. This bit is set if the last CSR read SMBus transaction
was not claimed by a device. Success indicates that the transaction
was claimed and not that the operation completed without error.
7WERRRead-Only
and Clear
Write Error. This bit is set if the last CSR write SMBus transaction
was not claimed by a device. Success indicates that the transaction
was claimed and not that the operation completed without error.
Table 6.13 CSR Register Read or W rite CMD Field Description
PES5T5 User Manual6 - 14January 28, 2011
Page 69
IDT SMBus Interfaces
Notes
Serial EEPROM Read or Write Operation
Table 6.13 indicates the sequence of data as it is presented on the slave SMBus following the byte
address of the Slave SMBus interface.
Byte
Positio
n
0CCODECommand Code. Slave Command Code field described in Table
1BYTCNTByte Count. The byte count field is only transmitted for block type
2CMDCommand. This field contains information related to the serial
3EEADDRSerial EEPROM Address. This field specifies the address of the
4ADDRLAddress Low. Lower 8-bits of the Serial EEPROM byte to access.
5ADDRUAddress Upper. Upper 8-bits of the Serial EEPROM byte to access.
6DATAData. Serial EEPROM value read or to be written.
Field
Name
Description
6.11.
SMBus transactions. SMBus word and byte accesses do not contain
this field. The byte count field indicates the number of bytes following
the byte count field when performing a write or setting up for a read.
The byte count field is also used when returning data to indicate the
number of following bytes (including status).
EEPROM transaction.
Serial EEPROM on the Master SMBus when the USA bit is set in the
CMD field. Bit zero must be zero and thus the 7-bit address must be
left justified.
Table 6.14 Serial EEPROM Read or Write Operation Byte Sequence
The format of the CMD field is shown in Figure 6.7 and described in Table 6.15.
Bit
7
Bit
6
Bit
5
Bit
4
Bit
3
Bit
2
Bit
1
Figure 6.7 Serial EEPROM Read or Write CMD Field Format
Bit
0
OPUSA0NAERRLAERROTHERERR0
PES5T5 User Manual6 - 15January 28, 2011
Page 70
IDT SMBus Interfaces
Notes
Bit
Field
NameType
1
Description
0OP RWSerial EEPROM Operation. This field encodes the serial EEPROM
operation to be performed.
0 - Serial EEPROM write
1 - Serial EEPROM read
1USA RWUse Specified Address. When this bit is set the serial EEPROM
SMBus address specified in the EEADDR is used instead of that
specified in the ADDR field in the EEPROMINTF register.
When this bit is set the serial EEPROM SMBus address specified in
the EEADDR is used instead of that specified in the MSMBADDR
field in the SMBUSSTS register.
2ReservedReserved field.
3NAERRRCNo Acknowledge Error. This bit is set if an unexpected NACK is
observed during a master SMBus transaction when accessing the
serial EEPROM. This bit has the same function as the NAERR bit in
the SMBUSSTS register.
The setting of this bit may indicate the following: that the addressed
device does not exist on the SMBus (i.e., addressing error), data is
unavailable or the device is busy, an invalid command was detected
by the slave, invalid data was detected by the slave.
4LAERRRCLost Arbitration Error. This bit is set if the master SMBus interface
loses 16 consecutive arbitration attempts when accessing the serial
EEPROM. This bit has the same function as the LAERR bit in the
SMBUSSTS register.
5OTHERERR RC Other Error. This bit is set if a misplaced START or STOP condition
is detected by the master SMBus interface when accessing the serial
EEPROM. This bit has the same function as the OTHERERR bit in
the SMBUSSTS register.
7:6Reserved0Reserved. Must be zero.
Table 6.15 Serial EEPROM Read or Write CMD Field Description
1.
See Table 2 in the About this Manual chapter for a definition of these abbreviations.
Sample Slave SMBus Operation
This section illustrates sample Slave SMBus operations. Shaded items are driven by the PES5T5’s
slave SMBus interface and non-shaded items are driven by an SMBus host.
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
Wr A
Wr A
Wr A
ADDRU
Figure 6.8 CSR Register Read Using SMBus Block Write/Read Transactions with PEC Disabled
A
CCODE
START,END
CCODE
START,END
CCODE
START,END
BYTCNT=3
A
(PES5T5 not ready with data)
N
P
PES5T5 Slave
A
S
SMBus Address
DATALMDATALL
ANP
CMD=read
A
BYTCNT=7
A
Rd
DATAUM
ADDRL
A
AAA
DATAUU
A
A
N
ADDRU
A P
ADDRLCMD (status)
PES5T5 User Manual6 - 16January 28, 2011
Page 71
IDT SMBus Interfaces
Notes
PES5T5 Slave
S
SMBus Address
Wr AA
CCODE
START,END
BYTCNT=4
CMD=read
A
EEADDR
A
ADDRL
A
A
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
ADDRU
ADDRL
Wr A
Wr A
A
A
P
CCODE
START,END
CCODE
START,END
(PES5T5 not ready with data)
N
P
PES5T5 Slave
A
S
SMBus Address
DATAADDRU
AP
N
BYTCNT=5
Rd
A
AAA
EEADDRCMD (status)
Figure 6.9 Serial EEPROM Read Using SMBus Block Write/Read Transactions with PEC Disabled
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
Wr A
Wr A
Wr A
CCODE
START,END
CCODE
START,END
CCODE
START,END
(PES5T5 busy with previous command, not ready for a new command)
N P
(PES5T5 busy with previous command, not ready for a new command)
N P
A
BYTCNT=7
CMD=write
A
ADDRL
A
A
ADDRU
A
DATALL
DATALM
A
DATAUM
A
DATAUU
A
A P
Figure 6.10 CSR Register Write Using SMBus Block Write Transactions with PEC Disabled
PES5T5 Slave
S
SMBus Address
Wr AA
ADDRU
A
CCODE
START,END
DATA
A P
BYTCNT=5
CMD=write
A
EEADDR
A
ADDRL
A
Figure 6.11 Serial EEPROM Write Using SMBus Block Write Transactions with PEC Disabled
PES5T5 Slave
S
SMBus Address
Wr A
ADDRU
A
CCODE
START,END
DATA
BYTCNT=5
A
AP
PEC
A
A
CMD=write
EEADDR
A
ADDRL
A
Figure 6.12 Serial EEPROM Write Using SMBus Block Write Transactions with PEC Enabled
A
A
PES5T5 User Manual6 - 17January 28, 2011
Page 72
IDT SMBus Interfaces
Notes
PES5T5 Slave
S
SMBus Address
Wr A
CCODE
START, Word
CMD=read
A
ADDRL
A
A
P
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
SMBus Address
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
PES5T5 Slave
S
SMBus Address
Wr A
Wr
Wr A
Rd
Wr
Rd
Wr
Rd
Wr
CCODE
END, Byte
CCODE
A
START,Word
CCODE
START,Word
A
CCODE
A
Byte
ADDRU
AS
CCODE
A
Word
AA
CCODE
A
END, Word
ADDRU
A
(PES5T5 not ready with data)
N P
A
ADDRLCMD (status)
AN
A
A P
A
DATALMDATALL
A
A
P
P
N
P
PES5T5 Slave
S
SMBus Address
Rd
AA
DATAUUDATAUM
N
P
Figure 6.13 CSR Register Read Using SMBus Read and Write Transactions with PEC Disabled
PES5T5 User Manual6 - 18January 28, 2011
Page 73
Chapter 7
Power Management
®
Notes
Introduction
The PES5T5 supports the following device power management states: D0 Uninitialized, D0 Active,
D3
, and D3
Hot
is provided in Figure 7.1 and described in Table 7.1.
A power management capability structure is located in the configuration space of each PCI-PCI bridge
in the PES5T5. The power management capability structure associated with a PCI-PCI bridge of a downstream port only affects that port. Entering the D3
the L1 state. The power management capability structure associated with the upstream port (i.e., port 0)
affects the entire device. The PES5T5 supports the link Wakeup mechanism. It supports both in-band
Beacon signaling (transmission only, not detection) and side band WAKEN signaling. The Wakeup Protocol
requires the Vaux power supply to be ON.
The functional context is maintained in the D3
Power Management Control and Status Register (PMCSR) is set to 1. The internal logic and the contents of
the registers are maintained and the software is not required to re-initialize the device on transitions from
D3
to D0. Thus, the default value of the NOSOFTRST bit in the PMCSR register corresponds to the
Hot
functional context being maintained in the D3
Ready state regardless of the NOSOFTRST bit settings, and the software will have to re-initialize the
device.
. A power management state transition diagram for the states supported by the PES5T5
Cold
state allows the link associated with the bridge to enter
Hot
state if the No_Soft_Reset (NOSOFTRST) bit in the
Hot
state. However, the device is reset if the link enters L2/L3
Hot
Power-On Reset
D0
Uninitialized
D0
Active
D3
hot
Wakeup Protocol
D3
cold
Figure 7.1 PES5T5 Power Management State Transition Diagram
PES5T5 User Manual 7 - 1January 28, 2011
Page 74
IDT Power Management
Notes
From StateTo StateDescription
AnyD0 UninitializedPower-on fundamental reset.
D0 UninitializedD0 ActivePCI-PCI bridge configured by software.
D0 ActiveD3
D0 UninitializedThe Power Management State (PMSTATE) field in the PCI Power
D3
D0 UninitializedThe device transitions to the D0 Uninitialized state when the system
Table 7.1 PES5T5 Power Management State Transition Diagram
D3
D3
D3
Hot
Hot
Cold
Hot
Cold
The Power Management State (PMSTATE) field in the PCI Power
Management Control and Status (PMCSR) register is written with the
value that corresponds to the D3
Management Control and Status (PMCSR) register is written with the
value that corresponds to D0 state.
Power is removed from the device.
reinstalls device power and clock and applies a fundamental reset in
response to the Wakeup Protocol. The Wakeup mechanism is powered by the Vaux power supply.
Hot
state.
The PES5T5 PCI-to-PCI bridges (i.e., ports) have the following behavior when in the D3
management state.
– A bridge accepts, processes, and completes all type 0 configuration read and write requests.
– A bridge accepts and processes all message requests that target the bridge.
– All requests received by the bridge on the primary interface, except as noted above, are treated
as unsupported requests (UR).
– Any error message resulting from the receipt of a TLP is reported in the same manner as when
the bridge is not in the D3
state (e.g., generation of an ERR_NONF AT AL message t o the root).
Hot
– Error messages resulting from any event other than the receipt of a TLP are discarded (i.e., no
error message is generated).
– All completions that target the bridge are treated as unexpected completions (UC).
– Completions flowing in either direction through the bridge are routed as normal. This behavior of
the bridge does not differ from that of the bridge when it is in the D0 power management state.
– All request TLPs received on the secondary interface are treated as unsupported requests (UR).
Hot
power
PME Messages
Downstream ports (i.e., PCI-PCI bridges associated with downstream ports) support the generation of
hot-plug PME events (i.e., a PM_PME power management message) from the D3
both the case when the downstream port is in the D3
state or the entire switch is in the D3
Hot
The generation of a PME message by downstream ports necessitates the implementation of a PME
service time-out mechanism to ensure that PME messages are not lost. After a PM_PME message is transmitted, if the PME Status (PMES) bit in the downstream port’s PCI Power Management Control and Status
(PMCSR) register is not cleared within the time-out period specified in the PM_PME Time-Out (PMPMETO)
field in the port’s PM_PME Timer (PMPMETIMER) register, then the PM_PME message is retransmitted
and the timer is restarted.
If the PES5T5 issues a hot plug PME message but the PME_Status is not cleared before the link enters
a deep sleep state in response to PME_Turn_Off message, it reactivates the link using the wakeup mechanism ( refer to section Wakeup Protocol on page 7-4).
PES5T5 User Manual7 - 2January 28, 2011
state. This includes
Hot
state.
Hot
Page 75
IDT Power Management
Notes
Power Express Power Management Fence Protocol
The Root complex takes the following steps to turn off power to a system:
– The root places all devices in the D3
– Upon entry to D3
, all devices transition their links to the L1 state
Hot
– The root broadcasts a PME_Turn_Off message
– Devices acknowledge the PME_Turn_Off message by returning a PME_TO_ACK message.
When the PES5T5 receives a PME_Turn_Off message it broadcasts the PME_Turn_Off message on all
active downstream ports. Prior to sending PME_TO_Ack response back, the upstream port starts aggregating PME_TO_Ack response from all the downstream ports. After it has received a PME_TO_Ack
message on each of its downstream ports, the PES5T5 transmits a PME_TO_Ack message on its
upstream port and transitions its upstream link to L2/L3 Ready state.
The aggregation of PME_TO_Ack messages on downstream ports is abandoned when the upstream
port receives a TLP after receiving a PME_Turn_Off message on that port, but before it has responded with
a PME_TO_Ack message. Once a PME_TO_Ack message has been scheduled for transmission on the
upstream port, there is no need to abandon PME_TO_Ack aggregation, and received TLPs at that point
may be discarded.
If the TLP that causes PME_TO_Ack aggregation to be abandoned targets the PES5T5, the PES5T5
responds to the TLP normally. If the TLP that causes aggregation to be abandoned targets a downstream
port and the port is in L0, the TLP is transmitted on the downstream port. If the downstream port is not in L0
(i.e., it is in L2/L3 Ready), the switch transitions the link to Detect and then to L0. Once the link reaches L0,
the TLP is transmitted on the downstream port.
When PME_TO_Ack aggregation is abandoned, the PES5T5 makes no attempt to abandon the
PME_Turn_Off and PME_TO_Ack protocol on downstream ports. Devices downstream of the PES5T5 are
allowed to respond with a PME_TO_Ack and to transition to L2/L3 Ready. When the PES5T5 receives a
TLP (targeting switch or downstream devices) during the PME aggregation process, it waits for the arrival of
PME_TO_Ack from all the downstream ports before initiating link retraining on all the downstream ports.
The received TLP is sent to the destination port after the links retrain.
Hot
state
In order to avoid deadlock, a downstream port that does not receive a PME_TO_Ack message in the
time-out period specified in the PME_TO_Ack Time-Out (PMETOATO) field in the PME_TO_Ack Timer
(PMETOATIMER) register, declares a time-out, transitions its link to L2/L3 Ready state and signals to the
upstream port that a PME_TO_Ack message has been received. Upon receiving a PME_Turn_Off
message, the PES5T5 blocks the transmission of PM_PME messages. If instead of being transitioned to
the D3
state, the PES5T5 is transitioned to the D0
cold
uninitialized
state, then the PES5T5 resumes generation
of PM_PME messages.
Power Budgeting Capability
The PES5T5 contains the mechanisms necessary to implement the PCI express power budgeting
enhanced capability. However, by default, these mechanisms are not enabled. To enable the power
budgeting capability, registers in this capability should be initialized and the Next Pointer (NXTPTR) field in
one of the other enhanced capabilities should be initialized to point to the power budgeting capability. The
Next Pointer (NXTPTR) of the power budgeting capability should be adjusted if necessary.
The power budgeting capability consists of the four power budgeting capability registers defined in the
PCIe 1.0a base specification and eight general purpose read-write registers. See section Power Budgeting
Enhanced Capability on page 9-49 for a description of these registers.
The Power Budgeting Capabilities (PWRBCAP) register contains the PCI express enhanced capability
header for the power budgeting capability. By default, this register has an initial read-only value of zero. To
enable the power budgeting capability, this register should be initialized via the serial EEPROM.
The Power Budgeting Data Value [0..9] (PWRBDV[0..9) registers are used to hold the power budgeting
information for that port in a particular operating condition. The PWRBDV registers may be read and written
when the Power Budgeting Data Value Unlock (PWRBDVUL) bit is set in the Switch Control (SWCTL)
PES5T5 User Manual7 - 3January 28, 2011
Page 76
IDT Power Management
Notes
register. When the PWRBDVUL bit is cleared, these register are read-only and writes to these registers are
ignored. To enable the power budgeting capability, the PWRBDV registers should be initialized with power
budgeting information via the serial EEPROM.
Wakeup Protocol
The PES5T5 supports the PCIe link wakeup protocol when the following conditions are met:
– Auxiliary Power is turned on
– The PES5T5 is enabled for auxiliary power consumption
– PMEE bit in the Power Management Control and Status Register is set.
The PES5T5 supports both in-band Beacon signaling (transmission only) and the WAKEN side band
signal to initiate
– PES5T5 has the ability to initiate the wakeup protocol via assertion of the WAKEN signal or in-
– PES5T5 has the ability to translate and propagate the WAKEN input signal to in-band Beacon
– PES5T5 does not support reception of the in-band Beacon signal.
The WAKEN signal mechanism and Beacon signal mechanism are enabled by default. Both of these
mechanisms can be disabled by clearing the WAKEEN and BCONEN bits in wakeup protocol control
(WAKEUPCNTL) register. The PES5T5 uses auxiliary voltage to power WAKEN and Beacon generation
circuitry besides retaining PME context. The PME context comprises the contents of Power Management
Status and control register.
The AUXPD bit in the PCI Express Device status (PCIEDSTS) register records the status of the auxiliary
supply. If the auxiliary voltage is present, this bit is set, otherwise it is reset. Powering down of the PCIe
hierarchy adheres to the following sequence of events:
– On receiving PME_Turn_Off message, Upstream port forwards the message to all the active
– Upstream waits for PME_TO_Ack message from all the downstream ports.
– On receiving PME_TO_Ack messages from all the downstream ports, Upstream port sends
– The upstream port sends PM_Enter_L23 DLLP to the upstream component and waits for the
– On receving acknowledgement for the PM_Enter_L23 DLLP on the upstream port, the SerDes for
The PME_Status (PMES) bit in the PMCSR register is sticky and the PES5T5 maintains its value as part
of the PME Context through reset. If this bit is set and is not cleared by software before the link prepares to
enter non-communicating state in response to the receipt of PME_Turn_Off message, the PES5T5 initiates
the wakeup protocol. Once the link is retrained and reactivated, the PES5T5 sends a PME message to the
root complex.
The WAKEN signal can be used as input or an output. The direction of the WAKEN signal can be
changed by programming the WAKEDIR bit in the Switch Control (SWCTL) register. The programmed
direction of the WAKEN signal is maintained in D3cold state as long as auxiliary power supply is available
and the wakeup protocol enabled.
or propagate the wakeup protocol.
band beacon signal transmission.
output signaling.
downstream ports
PME_TO_Ack to the root complex. In case PME_TO_Ack is not received from downstream port
within time period specified in PME_TO_Ack timer register, the upstream port p roceeds ahead as
if the PME_TO_Ack message has been received by all the downstream ports.
acknowledgement. Also, the downstream ports acknowledge the PM_Enter_L23 DLLPs received
from the downstream components.
the upstream port and downstream ports are turned off (i.e., the links are placed in L23-Ready
state).
PES5T5 User Manual7 - 4January 28, 2011
Page 77
IDT Power Management
Notes
WAKEN Signal as an Input
The WAKEN signal may be configured as an input to make use of the PES5T5’s ability to translate
WAKEN input to Beacon transmission (on the upstream link). To enable this feature, the following must be
true:
– The WAKEDIR bit in the SWCTL register must be 0x0.
– The WAKEEN bit in the WAKEUP register is set.
– The BCONEN bit in the WAKEUP register is set.
– Auxiliary power is ON.
– Auxiliary power consumption is enabled (APWREN bit is set in the Switch Control register).
– The PMEE bit in the PMCSR register of the upstream port is set.
On receiving WAKEN signal, the PES5T5 propagates transmission of the in-band beacon signal on the
upstream link until a break in electrical idle is detected in this link.
WAKEN Signal as an Output
The WAKEN signal may be configured as an output when it is desired that the PES5T5 initiate the
wakeup protocol by asserting this signal. In order to enable the WAKEN signal as an output, the following
must be true:
– The WAKEDIR bit in the SWCTL register must be 0x1.
– The WAKEEN bit in the WAKEUP register is set.
– Auxiliary power is ON
– Auxiliary power consumption is enabled (APWREN bit is set in Switch Control register)
– PMEE bit in the PMCSR register in the associated downstream port is set.
WAKEN and Beacon Disabled
When both the WAKEN and Beacon signalling mechanisms are disabled, the PES5T5 wakeup protocol
mechanism is disabled.
Auxiliary Power Implementation
Switch System States
The PES5T5 system states are determined by the main power and auxiliary power supply ON/OFF state
as shown in Figure 7.2.
Active Standby
Any State
Device OFF
Main Power Off
Auxiliary Power Off
Device ON
Main Power ON
Main Power Off
Auxiliary Power ON
Aux Pwr Enabled
Inactive Standby
Main Power Off
Auxiliary Power ON
Aux Pwr Disabled
Figure 7.2 PES5T5 System States
PES5T5 User Manual7 - 5January 28, 2011
Page 78
IDT Power Management
Notes
In Device OFF state, both main power and the auxiliary power is off.
The device enters Inactive Standby when the auxiliary power is applied and Main Power is Off. When
main power is applied the device enters the Device ON state. As shown in Figure 7.3, when main power is
applied for the first time after auxiliary power is switched ON, the external POR circuitry is required to assert
PERSTN and sequence the APWRDISN signal with respect to PERSTN . The internal logic utilizes this
external POR driven sequence to build a capability to determine whether switch was in L2 state or not at the
time of application of fundamental reset.
If the APWRDISN signal is low after 8 clock cycles from de-assertion of PERSTN then it implies that the
device was not in L2 state when fundamental reset was applied. All the FRSticky bits are initialized in this
case. If APWRDISN signal is high after 8 clock cycles from de-assertion of PERSTN then all the FRSticky
bits are preserved.
The state of APWRDISN signal after 256 clocks of de-assertion of PERSTN is used to initialize the
APWREN bit in the switch control register. If the signal is low, APWREN bit is ‘0’ indicating that the L2 mode
has been disabled. Otherwise, APWREN bit is set.
The PME Enable bit controls the ability of the device to raise PME events from D3cold state . Only
devices that are enabled to generate PME events from D3cold are allowed to utilize auxiliary power supply .
The auxiliary power can be used only if the Auxiliary Power Detected (AUXPD) bit is set in the PCI
Express Device Status register. The Auxiliary Power Enable bit (APWREN) in the Switch Control (SWCTL)
register controls setting or resetting of this bit as described in section section Auxiliary Power Control on
page 7-6 . The L2 mode is enabled only when both AUXPD bit in PCIESTS and PMEE bit PMCSR register
are set. If L2 mode is enabled and main power is removed, the switch enters Active Standby.
When the main power rail is switched OFF and auxiliary power rail is ON then the switch can enter
Active or Inactive standby depending upon whether auxiliary power is enabled. If the auxiliary power is
enabled then the switch enters Active standby and all the FRSticky register bits are saved along with
powering ON of the internal Wake and Beacon sensing and generation logic. Otherwise, the device enters
InActive standby and the FRSticky register bits are not saved. The internal Wake and Beacon logic is not
powered ON in this state.
The normal configuration register fields (RW, RO, etc.) are set to the initial value as a result of any type
of reset. The Sticky and RWL fields are preserved across hot and secondary bus resets. The FRSticky
fields are preserved across all resets (hot, warm, cold). The FRSticky fields are reset when main power is
applied for the first time after auxiliary power is turned ON as shown in Figure 7.3.
Auxiliary Power Control
The PES5T5 supports the Auxiliary Power Disable (APWRDISN) input pin that is used to enable/disable
the Auxiliary Power Usage.
PES5T5 User Manual7 - 6January 28, 2011
Page 79
IDT Power Management
Notes
APWRDISN
PERSTN
256 Clks
8 Clks
a. L2 Mode Enabled, FRSticky bits initialized
APWRDISN
(High)
PERSTN
256 Clks
8 Clks
APWRDISN
(Low)
PERSTN
8 Clks
Figure 7.3 L2 Mode Enable/Disable and FRSticky Bit Initialization
b. L2 Mode Enabled, FRSticky bits not initialized
256 Clks
b. L2 Mode Disabled
If the APWRDISN signal is inactive (High) 256 clocks after de-assertion of the fundamental reset, the
Auxiliary Power Enable (APWREN) bit is set in the SWCTL register. If th e APWRDISN signal is act ive (Low)
256 clocks after de-assertion of the fundamental reset, the APWREN bit is reset and auxiliary power usage
is disabled.
The AUXPD bit in the PCI Express Device Status register is set only when the APWREN bit in the
Switch Control Register is set to ‘1’. Based on the supported auxiliary power usage model shown in Figure
7.5, the PES5T5 does not sense an auxiliary power presence on the power pin. The Auxiliary Power Usage
could also be enabled, given that the PMEE bit is set in the PMCSR register, by setting the APWREN bit in
the Switch Control once the system comes up. In order for proper transition to/from L2 mode, it is assumed
that the software also correctly sets the state of APWRDISN when enabling the APWREN bit.
L2 Mode Enabled, FRSticky Bits Initialized
The corresponding signal sequence for this state transition is shown in Figure 7.3(a). The external POR
circuitry initiates this sequence on APWRDISN when the main power is first switched ON after the auxiliary
power is turned ON. The APWRDISN signal input is sampled 8 clock cycles after de-assertion of the fundamental reset (PERSTN). A low state of this signal triggers initialization of the FRSticky bits. The
APWRDISN signal input is sampled again 256 clock cycles after de-assertion of the fundamental reset. A
high state of this signal sets the APWREN bit in the SWCTL register.
L2 Mode Enabled, FRSticky Bits Not Initialized
This sequence is shown in Figure 7.3(ba). The external POR circuitry maintains the APWRDISN signal
high after main power is first turned ON. The APWRDISN signal input is sampled 8 clock cycles after deassertion of the fundamental reset (main power is turned OFF to save power when the hierarchy is idle and
PES5T5 User Manual7 - 7January 28, 2011
Page 80
IDT Power Management
Notes
turned ON using in-band beacon or out-of-band WAKEN signaling when the traffic resumes). The signal is
sampled High, resulting in retention of the state of the FRSticky bits. The APWRDISN signal input is
sampled again 256 clock cycles after de-assertion of the fundamental reset (PERSTN). A high state of this
signal continues to set the APWREN bit in the SWCTL register.
L2 Mode Disabled
This sequence is shown in Figure 7.3(c). The external POR circuitry ties the APWRDISN signal low . The
APWRDISN signal input is sampled 8 clock cycles after de-assertion of the fundamental reset (PERSTN). A
Low state of this signal results in initialization of the FRSticky bits. The APWRDISN signal input is sampled
again 256 clock cycles after de-assertion of the fundamental reset (PERSTN). A Low state of this signal
resets the APWREN bit in the SWCTL register, thereby disabling L2 mode.
PES5T5 Auxiliary Power Usage
The AUXPD bit in the PCI Express Device Status register is set only when Auxiliary Power Usage is
enabled by either de-asserting the Auxiliary Power Disable active low signal at bring-up time or by setting
the APWREN bit in the Switch Control register. Based on the supported Auxiliary Power Usage model
shown in Figure 7.4, the PES5T5 does not sense an auxiliary power presence on the power pin.
All the core logic in the PES5T5 is powered from a common supply. The auxiliary power is used to
power I/Os that are ON during active standby.
– VA3P3 (3.3V) powers I/Os that are ON during active standby
– VA1P0 (1.0 V)
• Powers RAMBus SerDes Macros
• Powers V
TT
PE
• Powers Core logic that operates during active standby.
Vaux
3.3 V
Regulator
Figure 7.4 Vaux Usage Model
The auxiliary power supply current budget numbers are given in Tables 7.2 and 7.3.
VA3P3
3.3 V
VA1P0
1.0 V
PES5T5 User Manual7 - 8January 28, 2011
Page 81
IDT Power Management
Notes
Item
Current Estimate
(mA)
Comment
IO Power
3.3 V
DD
Supply
Rambus L2 (2 Ser-
Des quads ON with
Beacon OFF in
both the SerDes)
Core Logic14
3.3 V I/O6
Regulator Leakagetbd
Total Currenttbd
Table 7.2 Auxiliary Power Enabled (Beacon OFF)
Item
IO Power
3.3 V
DD
Supply
Rambus L2 (both-
SerDes OFF)
Core Logic14
3.3 V I/O6
Regulator Leakagetbd
Current Estimate
110
(mA)
6In L2 mode, auxiliary power supply is
used to power up all the I/Os.
Comment
6In L2 mode, auxiliary power supply is
used to power up all the I/Os.
4
Total Currenttbd
Table 7.3 Auxiliary Power Enabled (SerDes OFF, only WAKEN Enabled)
In Active standby, the clock is gated. When the main power is switched off, the auxiliary power supply is
used to power the SerDes (for Beacon sensing and generation), provide V
PE supply and power core
TT
logic that is operational during Active standby. This is illustrated in Figure 7.5.
PES5T5 User Manual7 - 9January 28, 2011
Page 82
IDT Power Management
Notes
+12V
SwitcherRegulator
3.3 Vaux Power Voltage
Figure 7.5 Conceptual Diagram of the PES5T5 Auxiliary Power Connection
Regulator
Regulator
Regulator
Regulator
1.0 V
1.5 V
3.3 V
1.0 V
1.5 V
VDDIO
VDDCORE
VDDAPE
VDDPE
PES5T5
VTTPE
When the device enters the Active standby mode, the auxiliary voltage powers the VDDCORE, VDDAPE,
V
PE, VDDIO, and VTTPE supplies to the PES5T5.
DD
PES5T5 User Manual7 - 10January 28, 2011
Page 83
Chapter 8
Hot-Plug and Hot-Swap
®
Notes
Introduction
As illustrated in Figures 8.1 through 8.3, a PCIe switch may be used in one of three hot-plug configurations. Figure 8.1 illustrates the use of the PES5T5 in an application in which two downstream ports are
connected to slots into which add-in cards may be hot-plugged. Figure 8.2 illustrates the use of the PES5T5
in an add-in card application. Here the downstream ports are hardwired to devices on the add-in card and
the upstream port serves as the add-in card’s PCIe interface. In this application the upstream port may be
hot-plugged into a slot on the main system. Finally, Figure 8.3 illustrates the use of the PES5T5 in a carrier
card application. In this application, the downstream ports are connected to slots which may be hot-plugged
and the entire assembly may be hot-plugged into a slot on the main system. Since this application requires
nothing more than the functionality illustrated in both Figures 8.1 through 8.2, it will not be discussed further.
Upstream
Link
Port 0
PES5T5
Master
SMBus
...
Port x
......
Port y
SMBus I/O
Expander
Hot-Plug Signals
Port x
Slot
Figure 8.1 Hot-Plug on Switch Downstream Slots Application
Port y
Slot
PES5T5 User Manual 8 - 1January 28, 2011
Page 84
IDT Hot-Plug and Hot-Swap
Notes
Add-In Card
Upstream
Link
Port 0
PES5T5
...
PCI Express
Device
Port x
......
Port y
PCI Express
Device
Figure 8.2 Hot-Plug with Switch on Add-In Card Application
Upstream
Link
Carrier
Card
Port 0
PES5T5
Master
SMBus
...
......
Port xPort y
SMBus I/O
Expander
Hot-Plug Signals
Port x
Slot
Port y
Slot
Figure 8.3 Hot-Plug with Carrier Card Application
The PCI Express Base Specification revision 1.0a allowed a hot-plug attention indicator, power indicator,
and attention button to be located on the board on which the slot is implemented or on the add-in board.
When located on the add-in board, state changes are communicated between the hot-plug controller associated with the slot and the add-in card via hot-plug messages. This capability was removed in revision 1.1
of the PCI Express Base Specification and is not supported in the PES5T5.
PES5T5 User Manual8 - 2January 28, 2011
Page 85
IDT Hot-Plug and Hot-Swap
Notes
The remainder of this section discusses the use of the PES5T5 in an application in which one or more of
the downstream ports are used in an application in which an add-in card may be hot-plugged into a downstream slot. Associated with each downstream port in the PES5T5 is a hot-plug controller. The hot-plug
controller may be enabled by setting the HPC bit in the PCI Express Slot Capabilities (PCIESCAP) register
associated with that port during configuration (e.g., via serial EEPROM).
The PES5T5 allows sensor inputs and indicator outputs to be located next to the slot or on the plug in
module. Regardless of the physical location, the indicators are controlled by the PES5T5’s downstream
port. Table 8.1 lists the hot-plug inputs and outputs that may be associated with a slot. When enabled during
configuration in the PCIESCAP register, these inputs and outputs are made available to external logic using
an external I/O expander located on the master SMBus interface.
The PES5T5 supports both presence detect signalling via a pin assertion as well as in-band presence
detect. The PDETECT field in Hot Plug Configuration control register and RDETECT field in the PHY Link
Configuration register
SignalTypeName/Description
PxAPNIPort x
PxPDNIPort x Presence Detect Input.
PxPFNIPort x Power Fault Input.
PxMRLNIPort x Manually-operated Retention Latch (MRL) Input.
1
is used to enable presence detect options.
1
Attention Push button Input.
PxAINOPort x Attention Indicator Output.
PxPINOPort x Power Indicator Output.
PxPEPOPort x Power Enable Output.
PxILOCKPOPort x Electromechanical Interlock.
PxPWRGDNIPort x Power Good Input (asserted when slot power is good).
2
PxRSTN
1.
x corresponds to downstream port number (i.e., 2 through 5).
2.
This signal is a GPIO pin alternate function and is not available as an I/O expander output.
OPort x Reset Output.
Table 8.1 Downstream Port Hot Plug Signals
Since the polarity of hot-plug signals has been defined differently in various specifications, each hot plug
signal has a corresponding control bit in the Hot-Plug Configuration Control (HPCFGCTL) that allows the
polarity of that signal to be inverted. Inversion affects the corresponding signal in all ports.
When a one is written to the EIC bit in the PCIESCTL register, the PxILOCKP signal is pulsed for with a
pulse length greater than 100 ms and less than 150 ms (i.e., it transitions from negated to asserted, maintains an asserted state for 100 to 150 ms, and then transitions back to negated). When the Toggle Electromechanical Interlock Control (TEMICTL) bit in the HPCFGCTL register is set, writing a one to the EIC bit
inverts the state of the PxILOCKP signal.
When the Replace MRL Status with EMIL Status (RMRLWEMIL) bit is set in the HPCFGCTL register,
then the port’s PxMRLN input is used as the electromechanical state input. The state of this input is used as
the state of the electromechanical interlock state obtained by reading the Electromechanical Interlock
Status (EIS) bit in the PCI Express Slot Status (PCIESSTS) register. In this mode, the state of the Manuallyoperated Retention Latch Sensor State (MRLSS) status is always reported as closed (i.e., zero). When the
RMRLWEMIL bit is cleared, the EIS bit state in the PCIESSTS register always returns the value of corresponding PxILOCKP I/O expander signal output.
1.
Note: For further information on this register, please contact ssdhelp@idt.com.
PES5T5 User Manual8 - 3January 28, 2011
Page 86
IDT Hot-Plug and Hot-Swap
Notes
When the MRL Automatic Power Off (MRLPWROFF) bit is set in the HPCFGCTL register and the
Manual Retention Latch Present (MRLP) bit is set in the PCI Express Slot Capability (PCIESCAP) register,
then power to the slot is automatically turned off when the MRL sensor indicates that the MRL is open. This
occurs regardless of the state of the Power Controller Control (PCC) bit in the PCI Express Slot Control
(PCIESCTL) register. The state of a port’s Power Fault (PxPFN) input is not latched by the PES5T5. For
proper operation, the system designer should ensure that once the PxPFN signal is asserted, it remains
asserted until the power enable (PxPEP) signal is toggled. This is required adapter behavior for the PCI
Express ExpressModule form factor.
Downstream port reset outputs are described in section Downstream Port Reset Outputs on page 2-9.
The default value of hot-plug registers following a hot or fundamental reset may be configured via serial
EEPROM initialization. Since hot-plug I/O expander initialization occurs after serial EEPROM initialization,
the Command Completed (CC) bit is not set in the PCI Express Slot Status (PCIESSTS) register as a result
of serial EEPROM initialization.
Hot-Plug I/O Expander
The PES5T5 utilizes external SMBus/I2C-bus I/O expanders connected to the master SMBus interface
for hot-plug related signals associated with downstream ports. See section I/O Expanders on page 6-6 for
details on the operation of the I/O expanders and for the mapping of downstream hot-plug signals to I/O
expander inputs and outputs.
Hot-Plug Interrupts and Wake-up
The hot-plug controller associated with a downstream slot may generate an interrupt or wakeup event.
Hot-plug interrupts are only generated when the Hot Plug Interrupt Enable (HPIE) bit is set in the corresponding port’s PCI Express Slot Control (PCIESCTL) register.
The following bits, when set in the PCI Express Slot Status (PCIESSTS) register, generate an inte rrupt if
not masked by the corresponding bit in the PCI Express Slot Control (PCIESCTL) register or by the HPIE
bit: the Attention Button Pressed (ABP), Power Fault Detected (PFD), MRL Sensor Changed (MRLSC),
Presence Detected Changed (PDC), and Command Completed (CC).
When an unmasked hot-plug interrupt is generated, the action taken is determined by the MSI Enable
(EN) bit in the MSI Capability (MSICAP) register and the Interrupt Disable (INTXD) bit in the PCI Command
(PCICMD) register. When the downstream port or the entire switch is in a D3
state, the hot-plug
Hot
controller generates a wakeup event using a PM_PME message instead of an interrupt if the event interrupt
is not masked in the slot control (PCIESCTL) register and hot-plug interrupts are disabled by the HPIE bit. If
the event interrupt is not masked and hot-plug interrupts are enabled, both a PM_PME and an interrupt are
generated. If the event interrupt is masked, neither a PM_PME nor interrupt are generated. Note that a
command completed (CC bit) interrupt will not generate a wakeup event.
Legacy System Hot-Plug Support
Some systems require support for operating systems that lack PCIe hot-plug support. The PES5T5
supports these systems by providing a General Purpose Event (GPEN) output as an alternate function of
GPIO[7] that can be used instead of the INTx, MSI, and PME mechanisms defined by PCI Express hotplug. Associated with each downstream port’s hot-plug controller is a bit in the General Purpose Event
Control (P0_GPECTL) register. When this bit is set, then the corresponding PCIe base 1.1 hot-plug event
notification mechanisms are disabled for that port and INTx, MSI and PME events will not be generated by
that port due to hot-plug events. Instead, hot-plug events are signaled through assertion of the GPEN
signal. GPEN is an alternate function of GPIO[7], and GPIO[7] will not be asserted when GPEN is asserted
unless it is configured to operate as an alternate function.
Whenever a port signals a hot-plug event through assertion of the GPEN signal, the corresponding
port’s status bit in the General Purpose Event Status (P0_GPESTS) register is set. A bit in the P0_GPESTS
register can only be set if the corresponding port’s hot-plug controller is configured to signal hot-plug events
using the general purpose event (GPEN) signal assertion mechanism.
PES5T5 User Manual8 - 4January 28, 2011
Page 87
IDT Hot-Plug and Hot-Swap
Notes
The hot-plug event signalling mechanism is the only thing that is affected when a port is configured to
use general purpose events instead of the PCIe defined hot-plug signalling mechanisms (i.e., INTx, MSI
and PME). Thus, the PCIe defined capability, status and mask bits defined in the PCIe slot capabilities,
status and control registers operate as normal and all other hot-plug functionality associated with the port
remains unchanged. INTx, MSI and PME events from other sources are also unaffected.
The enhanced hot-plug signalling mechanism supported by the PES5T5 is graphically illustrated in
Figure 8.4. This figure provides a conceptual summary of the enhanced hot-plug signalling mechanism in
the form of a pseudo logic diagram. Logic gates in this diagram are intended for conveying general
concepts, and not for direct implementation.
General Purpose Event
Enable
RW
General Purpose
Event Mechanism
Activate INTx
Mechanism
Activate MSI
Mechanism
Activate Wakeup
Mechanism
Slot Status
Register
Command
Completed
RW1C
RW1C
Attention Button
Pressed
RW1C
RW1C
Power Fault
Detected
RW1C
RW1C
MRL Sensor State
Changed
RW1C
RW1C
Presence Detected
Changed
RW1C
RW1C
Data Link Layer
State Changed
RW1C
RW1C
Slot Control
Register
Hot-Plug Interrupt
Enable
RW
Command
Completed Enable
RW
Attention Button
Pressed Enable
RW
Power Fault
Detected Enable
RW
MRL Sensor State
Changed Enable
RW
Presence Detected
Changed Enable
RW
Data Link Layer
State Changed Enable
RW
RW
MSI Enable
Bit
PME Enable
Bit
RW
Interrupt
Disable
RW
Figure 8.4 PES5T5 Hot-Plug Event Signalling
PES5T5 User Manual8 - 5January 28, 2011
Page 88
IDT Hot-Plug and Hot-Swap
Notes
Hot-Swap
The PES5T5 is hot-swap capable and meets the following requirements
– All of the I/Os are tri-stated on reset (i.e., SerDes, GPIO, SMBuses, etc.).
– All I/O cells function predictably from early power. This means that the device is able to tolerate a
non-monotonic ramp-up as well as a rapid ramp-up of the DC power.
– All I/O cells are able to tolerate a precharge voltage.
– Since no clock is present during physical connection, the device will maintain all outputs in a high-
impedance state even when no clock is present.
– The I/O cells meet VI requirements for hot-swap.
– The I/O cells respect the required leakage current limits over the entire input voltage range.
In summary, the PES5T5 meets all of the I/O requirements necessary to build a PICMG compliant hotswap board or system. The hot-swap I/O buffers of the PES5T5 may also be used to construct proprietary
hot-swap systems. See the 89HPES5T5 Data Sheet for a detailed specification of I/O buffer characteristics.
PES5T5 User Manual8 - 6January 28, 2011
Page 89
Chapter 9
Configuration Registers
®
Notes
Configuration Space Organization
Each software visible register in the PES5T55T5A is contained in the PCI configuration space of one of
the ports. Thus, there are no registers in the PES5T5A that cannot be accessed by the root. Each software
visible register in the PES5T5A has a system address. The system address is formed by adding the PCI
configuration space offset value of the register to the base address of the port in which it is located. The
system address is used for serial EEPROM register initialization and slave SMBus register accesses.
The base address for each PES5T5A port is listed in Table 9.1. The PCI configuration space offset
addresses for registers in the upstream port are listed in Table 9.2 while the PCI configuration space offset
addresses for registers in downstream ports are listed Table 9.3.
Base
Address
0x0000Port 0 configuration space (upstream port)
0x2000Port 2 configuration space (downstream port)
0x3000Port 3 configuration space (downstream port)
0x4000Port 4 configuration space (downstream port)
0x5000Port 5 configuration space (downstream port)
Table 9.1 Base Addresses for Port Configuration Space Registers
As shown in Figure 9.1, upstream and downstream ports share a similar PCI configuration space
register layout. The upstream port contains global switch control and status registers. The downstream
ports contain an MSI capability structure to generate MSIs as a result of hot-plug events, and the upstream
port supports MSI capability structure to report internal parity errors.
PCI Configuration Space
Reading from an upstream port offset not defined in Table 9.2 or a downstream offset not defined in
Table 9.3 returns a value of zero. Writes to such an offset complete successfully but modify no data and
have no other effect.
PES5T5 User Manual 9 - 1January 28, 2011
Page 90
IDT Configuration Registers
Notes
0x000
PCI
Configuration Space
(64 DWords)
0x000
0x040
0x0C0
0x0D0
0x0F0
0x0FF
Type 1
Configuration Header
PCI Express
Capability Structure
PCI Power Management
Capability Structure
MSI
Capability Structure
SSID/SSVID
Extended Config Access
Advanced Error Reporting
Enhanced Capability
Device Serial Number
Enhanced Capability
PCIe Virtual Channel
Enhanced Capability
Power Budgeting
Enhanced Capability
Switch Control
& Status Registers
Reserved
Power Management
Control & Status Registers
Reserved
0x100
0x180
0x200
0x280
0x328
0x39C
0x4C4
0x4D4
L2 Mode Control
Upstream Port Only
0x5CC
Figure 9.1 Port Configuration Space Organization
PES5T5 User Manual9 - 2January 28, 2011
Page 91
IDT Configuration Registers
Notes
Upstream Port (Port 0)
Cfg.
Offset
0x000WordP0_VIDVID - Vendor Identification Register (0x000) on page 9-11
0x002WordP0_DIDDID - Device Identification Register (0x002) on page 9-11
0x004WordP0_PCICMDPCICMD - PCI Comm and Register (0x004) on page 9-11
0x006WordP0_PCISTSPCISTS - PCI Status Register (0x006) on page 9-12
0x008ByteP0_RIDRID - Revision Identification Register (0x008) on page 9-13
0x0093 BytesP0_CCODECCODE - Class Code Register (0x009) on page 9-13
0x00CByteP0_CLSCLS - Cache Line Size Register (0x00C) on page 9-14
0x00DByteP0_PLTIMERPLTIMER - Primary Latency Timer (0x00D) on page 9-14
0x00EByteP0_HDRHDR - Header Type Register (0x00E) on page 9-14
0x00FByteP0_BISTBIST - Built-in Self Test Register (0x00F) on page 9-14
0x010DWordP0_BAR0BAR0 - Base Address Register 0 (0x010) on page 9-14
0x014DWordP0_BAR1BAR1 - Base Address Register 1 (0x014) on page 9-14
0x018ByteP0_PBUSNPBUSN - Primary Bus Number Register (0x018) on page 9-15
0x019ByteP0_SBUSNSBUSN - Secondary Bus Number Register (0x019) on page 9-15
0x01AByteP0_SUBUSNSUBUSN - Subordinate Bus Number Register (0x01A) on page 9-15
0x01BByteP0_SLTIMERSLTIMER - Secondary Latency Timer Register (0x01B) on page 9-15
Size
Register
Mnemonic
Register Definition
0x01CByteP0_IOBASEIOBASE - I/O Base Register (0x01C) on page 9-15
0x01DByteP0_IOLIMITIOLIMIT - I/O Limit Register (0x01D) on page 9-16
0x01EWordP0_SECSTSSECSTS - Secondary Status Register (0x01E) on page 9-16
0x020WordP0_MBASEMBASE - Memory Base Register (0x020) on page 9-16
0x022WordP0_MLIMITMLIMIT - Memory Limit Register (0x022) on page 9-17
0x024WordP0_PMBASEPMBASE - Prefetchable Memory Base Register (0x024) on page 9-
17
0x026WordP0_PMLIMITPMLIMIT - Prefetchable Memory Limit Register (0x026) on page 9-17
0x028DWordP0_PMBASEUPMBASEU - Prefetchable Memory Base Upper Register (0x028) on
page 9-18
0x02CDWordP0_PMLIMITUPMLIMITU - Prefetchable Memory Limit Upper Register (0x02C) on
page 9-18
0x030WordP0_IOBASEUIOBASEU - I/O Base Upper Register (0x030) on page 9-18
0x032WordP0_IOLIMITUIOLIMITU - I/O Limit Upper Register (0x032) on page 9-18
0x034ByteP0_CAPPTRCAPPTR - Capabilities Pointer Register (0x034) on page 9-19
0x038DWordP0_EROMBASEEROMBASE - Expansion ROM Base Address Register (0x038) on
page 9-19
0x03CByteP0_INTRLINEINTRLINE - Interrupt Line Register (0x03C) on page 9-19
0x03DByteP0_INTRPININTRPIN - Interrupt PIN Register (0x03D) on page 9-19
Table 9.2 Upstream Port 0 Configuration Space Registers (Part 1 of 5)
PES5T5 User Manual9 - 3January 28, 2011
Page 92
IDT Configuration Registers
Notes
Cfg.
Offset
0x03EWordP0_BCTLBCTL - Bridge Control Register (0x03E) on page 9-19
0x040DWordP0_PCIECAPPCIECAP - PCI Express Capability (0x040) on page 9-21
0x044DWordP0_PCIEDCAPPCIEDCAP - PCI Express Device Capabilities (0x044) on page 9-21
0x048WordP0_PCIEDCTLPCIEDCTL - PCI Express Device Control (0x048) on page 9-22
0x04AWordP0_PCIEDSTSPCIEDSTS - PCI Express Device Status (0x04A) on page 9-23
0x04CDWordP0_PCIELCAPPCIELCAP - PCI Express Link Capabilities (0x04C) on page 9-24
0x050WordP0_PCIELCTLPCIELCTL - PCI Express Link Control (0x050) on page 9-25
0x052WordP0_PCIELSTSPCIELSTS - PCI Express Link Status (0x052) on page 9-26
0x064DWordP0_PCIEDCAP2PCIEDCAP2 - PCI Express Device Capabilities 2 (0x064) on page 9-
0x068WordP0_PCIEDCTL2PCIEDCTL2 - PCI Express Device Control 2 (0x068) on page 9-31
0x06AWordP0_PCIEDSTS2PCIEDSTS2 - PCI Express Device Status 2 (0x06A) on page 9-31
0x06CDWordP0_PCIELCAP2PCIELCAP2 - PCI Express Link Capabilities 2 (0x06C) on page 9-31
0x070WordP0_PCIELCTL2PCIELCTL2 - PCI Express Link Control 2 (0x070) on page 9-31
0x072WordP0_PCIELSTS2PCIELSTS2 - PCI Express Link Status 2 (0x072) on page 9-32
0x0C0DWordP0_PMCAPPMCAP - PCI Power Management Capabilities (0x0C0) on page 9-32
0x0C4DWordP0_PMCSRPMCSR - PCI Power Management Control and Status (0x0C4) on
0x0D0DWordPx_MSICAPMSICAP - Message Signaled Interrupt Capability and Control
Size
Register
Mnemonic
Register Definition
31
page 9-33
(0x0D0) on page 9-34
0x0D4DWordPx_MSIADDRMSIADDR - Message Signaled Interrupt Address (0x0D4) on page 9-
34
0x0D8DWordPx_MSIUADDRMSIUADDR - Message Signaled Interrupt Upper Address (0x0D8) on
page 9-35
0x0DCDWordPx_MSIMDATAMSIMDATA - Message Signaled Interrupt Message Data (0x0DC) on
page 9-35
0x0F0DwordP0_SSIDSSVIDCAPSSIDSSVIDCAP - Subsystem ID and Subsystem Vendor ID Capabil-
ity (0x0F0) on page 9-35
0x0F4DwordP0_SSIDSSVIDSSIDSSVID - Subsystem ID and Subsystem Vendor ID (0x0F4) on
page 9-36
0x0F8WordP0_ECFGADDRECFGADDR - Extended Configuration Space Access Address
(0x0F8) on page 9-36
0x0FCWordP0_ECFGDATAECFGDATA - Extended Configuration Space Access Data (0x0FC)
on page 9-36
0x100DwordP0_AERCAPAERCAP - AER Capabilities (0x100) on page 9-37
0x104DwordP0_AERUESAERUES - AER Uncorrectable Error Status (0x104) on page 9-37
0x108DwordP0_AERUEMAERUEM - AER Uncorrectable Error Mask (0x108) on page 9-38
0x10CDwordP0_AERUESVAERUESV - AER Uncorrectable Error Severity (0x10C) on page 9-39
0x110DwordP0_AERCESAERCES - AER Correctable Error Status (0x110) on page 9-40
Table 9.2 Upstream Port 0 Configuration Space Registers (Part 2 of 5)
PES5T5 User Manual9 - 4January 28, 2011
Page 93
IDT Configuration Registers
Notes
Cfg.
Offset
0x114DwordP0_AERCEMAERCEM - AER Correctable Error Mask (0x114) on page 9-41
0x118DwordP0_AERCTLAERCTL - AER Control (0x118) on page 9-41
0x11CDwordP0_AERHL1DWAERHL1DW - AER Header Log 1st Doubleword (0x11C) on page 9-
0x180DwordP0_SNUMCAPSNUMCAP - Serial Number Capabilities (0x180) on page 9-43
0x184DwordP0_SNUMLDWSNUMLDW - Serial Number Lower Doubleword (0x184) on page 9-43
0x188DwordP0_SNUMUDWSNUMUDW - Serial Number Upper Doubleword (0x188) on page 9-
0x204DWordP0_PVCCAP1PVCCAP1- Port VC Capability 1 (0x204) on page 9-43
0x208DWordP0_PVCCAP2PVCCAP2- Port VC Capability 2 (0x208) on page 9-44
0x20CDWordP0_PVCCTLPVCCTL - Port VC Control (0x20C) on page 9-45
0x20EDWordP0_PVCSTSPVCSTS - Port VC Status (0x20E) on page 9-45
Size
Register
Mnemonic
Register Definition
42
42
42
42
43
(0x200) on page 9-43
0x210DWordP0_VCR0CAPVCR0CAP- VC Resource 0 Capability (0x210) on page 9-45
0x214DWordP0_VCR0CTLVCR0CTL- VC Resource 0 Control (0x214) on page 9-46
0x218DWordP0_VCR0STSVCR0STS - VC Resource 0 Status (0x218) on page 9-47
0x220DWordP0_VCR0TBL0VCR0TBL0 - VC Resource 0 Arbitration Table Entry 0 (0x220) on
0x280DwordP0_PWRBCAPPWRBCAP - Power Budgeting Capabilities (0x280) on page 9-49
0x284DwordP0_PWRBDSELPWRBDSEL - Power Budgeting Data Select (0x284) on page 9-50
0x288DwordP0_PWRBDPWRBD - Power Budgeting Data (0x288) on page 9-50
0x28CDwordP0_PWRBPBCPWRBPBC - Power Budgeting Power Budget Capability (0x28C) on
page 9-50
0x300DwordP0_PWRBDV0PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
9-50
0x304DwordP0_PWRBDV1PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
9-50
Table 9.2 Upstream Port 0 Configuration Space Registers (Part 3 of 5)
PES5T5 User Manual9 - 5January 28, 2011
Page 94
IDT Configuration Registers
Notes
Cfg.
Offset
0x308DwordP0_PWRBDV2PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x30CDwordP0_PWRBDV3PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x310DwordP0_PWRBDV4PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x314DwordP0_PWRBDV5PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x318DwordP0_PWRBDV6PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x31CDwordP0_PWRBDV7PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x320DwordP0_PWRBDV8PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x324DwordP0_PWRBDV9PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x328DWordSWSTSSWSTS - Switch Status (0x328) on page 9-51
0x32CDWordSWCTLSWCTL - Switch Control (0x32C) on page 9-52
0x330DWordHPCFGCTLHPCFGCTL - Hot-Plug Configuration Control (0x330) on page 9-53
0x334DWordGPRGPR - General Purpose Register (0x334) on page 9-54
Size
Register
Mnemonic
Register Definition
9-50
9-50
9-50
9-50
9-50
9-50
9-50
9-50
0x338DWordGPIOFUNCGPIOFUNC - General Purpose I/O Control Function (0x338) on page
9-55
0x33CDWordGPIOCFGGPIOCFG - General Purpose I/O Configuration (0x33C) on page 9-55
0x340DWordGPIODGPIOD - General Purpose I/O Data (0x340) on page 9-55
0x344DWordSMBUSSTSSMBUSSTS - SMBus Status (0x344) on page 9-55
0x348DWordSMBUSCTLSMBUSCTL - SMBus Control (0x348) on page 9-56
0x34CDWordEEPROMINTFEEPROMINTF - Serial EEPROM Interface (0x34C) on page 9-57
0x350DWordIOEXPINTFIOEXPINTF - I/O Expander Interface (0x350) on page 9-58
0x354DWordIOEXPADDR0IOEXPADDR0 - SMBus I/O Expander Address 0 (0x354) on page 9-
0x35CDWordGPECTLGPECTL - General Purpose Event Control (0x35C) on page 9-60
0x360DWordGPESTSGPESTS - General Purpose Event Status (0x360) on page 9-61
0x4D4DwordP0_SWPECTLSWPECTL - Switch Parity Error Control (0x4D4) on page 9-61
0x4D8DwordP0_SWERRSTSSWERRSTS - Switch Internal Error Status (0x4D8) on page 9-62
0x4DCDwordP0_SWERRCTLSWERRCTL - Switch Internal Error Reporting Control (0x4DC) on
page 9-62
0x4E0DwordP0_SWERRCNTSWERRCNT - Switch Internal Error Count (0x4E0) on page 9-63
0x4E4DwordP0_SWTOCTLSWTOCTL - Switch Time-Out Control (0x4E4) on page 9-63
Table 9.2 Upstream Port 0 Configuration Space Registers (Part 4 of 5)
PES5T5 User Manual9 - 6January 28, 2011
Page 95
IDT Configuration Registers
Notes
Cfg.
Offset
0x4E8DwordP0_SWTORCTLSWTORCTL - Switch Time-Out Reporting Control (0x4E8) on page 9-
0x4ECDwordP0_SWTOCNTSWTOCNT - Switch Time-Out Count (0x4EC) on page 9-64
0x5CCDwordP0_WAKEUPCNTLWAKEUPCNTL - Wakeup Protocol Control Register (0x5CC) on page
Size
Register
Mnemonic
63
9-64
Table 9.2 Upstream Port 0 Configuration Space Registers (Part 5 of 5)
Register Definition
Downstream Ports (Ports 2 through 5)
Cfg.
Offset
0x000WordPx_VIDVID - Vendor Identification Register (0x000) on page 9-11
0x002WordPx_DIDDID - Device Identification Register (0x002) on page 9-11
0x004WordPx_PCICMDPCICMD - PCI Command Register (0x004) on page 9-11
0x006WordPx_PCISTSPCISTS - PCI Status Register (0x006) on page 9-12
0x008BytePx_RIDRID - Revision Identification Register (0x008) on page 9-13
0x0093 BytesPx_CCODECCODE - Class Code Register (0x009) on page 9-13
Size
Register
Mnemonic
Register Definition
0x00CBytePx_CLSCLS - Cache Line Size Register (0x00C) on page 9-14
0x00DBytePx_PLTIMERPLTIMER - Primary Latency Timer (0x00D) on page 9-14
0x00EBytePx_HDRHDR - Header Type Register (0x00E) on page 9-14
0x00FBytePx_BISTBIST - Built-in Self Test Register (0x00F) on page 9-14
0x010DWordPx_BAR0BAR0 - Base Address Register 0 (0x010) on page 9-14
0x014DWordPx_BAR1BAR1 - Base Address Register 1 (0x014) on page 9-14
0x018BytePx_PBUSNPBUSN - Primary Bus Number Register (0x018) on page 9-15
0x019BytePx_SBUSNSBUSN - Secondary Bus Number Register (0x019) on page 9-15
0x01ABytePx_SUBUSNSUBUSN - Subordinate Bus Number Register (0x01A) on page 9-15
0x01BBytePx_SLTIMERSLTIMER - Secondary Latency Timer Register (0x01B) on page 9-15
0x01CBytePx_IOBASEIOBASE - I/O Base Register (0x01C) on page 9-15
0x01DBytePx_IOLIMITIOLIMIT - I/O Limit Register (0x01D) on page 9-16
0x01EWordPx_SECSTSSECSTS - Secondary Status Register (0x01E) on page 9-16
0x020WordPx_MBASEMBASE - Memory Base Register (0x020) on page 9-16
0x022WordPx_MLIMITMLIMIT - Memory Limit Register (0x022) on page 9-17
0x024WordPx_PMBASEPMBASE - Prefetchable Memory Base Register (0x024) on page 9-
17
0x026WordPx_PMLIMITPMLIMIT - Prefetchable Memory Limit Register (0x026) on page 9-17
0x028DWordPx_PMBASEUPMBASEU - Prefetchable Memory Base Upper Register (0x028) on
page 9-18
Table 9.3 Downstream Ports 2 through 5 Configuration Space Registers (Part 1 of 4)
PES5T5 User Manual9 - 7January 28, 2011
Page 96
IDT Configuration Registers
Notes
Cfg.
Offset
0x02CDWordPx_PMLIMITUPMLIMITU - Prefetchable Memory Limit Upper Register (0x02C) on
0x030WordPx_IOBASEUIOBASEU - I/O Base Upper Register (0x030) on page 9-18
0x032WordPx_IOLIMITUIOLIMITU - I/O Limit Upper Register (0x032) on page 9-18
0x034BytePx_CAPPTRCAPPTR - Capabilities Pointer Register (0x034) on page 9-19
0x038DWordPx_EROMBASEEROMBASE - Expansion ROM Base Address Register (0x038) on
0x03CBytePx_INTRLINEINTRLINE - Interrupt Line Register (0x03C) on page 9-19
0x03DBytePx_INTRPININTRPIN - Interrupt PIN Register (0x03D) on page 9-19
0x03EWordPx_BCTLBCTL - Bridge Control Register (0x03E) on page 9-19
0x040DWordPx_PCIECAPPCIECAP - PCI Express Capability (0x040) on page 9-21
0x044DWordPx_PCIEDCAPPCIEDCAP - PCI Express Device Capabilities (0x044) on page 9-21
0x048WordPx_PCIEDCTLPCIEDCTL - PCI Express Device Control (0x048) on page 9-22
0x04AWordPx_PCIEDSTSPCIEDSTS - PCI Express Device Status (0x04A) on page 9-23
0x04CDWordPx_PCIELCAPPCIELCAP - PCI Express Link Capabilities (0x04C) on page 9-24
0x050WordPx_PCIELCTLPCIELCTL - PCI Express Link Control (0x050) on page 9-25
0x052WordPx_PCIELSTSPCIELSTS - PCI Express Link Status (0x052) on page 9-26
Size
Register
Mnemonic
Register Definition
page 9-18
page 9-19
0x054DWordPx_PCIESCAPPCIESCAP - PCI Express Slot Capabilities (0x054) on page 9-27
0x058WordPx_PCIESCTLPCIESCTL - PCI Express Slot Control (0x058) on page 9-28
0x05AWordPx_PCIESSTSPCIESSTS - PCI Express Slot Status (0x05A) on page 9-30
0x064DWordPx_PCIEDCAP2PCIEDCAP2 - PCI Express Device Capabilities 2 (0x064) on page 9-
31
0x068WordPx_PCIEDCTL2PCIEDCTL2 - PCI Express Device Control 2 (0x068) on page 9-31
0x06AWordPx_PCIEDSTS2PCIEDSTS2 - PCI Express Device Status 2 (0x06A) on page 9-31
0x06CDWordPx_PCIELCAP2PCIELCAP2 - PCI Express Link Capabilities 2 (0x06C) on page 9-31
0x070WordPx_PCIELCTL2PCIELCTL2 - PCI Express Link Control 2 (0x070) on page 9-31
0x072WordPx_PCIELSTS2PCIELSTS2 - PCI Express Link Status 2 (0x072) on page 9-32
0x074DWordPx_PCIESCAP2PCIESCAP2 - PCI Express Slot Capabilities 2 (0x074) on page 9-32
0x078WordPx_PCIESCTL2PCIESCTL2 - PCI Express Slot Control 2 (0x078) on page 9-32
0x07AWordPx_PCIESSTS2PCIESSTS2 - PCI Express Slot Status 2 (0x07A) on page 9-32
0x0C0DWordPx_PMCAPPMCAP - PCI Power Management Capabilities (0x0C0) on page 9-32
0x0C4DWordPx_PMCSRPMCSR - PCI Power Management Control and Status (0x0C4) on
page 9-33
0x0D0DWordPx_MSICAPMSICAP - Message Signaled Interrupt Capability and Control
(0x0D0) on page 9-34
0x0D4DWordPx_MSIADDRMSIADDR - Message Signaled Interrupt Address (0x0D4) on page 9-
34
Table 9.3 Downstream Ports 2 through 5 Configuration Space Registers (Part 2 of 4)
PES5T5 User Manual9 - 8January 28, 2011
Page 97
IDT Configuration Registers
Notes
Cfg.
Offset
0x0D8DWordPx_MSIUADDRMSIUADDR - Message Signaled Interrupt Upper Address (0x0D8) on
0x0DCDWordPx_MSIMDATAMSIMDATA - Message Signaled Interrupt Message Data (0x0DC) on
0x0F0DwordPx_SSIDSSVIDCAPSSIDSSVIDCAP - Subsystem ID and Subsystem Vendor ID Capabil-
0x0F4DwordPx_SSIDSSVIDSSIDSSVID - Subsystem ID and Subsystem Vendor ID (0x0F4) on
0x0F8WordPx_ECFGADDRECFGADDR - Extended Configuration Space Access Address
0x0FCWordPx_ECFGDATAECFGDATA - Extended Configuration Space Access Data (0x0FC)
0x100DwordPx_AERCAPAERCAP - AER Capabilities (0x100) on page 9-37
0x104DwordPx_AERUESAERUES - AER Uncorrectable Error Status (0x104) on page 9-37
0x108DwordPx_AERUEMAERUEM - AER Uncorrectable Error Mask (0x108) on page 9-38
0x10CDwordPx_AERUESVAERUESV - AER Uncorrectable Error Severity (0x10C) on page 9-39
0x110DwordPx_AERCESAERCES - AER Correctable Error Status (0x110) on page 9-40
0x114DwordPx_AERCEMAERCEM - AER Correctable Error Mask (0x114) on page 9-41
0x118DwordPx_AERCTLAERCTL - AER Control (0x118) on page 9-41
0x11CDwordPx_AERHL1DWAERHL1DW - AER Header Log 1st Doubleword (0x11C) on page 9-
0x180DwordPx_SNUMCAPSNUMCAP - Serial Number Capabilities (0x180) on page 9-43
0x184DwordPx_SNUMLDWSNUMLDW - Serial Number Lower Doubleword (0x184) on page 9-43
0x188DwordPx_SNUMUDWSNUMUDW - Serial Number Upper Doubleword (0x188) on page 9-
0x204DWordPx_PVCCAP1PVCCAP1- Port VC Capability 1 (0x204) on page 9-43
0x208DWordPx_PVCCAP2PVCCAP2- Port VC Capability 2 (0x208) on page 9-44
0x20CWordPx_PVCCTLPVCCTL - Port VC Control (0x20C) on page 9-45
0x20EWordPx_PVCSTSPVCSTS - Port VC Status (0x20E) on page 9-45
0x210DWordPx_VCR0CAPVCR0CAP- VC Resource 0 Capability (0x210) on page 9-45
0x214DWordPx_VCR0CTLVCR0CTL- VC Resource 0 Control (0x214) on page 9-46
0x218DWordPx_VCR0STSVCR0STS - VC Resource 0 Status (0x218) on page 9-47
Table 9.3 Downstream Ports 2 through 5 Configuration Space Registers (Part 3 of 4)
PES5T5 User Manual9 - 9January 28, 2011
Page 98
IDT Configuration Registers
Notes
Cfg.
Offset
0x280DwordPx_PWRBCAPPWRBCAP - Power Budgeting Capabilities (0x280) on page 9-49
0x284DwordPx_PWRBDSELPWRBDSEL - Power Budgeting Data Select (0x284) on page 9-50
0x288DwordPx_PWRBDPWRBD - Power Budgeting Data (0x288) on page 9-50
0x28CDwordPx_PWRBPBCPWRBPBC - Power Budgeting Power Budget Capability (0x28C) on
0x300DwordPx_PWRBDV0PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x304DwordPx_PWRBDV1PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x308DwordPx_PWRBDV2PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x30CDwordPx_PWRBDV3PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x310DwordPx_PWRBDV4PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x314DwordPx_PWRBDV5PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x318DwordPx_PWRBDV6PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x31CDwordPx_PWRBDV7PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
0x320DwordPx_PWRBDV8PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
Size
Register
Mnemonic
Register Definition
page 9-50
9-50
9-50
9-50
9-50
9-50
9-50
9-50
9-50
9-50
0x324DwordPx_PWRBDV9PWRBDV[9:0] - Power Budgeting Data Value [9:0] (0x300) on page
9-50
0x4D4DwordPx_SWPECTLSWPECTL - Switch Parity Error Control (0x4D4) on page 9-61
0x4D8DwordPx_SWERRSTSSWERRSTS - Switch Internal Error Status (0x4D8) on page 9-62
0x4DCDwordPx_SWERRCTLSWERRCTL - Switch Internal Error Reporting Control (0x4DC) on
page 9-62
0x4E0DwordPx_SWERRCNTSWERRCNT - Switch Internal Error Count (0x4E0) on page 9-63
0x4E4DwordPx_SWTOCTLSWTOCTL - Switch Time-Out Control (0x4E4) on page 9-63
0x4E8DwordPx_SWTORCTLSWTORCTL - Switch Time-Out Reporting Control (0x4E8) on page 9-
63
0x4ECDwordPx_SWTOCNTSWTOCNT - Switch Time-Out Count (0x4EC) on page 9-64
Table 9.3 Downstream Ports 2 through 5 Configuration Space Registers (Part 4 of 4)
PES5T5 User Manual9 - 10January 28, 2011
Page 99
IDT Configuration Registers
Notes
Register Definitions
Type 1 Configuration Header Registers
VID - Vendor Identification Register (0x000)
Bit
Field
15:0VIDRO0x111DVendor Identification. This field contains the 16-bit vendor
DID - Device Identification Register (0x002)
Bit
Field
15:0DIDRO-Device Identification. This field contains the 16-bit device
PCICMD - PCI Command Register (0x004)
Bit
Field
Field
Name
Field
Name
Field
Name
Type
Type
Type
Default
Value
Default
Value
Default
Value
Description
ID value assigned to IDT.
See section Vendor ID on page 1-10.
Description
ID assigned by IDT to this bridge.
See section Device ID on page 1-10.
Description
0IOAERW0x0I/O Access Enable. When this bit is cleared, the bridge does
not respond to I/O accesses from the primary bus specified
by IOBASE and IOLIMIT.
0x0 -(disable) Disable I/O space.
0x1 - (enable) Enable I/O space.
1MAERW0x0Memory Access Enable. When this bit is cleared, the
bridge does not respond to memory and prefetchable memory space access from the primary bus specified by MBASE,
MLIMIT, PMBASE and PMLIMIT.
0x0 -(disable) Disable memory space.
0x1 - (enable) Enable memory space.
2BMERW0x0Bus Master Enable. When this bit is cleared, the bridge
does not issue requests (e.g., memory, I/O and MSIs since
they are in-band writes) on behalf of subordinate devices
and responds to non-posted transactions with a Unsupported Request (UR) completion. This bit does not affect
completions in either direction or the forwarding of non memory or I/O requests.
0x0 -(disable) Disable request forwarding.
0x1 - (enable) Enable request forwarding.
3SSERO0x0Special Cycle Enable. Not applicable.
4MWIRO0x0Memory Write Invalidate. Not applicable.
5VGASRO0x0VGA Palette Snoop. Not applicable.
PES5T5 User Manual9 - 11January 28, 2011
Page 100
IDT Configuration Registers
Notes
Bit
Field
6PERRERW0x0Parity Error Enable. The Master Data Parity Error bit is set
7ADSTEPRO 0x0Address Data Stepping. Not applicable.
8SERRERW0x0SERR Enable. Non-fatal and fatal errors detected by the
9FB2BRO0x0Fast Back-to-Back Enable. Not applicable.
Field
Name
Type
Default
Value
Description
in the PCI Status register (PCISTS) if this bit is set and the
bridge receives a poisoned completion or generates a poi-
soned write. If this bit is cleared, then the Master Data Parity
Error bit in the PCI Status register is never set.
0x0 -(disable) Disable Master Parity Error bit reporting.
0x1 -(enable) Enable Master Parity Error bit reporting.
bridge are reported to the Root Complex when this bit is set
or the bits in the PCI Express Device Control register are set
(see PCIEDCTL - PCI Express Device Control (0x048) on
page 9-22).
In addition, when this bit is set it enables the forwarding of
ERR_NONFATAL and ERR_FATAL error messages from
the secondary to the primary interface. ERR_COR mes-
sages are unaffected by this bit and are always forwarded.
0x0 -(disable) Disable non-fatal and fatal error reporting if
also disabled in Device Control register.
0x1 -(enable) Enable non-fatal and fatal error reporting.
10INTXDRW0x0INTx Disable. Controls the ability of the PCI-PCI bridge to
generate an INTx interrupt message.
When this bit is cleared, any interrupts generated by this
bridge are negated. This may result in a change in the
resolved interrupt state of the bridge.
This bit has no effect on interrupts forwarded from the sec-
ondary to the primary interface.
15:11ReservedRO0x0Reserved field.
PCISTS - PCI Status Register (0x006)
Bit
Field
2:0ReservedRO0x0Reserved field.
3INTSRO0x0INTx Status. This bit is set when an INTx interrupt is pend-
4CAPLRO0x1Capabilities List. This bit is hardwired to one to indicate that
Field
Name
Type
Default
Value
Description
ing from the device.
INTx emulation interrupts forwarded by switch ports from
devices downstream of the bridge are not reflected in this bit.
For downstream ports, this bit is set if an interrupt has been
“asserted” by the corresponding port’s hot-plug controller.
In the upstream port, this field is set if an internal parity error
has been detected or config access error has occurred.
the bridge implements an extended capability list item.
5C66MHZRO0x066 MHz Capable. Not applicable.
6ReservedRO0x0Reserved field.
PES5T5 User Manual9 - 12January 28, 2011
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.