NH82801IR - Intel - Pdf.Support

Document Number: 316972-004

Intel® I/O Controller Hub 9 (ICH9)

Family

Datasheet

– For the Intel® 82801IB ICH9, 82801IR ICH9R, 82801IH ICH9DH,

82801IO ICH9DO, 82801IBM ICH9M and 82801IEM ICH9M-E,

and ICH9M-SFF ICH9-I/O Controller Hubs

August 2008

2Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Legal Lines and Discla ime rs

INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR

OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS

OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING

TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE,

MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for

use in medical, life saving, or life sustaining applications.

Intel may make changes to specifications and product descriptions at any time, without notice.

Designers must not rely on the absence or characteristics of any features or instr uc tions marked “reserved ” or “undefined.” Intel reserves these for

future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.

The Intel® I/O Controller Hub 9 (ICH9) F amily chipset component may contain design defects or errors known as errata which may cause the product to

deviate from published specifications. Current characterized errata are available on request.

Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.

I2C is a two-wire communications bus/protocol developed by Philips. SMBus is a subset of the I2C bus/protocol and was developed by Intel.

Implementations of the I2C bus/protocol may require licenses from various entities, including Philips Electronics N.V. and North American Philips

Corporation.

Intel® Active Management Technology requires the computer system to have an Intel® AMT -enabled chipset, network hardware and software, as well as

connection with a power source and a corporate network connection. Setup requires configuration by the purchaser and may require scripting wi th the

management console or further integration into existing security frameworks to enable certain functionality. It may also require modifications of

implementation of new business processes. With regard to notebooks, Intel AMT may not be available or certain capabilities may be limited over a host

OS-based VPN or when connecting wirelessly, on battery power, sleeping, hibernating or powered off. F or more information, see www.intel.com/

technology/platform-technology/intel-amt/

Intel® Virtualization Technology requires a computer system with a processor, chipset, BIOS, virtual machine monitor (VMM) and for some uses, certain

platform software enabled for it. Functionality, performance or other benefit will vary depending on hardware and software configurations and may

require a BIOS update. Software applications may not be compatible with all operating systems. Please check with your application vendor.

Intel, I n te l Sp ee dS t ep, Inte l V i iv, and the Intel lo g o a re tradem arks or re gistered tr ademarks of In tel C orp or at ion or it s subs idi ari es i n t he U nit ed Stat es

and other countries.

*Other names and brands may be claimed as the property of others.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 3

Contents

1Introduction............................................................................................................43

1.1 About This Document.........................................................................................43

1.2 Overview .........................................................................................................47

1.2.1 Capability Overview................................................................................49

1.3 Intel® ICH9 Family High-Level Component Differences...........................................54

2 Signal Description ...................................................................................................55

2.1 Direct Media Interface (DMI) to Host Controller.....................................................58

2.2 PCI Express* ....................................................................................................59

2.3 LAN Connect Interface .......................................................................................59

2.4 Gigabit LAN Connect Interf ace ..... .. ............ ........................ ....................... ..........60

2.5 Firmware Hub Interface.... .. .. ............. .................................................................61

2.6 PCI Interface ....................................................................................................62

2.7 Serial ATA Interface.................. .. .......... .. .. .. ...................... .. .. .. ..................... .. .. ..64

2.8 LPC Interface....................................................................................................67

2.9 Interrupt Interface ............................................................................................68

2.10 USB Interface.... ... .......... .. .. ........... .. .. ........... .. .......... .. .. ........... .. .. ........... .. .. ......69

2.11 Power Management Interface..............................................................................71

2.12 Processor Interface............................................................................................74

2.13 SMBus Interface................................................................................................75

2.14 System Management Interface............................................................................76

2.15 Real Time Clock Interface...................................................................................78

2.16 Other Clocks.....................................................................................................78

2.17 Miscellaneous Sig nals .................................... .. .. .. .......... ... .. ..................... .. .. ......78

2.18 Intel® High Definition Audio Link.........................................................................80

2.19 Serial Peripheral Interface (SPI)..........................................................................81

2.20 Controller Link..................................................................................................82

2.21 Intel® Quiet System Technology (Desktop Only)...................................................83

2.22 General Purpose I/O Signals ...............................................................................83

2.23 Power and Ground Signals..................................................................................86

2.24 Pin Straps ........................................................................................................88

2.24.1 Functional Straps .......... .. ............................... .. .. ... ..................... .. .. .. ......88

2.24.2 External RTC Circuitry.............................................................................90

3Intel

® ICH9 Pin States.............................................................................................91

3.1 Integrated Pull-Ups and Pull-Downs.....................................................................91

3.2 Output and I/O Signals Planes and States.............................................................92

3.3 Power Planes for Input Signals.......................................................................... 101

4Intel

® ICH9 and System Clock Domains................................................................. 107

5 Functional Description........................................................................................... 109

5.1 DMI-to-PCI Bridge (D30:F0 ) .............. .. .. .. ......................................................... 109

5.1.1 PCI Bus Interface ................................................................................. 109

5.1.2 PCI Bridge As an Initiator...................................................................... 109

5.1.2.1 Memory Reads and Writes.......... .. ............................................ 110

5.1.2.2 I/O Reads and Writes .................. .. .......................................... 110

5.1.2.3 Configuratio n Reads and Writes ................. .. .. ..................... .. .. .. 110

5.1.2.4 Locked Cycles ........................................................................ 110

5.1.2.5 Target / Master Aborts............................................................. 110

5.1.2.6 Secondary Master Latency Timer............................................... 110

5.1.2.7 Dual Address Cycle (DAC)........................................................ 110

5.1.2.8 Memory and I/O Decode to PCI................................................. 111

4Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.1.3 Parity Error Detection and Generation......................................................111

5.1.4 PCIRST# .............................................................................................112

5.1.5 Peer Cycles..........................................................................................112

5.1.6 PCI-to-PCI Bridge Model........................................................................112

5.1.7 IDSEL to Device Number Mapping...........................................................113

5.1.8 Standard PCI Bus Configuration Mechanism..............................................113

5.2 PCI Express* Root Ports (D28:F0,F1,F2,F3,F4,F5)................................................113

5.2.1 Interrupt Generation.............................................................................113

5.2.2 Power Management....... ... .. .. .......... .. .. ........... .. .. ........... .. .. ........... .. .. ......114

5.2.2.1 S3/S4/S5 Support...................................................................114

5.2.2.2 Resuming from Suspended State...............................................114

5.2.2.3 Device Initiated PM_PME Message .............................................114

5.2.2.4 SMI/SCI Generation.................................................................115

5.2.3 SERR# Generation................................................................................115

5.2.4 Hot-Plug..............................................................................................116

5.2.4.1 Presence Detection..................................................................116

5.2.4.2 Message Generation ................................................................116

5.2.4.3 Attention Button Detection .......................................................117

5.2.4.4 SMI/SCI Generation.................................................................117

5.3 Gigabit Ethernet Controller (B0:D25:F0) .............................................................117

5.3.1 Gigabit Ethernet PCI Bus Interface..........................................................118

5.3.1.1 Transaction Layer....................................................................118

5.3.1.2 Data Alignment.......................................................................118

5.3.1.3 Configuration Request Retry Status ...........................................119

5.3.2 Error Events and Error Reporting ............................................................119

5.3.2.1 Data Parity Error.....................................................................119

5.3.2.2 Completion with Unsuccessful Completio n Statu s............... .. .. .. .. ..119

5.3.3 Ethernet Interface ................................................................................119

5.3.3.1 MAC/LAN Connect Interface......................................................119

5.3.4 PCI Power Management.........................................................................120

5.3.4.1 Wake-Up................................................................................120

5.3.5 Configurable LEDs.................................................................................121

5.3.6 Function Level Reset Support (FLR).........................................................122

5.3.6.1 FLR Steps.................... .. ........... .. .. .......... ... .......... .. .. ........... .. ..122

5.4 LPC Bridge (w/ System and Management Functions) (D31:F0)...............................123

5.4.1 LPC Interface .......................................................................................123

5.4.1.1 LPC Cycle Types......................................................................124

5.4.1.2 Start Field Definition................................................................124

5.4.1.3 Cycle Type / Direction (CYCTYPE + DIR).....................................125

5.4.1.4 Size.......................................................................................125

5.4.1.5 SYNC.....................................................................................126

5.4.1.6 SYNC Time-Out.......................................................................126

5.4.1.7 SYNC Error Indication ..............................................................126

5.4.1.8 LFRAME# Usage............... ........... .. .. ..................... .. .. ........... .. ..127

5.4.1.9 I/O Cycles..............................................................................127

5.4.1.1 0 Bus Master Cycles .......... .. ........... .. .. .. ........... .. .. .......... ... .. ........127

5.4.1.11 LPC Power Management...........................................................127

5.4.1.12 Configuration and Intel® ICH9 Implications.......... .. .. .. .. ............. ..128

5.5 DMA Operation (D31:F0 ) ............. .. .. .......... .. .. ... .......... .. .. ..................... ... .. .. ......128

5.5.1 Channel Priority....................................................................................129

5.5.1.1 Fixed Priority..........................................................................129

5.5.1.2 Rotating Priority......................................................................129

5.5.2 Address Compatibility Mode ...................................................................129

5.5.3 Summary of DMA Transfer Sizes.............................................................130

5.5.3.1 Address Shifting When Programmed for 16-Bit I/O Count by Words130

5.5.4 Autoinitialize........................................................................................130

5.5.5 Software Commands.............................................................................131

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 5

5.6 LPC DMA........................................................................................................ 131

5.6.1 Asserting DMA Requests........................................................................ 131

5.6.2 Aband oning DMA Reques ts ............... ........... .. .. .. ........... .. .. ..................... 132

5.6.3 General Flow of DMA Transfers............................................................... 132

5.6.4 Terminal Count .................................................................................... 133

5.6.5 Verify Mode......................................................................................... 133

5.6.6 DMA Request Deassertion...................................................................... 133

5.6.7 SYNC Field / LDRQ# Rules..................................................................... 134

5.7 8254 Timers (D31:F0) ..................................................................................... 135

5.7.1 Timer Programming.............................................................................. 135

5.7.2 Reading from the Interval Timer............................................................. 136

5.7.2.1 Simple Read........................................................................... 136

5.7.2.2 Counter Latch Command. .. .. ... ..................... .. .. .. ..................... .. 137

5.7.2.3 Read Back Command .............................................................. 137

5.8 8259 Interrupt Controllers (PIC) (D31:F0).......................................................... 138

5.8.1 Interrupt Handling................................................................................ 139

5.8.1.1 Generating Interrupts.............................................................. 139

5.8.1.2 Acknowledging Interrupts ........................................................ 139

5.8.1.3 Hardware/Software Interrupt Sequence..................................... 140

5.8.2 Initialization Command Words (ICWx)..................................................... 140

5.8.2.1 ICW1 .................................................................................... 140

5.8.2.2 ICW2 .................................................................................... 141

5.8.2.3 ICW3 .................................................................................... 141

5.8.2.4 ICW4 .................................................................................... 141

5.8.3 Operation Command Words (OCW)......................................................... 141

5.8.4 Mod es of Ope ration ............. ............................... ... .. .. ..................... .. .. .. 141

5.8.4.1 Fully Nested Mode................................................................... 141

5.8.4.2 Special Fully-Nested Mode........................................................ 142

5.8.4.3 Automatic Rotation Mode (Equal Priority Devices)........................ 142

5.8.4.4 Specific Rotation Mode (Specific Priority).................................... 142

5.8.4.5 Poll Mode..... ... .. .......... .. .. ........... .. .. ........... .. .. .......... ... .. .......... 142

5.8.4.6 Cascade Mode......... .. .. ........... .. .. .......... ... .. .......... .. .. ........... .. .. 143

5.8.4.7 Edge and Level Triggered Mode ................................................ 143

5.8.4.8 End of Interrupt (EOI) Operations ............................................. 143

5.8.4.9 Normal End of Interrupt........................................................... 143

5.8.4.10 Automatic End of Interrupt Mode .............................................. 143

5.8.5 Masking Interrupts ............................................................................... 144

5.8.5.1 Masking on an Individual Interrupt Request................................ 144

5.8.5.2 Special Mask Mode.................................................................. 144

5.8.6 Steering PCI Interrupts......................................................................... 144

5.9 Advanced Programmable Interrupt Controller (APIC) (D31:F0) .............................. 145

5.9.1 Interrupt Handling................................................................................ 145

5.9.2 Interrupt Mapping ................................................................................ 145

5.9.3 PCI / PCI Express* Message-Based Interrupts.......................................... 146

5.9.4 Front Side Bus Interrupt De liv e ry ............................ ............ ............. ...... 146

5.9.4.1 Edge-Trig ge re d Ope ration......................... .. .. ..................... .. .. .. 147

5.9.4.2 Level-Trigge r e d Ope ration............ .. .. ........... .. .. .. ........... .. .. ........ 147

5.9.4.3 Registers Associated with Front Side Bus Interrupt Delivery....... ... 147

5.9.4.4 Interrupt Message Format........................................................ 147

5.9.5 IOxAPIC Address Remapping ................................................................. 148

5.9.6 External Interrupt Controller Support...................................................... 148

5.10 Serial Interrupt (D31:F0 ) ................ .......... .. ... ..................... .. .. .. ........... .. .. ........ 149

5.10.1 Start Frame......................................................................................... 149

5.10.2 Data Frames........................................................................................ 150

5.10.3 Stop Frame ............. .. ........... .. .. ..................... .. .. ........... .. .. ........... .. .. .... 150

5.10.4 Specific Interrupts Not Supported via SERIRQ.......................................... 150

6Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.10.5 Data Frame Format...............................................................................151

5.11 Real Time Clock (D31:F0).................................................................................152

5.11.1 Update Cycles ......................................................................................152

5.11.2 Interrupts............................................................................................153

5.11.3 Lockable RAM Ranges............................................................................153

5.11.4 Century Rollover... .. ........... .. .. .......... .. ... .......... .. .. ........... .. .. ........... .. ......153

5.11.5 Clearing Battery-Backed RTC RAM...........................................................153

5.12 Processor Interface (D31:F0) ............................................................................155

5.12.1 Processor Interface Signals ....................................................................155

5.12.1. 1 A20M# (Mask A20)..... .. .. ........... .. .. ..................... .. .. ........... .. .. ..155

5.12.1.2 INIT# (Initialization)................................................................156

5.12.1.3 FERR#/IGNNE# (Numeric Coprocessor Error/ Ignore

Numeric Error)........................................................................156

5.12.1.4 NMI (Non-Maskable Interrupt) ..................................................157

5.12.1.5 Stop Clock Request (STP CLK#) ............. ....................................157

5.12.1.6 CPU Power Good (CPUPWRGD)..................................................157

5.12.1.7 Deeper Sleep (DPSL P #) (Mob ile Only).............................. .. ........157

5.12.2 Dual-Processor Issues (Desktop Only) .....................................................158

5.12.2.1 Signal Differen ce s ................ ... .. ..................... .. .. .. ........... .. .. ....158

5.12.2.2 Power Management .................................................................158

5.13 Power Mana ge me nt (D3 1:F0)......... .. .. .......... .. ... ..................... .. .. ..................... ..159

5.13.1 Features..............................................................................................159

5.13.2 Intel® ICH9 and System Power States....... .. .. .. ........... .. .. .. ..................... ..159

5.13.3 System Power Plan es ................... .. .. ..................... ... .. .......... .. .. ........... ..162

5.13.4 SMI#/SCI Generation............................................................................162

5.13.4.1 PCI Express* SCI ....................................................................165

5.13.4.2 PCI Express* Hot-Plug .............................................................165

5.13.5 Dynamic Processor Clock Control ............................................................165

5.13.5.1 Slow C4 and C5 Exit (Mobile Only).............................................166

5.13.5.2 Transition Rules among S0/Cx and Throttling States ....................167

5.13.5.3 Deferred C3/C4 (Mobile Only) ...................................................167

5.13.5.4 POPUP (Auto C3/C4 to C2) (Mobile Only)....................................167

5.13.5.5 POPDOWN (Auto C2 to C3/C4) (Mobile Only)....... ........................168

5.13.5.6 C5 and C6 Entry/Exit (Mobile Only)............................................168

5.13.5.7 C5 Exit (Mobile Only)...............................................................168

5.13.6 Dynamic PCI Clock Control (Mobile Only) .................................................168

5.13.6.1 Conditions for Checking the PCI Clock........................................169

5.13.6.2 Conditions for Maintaining the PCI Clock.....................................169

5.13.6.3 Conditions for Stopping the PCI Clock ........................................169

5.13.6.4 Conditions for Re-Starting the PCI Clock.....................................169

5.13.6.5 LPC Devices and CLKRUN#.......................................................169

5.13.7 Sleep States ........................................................................................170

5.13.7.1 Sleep State Overview...............................................................170

5.13.7.2 Initiating Sleep State...............................................................170

5.13.7.3 Exiting Sleep States.................................................................170

5.13.7.4 PCI Express* WAKE# Signal and PME Even t Messag e...................172

5.13.7.5 Sx-G3-Sx, Handling Power Failures............................................172

5.13.8 Thermal Manage me nt................. ..................... .. .. .. ........... .. .. .................173

5.13.8. 1 THRM# Signal................ .. .. ........... .. .. ........... .. .. .......... ... .. ........173

5.13.8.2 Software Initiated Passive Cooling .............................................173

5.13.8.3 THRM# Override Softw are Bit ........... .. ....................... ...............174

5.13.8.4 Active Cooling.........................................................................174

5.13.9 Event Input Signals and Their Usage .......................................................174

5.13.9.1 PWRBTN# (Power Button) ........................................................174

5.13.9.2 RI# (Ring Indicator)........... .. ... ............ ............. ............. ..........175

5.13.9.3 PME# (PCI Power Management Event) .......................................176

5.13.9.4 SYS_RESET# Signal ................................................................176

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 7

5.13.9.5 THRMTRIP# Sig nal....... .. ........... .. .. .. ........... .. .. ..................... .. .. 176

5.13.10ALT Access Mode.................................................................................. 177

5.13.10.1Write Only Re g isters with Read Paths in ALT Access Mode ............ 178

5.13.10.2PIC Reserved Bits ................................................................... 180

5.13.10.3Read Only Registers with Write Paths in ALT Access Mode ............ 180

5.13.11System Power Supplies, Planes, and Signals ............................................ 181

5.13.11.1Power Plane Control with SLP_S3#, SLP_S4#, SLP_S5#

and SLP_M# .......................................................................... 181

5.13.11.2SL P _S 4 # and Susp e nd-T o -RA M Se q ue n cing ................ ... .. .......... 181

5.13.11.3PWROK Signal........................................................................ 182

5.13.11.4CPUPWRGD Signal .................................................................. 182

5.13.11.5VRMPWRGD Signal.................................................................. 182

5.13.11.6BA TLO W# (Battery Lo w) (Mob ile Only)............. .. .. .. .. .. ............. .. 182

5.13.12Clock Generators.................................................................................. 183

5.13.12.1Clock Control Signals from Intel® ICH9 to Clock

Synthesizer (Mobile Only) ........................................................ 183

5.13.13Legacy Power Management Theory of Operation....................................... 184

5.13.13.1APM Power Management (Desktop Only).................................... 184

5.13.13.2Mobile AP M Pow er Management (Mobile Only) ....... ............. .. .. .... 184

5.13.14Reset Behavior..... .. .. .. ........... .. .. ..................... .. .. ...................... .. .. ........ 184

5.14 System Management (D31:F0).......................................................................... 186

5.14.1 Theory of Operation.............................................................................. 186

5.14.1.1 Detecting a System Lockup...................................................... 186

5.14.1.2 Handling an Intruder............................................................... 186

5.14.1.3 Detecting Improper Firmware Hub Programming......................... 187

5.14.1.4 Heartbeat and Event Reporting via SMLink/SM B us....................... 187

5.14.2 TCO Modes....................... .. .. .......... ... .......... .. .. ........... .. ........... .. .......... 187

5.14.2.1 TCO Legacy/Compatible Mode .................................................. 187

5.14.2.2 Advanced TCO Mode ............................................................... 189

5.15 General Purpose I/O (D31:F0) .......................................................................... 190

5.15.1 Power Wells......................................................................................... 190

5.15.2 SMI# and SCI Routing .......................................................................... 190

5.15.3 Triggering ........................................................................................... 191

5.15.4 Serial POST Codes Over GPIO................................................................ 191

5.15.4.1 Theory of operation................................................................. 191

5.15.4.2 Serial Message Format ............................................................ 192

5.15.5 Controller Link GPIOs (Digital Office Only) ............................................... 193

5.16 SATA Host Controller (D31:F2, F5) ......... .. .. .. ........................ ............ ................. 193

5.16.1 SATA Feature Sup p o rt.................... .. ... ..................... .. .. .......... ... .. .......... 194

5.16.2 Theory of Operation.............................................................................. 195

5.16.2.1 Standard ATA Emulation .......................................................... 195

5.16.2.2 48-Bit LBA Operation............... .. .. ............. ............................... 195

5.16.3 SATA Swap Bay Sup p o rt .... .......... .. .. ........... .. .. ........... .. .. ........... .. .......... 195

5.16.4 Hot Plug Operation ............................................................................... 195

5.16.4.1 Low Power Device Presence Detection ....................................... 195

5.16.5 Function Level Reset Support (FLR) ........................................................ 196

5.16.5.1 FLR Steps.............................................................................. 196

5.16.6 Intel® Matrix Storage Technology Configuration (Intel® ICH9R, ICH9DH,

ICH9DO, ICH9M and ICH9M-E Only) ....................................................... 197

5.16.6.1 Intel® Matrix Storage Manager RAID Option ROM........................ 197

5.16.7 Power Management Operation................................................................ 198

5.16.7.1 Power State Mappings ............................................................. 198

5.16.7.2 Power State Transitions........................................................... 199

5.16.7.3 SMI Trapping (APM)................................................................ 200

5.16.8 SATA Device Pre s ence . ... .......... .. .. ........... .. .. ........... .. .. .......... .. ... ............ 200

5.16.9 SATA LED......................... .. .......... .. ........... .. .. ........... .. .......... ... .......... .. 200

8Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.16.10AHCI Operation ....................................................................................201

5.16.11Serial ATA Reference Clock Low Power Request (SATACLKREQ#) ................201

5.16.12SGPIO Signals......................................................................................201

5.16.12.1Mechanism.............................................................................202

5.16.12.2Message Format......................................................................202

5.16.12.3LED Message Type ..................................................................203

5.16.12. 4SGPIO Waveform ............... ..................... ... .. .. ..................... .. ..205

5.16.13External SATA......................................................................................206

5.17 High Precision Event Timers ..............................................................................206

5.17.1 Timer Accuracy ....................................................................................206

5.17.2 Interrupt Mapping.................................................................................206

5.17.3 Periodic vs. Non-Periodic Modes..............................................................207

5.17.4 Enabling the Tim er s ................. .. ........... .. .. .......... .. ... .. .......... .. .. ........... ..208

5.17.5 Interrupt Levels....................................................................................208

5.17.6 Handling Interrupts...............................................................................208

5.17.7 Issues Related to 64-Bit Timers with 32-Bit Processors ..............................209

5.18 USB UHCI Host Controllers (D29:F0, F1, F2, F3 and D26:F0, F1 and F2) .................209

5.18.1 Data Structures in Main Memory.............................................................209

5.18.2 Data Transfers to/from Main Memory ......................................................209

5.18.3 Data Encoding and Bit Stuffing ...............................................................210

5.18.4 Bus Protocol .........................................................................................210

5.18.4.1 Bit Ordering................................ .. .. ..................... .. .. ...............210

5.18.4.2 SYNC Field .............................................................................210

5.18.4.3 Packet Field Formats................................................................210

5.18.4.4 Address Fields.........................................................................210

5.18.4.5 Frame Number Field ................................................................210

5.18.4.6 Data Field ..............................................................................210

5.18.4.7 Cyclic Redundancy Check (CRC)................................................210

5.18.5 Packet Formats ....................................................................................210

5.18.6 USB Interrupts .....................................................................................211

5.18.6.1 Transaction-Based Interrupts....................................................211

5.18.6.2 Non-Transaction Based Interrupts ............. ... .. .. ............ ... .. ........213

5.18.7 USB Power Management........................................................................213

5.18.8 USB Legacy Keyboard Operation.............................................................214

5.18.9 Function Level Reset Support (FLR).........................................................216

5.18.9. 1 FLR Steps............ .. .. .......... .. ... .......... .. .. ........... .. .. ........... .. ......216

5.19 USB EHCI Host Controllers (D29:F7 and D26:F7).................................................217

5.19.1 EHC Initialization..................................................................................217

5.19.1.1 BIOS Initialization ...................................................................217

5.19.1.2 Driver Initialization..................................................................217

5.19.1. 3 EHC Resets ................... .. .. .. ........... .. .. ........... .. .. ........... .. .. ......218

5.19.2 Data Structures in Main Memory.............................................................218

5.19.3 USB 2.0 Enhanced Host Controller DMA ...................................................218

5.19.4 Data Encoding and Bit Stuffing ...............................................................218

5.19.5 Packet Formats ....................................................................................219

5.19.6 USB 2.0 Interrupts and Error Conditions ..................................................219

5.19.6.1 Aborts on USB 2.0-Initiated Me mory Re ad s........................... .. ....219

5.19.7 USB 2.0 Power Management ..................................................................220

5.19.7.1 Pause Feature.........................................................................220

5.19.7.2 Suspend Feature.....................................................................220

5.19.7.3 ACPI Device States..................................................................220

5.19.7.4 ACPI System States.................................................................221

5.19.7.5 Mobile Considerations ..............................................................221

5.19.8 Interaction with UHCI Host Controllers......... .. .. .. ............. .. ............. .. ........221

5.19.8.1 Port-Routing Logic...................................................................222

5.19.8.2 Device Connects ...... .. ..................... .. .. .. ........... .. .. ...................223

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 9

5.19.8.3 Device Disconnects ................................................................. 224

5.19.8.4 Effect of Resets on Port-Routing Logic........................................ 224

5.19.9 USB 2.0 Legacy Keyb oard Ope ration........................................... ............ 224

5.19.10USB 2.0 Based Debug Port ............. .. ... .......... .. .. ........... .. .. ........... .. .. ...... 225

5.19.10.1 Theory of Operation ............................................................... 225

5.19.11USB Pre-Fetch Based Pause................... ............................... .. ... .. .......... 229

5.19.12Function Level Reset Support (FLR) ........................................................ 230

5.19.12.1 F LR Ste ps............................ .. .......... .. .. ........... .. .. ........... .. .. .... 230

5.20 SMBus Controller (D31:F3)............................................................................... 230

5.20.1 Host Controller..................................................................................... 231

5.20.1.1 Command Protocols ................................................................ 231

5.20.2 Bus Arbitration..................................................................................... 235

5.20.3 Bus Timing.......................................................................................... 235

5.20.3.1 Clock Stretching ..................................................................... 235

5.20.3.2 Bus Time Out (Intel® ICH9 as SMBus Master)............................. 235

5.20.4 Interrupts / SMI#................................................................................. 236

5.20.5 SMBALERT# ........................................................................................ 237

5.20.6 SMBus CRC Generation and Checking...................................................... 237

5.20.7 SMBus Slave Interface .......................................................................... 237

5.20.7.1 Format of Slave Write Cycle ..................................................... 238

5.20.7.2 Format of Read Command........................................................ 240

5.20.7.3 Slave Read of RTC Time Bytes.................................................. 242

5.20.7.4 Format of Host Notify Command ............................................... 243

5.21 Intel® High Definition Audio Overview................................................................ 244

5.21.1 Intel® High Definition Audio Docking (Mobile Only)................................... 244

5.21.1.1 Dock Sequence....................................................................... 244

5.21.1.2 Exiting D3/CRST# when Docked ............................................... 245

5.21.1.3 Cold Boot/Resume from S3 When Docked .................................. 246

5.21.1.4 Undock Sequen ce ........................... .. .. ........... .. .. ........... .. .. ...... 246

5.21.1.5 Interaction Between Dock/Undock and Power Management States. 247

5.21.1.6 Relationship between HDA_DOCK_RST# and HDA_RST# ............. 247

5.21.2 Function Level Reset Support (FLR) ........................................................ 248

5.21.2.1 FLR Steps.............................................................................. 248

5.22 Intel® Active Man a gement Tec hnology (Int el® AMT) (Digital Office Only)................ 248

5.22.1 Intel® AMT Features............................................................................. 249

5.22.2 Intel® AMT Requirements...................................................................... 249

5.23 Serial Peripheral Interface (SPI)........................................................................ 249

5.23.1 SPI Supported Feature Overview............................................................ 249

5.23.1.1 Non-Descriptor Mode............................................................... 250

5.23.1.2 Descriptor Mode ..................................................................... 250

5.23.1.3 Device Partitioning.................................................................. 251

5.23.2 Flash Descriptor................................................................................... 251

5.23.2.1 Descriptor Master Region......................................................... 253

5.23.3 Flash Access........................................................................................ 254

5.23.3.1 Direct Access Security ............................................................. 254

5.23.3.2 Register Access Security.......................................................... 254

5.23.4 Serial Flash Device Compatibility Requirements........................................ 254

5.23.4.1 Intel® ICH9 SPI Based BIOS Requirements .............. .................. 255

5.23.4.2 Integrated LAN Firmware SPI Flash Requirements ....................... 255

5.23.4.3 Intel® Management Engine Firmware SPI Flash Requirements....... 255

5.23.4.4 Hardware Sequencing Requirements.......................................... 256

5.23.5 Multiple Page Write Usage Model ............ ................................................ 257

5.23.5.1 Soft Flash Protection ............................................................... 257

5.23.5.2 BIOS Range Write Protection.................................................... 257

5.23.5.3 SMI# Based Global Write Protection ............... .. .. .. .. ............. .. .... 258

5.23.6 Flash Device Configurations................................................................... 258

10 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.23.7 SPI Flash Device Recommended Pinout....................................................258

5.23.8 Serial Flash Device Package ...................................................................259

5.23.8.1 Common Footprint Usage Model....................... .. .. .. ............. .. ....259

5.23.8.2 Serial Flash Device Package Recommendations ...........................259

5.24 Intel® Quiet System Technology (Intel® QST) (Desktop Only) ...............................260

5.24.1 PWM Outputs.......................................................................................260

5.24.2 TACH Inputs ........................................................................................260

5.25 Thermal Sensors. .. ........... .. .. ........... .. .. .......... ... .. .......... .. ........... .. .. ........... .. .. ....260

5.26 Feature Capability Mechanism ...........................................................................261

5.27 Integrated Trus ted Platform Mod ule (Mob ile Only)................... .. .. .. .. ............. .. .. .. ..261

5.27.1 Integrated TPM Hardware Requireme nts ............ .. .. .. ................................261

5.27.2 Enabling integrated TPM ............. ..................... .. .. .. ...................... .. .. .. ....261

6 Ballout Definition...................................................................................................263

6.1 Intel® ICH9 Ballout (Desktop Only).......................... ....................... ............. ......263

6.2 Intel® 82801IBM ICH9M and 82801IEM ICH9M-E Ballout (Mobile Only).......... .........27 2

6.3 Intel® ICH9M-SFF Ballout (Mobile Only)................ .. .. .. .. ............. .. ............. ..........281

7 Package Information .............................................................................................289

7.1 Intel® ICH9 Package (Desk top Only)..................................................................289

7.2 Intel® ICH9 Mobile Package (Mob ile Only)............... ............ ... ............ .. ............. ..291

7.2.1 Intel® 82801IBM ICH9M and 82801IEM ICH9M-E Package............ ..............291

7.2.2 Intel® ICH9M - S SF Packag e..... .......... .. ... ..................... .. .. .. ........... .. .. ......293

8 Electrical Characteristics........................................................................................295

8.1 Thermal Specifications................................. .....................................................295

8.2 Absolute Maximum Ratings ...............................................................................295

8.3 DC Characteristics ............................................. .. .. .. ................................ .. .. .. ..295

8.4 AC Characteristics.............. .. .. ................................ .. .. .. ................................ .. ..308

8.5 Timing Diagrams ........... .. .. ........... .. .. ..................... .. .. ..................... .. .. ........... ..321

9 Register and Memory Mapping...............................................................................333

9.1 PCI Devices and Functions ................................................................................334

9.2 PCI Configuration Map......................................................................................335

9.3 I/O Map..........................................................................................................335

9.3.1 Fixed I/O Address Ranges......................................................................335

9.3.2 Variable I/O Decode Ranges...................................................................338

9.4 Memory Map...................................................................................................339

9.4.1 Boot-Block Up date Sc he me....... .. .. .. .. ............. ............. ............ ............. ..340

10 Chipset Configuration Registers.............................................................................343

10.1 Chipset Configuration Registers (Memory Space) .................................................343

10.1.1 VCH—Virtual Channel Capability Header Register ......................................346

10.1.2 VCAP1—Virtual Channel Capability #1 Register.........................................346

10.1.3 VCAP2—Virtual Channel Capability #2 Register.........................................347

10.1.4 PVC—Port Virtual Channel Control Register...............................................347

10.1.5 PVS—Port Virtual Channel Status Register................................................347

10.1.6 V0CAP—Virtual Channel 0 Resource Capability Register..............................348

10.1.7 V0CTL—Virtual Channel 0 Resource Control Register .................................349

10.1.8 V0STS—Virtual Channel 0 Resource Status Register ........................ .. ........349

10.1.9 V1CAP—Virtual Channel 1 Resource Capability Register..............................350

10.1.10V1CTL—Virtual Channel 1 Resource Control Register .................................350

10.1.11V1STS—Virtual Channel 1 Resource Status Register ..................................351

10.1.12PAT—Port Arbi tration Ta b le ........... .. ................................ .. .. .. .................351

10.1.13CIR1—Chipset Initialization Register 1.....................................................352

10.1.14REC—Root Error Command Regi ster.......... .. .. ............. ............ ............. ....352

10.1.15RCTCL—Root Complex Topology Capabilities List Register ..........................352

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 11

10.1.16ESD—Element Self Description Register................................................... 353

10.1.17ULD—Upstream Link Descriptor Register ................................................. 353

10.1.18ULBA—Upstream Link Base Ad d r ess Re g i ster . .. .. .. .. ... .. ............ ............. .... 353

10.1.19RP1D—Root Port 1 Descriptor Register.................................................... 354

10.1.20RP1BA—Root Port 1 Base Address Register.............................................. 354

10.1.21RP2D—Root Port 2 Descriptor Register.................................................... 354

10.1.22RP2BA—Root Port 2 Base Address Register.............................................. 355

10.1.23RP3D—Root Port 3 Descriptor Register.................................................... 355

10.1.24RP3BA—Root Port 3 Base Address Register.............................................. 355

10.1.25RP4D—Root Port 4 Descriptor Register.................................................... 356

10.1.26RP4BA—Root Port 4 Base Address Register.............................................. 356

10.1.27HDD—Intel® High Definition Audio Descriptor Register .............................. 356

10.1.28HDBA—Intel® High Definition Audio Base Address Register ........................ 357

10.1.29RP5D—Root Port 5 Descriptor Register.................................................... 357

10.1.30RP5BA—Root Port 5 Base Address Register.............................................. 357

10.1.31RP6D—Root Port 6 Descriptor Register.................................................... 358

10.1.32RP6BA—Root Port 6 Base Address Register.............................................. 358

10.1.33ILCL—Internal Link Capabilities List Register ............................................ 358

10.1.34LCAP—Link Capabilities Register............................................................. 359

10.1.35LCTL—Link Control Register................................................................... 359

10.1.36LSTS—Link Status Register.................................................................... 359

10.1.37CIR2 — Chipset Initialization Register 2................................................... 360

10.1.38CIR3 — Chipset Initialization Register 3................................................... 360

10.1.39BCR — Backbone Configuration Register.................................................. 360

10.1.40RPC—Root Port Configuration Register .................................................... 361

10.1.41DMIC—DMI Control Register .................................................................. 362

10.1.42RPFN—Root Port Function Number and Hide for PCI Express* Root Ports ..... 362

10.1.43FLRSTAT—FLR Pending Status Register ................................................... 363

10.1.44CIR13—Chipset Initialization Register 13................................................. 364

10.1.45CIR 5—Chipset Initialization Register 5..................................................... 364

10.1.46TRSR—Trap Status Register................................................................... 364

10.1.47TRCR—Trapped Cycle Register ............................................................... 365

10.1.48TWDR—Trapped Write Data Register....................................................... 365

10.1.49IOTRn — I/O Trap Register (0-3)............................................................ 366

10.1.50DMC—DMI Miscellaneous Control Register ............................................... 367

10.1.51CIR 6—Chipset Initialization Register 6..................................................... 367

10.1.52CIR 7—Chipset Initialization Register 7..................................................... 368

10.1.53CIR11—Chipset Initialization Register 11 (Mobile Only).............................. 368

10.1.54CIR12—Chipset Initialization Register 12 (Mobile Only).............................. 368

10.1.55TCTL—TCO Configuration Register.......................................................... 369

10.1.56D31IP—Device 31 Interrupt Pin Register.................................................. 369

10.1.57D30IP—Device 30 Interrupt Pin Register.................................................. 370

10.1.58D29IP—Device 29 Interrupt Pin Register.................................................. 371

10.1.59D28IP—Device 28 Interrupt Pin Register.................................................. 372

10.1.60D27IP—Device 27 Interrupt Pin Register.................................................. 373

10.1.61D26IP—Device 26 Interrupt Pin Register.................................................. 374

10.1.62D25IP—Device 25 Interrupt Pin Register.................................................. 375

10.1.63D31IR—Device 31 Interrupt Route Register ............................................. 375

10.1.64D30IR—Device 30 Interrupt Route Register ............................................. 376

10.1.65D29IR—Device 29 Interrupt Route Register ............................................. 377

10.1.66D28IR—Device 28 Interrupt Route Register ............................................. 378

10.1.67D27IR—Device 27 Interrupt Route Register ............................................. 379

10.1.68D26IR—Device 26 Interrupt Route Register ............................................. 380

10.1.69D25IR—Device 25 Interrupt Route Register ............................................. 381

10.1.70OIC—Other Interrupt Control Register..................................................... 382

12 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.71SBEMC3—Scheduled Break Event C3 Exit Latency (Mobile Only)..................382

10.1.72SBEMC4—Scheduled Break Event C4 Exit Latency (Mobile Only)..................383

10.1.73RC—RTC Configuration Register..............................................................383

10.1.74HPTC—High Precision Timer Configuration Register ...................................384

10.1.75GCS—General Control and Status Register ...............................................385

10.1.76BUC—Backed Up Control Register ...........................................................387

10.1.77FD—Function Disable Register ................................................................388

10.1.78CG—Clock Gating..................................................................................390

10.1.79FDSW—Function Disable SUS Well ..........................................................392

10.1.80CIR8—Chipset Initialization Register 8.....................................................392

10.1.81CIR9—Chipset Initialization Register 9.....................................................392

10.1.82PPO - Port Power Off.............................................................................392

10.1.83CIR10 - Chipset Initialization Register 10.................................................393

10.1.84MAP - Remap Control Regi ste r..... .. .. .. .....................................................393

11 PCI-to-PCI Bridge Registers (D30:F0)....................................................................395

11.1 PCI Configuration Registers (D30:F0).................................................................395

11.1.1 VID— Vendor Identification Register (PCI-P CI—D30:F0)....... ........... ...........396

11.1.2 DID— Device Identification Register (PCI-PCI—D30:F0).......................... ...396

11.1.3 PCICMD—PC I Command (PCI-PCI—D30:F0 )... .. .. .. .. .. ... ............ ............. ....397

11.1.4 PSTS—PCI Status Register (PCI-PCI—D30:F0)..........................................397

11.1.5 RID—Revision Identification Register (PCI-PCI—D30:F0)............................399

11.1.6 CC—Class Code Register (PCI-PCI—D30:F0).............................................399

11.1.7 PMLT—Primary Master Latency Timer Register (PCI-PCI—D30:F0)...............400

11.1.8 HEADTYP—Head er Ty pe Reg ister (PCI-PCI—D30:F0) ......................... .. ......400

11.1.9 BNUM—Bus Number Register (PCI-PCI—D 30 :F0 ) ............... ............. .. .. .. ....400

11.1.10SMLT—Seco n dary Mas t er Late ncy Ti m er Re g i st er (PCI-PCI—D30: F 0 )... .. .. .. ..401

11.1.11IOBASE_LIMIT—I/O Base and Limit Regi ster (PC I -PC I—D 30 :F0 ) .................401

11.1.12SECSTS—Second a ry Status Regi ster (PC I -PC I —D3 0 :F0) ............... ... ..........402

11.1.13MEMBASE_LIMIT—Memory Base and Limit Register

(PCI-PCI—D30:F0)................................................................................403

11.1.14PREF_MEM_BASE_LIMIT—Prefetchable Memory Base

and Limit Register (PC I-PCI—D30:F0) .............................. .......................403

11.1.15PMBU32—Prefetchable Memory Base Upper 32 Bits

11.1.16PMLU32—Prefetchable Memory Limit Upper 32 Bits

11.1.17CAPP—Capability List Pointer Register (PCI-PCI—D30:F0) ..........................404

11.1.18INTR—Interrupt Information Register (PCI-PCI—D30:F0)...........................404

11.1.19BCTRL—Bridge Control Register (PCI-PCI—D30:F0)...................................405

11.1.20SPDH—Secondary PCI Device Hiding Register (PCI-PCI—D30:F0)................406

11.1.21DTC—Delayed Transaction Control Register (PCI-PCI—D30:F0)...................407

11.1.22BPS—Bridge Proprietary Status Register (PCI-PCI—D30:F0) .......................408

11.1.23BPC—Bridge Policy Configuration Register (PCI-PCI—D30:F0).....................409

11.1.24SVCAP—Subsystem Vendor Capability Register (PCI-PCI—D30:F0)..............410

11.1.25SVID—Subsystem Vendor IDs Register (PCI-PCI—D30:F0).........................410

12 Gigabit LAN Configuration Registers ......................................................................411

12.1 Gigabit LAN Configuration Registers (Gigabit LAN — D25:F0).................................411

12.1.1 VID—Vendor Identification Register

(Gigabit LAN—D25:F0) ..........................................................................412

12.1.2 DID—Device Identification Register

(Gigabit LAN—D25:F0) ..........................................................................412

12.1.3 PCICMD—PCI Command Register

(Gigabit LAN—D25:F0) ..........................................................................413

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 13

12.1.4 PCISTS—PCI Status Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 414

12.1.5 RID—Revision Identification Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 415

12.1.6 CC—Class Code Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 415

12.1.7 CLS—Cache Line Size Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 415

12.1.8 PLT—Primary Latency Timer Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 415

12.1.9 HT —Header Type Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 415

12.1.10MBARA—Memory Base Address Register A

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 416

12.1.11MBARB—Memory Base Address Register B

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 416

12.1.12MBARC—Memory Base Address Register C

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 417

12.1.13SVID—Subsystem Vendor ID Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 417

12.1.14SID—Subsystem ID Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 417

12.1.15ERBA—Expansion ROM Base Address Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 417

12.1.16CAPP—Capabilities List Pointe r Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 418

12.1.17INTR—Interrupt Information Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 418

12.1.18MLMG—Maximum Latency/Minimum Grant Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 418

12.1.19CLIST 1—Capabilities List Register 1

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 418

12.1.20PMC—PCI Powe r Management Capabilities Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 419

12.1.21PMCS—PCI Power Management Control and Status

12.1.22DR—Data Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 421

12.1.23CLIST 2—Capabilities List Register 2

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 421

12.1.24MCTL—Message Control Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 421

12.1.25MADDL—Message Address Low Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 422

12.1.26MADDH—Message Address High Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 422

12.1.27MDAT—Message Data Register

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 422

12.1.28FLR CAP—Function Level Reset Capability

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 422

12.1.29FLR CLV—Function Level Reset Capability Le ngth and Version

(Gigabit LAN—D25:F0)................... ........................................... .. .. .. ...... 423

12.1.30DEVCTRL—Device Control (Gigabit LAN—D25:F0)..................................... 423

12.2 MBARA—Gigabit LAN Base Address A Registers ................................................... 424

12.2.1 LDR4—LAN Device Initialization Register 4

(Gigabit LAN Memory Mapped Base Address Register)............................... 424

14 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

12.2.2 LDR 3—LAN Device Initialization Register 3

(Gigabit LAN Memory Mapped Base Address Register) ... ............................42 4

12.2.3 LDCR2—LAN Device Control Register 2

(Gigabit LAN Memory Mapped Base Address Register) ... ............................42 5

12.2.4 LDCR4—LAN Device Control Register 4

(Gigabit LAN Memory Mapped Base Address Register) ... ............................42 5

12.2.5 LDR5—LAN Device Control Register 5

(Gigabit LAN Memory Mapped Base Address Register) ... ............................42 5

12.2.6 LDR 2—LAN Device Initialization Register 1

(Gigabit LAN Memory Mapped Base Address Register) ... ............................42 5

13 LPC Interface Bridge Registers (D31:F0) ...............................................................427

13.1 PCI Configuration Registers (LPC I/F—D31:F0) ....................................................427

13.1.1 VID—Vendor Identification Register (LPC I/F—D31:F0) ..............................428

13.1.2 DID—Device Identification Register (LPC I/F—D31:F0)..... ..........................428

13.1.3 PCICMD—PCI COMMAND Register (LPC I/F—D31:F0).................................429

13.1.4 PCISTS—PCI Status Register (LPC I/F—D31:F0)........................................430

13.1.5 RID—Revision Identification Register (LPC I/F—D31: F0 ) ... .......... .. ........... ..431

13.1.6 PI—Programming Interface Register (LPC I/F—D31:F0) ............. ................431

13.1.7 SCC—Sub Class Code Re g i ster (LP C I/F—D31:F0) .............. ............. ..........431

13.1.8 BCC—Base Class Code Register (LPC I/F—D31:F0)....................................431

13.1.9 PLT—Primary Latency Timer Register (LPC I/F—D31:F0) ............................431

13.1.10HEADTYP — He ad er Ty pe Reg i ster (LP C I/F—D31:F0)......... .. .......................432

13.1.11SS—Sub System Identifiers Register (LPC I/F—D31:F0).......................... ...432

13.1.12CAPP—Capability List Pointer (LPC I/F—D31:F0) .......................................432

13.1.13PMBASE—ACPI Base Address Register (LPC I/F—D31:F0)...........................432

13.1.14ACPI_CNTL—ACPI Control Register (LPC I/F — D31:F0) .............................433

13.1.15GPIOBASE—GPIO Base Address Register (LPC I/F — D31:F0) .....................434

13.1.16GC—GPIO Control Register (LPC I/F — D31:F0) ........................................435

13.1.17PIRQ[n]_ROUT—PIRQ[A,B,C,D] Routing Control Register

(LPC I/F—D31:F0) ................................................................................436

13.1.18SIRQ_CNTL—Serial IRQ Control Register

(LPC I/F—D31:F0) ................................................................................437

13.1.19PIRQ[n]_ROUT—PIRQ[E,F,G,H] Routing Control Register

(LPC I/F—D31:F0) ................................................................................438

13.1.20LPC_IBDF—IOxAPIC Bus:Device:Function

(LPC I/F—D31:F0) ................................................................................439

13.1.21LPC_I/O_DEC—I/O Decode Ranges Register

(LPC I/F—D31:F0) ................................................................................439

13.1.22LPC_EN—LPC I/F Enables Register (LPC I/F—D31:F0)................................440

13.1.23GEN1_DEC—LPC I/F Generic Decode Range 1 Register

(LPC I/F—D31:F0) ................................................................................441

13.1.24GEN2_DEC—LPC I/F Generic Decode Range 2 Register

(LPC I/F—D31:F0) ................................................................................442

13.1.25GEN3_DEC—LPC I/F Generic Decode Range 3 Register

(LPC I/F—D31:F0) ................................................................................442

13.1.26GEN4_DEC—LPC I/F Generic Decode Range 4 Register

(LPC I/F—D31:F0) ................................................................................443

13.1.27FWH_SEL1—Firmware Hub Select 1 Register

(LPC I/F—D31:F0) ................................................................................444

13.1.28FWH_SEL2—Firmware Hub Select 2 Register

(LPC I/F—D31:F0) ................................................................................445

13.1.29FWH_DEC_EN1—Firmware Hub Decode Enable Register

(LPC I/F—D31:F0) ................................................................................445

13.1.30BIOS_CNTL—BIOS Control Register

(LPC I/F—D31:F0) ................................................................................449

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 15

13.1.31FDCAP—Feature De tection Capability ID

(LPC I/F—D31:F0)................................................................................ 450

13.1.32FDLEN—Feature Detection Capability Length

(LPC I/F—D31:F0)................................................................................ 450

13.1.33FDVER—Feature Detection Version

(LPC I/F—D31:F0)................................................................................ 450

13.1.34FDVCT—Feature Vector

(LPC I/F—D31:F0)................................................................................ 451

13.1.35RCBA—Root Complex Base Address Register

(LPC I/F—D31:F0)................................................................................ 451

13.2 DMA I/O Registers (LPC I/F—D31:F0) ..................................... .. .. ..................... .. 452

13.2.1 DMABASE_CA—D M A Ba se and Curre nt Ad dress

Registers (LPC I/F—D31:F0).................................................................. 453

13.2.2 DMABASE_CC—DMA Base and Current Count Registers

(LPC I/F—D31:F0)................................................................................ 454

13.2.3 DM AMEM_LP—DMA Memory Low Page Registers

(LPC I/F—D31:F0)................................................................................ 454

13.2.4 DMACMD—DMA Command Register (LPC I/F—D31:F0).............................. 455

13.2.5 DMASTA—DMA Status Register (LPC I/F—D31:F0).................................... 455

13.2.6 DMA_WRSMSK—DMA Write Single Mask Register

(LPC I/F—D31:F0)................................................................................ 456

13.2.7 DMACH_MODE—DMA Channel Mode Register

(LPC I/F—D31:F0)................................................................................ 457

13.2.8 DMA Clear Byte Pointer Register (LPC I/F—D31:F0) .................................. 458

13.2.9 DMA Master Clear Register (LPC I/F—D31:F0).......................................... 458

13.2.10DMA_CLMSK—DMA Clear Mask Register (LPC I/F—D31:F0)........................ 458

13.2.11DMA_WRMSK—DMA Write All Mask Register

(LPC I/F—D31:F0)................................................................................ 459

13.3 Timer I/O Registers (LPC I/F—D31:F0)............................................................... 460

13.3.1 TCW—Timer Control Word Register (LPC I/F—D31:F0) .............................. 461

13.3.2 RDBK_CMD—Read Back Command (LPC I/F—D31:F0)............................... 462

13.3.3 SBYTE_F MT—Interval Timer Status Byte Format Register

(LPC I/F—D31:F0)................................................................................ 463

13.3.4 Counter Access Ports Register (LPC I/F—D31:F0) ..................................... 464

13.4 8259 Interrupt Controller (PIC) Registe r s

(LPC I/F—D31:F0)........................................................................................... 465

13.4.1 Interrupt Controller I/O MAP (LPC I/F—D31:F0) ....................................... 465

13.4.2 ICW1—Initialization Command Word 1 Register

(LPC I/F—D31:F0)................................................................................ 466

13.4.3 ICW2—Initialization Command Word 2 Register

(LPC I/F—D31:F0)................................................................................ 467

13.4.4 ICW3—Master Controller Initialization Command

Word 3 Register (LPC I/F—D31:F0)......................................................... 468

13.4.5 I CW3—Slave Controller Initialization Command

Word 3 Register (LPC I/F—D31:F0)......................................................... 468

13.4.6 ICW4—Initialization Command Word 4 Register

(LPC I/F—D31:F0)................................................................................ 469

13.4.7 OCW1—Operational Control Word 1 (Interrupt Mask)

13.4.8 O CW2—Operational Control Word 2 Register

(LPC I/F—D31:F0)................................................................................ 470

13.4.9 O CW3—Operational Control Word 3 Register

(LPC I/F—D31:F0)................................................................................ 471

13.4.10ELCR1—Master Controller Edge/Level Triggered Register

(LPC I/F—D31:F0)................................................................................ 472

13.4.11ELCR2—Slave Controller Edge/Level Triggered Register

(LPC I/F—D31:F0)................................................................................ 473

16 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.5 Advanced Programmable Interrupt Controller (APIC)(D31:F0)................................474

13.5.1 APIC Register Map (LPC I/F—D31:F0)......................................................474

13.5.2 IND—Index Register (LPC I/F—D31:F0)...................................................474

13.5.3 DAT—Data Register (LPC I/F—D31:F0)....................................................475

13.5.4 EOIR—EOI Register (LPC I/F—D31 : F0) ....................... ............ ............. ....475

13.5.5 ID—Identification Register (LPC I/F—D31:F0)...........................................476

13.5.6 VER—Version Register (LPC I/F—D31:F0) ................................................476

13.5.7 REDIR_TBL—Redirection Table (LPC I/F—D31:F0).....................................477

13.6 Real Time Clock Registers.................................................................................479

13.6.1 I/O Register Address Map ......................................................................479

13.6.2 Indexed Registers.................................................................................480

13.6.2.1 RTC_REGA—Register A ............................................................481

13.6.2.2 RTC_REGB—Register B (General Configuration)...........................482

13.6.2.3 RTC_REGC—Register C (Flag Register).......................................483

13.6.2.4 RTC_REGD—Register D (Flag Register).......................................483

13.7 Processor Interface Registers (LPC I/F—D31:F0)..................................................484

13.7.1 NMI_SC—NMI Status and Control Register

(LPC I/F—D31:F0) ................................................................................484

13.7.2 NMI_EN—NMI Enable (and Real Time Clock Index)

13.7.3 PORT92—Fast A20 and Init Register (LPC I/F—D31:F0) . ............ ................485

13.7.4 COPROC_ERR—Coprocessor Error Register

(LPC I/F—D31:F0) ................................................................................486

13.7.5 RST_CNT—Reset Control Register (LPC I/F—D31:F0).................................486

13.8 Power Manage me nt Regi sters (PM —D31:F0) ......... .. .. .. ............. ............ ............. ..487

13.8.1 Power Management PCI Configuration Registers

(PM—D31:F0) ......................................................................................487

13.8.1.1 GEN_PMCON_1—General PM Configuration 1 Register

(PM—D31:F0).........................................................................488

13.8.1.2 GEN_PMCON_2—General PM Configuration 2 Register

(PM—D31:F0).........................................................................490

13.8.1.3 GEN_PMCON_3—General PM Configuration 3 Register

(PM—D31:F0).........................................................................492

13.8.1.4 GEN_PMCON_LOCK- General Power Management

Configuration Lock Register ......................................................494

13.8.1.5 C5_EXIT_TIMING_CNT- C5 Exit Timing Register (Mobile Only).... .. .495

13.8.1.6 Cx-STATE_CNF—Cx State Configuration Register

(PM—D31:F0) (Mobile Only, Except Bit 2)...................................496

13.8.1.7 C4-TIMING_CNT—C4 Timing Control Register

(PM—D31:F0) (Mob ile Only) ................. .. .. ... ............ ............. ....497

13.8.1.8 BM_BREAK_EN Register (PM—D31:F0) (Mobile Only) ...................498

13.8.1.9 PMIR—Power M a nagement Initialization Register (PM—D31:F0 ).....499

13.8.1.10GPIO_ROUT—GPIO Routing Control Register

(PM—D31:F0).........................................................................499

13.8.2 APM I/O Decode .............................. .. ... ..................... .. .. ..................... ..500

13.8.2.1 APM_CNT—Advanced Power Management Control Port Register.....500

13.8.2.2 APM_STS—Advanced Power Management Status Port Register ......500

13.8.3 Power Manageme nt I/O Regi ste rs ........... .. .. ....................... .....................501

13.8.3.1 PM1_STS—Power Management 1 Status Register.........................503

13.8.3.2 PM1_EN—Power Management 1 Enable Register............ ..............506

13.8.3.3 PM1_CNT—Power Management 1 Control....................................507

13.8.3.4 PM1_TMR—Power Management 1 Timer Register.........................508

13.8.3.5 PROC_CNT—Processor Control Register......................................508

13.8.3.6 LV2 — Level 2 Register ............................................................510

13.8.3.7 LV3—Level 3 Reg i ster (Mobile Only)...................... ............. ........510

13.8.3.8 LV4—Level 4 Reg i ster (Mobile Only)...................... ............. ........510

13.8.3.9 LV5—Level 5 Reg i ster (Mobile Only)...................... ............. ........511

13.8.3.10LV6—Level 6 Register (Mobile Only)...........................................511

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 17

13.8.3.11GPE0_STS—General Purpose Event 0 Status Register .................. 512

13.8.3.12GPE0_EN—Gene r al Pu rpose Event 0 Enables Register ............. .. ... 515

13.8.3.13SMI_EN—SMI Control and Enable Register ................................. 517

13.8.3.14SMI_STS—SMI Status Register................................................. 519

13.8.3.15ALT_GP_SMI_EN—Alternate GPI SMI Enable Register .................. 521

13.8.3.16ALT_GP_SMI_STS—Alternate GPI SMI Status Register ................. 522

13.8.3.17UPRWC—USB Per-Port Registers Write Control............................ 522

13.8.3.18GPE_CNTL— Gene ral Purpose Control Register............ ............... . 523

13.8.3.19DEVACT_STS — Device Activity Status Register .......................... 523

13.8.3.20PM2_CNT—Power Management 2 Control (Mobile Only)................ 524

13.8.3.21C3_RES— C3 Residency Register (Mobile Only)............. .............. 524

13.8.3.22C5_RES— C5 Residency Register (Mobile Only)............. .............. 525

13.9 System Management TCO Registers (D31:F0)..................................................... 526

13.9.1 TCO_RLD—TCO Timer Reload and Current Value Register .......................... 526

13.9.2 TCO_DAT_IN—TCO Data In Register....................................................... 527

13.9.3 TCO_DAT_OUT—TCO Data Out Register .................................................. 527

13.9.4 TCO1_STS—TCO1 Status Register .......................................................... 527

13.9.5 TCO2_STS—TCO2 Status Register .......................................................... 529

13.9.6 TCO1_CNT—TCO1 Control Register......................................................... 531

13.9.7 TCO2_CNT—TCO2 Control Register......................................................... 532

13.9.8 TCO_MESSAGE1 and TCO_MESSAGE2 Registers....................................... 532

13.9.9 TCO_WDCNT—TCO Watchdog Control Register......................................... 533

13.9.10SW_IRQ_GEN—Software IRQ Generation Register .................................... 533

13.9.11TCO_TMR—TCO Timer Initial Value Register............................................. 533

13.10 General Purpose I/O Registers (D31:F0)............................................................. 534

13.10.1GPIO_USE_SEL—GPIO Use Select Register [31:0] .................................... 535

13.10.2GP_IO_SEL—GPIO Input/Output Select Register [31:0]............................. 535

13.10.3GP_LVL—GPIO Level for Input or Output Register [31:0]........................... 536

13.10.4GPO_BLINK—GPO Blink Enab le Reg i ste r [31:0 ] ..................... .. ............. .. .. 536

13.10.5GP_SER_BLINK[31:0]—GP Serial Blink [31:0].......................................... 537

13.10.6GP_SB_CMDSTS[31:0]—GP Serial Blink Command Status [31:0]... .. .. .. .. .. .. . 538

13.10.7GP_SB_DATA[31:0]—GP Serial Blink Data [31:0] ..................................... 538

13.10.8GPI_INV—GPIO Signal Invert Register [31:0]........................................... 539

13.10.9GPIO_USE_SEL2—GPIO Use Select 2 Register [60:32] .............................. 539

13.10.10GP_IO_SEL2—GPIO Input/Output Select 2 Register [60:32] . .................... 540

13.10.11GP_LVL2—GPIO Level for Inp ut or Output 2 Register [63:32] ................... 540

14 SATA Controller Registers (D31:F2)....................................................................... 541

14.1 PCI Configuration Registers (SATA–D31:F2) ........................................................ 541

14.1.1 VID—Vendor Identification Register (SATA—D31:F2) ................................ 542

14.1.2 DID—Device Identification Register (SATA—D31:F2)............... ............. ..... 543

14.1.3 PCICMD—PCI Command Register (SATA–D31:F2)..................................... 543

14.1.4 PCISTS — PCI Status Register (SATA–D31:F2)......................................... 544

14.1.5 RID—Revision Identification Register (SATA—D31:F2)............................... 545

14.1.6 PI—Programming Interface Register (SATA–D31:F2)................................. 545

14.1.6.1 When Sub Class Code Register (D31:F2:Offset 0Ah) = 01h .......... 545

14.1.6.2 When Sub Class Code Register (D31:F2:Offset 0Ah) = 04h .......... 546

14.1.6.3 When Sub Class Code Register (D31:F2:Offset 0Ah) = 06h .......... 546

14.1.7 SCC—Sub Class Code Register (SATA–D31:F2) ........................................ 546

14.1.8 BCC—Base Class Code Register (SATA–D31:F2SATA–D31:F2).................... 547

14.1.9 PMLT—Primary Master Latency Timer Register (SATA–D31:F2)................... 547

14.1.10HTYPE—Header Type (SATA–D31:F2) ..................................................... 547

14.1.11PCMD_BAR—Primary Command Block Base Address

14.1.12PCNL_BAR—Primary Control Block Base Address Register

(SATA–D31:F2).................................................................................... 548

18 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.13SCMD_BAR—Secondary Command Block Base Address

14.1.14SCNL_BAR—Secondary Control Block Base Address

14.1.15BAR — Legacy Bus Master Base Address Register

(SATA–D31:F2)....................................................................................549

14.1.16ABAR/SIDPBA1 — AHCI Base Address Register/Serial ATA Index

Data Pair Base Address (SATA–D31:F2)...................................................549

14.1.16.1When SCC is not 01h...............................................................549

14.1.16.2When SCC is 01h ....................................................................550

14.1.17SVID—Subsyste m Vendor Id e ntification Re g iste r (SAT A– D3 1 :F2)... .............550

14.1.18SID—Subsystem Identification Register (SATA–D31:F2).............................550

14.1.19CAP—Capabilities Pointer Register (SATA–D31:F2)....................................550

14.1.20INT_LN—Interrupt Line Register (SATA–D31:F2).......................................551

14.1.21INT_PN—Interrupt Pin Register (SATA–D31:F2)........................................551

14.1.22IDE_TIM — IDE Timing Register (SATA–D31:F2).......................................551

14.1.23PID—PCI Power Management Capability Identification

14.1.24PC—PCI Power Management Capabilities Register

(SATA–D31:F2)....................................................................................552

14.1.25PMCS—PCI Power Management Control and Status

14.1.26MSICI—Message Signaled Interrupt Capability Identification (SATA–D31:F2) 553

14.1.27MSIMC—Message Signaled Interrupt Message Control (SATA–D31:F2).........55 4

14.1.28MSIMA— Message Signaled Interrupt Message Address (SATA–D31:F2).......555

14.1.29MSIMD—Message Signaled Interrupt Message Data (SATA –D31:F2) ..... .......555

14.1.30MAP—Address Map Register (SATA–D31:F2).............................................556

14.1.31PCS—Port Control and Status Register (SATA–D31:F2)..............................556

14.1.32SCLKCG - SATA Clock Gating Control Register ..........................................559

14.1.33SCLKGC - SATA Clock General Configuration Register ................................560

14.1.33.1SATACR0—SATA Capability Register 0 (SATA–D31:F2).................561

14.1.33.2SATACR1—SATA Capability Register 1 (SATA–D31:F2).................561

14.1.34FLRCID—FLR Capability ID (SATA–D31:F2) ..............................................562

14.1.35FLRCLV—FLR Capability Length and Version (SATA–D31:F2).......................562

14.1.36FLRC—FLR Control (SATA–D31:F2) .........................................................563

14.1.37ATC—APM Trapp i ng Control Register (SATA–D31:F2).............. .. ............. ....563

14.1.38ATS—APM Trapp i ng Status Reg iste r (SAT A– D 31: F2 )..... .. .. .. ............. ..........564

14.1.39SP Scratch Pad Register (SATA–D31:F2)..................................................564

14.1.40BFCS—BIST FIS Control/Status Register (SATA–D31:F2) ...........................565

14.1.41BFTD1—BIST FIS Transmit Data1 Register (SATA–D31:F2) ........................567

14.1.42BFTD2—BIST FIS Transmit Data2 Register (SATA–D31:F2) ........................567

14.2 Bus Master IDE I/O Registers (D31:F2)...............................................................568

14.2.1 BMIC[P,S]—Bus Master IDE Command Register (D31:F2) ...... ............. .......569

14.2.2 BMIS[P,S]—Bus Master IDE Status Register (D31:F2)................................570

14.2.3 BMID[P,S]—Bus Master IDE Descriptor Table Pointer

14.2.4 AIR—AHCI Index Register (D31:F2) ........................................................571

14.2.5 AIDR—AHCI Index Data Register (D31:F2)...............................................571

14.3 Serial ATA Index/Data Pair Superset Registers.....................................................572

14.3.1 SINDX – Serial ATA Index (D31 :F2) .......... .. ....................... .....................572

14.3.2 SDATA – Serial ATA Data (D31:F2) .........................................................573

14.3.2.1 PxSSTS—Serial ATA Status Register (D31:F2).............................574

14.3.2.2 PxSCTL — Serial ATA Control Register (D31:F2)......... ............. .. ..575

14.3.2.3 PxSERR—Serial ATA Error Register (D31:F2)...............................576

14.4 AHCI Registers (D31:F2) ..................................................................................577

14.4.1 AHCI Generic Host Control Registers (D31:F2)..........................................578

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 19

14.4.1.1 CAP—Host Capabilities Register (D31:F2)................................... 578

14.4.1.2 GHC—Global ICH9 Control Register (D31 : F2)......... .. .. .. ... .. .. ........ 580

14.4.1.3 IS—Interrupt Status Register (D31:F2)...................................... 581

14.4.1.4 PI—Ports Implemented Register (D31:F2).................................. 582

14.4.1.5 VS—AHCI Version (D3 1:F2) ................... .................................. 583

14.4.1.6 CCC_CTL—Command Completion Coalescing Control

14.4.1.7 CCC_Ports—Command Completion Coalescing Ports

14.4.1.8 EM_LOC—Enclosure Management Location Register (D31:F2) ....... 584

14.4.1.9 EM_CTRL—Enclosure Management Control Register (D31:F2) ....... 585

14.4.2 Vendor Specific Registers (D31:F2)......................................................... 586

14.4.2.1 VSP—Vendor Specific (D31:F2)................................................. 586

14.4.3 Port Registers (D31:F2) ........................................................................ 586

14.4.3.1 PxCLB—Port [5:0] Command List Base Address Register

(D31:F2) ............................................................................... 589

14.4.3.2 PxCLBU—Port [5:0] Command List Base Address Upper

32-Bits Register (D31:F2)........ .. .. .. .......................................... 589

14.4.3.3 PxFB—Port [5:0] FIS Base Address Register (D31:F2).................. 590

14.4.3.4 PxFBU—Port [5:0] FIS Base Address Upper 32-Bits

14.4.3.5 PxIS—Port [5:0] Interrupt Status Register (D31:F2).................... 591

14.4.3.6 PxIE—Port [5:0] Interrupt Enable Register (D31:F2).................... 592

14.4.3.7 PxCMD—Port [5:0] Command Register (D31:F2)......................... 594

14.4.3.8 PxTFD—Port [5:0] Task File Data Register (D31:F2) .................... 597

14.4.3.9 PxSIG—Port [5:0] Signature Register (D31:F2)........................... 598

14.4.3.10PxSSTS—Port [5:0] Serial ATA Status Register (D31:F2).............. 599

14.4.3.11PxSCTL — Port [5:0] Serial ATA Control Register (D31:F2)........... 600

14.4.3.12PxSERR—Port [5:0] Serial ATA Error Register (D31:F2)................ 601

14.4.3.13PxSACT—Port [5:0] Serial ATA Active (D31:F2) .......................... 603

14.4.3.14PxCI—Port [5:0] Command Issue Register (D31:F2).................... 603

15 SATA Controller Registers (D31:F5)....................................................................... 605

15.1 PCI Configuration Registers (SATA–D31:F5) ........................................................ 605

15.1.1 VID—Vendor Identification Register (SATA—D31:F5) ................................ 606

15.1.2 DID—Device Identification Register (SATA—D31:F5)............... ............. ..... 607

15.1.3 PCICMD—PCI Command Register (SATA–D31:F5)..................................... 607

15.1.4 PCISTS — PCI Status Register (SATA–D31:F5)......................................... 608

15.1.5 RID—Revision Identification Register (SATA—D31:F5)............................... 608

15.1.6 PI—Programming Interface Register (SATA–D31:F5)................................. 609

15.1.7 SCC—Sub Class Code Register (SATA–D31:F5) ........................................ 609

15.1.8 BCC—Base Class Code Register (SATA–D31:F5) ....................................... 609

15.1.9 PMLT—Primary Master Latency Timer Register (SATA–D31:F5)................... 610

15.1.10PCMD_BAR—Primary Command Block Base Address

15.1.11PCNL_BAR—Primary Control Block Base Address Register

(SATA–D31:F5).................................................................................... 610

15.1.12SCMD_BAR—Secondary Command Block Base Address

15.1.13SCNL_BAR—Secondary Control Block Base Address

15.1.14BAR — Legacy Bus Master Base Address Register

(SATA–D31:F5).................................................................................... 612

15.1.15SIDPBA — SATA Index/Data Pair Base Address Register

(SATA–D31:F5).................................................................................... 612

15.1.16SVID—Subsystem Vendor Identification Register

(SATA–D31:F5).................................................................................... 613

15.1.17SID—Subsystem Identification Register (SATA–D31:F5)............................ 613

20 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

15.1.18CAP—Capabilities Pointer Register (SATA–D31:F5)....................................613

15.1.19INT_LN—Interrupt Line Register (SATA–D31:F5).......................................613

15.1.20INT_PN—Interrupt Pin Register (SATA–D31:F5)........................................613

15.1.21IDE_TIM — IDE Timing Register (SATA–D31:F5).......................................614

15.1.22PID—PCI Power Management Capability Identification

15.1.23PC—PCI Power Management Capabilities Register

(SATA–D31:F5)....................................................................................614

15.1.24PMCS—PCI Power Management Control and Status

15.1.25MID—Message Signal Interrupt Identifier (SATA–D31:F5) ..........................615

15.1.26MC—Message Signal Interrupt Message Control (SATA–D31:F5)..................616

15.1.27MA—Message Signal Interrupt Message Address (SATA–D31:F5).................616

15.1.28MD—Message Signal Interrupt Message Data (SATA–D31:F5).....................616

15.1.29MAP—Address Map Register (SATA–D31:F5)16.........................................617

15.1.30PCS—Port Control and Status Register (SATA–D31:F5)..............................618

15.1.31SATACR0— SATA Capability Register 0 (SATA–D31:F5) .............................619

15.1.32SATACR1— SATA Capability Register 1 (SATA–D31:F5) .............................619

15.1.33FLRCID— FLR Capability ID (SATA–D31:F5) .............................................619

15.1.34FLRCLV— FLR Capability Length and Value (SATA–D31:F5) ........................620

15.1.35FLRCTRL— FLR Control (SATA–D31:F5) ...................................................620

15.1.36ATC—APM Trapp i ng Control Register (SATA–D31:F5).............. .. ............. ....621

15.1.37ATC—APM Trap p i ng Control (SATA–D31 : F5)........... .. ... ..................... .. .. ....621

15.2 Bus Master IDE I/O Registers (D31:F5)...............................................................622

15.2.1 BMIC[P,S]—Bus Master IDE Command Register (D31:F5) ...... ............. .......623

15.2.2 BMIS[P,S]—Bus Master IDE Status Register (D31:F5)................................624

15.2.3 BMID[P,S]—Bus Master IDE Descriptor Table Pointer

15.3 AHCI Index Data Pair Registers..........................................................................625

15.3.1 INDEX—AHCI Index Register (D31:F5) ....................................................625

15.3.2 Data—AHCI Data Regi ster (D3 1 : F5)................ .. .. .. ..................................625

15.4 Serial ATA Index/Data Pair Superset Registers.....................................................626

15.4.1 SINDX—SATA Inde x Reg i ste r (D31 :F5).......... .. ....................... .................626

15.4.2 SDATA—SATA Index Data Register (D31:F5)............................................626

15.4.2.1 PxSSTS—Serial ATA Status Register (D31:F5).............................627

15.4.2.2 PxSCTL — Serial ATA Control Register (D31:F5)......... ............. .. ..628

15.4.2.3 PxSERR—Serial ATA Error Register (D31:F5)...............................629

16 UHCI Controllers Registers ....................................................................................631

16.1 PCI Configuratio n Registers

(USB—D29:F0/F1/F2/F3, D26:F0/F1/F2).............................................................631

16.1.1 VID—Vendor Identification Register

(USB—D29:F0/F1/F2/F3, D26:F0/F1/F2)..................................................632

16.1.2 DID—Device Identification Register

(USB—D29:F0/F1/F2/F3, D26:F0/F1/F2)..................................................632

16.1.3 PCICMD—PCI Command Register (USB—D29:F0/F1/F2/F3, D26:F0/F1/F2)...633

16.1.4 PCISTS—PCI Status Register

(USB—D29:F0/F1/F2/F3, D26:F0/F1/F2)..................................................634

16.1.5 RID—Revision Identification Register

(USB—D29:F0/F1/F2/F3, D26:F0/F1/F2)..................................................634

16.1.6 PI—Programming Interface Register

(USB—D29:F0/F1/F2/F3, D26:F0/F1/F2)..................................................635

16.1.7 SCC—Sub Class Code Register

(USB—D29:F0/F1/F2/F3, D26:F0/F1/F2)..................................................635

16.1.8 BCC—Base Class Code Register

(USB—D29:F0/F1/F2/F3, D26:F0/F1/F2)..................................................635

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 21

16.1.9 MLT—Master Latency Timer Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 635

16.1.10HEADTYP—Header Type Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 636

16.1.11BASE—Base Address Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 636

16.1.12SVID — Subsystem Vendor Identification Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 636

16.1.13SID — Subsystem Identification Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 637

16.1.14CAP_PTR—Capabilities Pointer

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 637

16.1.15INT_LN—Interrupt Line Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 637

16.1.16INT_PN—Interrupt Pin Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 638

16.1.17FLR CID—Function Le vel Reset Capability ID

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 638

16.1.18FLR NCP—Function Level Reset Next Capability Pointer

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 638

16.1.19FLR CLV—Function Level Reset Capability Le ngth and Version

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 639

16.1.20USB_FLRCTRL—FLR Control Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 639

16.1.21USB_FLRSTAT—FLR Status Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 640

16.1.22USB_RELNUM—Serial Bus Release Number Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 640

16.1.23USB_LEGKEY—USB Legacy Keyboard/Mouse Control

16.1.24USB_RES—USB Resume Enable Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 642

16.1.25CWP—Core Well Policy Register

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 643

16.1.26UCR1—UCHI Configuration Register 1

(USB—D29:F0/F1/F2 / F3 , D2 6:F0 /F1/ F2).................. .. .. .. .. ............. .. ........ 643

16.2 USB I/O Register s ............... .. ........... .. .. ........... .. .......... .. ... .......... .. .. ........... .. .. .. 644

16.2.1 USBCMD—US B Command Register ........... .. ................................ .. .. .. ...... 645

16.2.2 USBSTS—U SB Status Re g i ster ............... ..................... .. .. ..................... .. 648

16.2.3 USBINTR—USB Interrupt Enable Register ................................................ 649

16.2.4 FRNUM—Frame Number Register............................................................ 649

16.2.5 FRBASEADD—Frame List Base Address Register ....................................... 650

16.2.6 SOFMOD—Start of Frame Modi fy Register............ .. ... ............ ............. ...... 651

16.2.7 PORTSC[0,1]—Port Status and Control Register........................................ 652

17 EHCI Controller Registers (D29:F7, D26:F7) .......................................................... 655

17.1 USB EHCI Configuration Registers (USB EHCI—D29:F7, D26:F7) ........................... 655

17.1.1 VID —Vendor Identification Register

(USB EHCI—D29 :F7, D26:F7)......... .. ...................... .. .. ..................... .. .. .. 656

17.1.2 DID—Device Identification Register

(USB EHCI—D29 :F7, D26:F7)......... .. ...................... .. .. ..................... .. .. .. 656

17.1.3 PCICMD—PCI Command Register

(USB EHCI—D29 :F7, D26:F7)......... .. ...................... .. .. ..................... .. .. .. 657

17.1.4 PCISTS—PCI Status Register (USB EHCI—D2 9:F7, D26 :F7) ..................... .. 658

17.1.5 RID—Revision Identification Register

(USB EHCI—D29 :F7, D26:F7)......... .. ...................... .. .. ..................... .. .. .. 659

22 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

17.1.6 PI—Programming Interface Register

(USB EHCI—D29:F7, D26:F7).................................................................659

17.1.7 SCC—Sub Class Code Register

(USB EHCI—D29:F7, D26:F7).................................................................659

17.1.8 BCC—Base Class Code Register

(USB EHCI—D29:F7, D26:F7).................................................................659

17.1.9 PMLT—Primary Master Latency Timer Register

(USB EHCI—D29:F7, D26:F7).................................................................660

17.1.10MEM_BASE—Memory Base Address Register

(USB EHCI—D29:F7, D26:F7).................................................................660

17.1.11SVID—USB EHCI Subsystem Vendor ID Register

(USB EHCI—D29:F7, D26:F7).................................................................660

17.1.12SID—USB EHCI Subsystem ID Register

(USB EHCI—D29:F7, D26:F7).................................................................661

17.1.13CAP_PTR—Capabilities Pointer Register

(USB EHCI—D29:F7, D26:F7).................................................................661

17.1.14INT_LN—Interrupt Line Register

(USB EHCI—D29:F7, D26:F7).................................................................661

17.1.15INT_PN—Interrupt Pin Register

(USB EHCI—D29:F7, D26:F7).................................................................661

17.1.16PWR_CAPID—PCI Power Management Capability ID

17.1.17NXT_PTR1—Next Item Pointer #1 Register

(USB EHCI—D29:F7, D26:F7).................................................................662

17.1.18PWR_CAP—Power Management Capabilities Register

(USB EHCI—D29:F7, D26:F7).................................................................663

17.1.19PWR_CNTL_STS—Power Management Control/

Status Register (USB EHCI—D29:F7, D26:F7) ..........................................664

17.1.20DEBUG_CAPID—Debug Port Capability ID Register

(USB EHCI—D29:F7, D26:F7).................................................................665

17.1.21NXT_PTR2—Next Item Pointer #2 Register

(USB EHCI—D29:F7, D26:F7).................................................................665

17.1.22DEBUG_BASE—Debug Port Base Offset Register

(USB EHCI—D29:F7, D26:F7).................................................................665

17.1.23USB_RELNUM—USB Release Number Register

(USB EHCI—D29:F7, D26:F7).................................................................665

17.1.24FL_ADJ—Frame Length Adjustment Register

(USB EHCI—D29:F7, D26:F7).................................................................666

17.1.25PWAKE_CAP—Port Wake Capability Register

(USB EHCI—D29:F7, D26:F7).................................................................667

17.1.26LEG_EXT_CAP—USB EHCI Legacy Support Extended

Capability Register (USB EHCI—D29:F7, D26:F7)......................................668

17.1.27LEG_EXT_CS—USB EHCI Legacy Support Extended

Control / Status Register (USB EHCI —D29:F7, D26:F7 ) ................. ............668

17.1.28SPECIAL_SMI—Intel Specific USB 2.0 SMI Register

(USB EHCI—D29:F7, D26:F7).................................................................671

17.1.29ACCESS_CNTL—Access Control Register

(USB EHCI—D29:F7, D26:F7).................................................................673

17.1.30EHCIIR1—EHCI Initialization Register 1

(USB EHCI—D29:F7, D26:F7).................................................................673

17.1.31FLR_CID—F unction Level Reset Capability ID

(USB EHCI—D29:F7, D26:F7).................................................................673

17.1.32FLR_NEXT—Function Level Reset Next Capability Pointer

(USB EHCI—D29:F7, D26:F7).................................................................674

17.1.33FLR_CLV—Function Level Reset Capability Length and Version

(USB EHCI—D29:F7, D26:F7).................................................................674

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 23

17.1.34FLR_CTRL—Function Level Reset Control Register

(USB EHCI—D29 :F7, D26:F7)......... .. ...................... .. .. ..................... .. .. .. 675

17.1.35FLR_STS—Function Level Reset Status Register

(USB EHCI—D29 :F7, D26:F7)......... .. ...................... .. .. ..................... .. .. .. 675

17.1.36EHCIIR2—EHCI Initialization Register 2

(USB EHCI—D29 :F7, D26:F7)......... .. ...................... .. .. ..................... .. .. .. 675

17.2 Memory-Mapped I/O Registers.......................................................................... 676

17.2.1 Host Controller Capability Registers ........................................................ 676

17.2.1.1 CAPLENGTH—Capability Registers Length Register ...................... 677

17.2.1.2 HCIVERSION—Host Controller Interface Version Number

17.2.1.3 HCSPARAMS—Host Controller Structural Parameters.................... 678

17.2.1.4 HCCPARAMS—Host Controller Capability Parameters

17.2.2 Host Controller Operational Registers...................................................... 680

17.2.2.1 USB2.0_CMD—USB 2.0 Command Reg i ster .. ............ ............. ..... 681

17.2.2.2 USB2.0_STS—USB 2.0 Status Register ...................................... 684

17.2.2.3 USB2.0_INTR—USB 2.0 Interrupt Enable Register....................... 686

17.2.2.4 FRINDEX—Frame Index Register............................................... 687

17.2.2.5 CTRLDSSEGMENT—Control Data Structure Segment

17.2.2.6 PERIODICLISTBASE—Periodic Frame List Base Address

17.2.2.7 ASYNCLISTADDR—Current Asynchronous List Address

17.2.2.8 CONFIGFLAG—Configure Flag Register....................................... 689

17.2.2.9 PORTSC—Port N Status and Control Register .............................. 690

17.2.3 USB 2.0-Based Debug Port Register........................................................ 694

17.2.3.1 CNTL_STS—Control/Status Register .......................................... 695

17.2.3.2 USBPID—USB PIDs Register............... .. .. ... ..................... .. .. .. .... 697

17.2.3.3 DATABUF[7:0]—Data Buffer Bytes[7:0] Register......................... 697

17.2.3.4 CONFIG—Configuration Register ............................................... 697

18 Intel® High Definition Audio Controller Registers (D27:F0) ................................... 699

18.1 Intel® High Definition Audio PCI Configuration Space

(Intel® High Definition Audio— D27:F0) ............................................................. 699

18.1.1 VID —Vendor Identification Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 701

18.1.2 DID—Device Identification Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 701

18.1.3 PCICMD—PCI Command Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 701

18.1.4 PCISTS—PCI Status Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 702

18.1.5 RID—Revision Identification Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 703

18.1.6 PI—Prog ramming Interface Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 703

18.1.7 SCC—Sub Class Code Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 703

18.1.8 B CC—Base Class Code Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 703

18.1.9 CLS—Cache Line Size Reg ister

(Intel® High Definition Audio Controller—D27:F0)..................................... 703

18.1.10LT—Latency Timer Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 704

18.1.11HEADTYP—Header Type Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 704

24 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

18.1.12HDBARL—Intel® High Definition Audio Lower Base Address Register

(Intel® High Definition Audio—D27:F0)....................................................704

18.1.13HDBARU—Intel® High Definition Audio Upper Base Address Register

(Intel® High Definition Audio Controller—D27:F0).....................................704

18.1.14SVID—Subsystem Vendor Identification Register

(Intel® High Definition Audio Controller—D27:F0).....................................705

18.1.15SID—Subsystem Identification Register

(Intel® High Definition Audio Controller—D27:F0).....................................705

18.1.16CAPPTR—Capabilities Pointer Register (Audio—D27:F0) .............................705

18.1.17INTLN—Interrupt Line Register

(Intel® High Definition Audio Controller—D27:F0).....................................706

18.1.18INTPN—Interrupt Pin Register

(Intel® High Definition Audio Controller—D27:F0).....................................706

18.1.19HDCTL—Intel® High Definition Audio Control Register

(Intel® High Definition Audio Controller—D27:F0).....................................706

18.1.20TCSEL—Traffic Class Select Register

(Intel® High Definition Audio Controller—D27:F0).....................................707

18.1.21DCKCTL—Docking Control Register (Mobile Only)

(Intel® High Definition Audio Controller—D27:F0).....................................707

18.1.22DCKSTS—Docking Status Register (Mobile Only)

(Intel® High Definition Audio Controller—D27:F0).....................................708

18.1.23PID—PCI Power Management Capability ID Register

(Intel® High Definition Audio Controller—D27:F0).....................................708

18.1.24PC—Power Management Capabilities Register

(Intel® High Definition Audio Controller—D27:F0).....................................709

18.1.25PCS—Power Management Control and Status Register

(Intel® High Definition Audio Controller—D27:F0).....................................710

18.1.26MID—MSI Capability ID Register

(Intel® High Definition Audio Controller—D27:F0).....................................711

18.1.27MMC—MSI Message Control Register

(Intel® High Definition Audio Controller—D27:F0).....................................711

18.1.28MMLA—MSI Message Lower Address Register

(Intel® High Definition Audio Controller—D27:F0).....................................711

18.1.29MMUA—MSI Message Upper Address Register

(Intel® High Definition Audio Controller—D27:F0).....................................711

18.1.30MMD—MSI Message Data Register

(Intel® High Definition Audio Controller—D27:F0).....................................712

18.1.31PXID—PCI Express* Capability ID Register

(Intel® High Definition Audio Controller—D27:F0).....................................712

18.1.32PXC—PCI Express* Capabilities Register

(Intel® High Definition Audio Controller—D27:F0).....................................712

18.1.33DEVCAP—Device Capabilities Register

(Intel® High Definition Audio Controller—D27:F0).....................................713

18.1.34DEVC—Device Control Register

(Intel® High Definition Audio Controller—D27:F0).....................................714

18.1.35DEVS—Device Status Register

(Intel® High Definition Audio Controller—D27:F0).....................................715

18.1.36VCCAP—Virtual Channel Enhanced Capability Header

(Intel® High Definition Audio Controller—D27:F0).....................................715

18.1.37PVCCAP1—Port VC Capability Register 1

(Intel® High Definition Audio Controller—D27:F0).....................................716

18.1.38PVCCAP2 — Port VC Capability Register 2

(Intel® High Definition Audio Controller—D27:F0).....................................716

18.1.39PVCCTL — Port VC Control Register

(Intel® High Definition Audio Controller—D27:F0).....................................716

18.1.40PVCSTS—Port VC Status Register

(Intel® High Definition Audio Controller—D27:F0).....................................717

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 25

18.1.41VC0CAP—VC0 Resource Capability Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 717

18.1.42VC0CTL—VC0 Resource Control Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 718

18.1.43VC0STS—VC0 Resource Status Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 718

18.1.44VCiCAP—VCi Resource Capability Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 719

18.1.45VCiCTL—VCi Resource Control Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 719

18.1.46VCiSTS—VCi Resource Status Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 720

18.1.47RCCAP—Root Complex Link Declaration Enhanced

Capability Header Register (Intel® High Definition Audio Controller—D27:F0)720

18.1.48ESD—Element Self Description Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 720

18.1.49L1DESC—Link 1 Description Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 721

18.1.50L1ADDL—Link 1 Lower Address Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 721

18.1.51L1ADDU—Link 1 Upper Address Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 721

18.2 Intel® High Definition Audio Memory Mapped Configuration Registers

(Intel® High Definition Audio— D27:F0) ............................................................. 722

18.2.1 GCAP—Global Capabilities Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 726

18.2.2 VMIN—Minor Version Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 726

18.2.3 VMAJ—Major Version Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 726

18.2.4 OUTPAY—Output Payload Capability Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 727

18.2.5 INPAY—Input Payload Capability Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 727

18.2.6 GCTL—Global Control Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 728

18.2.7 WAKEEN—Wake Enable Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 729

18.2.8 STATESTS—State Change Status Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 729

18.2.9 GSTS—Global Status Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 730

18.2.10ECAP—Extende d Capabilities (Mobile Only)

(Intel® High Definition Audio Controller—D27:F0)..................................... 731

18.2.11OUTSTRMPAY—Output Stream Payload Capability

(Intel® High Definition Audio Controller—D27:F0)..................................... 731

18.2.12INSTRMPAY—Input Stream Payload Capability

(Intel® High Definition Audio Controller—D27:F0)..................................... 732

18.2.13INTCTL—Interrupt Control Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 733

18.2.14INTSTS—Interrupt Status Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 734

18.2.15WALCLK—Wall Clock Counter Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 734

18.2.16SSYNC—Stream Synchronization Register

(Intel® High Definition Audio Controller—D27:F0)..................................... 735

26 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

18.2.17CORBLBASE— CORB Lower Base Address Register

(Intel® High Definition Audio Controller—D27:F0).....................................735

18.2.18CORBUBASE—CORB Upper Base Address Register

(Intel® High Definition Audio Controller—D27:F0).....................................736

18.2.19CORBWP—CORB Write Pointer Reg i st er

(Intel® High Definition Audio Controller—D27:F0).....................................736

18.2.20CORBRP—CORB Read Pointer Register

(Intel® High Definition Audio Controller—D27:F0).....................................736

18.2.21CORBCTL—CORB Control Register

(Intel® High Definition Audio Controller—D27:F0).....................................737

18.2.22CORBST—CORB Status Register

(Intel® High Definition Audio Controller—D27:F0).....................................737

18.2.23CORBSIZE—CORB Size Register

Intel® High Definition Audio Controller—D27:F0) ......................................737

18.2.24RIRBLBASE—RIRB Lower Base Address Register

(Intel® High Definition Audio Controller—D27:F0).....................................738

18.2.25RIRBUBASE—RIRB Upper Base Address Register

(Intel® High Definition Audio Controller—D27:F0).....................................738

18.2.26RIRBWP—RIRB Write Pointer Register

(Intel® High Definition Audio Controller—D27:F0).....................................738

18.2.27RINTCNT—Response Interrupt Count Register

(Intel® High Definition Audio Controller—D27:F0).....................................739

18.2.28RIRBCTL—RIRB Control Register

(Intel® High Definition Audio Controller—D27:F0).....................................739

18.2.29RIRBSTS—RIRB Status Register

(Intel® High Definition Audio Controller—D27:F0).....................................740

18.2.30RIRBSIZE—RIRB Size Register

(Intel® High Definition Audio Controller—D27:F0).....................................740

18.2.31IC—Immediate Command Register

(Intel® High Definition Audio Controller—D27:F0).....................................740

18.2.32IR—Immediate Response Register

(Intel® High Definition Audio Controller—D27:F0).....................................741

18.2.33IRS—Immediate Command Status Register

(Intel® High Definition Audio Controller—D27:F0).....................................741

18.2.34DPLBASE—DMA Position Lower Base Address Register

(Intel® High Definition Audio Controller—D27:F0).....................................742

18.2.35DPUBASE—DMA Position Upper Base Address Register

(Intel® High Definition Audio Controller—D27:F0).....................................742

18.2.36SDCTL—Stream Descriptor Control Register

(Intel® High Definition Audio Controller—D27:F0).....................................743

18.2.37SDSTS—Stream Descriptor Status Register

(Intel® High Definition Audio Controller—D27:F0).....................................745

18.2.38SDLPIB—Stream Descriptor Link Position in Buffer

18.2.39SDCBL—Stream Descriptor Cyclic Buffer Length Register

(Intel® High Definition Audio Controller—D27:F0).....................................746

18.2.40SDLVI—Stream Descriptor Last Valid Index Register

(Intel® High Definition Audio Controller—D27:F0).....................................747

18.2.41SDFIFOW—Stream Descriptor FIFO Watermark Register

(Intel® High Definition Audio Controller—D27:F0).....................................747

18.2.42SDFIFOS—Stream Descriptor FIFO Size Register

(Intel® High Definition Audio Controller—D27:F0).....................................748

18.2.43SDF MT—Stream Descriptor Format Register

(Intel® High Definition Audio Controller—D27:F0).....................................749

18.2.44SDBDPL—Stream Descriptor Buffer Descriptor List Pointer Lower Base

Address Register (Intel® High Definition Audio Controller—D27:F0).............750

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 27

18.2.45SDBDPU—Stream Descriptor Buffer Descriptor List Pointer Upper Base

Address Register (Intel® High Definition Audio Controller—D27:F0) ............ 750

19 SMBus Controller Registers (D31:F3) .................................................................... 751

19.1 PCI Configuration Registers (SMBus—D31:F3)..................................................... 751

19.1.1 VID—Vendor Identification Register (SMBus—D31:F3)...................... ......... 751

19.1.2 DID—Device Identification Register (SM Bus—D 31:F3)............................... 752

19.1.3 PCICMD—PCI Command Register (SMBus—D31:F3).................................. 752

19.1.4 PCISTS—PCI Status Register (SMBus—D31:F3)........................................ 753

19.1.5 RID —Revision Identification Register (SMBus—D31:F3)............................. 753

19.1.6 PI—Programming Interface Register (SMBus—D31:F3).............................. 754

19.1.7 SCC—Sub Class Code Register (SMBus—D31:F3)...................................... 754

19.1.8 BCC—Base Class Code Register (SMBus—D31:F3) .................................... 754

19.1.9 SMBMBAR0—D31_F3_SMBus Memory Base Address 0 (SMBus—D31:F3) ..... 754

19.1.10SMBMBAR1—D31_F3_SMBus Memory Base Address 1 (SMBus—D31:F3) .... . 755

19.1.11SMB_BASE—SMBus Base Address Register (SMBus—D31:F3)..................... 755

19.1.12SVID—Subsystem Vendor Identification Register (SMBus—D31:F2/F4)........ 755

19.1.13SID—Subsystem Identification Register (SMBus—D31:F2/F4)..................... 756

19.1.14INT_LN—Interrupt Line Register (SMBus—D31:F3) ................................... 756

19.1.15INT_PN—Interrupt Pin Register (SMBus—D31:F3)..................................... 756

19.1.16HOSTC—Host Configuration Register (SMBus—D31:F3) ............................. 757

19.2 SMBus I/O and Memory Mapped I/O Registers .................................................... 758

19.2.1 HST_STS—Host Status Register (SMBus—D31:F3).................................... 759

19.2.2 HST_CNT—Ho st Contro l Reg iste r (SMBu s —D3 1 :F3) ................. .. ... .. .......... 760

19.2.3 HST_CMD—Host Command Register (SMBus—D31:F3)................. ............. 762

19.2.4 XMIT_SLVA—Transmit Slave Address Register (SMBus—D31:F3)................ 762

19.2.5 HST_D0—H o st Data 0 Reg ister (SMBus—D31:F3 )..................................... 762

19.2.6 HST_D1—H o st Data 1 Reg ister (SMBus—D31:F3 )..................................... 762

19.2.7 Host_BLOCK_DB—Host Block Data Byte Register (SMBus—D31:F3) ............ 763

19.2.8 PEC—Packet Error Check (PEC) Register (SMBus—D31:F3) ........................ 763

19.2.9 RCV_SLVA—Receive Slave Address Register (SMBus—D31:F3)................... 764

19.2.10SLV_DATA—Receive Slave Data Register (SMBus—D31:F3) ....................... 764

19.2.11AUX_STS—Auxiliary Status Register (SMBus—D31:F3).............................. 764

19.2.12AUX_CTL—Auxiliary Control Register (SMBus—D31:F3)............................. 765

19.2.13SMLINK_PIN_CTL—SMLink Pin Control Register (SMBus—D31:F3) .............. 765

19.2.14SMBus_PIN_CTL—SM Bus Pin Control Reg iste r (SMBu s —D3 1 :F3).. ... .. .. .. ...... 766

19.2.15SLV_STS—Slave Status Register (SMBus—D31:F3)................................... 766

19.2.16SLV_CMD—Slave Command Register (SMBus—D31:F3)............................. 767

19.2.17NOTIFY_DADDR—Notify Device Address Register (SMBus—D31:F3) ............ 767

19.2.18NOTIFY_DLOW—Notify Data Low Byte Register (SMBus—D31:F3)............... 768

19.2.19NOTIFY_DHIGH—Notify Data High Byte Re g i ster (SM Bus—D31:F3)............. 768

20 PCI Express* Configuration Registers.................................................................... 769

20.1 PCI Express* Configuration Registers (PCI Express—D28: F0/F1/F2/F3/F4/F5) .... ..... 769

20.1.1 VID —Vendor Identification Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 772

20.1.2 DID—Device Identification Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 772

20.1.3 PCICMD—PCI Command Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 773

20.1.4 PCISTS—PCI Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 774

20.1.5 RID—Revision Identification Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 775

20.1.6 PI—Prog ramming Interface Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 775

28 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

20.1.7 SCC—Sub Class Code Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................775

20.1.8 BCC—Base Class Code Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................775

20.1.9 CLS—Cache Line Size Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................776

20.1.10PLT—Primary Latency Timer Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................776

20.1.11HEADTYP —He ader Type Regis ter

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................776

20.1.12BNUM—Bus Number Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................776

20.1.13SLT—Secondary Latency Timer

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................777

20.1.14IOBL—I/O Base and Limit Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................777

20.1.15SSTS—Secondary Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................778

20.1.16MBL—Memory Base and Limit Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................779

20.1.17PMBL—Prefetchable Memory Base and Limit Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................779

20.1.18PMBU32—Prefetchable Memory Base Upper 32 Bits

20.1.19PMLU32—Prefetchable Memory Limit Upper 32 Bits

20.1.20CAPP—Capabilities List Pointer Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................780

20.1.21INTR—Interrupt Information Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................780

20.1.22BCTRL—Bridge Control Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................781

20.1.23CLIST—Capabilities List Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................782

20.1.24XCAP—PCI Express* Capabilities Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................782

20.1.25DCAP—Device Capabilities Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................783

20.1.26DCTL—Device Control Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................784

20.1.27DSTS—Device Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................785

20.1.28LCAP—Link Capabilities Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................786

20.1.29LCTL—Link Control Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................788

20.1.30LSTS—Link Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................789

20.1.31SLCAP—Slot Capabilities Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................790

20.1.32SLCTL—Slot Control Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................791

20.1.33SLSTS—Slot Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................792

20.1.34RCTL—Root Control Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................793

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 29

20.1.35RSTS—Root Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 793

20.1.36MID—Message Signaled Interrupt Identifiers Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 794

20.1.37MC—Message Signaled Interrupt Message Control Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 794

20.1.38MA—Message Signaled Interrupt Message Address

20.1.39MD—Message Signaled Interrupt Message Data Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 795

20.1.40SVCAP—Subsyste m Vendor Capa bility Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 795

20.1.41SVID—Subsystem Vendor Identification Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 795

20.1.42PMCAP—Powe r Management Capability Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 795

20.1.43PMC—PCI Powe r Management Capabilities Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 796

20.1.44PMCS—PCI Power Management Control and Status

20.1.45MPC2—Miscellaneous Port Configuration Register 2

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 798

20.1.46MPC—Miscellaneous Port Configuration Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 798

20.1.47SMSCS—SMI/SCI Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 801

20.1.48RPDCGEN—Root Port Dynamic Clock Gating Enable

(PCI Express-D28:F0/F1/F2/F3/F4/F5).................................................... 802

20.1.49IPWS—Intel® PRO/Wireless 3945ABG Status

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 802

20.1.50PECR1—PCI Express* Configuration Register 1

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 803

20.1.51VCH—Virtual Channel Capability Header Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 803

20.1.52VCAP2—Virtual Channel Capability 2 Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 803

20.1.53PVC—Port Virtual Channel Control Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 804

20.1.54PVS—Port Virtual Channel Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 804

20.1.55V0CAP—Virtual Channel 0 Resource Capability Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 804

20.1.56V0CTL—Virtual Channel 0 Resource Control Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 805

20.1.57V0STS—Virtual Channel 0 Resource Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 805

20.1.58UES—Uncorrectable Error Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 806

20.1.59UEM—Uncorrectable Error Mask

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 807

20.1.60UEV — Uncorrectable Error Severity

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 808

20.1.61CES — Correctable Error Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 809

20.1.62CEM — Correctable Error Mask Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)................................................... 809

30 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

20.1.63AECC — Advanced Error Capabilities and Control Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................810

20.1.64RES — Root Error Status Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................810

20.1.65RCTCL — Root Complex Topology Capability List Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................810

20.1.66ESD—Element Self Description Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................811

20.1.67ULD — Upstream Link Description Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................811

20.1.68ULBA — Upstream Link Base Address Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................812

20.1.69PECR2 — PCI Express* Configuration Register 2

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................812

20.1.70PEETM — PCI Express* Extended Test Mode Register

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................812

20.1.71PEC1 — PCI Express* Configuration Register 1

(PCI Express—D28:F0/F1/F2/F3/F4/F5)...................................................813

21 High Precision Event Timer Registers.....................................................................815

21.1 Memory Mapped Registers ................................................................................815

21.1.1 GCAP_ID—General Capabilities and Identification Register .........................816

21.1.2 GEN_CONF—Gener a l Conf iguration Register....... .. .. .. ... .. ............ .. ... ..........817

21.1.3 GINTR_STA—General Interrupt Status Register.........................................817

21.1.4 MAIN_CNT— Main Counter Value Register....... .. .. .. .. .. ... .. .. ............ ... ..........818

21.1.5 TIMn_CONF—Timer n Configuration and Capabilities Register .....................818

21.1.6 TIMn_COMP—Timer n Comparator Value Register .....................................820

22 Serial Peripheral Interface ( SPI) ...........................................................................821

22.1 Serial Peripheral Interface Memory Mapped Configuration Registers.............. .. .. ......821

22.1.1 BFPR –BIOS Flash Primary Region Register

(SPI Memory Mapped Configuration Registers)..........................................822

22.1.2 HSFS—Hardware Sequencing Flash Status Register

(SPI Memory Mapped Configuration Registers)..........................................823

22.1.3 HSFC—Hardware Sequencing Flash Control Register

(SPI Memory Mapped Configuration Registers)..........................................824

22.1.4 FADDR—Flash Address Register

(SPI Memory Mapped Configuration Registers)..........................................825

22.1.5 FDATA0—Flash Data 0 Register

(SPI Memory Mapped Configuration Registers)..........................................825

22.1.6 FDATAN—Flash Data [N] Register

(SPI Memory Mapped Configuration Registers)..........................................826

22.1.7 FRAP—Flash Regions Access Permissions Register

(SPI Memory Mapped Configuration Registers)..........................................827

22.1.8 FREG0—Flash Region 0 (Flash Descriptor) Register

(SPI Memory Mapped Configuration Registers)..........................................828

22.1.9 FREG1—Flash Region 1 (BIOS Descriptor) Register

(SPI Memory Mapped Configuration Registers)..........................................828

22.1.10FREG2—Flash Region 2 (ME) Register

(SPI Memory Mapped Configuration Registers)..........................................829

22.1.11FREG3—Flash Region 3 (GbE) Register

(SPI Memory Mapped Configuration Registers)..........................................829

22.1.12FREG4—Flash Region 4 (Platform Data) Register

(SPI Memory Mapped Configuration Registers)..........................................830

22.1.13PR0—Protected Range 0 Register

(SPI Memory Mapped Configuration Registers)..........................................830

22.1.14PR1—Protected Range 1 Register

(SPI Memory Mapped Configuration Registers)..........................................831

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 31

22.1.15PR2—Protected Range 2 Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 832

22.1.16PR3—Protected Range 3 Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 833

22.1.17PR4—Protected Range 4 Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 834

22.1.18SSFS—Software Sequencing Flash Status Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 835

22.1.19SSFC—Software Sequencing Flash Control Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 836

22.1.20PREOP—Prefix Opcode Configuration Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 837

22.1.21OPTYPE—Opcode Type Configuration Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 837

22.1.22OPMENU—Opcode Menu Configuration Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 838

22.1.23BBAR—BIOS Base Address Configuration Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 839

22.1.24FDOC—Flash Descriptor Observability Control Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 839

22.1.25FDOD—Flash Descriptor Observability Data Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 840

22.1.26AFC—Additional Flash Control Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 840

22.1.27LVSCC— Host Lower Vendor Specific Component Capabilities Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 841

22.1.28UVSCC— Host Upper Vendor Specific Component Capabilities Register

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 842

22.1.29FPB — Flash Partition Boundary

(SPI Memory Mapped Conf iguration Registers).............. ............ ... .. .. .. ...... 844

22.2 Flash Descriptor Registers ................................................................................ 845

22.2.1 Flash Descriptor Content ....................................................................... 845

22.2.1.1 FLVALSIG - Flash Valid Signature Register

(Flash Descriptor Registers) ..................................................... 845

22.2.1.2 FLMAP0 - Flash Map 0 Register (Flash Descriptor Registers).......... 845

22.2.1.3 FLMAP1—Flash Map 1 Register (Flash Descriptor Registers) .......... 846

22.2.1.4 FLMAP2—Flash Map 2 Register (Flash Descriptor Registers) .......... 846

22.2.2 Flash Descriptor Component Section....................................................... 847

22.2.2.1 FLCOMP—Flash Components Register

(Flash Descriptor Registers) ..................................................... 847

22.2.2.2 FLILL—Flash Invalid Instructions Register

(Flash Descriptor Registers) ..................................................... 849

22.2.2.3 FLPB—Flash Partition Boundary Register

(Flash Descriptor Registers) ..................................................... 849

22.2.3 Flash Descriptor Region Section ............................................................. 850

22.2.3.1 FLREG0—Flash Region 0 Register (Flash Descriptor Registers) ...... 850

22.2.3.2 FLREG1—Flash Region 1 (BIOS) Register

(Flash Descriptor Registers) ..................................................... 850

22.2.3.3 FLREG2—Flash Region 2 (ME) Register

(Flash Descriptor Registers) ..................................................... 851

22.2.3.4 FLREG3—Flash Region 3 (GbE) Register

(Flash Descriptor Registers) ..................................................... 851

22.2.3.5 FLREG4—Flash Region 4 (Platform Data) Register

(Flash Descriptor Registers) ..................................................... 851

22.2.4 Flash Descriptor Master Section.............................................................. 852

22.2.4.1 FLMSTR1—Flash Master 1 (Host CPU/ BIOS)

(Flash Descriptor Registers) ..................................................... 852

22.2.4.2 FLMSTR2—Flash Master 2 (ME) (Flash Descriptor Registers) ......... 853

32 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

22.2.4.3 FLMSTR3—Flash Master 3 (GbE) (Flash Descriptor Registers) ........854

22.2.5 Descriptor Upper Map Section.................................................................855

22.2.5.1 FLUMAP1—Flash Upper Map 1 (Flash Descriptor Registers)............855

22.2.6 ME Vendor Spe cific Component Capabilities Table .....................................856

22.2.6.1 JID0—JEDEC-ID 0 Register (Flash Descriptor Registers) ...............856

22.2.6.2 VSCC0—Vendor Specific Component Capabilities 0

(Flash Descriptor Registers)......................................................856

22.2.6.3 JIDn—JEDEC-ID Register n (Flash Descriptor Registers)................858

22.2.6.4 VSCCn—Vendor Specific Component Capabilities n

(Flash Descriptor Registers)......................................................858

22.3 OEM Section ...................................................................................................860

22.4 GbE SPI Flash Program Registers.......................................................................860

22.4.1 GLFPR –Gigabit LAN Flash Primary Region Register

(GbE LAN Memory Mapped Configuration Registers) ..................................861

22.4.2 HSFS—Hardware Sequencing Flash Status Register

(GbE LAN Memory Mapped Configuration Registers) ..................................862

22.4.3 HSFC—Hardware Sequencing Flash Control Register

(GbE LAN Memory Mapped Configuration Registers) ..................................863

22.4.4 FADDR—Flash Address Register

(GbE LAN Memory Mapped Configuration Registers) ..................................863

22.4.5 FDATA0—Flash Data 0 Register

(GbE LAN Memory Mapped Configuration Registers) ..................................864

22.4.6 FRAP—Flash Regions Access Permissions Register

(GbE LAN Memory Mapped Configuration Registers) ..................................865

22.4.7 FREG0—Flash Region 0 (Flash Descriptor) Register

(GbE LAN Memory Mapped Configuration Registers) ..................................866

22.4.8 FREG1—Flash Region 1 (BIOS Descriptor) Register

(GbE LAN Memory Mapped Configuration Registers) ..................................866

22.4.9 FREG2—Flash Region 2 (ME) Register

(GbE LAN Memory Mapped Configuration Registers) ..................................866

22.4.10FREG3—Flash Region 3 (GbE) Register

(GbE LAN Memory Mapped Configuration Registers) ..................................867

22.4.11PR0—Protected Range 0 Register

(GbE LAN Memory Mapped Configuration Registers) ..................................867

22.4.12PR1—Protected Range 1 Register

(GbE LAN Memory Mapped Configuration Registers) ..................................868

22.4.13SSFS—Software Sequencing Flash Status Register

(GbE LAN Memory Mapped Configuration Registers) ..................................869

22.4.14SSFC—Software Sequencing Flash Control Register

(GbE LAN Memory Mapped Configuration Registers) ..................................870

22.4.15PREOP—Prefix Opcode Configuration Register

(GbE LAN Memory Mapped Configuration Registers) ..................................871

22.4.16OPTYPE—Opcode Type Configuration Register

(GbE LAN Memory Mapped Configuration Registers) ..................................871

22.4.17OPMENU—Opcode Menu Configuration Register

(GbE LAN Memory Mapped Configuration Registers) ..................................872

23 Thermal Senso r Registers (D31:F6) .......................................................................873

23.1 PCI Bus Configuration Registers.........................................................................873

23.1.1 VID—Vendor Identification.....................................................................874

23.1.2 DID—Device Identification .....................................................................874

23.1.3 CMD—Command...................................................................................874

23.1.4 STS—Status.........................................................................................875

23.1.5 RID—Revision Identification ...................................................................875

23.1.6 PI— Programming Interface ............................. ....................... ...............875

23.1.7 SCC—Sub Class Cod e......... .. .. .......... .. ... .. .......... .. .. ...................... .. .. .. ....876

23.1.8 BCC—Base Class Code...........................................................................876

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 33

23.1.9 CLS—Cache Line Size............................................................................ 876

23.1.10LT—Latency Tim er.... .. ... .......... .. .. ........... .. .. .. ........... .. .. .......... ... .. .......... 876

23.1.11HTYPE—Header Type ............................................................................ 876

23.1.12BIST—Built-in Self Test......................................................................... 877

23.1.13TBAR—Thermal Base ............................................................................ 877

23.1.14TBARH—Thermal Base High DWord......................................................... 877

23.1.15SVID—Subsyste m Ve nd or ID .......................................... .. .. .. ........... .. .. .. 878

23.1.16SID—Subsystem ID.............................................................................. 878

23.1.17CAP_PTR —Capabilities Pointer............................................................... 878

23.1.18INTLN—Interrupt Line........................................................................... 878

23.1.19INTPN—Interrupt Pin ............... ........... .. .. .. ..................... .. .. .. ........... .. .. .. 879

23.1.20TBARB—BIOS Assigned Thermal Base Address ......................................... 879

23.1.21TBARBH—BIOS Assigned Thermal Base High DWord ................................. 879

23.1.22PID—PCI Power Management Capability ID.............................................. 880

23.1.23PC—Power Management Capabilities....................................................... 880

23.1.24PCS—Power Management Control And Status........................................... 881

23.2 Thermal Memory Mapped Configuration Registers (Thermal Sensor - D31:F26)........ 882

23.2.1 TSxE—Thermal Sensor [1:0] Enable ....................................................... 882

23.2.2 TSxS—Thermal Se nsor[1 :0 ] Status............... .. .. .. ............. ............. .......... 883

23.2.3 TSxTTP—Thermal Sensor [1:0] Catastrophic Trip Point.............................. 883

23.2.4 TSxCO—Thermal Sensor [1:0] Catastrophic Lock-Down............................. 883

23.2.5 TSxPC—Thermal Sensor [1:0] Policy Control............................................ 884

23.2.6 TSxLOCK—Thermal Sensor [1:0] Register Lock Control ............................. 884

34 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Figures

2-1 Intel® ICH9 Interface Signals Block Diagram (Desktop)................................................. 56

2-2 Intel® ICH9 Interface Signals Block Diagram (Mobile) ...................................................57

2-3 Example External RTC Circuit................ ....................... ....................... .......................90

4-1 Desktop Conceptual System Clock Diagram................................................................108

4-2 Mobile Conceptual Clock Diagram .............................................................................108

5-1 Generation of SERR# to Platform..............................................................................115

5-2 LPC Interface Diagram ............................................................................................123

5-3 Intel® ICH9 DMA Controller .....................................................................................128

5-4 DMA Request Assertion through LDRQ#.....................................................................132

5-5 Coprocessor Error Timing Diagram. ...........................................................................157

5-6 TCO Legacy/Compatible Mode SMBus Configuration ....................................................188

5-7 Advanced TCO Intel® AMT Mode SMBus/SMLink Configuration......................................189

5-8 Advanced TCO BMC Mode SMBus/SMLink Configuration ...............................................190

5-9 Serial Post over GPIO Refere nce Circuit .....................................................................191

5-10SATA Power States.................................................................................................198

5-11Flow for Port Enable / Device Present Bits..................................................................200

5-12Serial Data transmitted over the SGPIO Interface .......................................................205

5-13USB Legacy Keyboard Flow Diagram .........................................................................214

5-14 Intel® ICH9-USB Port Connections Default Six and Six Configuration............................222

5-15 Intel® ICH9-USB Port Connections Eight and Four Configuration..................................222

5-16Flash Partition Boundary..........................................................................................251

5-17Flash Descriptor Sections....... .. .. .. ............. .. ............. ............ ............. ............. ..........252

6-1 Intel® ICH9 Ballout (Top view–Left Side) (Desktop Only).............................................264

6-2 Intel® ICH9 Ballout (Top view–Right Side) (Desktop Only)...........................................265

6-3 Intel® ICH9M and ICH9M-E Ballout (Top View–Left Side) (Mobile Only)..........................273

6-4 Intel® ICH9M and ICH9M-E Ballout (Top View–Right Side) (Mobile Only)........................274

6-5 Intel® ICH9M SFF Preliminary Ballout(Top view–Left Side)...........................................282

6-6 Intel® ICH9M-SFF Preliminary Ballout(Top view–Right Side).........................................283

7-1 Intel® ICH9 Package (Top View)...............................................................................289

7-2 Intel® ICH9 Package (Bottom View)..........................................................................290

7-3 Intel® ICH9 Package (Side View)..............................................................................290

7-4 Intel® ICH9M Package (Top View) ............................................................................291

7-5 Intel® ICH9M Package (Bottom View) .......................................................................292

7-6 Intel® ICH9M Package (Side View) ...........................................................................292

7-7 Intel® ICH9M-SSF Package Drawing .........................................................................293

8-1 Clock Timing..........................................................................................................321

8-2 Valid Delay from Rising Clock Edge...........................................................................321

8-3 Setup and Hold Times............. .. .. ........... .. .. .......... ... .. .......... .. .. ... .......... .. .. ........... .. ..321

8-4 Float Delay............................................................................................................322

8-5 Pulse Width ...........................................................................................................322

8-6 Output Enable Delay............. ..................... .. .. ..................... .. .. ...................... .. .. ......322

8-7 USB Rise and Fall Times..........................................................................................322

8-8 USB Jitter............. .. ........... .. .......... ... .. .......... .. .. ........... .. .. ........... .. .......... .. ... ..........323

8-9 USB EOP Width .............. .. .......... .. .. ..................... ... .. .......... .. .. ........... .. .. ........... .. .. ..323

8-10SMBus Transaction .................................................................................................323

8-11SMBus Timeout......................................................................................................324

8-12SPI Timings...........................................................................................................324

8-13Intel® High Definition Audio Input and Output Timings................................................325

8-14Power Se q uencing and Reset Signal Timings ................ ............ ........................ ..........325

8-15G3 (Mechanical Off) to S0 Timings............................................................................326

8-16S0 to S1 to S0 Timing.............................................................................................327

8-17S0 to S5 to S0 Timings (Desktop Only) .....................................................................327

8-18S0 to S5 to S0 Timings (Mobile Only)........................................................................328

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 35

8-19C0 to C2 to C0 Timings (Mobile Only) ....................................................................... 328

8-20C0 to C3 to C0 Timings (Mobile Only) ....................................................................... 329

8-21C0 to C4 to C0 Timings (Mobile Only) ....................................................................... 329

8-22C0 to C5/C6 to C0 Timings (Mobile Only) .................................................................. 330

8-23Sleep control signal relationship - Host boots and Management Engine off..................... 330

8-24Sleep control signal relationship - Host and Management Engine boot after G3............... 331

8-25Sleep control signal relationship - Host stays in S5 and Management

Engine boots after G3............................................................................................. 331

8-26S4, S5/M1 to S0/M0............................................................................................... 332

8-27S0 to G3 Timings (Desktop Only)............................................................................. 332

8-28S0 to G3 Timings (Mobile Only)................................................................................ 332

Tables

1-1 Industry Specifications..............................................................................................43

1-2 Intel Specification ....................................................................................................44

1-3 PCI Devices and Functions..... ................................ .. .. .. ..................... .. .. .. ...................47

1-4 Intel® ICH9 Desktop/Server Family............................................................................54

1-5 Intel® ICH9 Mobile Family.........................................................................................54

2-1 Direct Media Interface Signals ..... .. ... .........................................................................58

2-2 PCI Express* Signals................................................................................................59

2-3 LAN Connect Interface Signals...................................................................................59

2-4 Gigabit LAN Connect Interface Signals ........................................................................60

2-5 Firmware Hub Interface Signals .................................................................................61

2-6 PCI Interface Signals................................................................................................62

2-7 Serial ATA Interface Signals ......................................................................................64

2-8 LPC Interface Signals................................................................................................67

2-9 Interrupt Signals......................................................................................................68

2-10USB Interface Signals...............................................................................................69

2-11Power Management Interface Signals .........................................................................71

2-12Processor Interface Signals .......................................................................................74

2-13SM Bus Interface Signals ..........................................................................................75

2-14System Managem ent Inte rface Sign als. .. .. .. .. .. .... .........................................................76

2-15Real Time Clock Interface .........................................................................................78

2-16Other Clocks ...........................................................................................................78

2-17Miscellaneous Sig n als........................................... .. .. .. ..................... .. .. .. ........... .. .. .. ..78

2-18Intel® High Definition Audio Link Signals ....................................................................80

2-19Serial Peripheral Interface (SPI) Signals......................................................................81

2-20Controller Link Si gnals........ .. .. .......................................... .. .. ... ..................... .. .. .. ......82

2-21Intel® Quiet System Technology Signals.....................................................................83

2-22General Purpose I/O Signals......................................................................................83

2-23Power and Ground Signals.........................................................................................86

2-24Functional Strap Definitions.......................................................................................88

3-1 Integrated Pull-Up and Pull-Do wn Resistors ....... ..........................................................91

3-2 Power Plane and States for Output and I/O Signals for Desktop Configurations.................93

3-3 Power Plane and States for Output and I/O Signals for Mobile Configurations ...................97

3-4 Power Plane for Input Signals for Desktop Configurations ............................................ 102

3-5 Power Plane for Input Signals for Mobile Configurations............................................... 104

4-1 Intel® ICH9 and System Clock Domains.................................................................... 107

5-1 PCI Bridge Initiator Cycle Types............................................................................... 109

5-2 Type 1 Address Format........... .. .. .. ........... .. .. ..................... .. .. ...................... .. .. ........ 112

5-3 MSI vs. PCI IRQ Actions.......................................................................................... 114

5-4 LAN Mode Support ................................................................................................. 119

5-5 LPC Cycle Types Supported ..................................................................................... 124

5-6 Start Field Bit Definitions ................... .. .. .. .. ............................................................. 124

36 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5-7 Cycle Type Bit Definitions ........................................................................................125

5-8 Transfer Size Bit Definition ......................................................................................125

5-9 SYNC Bit Definition.................................................................................................126

5-10DMA Transfer Size..................................................................................................130

5-11Address Shifting in 16-Bit I/O DMA Transfers .............................................................130

5-12Counter Operating Modes ........................................................................................136

5-13Interrupt Controller Core Connections .......................................................................138

5-14Interrupt Status Registers .......................................................................................139

5-15Content of Interrupt Vector Byte ..............................................................................139

5-16APIC Interrupt Mapping1.........................................................................................145

5-17Interrupt Message Address Format ...........................................................................147

5-18Interrupt Message Data Format................................................................................148

5-19Stop Frame Explanation ..........................................................................................150

5-20Data Frame Format ................................................................................................151

5-21Configuration Bits Reset by RTCRST# Assertion..........................................................154

5-22INIT# Going Active......... .. .. ..................... .. .. .. ..................... .. .. ... ..................... .. .. .. ..156

5-23NMI Sources..........................................................................................................157

5-24DP Signal Differences..............................................................................................158

5-25General Power States for Systems Using Intel® ICH9..................................................160

5-26State Transition Rules for Intel® ICH9.......................................................................161

5-27System Power Plane ...............................................................................................162

5-28Causes of SMI# and SCI .........................................................................................163

5-29Break Events .........................................................................................................166

5-30Sleep Types...........................................................................................................170

5-31Causes of Wake Events ...........................................................................................171

5-32GPI Wake Events....................................................................................................172

5-33Transitions Due to Power Failure................ .. .. ...........................................................173

5-34Transitions Due to Power Button...................... .........................................................174

5-35Transitions Due to RI# Signal ................... .. ............................................ .................175

5-36Write Only Registers with Read Paths in ALT Access Mode............................................178

5-37PIC Reserved Bits Return Values...............................................................................180

5-38Register Write Accesses in ALT Access Mode ..............................................................180

5-39Intel® ICH9 Clock Inputs................. ... ..................... .. .. ..................... .. .. .. ........... .. .. ..183

5-40Causes of Host and Global Resets.............................................................................185

5-41Event Transitions that Cause Messages .....................................................................188

5-42Multi-activity LED Me ssag e Type.............. .. ...............................................................204

5-43Legacy Replacement Routing ...................................................................................207

5-44Bits Maintained in Low Power States .........................................................................213

5-45USB Legacy Keyboard State Transitions.....................................................................215

5-46UHCI vs. EHCI .......................................................................................................217

5-47Debug Port Behavior...............................................................................................226

5-48I2C Block Read.......................................................................................................234

5-49Enable for SMBALERT# ...........................................................................................236

5-50Enables for SMBus Slave Write and SMBus Host Events ...............................................236

5-51Enables for the Host Notify Command .......................................................................237

5-52Slave Write Registers..............................................................................................238

5-53Command Types ....................................................................................................239

5-54Slave Read Cycle Format.........................................................................................240

5-55Data Values for Slave Read Registers........................................................................240

5-56Host Notify Format .................................................................................................243

5-57Region Size versus Erase Granularity of Flash Components ..........................................251

5-58Region Access Control Table ....................................................................................253

5-59Hardware Sequencing Commands and Opcode Requirements .......................................256

5-60Flash Protection Mechanism Summary.......................................................................257

5-61Recommended Pinout for 8-Pin Serial Flash Device .....................................................258

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 37

5-62Recommended Pinout for 16-Pin Serial Flash Device ................................................... 259

6-1 Intel® ICH9 Ballout by Signal Name (Desktop Only) ................................................... 266

6-2 Intel® ICH9M and ICH9M-E Ballout by Signal Name (Mobile Only) ................................ 275

6-3 Intel® ICH9M-SFF Ballout by Signal Name - (Mobile Only)........................................... 284

8-1 Intel® ICH9 Absolute Maximum Ratings.................................................................... 295

8-2 DC Current Characteristics1 (Desktop Only)............................................................... 295

8-3 Preliminary DC Current Characteristics (Mobile Only)1 ................................................ 297

8-4 DC Characteristic Input Signal Association................................................................. 298

8-5 DC Input Characteristics ......................................................................................... 300

8-6 DC Characteristic Output Signal Association............................................................... 302

8-7 DC Output Characteristics ....................................................................................... 304

8-8 Other DC Characteristics......................................................................................... 306

8-9 Clock Timings........................................................................................................ 308

8-10PCI Interface Timing............................................................................................... 309

8-11Universal Serial Bus Timing..................................................................................... 310

8-12SATA Interf ace Timings ........ .. .. ..................... .. .. ........... .. .. ........... .. .. ........... .. .. .. ...... 311

8-13SMBus Timing ....................................................................................................... 312

8-14Intel® High Definition Audio Timing.......................................................................... 312

8-15LPC Timing............................................................................................................ 313

8-16Miscellaneous Timings ................ .. ..................... ... .. .. .......... .. ... .. ..................... .. .. .. .. 313

8-17SPI Timings (20 MHz)............................................................................................. 313

8-18SPI Timings (33 MHz)............................................................................................. 314

8-19SST Timings.......................................................................................................... 314

8-20PECI Tim i ngs........ ........... .. .......... ... .. .......... .. ........... .. .. ........... .. .......... .. ........... .. .. .. 315

8-21Power Sequencing and Reset Signal Timings.............................................................. 315

8-22Power Management Timings.................................................................................... 317

9-1 PCI Devices and Functions..... ................................ .. .. .. ..................... .. .. .. ................. 334

9-2 Fixed I/O Ranges Decoded by Intel® ICH9........................... .. .. ........... .. ........... .. .. ...... 336

9-3 Variable I/O Decode Ranges.................................................................................... 338

9-4 Memory Decode Ranges from Processor Perspective ................................................... 339

10-1Chipset Configuration Register Memory Map (Memory Space) ...................................... 343

11-1PCI Bridge Register Address Map (PCI-PCI—D30:F0) .................................................. 395

12-1Gigabit LAN Configuration Registers Address Map (Gigabit LAN —D25:F0) ..................... 411

12-2Gigabit LAN Base Address A Registers Address Map (Gigabit LAN— D25:F0) .................. 424

13-1LPC Interface PCI Register Address Map (LPC I/F—D31:F0) ......................................... 427

13-2DMA Registers....................................................................................................... 452

13-3PIC Registers (LPC I/F—D31:F0).............................................................................. 465

13-4APIC Direct Registers (LPC I/F—D31:F0)................................................................... 474

13-5APIC Indirect Registers (LPC I/F—D31:F0)................................................................. 474

13-6RTC I/O Registers .................................................................................................. 479

13-7RTC (Standard) RAM Bank ...................................................................................... 480

13-8Processor Interface PCI Regi ster Address Map (LPC I/F—D31:F0) ... ............ .................. 484

13-9Power Management PCI Register Address Map (PM—D31:F0)....................................... 487

13-10APM Register Map ................................................................................................ 500

13-11ACPI and Leg acy I/O Reg i ster Map ... ............................... .. .. .. ...................... .. .. .. ...... 501

13-12TCO I/O Register Address Map............................................................................... 526

13-13Registers to Control GPIO Address Map ................................................................... 534

14-1SATA Controller PCI Register Addr e ss Map (SAT A –D 3 1:F2)............. .. .. .. .. .. .. ............. .. .. 541

14-2Bus Master IDE I/O Register Address Map ................................................................. 568

14-3AHCI Regi ste r Add re s s Map.............. .......... .. .. ........... .. .. ........... .. .. .......... .. ........... .. .. 577

14-4Generic Host Controller Register Address Map............................................................ 578

14-5Port [5:0] DMA Register Address Map....................................................................... 586

15-1SATA Controller PCI Register Addr e ss Map (SAT A –D 3 1:F5)............. .. .. .. .. .. .. ............. .. .. 605

15-2Bus Master IDE I/O Register Address Map ................................................................. 622

15-3AHCI Index Data Pair Register Map ........... .. .. ........................................................... 625

38 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

16-1UHCI Controller PCI Configuration Map......................................................................631

16-2UHCI Controller PCI Register Address Map

(USB—D29:F0/F1 /F2/F3 , D2 6 :F0 /F1 / F2) .............. .. ... .. .. ............ ............. ............. ......631

16-3USB I/O Registers .......................... ... .. ..................... .. .. .. ........... .. .. ..................... .. ..644

16-4Run/Stop, Debug Bit Interaction SWDBG (Bit 5), Run/Stop (Bit 0) Operation..................647

17-1USB EHCI PCI Register Address Map (USB EHCI—D29:F7, D26:F7)...............................655

17-2Enhanced Host Controller Capability Registers............................................................676

17-3Enhanced Host Controller Operational Register Address Map ........................................680

17-4Debug Port Register Address Map.............................................................................694

18-1Intel® High Definition Audio PCI Register Address Map

(Intel® High Definition Audio D27:F0) .......................................................................699

18-2Intel® High Definition Audio PCI Register Address Map

(Intel® High Definition Audio D27:F0) .......................................................................722

19-1SMBus Controller PCI Register Address Map (SMBus—D31:F3) .....................................751

19-2SMBus I/O and Memory Mapped I/O Register Address Map ..........................................758

20-1PCI Express* Configuration Registers Address Map

(PCI Express—D28:F0/F1/F2/F3/F4/F5).....................................................................769

21-1Memory-Mapped Registers.......................................................................................815

22-1Serial Peripheral Interface (SPI) Register Address Map

(SPI Memory Mappe d Conf igur ation Registers) ....................... .. ............. .. ............. ......821

22-2Gigabit LAN SPI Flash Program Register Address Map

(GbE LAN Memory Mapped Configuration Registers)....................................................860

23-1Thermal Sensor Register Address Map.......................................................................873

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 39

Revision History

Revision

Number Description Revision Date

-001 • Initial release June 2007

-002 • Added spcifications for Intel® 82801IO ICH9DO August 2007

-003 • Added mobile family – Intel 82801IBM ICH9M and 82801IEM ICH9M-E

• Added specification update information. July 2008

-004 • Added ICH9M-SFF ICH9-I/O Controller Hub August 2008

40 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Intel® ICH9 Features

Direct Media Interface

—10 Gb/s each direction, full duplex

—Transparent to software

PCI Express*

—6 PCI Express root ports

—Supports PCI Express 1.1

—Ports 1-4 can be statically configured as 4x1, or 1x4

—Support for full 2.5 Gb/s bandwidth in each direction

per x1 lane

—Module based Hot-Plug supported

(e.g., ExpressCard*)

PCI Bus Interface

—Supports PCI Rev 2.3 Specification at 33 MHz

—Four available PCI REQ/GNT pairs

—Support for 64-bit addressing on PCI using DAC

protocol

Integrated Serial ATA Host Controller

—Up to six SATA ports

—Data transfer rates up to 3.0 Gb/s

(300 MB/s).

—Integrated AHCI controller

External SATA support

—NEW: Port Disable Capability

Intel® Matrix Storage Technology (ICH9R, ICH9DH,

ICH9DO, ICH9M, and ICH9M-E only)

—Configures the ICH9 SATA Controller as an AHCI

controller

—Configures the ICH9 SATA controller as a RAID

controller supporting RAID 0/1/5/10 (Except ICH9M)

Intel® High Definition Audio Interface

—PCI Express endpoint

—Independent Bus Master logic for eight general

purpose streams: four input and four output

—Support four external Codecs

—Supports variable length stream slots

—Supports multichannel, 32-bit sample depth, 192 kHz

sample rate output

—Provides mic array support

—Allows for non-48 kHz sampling output

—Support for ACPI Device States

—Low Voltage Mode

—Docking Support (ICH9M only)

Intel® Quiet System Technology (Desktop only)

—Four TACH signals and three PWM signals

—NEW: Improved algorithms for better performance

Simple Serial Tra n s port (SST) 1.0 Bus and Platform

Environmental Control Interface (PECI) (Desktop only)

USB 2.0

—NEW: Six UHCI Host Controllers, supporting up to

twelve external ports

—Two EHCI Host Controllers, supporting up to twelve

external ports

—Two Configuration Options for EHCI Controllers 6+6

and 8+4

—Per-Port-Disable Capability

—Includes up to two USB 2.0 High-speed Debug Ports

—Supports wake-up from sleeping states S1–S4

—Supports legacy Keyboard/Mouse software

Integrated Gigabit LAN Controller

—Integrated ASF Management Controller

—Network security with System Defens e

—Supports IEEE 802.3

—LAN Connect Interface (LCI) and Gigabit LAN

Connect Interface (GLCI)

—10/100/1000 Mbps Ethernet Support

—NEW: Jumbo Frame Support

Intel® Active Management Technology with System

Defense (Digital Office only)

—NEW: Network Outbreak Containment Heuristics

Intel® I/O Virtualization (VT-d) support

Intel® Trusted Execution Technology support

Power Management Logic

—Supports ACPI 3.0b

—ACPI-defined power states (C1, C2, S1, S3–S5 for

Desktop and C1–C6, S1, S3–S5 for Mobile)

—ACPI Power Management Timer

—(Mobile Only) Support for “Intel SpeedStep®

Technology” processor power control and “Deeper

Sleep” power state

—PCI CLKRUN# (Mobile only) and PME# support

—SMI# generation

—All registers readable/restorable for proper resume

from 0 V suspend states

—Support for APM-based legacy power management for

non-ACPI Desktop and Mobile implementations

External Glue Integration

—Integrated Pull-up, Pull-down and Series Termination

resistors on processor I/F

—Integrated Pull-down and Series resistors on USB

Enhanced DMA Controller

—Two cascaded 8237 DMA controllers

—Supports LPC DMA

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 41

Note: Not all features are available on all ICH9 components. See Section 1.3 for more details.

SMBus

—Faster speed, up to 100 kbps

—Flexible SMBus/SMLink architecture to optimize for

ASF

—Provides independent manageability bus through

SMLink interface

—Supports SMBus 2.0 Specification

—Host interface allows processor to communicate via

SMBus

—Slave interface allows an int ernal or external

Microcontroller to access system resource s

—Compatible with most two-wire components that are

also I2C compatible

High Precision Event Timers

—Advanced operating system interrupt scheduling

Timers Based on 82C54

—System timer, Refresh request, Speaker tone output

Real-Time Clock

—256-byte battery-backed CMOS RAM

—Integrated oscillator components

—Lower Power DC/DC Convert er implementation

System TCO Reduction Circuits

—T imers to generate SMI# and Reset upon detection of

system hang

—Timers to detect improper processor reset

—Integrated processor frequency strap logic

—Supports ability to disable external devices

Interrupt Controller

—Supports up to eight PCI interrupt pins

—Supports PCI 2.3 Message Signaled Interrupts

—Two cascaded 82C59 with 15 interrupts

—Integrated I/O APIC capability with 24 interrupts

—Supports Processor System Bus interrupt delivery

1.05 V operation with 1.5 and 3.3 V I/O

—5 V tolerant buffers on PCI, USB and selected Legacy

signals

1.05 V Core Voltage

Five Integrated Voltage Regulators for different power

rails

Firmware Hub I/F supports BIOS Memory size up to 8

MBytes

Serial Peripheral Interface (SPI)

—Supports up to two SPI devices

—Supports 20 MHz and 33 MHz SPI devices

—NEW: Dual erase support

Low Pin Count (LPC) I/F

—Supports two Master/DMA devices.

—Support for Security Device (Trusted Platform

Module) connected to LPC.

GPIO

—TTL, Open-Drain, Inversion

—NEW: GPIO lock down

Package 31x31 mm mixed-pitch 676 mBGA

—Different footprint for Mobile

42 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

§ §

Desktop Configuration

Mobile Configuration

SPI BIOS

SPI Flash

Intel® Gigabit

Ethernet Phy

Intel®

ICH9

USB 2.0

(Suppor ts 12 USB ports

Dual EHCI Controller)

System Management

(TCO)

GPIO

SMBus 2.0/I2C

Power Management

PCI Bus

...

Clock Gene rator

Intel® High Definition

Audio Codec(s)

Firmware Hub

Other ASICs

(Optional)

LPC I/F

Super I/O

SATA (6 ports)

PCI Express* x1

DMI

(To (G)MCH)

TPM

(Optional)

LCI

GLCI

Intel®

ICH9M

USB 2.0

(Supp orts 12 U SB ports

D ual E HC I Controllers)

System M anagem ent

(TCO)

GPIO

SM Bus 2.0/I2C

Pow er M anagem ent

PCI Bus

Clock Generator

Cardbus

C on troller (&

attached slots)

DMI

(T o (G)MCH )

In te l® Gig a b it

Ethern et Phy

In te l® H ig h D e fin ition

Aud io C odec(s)

Flash BIO S

Other ASICs

(Optional)

LPC I/F

S u p e r I/O

SATA (4 ports)

Docking

Bridge

PCI Express x1

TPM

(Optional)

GLCI

LCI

SPI Flash

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 43

Introduction

1 Introduction

This document is intended for Original Equipment Manufacturers and BIOS vendors

creating Intel® I/O Controller Hub 9 (ICH9) Family based products. This document is

for the following components:

•Intel

® 82801IB ICH9 (ICH9)

•Intel

® 82801IR ICH9 RAID (ICH9R)

•Intel

® 82801IH ICH9 Digital Home (ICH9DH)

•Intel

® 82801IO ICH9 Digital Office (ICH9DO)

•Intel

® 82801IBM ICH9 Mobile (ICH9M)

•Intel

® 82801IEM ICH9 Mobile Enhanced (ICH9M-E)

Section 1.3 provides high-level feature differences for the ICH9 Family components.

Note: Throughout this document, ICH9 is used as a general ICH9 term and refers to the Intel

82801IB ICH9, Intel 82801IR ICH9R, and Intel 82801IH ICH9DH, and Intel 82801IO

ICH9DO, Intel 82801IBM ICH9M, and Intel 82801IEM ICH9M-E components, unless

specifically noted otherwise.

Note: Throughout this document, the term “Desktop” refers to any implementation using a

desktop version of the ICH9 (e.g. ICH9R), be it in a desktop, server, workstation, etc.,

unless specifically noted otherwise.

Note: Throughout this document, the term “Desktop Only” refers to information that is for the

Intel 82801IB ICH9, Intel 82801IR ICH9R, and Intel 82801IH ICH9DH, and Intel

82801IO ICH9DO unless specifically noted otherwise. The term “Digital Home

Only“refers to information that is for the Intel 82801IH ICH9DH, unless specifically

noted otherwise. The term “Digital Office Only“ refers to information that is for the Intel

82801IO ICH9DO and Intel 82801IBM ICH9M-E, unless specifically noted otherwise.

The term “Mobile Only” refers to information that is for both the Intel 82801IBM ICH9M

and Intel 82801IEM ICH9M-E, unless noted otherwise.

1.1 About This Document

This document is intended for Original Equipment Manufacturers and BIOS vendors

creating Intel® ICH9 family-based products (See Section 1.3 for currently defin ed ICH9

components). This document assumes a working knowledge of the vocabulary and

principles of PCI Express*, USB, AHCI, SATA, Intel® High Definition Audio (Intel® HD

Audio), SMBus, PCI, ACPI and LPC. Although some details of these features are

described within this manual, refer to the individual industry specifications listed in

Table 1-1 for the complete details.

Table 1-1. Industry Spe c ifications

Specification Location

PCI Express* Base Specification, Revision 1.1 http://www.pcisig.com/specifications

Low Pin Count Interface Specification , Revisi on

1.1 (LPC) http://developer.intel.com/design/chipsets/

industry/lpc.htm

System Management Bus Specification, Version

2.0 (SMBus) http://www.smbus.org/specs/

Introduction

44 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Document users may also need to reference the following Intel Specification listed in

Table 1-2 when using this document.

PCI Local Bus Specif ication, Revision 2.3 (PCI) http://www.pcisig.com/specifications

PCI Mobile Design Guide , Revision 1.1 http://www.pcisig.com/specifications

PCI Power Management Specification, R evision

1.1 http://www.pcisig.com/specifications

Universal Ser ial Bus Specification (USB),

Re visio n 2.0 http://www.usb.org/developers/docs

Advanced Configuration and Power Interface,

Version 3.0b (ACPI) http://www.acpi.info/spec.htm

Universal Host Controller Interface, Revision

1.1 (UHCI) http://developer.intel.com/technology/USB/

UHCI11D.htm

Enhanced Host Controller Interface

Specification for Universal Serial Bus, Revision

1.0 (EHCI)

http://developer.intel.com/technology/usb/

ehcispec.htm

Serial ATA Specification, Revision 1.0a http://www.serialata.org/specifications.asp

Serial ATA II: Extensions to Serial ATA 1.0,

Re visio n 1.0 http://www.serialata.org/specifications.asp

Serial ATA II Cables and Connectors Volume 2

Gold http://www.serialata.org/specifications.asp

Alert Standard Format Specification, Version

1.03 http://www.dmtf.org/standards/asf

IEEE 802.3 Fast Ethernet http://standards.ieee.org/getieee802/

IA-PC HPET (High Precision Event Timers)

Specification, Revision 0.98a http://www.intel.com/technology/architecture/

hpetspec.htm

TPM Specification 1.02, Level 2 Revision 103 http://www.trustedcomputinggroup.org/specs/

TPM

Table 1-1. Industry Specifications

SpecificationLocation

Table 1-2. Intel Specification

Specification Location

Intel® I/O Controller Hub (ICH9) Family Datasheet

Specification Update www.intel.com/design/chipsets/

specupdt/316973.htm

Intel® I/O Controller Hub (ICH9) Thermal and

Mechanical Design Guide www.intel.com/design/chipsets/

designex/316974.htm

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 45

Introduction

Chapter 1. Introduction

Chapter 1 introduces the ICH9 and provides information on manual organization and

gives a general overview of the ICH9.

Chapter 2. Signal Description

Chapter 2 provides a block diagra m of the ICH9/ICH 9M and a detailed descrip tion of

each signal. Signals are arranged according to interface and details are provided as to

the drive characteristics (Input/Output, Open Drain, etc.) of all signals.

Chapter 3. Intel® ICH9 Pin States

Chapter 3 provides a complete list of signals, their associated power well, their logic

level in each suspend state, and their logic level before and after reset.

Chapter 4. Intel® ICH9 and System Clock Domains

Chapter 4 provides a list of each clock domain associated with the ICH9 in an ICH9

based system.

Chapter 5. Functional Description

Chapter 5 provides a detailed description of the functions in the ICH9. All PCI buses,

devices and functions in this manual are abbreviated using the following nomenclature;

Bus:Device:Function. This manual abbreviates a bus as B0, devices as D25, D26, D27,

D28, D29, D30 and D31 and functions as F0, F1, F2, F3, F4, F5, F6 and F7. For example

Device 31 Function 0 is abbreviated as D31:F0, Bus 0 Device 25 Function 0 is

abbreviated as B0:D25:F0. Generally, the bus number will not be used, and can be

considered to be Bus 0. Note that the ICH9’s external PCI bus is typically Bus 1, but

may be assigned a different number depending upon system configuration.

Chapter 6. Ballout Definition

Chapter 6 provides a table of each signal and its ball assignment in the 676-mBGA

package.

Chapter 7. Package Information

Chapter 7 provides drawings of the physical dimensions and characteristics of the 676-

mBGA package.

Chapter 8. Electrical Characteristics

Chapter 8 provides all AC and DC characteristics including detailed timing diagrams.

Chapter 9. Register and Memory Mappings

Chapter 9 provides an overview of the registers, fixed I/O ranges, variable I/O ranges

and memory ranges decoded by the ICH9.

Chapter 10. Chipset Configuration Registers

Chapter 10 provides a detailed description of all registers and base functionality that is

related to chipset configuration and not a specific interface (such as LPC, PCI, or PCI

Express*). It contains the root complex register block, which describes the behavior of

the upstream internal link.

Chapter 11. PCI-to-PCI Bridge Registers

Chapter 11 provides a detailed description of all registers that reside in the PCI-to-PCI

bridge. This bridge resides at Device 30, Function 0 (D30:F0).

Chapter 12. Integrated LAN Controller Registers

Chapter 12 provides a detailed description of all registers that reside in the ICH9’s

integrated LAN controller. The integrated LAN Controller resides at Device 25, Function

0 (D25:F0).

Introduction

46 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Chapter 13. LPC Bridge Registers

Chapter 13 provides a detailed description of all registers that reside in the LPC bridge.

This bridge resides at Device 31, Function 0 (D31:F0). This function contains registers

for many different units within the ICH9 including DMA, Timers, Interrupts, Processor

Interface, GPIO, Power Management, System Management and RTC.

Chapter 14. SATA Controller Registers

Chapter 14 provides a detailed description of all registers that reside in the SATA

controller #1. This controller resides at Device 31, Function 2 (D31:F2).

Chapter 15. SATA Controller Registers

Chapter 15 provides a detailed description of all registers that reside in the SATA

controller #2. This controller resides at Device 31, Function 5 (D31:F5).

Chapter 16. UHCI Controller Registers

Chapter 16 provides a detailed description of all registers that reside in the six UHCI

host controllers. These controllers reside at Device 29, Functions 0, 1, 2, and 3

(D29:F0/F1/F2/F3) and Device 26, Function 0, 1 and 2 (D26:F0/F1/F2).

Chapter 17. EHCI Controller Registers

Chapter 17 provides a detailed description of all registers that reside in the two EHCI

host controllers. These controllers reside at Device 29, Function 7 (D29:F7) and Device

26, Function 7 (D26:F7).

Chapter 18. SMBus Controller Registers

Chapter 19 provides a detailed description of all registers that reside in the SMBus

controller. This controller resides at Device 31, Function 3 (D31:F3).

Chapter 19. Intel® High Definition Audio Controller Registers

Chapter 18 provides a detailed description of all registers that reside in the Intel High

Definition Audio controller. This controller resides at Device 27, Function 0 (D27:F0).

Chapter 20. PCI Express* Port Controller Registers

Chapter 20 provides a detailed description of all registers that reside in the PCI Express

controller. This controller resides at Device 28, Functions 0 to 5 (D28:F0-F5).

Chapter 21. High Precision Event Timers Registers

Chapter 21 provides a detailed description of all registers that reside in the multimedia

timer memory mapped register space.

Chapter 22. Serial Peripheral Interface Registers

Chapter 22 provides a detailed description of all registers that reside in the SPI

memory mapped register space.

Chapter 23. Thermal Sensors

Chapter 23 provides a detailed description of all registers that reside in the thermal

sensors PCI configuration space. The registers reside at Device 31, Function 6

(D31:F6).

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 47

Introduction

1.2 Overview

The ICH9 provides extensive I/O support. Functions and capabilities include:

•PCI Express* Base Specification, Revision 1.1 support

•PCI Local Bus Specification, Revision 2.3 support for 33 MHz PCI operations

(supports up to four Req/Gnt pairs).

• ACPI Power Management Logic Support, Revision 3.0b

• Enhanced DMA controller, interrupt controller, and timer functions

• Integrated Serial AT A h ost controllers with independent DMA oper ation on up to six

ports (Desktop only) or four ports (Mobile only) and AHCI support.

• USB host interface with support for up to twelve USB ports; six UHCI host

controllers; two EHCI high-speed USB 2.0 Host controllers

• Integrated 10/100/1000 Gigabit Ethernet MAC with System Defense

•System Management Bus (SMBus) Specification, Version 2.0 with additional

support for I2C devices

• Supports Intel® High Definition Audio

• Supports Intel® Matrix Storage Technology (Intel® ICH9R, ICH9DH, ICH9 DO,

ICH9M, and ICH9M-E Only)

• Supports Intel® Active Management Technology (Digital Office only)

• Supports Intel® Virtualization Technology for Directed I/O

• Supports Intel® Trusted Execution Technology

• Low Pin Count (LPC) interfa c e

• Firmware Hub (FWH) interface support

• Serial Peripheral Interface (SPI) support

•Intel

® Quiet System Technology (Desktop Only)

• Integrated TPM 1.2 (Mobile Only)

The Intel ICH9 incorporates a variety of PCI devices and functions, as shown in

Table 1-3. They are divided into seven logical devices. The first is the DMI-To-PCI

bridge (Device 30). The second device (Device 31) contains most of the standard PCI

functions that always existed in the PCI-to-ISA bridges (South Bridges), such as the

Intel PIIX4. The third and fourth (Device 29 and Device 26) are the USB host controller

devices. The fifth (Device 28) is PCI Express device. The sixth (Device 27) is the HD

Audio controller device, and the seventh (Device 25) is the Gigabit Ethernet controller

device.

Table 1-3. PCI Devices and Functions (Sheet 1 of 2)

Bus:Device:Function Function Description

Bus 0:Device 30:Function 0 DMI-to-PCI Bridge

Bus 0:Device 31:Function 0 LPC Controller1

Bus 0:Device 31:Func tion 2 SATA Controller #1

Bus 0:Device 31:Func tion 5 SATA Controller #23

Bus 0:Device 31:Function 6 Thermal Subsystem

Bus 0:Device 31:Function 3 SMBus Controller

Bus 0:Device 29:Function 0 USB FS/LS UHCI Controller #1

Introduction

48 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. The PCI-to-LPC bridge contains registers that control LPC, Power Management, System

Management, GPIO, Processor Interface, RTC, Interrupts, Timers, and DMA

2. Device 26:Function 2 maybe configured as Device 29:Function 3 during BIOS Post.

3. SATA Controller 2 is only visible when D31:F2 CC.SCC=01h.

Bus 0:Device 29:Function 1 USB FS/LS UHCI Controller #2

Bus 0:Device 29:Function 2 USB FS/LS UHCI Controller #3

Bus 0:Device 29:Function 3 USB FS/LS UHCI Controller #62

Bus 0:Device 29: Function 7 USB HS EHCI Controlle r #1

Bus 0:Device 26:Function 0 USB FS/LS UHCI Controller #4

Bus 0:Device 26:Function 1 USB FS/LS UHCI Controller #5

Bus 0:Device 26:Function 2 USB FS/LS UHCI Controller #62

Bus 0:Device 26:Fucntion 7 USB HS EHCI Controller #2

Bus 0:Device 28: Function 0 PCI Express* Port 1

Bus 0:Device 28: Function 1 PCI Express Port 2

Bus 0:Device 28: Function 2 PCI Express Port 3

Bus 0:Device 28: Function 3 PCI Express Port 4

Bus 0:Device 28: Function 4 PCI Express Port 5

Bus 0:Device 28: Function 5 PCI Express Port 6

Bus 0:Device 27 :Function 0 Intel® High Definition Audio Controller

Bus 0:Device 25:Function 0 Gigabit Ethernet Controller

Table 1-3. PCI Devices and Functions (Sheet 2 of 2)

Bus:Device:Function Function Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 49

Introduction

1.2.1 Capability Overview

The following sub-sections provide an overview of the ICH9 capabilities.

Direct Media Interface (DMI)

Direct Media Interface (DMI) is the chip-to-chip connection between the Memory

Controller Hub / Graphics Memory Controller Hub ((G)MCH) and I/O Controller Hub 9

(ICH9). This high-speed interface integrates advanced priority-based servicing allowing

for concurrent traffic and true isochronous transfer capabilities. Base functionality is

completely software-transparent, permitting current and legacy software to operate

normally.

PCI Express* Interface

The ICH9 provides up to 6 PCI Express Root Ports, supporting the PCI Express Base

Specification, Revision 1.1. Each Root Port supports 2.5 GB/s bandwidth in each

direction (5 GB/s concurrent). PCI Express Root Ports 1-4 can be statically configured

as four x1 P orts or ganged together to form one x4 port. Ports 5 and 6 can only be used

as two x1 ports. On Mobile platforms, PCI Express Ports 1-4 can also be configured as

one x2 port (using ports 1 and 2) with ports 3 and 4 configured as x1 ports.

Note: The integrated Gigabit Ethernet controllers data lines for 1000 Mb/s speed are

multiplexed with PCI Express* Root Port 6 and therefore una vailabl e if a Gigabi t

Ethernet PHY is connected. The use of a 10/100 Mb/s PHY does not consume PCI

Express Root Port 6 and therefore the port is available to be utilized as a x1 Port.

Serial ATA (SATA) Controller

The ICH9 has two integrated SATA host controllers that support independent DMA

operation on up to six ports (desktop only) or four ports (mobile only) and supports

data transfer rates of up to 3.0 Gb/s (300 MB/s). The SATA controller contains two

modes of operation – a legacy mode using I/O space, and an AHCI mode using memory

space. Software that uses legacy mode will not have AHCI capabilities.

The ICH9 supports the Serial ATA Specification, Revision 1.0a. The ICH9 also supports

several optional sections of the Serial ATA II: Extensions to Serial ATA 1.0

Specification, Revision 1.0 (AHCI support is required for some elements).

Note: SATA Ports 2 and 3 are not functional in the ICH9 Base and Mobile components. See

Section 1.3 for details on component feature availability.

AHCI

The ICH9 provides hardware support for Advanced Host Controller Interface (AHCI), a

new programming interface for SATA host controllers. Platforms supporting AHCI may

take advantage of performance features such as no master/slave designation for SATA

devices—each device is treated as a master—and hardware-assisted native command

queuing. AHCI also provides usability enhancements such as Hot-Plug. AHCI requires

appropriate software support (e.g., an AHCI driver) and for some features, hardware

support in the SATA device or additional platform hardware. Se e Section 1.3 for details

on component feature availability.

Intel® Matrix Storage Technology (Intel® ICH9R, ICH9DH, ICH9DO,

ICH9M, and ICH9M-E Only)

The ICH9 provides support for Intel® Matrix Storage Technology, providing both AHCI

(see above for details on AHCI) and integrated RAID functionality. The industry-leading

RAID capability provides high-performance RAID 0, 1, 5, and 10 functionality on up to

Introduction

50 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

6 SATA ports of ICH9. Matrix RAID support is provided to allow multiple RAID levels to

be combined on a single set of hard drives, such as RAID 0 and RAID 1 on two disks.

Other RAID features include hot spare support, SMART alerting, and RAID 0 auto

replace. Software components include an Option ROM for pre-boot configuration and

boot functionality, a Microsoft Windows* compatible driver, and a user interface for

configuration and management of the RAID capability of ICH9. Please see Section 1.3

for details on component feature availability.

Note: Intel® Matrix Storage Technology RAID functionality not supported on ICH9M base

component.

PCI Interface

The ICH9 PCI interface provides a 33 MHz, Revision 2.3 implementation. The ICH9

integrates a PCI arbiter that supports up to four external PCI bus masters in addition to

the internal ICH9 requests. This allows for combinations of up to four PCI down devices

and PCI slots.

Low Pin Count (LPC) Interface

The ICH9 implements an LPC Interface as described in the LPC 1.1 Specification. The

Low Pin Count (LPC) bridge function of the ICH9 resides in PCI Device 31:Function 0. In

addition to the LPC bridge interface function, D31:F0 contains other functional units

including DMA, interrupt controllers, timers, power management, system management,

GPIO, and RTC.

Serial Peripheral Interface (SPI)

The ICH9 implements an SPI Interface as an alternative interface for the BIOS flash

device. An SPI flash device can be used as a replacement for the FWH, and is required

to support Gigabit Ethernet, Intel® Active Management Technology (Intel® ICH9DO

and ICH9M-E only), and integrated Intel® Quiet System Technology (Desktop Only).

The ICH9 supports up to two SPI flash devices with speed up to 33 MHz using two chip

select pins.

Compatibility Modules (DMA Controller, Timer/Counters, Interrupt

Controller)

The DMA controller incorporates the logic of two 82C37 DMA controllers, with seven

independently programmable channels. Channels 0–3 are hardwired to 8-bit, count-by-

byte transfers, and channels 5–7 are hardwired to 16-bit, count -by-word tr ansfers. Any

two of the seven DMA channels can be programmed to support fast Type-F transfers.

Channel 4 is reserved as a generic bus master request.

The ICH9 supports LPC DMA, which is similar to ISA DMA, through the ICH9’s DMA

controller. LPC DMA is handled through the use of the LDRQ# lines from peripherals

and special encoding on LAD[3:0] from the host. Single, Demand, Verify, and

Increment modes are supported on the LPC interface.

The timer/counter block contains three counters that are equivalent in function to those

found in one 82C54 programmable interval timer. These three counters are combined

to provide the system timer function, and speaker tone. The 14.31818 MHz oscillator

input provides the clock source for these three counters.

The ICH9 provides an ISA-Compatible Programmable Interrupt Controller (PIC) that

incorporates the functionality of two, 82C59 interrupt controllers. The two interrupt

controllers are cascaded so that 14 external and two internal interrupts are possible. In

addition, the ICH9 supports a serial interrupt scheme.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 51

Introduction

All of the registers in these modules can be read and restored. This is required to save

and restore system state after power has been removed and restored to the platform.

Advanced Programmable Interrupt Controller (APIC)

In addition to the standard ISA compatible Programmable Interrupt controller (PIC)

described in the previous section, the ICH9 incorporates the Advanced Programmable

Interrupt Controller (APIC).

Universal Serial Bus (USB) Controllers

The ICH9 contains up to two Enh anced Host Controller Interface (EHCI) host controllers

that support USB high-speed signaling. High-speed USB 2.0 allows data transfers up to

480 Mb/s which is 40 times faster than full-speed USB. The ICH9 also contains up to six

Universal Host Controller Interface (UHCI) controllers that support USB full-speed and

low-speed signaling.

The ICH9 supports up to twelve USB 2.0 ports. All twelve ports are high-speed, full-

speed, and low-speed capable. ICH9’s port-routing logic determines whether a USB

port is controlled by one of the UHCI or EHCI controllers. See Section 5.18 and

Section 5.19 for details.

Gigabit Ethernet Controller

The Gigabit Ethernet Controller provides a system interface via a PCI function. The

controller provides a full memory-mapped or IO mapped interface along with a 64 bit

address master support for systems using more than 4 GB of physical memory and

DMA (Direct Memory Addressing) mechanisms for high performance data tr ansfers. Its

bus master capabilities enable the component to process high-level commands and

perform multiple operations; this lowers processor utilization by off-loading

communication tasks from the processor. Two large configurable transmit and receive

FIFOs (up to 20 KB each) help prevent data underruns and overruns while waiting for

bus accesses. This enables the integrated LAN controller to transmit data with

minimum interfra me spacing (IFS).

The LAN controller can operate at multiple speeds (10/100/1000 MB/s) and in either

full duplex or half duplex mode. In full duplex mode the LAN controller adheres with the

IEEE 802.3x Flow Control Specification. Half duplex performance is enhanced by a

proprietary collision reduction mechanism. See Section 5.3 for details.

RTC

The ICH9 contains a Motorola MC146818A-compatible real-time clock with 256 bytes of

battery-backed RAM. The real-time clock performs two key functions: keeping track of

the time of day and storing system data, even when the system is powered down. The

RTC operates on a 32.768 KHz crystal and a 3 V battery.

The R TC also supports two lockable memory r anges. By setting bits in the configuration

space, two 8-byte ranges can be locked to read and write accesses. This prevents

unauthorized reading of passwords or other system security information.

The R TC also supports a date alarm that allows for scheduling a wak e up event up to 30

days in advance, rather than just 24 hours in advance.

GPIO

Various general purpose inputs and outputs are provided for custom system design.

The number of inputs and outputs varies depending on ICH9 configuration.

Introduction

52 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Enhanced Power Management

The ICH9’s power management functions include enhanced clock control and various

low-power (suspend) states (e.g., Suspend-to-RAM and Suspend-to-Disk). A hardware-

based thermal management circuit permits software-independent entrance to low-

power states. The ICH9 contains full support for the Advanced Configuration and Power

Interface (ACPI) Specification, Revision 3.0a.

Intel® Active Management Technology (Intel® AMT) (Digital Office

Only)

Intel® Active Management Technology is the next generation of client manageability via

the wired network. Intel AMT is a set of adv anced manageability features developed as

a direct result of IT customer feedback gained through Intel market research. With the

new implementation of System Defense in ICH9, the advanced manageability feature

set of Intel AMT is further enhanced. Please see Section 1.3 for details on component

feature availability.

Manageability

The ICH9 integrates several functions designed to manage the system and lower the

total cost of ownership (TCO) of the system. These system management functions are

designed to report errors, diagnose the system, and recover from system lockups

without the aid of an external microcontroller.

•TCO Timer. The ICH9’s integrated programmable TCO timer is used to detect

system locks. The first expiration of the timer generates an SMI# that the system

can use to recover fro m a software lock. Th e second expir ation of the timer causes

a system reset to recover from a hardware lock.

•Processor Present Indicator. The ICH9 looks for the processor to fetch the first

instruction after reset. If the processor does not fetch the first instruction, the ICH9

will reboot the system.

•ECC Error Reporting. When detecting an ECC error, the host controller has the

ability to send one of several messages to the ICH9. The host controller can

instruct the ICH9 to generate either an SMI#, NMI, SERR#, or TCO interrupt.

•Function Disable. The ICH9 provides the ability to disable the following integr ated

functions: LAN, USB, LPC, Intel HD Audio, SATA, PCI Express or SMBus. Once

disabled, these functions no longer decode I/O, memory, or PCI configuration

space. Also, no interrupts or power management events are generated from the

disabled functions.

•Intruder Detect. The ICH9 provides an input signal (INTRUDER#) that can be

attached to a switch that is activated by the system case being opened. The ICH9

can be programmed to generate an SMI# or TCO interrupt due to an active

INTRUDER# signal.

System Management Bus (SMBus 2.0)

The ICH9 contains an SMBus Host interface that allows the processor to communicate

with SMBus slaves. This interface is compatible with most I2C devices. Special I2C

commands are implemented.

The ICH9’s SMBus host controller provides a mechanism for the processor to initiate

communications with SMBus peripherals (slaves). Also, the ICH9 supports slave

functionality, including the Host Notify protocol. Hence, the hos t control ler supports

eight command protocols of the SMBus interface (see System Management Bus

(SMBus) Specification, Version 2.0): Quick Command, Send Byte, R e ceiv e Byte, Write

Byte/Word, Read Byte/Word, Process Call, Block Read/Write, and Host Notify.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 53

Introduction

ICH9’s SMBus also implements hardware-based Packet Error Checking for data

robustness and the Address Resolution Protocol (ARP) to dynamically provide address

to all SMBus devices.

Intel® High Definition Audio Controller

The Intel® High Definition Audio Specification defines a digital interface that can be

used to attach different types of codecs, such as audio and modem codecs. The ICH9

Intel® HD Audio controller supports up to 4 codecs. The link can operate at either 3.3 V

or 1.5 V.

With the support of multi-channel audio stream, 32-bit sample depth, and sample rate

up to 192 kHz, the Intel® HD Audio controller provides audio quality that can deliver CE

levels of audio experience. On the input side, the ICH9 adds support for an array of

microphones.

Intel® Quiet System Technology (Intel® QST) (Desktop Only)

The ICH9 integrates four fan speed sensors (four TACH signals) and 3 fan speed

controllers (three Pulse Width Modulator signals), which enables monitoring and

controlling up to four fans on the system. With the new implementation of the single-

wire Simple Serial Transport (SST) 1.0 bus and Platform Environmental Control

Interface (PECI), the ICH9 provides an easy way to connect to SST-based thermal

sensors and access the processor thermal data. In addition, coupled with the new

sophisticated fan speed control algorithms, Intel® QST provides effective thermal and

acoustic management for the platform.

Note: Intel® Quiet System Technology functionality requires a correctly configured system,

including an appropriate (G)MCH with ME, ME firmware, and system BIOS support.

Intel® Virtualization Technology for Directed I/O (Intel® VT-d)

The ICH9 provides hardware support for implementation of Intel® Virtualization

Technology with Directed I/O (Intel® VT-d). Intel VT-d Technology consists of

technology components that support the virtualization of platforms based on Intel®

Architecture Processors. Intel VT-d Technology enables multiple operating systems and

applications to run in independent partitions. A partition behaves like a virtual machine

(VM) and provides isolation and protection across partitions. Each partition is allocated

it’s own subset of host physical memory.

Integrated Trusted Platform Module (Mobile Only)

The integrated Trusted Platform Module (TPM) implementation consists of firmware,

Intel® Management Engine resources and dedicated hardware within the ICH and the

(G)MCH. The integrated TPM supports all requirements of the TPM Specification V ersion

1.2, Revision 103, as published by the Trusted Computing Group. The Integrated TPM

behaves like a discrete TPM device, and can support third party applications, as well as

Microsoft* specific functionality in the Vista* OS.

Note: Integrated TPM functionality requires a correctly configured system, including an

appropriate mobile (G)MCH with Intel Management Engine firmware, ICH9M and SPI

Flash.

Introduction

54 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

1.3 Intel® ICH9 Family High-Level Component

Differences

NOTES:

1. Contact your local Intel Field Sales Representative for currently available ICH9

components.

2. Table above shows feature difference between ICH9 components. If a feature is n ot listed

in the table it is considere d a Base feature that is included in all components.

3. SATA ports 2 and 3 are not functional in the base component.

4. ICH9 Base provides hardware support for AHCI functionality when enabled by appropriate

system configuration and software driver.

NOTES:

1. Contact your local Intel Field Sales Representative for currently available ICH9

components.

2. Table above shows feature difference between IC H9 mobile components. If a feature is not

listed in the table it is considered a Base feature that is included in all mobile compo nents.

§ §

Table 1-4. Intel® ICH9 Desktop/Server Family

Component

Name Short

Name

SATA

Ports

(#)

Intel® Matrix

Storage Technology Intel® ViivTM

Platform

Driver Support

AHCI RAID

0/1/5/10

Support

ICH9 Base ICH9 4

(Note 3) No

(Note 4) No No

ICH9 RAID ICH9R 6 Yes Yes Yes

ICH9 Digital

Home ICH9DH 6 Yes No Yes

ICH9 Digital

Office ICH9DO 6 Yes Yes No

Table 1-5. Intel® ICH9 Mobile Family

Component

Name Short Name

Intel® Matrix

Storage Technology Intel® Active

Management Technology

AHCI RAID

0/1/5/10

Support

ICH9 Mobile

Base ICH9M Yes No No

ICH9 Mobile

Enhanced ICH9M-E Yes Yes Yes

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 55

Signal Description

2 Signal Description

This chapter provides a detailed description of each signal. The signals are arranged in

functional groups according to their associated interface.

The “#” symbol at the end of the signal name indicates that the active, or asserted

state occurs when the signal is at a low voltage level. When “#” is not present, the

signal is asserted when at the high voltage level.

The following notations are used to describe the signal type:

IInput Pin

O Output Pin

OD O Open Drain Output Pin.

I/OD Bi-directional Input/Open Drain Output Pin.

I/O Bi-directional Input / Output Pin.

The “Type” for each signal is indicative of the functional operating mode of the signal.

Unless otherwise noted in Section 3.2 or Section 3.3, a signal is considered to be in the

functional operating mode after RTCRST# deasserts for signals in the RTC well, after

RSMRST# deasserts for signals in the suspend well, after PWROK asserts for signals in

the core well, and after LAN_RST# deasserts for signals in the LAN well.

Signal Description

56 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Figure 2-1. Intel® ICH9 Interface Signals Block Diagram (Desktop)

THRM#

THRMTRIP#

SYS_RESET#

RSMRST#

MCH_SYNC#

SLP_S3#

SLP_S4#

SLP_S5#

SLP_M#

S4_STATE#/GPIO26

PWROK

CLPWROK

PWRBTN#

RI#

WAKE#

SUS_STAT# / LPCPD#

SUSCLK

LAN_RST#

VRMPWRGD

PLTRST#

CK_PWRGD

STP_PCI# / GPIO15

STP_CPU# / GPIO25

AD[31:0]

C/BE[3:0]#

DEVSEL#

FRAME#

IRDY#

TRDY#

STOP#

PAR

PERR#

REQ0#

REQ1# / GPIO50

REQ2# / GPIO52

REQ3# / GPIO54

GNT0#

GNT1# / GPIO51

GNT2# / GPIO53

GNT3# / GPIO55

SERR#

PME#

PCICLK

PCIRST#

PLOCK#

PCI

Interface

LAN_RSTSYNC

GLAN_CLK

GLAN_TXp/PET6p; GLAN_TXn/PET6n

GLAN_RXp/PER6p; GLAN_RXn/PER6n

GLAN_COMPO

GLAN_COMPI

Gigabit LAN

Connect

Interface

Power

Mgnt.

Interrup t

Interface

A20M#

FERR#

IGNNE#

INIT#

INIT3_3V#

INTR

NMI

SMI#

STPCLK#

RCIN#

A20GATE

CPUPWRGD

Processor

Interface

USB

SERIRQ

PIRQ[D:A]#

PI RQ[H:E]# / GPIO[5 :2 ]

USB[11:0 ]P; USB [1 1 :0 ]N

OC0#/GP IO59; OC1#/GPIO40

OC2#/GP IO41; OC3#/GPIO42

OC4#/GP IO43; OC5#/GPIO29

OC6#/GP IO30; OC7#/GPIO31

OC8#/GP IO44; OC9#/GPIO45

OC10#/GP IO4 6; OC 11#/GPIO47

USBRBIAS

USBRBIAS#

RTCX1

RTCX2

CLK14

CLK48

SATA_CLKP, SATA_CLKN

DMI_CLKP, DMI_CLKN

RTC

Clocks

Misc.

Signals

INTVRMEN

SPKR

SRTCRST#; RTCRST#

TP[5:4]

TP[7,2:1]

TP[6,0]

LAN100_SLP

General

Purpose

I/O

GPIO[49,34:32,28:27,

20,18,16,13:12,8,0]

PWM[2:0]

TACH0/GPIO17; TACH1/GPIO1

TACH2/GPIO6; TACH3/GPIO7

SST

PECI

INTRUDER#

SMLINK[1:0]

LINKALERT#/CLGPIO4/GPIO60

MEM_LED/GPIO24; CLGPIO1/GPIO10

CLGPIO2/GPIO14;

CLGPIO5/GPIO57

GLGPIO6/SPI_CS1#/GPIO58;

WOL_EN/GPIO9

DMI[3:0]TXP, DMI[3:0]TXN

DMI[3:0]RXP, DMI[3:0]RXN

DMI_ZCOMP

DMI_IRCOMP

Direct

Media

Interface

LPC

Interface

SMBus

Interface

HDA_RST#

HDA_SYNC

HDA_BIT_CLK

HDA_SDOUT

HDA_SDIN[3:0]

Intel®

High

De fin itio n

Audio

Firm w a re

Hub

System

Mgnt.

FWH[3:0] / LAD[3:0]

FWH4 / LFRAME#

LAD[3:0] / FWH[3:0]

LFRAME# / FWH4

LDRQ0#

LDRQ1# / GPIO23

SMBDATA

SMBCLK

SMBALERT# / GPIO11

GLAN_CLK

LAN_RXD[2:0]

LAN_TXD[2:0]

LAN_RSTSYNC

LAN

Connect

Interface

SATA[5:0]TXP, SATA[5:0]TXN

SATA[5:0]RXP, SATA[5:0]RXN

SATARBIAS

SATARBIAS#

SATALED#

SATACLKREQ# / GPIO35

SATA0GP /GPIO21

SATA1GP /GPIO19

SATA2GP /GPIO36

SATA3GP /GPIO37

SATA4GP

SATA5GP

SCLOCK/GPIO22

SLOAD/GPIO38

SDATAOUT0/GPIO39

SDATAOUT1/GPIO48

Serial ATA

Interface

PCI

Express*

Interface

PETp[5:1], PETn[5:1]

PERp[5:1], PERn[5:1]

GLAN_TXp/PET6p; GLAN_TXn/PET6n

GLAN_RXp/PER6p; GLAN_RXn/PER6n

SPI

SPI_CS0#

SPI_CS1#/CLGPIO6/GPIO58

SPI_MISO

SPI_MOSI

SPI_CLK

CL_CLK0 ; CL_DATA0

CL_VREF0

CL_RST0#

Co n tro lle r

Link

Fan Speed

Control

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 57

Signal Description

Figure 2-2. Intel® ICH9 Interface Signals Block Diagram (Mobile)

AD[31:0]

C/BE[3:0]#

DEVSEL#

FRAME#

IRDY#

TRDY#

STOP#

PAR

PERR#

REQ0#

REQ1# / GPIO50

REQ2# / GPIO52

REQ3# / GPIO54

GNT0#

GNT1# / GPIO51

GNT2# / GPIO53

GNT3# / GPIO55

SERR#

PME#

PCICLK

PCIRST#

PLOCK#

PCI

Interface

GLAN_CLK

GLAN_TXp/PET6p; GLAN_TXn/PET6n

GLAN_RXp/PER6p; GLAN_RXn/PER6n

GLAN_COMPO

GLAN_COMPI

GbE

Controller

Interrupt

Interface

A20M#

FERR#

IGNNE#

INIT#

INTR

NMI

SMI#

STPCLK#

RCIN#

A20GATE

CPUPWRGD

DPSLP#

Processor

Interface

USB

SERIRQ

PIRQ[D:A]#

PIRQ[H:E]# / GPIO[5:2]

USB[11:0]P; U S B[11:0]N

OC0#/GPIO59; OC1#/GPI O40

OC2#/GPIO41; OC3#/GPI O42

OC4#/GPIO43; OC5#/GPI O29

OC6#/GPIO30; OC7#/GPI O31

OC8#/GPIO44; OC9#/GPI O45

OC10#/GP IO 46; OC11#/GPIO 4 7

USBRBIAS

USBRBIAS#

RTCX1

RTCX2

CLK14

CLK48

SATA_CLKP, SATA_CLKN

DMI_CLKP, DMI_CLKN

RTC

Clocks

Misc.

Signals

INTVRMEN

SPKR

RTCRST#; SRTCRST#

TP[12:8,3]

LAN100_SLP

General

Purpose

I/O

GPIO[56,49,28:27,20,18:17,

13, 8:6,1]

SMBDATA

SMBCLK

SMBALERT# / GPIO11

Serial ATA

Interface

SPI

SPI_CS0#

SPI_CS1#/GPIO58/CLGPIO6

SPI_MISO

SPI_MOSI

SPI_CLK

GLAN_CLK

LAN_RXD[2:0]

LAN_TXD[2:0]

LAN_RSTSYNC

LAN_PHY_PWR_CTRL/GPIO12

Platform

LAN

Connect

INTRUDER#

SMLINK[1:0]

LINKALERT#/CLGPIO4/GPIO60

MEM_LED/GPIO24; SUS_PWR_ACK/

GPIO10; AC_PRESENT/GPIO14;

WOL_EN/GPIO9; CLGPIO5/GPIO57

System

Mgnt.

SMBus

Interface

LAD[3:0] / FWH[3:0]

LFRAME# / FWH4

LDRQ0#

LDRQ1# / GPIO23

LPC

Interface

Firmware

Hub FWH[3:0] / LAD[3:0]

FWH4 / LFRAME#

DMI[3:0]TXP, DMI[3:0]TXN

DMI[3:0]RXP, DMI[3:0]RXN

DMI_ZCOMP

DMI_IRCOMP

Direct

Media

Interface

HDA_RST#

HDA_SYNC

HDA_BIT_CLK

HDA_SDOUT

HDA_SDIN[3:0]

HDA_DOCK_EN/GPIO33

HDA_DOCK_RST#/GPIO34

Intel®

High

Definition

Audio

THRM#

THRMTRIP#

SYS_RESET#

RSMRST#

MCH_SYNC#

SLP_S3#

SLP_S4#

SLP_S5#

SLP_M#

S4_STATE#/GPIO26

PWROK

CLPWROK

PWRBTN#

RI#

WAKE#

SUS_STAT# / LPCPD

SUSCLK

LAN_RST#

VRMPWRGD

PLTRST#

CK_PWRGD

PMSYNC#/GPIO0

CLKRUN#

STP_PCI#

STP_CPU#

BATLOW#

DPRSLPVR/GPIO16

DPRSTP#

Power

Mgnt.

SATA[5:4,1:0]TXP, SATA[5:4,1:0]TXN

SATA[5:4,1:0]RXP, SA T A[5:4,1:0]RXN

SATARBIAS

SATARBIAS#

SATALED#

SATACLKREQ# / GPIO35

SATA0GP /GPIO21; SATA1GP /GPIO19

SATA4GP /GPIO36; SATA5GP /GPIO37

SCLOCK/GPIO22

SLOAD/GPIO38

SDATAOUT0/GPIO39

SDATAOUT1/GPIO48

PCI

Express*

Interface

PETp[ 5:1 ], PETn[5:1]

PERp [5 :1], PERn[5:1]

GLAN_TXp/PET6p; GLAN_TXn/PET6n

GLAN_RXp/PER6p; GLAN_RXn/PER6n

CL_CLK[1:0] ; CL_DAT A[1:0]

CL_VREF[1:0]

CL_RST[1:0]#

Controller

Link

Serial

ATA

Interface

Signal Description

58 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.1 Direct Media Interface (DMI) to Host Controller

Table 2-1. Direct Media Interface Signals

Name Type Description

DMI0TXP,

DMI0TXN ODi rect Media Interface Differential Transmit Pair 0

DMI0RXP,

DMI0RXN IDi rec t Media Interface D iff erential Receive Pair 0

DMI1TXP,

DMI1TXN ODi rect Media Interface Differential Transmit Pair 1

DMI1RXP,

DMI1RXN IDi rec t Media Interface D iff erential Receive Pair 1

DMI2TXP,

DMI2TXN ODi rect Media Interface Differential Transmit Pair 2

DMI2RXP,

DMI2RXN IDi rec t Media Interface D iff erential Receive Pair 2

DMI3TXP,

DMI3TXN ODi rect Media Interface Differential Transmit Pair 3

DMI3RXP,

DMI3RXN IDi rec t Media Interface D iff erential Receive Pair 3

DMI_ZCOMP IImpedance Compensation Input: Determines DMI input

impedance.

DMI_IRCOMP OImpedance/Current Compensation Output: Determines DMI

output impedance and bias current.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 59

Signal Description

2.2 PCI Express*

2.3 LAN Connect Interface

Table 2-2. PCI Express* Signals

Name Type Description

PETp1, PETn1 OPCI Express* Differential Transmit Pair 1

PERp1, PERn1 IPCI Express Differential Receive Pair 1

PETp2, PETn2 OPCI Express Differential Transmit Pair 2

PERp2, PERn2 IPCI Express Differential Receive Pair 2

PETp3, PETn3 OPCI Express Differential Transmit Pair 3

PERp3, PERn3 IPCI Express Differential Receive Pair 3

PETp4, PETn4 OPCI Express Differential Transmit Pair 4

PERp4, PERn4 IPCI Express Differential Receive Pair 4

PETp5, PETn5 OPCI Express Differential Transmit Pair 5

PERp5, PERn5 IPCI Express Differential Receive Pair 5

PETp6/GLAN_TXp,

PETn6/GLAN_TXn OPCI Express Differential Transmit Pair 6: The differential pair

will functio n as the Gigabit LAN Con nect Interface transmit pair

when the integrated Gigabit LAN controller is enabled.

PERp6/GLAN_RXp,

PERn6/GLAN_RXn IPCI Express Differential Receive Pair 6: The differential pair

will functio n as the Gigabit LAN Con nect Interface re ceive pair

when the integrated Gigabit LAN controller is enabled.

Table 2-3. LAN Connect Interface Signals

Name Type Description

GLAN_CLK I

Gigabit LAN Input Clock: Clock driven by the Platform LAN Connect

device. The frequency will vary depending on link speed.

NOTE: The clock is shared between the LAN Connect Interface and the

Gigabit LAN Connect Interface.

LAN_RXD[2:0] IReceived Da ta : The Platform LAN Connect device uses these signal s

to transfer data and control information to the integrated LAN

controller. These signal s have integrated weak pull-up resistors.

Signal Description

60 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.4 Gigabit LAN Connect Interface

LAN_TXD[2:0] OTransmit Data: The integrated LAN controller uses these signals to

transfer data and control information to the Platform LAN Connect

component.

LAN_RSTSYNC O

LAN Reset/Sync: This is the res e t/ syn c sign al from th e LAN Conne c t

Interface to the physical device. The Platform LAN Connect device’s

Reset and Sync signals are multip lexed onto this pin.

NOTE: The signal is shared bet w een LAN Connect Interface and

Gigabit LAN Connect Interface.

LAN_PHY_PW

R_CTRL (Mobile

Only) / GPIO12 O

LAN PHY Power Control: This signal may optionally be connected to a switch

to turn 3.3V PHY power off when LAN is disabled for additional power savings.

This capability is configured in the NVM. When using an 82567 PHY solution, the

LAN_PHY_PWR_CTRL signal should be connected to the PHY’s LAN_DISABLE_N

pin for a hardware based LAN disable mechanism.

Signal can instead be used as GPIO12.

Table 2-4. Gigabit LAN Connect Interface Signals

Name Type Description

GLAN_CLK I

Gigabit LAN Input Clock: Clock driven by the Platform LAN

Connect device. The frequency will vary depending on link

speed.

NOTE: The clock is shared between the LAN Connect Interface

and the Gigabit LAN Connect Interface.

GLAN_TXp/PET6p;

GLAN_TXn/PET6n OGigabit LAN Differential Transmit Pair. Can be instead used

as PCI Express port 6 differential transmit pair.

GLAN_RXp/PER6p;

GLAN_RXn/PER6n IGigabit LAN Differential Receive Pair. Can be instead used

as PCI Express port 6 differential receive pair.

GLAN_COMPO OImpedance Compensation Output pad: Determines Gigabit

LAN Connect Interface output impedance and bias current.

GLAN_COMPI IImpedance Compensation Input pad: Determines Gigabit

LAN Connect Interface input impedance.

LAN_RSTSYNC O

LAN Reset/Sync: This is the reset /sync signal from the Gigabit

LAN interface to the physical device. The Platform LAN Connect

device’s Reset and Sync signals are multiplexed onto this pin.

NOTE: The signal is shared between LAN Connect Interface and

Gigabit LAN Connect Interface.

Table 2-3. LAN Connect Interface Signals

Name Type Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 61

Signal Description

2.5 Firmware Hub Interface

Table 2-5. Firmware Hub Interface Signals

Name Type Description

FWH[3:0] /

LAD[3:0] I/O Firmware Hub Signals. These signals are multiplexed with the LPC

address signals.

FWH4 /

LFRAME# OFirmware Hub Signals. This signal is multiplexed with th e LPC

LFRAME# signal.

INIT3_3V#

(Desktop

Only) OInitialization 3.3 V: This is the ide ntical 3.3 V copy of INIT# intended

for Firmware Hub.

Signal Description

62 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.6 PCI Interface

Table 2-6. PCI Interface Signals (Sheet 1 of 3)

Name Type Description

AD[31:0] I/O

PCI Address/Data: AD[31:0] is a multiplexed address and data

bus. During the first clock of a transaction, AD[31:0] contain a

physical address (32 bits). During subsequent clocks, AD[31:0]

contain data. The Intel® ICH9 will drive all 0s on AD[31:0] during

the address phase of all PCI Special Cycles.

C/BE[3:0]# I/O

Bus Command and Byte Enables: The command and byte enable

signals are multiplexed on the same PCI pins. During the address

phase of a transaction,

C/BE[3:0]# define the bus command. During the data phase C/

BE[3:0]# define the Byte Enables.

All command encodings not shown are reserved. The ICH9 does not

decode reserved val ues, and therefore will not respond if a PCI

master generates a cycle using one of th e reserved values.

DEVSEL# I/O

Device Select: The ICH9 asserts DEVSEL# to claim a PCI

transaction. As an output, the ICH9 asserts DEVSEL# when a PCI

master peripheral attempts an access to an internal ICH9 address

or an address destined for DMI (main memory or graphics). As an

input, DEVSEL# indicates the respon se to an ICH9-initiated

transaction on the PCI bus. DEVSEL# is tri-stated from the leading

edge of PLTRST#. DEVSEL# remains tri-stated by the ICH9 until

driven by a target device.

FRAME# I/O

Cycle Frame: The current initiator drives FRAME# to indicate the

beginning and duration of a PCI transaction. While the initiator

asserts FRAME#, data transfers continue. When the initiator

negates FRAME#, the transaction is in the final data phase.

FRAME# is an input to the ICH9 when the ICH9 is the target, and

FRAME# is an output from the ICH9 when the ICH9 is the initiator.

FRAME# remains tri-stated by the ICH9 until driven by an initiator.

C/BE[3:0]# Command Type

0000b Interrupt Acknowledge

0001b Special Cycle

0010b I/O Read

0011b I/O Write

0110b Memory Read

0111b Memory Write

1010b Configuration Read

1011b Configuration Write

1100b Memory Read Multiple

1110b Memory Read Line

1111b Memory Write and Invalidate

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 63

Signal Description

IRDY# I/O

Initiator Ready: IRDY# indicates the ICH9's ability , as an initiator,

to complete the current data phase o f the transaction. It is used in

conjunction with TRDY#. A data phase is completed on any clock

both IRDY# and TRDY# are sampled asserted. During a write,

IRDY# indicates the ICH9 has valid data present on AD[31:0].

During a read, it indicates the ICH9 is prepared to latch data.

IRDY# is an input to the ICH9 when the ICH9 is the target and an

output from the ICH9 when the ICH9 is an initiat or. IRDY# remains

tri-stated by the ICH9 until driven by an initiator.

TRDY# I/O

Target Ready: TRDY# indicates the ICH9's ability as a target to

complete the curre nt data phase of the transaction. TRDY# is used

in conjunction with IRDY#. A data phase is completed when both

TRDY# and IRDY# are sampled asserted. During a read, TRDY#

indicates that the ICH9, as a target, has placed valid data on

AD[31:0]. During a write, TRDY# indicates the ICH9, as a target is

prepared to latch data. TRDY# is a n input to the ICH9 when the

ICH9 is the initiator and an output from the ICH9 when the ICH9 is

a target. TRDY# is tri-stated from the leading edge of PLTRST#.

TRDY# remains tri-stated by the ICH9 until driven by a target.

STOP# I/O

Stop: STOP# indicates that th e ICH9, as a target, is requestin g the

initiator to stop the current transaction. STOP# causes the ICH9, as

an initiator, to stop the current transaction. STOP# is an output

when the ICH9 is a target and an input when the ICH9 is an

initiator.

PAR I/O

Calculated/Checked Parity: PAR uses “even” parity calculated on

36 bits, AD[31:0] plus C/BE[3:0]#. “Even” parity means that the

ICH9 counts the n umber of ones within the 36 bits plus P AR and th e

sum is always even. The ICH9 always calculates PAR on 36 bits

regardless of the valid byte enables. The ICH9 generates PAR for

address and data phases and only ensures PAR to be valid one PCI

clock after the corresponding address or data phase. The ICH9

drives and tri-states PAR identically to the AD[31:0] lines except

that the ICH9 delays P AR by exactly one PCI clock. PAR is an output

during the address phase (delayed one clock) for all ICH9 initiated

transactions. PAR is an output during the data phase (delayed one

clock) when the ICH9 is the init iator of a PCI write transaction, and

when it is the target of a read transaction. ICH9 checks parity when

it is the target of a PCI write transaction. If a parity error is

detected, the ICH9 will set the appropriate internal status bits, and

has the option to generate an NMI# or SMI#.

PERR# I/O

Parity Error: An external PCI device drives PERR# when it receives

data that has a parity error. The ICH9 drives PERR# when it detects

a parity error. The ICH9 can either generate an NMI# or SMI# upon

detecting a parity error (either detected internally or reported via

the PERR# signal).

REQ0#

REQ1#/ GPIO50

REQ2#/ GPIO52

REQ3#/ GPIO54

IPCI Requests: The ICH9 supports up to 4 masters on the PCI bus.

REQ[3:1]# pins can instead be used as GPIO.

Table 2-6. PCI Interface Signals (Sheet 2 of 3)

Name Type Description

Signal Description

64 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.7 Serial ATA Interface

GNT0#

GNT1#/ GPIO51

GNT2#/ GPIO53

GNT3#/ GPIO55

PCI Grants: The ICH9 supports up to 4 master s on the PCI bus.

GNT[3:1]# pins can instead be used as GPIO.

Pull-up resistors are not required on these signals. If pull-ups are

used, they should be tied to the Vcc3_3 power rail.

NOTE: GNT[3:0]# are sampled as a functional strap. See

Section 2.24.1 for details.

PCICLK I

PCI Clock: This is a 33 MHz clock. PCICLK provides timing for all

transactions on the PCI Bus.

Note: (Mobile Only) This clock does n ot stop based on STP_PCI#

signal. PCI Clock only stops based on SLP_S3#.

PCIRST# O

PCI Reset: This is the Secondary PCI Bus reset signal. It is a

logical OR of the primary int erface PLTRST# signal and the state of

the Secondary Bus Reset bit of the Bridge Control register

(D30:F0:3Eh, bit 6).

PLOCK# I/O

PCI Lock: This signal indicates an ex clusive bus operation and may

require multiple transactions to complete. ICH9 asserts PLOCK#

when it performs non-exclusive transactions on the PCI bus.

PLOCK# is ignored when PCI masters are granted the bus in

desktop configurations.

Note: In mobile configuration, devices on the PCI bus (other than

the ICH9) are not permitted to assert the PLOCK# signal.

SERR# I/OD System Error: SERR# can be pulsed active by any PCI device that

detects a system error condition. Upon sampling SERR# active, the

ICH9 has the ability to generate an NMI, SMI#, or interrupt.

PME# I/OD

PCI Power Management Event: PCI peripherals drive PME# to

wake the system from low-power states S1–S5. PME# assertion can

also be enabled to generate an SCI from the S0 state. In some

cases the ICH9 m ay drive PME# active due to an internal wake

event. T he ICH9 wil l not dri ve PME # high, but it will be pulled up to

VccSus3_3 by an internal pull-up resistor.

Table 2-7. Serial ATA Interface Signals (Sheet 1 of 4)

Name Type Description

SATA0TXP

SATA0TXN O

Serial ATA 0 Differential Transmit Pairs: These are outbound

high-speed differential signals to Port 0.

In compatible mode, SATA Port 0 is the primary master of SATA

Controller 1.

SATA0RXP

SATA0RXN I

Serial ATA 0 Differential Receive Pair: These are inbound high-

speed differential signals from Port 0.

In compatible mode, SATA Port 0 is the primary master of SATA

Controller 1.

SATA1TXP

SATA1TXN O

Serial ATA 1 Differential Transmit Pair: These are outbound

high-speed differential signals to Port 1.

In compatible mode, SATA Port 1 is the secondary master of SATA

Controller 1.

Table 2-6. PCI Interface Signals (Sheet 3 of 3)

Name Type Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 65

Signal Description

SATA1RXP

SATA1RXN I

Serial ATA 1 Differential Receive Pair: These are inbound high-

speed differential signals from Port 1.

In compatible mode, SATA Port 1 is the seco ndary master of SATA

Controller 1

SATA2TXP

SATA2TXN

(ICH9R, ICH9DH,

ICH9DO Only)

Serial ATA 2 Differential Transmit Pair: These are outbound

high-speed differential signals to Port 2.

In compatible mode, SATA Port 2 is the primary slave of SATA

Controller 1.

NOTE: This port is not functional in the Desktop ICH9 Base

component.

SATA2RXP

SATA2RXN

(ICH9R, ICH9DH,

ICH9DO Only)

Serial ATA 2 Differential Receive Pair: These are inbound high-

speed differential signals from Port 2.

In compatible mode, SATA Port 2 is the primary slave of SATA

Controller 1.

NOTE: This port is not functional in the Desktop ICH9 Base

component.

SATA3TXP

SATA3TXN

(ICH9R, ICH9DH,

ICH9DO Only)

Serial ATA 3 Differential Transmit Pair: These are outbound

high-speed differential signals to Port 3.

In compatible mode, SATA Port 3 is the secondary slave of SATA

Controller 1.

NOTE: This port is not functional in the Desktop ICH9 Base

component.

SATA3RXP

SATA3RXN

(ICH9R, ICH9DH,

ICH9DO Only)

Serial ATA 3 Differential Receive Pair: These are inbound high-

speed differential signals from Port 3.

In compatible mode, SATA Port 3 is the secondary slave of SATA

Controller 1.

NOTE: This port is not functional in the Desktop ICH9 Base

component.

SATA4TXP

SATA4TXN O

Serial ATA 4 Differential Transmit Pair: These are outbound

high-speed differential signals to Port 4.

In compatible mode, SATA Port 4 is the primary master of SATA

Controller 2.

SATA4RXP

SATA4RXN I

Serial ATA 4 Differential Receive Pair: These are inbound high-

speed differential signals from Port 4.

In compatible mode, SATA Port 4 is the primary master of SATA

Controller 2

SATA5TXP

SATA5TXN O

Serial ATA 5 Differential Transmit Pair: These are outbound

high-speed differential signals to Port 5.

In compatible mode, SATA Port 5 is the seco ndary master of SATA

Controller 2.

SATA5RXP

SATA5RXN I

Serial ATA 5 Differential Receive Pair: These are inbound high-

speed differential signals from Port 5.

In compatible mode, SATA Port 5 is the seco ndary master of SATA

Controller 2.

SATARBIAS OSerial ATA Resistor Bias: This is an analog connection point for

an external resistor to ground.

SATARBIAS# ISerial ATA Resistor Bias Complement: This is an analog

connection point for an external resistor to ground.

Table 2-7. Serial ATA Interface Signals (Sheet 2 of 4)

Name Type Description

Signal Description

66 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

SATA0GP /

GPIO21 I

Serial ATA 0 General Purpose: This is an input pin which can be

configured as an interlock switch corresponding to SATA Port 0.

When used as an interlock switch status indication, this signal

should be drive to ‘0’ to indicate that the switch is closed and to ‘1’

to indicate that the switch is open.

If interlock switches are not required, this pin can be configure d as

GPIO21.

SATA1GP /

GPIO19 I

Serial ATA 1 General Purpose: Same function as SATA0GP,

except for SATA Port 1.

If interlock switches are not required, this pin can be configure d as

GPIO19.

SATA2GP /

GPIO36

(ICH9R, ICH9DH,

ICH9DO Only)

Serial ATA 2 General Purpose: Same function as SATA0GP,

except for SATA Port 2.

If interlock switches are not required, this pin can be configure d as

GPIO36.

NOTE: This signal can also be used as GPIO36 for Desktop

components. This signal can only be used as GPIO3 6 in the

Desktop ICH9 Base component.

SATA3GP /

GPIO37

(ICH9R, ICH9DH,

ICH9DO Only)

Serial ATA 3 General Purpose: Same function as SATA0GP,

except for SATA Port 3.

If interlock switches are not required, this pin can be configure d as

GPIO37.

NOTE: This signal can also be used as GPIO37 for Desktop

components. This signal can only be used as GPIO3 7 in the

Desktop ICH9 Base component.

SATA4GP /

GPIO36 (Mobile

Only) I

Serial ATA 4 General Purpose: Same function as SATA0GP,

except for SATA Port 4.

Note: This signal can also be used as GPIO36 for Mobile

components.

SATA5GP /

GPIO37 (Mobile

Only) I

Serial ATA 5 General Purpose: Same function as SATA0GP,

except for SATA Port 5.

Note: This signal can also be used as GPIO37 for Mobile

components.

SATALED# OD O

Serial ATA LED: This signal is an open-drain output pin driven

during SATA command activity. It is to be connected to external

circuitry that can provide the current to driv e a platform LED. When

active, the LED is on. When tri-stated, the LED is off. An external

pull-up resistor to Vcc3_3 is required.

NOTE: This signal is sampled as a functional strap. See

Section 2.24.1 for details.

SATACLKREQ#/

GPIO35 OD O

Serial ATA Clock Request: This signal is an open-drain output pin

when configured as SATACLKREQ#. It is used to connect to the

system clock chip. When active, request for SATA Clock running is

asserted. When tri-stated, it tells the Clock Chip that SATA Clock

can be stopped. An external pull-up resistor is required.

Table 2-7. Serial ATA Interface Signals (Sheet 3 of 4)

Name Type Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 67

Signal Description

2.8 LPC Interface

SCLOCK/GPIO22 OD O

SGPIO Reference Clock: The SATA controller uses rising edges of

this clock to transmit serial data, and the target uses the falling

edge of this clock to latch data.

If SGPIO interface is not used, this signal can be used as a GPIO.

SLOAD/GPIO38 OD O

SGPIO Load: The controller drives a ‘1’ at the rising edge of

SCLOCK to indicate either the start or end of a bit stream. A 4-bit

vendor specific pattern will be transmitted right after the signal

assertion.

If SGPIO interface is not used, this signal can be used as a GPIO.

SDATAOUT0/

GPIO39

SDATAOUT1/

GPIO48

OD O SGPIO Dataout: Driven by the controller to indicate the drive

status in the following sequence: drive 0, 1, 2, 3, 4, 5, 0, 1, 2...

If SGPIO interface is not used, the signals can be used as GPIO.

Table 2-8. LPC Interface Sig nals

Name Type Description

LAD[3:0] /

FWH[3:0] I/O LPC Multiplexed Command, Address, Data: For LAD[3:0], internal

pull-ups are provided.

LFRAME# /

FWH4 OLPC Frame: LFRAME# indicates the start of an LPC cycle, or an abort.

LDRQ0#,

LDRQ1# /

GPIO23 I

LPC Serial DMA/Master Request Inputs: LDRQ[1:0]# are used to

request DMA or bus maste r a ccess. These signal s are typically connected

to an external Super I/O device. An internal pull-up resistor is provided on

these signals.

LDRQ1# may optionally be used as GPIO.

Table 2-7. Serial ATA Interface Signals (Sheet 4 of 4)

Name Type Description

Signal Description

68 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.9 Interrupt Interface

Table 2-9. Interrupt Signals

Name Type Description

SERIRQ I/OD Serial Interrupt Reque st: This pin implements the serial interrupt

protocol.

PIRQ[D:A]# I/OD

PCI Interrupt Requests: In non-APIC mode the PIRQx# signals can

be routed to interrupts 3, 4, 5, 6, 7, 9, 10, 11, 12, 14 or 15 as

described in Section 5.8.6. Each PIRQx# line has a separate Route

Control register.

In APIC mode, these signals are connected to the internal I/O APIC in

the following fashion: PIRQA# is connected to IRQ16, PIRQB # to

IRQ17, PIRQC# to IRQ18, and PIRQD# to IRQ19. This frees the

legacy interrupts.

PIRQ[H:E]# /

GPIO[5:2] I/OD

PCI Interrupt Requests: In non-APIC mode the PIRQx# signals can

be routed to interrupts 3, 4, 5, 6, 7, 9, 10, 11, 12, 14 or 15 as

described in Section 5.8.6. Each PIRQx# line has a separate Route

Control register.

In APIC mode, these signals are connected to the internal I/O APIC in

the following fashion: PIRQE# is connected to IRQ20, PIRQF# to

IRQ21, PIRQG# to IRQ22, and PIRQH# to IRQ23. This frees the

legacy interrupts. If not needed for interrupts, these signals can be

used as GPIO.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 69

Signal Description

2.10 USB Interface

Table 2-10. USB Interface Signals

Name Type Description

USBP0P,

USBP0N,

USBP1P,

USBP1N

I/O

Universal Serial Bus Port [1 :0 ] Differential: These differential

pairs are used t o t ransmit Data/Address/Command signals for ports

0 and 1. These ports can be routed to UHCI controller #1 or the

EHCI controller #1.

NOTE: No external resistors are required on these signals. The

Intel® ICH9 integrates 15 kΩ pull-downs and provides an

output driver impedance of 45 Ω which requires no external

series resistor.

USBP2P,

USBP2N,

USBP3P,

USBP3N

I/O

Universal Serial Bus Port [3 :2 ] Differential: These differential

pairs are used to tr ansmit data/address/command si gnals for ports 2

and 3. These ports can be routed to UHCI controller #2 or the EHCI

controller #1.

NOTE: No external resistors are required on these signals. The ICH9

integrates 15 kΩ pull-downs and provides an output driver

impedance of 45 Ω which requires no external series resistor.

USBP4P,

USBP4N,

USBP5P,

USBP5N

I/O

Universal Serial Bus Port [5 :4 ] Differential: These differential

pairs are used t o t ransmit Data/Address/Command signals for ports

4 and 5. These ports can be routed to UHCI controller #3 or the

EHCI controller #1.

NOTE: No external resistors are required on these signals. The ICH9

integrates 15 kΩ pull-downs and provides an output driver

impedance of 45 Ω which requires no external series resistor.

USBP6P,

USBP6N,

USBP7P,

USBP7N

I/O

Universal Serial Bus Port [7 :6 ] Differential: These differential

pairs are used t o t ransmit Data/Address/Command signals for ports

6 and 7. These ports can be routed to UHCI controller #4 or the

EHCI controller #2.

NOTE: No external resistors are required on these signals. The ICH9

integrates 15 kΩ pull-downs and provides an output driver

impedance of 45 Ω which requires no external series resistor.

USBP8P,

USBP8N,

USBP9P,

USBP9N

I/O

Universal Serial Bus Port [9 :8 ] Differential: These differential

pairs are used t o t ransmit Data/Address/Command signals for ports

8 and 9. These ports can be routed to UHCI controller #5 or the

EHCI controller #2.

NOTE: No external resistors are required on these signals. The ICH9

integrates 15 kΩ pull-downs and provides an output driver

impedance of 45 Ω which requires no external series resistor.

Signal Description

70 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

USBP10P,

USBP10N,

USBP11P,

USBP11N

I/O

Universal Serial Bus Port [1 1: 1 0] Differential: These

differential pairs are used to tr ansmit Data/Address/Command

signals for ports 10 and 11. These ports can be routed to UHCI

controller #6 or the EHCI controller #2. These ports can be

optionally routed to EHCI Controller #1 when bit 0 RCBA 35F0h is

set.

NOTE: No external resistors are requ ired on these signals. The ICH9

integrates 15 kΩ pull-downs and provides an output driver

impedance of 45 Ω which requires no external series resistor.

OC0# / GPIO59

OC1# / GPIO40

OC2# / GPIO41

OC3# / GPIO42

OC4# / GPIO43

OC5# / GPIO29

OC6# / GPIO30

OC7# / GPIO31

OC8# / GPIO44

OC9# / GPIO45

OC10# / GPIO46

OC11# / GPIO47

Overcurrent Indicators: These signals set correspon ding bits in

the USB controllers to indic ate that an overcurrent condition has

occurred.

OC[11:0]# may optionally be used as GPIOs.

NOTE: OC[11:0]# are not 5 V tolerant.

USBRBIAS OUSB Resistor Bias: Analog connection point for an external

resistor. Used to set transmit currents and internal load resistors.

USBRBIAS# IUSB Resistor Bias Complement: Analog connection point for an

external resistor. Used to set transmit currents and internal load

resistors.

Table 2-10. USB Interface Signals

Name Type Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 71

Signal Description

2.11 Power Management Interface

Table 2-11. Power Management Interface Signals (Sheet 1 of 3)

Name Type Description

PLTRST# O

Platform Reset: The Intel® ICH9 asserts PLTRST# to reset devices

on the platform (e.g., SIO, FWH, LAN, (G)MCH, TPM, etc.). The ICH9

asserts PL TRST# during power-up and when S/W initiates a hard reset

sequence through the Reset Control register (I/O Register CF9h). The

ICH9 drives PLTRST# inactive a minimum of 1 ms after both PWROK

and VRMPWRGD are driven high. The ICH9 drives PLTRST# active a

minimum of 1 ms when initiated through the Reset Control register

(I/O Register CF9h).

NOTE: PLTRST# is in the VccSus3_3 well.

THRM# IThermal Alarm: Active low signal generated by external hardw are to

generate an SMI# or SCI.

THRMTRIP# I

Thermal Trip: When low, th is signal indicates that a thermal t rip from

the processor occurred, and the ICH9 will immediately transition to a

S5 state. The ICH9 will not wai t for the processor stop grant cycle

since the proces sor has overheated.

SLP_S3# OS3 Sleep Control: SLP_S3# is for power plane control. This signal

shuts off power to all non-critical systems when in S3 (Suspend To

RAM), S4 (Suspend to Disk), or S5 (Soft Off) states.

SLP_S4# O

S4 Sleep Control : SLP_S4# is for power plane control. This signal

shuts power to all non-critical systems when in the S4 (Suspend to

Disk) or S5 (Soft O ff) state.

NOTE: This pin must be used to control the DRAM power in order to

use the ICH9’s DRAM power-cycling feature. Refer to

Chapter 5.13.11.2 for details.

NOTE: In a system with Intel AMT or ASF support, this signal should

be used to control the DRAM power. In M1 state (where the

host platform is in S3–S5 states and the manageability sub-

system is running) the signal is forced high along with SLP_M#

in order to properly maintain power to the DIMM used for

manageability sub-system.

SLP_S5# OS5 Sleep Control: SLP_S5# is for power plane control. This signal is

used to shut power off to all non-critical systems when in the S5 (Soft

Off) states.

SLP_M# O

Manageability Sleep State Co ntrol: This signal is used to control

power planes to the Intel® AMT or ASF sub-system. If no Intel AMT or

ASF Management Engine firmware is present, SLP_M# will have the

same timings as SLP_S3#.

S4_STATE# /

GPIO26 O

S4 State Indication: This signal asserts low when th e host platform

is in S4 or S5 state. In platforms where the management engine is

forcing the SLP_S4# high along with SLP_M#, this si gnal can be used

by other devices on the board to know when the host platform is

below the S3 state.

Signal Description

72 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

PWROK I

Power OK: When asserted, PWROK is an indication to the ICH9 that all

power rails have been stable for 99 ms and that PCICLK has been

stable for 1 ms. PWROK can be driven asynchronously. When PWROK

is negated, the ICH9 asserts PLTRST#.

NOTE:

1. PWROK must deassert for a minimum of three RTC clock

periods in order for the ICH9 to fully reset the power and

properly generate the PLTRST# output.

2. PWROK must not glitch, even if RSMRST# is l ow.

CLPWROK I

Controller Link Power OK: When asserted, indicates that power to

the Controller Link subsystem (MCH, ICH, etc.) is stable and tells the

ICH to deassert CL_RST# to the MCH.

NOTES:

1. CLPWROK must not assert before RSMRST# deasserts.

2. CLPWROK must not assert after PWROK asserts.

PWRBTN# I

Power Button: The P ower Button will cause SMI# or SCI to indicate a

system request to go to a sleep state. If the system is already in a

sleep state, this signal will cause a wake event. If PWRBTN# is pressed

for more than 4 seconds, this will cause an unconditional transition

(power button override) to the S5 state. Override will occur even if the

system is in the S1-S4 states. This signal has an internal pull-up

resistor and has an internal 16 ms de-bounce on the input.

RI# IRing Indicate: This signal is an input from a modem. It can be

enabled as a wake event, and this is preserved across power failures.

SYS_RESET# ISystem Reset: This pin forces an internal reset after being

debounced. The ICH9 will reset immediately if the SMBus is idle;

otherwise, it will wait up to 25 ms ± 2 ms for the SMBus to idle before

forcing a reset on the system.

RSMRST# I

Resume Well Reset: This signal is used for resetting the resume

power plane logic. This signal must be asserted for at least 10 ms after

the suspend power wells are valid. When deasserted, this signal is an

indication that the suspend power wells are stable.

LAN_RST# I

LAN Reset: When asserted, the internal LAN controller is in reset.

This signal must be asserted until the LAN power wells (VccLAN3_3

and VccLAN1_05) and VccCL3_3 power well are valid. When

deasserted, t his signal is an indication that the LAN powe r wells are

stable.

NOTES:

1. LAN_RST# mu st not deassert before RSMRST# deasserts

2. LAN_RST# must not deassert after PWROK asserts.

3. LAN_RST# mu st not deassert until 1ms after the LAN power

wells (VccLAN3_3 and VccLAN1_05 and VccCL3_3 power well

are valid.

4. If integrated LAN is not used LAN_RST# can be tied to Vss.

5. LAN_RST# must as se rt a mi ni mu m of 20 ns before LAN po wer

rails become inactive.

WAKE# IPCI Express* Wake Event: Sideband wake signal on PCI Express

asserted by components requesting wake up.

MCH_SYNC# IMCH SYNC: This input is inter n ally ANDed with the PWROK in put.

Connect to the ICH_SYNC# output of (G)MCH.

Table 2-11. Power Management Interface Signals (Sheet 2 of 3)

Name Type Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 73

Signal Description

SUS_STAT# /

LPCPD# O

Suspend Status: This signal is asserted by the ICH9 to indicate that

the system will be entering a low power state soon. This can be

monitored by devices with memory that need to switch from normal

refresh to suspend refresh mode. It can also be used by other

peripherals as an indication that they should isolate their outputs that

may be going to powered-off planes. This signal is called LPCPD# on

the LPC interface.

SUSCLK OSuspend Clock: This clock is an output of the R TC gener ator circuit t o

use by other chips for refresh clock.

VRMPWRGD I

VRM Power Good: This signal should be connected to the processor’ s

VRM Power Good signifying the VRM is stable. This signal is internally

ANDed with the PWROK input.

This signal is in the suspend well.

CK_PWRGD OClock Generator Power Good: i ndicates to the clock generator

when the main power well is valid. This signal is asserted high when

both SLP_S3# and VRMPWRGD are high.

PMSYNC#

(Mobile Only) /

GPIO0 OPower Management Sync: When asserted, it signals the MCH to

deassert CPUSLP# pin when exiting out of C5 or C6.

Signal may also be used as a GPIO.

CLKRUN#

(Mobile On ly)/

GPIO32

(Desktop Only)

I/O PCI Clock Run: Used to support PCI CLKRUN protocol. Connects to

peripherals that need to request clock restart or prevention of clock

stopping.

STP_PCI# /

GPIO15

(Desktop Only) O

Stop PCI Clock: This signal is an output to the external clock

generator for it to turn off the PCI clock. It is used to support PCI

CLKRUN# protocol on mobile platforms.

In Sx, this pin is also used to communicate the host clock frequency

select for Management Engine operation in order to support Moff/Sx to

M1/Sx transitions in a mobile Intel® AMT or ASF enabled system.

This signal is used as a GPIO in desktop platforms.

STP_CPU# /

GPIO25

(Desktop Only) O

Stop CPU Clock: This signal is an output to the external clock

generator for it to turn off the processor clock. It is used to support

the C3 state on mobile platforms.

In Sx, this pin is also used to communicate the host clock frequency

select for Management Engine operation in order to support Moff/Sx to

M1/Sx transitions in a mobile Intel® AMT or ASF enabled system.

This signal is used as a GPIO in desktop platforms.

BATLOW#

(Mobile Only) /

TP0

(Desktop Only)

Battery Low: This signal is an input from the battery to indic a te that

there is insufficient power to boot the system. A ssertion will prevent

wake from S3–S5 state. This signal can also be enabled to cause an

SMI# when asserted.

DPRSLPVR

(Mobile Only) /

GPIO16 O

Deeper Sleep - Voltage Regulator: This signal is used to lower the

voltage of the VRM during the C4 state. When the signal is high, the

voltage regulator outputs the lower “Deeper Sl eep” vol tage. When low

(default), the voltage regulator outputs the higher “Normal” volt age.

DPRSTP#

(Mobile Only) /

TP1

(Desktop Only)

ODeeper Stop: This is a copy of the DPRSLPVR and it is active low.

Table 2-11. Power Management Interface Signals (Sheet 3 of 3)

Name Type Description

Signal Description

74 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.12 Processor Interface

Table 2-12. Processor Interface Signals (Sheet 1 of 2)

Name Type Description

A20M# OMask A20: A20M# will go active based on either setting the

appropriate bit in the Port 92h register, or based on the A20GATE

input being active.

FERR# I

Numeric Coprocessor Error: This signal is tied to the coprocessor

error signal on the processor. FERR# is only used if the ICH9

coprocessor error reporting function is enabled in the OIC.CEN

asserted, the ICH9 generates an internal IRQ13 to its interrupt

controller unit. It is also used to gate the IGNNE# signal to ensure

that IGNNE# is not asserted to the pr ocessor unl ess FERR # is activ e.

FERR# requires an external weak pull-up to ensu re a high le vel when

the coprocessor error function is disabled.

NOTE: FERR# can be used in some states for notification by the

processor of pending interrupt events. This functionality is

independent of the OIC regi st er bi t se tting.

IGNNE# O

Ignore Numeric Error: This signal is connected to the ignore error

pin on the processor. IGNNE# is only used if the ICH9 coprocessor

error reporting function is enabled in the OIC.CEN register (Chipset

Config Registers:Off set 31FFh: bit 1) . If FERR# is ac tiv e, indic ating a

coprocessor error, a write to the Coprocessor Error register (I/O

asserted until FERR# is negated. If FERR# is not asserted when the

Coprocessor Error register is written, the IGNNE# signal is not

asserted.

INIT# OInitialization: INIT# is asserted by the ICH9 for 16 PCI clocks to

reset the processor. ICH9 can be configured to support processor

Built In Self Test (BIST).

INTR OCPU Interrupt: INTR is asserted by the ICH9 to signal to the

processor that an interrupt request is pending and needs to be

serviced. It is an asynchronous output and normally driven low.

NMI O

Non-Maskable Interrupt: NMI is used to force a non-Maskable

interrupt to the processor. The ICH9 can generate an NMI when either

SERR# is asserted or IOCHK# goes active via the SERIRQ# stream.

The processor detects an NMI when it detects a rising edge on NMI.

NMI is reset by setting the corresponding NMI source enable/disable

bit in the NMI Status and Control register (I/O Register 61h).

SMI# OSystem Management Interrupt: SMI# is an active low output

synchronous to PCICLK. It is asserted by the ICH9 in response to one

of many enabled hardware or software events.

STPCLK# O

Stop Clock Request: STPCLK# is an active low output synchronous

to PCICLK. It is asserted by the ICH9 in response to one of many

hardware or software events. When the processor samples STPCLK#

asserted, it responds by stopping its internal clock.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 75

Signal Description

2.13 SMBus Interface

RCIN# I

Keyboard Controller Reset CPU: The keyboard controller can

generate INIT# to the processor. This saves the external OR gate

with the ICH9’s other sources of INIT#. When the ICH9 detects the

assertion of this signal, INIT# is generated for

16 PCI clocks.

NOTE: The ICH9 will ignore RCIN# assertion during transitions to the

S1, S3, S4, and S5 states.

A20GATE IA20 Gate: A20GATE is from the keyboard controller. The signal acts

as an alternative method to force the A20M# signal active. It saves

the external OR gate needed with various other chipsets.

CPUPWRGD O

CPU Power Good: Th is signal should be connected to the

processor’s PWRGOOD input to indicate when the processor power is

valid. This is an output signal that represen ts a logical AND of the

ICH9’s PWROK and VRMPWRGD signals.

DPSLP#

(Mobile Only) /

TP2

(Desktop Only)

Deeper Sleep: DPSLP# is asserted by the ICH9 to the processor.

When the signal is lo w, the processor enters the deep sleep state by

gating off the processor Core Clock inside the processor. When the

signal is high (default), the processor is not in the deep sleep state.

Table 2-13. SM Bus Interface Signals

Name Type Description

SMBDATA I/OD SMBus Data: External pull-up resistor is required.

SMBCLK I/OD SMBus Clock: External pull-up resistor is required.

SMBALERT# /

GPIO11 ISMBus Alert: This signal is used to wake the system or generate

SMI#. If not used for SMBALERT#, it can be used as a GPIO.

Table 2-12. Processor Interface Signals (Sheet 2 of 2)

Name Type Description

Signal Description

76 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.14 System Management Interface

Table 2-14. System Management Interface Signals (Sheet 1 of 2)

Name Type Description

INTRUDER# IIntruder Detect: This signal can be set to disable system if box

detected open. This signal’ s status is readable, so it can be used like a

GPIO if the Intruder Detection is not needed.

SMLINK[1:0] I/OD

System Management Link: SMBus lin k to optional external s ys te m

management ASIC or LAN controller. External pull-ups are required.

Note that SMLINK0 corresponds to an SMBus Clock signal, and

SMLINK1 corresponds to an SMBus Data signal.

LINKALERT# /

CLGPIO4

(Digital Office

Only) / GPIO60

O OD

SMLink Alert: Output of the integrated LAN controller and input to

either the integrated ASF, Intel® AMT or an external management

controller in order for the LAN’ s SMLINK slave to be serviced. External

pull-up resistor is required.

This signal can instead be used as a GPIO or CLGPIO (Digital Office

Only).

MEM_LED /

GPIO24 O OD

Memory LED: Provides DRAM-powered LED control. Allows for the

blinking of an LED to indicate memory activity in all power states.

This functional ity is configure d and controlled by the Intel®

Management Engine.

This signal can instead be used as GPIO24.

SUS_PWR_ACK

(Mobile Only)/

CLGPIO1 (Digital

Office Only) /

GPIO10

SUS_PWR_ACK: This signal is asserted by the Intel® Management

Engine to indicate when the ICH suspend well ma y be powered down.

External 10 kΩ pull-up resistor to VccSus3_3 is required. This

functionality is configured and controlled by the Management Engine.

This signal can instead be used as GPIO10 in platforms that do not

support Intel® AMT or ASF.

This signal is used as GPIO10 or CLGPIO1 (Digital Office Only) in

desktop systems.

AC_PRESENT

(Mobile Only)/

CLGPIO2 (Digital

Office Only) /

GPIO14

AC_PRESENT: This signal is used to indicate to the Intel®

Management Engine that the platform is connected to an AC power

source. This functionality is configured and controlled by the

Management Engine.

This signal can instead be used as GPIO14 in platforms that do not

support Intel® AMT or ASF.

This signal is used as GPIO14 or CLGPIO2 (Digital Office Only) in

desktop systems.

NOTE: Even though the signal is controlled by the Management

Engine, the host can still u se this pin to generate SCI/SMI.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 77

Signal Description

WOL_EN /

GPIO9 O

Wake On LAN Power Enable. In an Intel® AMT or ASF enabled

system, this output signal is driven high by the ICH to control the LAN

subsystem power (VccLAN3_3, VccCL3_3, LAN P H Y Power, and SPI

device) to support Wake on LAN (WOL) when the Inte l® Management

Engine is powered off. This functionality is configured and controlled

by the Management Engine prior to entering the powered off state.

NOTES:

1. This signal should be OR’d with the SLP_M# signal on the

motherboard to determine when to power the LAN subsystem.

2. In order to support WOL out of a G3 state, the WOL_EN pin

needs to be pulled high by an external resistor until the

Management Engine is init ialized.

If ASF or AMT are disabled on a board that is configured for WOL_EN

support, BIOS must utilize GPIO9 to control power to the LAN

subsystem when entering S3–S5.

In platforms that do not support Intel AMT or ASF, this signal is used

as GPIO9.

CLGPIO1

(Digital Office

Only) /

SUS_PWR_ACK

(Mobile On ly)/

GPIO10

Controller Link General Purpose I/O 1. This signal is not used by

the Intel® Management Engine in desktop systems.

This signal is used as GPIO10 in desktop systems. This signal is used

as SUS_PWR_ACK in mobile systems.

CLGPIO2

(Digital Office

Only) /

AC_PRESENT

(Mobile Only) /

GPIO14

I/O

Controller Link General Purpose I/O 2. This signal is not used by

the Intel® Management Engine in desktop systems.

This signal is used as GPIO14 in desktop systems. This signal is used

as AC_PRESENT in mobile systems.

CLGPIO4

(Digital Office

Only) /

LINKALERT# /

GPIO60

I/O Controller Link General Purpose I/O 4. This signal is not used by

the Intel® Management Engine in mobile and desktop systems.

This signal may be used as GPIO60 or LINKALERT#.

CLGPIO5

(Digital Office

Only) /

GPIO57

Controller Link General Purpose I/O 5. This signal is not used by

the Intel® Management Engine in desktop systems. In mobile

systems, this si gnal is asserted to indicate Physical Presence to the

integrated TPM module.

This signal is used as GPIO57 in desktop systems.

CLGPIO6

(Digital Office

Only) /

SPI_CS1# /

GPIO58

(Desktop Only)

I/O Controller Link General Purpose I/O 6. This signal is not used by

the Intel® Management Engine in mobile and desktop systems.

This signal may be used as a GPIO58 (Desktop Only) or SPI_CS1#.

Table 2-14. System Management Interface Signals (Sheet 2 of 2)

Name Type Description

Signal Description

78 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.15 Real Time Clock Interface

2.16 Other Clocks

2.17 Miscellaneous Signals

Table 2-15. Real Time Clock Interface

Name Type Description

RTCX1 Special Crystal Input 1: This signal is connected to the 32.768 kHz crystal. If

no external crystal is used, then RT CX1 can be driv en with the desired

clock rate .

RTCX2 Special Crystal Input 2: This signal is connected to the 32.768 kHz crystal. If

no external crystal i s used, then RTCX2 should be left floating.

Table 2-16. Other Clocks

Name Type Description

CLK14 IOscillator Cl ock: Used for 8254 timers. Runs at 14.31818 MHz. This

clock is permitted to stop during S3 (or lower) states.

CLK48 I48 MHz Clock: Used to run the USB controller. Runs at 48.000 MHz.

This clock is permitted to stop during S3 (or lower) states.

SATA_CLKP

SATA_CLKN I100 MHz Differential Clock: These signals are used to run the SATA

controller at 100 MHz. This clock is permitted to stop during S3/S4/S5

states.

DMI_CLKP,

DMI_CLKN I100 MHz Differential Clock: These signals are used to run the Direct

Media Interface. Runs at 100 MHz.

Table 2-17. Miscellaneous Signals (Sheet 1 of 3)

Name Type Description

INTVRMEN IInternal Voltage Regulato r Enable: This signal en ables the

internal VccSus1_05, VccSus1_5 and VccCL1_5 regulators.

This signal must be pulled-up to VccRTC.

LAN100_SLP I

Internal Voltage Regulato r Enable: When connected to VccRTC,

this signal enables the internal voltage regulators powering

VccLAN1_05 and VccCL1_05.

This signal must be pulled-up to VccRTC.

SPKR O

Speaker: The SPKR signal is the output of counter 2 and is internally

“ANDed” with Port 61h bit 1 to provide Speaker Data Enable. This

signal drives an external speaker driver device, which in turn drives

the system speaker. Upon PLTRST#, its output state is 0.

NOTE: SPKR is sampled as a functional strap. See Section 2.24.1 for

more details. There is a weak integrated pull-down resistor on

SPKR pin.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 79

Signal Description

RTCRST# I

RTC Reset: When asserted, this s ignal resets registe r bits in the RTC

well.

NOTES:

1. Unless CMOS is being cleared (only to be done in the G3

power state), the RTCRST# input must always be high when

all other RTC power planes are on.

2. In the case where the RTC battery is dead or missing on the

platform, the RTCRST# pin must rise before the RSMRST#

pin.

SRTCRST# I

Secondary RTC Reset: This signal resets the manageability register

bits in the RTC well when the RTC battery is removed.

NOTES:

1. The SRT CRST# input must alwa ys be high when all other RT C

power planes are on.

2. In the case where the RTC battery is dead or missing on the

platform, the SRTCRST# pin must rise before the RSMRST#

pin.

TP0

(Desktop Only) /

BATLOW#

(Mobile Only)

ITest Point 0: This signal must have an external pull-up to

VccSus3_3.

TP1

(Desktop Only) /

DPRSTP#

(Mobile Only)

OTest Point 1: Route signal to a test point.

TP2

(Desktop Only) /

DPSLP#

(Mobile Only)

OTest Point 2: Route signal to a test point.

TP3 I/O Test Point 3: Route signal to a test point.

TP4

(Desktop Only) /

CL_DATA1

(Mobile Only)

I/O Test Point 4: Route signal to a test point.

TP5

(Desktop Only) /

CL_CLK1 (Mobile

Only)

I/O Test Point 5: Route signal to a test point.

TP6 (Desktop

Only) /

CL_VREF1

(Mobile Only)

ITest Point 6: Route signal to a test point.

TP7

(Desktop Only) /

CL_RST1#

(Mobile Only)

OTest Point 7: Route signal to a test point.

Table 2-17. Miscellaneous Signals (Sheet 2 of 3)

Name Type Description

Signal Description

80 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.18 Intel® High Definition Audio Link

TP[10:8]

(Mobile Only) /

PWM[2:0]

(Desktop Only)

OD O Test Point [10:8]: Route signal to a test point.

TP11 (Mobile

Only) / SST

(Desktop Only) I/O Test Point 11: Route signal to a test point.

TP12 (Mobile

Only) / PECI

(Desktop Only) I/O Test Point 12: Route signal to a test point.

Table 2-18. Intel® High Definition Audio Link Signals (Sheet 1 of 2)

Name Type Description

HDA_RST# OIntel® High De finition Audio Re set: Master hardware reset to

external codec( s).

HDA_SYNC O

Intel High Defi nition Audio Sync: 48 kHz fixed rate sample

sync to the codec(s). Also used to encode the stream number.

NOTE: This signal is sampled as a functional strap. See

Section 2.24.1 for more details. There is a weak

integrated pull-down resistor on this pin.

HDA_BIT_CLK O

Intel High Defi nition Audio Bit Clo ck Output: 24.000 MHz

serial data clock generated by the Intel High Definition Audio

controller (the Intel® ICH9). This signal has a weak internal pull-

down resistor.

HDA_SDOUT O

Intel H igh Defini tion A udio S erial Data Out : Serial TDM data

output to the codec(s). This serial output is double-pumped for a

bit rate of 48 Mb/s for Intel High Definition Audio.

NOTE: This signal is sampled as a functional strap. See

Section 2.24.1 for more details. There is a weak

integrated pull-down resistor on this pin.

Table 2-17. Miscellaneous Signals (Sheet 3 of 3)

Name Type Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 81

Signal Description

2.19 Serial Peripheral Interface (SPI)

HDA_SDIN[3:0] I

Intel High Definition Audio Serial Data In [3:0]: Serial TDM

data inputs from the codecs. The serial input is single-pumped

for a bit rate of 24 Mb/s for Intel® High Definition Audio. These

signals have integrated pull-down resistors, which are always

enabled.

NOTE: During enumeration, the ICH will drive this signal. During

normal operation, the CODEC will drive it.

HDA_DOCK_EN#

(Mobile On ly) /

GPIO33 O

High Definition Audio Dock Enable: This signal controls the

external Intel HD Audio docking isolation logic. This is an active

low signal. When deasserte d the external docking switch is in

isolate mode. When asserted the external docking switch

electrically connects the Intel HD Audio dock signals to the

corresponding Intel® ICH9 signals.

This signal can instead be used as GPIO33.

NOTE: This si gnal is sampled as a functional strap. See

Section 2.24.1 for more details.

HDA_DOCK_RST#

(Mobile On ly) /

GPIO34 O

High Definition Audio Dock Reset: This signal is a dedicated

HDA_RST# signal for the codec(s) in the docking station. Aside

from operating independently from the normal HDA_RST# signal,

it otherwise works similarly to the HDA_RST# signal.

This signal can instead be used as GPIO34.

Table 2-19. Serial Peripheral Interface (SPI) Signals

Name Type Description

SPI_CS0# OSPI Chip Select 0: Used as the SPI bus request signal.

SPI_CS1# /

CLGPIO6

(Digital Office

Only)/

GPIO58

(desktop Only)

SPI Chip Select 1: Used as the SPI bus request signal. Signal can

also be used as a CLGPIO6 (Digital Office Only) or GPIO58 (Desktop

Only).

NOTE: This signal is sampled as a functional strap. See

Section 2.24.1 for more details. There is a weak integrated

pull-up resistor on this pin.

SPI_MISO ISPI Master IN Slave OUT: Data input pin for ICH9.

SPI_MOSI O

SPI Master OUT Slave IN: Data output pin for ICH9.

NOTE: This signal is sampled as a functional strap. See

Section 2.24.1 for more details. There is a weak integrated

pull-down resistor on this pin.

SPI_CLK OSPI Clock: SPI clock signal, during idle the bus owner will drive the

clock signal low. 17.86 MHz and 31.25 MHz.

Table 2-18. Intel® High Definition Audio Link Signals (Sheet 2 of 2)

Name Type Description

Signal Description

82 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.20 Controller Link

Table 2-20. Controller Link Signals

Signal Name Type Description

CL_CLK0 I/O Controller Link Clock 0: bi-directi onal clock that connects to the

(G)MCH.

CL_DATA0 I/O Controller Link Data 0: bi-directional data that connects to the

(G)MCH.

CL_VREF0 IController Link Reference Voltage 0: External reference

voltage for Controller Link 0.

CL_RST0# OController Link Reset 0: North Controller Link reset that

connects to the (G)MCH.

CL_RST1#

(Mobile On ly) /

TP7

(Desktop Only)

OController Link Reset 1: South Controller Link reset that

connects to a Wireless LAN Device supporting Intel® Active

Management Technology.

CL_CLK1

(Mobile On ly) /

TP5

(Desktop Only)

I/O Controller Link Clock 1: bi-directional clock that c o nnects to a

Wireless LAN Device supporting Intel® Active Management

Technology.

CL_DATA1

(Mobile On ly) /

TP4

(Desktop Only)

I/O Controller Link Data 1: bi-directional data that connects to a

Wireless LAN Device supporting Intel® Active Management

Technology.

CL_VREF1

(Mobile On ly) /

TP6

(Desktop Only)

IController Link Reference Voltage 1: External reference

voltage for Controller Link 1.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 83

Signal Description

2.21 Intel® Quiet System Technology (Desktop Only)

2.22 General Purpose I/O Signals

Table 2-21. Intel® Quiet System Technology Signals

Signal Name Type Description

PWM[2:0]

(Desktop Only) /

TP[10:8]

(Mobile On ly)

OD O

Fan Pulse Width Modulation Outputs: Pulse Width Modulated

duty cycle output si gnal that is used for Intel® Quiet System

Technology.

When controlling a 3-wire fan, this signal controls a power

transistor that, in turn, controls power to the fan. When

controlling a 4-wire fan, this signal is connected to the “Control”

signal on the fan. The polarity of this signal is programmable.

The output default is low.

These signa ls are 5 V tolerant.

TACH0 /

(Desktop Only)

GPIO17

TACH1 /

(Desktop Only)

GPIO1

TACH2 /

(Desktop Only)

GPIO6

TACH3 /

(Desktop Only)

GPIO7

Fan Tachometer Inputs: Tachometer pulse input signal that is

used to measure fan speed. This signal is connected to the

“Sense” signal on the fan.

Can instead be used as a GPIO.

SST

(Desktop Only) /

TP11

(Mobile On ly)

I/O Simple Serial Transport: Single-wire, serial bus. Connect to

SST compliant devices such as SST thermal sensors or voltage

sensors.

PECI

(Desktop Only) /

TP12 (Mobile

Only)

I/O Platform Environment Control Interface: Single-wire, serial

bus. Connect to corresponding pin of the processor for accessing

processor digital thermometer.

Table 2-22. General Purpose I/O Signals (Sheet 1 of 3)

Name Type Tolerance Power

Well Default Description

GPIO60 I/O 3.3 V Suspend Native Multiplexed with LINKALERT#, or can

be used as CLGPIO4 (Digital Office

Only). (Note 11).

GPIO59 I/O 3.3 V Suspend Native Multiplexed with OC[0]#. (Note 11).

GPIO58

(Desktop Only) I/O 3.3 V Suspend

(Note 6) GPI Multiplexed with SPI_CS1# or can be

used as CLGPIO6 (Digital Office Only)

(Note 8 and 10).

GPIO57 I/O 3.3 V Suspend GPI Unmultiplexed. Can be used as

CLGPIO5 (Digital Office Only).

Signal Description

84 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

GPIO56 I/O 3.3 V Suspend GPI Unmultiplexed

GPIO55 I/O 3.3 V Core Native Multiplexed with GNT3# (Note 8).

GPIO54 I/O 5.0 V Core Native Multiplexed with REQ3#. (Note 11).

GPIO53 I/O 3.3 V Core Native Multiplexed with GNT2# (Note 8).

GPIO52 I/O 5.0 V Core Native Multiplexed with REQ2#. (Note 11).

GPIO51 I/O 3.3 V Core Native Multiplexed with GNT1# (Note 8).

GPIO50 I/O 5.0 V Core Native Multiplexed with REQ1#. (Note 11).

GPIO49 I/O 3.3V Core GPO Unmultiplexed (Note 8).

GPIO48 I/O 3.3 V Core GPI Multiplexed with SDATAO UT1.

GPIO[47:44] I/O 3.3V Suspend Native Multiplexed with OC[11:8]#. (Note 11).

GPIO[43:40] I/O 3.3 V Suspend Native Multiplexed with OC[4:1]#. (Note 11).

GPIO39 I/O 3.3 V Core GPI Multiplexed with SDATAOUT0.

GPIO38 I/O 3.3 V Core GPI Multiplexed with SLOAD.

GPIO37 I/O 3.3 V Core GPI Desktop: Multiplexed with SATA3GP.

Mobile: Multiplexed with SATA5GP.

GPIO36 I/O 3.3 V Core GPI Desktop: Multiplexed with SATA2GP.

Mobile: Multiplexed with SATA4GP.

GPIO35 I/O 3.3 V Core GPO Multiplexed with SATACLKREQ#.

GPIO34 I/O 3.3 V Core GPO Mobile: Multiplex e d with

HDA_DOCK_RST#.

Desktop: UnMultiplexed.

GPIO33 I/O 3.3 V Core GPO Mobile: Multiplex e d with

HDA_DOCK_EN#.

Desktop: UnMultiplexed.

GPIO32

(Desktop Only) I/O 3.3 V Core GPO Mobile: This GPIO is not implemented

and is used instead as CLKRUN#.

Desktop: UnMultiplexed.

GPIO31 I/O 3.3 V Suspend Native Multiplexed with OC7#. (Note 11).

GPIO30 I/O 3.3 V Suspend Native Multiplexed with OC6#. (Note 11).

GPIO29 I/O 3.3 V Suspend Native Multiplexed with OC5#. (Note 11).

GPIO28 I/O 3.3 V Suspend GPO Unmultiplexed.

GPIO27 I/O 3.3 V Suspend GPO Unmultiplexed

GPIO26 I/O 3.3 V Suspend Native Multiplexed with S4_STATE#. (Note 9)

GPIO25

(Desktop Only ) I/O 3.3 V Suspend Native

Mobile: This GPIO is not implemented

and is used instead as STP_CPU#.

Desktop: Default as STP_CPU# (Note

4).

GPIO24 I/O 3.3 V Suspend GPO Can be used as MEM_LED. GPIO24

configuration register bits are not

cleared by CF9h reset event.

GPIO23 I/O 3.3 V Core Native Multiplexed with LDRQ1#. (Note 11).

Table 2-22. General Purpose I/O Signals (Sheet 2 of 3)

Name Type Tolerance Power

Well Default Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 85

Signal Description

NOTES:

1. All GPIOs can be configured as either input or output.

2. GPI[15:0] can be configured to cause a SMI# or SCI. Note that a GPI can be routed to

either an SMI# or an SCI, but not both.

3. Some GPIOs exist in the VccSus3_3 power plane. Care must be taken to make sure GPIO

signals are not driven high into powered-down planes. Also, external devices should not be

driving powered down GPIOs high. Some ICH9 GPIOs may be connected to pins on devices

that exist in the core well. If these GPIOs are outputs, there is a danger that a loss of core

GPIO22 I/O 3.3 V Core GPI Multiplexed with SCLOCK.

GPIO21 I/O 3.3 V Core GPI Multiplexed with SATA0GP.

GPIO20 I/O 3.3 V Core GPO Unmultiplexed. (Note 8)

GPIO19 I/O 3.3 V Core GPI Multiplexed with SATA1GP.

GPIO18 I/O 3.3 V Core GPO Unmultiplexed.

GPIO17 I/O 3.3 V Core GPI Desktop: Multiplexed with TACH0.

Mobile: Unmultiplexed

GPIO16 I/O 3.3 V Core

Native

(Mobile) /

GPO

(Desktop)

Mobile: Natively used as DPRSLPVR.

Desktop: UnMultiplexed.

GPIO15

(Desktop Only) I/O 3.3 V Suspend Native

Mobile: GPIO is not implemented and is

used instead as STP_PCI#.

Desktop: Default as STP_PCI#. (Note

4).

GPIO14 I/O 3.3 V Suspend GPI Mobile: Can be used as AC_PRESENT

Desktop: Unmultiplexed. Can be used

as CLGPIO2 (Digital Office Only).

GPIO13 I/O 3.3 V Susp en d GPI Unmultip le xed.

GPIO12 I/O 3.3 V Suspend GPO

(Desktop) Mobile: LAN_PHY_PWR_CTRL.

Desktop: UnMultiplexed.

GPIO11 I/O 3.3 V Suspend Native Multiplexed with SMBALERT#. (Note

11).

GPIO10 I/O 3.3 V Suspend GPI Mobile: Can be used as SUS_PWR_ACK.

Desktop: Unmultiplexed. Can be used

as CLGPIO1 (Digital Office Only).

GPIO9 I/O 3.3 V Suspend Native Can be used as WOL_EN.

GPIO8 I/ O 3.3 V Suspend GPI Unmultip lexed.

GPIO[7:6] I/O 3.3 V Core GPI Desktop: Multiplexed with TACH[3:2].

Mobile: Unmultiplexed

GPIO[5:2] I/OD 5 V Core GPI Multiplexed with PIRQ[H:E]# (Note 6).

GPIO1 I/ O 3.3 V Co re GPI Desktop: Multiplexed with TACH1.

Mobile: Unmultiplexed

GPIO0 I/ O 3.3 V Co re GPI Mobile: Multiplexed with PMSYNC#.

Desktop: U n multiplexed

Table 2-22. General Purpose I/O Signals (Sheet 3 of 3)

Name Type Tolerance Power

Well Default Description

Signal Description

86 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

power (PWROK low) or a Power Butt on Override eve nt will result in the Intel ICH9 driving a

pin to a logic 1 to another device that is powered down.

4. The functio nality that is multip lexed with the GPIO may not be utilized in desktop

configuration.

5. This GPIO is not an open-drain when configured as an output.

6. SPI_CS1# and CLGPIO6 (Digital Office Only) are located in the VccCL3_3 well.

7. When this signal is configured as GPO the output stage is an open drain.

8. This signal is sampled as a functional strap. See Section 2.24.1 for more details.

9. The GPIO_USE_SEL bit for this si gnal is ov err idden by bit 8 in the GEN_PMCON_3 Register

(D31:F0).

10. The GPIO_USE_SEL bit for this is ignored. Functionality is set by bits 9:8 of FLMAP0

11. When the multiplexed GPIO is used as GPIO functionality, care should be taken to ensure

the signal is stable in its inactive state of the native functionality, immediately after reset

until it is initialized to GPIO functionality.

2.23 Power and Ground Signals

Table 2-23. Power and Ground Signals (Sheet 1 of 3)

Name Description

V5REF Reference for 5 V tolerance on core well inputs. This power may be shut off in

S3, S4, S5 or G3 states.

V5REF_Sus

Reference for 5 V toler ance on suspend well inputs. This power is not expected

to be shut off unle ss the syst em is un p lugged in desktop configur ations or the

main battery is removed or completely drained and AC power is not available

in mobile configurations.

Vcc1_05 1.05 V supply for core well logic. This power may be shut off in S3, S4, S5 or

G3 states.

Vcc1_5_A 1.5 V supply for Logic and I/O . This power may be sh ut off in S3 , S4, S5 or G3

states.

Vcc1_5_B 1.5 V supply for Logic and I/O . This power may be sh ut off in S3 , S4, S5 or G3

states.

Vcc3_3 3.3 V supply for core well I/O buffers. This power may be shut off in S3, S4,

S5 or G3 states.

VccCL1_05

1.05V supply for Controller Link. This plane must be on in S0 and other times

Controller Link is used.

This voltage is generated internally. This pin c an be left as No Connect unless

decoupling is required.

VccCL1_5

1.5V supply for Controller Link. This plane must be on in S0 and other times

Controller Link is used.

This voltage is generated internally. This pin c an be left as No Connect unless

decoupling is required.

VccCL3_3

3.3V supply for Controller Link. This is a separate power plane that may or

may not be powered in S3–S5 states. This plane must be on in S0 and other

times Controller Link is used.

NOTE: VccCL3_3 must always be powered when VccLAN3_3 is powered.

VccDMI Power supply for DMI. 1.05V, 1.25V or 1.5V depending on (G)MCH’s DMI

voltage.

VccDMIPLL 1.5 V supply f or core well logic. Th is signal is used for the DMI PLL. This power

may be shut off in S3, S4, S5 or G3 states.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 87

Signal Description

VccGLAN1_5 1.5V supply for integrated Gigabit LAN I/O buffers. This power is on in S0 and

is turned off in S3, S4, S5, even if integrated Gigabit LAN is not used.

VccGLAN3_3 3.3V supply for integrated Gigabit LAN logic and I/O. This power is on in S0

and is turned off in S3, S4, S5, even if integrated Gigabit LAN is not used.

VccGLANPLL 1.5V supply for core well logic. This signal is used for the integrated Gigabit

LAN PLL. This power is shut off in S3, S4, S5 and G3 states.

VccHDA

Core supply for Intel® High Definition Audio. This pin can be either 1.5 or 3.3

V. This power may be shut off in S3, S4, S5 or G3 states.

NOTE: VccSusHDA and VccHDA can be connected to either 1.5 V or 3.3 V

supplies, but both pins must be connected to supplies that are the

same nominal value.

VccLAN1_05

1.05 V supply for LAN controller logic. This is a separ ate power plane that may

or may not be powered in S3–S5 states.

This voltage is generated internally. These pins can be left as No Connect

unless decoupling is required.

VccLAN3_3

3.3 V supply for LAN Connect interface buffers. This is a separate power plane

that may or may not be powered in S3– S5 states. This plane must be on in S0.

NOTE: VccLAN3_3 must always be powered when VccCL3_3 or Vcc3_3 is

powered.

VccRTC

3.3 V (can drop to 2 .0 V m in . in G 3 s t ate) supply for the R TC well. This power

is not expected to be shut off unless the R TC battery is removed or completely

drained.

Note: Implementations should not attempt to clear CMOS by using a jumper

to pull VccRTC low. Clearing CMOS in an Intel® ICH9-based platform can be

done by using a jumper on RTCRST# or GPI.

VccSATAPLL 1.5 V supply for core well logic. This signal is used for the SATA PLL. This

power may be shut off in S3, S4, S5 or G3 states. Must be powered even if

SATA is not used.

VccSus1_05

1.05 V supply for suspend well logic. This power is not expected to be shut off

unless the system is unplugged in desktop configurations or the main battery

is removed or completely drained and AC power is not available in mobile

configurations.

This voltage is generated internally. These pins can be left as No Connects

unless decoupling is required.

VccSus1_5

1.5V supply for the suspend well I/O. This power is not exp ected to be shut off

unless the system is unplugged in desktop configurations.

This voltage is generated internally. These pins can be left as No Connects

unless decoupling is required.

VccSus3_3

3.3 V supply for suspend well I/O buffers. This power is not expected to be

shut off unless the system is unplugged in desktop configurations or the main

battery is removed or completely drained and AC power is not available in

mobile configurations.

VccSusHDA

Suspend supply for Intel® High Definition Audio. This pin can be either 1.5 or

3.3 V. This power is not expected to be shut off unless the system is

unplugged in desktop configurations or the main battery is removed or

completely drained and AC power is not available in mobile configurations.

NOTE: VccSusHDA and VccHDA can be connected to either 1.5 V or 3.3 V

supplies, but both pins must be connected to supplies that are the

same nominal value.

Table 2-23. Power and Ground Signals (Sheet 2 of 3)

Name Description

Signal Description

88 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2.24 Pin Straps

2.24.1 Functional Straps

The following signals are used for static configuration. They are sampled at the rising

edge of PWROK to select configurations (ex cept as noted), and then revert later to their

normal usage. To invoke the associated mode, the signal should be driv en at least four

PCI clocks prior to the time it is sampled.

VccUSBPLL 1.5 V supply for core well logic. This signal is used for the USB PLL. This power

may be shut off in S3, S4, S5 or G3 states. Must be powered even if USB not

used.

Vss Grounds.

V_CPU_IO P owered by the same supply as the processor I/O voltage. This supply is used

to drive the processor interface signals listed in Table 2-12.

Table 2-23. Power and Ground Signals (Sheet 3 of 3)

Name Description

Table 2-24. Functional Strap Definitions (Sheet 1 of 3)

Signal Usage When

Sampled Comment

HDA_SDOUT

XOR C hain

Entr ance / PCI

Express* Port

Config 1 bit 1

(Port 1-4)

Rising Edge of

PWROK

Allows entrance to XOR Cha in testing when TP3

pulled low at rising edge of PWROK.

When TP3 not pulled low at rising edge of PWROK,

sets bit 1 of RPC.PC (Chipset Config Registers:Offset

224h).This signal has a weak internal pull-down.

HDA_SYNC PCI Express

Port Config 1

bit 0 (Port 1-4)

Rising Edge of

PWROK

This signal has a weak internal pull-down.

Sets bit 0 of RPC.PC (Chipset Config Registers:Offset

224h)

GNT2# / GPIO53 PCI Express

Port Config 2

bit 2 (Port 5-6)

Rising Edge of

PWROK

This signal has a weak internal pull-up.

Sets bit 2 of RPC.PC2 (Chipset Config

Registers:Offset 0224h) when sample d low.

GPIO20 Reserved Rising Edge of

PWROK This signal has a weak internal pull-down.

NOTE: This signal should not be pulled high

GNT1#/GPIO51 ESI Strap

(Server Only) Rising edge of

PWROK

Tying this strap low configures DMI for ESI-

compatible operation. This signal has a weak internal

pull-up.

NOTE: ESI compatible mode is for server platforms

only. This signal should not be pulled low for

desktop and mobile.

GNT3# / GPIO55 Top-Block

Swap Over ride Rising Edge of

PWROK

The signal has a weak internal pull-up. If the signal is

sampled low, this indicates that the sy stem is

strapped to the “top-block swap” mode (Intel® ICH9

inverts A16 for all cycles targeting BIOS space). The

status of this strap is readable via the Top Swap bit

(Chipset Config Registers:Offset 3414h:bit 0). Note

that software will not be able to clear the Top-Swap

bit until the system is rebooted without GNT3# being

pulled down.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 89

Signal Description

GNT0# Boot BIOS

Destination

Selection 1

Rising Edge of

PWROK

This field determines the destination of accesses to

the BIOS memory r ange . Si gnals have weak internal

pull-ups. Also controllable via Boot BIOS Destination

bit (Chipset Config Registers:Offset 3410h:bit 11).

This strap is used in conjunction with Boot BIOS

Destination Selection 0 strap.

NOTE: Booting to PCI is intended for debug/testing

only . Boot BIOS Destination Select to LPC/PCI

by functional strap or via Boot BIOS

Destination Bi t will not affect SPI acces ses

initiated by Management Engine or

Integrated GbE LAN.

SPI_CS1# /

GPIO58

Desktop Only) /

CLGPIO6

(Digital Office

Only)

Boot BIOS

Destination

Selection 0

Rising Edge of

CLPWROK

This field determines the destination of accesses to

the BIOS memory r ange . Si gnals have weak internal

pull-ups. Also controllable via Boot BIOS Destination

bit (Chipset Config Registers:Offset 3410h:bit 10).

This strap is used in conjunction with Boot BIOS

Destination Selection 1 strap.

NOTE: Booting to PCI is intended for debug/testing

only . Boot BIOS Destination Select to LPC/PCI

by functional strap or via Boot BIOS

Destination Bi t will not affect SPI acces ses

initiated by Management Engine or

Integrated GbE LAN.

SATALED# PCI Express

Lane Reversal

(Lanes 1-4)

Rising Edge of

PWROK

Signal has weak internal pull-up.

Sets bit 27 of MPC.LR ( Dev ice 28: Fu ncti on 0: Offs et

D8)

SPKR No Reboot Rising Edge of

PWROK

The signal has a weak internal pull-down. If the

signal is sampled high, this indicates that the system

is strapped to the “No Reboot” mode (ICH9 will

disable the TCO Timer system reboot feature). The

status of this strap is readable via the NO REBOOT

bit (Chipset Config Registers:Offset 3410h:bit 5).

TP3 Reserved Rising Edge of

PWROK This signal has a weak internal pull-up. This signal

should not be pulled low.

Table 2-24. Functional Stra p Definitions (Sheet 2 of 3)

Signal Usage When

Sampled Comment

Bit11

(GNT0#) Bit 10

(SPI_CS1#) Boot BIOS

Destination

01 SPI

10 PCI

11 LPC

00Reserved

Bit11

(GNT0#) Bit 10

(SPI_CS1#) Boot BIOS

Destination

01 SPI

10 PCI

11 LPC

00Reserved

Signal Description

90 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE: See Section 3.1 for full details on pull-up/pull-down resistors.

2.24.2 External RTC Circuitry

To reduce RTC well power consumption, the ICH9 implements an internal oscillator

circuit that is sensitive to step voltage changes in VccRTC. Figure 2-3 shows an

example schematic recommended to ensure correct operation of the ICH9 RTC.

NOTE: C1 and C2 depend on crystal load.

GPIO33 /

HDA_DOCK_EN#

(Mobile Only)

Flash

Descriptor

Security

Override Strap

Rising Edge of

PWROK

This signal has a weak internal pull-up resistor. If

sampled low, the Flash Descriptor Security will be

overridden. If high, the security measures defined in

the Flash Descriptor will be in effect.

NOTE: This strap should only be enabled in

manufacturing environments.

GPIO49 DMI

Termination

Voltage

Rising Edge of

PWROK

The signal is required to be low for desktop

applications and required to be high for mobile

applications.

SPI_MOSI Reserved Rising Edge of

CLPWROK This signal has a weak internal pull-down resistor.

This signal should not be pulled high.

SPI_MOSI

(Moble Only) Integrated TPM

Enable Rising Edge of

CLPWROK

This signal has a weak internal pull-down resistor.

When the signal is sampled low the Integrated TPM

will be disabled. When the signal is sampled high,

the MCH TPM enable strap is samp led low and the

TPM Disable bit is clear, the Integrated TPM will be

enabled.

NOTE: This signal is required to be floating or pulled

low for desktop applications.

Table 2-24. Functional Strap Definitions (Sheet 3 of 3)

Signal Usage When

Sampled Comment

Figure 2-3. Example External RTC Circuit

32.768 KHz

Xtal 10MΩ

VCCRTC

RTCX2

RTCX1

Vbatt

1uF

1 KΩ

3.3V Sus

C1 C2

RTCRST#

1.0 uF

20 KΩ

0.1uF

SRTCRST#

20 KΩ

1.0 uF

Schottky D iodes

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 91

Intel® ICH9 Pin State s

3 Intel® ICH9 Pin States

3.1 Integrated Pull-Ups and Pull-Downs

NOTES:

1. Simulation data shows that these resistor values can range from 10 kΩ to 40 kΩ.

2. Simulation data shows that these resistor values can range from 9 kΩ to 50 kΩ.

3. Simulation data shows that these resistor values can range from 15 kΩ to 35 kΩ.

4. Simulation data shows that these resistor values can range from 7.5kΩ to 16kΩ.

5. Simulation data shows that these resistor values can range from 14.25 kΩ to 24.8 kΩ

Table 3-1. Integrated Pull -Up and Pull-Down Resistors

Signal Resistor Nominal Notes

CL_CLK[1:0] Pull-up 20K 13

CL_DATA[1:0] Pull-up 20k 13

CL_RST0# Pull-up 10K 4

DPRSLPVR (Mobile Only)/GPIO16 Pull-down 20K 2, 10

HDA_BIT_CLK Pull-down 20K 1, 9

HDA_DOCK_EN# (Mobile Only)/GPIO33 Pull-up 20k 3,7

HDA_RST# Pull-down 20K 2

HDA_SDIN[3:0] Pull-down 20K 2

HDA_SDOUT Pull-down 20K 2, 7

HDA_SYNC Pull-down 20K 2, 7

GNT0#, GNT[3:1]#/GPIO[55,53,51] Pull-up 20K 3, 11, 12

GPIO20 Pull-down 20K 3, 7

GPIO49 Pull-up 20k 3, 7

LAD[3:0]# / FHW[3:0]# Pull-up 20K 3

LAN_RXD[2:0] Pull-up 20K 4

LDRQ0 Pull-up 20K 3

LDRQ1 / GPIO23 Pull-up 20K 3

PME# Pull-up 20K 3

PWRBTN# Pull-up 20K 3

SATALED# Pull-up 15K 8

SPI_CS1# / GPIO58 (D esktop Only) /

CLGPIO6 (Digital Office Only) Pull-up 20K 3, 10

SPI_MOSI Pull-down 20K 3, 7

SPI_MISO Pull-up 20K 3

SPKR Pull-down 20K 2

TACH[3:0] Pull-up 20K 3

TP3 Pull-up 20K 6

USB[11:0] [P,N] Pull-down 15K 5

Intel® ICH9 Pin State s

92 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

6. Simulation data shows that these resistor values can range from 10 kΩ to 30 kΩ.

7. The pull-up or pull-down on this signal is only enabled at boot/reset for strapping function.

8. Simulation data shows that these resistor values can range from 10 kΩ to 20 kΩ. The

internal pull-up is only enabled during PLTRST# assertion.

9. The pull-down on this signal is only enabled when in S3 .

10. The pull-up or pull-down on this signal is only enabled during reset.

11. The pull-up on this signal is not enabled when PCIRST# is high.

12. The pull-up on this signal is enabled when the core power is valid.

13. Simulation data shows that these resistor values can range from 15 kΩ to 31 kΩ.

3.2 Output and I/O Signals Planes and States

Table 3-2 and Table 3-3 shows the power plane associated with the output and I/O

signals, as well as the state at various times. Within the table, the following terms are

used:

“High-Z” Tri-state. ICH9 not driving the signal high or low.

“High” ICH9 is driving the signal to a logic 1.

“Low” ICH9 is driving the signal to a logic 0.

“Defined” Driven to a level that is defined by the function or external pull-

up/pull-down resistor (will be high or low).

“Undefined” ICH9 is driving the signal, but the value is indeterminate.

“Running” Clock is toggling or signal is transitioning because function not

stopping.

“Off” The power plane is off; ICH9 is not driving when configured as

an output or sampling when configured as an input.

“Input” ICH9 is sampling and signal state determined by external driver.

Note: Signal levels are the same in S4 and S5, except as noted.

ICH9 suspend well signal states are indeterminate and undefined and may glitch prior

to RSMRST# deassertion. This does not apply to LAN_RST#, SLP_S3#, SLP_S4#,

S4_STATE# and SLP_S5#. These signals are determinate and defined prior to

RSMRST# deassertion.

ICH9 core well signal states are indeterminate and undefined and may glitch prior to

PWROK assertion. This does not apply to FERR# and THRMTRIP#. These signals are

determinate and defined prior to PWROK assertion.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 93

Intel® ICH9 Pin State s

Table 3-2. Power Plane and States for Output and I/O Signals for Desktop Configurations

(Sheet 1 of 4)

Signal Name Power

Plane During

Reset4Immediately

after Reset4S1 S3 S4/S5

PCI Express*

PETp[5:1],

PETn[5:1],

PETp6 / GLANTXp,

PETn6 / GLANTXn

Core High High8Defined Off Off

DMI

DMI[3:0]TXP,

DMI[3:0]TXN Core High High Defined Off Off

PCI Bus

AD[31:0] Core Low Undefined Defined Off Off

C/BE[3:0]# Core Low Undefined Defined Off Off

DEVSEL# Core High-Z High-Z High-Z Off Off

FRAME# Core High-Z High-Z High-Z Off Off

GNT0#11,

GNT[3:1]#11/

GPIO[55, 53, 51] Core High-Z High High Off Off

IRDY#, TRDY# Core High-Z High-Z High-Z Off Off

PAR Core Low Undefined Defined Off Off

PCIRST# Suspend Low High High Low Low

PERR# Core High-Z High-Z High-Z Off Off

PLOCK# Core High-Z High-Z High-Z Off Off

STOP# Core High-Z High-Z High-Z Off Off

LPC Interface

LAD[3:0] / FWH[3:0] Core High High High Off Off

LFRAME# / FWH[4] Core High High High Off Off

LPCPD# /

SUS_STAT# Suspend Low High High Low Low

Firmware Hub

INIT3_3V# Core High High High Off Off

LAN Connect Interface

LAN_RSTSYNC LAN High Low Defined Defined Defined

LAN_TXD[2:0] LAN Low Low Defined Defined Defined

Gigabit LAN Connect Interface

GLAN_TXp / PETp6,

GLAN_TXn / PETn6 GLAN High High Defined Off Off

LAN_RSTSYNC LAN High Low Defined Defined Defined

Intel® ICH9 Pin State s

94 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

SATA Interface

SATA[5:0]TXP,

SATA[5:0]TXN Core High-Z High-Z Defined Off Off

SATALED#11 Core High-Z High-Z Defined Off Off

SATARBIAS Core High-Z High-Z Defined Off Off

SATACLKREQ# /

GPIO35 Core Low Low Defined Off Off

SCLOCK/GPIO22 Core Input Input Defined Off Off

SLOAD/GPIO38 Core Input Input Defined Off Off

SDATAOUT[1:0]/

GPIO[48,39] Core Input Input Defined Off Off

Interrupts

PIRQ[A:D]#, Core High-Z High-Z High-Z Off Off

PIRQ[H:E]# /

GPIO[5:2] Core Input Input Defined Off Off

SERIRQ Core High-Z High-Z High-Z Off Off

USB Interface

USB[11:0][P,N] Suspend Low Low Defined Defined Defined

USBRBIAS Suspend High-Z High-Z Defined Defined Defined

Power Management

PLTRST# Suspend Low High High Low Low

SLP_M#9Suspend Low High High Defined Defined

SLP_S3# Suspend Low High High Low Low

SLP_S4# Suspend Low High High High Defined

S4_STATE# / GPIO26 Suspend Low Defined Defined De fined Defined

SLP_S5# Suspend Low High High High Low6

SUS_STAT# /

LPCPD# Suspend Low High High Low Low

SUSCLK Suspend Low Running

CK_PWRGD Suspend Low High High Low Low

STP_PCI# / GPIO15 Suspend High High Defined Defined Defined

STP_CPU# / GPIO25 Suspend High High D efined Defined Defined

Table 3-2. Power Plane and States for Output and I/O Signals for Desktop Configurations

(Sheet 2 of 4)

Signal Name Power

Plane During

Reset4Immediately

after Reset4S1 S3 S4/S5

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 95

Intel® ICH9 Pin State s

Processor Interface

A20M# CPU Dependant

on A20GATE

Signal See Note 1 High Off Off

CPUPWRGD CPU Low3High High Off Off

IGNNE# CPU High See Note 1 High Off Off

INIT# CPU High High High Off Off

INTR CPU See Note 5 See Note 5 Low Off Off

NMI CPU See Note 5 See Note 5 Low Off Off

SMI# CPU High High High Off Off

STPCLK# CPU High High Low Off Off

SMBus Interface

SMBCLK, SMBDATA Suspend High-Z High-Z Defined Defined Defined

System Management Interface

LINKALERT# /

CLGPIO4 (Digital

Office Only) / GPIO60 Suspend High-Z High-Z Defined Defined Defined

SMLINK[1:0] Suspend High-Z High-Z Defined Defined Defined

Miscellaneous Signals

SPKR11 Core High-Z Low Defined Off Off

Intel® High Definition Audio Interface

HDA_RST# HDA

Suspend Low Low7Defined Low Low

HDA_SDOUT11 HDA Low Low Low Off Off

HDA_SYNC HDA Low Low Low Off Off

HDA_BIT_CLK HDA Low Low Low Off Off

UnMultiplexed GPIO Signals

GPIO0 Core Input Input Defined Off Off

GPIO8 Suspend Input Input Defined Defined Defined

GPIO9 Suspend High-Z High-Z Defined Defined Defined

GPIO10 Suspend Input Input Defined Defined Defined

GPIO12 Suspend Low Low Defined Defined Defined

GPIO13 Suspend Input Input Defined Defined Defined

GPIO14 Suspend Input Input Defined Defined Defined

GPIO16 Core Low Low Defined Off Off

GPIO18 Core Hi gh See Note 2 Defined Off Off

Table 3-2. Power Plane and States for Output and I/O Signals for Desktop Configurations

(Sheet 3 of 4)

Signal Name Power

Plane During

Reset4Immediately

after Reset4S1 S3 S4/S5

Intel® ICH9 Pin State s

96 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. ICH9 drives these signals High after the processor Reset

2. GPIO[18] will toggle at a frequency of approximately 1 Hz when the ICH9 comes out of

reset

3. CPUPWRGD represents a logical AND of the ICH9’s VRMPWRGD and PWROK signals, and

thus will be driven low by ICH9 when either VRMPWRGD or PWROK are inactive.

4. The states of Core and processor signals are evaluated at the times During PLTRST# and

Immediately after PLTRST#. The states of the LAN and GLAN signals are evaluated at the

times During LAN_RST# and Immediately after LAN_RST#. The states of the Controller

Link signals are taken at the times During CL_RST# and Immediately after CL_RST#. The

states of the Suspend signals are evaluated at the times During RSMRST# and

Immediately after RSMRST#. The states of the HDA si gnals are evaluated at the times

During HDA_RST# and Immediately after HDA_RST#.

GPIO2011 Core Low High Defined Off Off

GPIO24 Suspend Low Low Defined Defined Defined

GPIO[28:27] Suspend Low Low Defined Defined Defined

GPIO3311, GPIO32 Core High High Defined Off Off

GPIO34 Core Low Low Defined Off Off

GPIO4911 Core High High Defined Off Off

GPIO56 Suspend Input Input Defined Defined Defined

GPIO57 Suspend Input Input Defined Defined Defined

SPI Interface

SPI_CS0# Controller

Link High High Defined Defined Defined

SPI_CS1#11 /

GPIO58 / CLGPIO6

(Digital Office Only)

Controller

Link High High Defined Defined Defined

SPI_MOSI11 Controller

Link Low Low Defined Defined Defined

SPI_CLK Controller

Link Low Low Running Defined Defined

Controller Link

CL_CLK0 Controller

Link Low Low Defined10 Defined10 Defined10

CL_DATA0 Controller

Link Low Low Defined10 Defined10 Defined10

CL_RST0# Suspend Low High Defined10 Defined10 Defined10

Intel® Quiet System Technology

PWM[2:0] Core High-Z Low Defined Off Off

SST Controller

Link High-Z Low Defined Off Off

PECI CPU High-Z Low Defined Off Off

Table 3-2. Power Plane and States for Output and I/O Signals for Desktop Configurations

(Sheet 4 of 4)

Signal Name Power

Plane During

Reset4Immediately

after Reset4S1 S3 S4/S5

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 97

Intel® ICH9 Pin State s

5. ICH9 drives these signals Low before PWROK rising and Low after the processor Reset.

6. SLP_S5# signals will be high in the S4 state.

7. Low until Intel High Definition Audio Controller Reset bit set (D27:F0:Offset

HDBAR+08h:bit 0), at which time HDA_RST# will be High and HDA_BIT_CLK will be

Running.

8. PETp/n[6:1] high until port is enabled by software.

9. The SLP_M# state will be determined by Intel AMT Policies.

10. The state of signals in S3-5 will be defined by Intel AMT Policies.

11. This signal is sampled as a functional strap during reset.

Table 3-3. Power Plane and States for Output and I/O Signals for Mobile Configurations

(Sheet 1 of 4)

Signal Name Power

Plane During

Reset4Immediately

after Reset4C3/C4/

C5/C6 S1 S3 S4/S5

PCI Express*

PETp[5:1],

PETn[5:1]

PETp6 / GLANTXp,

PETn6 / GLANTXn

Core High High8Defined Defined Off Off

DMI

DMI[3:0]TXP,

DMI[3:0]TXN Core High High Defined Defined Off Off

PCI Bus

AD[31:0] Core Low Undefined Defined Defined Off Off

C/BE[3:0]# Core Low Undefined Defined Defined Off Off

CLKRUN# Core Low Low Defined Off Off Off

DEVSEL# Core High-Z High-Z High-Z High-Z Off Off

FRAME# Core High-Z High-Z High-Z High-Z Off Off

GNT0#11,

GNT[3:1]#11 /

GPIO[55, 53, 51] Core High High High High Off Off

IRDY#, TRDY# Core High-Z High-Z High-Z H igh-Z Off Off

PAR Core Low Undefined Defined Defined Off Off

PCIRST# Suspend Low High High High Low Low

PERR# Core High-Z High-Z High-Z High-Z Off Off

PLOCK# Core High-Z High-Z High-Z High-Z Off Off

STOP# Core High-Z High-Z High-Z High-Z Off Off

LPC Interface

LAD[3:0] /

FWH[3:0] Core High High High High Off Off

LFRAME# / FWH[4] Core High High High High Off Off

LPCPD# /

SUS_STAT# Suspend Low High High High Low Low

LAN Connect Interface

LAN_RSTSYNC LAN High Low Defined Defined Defined Defined

Intel® ICH9 Pin State s

98 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

LAN_TXD[2:0] LAN Low Low Defined Defined Defined Defined

Gigabit LAN Connect Interface

GLAN_TXp /

PET6p, GLAN_TXn

/ PET6n GLAN High High Defined Defined Off Off

LAN_RSTSYNC LAN High Low Defined Defined Off Off

SATA Interface

SATA[5:4, 1:0]TXP ,

SATA[5:4, 1:0]TXN Core High-Z High-Z Defined Defined Off Off

SATALED#11 Core High-Z High-Z Defined Defined Off Off

SATARBIAS Core High-Z High-Z Defined Defined Off Off

SATACLKREQ# /

GPIO35 Core Low Low Defined Defined Off Off

SCLOCK / GPIO22 Core Input Input Defined Defined Off Off

SLOAD / GPIO38 Core Input Input Defined Defined Off Off

SDATAOUT[1:0] /

GPIO[48, 39] Core Input Input Defined Defined Off Off

Interrupts

PIRQ[A:D]#] Core High-Z High-Z Defined Defined Off Off

PIRQ[H:E ]# /

GPIO[5:2] Core Input Input Defined Defined Off Off

SERIRQ Core High-Z High-Z Running High-Z Off Off

USB Interface

USB[11:0][P,N] Suspend Low Low Low Low Low Low

USBRBIAS Suspend High-Z High-Z Defined Defined Defined Defined

Power Management

PLTRST# Suspend Low High High High Low Low

SLP_M#9Suspend Low High High High Low Defined

SLP_S3# Suspend Low High High High Low Low

SLP_S4# Suspend Low High High High High Defined

S4_STATE# /

GPIO26 Suspend Low Defined Defined Defined Defined Defined

SLP_S5# Suspend Low High High High High Low8

CLKRUN# Core Low Low Running High-Z Off Off

STP_CPU# Suspend High High Defined High Off Off

STP_PCI# Suspend High High Defined High Low Low

SUS_STAT# /

LPCPD# Suspend Low High High High Low Low

Table 3-3. Power Plane and States for Output and I/O Signals for Mobile Configurations

(Sheet 2 of 4)

Signal Name Power

Plane During

Reset4Immediately

after Reset4C3/C4/

C5/C6 S1 S3 S4/S5

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 99

Intel® ICH9 Pin State s

DPRSLPVR Core Low Low Low/High High Off Off

DPRSTP# CPU High High Low/High High Off Off

SUSCLK Suspend Low Running

CK_PWRGD Suspend Low High High High Low Low

PMSYNC# / GPIO0 Core Input Input Defined/

Low12 Defined Off Off

Processor Interface

A20M# CPU

Dependant

A20GATE

Signal

See Note 1 Defined High Off Off

CPUPWRGD CPU See Note 3 High High High Off Off

IGNNE# CPU Hi gh See Note 1 High High Off Off

INIT# CPU High High High High Off Off

INTR CPU See Note 6 See Note 6 Defined Low Off Off

NMI CPU See Note 6 See Note 6 Defined Low Off Off

SMI# CPU High High Defined High Off Off

STPCLK# CPU High High Low Low Off Off

DPSLP# CPU High High High/Low High Off Off

SMBus Interface

SMBCLK, SMBDATA Suspend High-Z High-Z Defined Defined Defined Defined

System Management Interface

MEM_LED /

GPIO24 Suspend Low Low Defined Defined Defined Defined

SUS_PWR_ACK

(Digital Office

Only) / GPIO10 Suspend Input Input Defined Defined Defined Defined

AC_PRESENT

(Digital Office

Only)/

GPIO14

Suspend Input Input Defined Defined Defined Defined

WOL_EN / GPIO9 Suspend High-Z High-Z Defined Defined Defined Defined

CLGPIO5 (Digital

Office Only)/

GPIO57 Suspend Input Input Defined Defined Defined Defined

SMLINK[1:0] Suspend High-Z High-Z Defined Defined Defined Defined

LINKALERT# /

GPIO60 / CLGPIO4

(Digital Office

Only)

Suspend High-Z High-Z Defined Defined Defined Defined

Table 3-3. Power Plane and States for Output and I/O Signals for Mobile Configurations

(Sheet 3 of 4)

Signal Name Power

Plane During

Reset4Immediately

after Reset4C3/C4/

C5/C6 S1 S3 S4/S5

Intel® ICH9 Pin State s

100 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. ICH9 drives these signals High after the processor Reset

2. GPIO[18] will toggle at a frequency of approximately 1 Hz when the ICH9 comes out of

reset

Miscellaneous Signals

SPKR11 Core High-Z Low Defined Defined Off Off

Intel® High Definition Audio Interface

HDA_RST# HDA

Suspend Low Low7High Defined Low Low

HDA_SDOUT11 HDA High-Z Running Running Low Off Off

HDA_SYNC11 HDA High-Z Running Running Low Off Off

HDA_BIT_CLK HDA High-Z Low7Running Low Off Off

HDA_DOCK_RST#

/ GPIO34 HDA Low Low7Defined Defined Off Off

HDA_DOCK_EN# /

GPIO3311 HDA High High Defined Defined Off Off

UnMultiplexed GPIO Signals

GPIO8 Suspend Input Input Defined Defined Defined Defined

GPIO12 Suspend Low Low Defined Defined Defined Defined

GPIO13 Suspend Input Input Defined Defined Defined Defined

GPIO2011 Core Low High Defined Defined Off Off

GPIO4911 Core High High Defined Defined Off Off

GPIO56 Suspend Input Input Defined Defined Defined Defined

SPI Interface

SPI_CS0# Controller

Link High High Defined Defined Defined Defined

SPI_CS1#11 Controller

Link High High Defined Defined Defined Defined

SPI_MOSI11 Controller

Link Low Low Defined Defined Defined Defined

SPI_CLK Controller

Link Low Low Running Running Defined Defined

Controller Link

CL_CLK0,

CL_DATA0 Controller

Link Low Low Defined10 Defined10 Defined10 Defined10

CL_CLK1,

CL_DATA1 Suspend Low Low Defined10 Defined10 Defined10 Defined10

CL_RST[1:0]# Suspend Low High Defined10 Defined10 Defined10 Defined10

Table 3-3. Power Plane and States for Output and I/O Signals for Mobile Configurations

(Sheet 4 of 4)

Signal Name Power

Plane During

Reset4Immediately

after Reset4C3/C4/

C5/C6 S1 S3 S4/S5

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 101

Intel® ICH9 Pin State s

3. CPUPWRGD represents a logical AND of the ICH9’s VRMPWRGD and PWROK signals, and

thus will be driven low by ICH9 when either VRMPWRGD or PWROK are inactive.

4. The states of Core and processor signals are evaluated at the times During PLTRST# and

Immediately after PLTRST#. The states of the LAN and GLAN signals are evaluated at the

times During LAN_RST# and Immediately after LAN_RST#. The states of the Controller

Link signals are evaluated at the times During CL_RST# and Immediately after CL_RST#.

The states of the Suspend signals are evaluated at the tim es During RSMRST# and

Immediately after RSMRST#. The states of the HDA signals are evaluated at the times

During HDA_RST# and Immediately after HDA_RST#.

5. ICH9 drives these signals Low before PWROK rising and Low after the processor Reset.

6. SLP_S5# signals will be high in the S4 state.

7. Low until Intel High Definition Audio Controller Reset bit set (D27:F0:Offset

HDBAR+08h:bit 0), at which time HDA_RST# will be High and HDA_BIT_CLK will be

Running.

8. PETp/n[6:1] high until port is enabled by software.

9. The SLP_M# state will be determined by Intel AMT policies.

10. The state of th ese signals in S3-5 will be defined by Intel AMT Policies.

11. This signal is sampled as a functional strap during reset.

12. PMSYNC# is low during C5/C6 state only.

3.3 Power Planes for Input Signals

Table 3-4 and Table 3-5 shows the power plane associated with each input signal, as

well as what device drives the signal at various times. Valid states include:

High

Low

Static: Will be high or low, but will not change

Driven: Will be high or low, and is allowed to change

Running: For input clocks

ICH9 suspend well signal states are indeterminate and undefined and may glitch prior

to RSMRST# deassertion. This does not apply to LAN_RST#, SLP_S3#, SLP_S4#,

S4_STATE# and SLP_S5#. These signals are determinate and defined prior to

RSMRST# deassertion.

ICH9 core well signal states are indeterminate and undefined and may glitch prior to

PWROK assertion. This does not apply to FERR# and THRMTRIP#. These signals are

determinate and defined prior to PWROK assertion.

Intel® ICH9 Pin State s

102 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 3-4. Power Plane for Input Signals for Desktop Configurations (Sheet 1 of 3)

Signal Name Power Well Driver During Reset S1 S3 S4/S5

DMI

DMI_CLKP,

DMI_CLKN Core Clock Generator Running Off Off

DMI[3:0]RXP,

DMI[3:0]RXN Core (G)MCH Driven Off Off

PCI Express*

PERp[5:1],

PERn[5:1],

PERp6 /

GLAN_RXp,

PERn6 /

GLAN_RXn

Core PCI Express* Device Driven Off Off

PCI Bus

REQ0#,

REQ1# /

GPIO501

REQ2# /

GPIO521

REQ3# /

GPIO541

Core External Pull-up Driven Off Off

PCICLK Core Clock Generator Running Off Off

PME# Suspend Internal Pull-up Driven Driven Driven

SERR# Core PCI Bus Peripherals High Off Off

LPC Interface

LDRQ0# Core LPC Devices High Off Off

LDRQ1# /

GPIO231Core LPC Devices High Off Off

LAN Connect Interface

GLAN_CLK Suspend LAN Connect Component D riven Off Off

LAN_RXD[2:0] Suspend LAN Connect Component Driven Driven Driven

Gigabit LAN Connect Interface

GLAN_RXp /

PER6p,

GLAN_RXn /

PER6n

Suspend Gigabit Lan Connect

Component Driven Off Off

SATA Interface

SATA_CLKP,

SATA_CLKN Core Clock Generator Running Off Off

SATA[5:0]RXP,

SATA[5:0]RXN Core SATA Drive Driven Off Off

SATARBIAS# Core External Pull-down Driven Off Off

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 103

Intel® ICH9 Pin State s

SATA[5:4]GP

SATA[3:0]GP /

GPIO[37, 36, 19,

21]1

Core External Device or

External Pull-up/Pull-down Driven Off Off

USB Interface

OC0# / GPIO59,

OC[4:1]# /

GPIO[43:40],

OC[7:5]# / GPIO

[31:29],

OC[11:8]# /

GPIO[47:44]

Suspend External Pull-ups Driven Driven Driven

USBRBIAS# Suspend External Pull-down Driven Driven Driven

Power Management

CLPWROK Suspend External Circuit Driven Driven Driven

LAN_RST# Suspend External Circuit High High High

MCH_SYNC# Core (G)MCH Driven Off Off

PWRBTN# Sus pend Internal Pull-up Driven Driven Driven

PWROK RTC System Power Supply Driven Off Off

RI# Suspend Serial Port Buffer Driven Driven Driven

RSMRST# RTC External RC Circuit High High High

SYS_RESET# Suspend External Circuit Driven Driven Driven

THRM# Core Thermal Sensor Driven Off Off

THRMTRIP# CPU Thermal Sensor Driven Off Off

VRMPWRGD Suspend Processor Voltage

Regulator High Low Low

WAKE# Suspend External Pull-up Driven Driven Driven

Processor Interface

A20GATE Core External Microcontroller Static Off Off

FERR# Core Processor Static Off Off

RCIN# Core External Microcontroller High Off Off

SMBus Interface

SMBALERT# /

GPIO111Suspend External Pull-up Driven Driven Driven

System Management Interface

INTRUDER# RTC External Switch Driven High High

Miscellaneous Signals

INTVRMEN RTC External Pull-up High High High

LAN100_SLP RTC External Pull-up High High High

Table 3-4. Power Plane for Input Signals for Desktop Configurations (Sheet 2 of 3)

Signal Name P ower Well Driver During Reset S1 S3 S4/S5

Intel® ICH9 Pin State s

104 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. These signals ca n be configured as outputs in GPIO mode.

RTCRST# RTC External RC Circuit High High High

SRTCRST# RTC External RC Circuit High High High

CL_VREF0 Controller

Link External Circuit Driven Driven Driven

TP0 Suspend Ext er nal Pull-up High H igh High

Intel® High Definition Audio Interface

HDA_SDIN[3:0] Suspend Intel High Definition Audio

Codec Low Low Low

SPI Interface

SPI_MISO Suspend Internal Pull-up Driven Driven Driven

Intel® Quiet System Technology

TACH[3:0]/

GPIO[7,6,1,17]1Core External Pull-up Driven Off Off

Clocks

CLK14 Core Clock Generator Running Off Off

CLK48 Core Clock Generator Running Off Off

Table 3-4. Power Plane for Input Signals for Desktop Configurations (Sheet 3 of 3)

Signal Name Power Well Driver During Reset S1 S3 S4/S5

Table 3-5. Power Plane for Input Signals for Mobile Configurations (Sheet 1 of 3)

Signal Name Power

Well Driver During Reset C3/C4/

C5/C6 S1 S3 S4/S5

DMI

DMI_CLKP

DMI_CLKN Core Clock Generator Running Running Off Off

DMI[3:0]RXP,

DMI[3:0]RXN Core (G)MCH Driven Driven Off Off

PCI Express

PERp[6:1], PERn[6:1] Core PCI Express* Device Driven Driven Off Off

PCI Bus

PCICLK Core Clock Generator Running Running Off Off

PME# Suspend Internal Pull-up Driven Driven Driven D riven

REQ0#,

REQ1/GPIO501

REQ2/GPIO521

REQ3/GPIO541

Core External Pull-up Driven Driven Off Off

SERR# Core PCI Bus Peripherals D riven High Off Off

LPC Interface

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 105

Intel® ICH9 Pin State s

LDRQ0# Core LPC Devices Driven High Off Off

LDRQ1# / GPIO231Core LPC Devices Driv en High Off Off

Platform LAN Connect Interface

GLAN_CLK LAN LAN Connect

Component Driven Driven Off Off

LAN_RXD[2:0] LAN LAN Connect

Component Driven Driven Driven Driven

Gigabit LAN Connect Interface

GLAN_RXp

GLAN_RXn GLAN Gigabit Lan Connect

Component Driven Driven Off Off

SATA Interface

SATA_CLKP,

SATA_CLKN Core Clock Generator Running Running Off Off

SATA[5:4, 1:0]RXP,

SATA [5:4, 1:0]RXN Core SATA Drive Driven Driven Off Off

SATARBIAS# Core External Pull-Down Driven Driven Off Off

SATA[5:4, 1:0]GP /

GPIO[37, 36, 19, 21]1Core External Device or

External Pull-up/Pull-

down Driven Driven Off Off

USB Interface

OC0# / GPIO59,

OC[7:5]# /

GPIO[31:29],

OC[4:1]# /

GPIO[43:40],

OC[11:8]# /

GPIO[47:44]

Suspend External Pull-ups Driven Driven Driven Driven

USBRBIAS# Suspend External Pull-down Driven Driven Driven Driven

Power Management

CLPWROK Suspend External Circuit Driven Driven Driven Driven

LAN_RST# Suspend Power Supply High High Static Static

MCH_SYNC# Core (G)MCH Driven Driven Off Off

PWRBTN# Suspend Internal Pull-up Driven Driven Driven Driven

PWROK RTC System Power Supply Driven Driven Off Off

RI# Suspend Serial Port Buffer Driven Driven Driven Driven

RSMRST# RTC External RC Circuit High High High H igh

SYS_RES ET # Suspend External Circuit Driven Driven Driven Driven

THRM# Core Thermal Sensor Dri ven Driven Off Off

THRMTRIP# CPU Thermal Sensor Driven Driven Off Off

VRMPWRGD Suspend Processor Voltage

Regulator Driven Driven Low Low

WAKE# Suspend External Pull-up Driven Driven Driven Driven

Table 3-5. Power Plane for Input Signals for Mobile Configurations (Sheet 2 of 3)

Signal Name Power

Well Driver During Reset C3/C4/

C5/C6 S1 S3 S4/S5

Intel® ICH9 Pin State s

106 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE:

1. These signals ca n be configured as outputs in GPIO mode.

2. The state of the DPRSLPVR and DPRSTP# signals in C4 are high if Deeper Sleep is enabled

or low if it is disabled.

§ §

BATLOW# Suspend Power Supply High High High High

Processor Interface

A20GATE Core External

Microcontroller Static Static Off Off

FERR# Core Processor Static Static Off Off

RCIN# Core External

Microcontroller High High Off Off

SMBus Interface

SMBALERT# /

GPIO111Suspend External Pull-up Driven Driven Driven Driven

System Management Interface

INTRUDER# RTC External Switch Driven Driven High High

Miscellaneous Signals

INTVRMEN RTC External Pull-up High High High High

LAN100_SLP RTC External Pull-up High High High High

RTCRST# RTC External RC Circuit High High High High

SRTCRST# RTC External RC Circuit High High High High

TP0 Suspend External Pull-up High High High High

CL_VREF0 Controller

Link External Circuit Driven Driven Driven Driven

CL_VREF1 Suspend External Circuit Driven Driven Driven Driven

Intel® High Definition Audio Interface

HDA_SDIN[3:0] Suspend Intel High Definition

Audio Codec Driven Low Low Low

SPI Interface

SPI_MISO Suspend Internal Pull-up Driven Driven Driven Driven

Clocks

CLK14 Core Clock Generator Running Running Off Off

CLK48 Core Clock Generator Running Running Off Off

Table 3-5. Power Plane for Input Signals for Mobile Configurations (Sheet 3 of 3)

Signal Name Power

Well Driver During Reset C3/C4/

C5/C6 S1 S3 S4/S5

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 107

Intel® ICH9 and System Clock Domains

4 Intel® ICH9 and System Clock

Domains

Table 4-1 shows the system clock domains. Figure 4-1 and Figure 4-2 shows the

assumed connection of the various system components, including the clock generator

in both desktop and mobile systems. For complete details of the system clocking

solution, refer to the system’s clock generator component specification.

Table 4-1. Intel® ICH9 and System Clock Domains

Clock

Domain Frequency Source Usage

ICH9

SATA_CLKP,

SATA_CLKN 100 MHz Main Clock

Generator Differential clock pair used for SATA.

ICH9

DMI_CLKP,

DMI_CLKN 100 MHz Main Clock

Generator Differential clock pair used for DMI.

ICH9

PCICLK 33 MHz Main Clock

Generator

Free-running PCI Clock to Intel® ICH9. This clock

remains on during S0 and S1 (in desktop) state,

and is expected to be shut off during S3 or below

in desktop configurations or S1 or below in

mobile configurations.

System PCI 33 MHz Main Clock

Generator

PCI Bus, LPC I/F. These only go to external PCI

and LPC devices. Will stop based on CLKRUN#

(and STP_PCI#) in mobile configurations.

ICH9

CLK48 48.000 MHz Main Clock

Generator

Super I/O, USB controllers. Expected to be shut

off during S3 or below in desktop configurations

or S1 or below in mobile configurations .

ICH9

CLK14 14.31818

MHz Main Clock

Generator

Used for ACPI timer and HPET. Expected to be

shut off during S3 or below in desktop

configurations or S1 or below in mobile

configurations.

GLAN_CLK 5 to 62.5

MHz LAN Connect

Component

Generated by the LAN Connect component.

Expected to be shut off during S3 or below in

desktop configurations or S1 or below in mobile

configurations.

SPI_CLK 17.86 MHz/

31.25 MHz ICH Generated by the ICH. Expected to be shut off

during S3 or below in desktop configurations or

S1 or below in mo bile configurations.

Intel® ICH9 and System Clock Domains

108 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

§ §

Figure 4-1. Desktop Conceptual System Clock Diagram

Figure 4-2. Mobile Conceptual Clock Diagram

Intel®

ICH9

32 kHz

XTAL

SUSCLK# (32 kHz)

14.3181 8 MH z PCI Clocks

(33 MH z)

Clock

Gen. 14.31818 MHz

48 MH z

LAN Connect

100 MHz D iff. Pair

1 to 6

Differe n tia l

Clock Fan

Out Device

SA T A 10 0 MH z Diff. P air

DMI 100 MHz Diff. Pair

PCI Express

100 MHz

Diff. Pair s

HD Audio Codec(s)

24 MH z

62.5 MH z

48.000 MHz

33 MH z

Intel®

ICH9M

32 kHz

XTAL

SUSCLK# (32 kHz)

14.31818 MHz

STP_CPU#

STP_PCI#

PCI Clocks

(33 MH z)

Clock

Gen. 14.31818 MHz

48 MH z

LAN Connect

100 MH z Diff. P a ir

1 to 6

Differe ntial

Clock Fan

Out Device

SATA 100 MHz Diff. Pair

DMI 1 00 MH z Diff. P a ir

PCI Express

100 M H z

Diff. Pairs

HD Audio Codec(s)

24 MHz

62.5 MHz

48.000 MHz

33 MHz

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 109

Functional Description

5 Functional Description

This chapter describes the functions and interfaces of the Intel® ICH9 family.

5.1 DMI-to-PCI Bridge (D30:F0)

The DMI-to-PCI bridge resides in PCI Device 30, Function 0 on bus #0. This portion of

the ICH9 implements the buffering and control logic between PCI and Direct Media

Interface (DMI). The arbitration for the PCI bus is handled by this PCI device. The PCI

decoder in this device must decode the ranges for the DMI. All register contents are

lost when core well power is removed.

Direct Media Interface (DMI) is the chip-to-chip connection between the Memory

Controller Hub / Graphics and Memory Controller Hub ((G)MCH) and I/O Controller Hub

9 (ICH9). This high-speed interface integrates advanced priority-based servicing

allowing for concurrent traffic and true isochronous transfer capabilities. Base

functionality is completely software transparen t permitting current and legacy software

to operate normally.

In order to provide for true isochronous transfers and configurable Quality of Service

(QoS) transactions, the ICH9 supports two virtual channels on DMI: VC0 and VC1.

These two channels provide a fixed arbitr ation scheme where VC1 is alwa ys the highest

priority. VC0 is the default conduit of traffic for DMI and is always enabled. VC1 must be

specifically enabled and configured at both ends of the DMI link (i.e ., the ICH9 and

(G)MCH).

Configuration registers for DMI, virtual channel support, and DMI active state power

management (ASPM) are in the RCRB space in the Chipset Config Registers

(Chapter 10).

DMI is also capable of operating in an Enterprise Southbridge Interface (ESI)

compatible mode. ESI is a chip-to-chip connection for server chipsets. In this ESI-

compatible mode, the DMI signals require AC coupling. A hardware strap is used to

configure DMI in ESI-compatible mode, see Section 2.24 for details.

5.1.1 PCI Bus Interface

The ICH9 PCI interface supports PCI Local Bus Specification, Revision 2.3, at 33 MHz.

The ICH9 integrates a PCI arbiter that supports up to four external PCI bus masters in

addition to the internal ICH9 requests.

5.1.2 PCI Bridge As an Initiator

The bridge initiates cycles on the PCI bus when granted by the PCI arbiter. The bridge

generates the following cycle types:

Table 5-1. PCI Bridge Initiator Cycle Types

Command C/BE# Notes

I/O Read/Write 2h/3h Non-posted

Memory Read/Write 6h/7h Writes are posted

Configuration Read/Write Ah/Bh Non-posted

Special Cycles 1h Posted

Functional Description

110 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.1.2.1 Memory Reads and Writes

The bridge bursts memory writes on PCI that are received as a single pack et from DMI.

5.1.2.2 I/O R eads and Writes

The bridge generates single DW I/O read and write cycles. When the cycle completes

on the PCI bus, the bridge generates a corresponding completion on DMI. If the cycle is

retried, the cycle is kept in the down bound queue and may be passed by a postable

cycle.

5.1.2.3 Config uratio n Read s and Writes

The bridge generates single DW configuration read and write cycles. When the cycle

completes on the PCI bus, the bridge generates a corresponding completion. If the

cycle is retried, the cycle is kept in the down bound queue and may be passed by a

postable cycle.

5.1.2.4 Locked Cycles

The bridge propagates locks from DMI per the PCI Local Bus Specification. The PCI

bridge implements bus lock, which means the arbiter will not grant to an y agent except

DMI while locked.

If a locked read results in a target or master abort, the lock is not established (as per

the PCI Local Bus Specification). Agents north of the ICH9 must not forward a

subsequent locked read to the bridge if they see the first one finish with a failed

completion.

5.1.2.5 Target / Master Aborts

When a cycle initiated by the bridge is master/target aborted, the bridge will not re-

attempt the same cycle. Fo r multiple DW cycles, the bridge increments the address and

attempts the next DW of the transaction. For all non-postable cycles, a target abort

response packet is returned for each DW that w as master or target aborted on PCI. The

bridge drops posted writes that abort.

5.1.2.6 Secondary Master Latency Timer

The bridge implem ents a Mast er Latenc y Time r via the SMLT register which, upon

expiration, causes the de-assertion of FRAME# at the next v alid clock edge when there

is another active request to use the PCI bus.

5.1.2.7 Dual A ddress Cycle (DAC)

The bridge will issue full 64-bit dual address cycles for device memory-mapped

registers above 4 GB.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 111

Functional Description

5.1.2.8 Memory and I/O Decode to PCI

The PCI bridge in the ICH9 is a subtractive decode agent, which follows the following

rules when forwarding a cycle from DMI to the PCI interface:

• The PCI bridge will positively decode any memory/IO address within its window

registers, assuming PCICMD.MSE (D30:F0:Offset 04h:bit 1) is set for memory

windows and PCICMD.IOSE (D30:F0:Offset 04h:bit 0) is set for IO windows.

• The PCI bridge will subtractively decode any 64-bit memory address not claimed

by another agent, assuming PCICMD.MSE (D30:F0:Offset 04h:bit 1) is set.

• The PCI bridge will subtractively decode any 16-bit I/O address not claimed by

another agent assuming PCICMD.IOSE (D30:F0:Offset 04h:bit 0) is set.

• If BCTRL.IE (D 30:F0:Offset 3Eh:bit 2) is set, the PCI bridge will not positively

forward from primary to secondary called out ranges in the IO window per PCI

Local Bus Specification (I/O transactions addressing the last 768 bytes in each, 1

KB block: offsets 100h to 3FFh). The PCI bridge will still take them subtractively

assuming the above rules.

• If BCTRL.VGA E (D30:F0:Offset 3Eh:bit 3) is set, the PCI bridge will positively

forward from primary to secondary I/O and memory ranges as called out in the PCI

Bridge Specification, assuming the above rules are met.

5.1.3 Parity Error Detection and Generation

PCI parity errors can be detected and reported. The following behavioral rules apply:

• When a parity error is detected on PCI, the bridge sets the SECSTS.DPE

(D30:F0:Off set 1Eh:bit 15).

• If the bridge is a master and BCTRL.PERE (D30:F0:Offset 3Eh:bit 0) is set and one

of the parity errors defined below is detected on PCI, then the bridge will set

SECSTS.DPD (D30:F0:Offset 1Eh:bit 8) and will also generate an internal SERR#.

— During a write cycle, the PERR# signal is active, or

— A data parity error is detected while performing a read cycle

• If an address or command parity error is detected on PCI and PCICMD.SEE

(D30:F0:Offset 04h:bit 8), BCTRL.PERE, and BCTRL.SEE (D30:F0:Offset 3Eh:bit 1)

are all set, the bridge will set PSTS.SSE (D30:F0:Offset 06h:bit 14) and generate

an internal SERR#.

• If the PSTS.SSE is set because of an address parity error and the PCICMD.SEE is

set, the bridge will generate an internal SERR#

• When bad parity is detected from DMI, bad parity will be driven on all data from the

bridge.

• When an address parity error is detected on PCI, the PCI bridge will never claim the

cycle. This is a slight deviation from the PCI bridge spec, which says that a cycle

should be claimed if BCTRL.PERE is not set. However, DMI does not have a concept

of address parity error, so claiming the cycle could result in the rest of the system

seeing a bad transaction as a good transaction.

Functional Description

112 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.1.4 PCIRST#

The PCIRST# pin is generated under two conditions:

•PLTRST# active

• BCTRL.SBR (D30:F0:Offset 3Eh:bit 6) set to 1

The PCIRST# pin is in the suspend well. PCIRST# shou ld be tied to PCI bus agents, but

not other agents in the system.

5.1.5 Peer Cycles

The PCI bridge may be the initiator of peer cycles. Peer cy cles include memory, IO, and

configuration cycle types. Peer cycles are only allowed through VC0, and are enabled

with the following bits:

• BPC.PDE (D30:F0: Off s et 4Ch:bit 2) – Memo ry and IO cycles

• BPC.CDE (D30:F0:Offset 4Ch:bit 1) – Configuration cycles

When enabled for peer for one of the above cycle types, the PCI bridge will perform a

peer decode to see if a peer agent can receive the cycle. When not enabled, memory

cycles (posted and/or non-posted) are sent to DMI, and I/O and/or configuration cycles

are not claimed.

Configuration cycles hav e special considerations. Under the PCI Local Bus Specification,

these cycles are not allowed to be forwarded upstream through a bridge. However, to

enable things such as manageability, BPC.CDE can be set. When set, type 1 cycles are

allowed into the part. The address format of the type 1 cycle is slightly different from a

standard PCI configuration cy cle to allow addressing of extended PCI space. The format

is as follows:

Note: The ICH9’s USB controllers cannot perform peer-to-peer traffic.

5.1.6 PCI-to-PCI Bridge Model

From a software perspective, the ICH9 contains a PCI-to-PCI bridge. This bridge

connects DMI to the PCI bus. By using the PC I -to-PCI bridge softw are model, the ICH9

can have its decode ranges programmed by existing plug-and-play software such that

PCI ranges do not conflict with graphics aperture ranges in the Host controller.

Table 5-2. Type 1 Address Format

Bits Definition

31:27 Reserved (same as the PCI Local Bus Specification)

26:24 Extended Configuration Address – allows addressing of up to

4K. These bits are combined with bits 7:2 to get the full

23:16 Bus Number (same as the PCI Local Bus Specification)

15:11 Device Num b er (same as the PCI Local Bus Specificati o n )

10:8 Function Number (same as the PCI Local Bus Specification)

7:2 Register (same as the PCI Local Bus Specific ation)

0Must be 1 to indicate a type 1 cycle. Type 0 cycles are not

decoded.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 113

Functional Description

5.1.7 IDSEL to Device Number Mapping

When addressing devices on the external PCI bus (with the PCI slots), the ICH9 asserts

one address signal as an IDSEL. When accessing device 0, the ICH9 asserts AD16.

When accessing Device 1, the ICH9 asserts AD17. This mapping continues all the way

up to device 15 where the ICH9 asserts AD31. Note that the ICH9’s internal functions

(Intel® High Definition Audio, USB , SATA and PCI Bridge) are enumer ated like they are

off of a separate PCI bus (DMI) from the external PCI bus.

5.1.8 Standard PCI Bus Configuration Mechanism

The PCI Bus defines a slot based “configuration space” that allows each device to

contain up to eight functions with each function containing up to 256, 8-bit

configuration registers. The PCI Local Bus Specification, Revision 2.3 defines two bus

cycles to access the PCI configuration space: Configuration Read and Configuration

Write. Memory and I/O spaces are supported directly by the processor. Configuration

space is supported by a mapping mechanism implemented within the ICH9. The PCI

Local Bus Specification, Revision 2.3 defines two mechanisms to access configuration

space, Mechanism 1 and Mechanism 2. The ICH9 only supports Mechanism 1.

Warning: Configuration writes to intern al devices, w hen the devices are disabled, are invalid and

may cause undefined results.

5.2 PCI Express* Root Ports (D28:F0,F1,F2,F3,F4,F5)

There are six root ports available in ICH9. These all reside in device 28, and take

function 0 – 5. Port 1 is function 0, port 2 is function 1, port 3 is function 2, port 4 is

function 3, port 5 is function 4, and port 6 is function 5.

PCI Express Root Ports 1-4 can be statically configured as four x1 Ports or ganged

together to form one x4 port. Ports 5 and 6 can only be used as two x1 ports. On

Mobile platforms, PCI Express Ports 1-4 can also be configured as one x2 port (using

ports 1 and 2) with ports 3 and 4 configured as x1 ports. The port configuration is set

by RCBA 224h [Bits 1:0] see Section 10.1.38 for more details.

5.2.1 Interrupt Generation

The root port generates interrupts on behalf of Hot-Plug and power management

events, w hen enable d. T hese i nterrup ts can ei ther be pin based, or can be MSIs, when

enabled.

When an interrupt is generated via the legacy pin, the pin is internally routed to the

ICH9 interrupt controllers. The pin that is driven is based upon the setting of the

chipset configuration registers. Specifically, the chipset configuration registers used are

the D28IP (Base address + 310Ch) and D28IR (Base address + 3146h) register s.

The following table summarizes interrupt behavior for MSI and wire-modes. In the

table “bits” refers to the Hot-Plug and PME interrupt bits.

Functional Description

114 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.2.2 Power Management

5.2.2.1 S3/S4/S5 Support

Software initiates the tran sitio n to S3/S4/S5 by performing an IO write to the Power

Management Control register in the ICH9. After the IO write completion has been

returned to the processor, each root port will send a PME_Turn_Off TLP (Transaction

Layer Packet) message on its downstream link. The device attached to the link will

eventually respond with a PME_TO_Ack TLP message followed by sending a

PM_Enter_L23 DLLP (Data Link Layer Packet) request to enter the L2/L3 Ready state.

When all of the ICH9 root ports links are in the L2/L3 Ready state, the ICH9 power

management control logic will proceed with the entry into S3/S4/S5.

Prior to entering S3, software is requ ired to put each device into D3 HOT. When a device

is put into D3HOT it will initiate entry into a L1 link state by sending a PM_Enter_L1

DLLP. Thus under normal operating conditions when the root ports sends the

PME_Turn_Off message the link will be in state L1. However, when the root port is

instructed to send the PME_Turn_Off message, it will send it whether or not the link

was in L1. Endpoints attached to ICH can make no assumptions about the state of the

link prior to receiving a PME_Turn_Off message.

5.2.2.2 Resuming from Suspended State

The root port contains enough circuitry in the suspend well to detect a wake event

through the WAKE# signal and to wake the system. When WAKE# is detected asserted,

an internal signal is sent to the power management controller of the ICH9 to cause the

system to wake up. This internal message is not logged in any register, nor is an

interrupt/GPE generated due to it.

5.2.2.3 Device Initiated PM_PME Message

When the system has returned to a working state from a previous low power state, a

device requesting service will send a PM_PME message continuously, until acknowledge

by the root port. The root port will take different actions depending upon whether this

is the first PM_PME has been received, or whether a previous message has been

received but not yet serviced by the operating system.

If this is the first message received (RSTS.PS - D28:F0/F1/F2/F3/F4/F5:Offset 60h:bit

16 is cleared), the root port will set RSTS.PS, and log the PME Requester ID into

RSTS.RID (D28:F0/F1/F2/F3/F4/F5:Offset 60h:bits 15:0). If an interrupt is enabled via

Table 5-3. MSI vs. PCI IRQ Actions

Interrupt Register Wire-Mode

Action MSI Action

All bits 0 Wire inactive No action

One or more bits set to 1 Wire active Send

message

One or more bits set to 1, new bit gets set to 1 Wire active Send

message

One or more bits set to 1, software clears some (but not all)

bits Wire active Send

message

One or more bits set to 1, software clears all bits Wire inactive No action

Software clears one or more bits, and one or more bits are

set on the same clock Wire active Send

message

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 115

Functional Description

RCTL.PIE (D28:F0/F1/F2/F3/F4/F5:Offset 5Ch:bit 3), an interrupt will be generated.

This interrupt can be either a pin or an MSI if MSI is enabled via MC.MSIE (D28:F0/F1/

F2/F3/F4/F5:Offset 82h:bit 0). See Section 5.2.2.4 for SMI/SCI generation.

If this is a subsequent message received (RSTS.PS is already set), the root port will set

RSTS.PP (D28:F0/F1/F2/F3/F4/F5:Offset 60h:bit 17) and log the PME Requester ID

from the message in a hidden register. No other action will be taken.

When the first PME event is cleared by softw are clearing RSTS.PS , the root port will set

RSTS.PS, clear RSTS.PP, and move the requester ID from the hidden register into

RSTS.RID.

If RCTL.PIE is set, an interrupt will be gener ated. If RCTL.PIE is not set, a message will

be sent to the power management controller so that a GPE can be set. If messages

have been logged (RSTS.PS is set), and RCTL.PIE is later written from a 0 to a 1, and

interrupt will be generated. This last condition handles the case where the message

was received prior to the operating system re-enabling interrupts after resuming from

a low power state.

5.2.2.4 SMI/SCI Generation

Interrupts for power management events are not supported on legacy operating

systems. To support power management on non-PCI Express aware oper ating systems,

PM events can be routed to generate SCI. To gener ate SC I, MPC.PMCE must be set.

When set, a power management event will cause SMSCS.PMCS (D28:F0/F1/F2/F3/F4/

F5:Offset DCh:bit 31) to be set.

Additionally, BIOS workarounds for power management can be supported by setting

MPC.PMME (D28:F0/F1/F2/F3/F4/F5:Offset D8h:bit 0). When this bit is set, power

management events will set SMSCS.PMMS (D28:F0/F1/F2/F3/F4/F5:Offset DCh:bit 0),

and SMI # will be generated. This bit will be set regardless of whether interrupts or SCI

is enabled. The SMI# may occur concurrently with an interrupt or SCI.

5.2.3 SERR# Generation

SERR# may be generated via two path s – through PCI mechanisms involving bits in the

PCI header, or through PCI Express* mechanisms involving bits in the PCI Express

capability structure.

Figure 5-1. Generation of SERR# to Platform

PSTS.SSE

SERR#

PCICMD.SEE

Secondary Parity Error

Primary Parity Error

Secondary SERR#

Correctable SERR#

Fatal SERR#

Non-Fatal SERR#

PCI

PCI Express

Functional Description

116 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.2.4 Hot-Plug

Each root port implements a Hot-Plug controller which performs the following:

• Messages to turn on / off / blink LEDs

• Presence and attention button detection

• Interrupt generation

The root port only allows Hot-Plug with modules (e.g., ExpressCard*). Edge-connector

based Hot-Plug is not supported.

5.2.4.1 Presence Detection

When a module is plugged in and power is supplied, the physical layer will detect the

presence of the device, and the root port sets SLSTS.PDS (D28:F0/F1/F2/F3/F4/

F5:Offset 5Ah:bit 6) and SLSTS.PDC (D28:F0/F1/F2/F3:Offset 6h:bit 3). If SLCTL.PDE

(D28:F0/F1/F2/F3F4/F5:Offset 58h:bit 3) and SLCTL.HPE (D28:F0/F1/F2/F3F4/

F5:Offset 58h:bit 5) are both set, the root port will also generate an interrupt.

When a module is removed (via the physical layer detection), the root port clears

SLSTS.PDS and sets SLSTS.PDC. If SLCTL.PDE and SLCTL.HPE are both set, the root

port will also generate an interrupt.

5.2.4.2 Message Generation

When system software writes to SLCTL.AIC (D28:F0/F1/F2/F3F4/F5:Offset 58h:bits

7:6) or SLCTL.PIC (D28:F0/F1/F2/F3F4/F5:Offset 58h:bits 9:8), the root port will send

a message down the link to change the state of LEDs on the module.

Writes to these fields are non-postable cycles, and the resulting message is a postable

cycle. When receiving one of these writes, the root port performs the following:

• Changes the state in the register.

• Generates a completion into the upstream queue

• Formulates a message for the downstream port if the field is written to regardless

of if the field changed.

• Generates the message on the downstream port

• When the last message of a command is transmitted, sets SLSTS.CCE (D28:F0/F1/

F2/F3F4/F5:Offset 58h:bit 4) to indicate the command has completed. If

SLCTL.CCE and SLCTL.HPE (D28:F0/F1/F2/F3F4/F5:Offset 58h:bit 5) are set, the

root port generates an interrupt.

The command completed register (SLSTS.CC) applies only to commands issued by

software to control the Attention Indicator (SLCTL.AIC), Power Indicator (SLCTL.PIC),

or Power Controller (SLCTL.PCC). However, writes to other parts of the Slot Control

Hence, any write to the Slot Control Register is considered a command and if enabled,

will result in a command complete interrupt. The only exception to this rule is a write to

disable the command complete interrupt which will not result in a command complete

interrupt.

A single write to the Slot Control register is considered to be a single command, and

hence receives a single command complete, even if the write affects more than one

field in the Slot Control Register.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 117

Functional Description

5.2.4.3 Attention Button Detection

When an attached device is ejected, an attention button could be pressed by the user.

This attention button press will result in the PCI Express message

“Attention_Button_Pressed” from the device. Upon receiving this message, the root

port will set SLSTS.ABP (D28:F0/F1/F2/F3F4/F5:Offset 5Ah:bit 0).

If SLCTL.ABE (D28:F0/F1/F2/F3F4/F5:Offset 58h:bit 0) and SLCTL.HPE (D28:F0/F1/F2/

F3F4/F5:Offset 58h:bit 5) are set, the Hot-Plug controller will also generate an

interrupt. The interrupt is generated on an edge-event. For example, if SLSTS.ABP is

already set, a new interrupt will not be generated.

5.2.4.4 SMI/SCI Generation

Interrupts for Hot-Plug events are not supported on legacy operating systems. To

support Hot -Plug on non-PCI Express aware oper ating systems, Hot-Plug ev ents can be

routed to generate SCI. To generate SCI, MPC.HPCE (D28:F0/F1/F2/F3F4/F5:Offset

D8h:bit 30) must be set. When set, enabled Hot-Plug events will cause SMSCS.HPCS

(D28:F0/F1/F2/F3F4/F5:Offset DCh:bit 30) to be set.

Additionally, BIOS workarounds for Hot-Plug can be supported by setting MPC.HPME

(D28:F0/F1/F2/F3F4/F5:Offset D8h:bit 1). When this bit is set, Hot-Plug events can

cause SMI status bits in SMSCS to be set. Supported Hot-Plug events and their

corresponding SMSCS bit are:

• Command Completed - SCSCS.HPCCM (D28:F0/F1/F2/F3/F4/F5:Offset DCh:bit 3)

• Presence Detect Changed - SMSCS.HPPDM (D28:F0/F1/F2/F3/F4/F5:Offset DCh:bit

• Attention Button Pressed - SMSCS.HP ABM (D28:F0/F1/F2/F3/F4/F5:Offset DCh:bit

• Link Active State Changed - SMSCS.HPLAS (D28:F0/F1/F2/F3/F4/F5:Offset DCh:bit

When any of these bits are set, SMI # will be generated. These bits are set regardless

of whether interrupts or SCI is enabled for Hot-Plug events. The SMI# may occur

concurrently with an interrupt or SCI.

5.3 Gigabit Ethernet Controller (B0:D25:F0)

The ICH9 integrates a Gigabit Ethernet Controller. The integrated Gigabit Ethernet

controller is compatible with Intel 10/100 PHY (Intel® 82562V Platform LAN Connect

device) and Gigabit Ethernet PHY (Intel® 82566 Gigabit Platform LAN Connect device).

The integrated Gigabit Ethernet controller provides two interfaces: LAN Connect

Interface (LCI) for 10/100 operation and Gigabit LAN Connect Interface (GLCI) for

Gigabit Ethernet operation. The GLCI is shared with the ICH9’s PCI Express port 6.

The ICH9 integrated Gigabit Ethernet controller supports multi speed operation,

10/100/1000 MB/s. The integrated Gigabit Ethernet can ope rate in full-duplex at all

supported speeds or half-duplex at 10/100 MB/s, and adheres with the IEEE 802.3x

Flow Control Specification.

Note: Gigabit Ethernet (1000Mb/s) is only supported in S0.

Functional Description

118 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

The controller provides a system interface via a PCI function. A full memory-m apped or

IO-mapped interface is provided to the software, along with DMA mechanisms for high

performance data transfer.

The following summarizes the ICH9 integrated Gigabit Ethernet controller features:

• Configurable LED operation for customization of LED display.

• IPv4 and IPv6 Checksum Offload support (receive, transmit, and large send).

• 64-bit address master support for system using more than 4 GB of physical

memory.

• Configurable receive and transmit data FIFO, programmable in 1 KB increments.

• Intelligent interrupt generation to enhance driver performance.

• Compliance with Advanced Configuration and Power Interface and PCI Power

Management standards.

• ACPI register set and power down functionality supporting D0 & D3 st ates.

• Full wake-up support (APM and ACPI).

• Magic Packet wake-up enable with unique MAC address.

• Fragmented UDP checksum off load for package reassembly.

• Jumbo frames supported.

5.3.1 Gigabit Ethernet PCI Bus Interface

The Gigabit Ethernet controller has a PCI interface to the host processor and host

memory. The following secti ons detail the transaction on the bus.

5.3.1.1 Transaction Layer

The upper layer of the host architecture is the transaction layer. The transaction layer

connects to the device core using an implementation specific protocol. Through this

core-to-transaction-layer protocol, the application-specific parts of the device interact

with the subsystem and transmit and receive requests to or from the remote agent,

respectively.

5.3.1.2 Dat a Alignment

5.3.1.2.1 4 K Boundary

PCI requests must never specify an Address/Length combination that causes a Memory

Space access to cross a 4 K boundary. It is the HW responsibility to break requests into

4 K - aligned requests (if needed). This does not pose any requirement on SW. However,

if SW allocates a buffer across a 4 K boundary, HW will issue multiple requests for the

buffer. SW should consider aligning buffers to 4 KB boundary in cases where it

improves performance.

The alignment to the 4 K boundaries is done in the core. The Transaction layer will not

do any alignment according to these boundaries.

5.3.1.2.2 64 Bytes

PCI requests are multiples of 64 bytes and aligned to make better use of memory

controller resources. Writes, ho wever, can be on any boundary and can cross a 64 byte

alignment boundary

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 119

Functional Description

5.3.1.3 Configuration Request Retry Status

The LAN Controller might have a delay in initialization due to NVM read. If the NVM

configuration read operation is not completed and the device receives a Configuration

Re quest, the device will respond with a Configuration Request Retry Completion Status

to terminate th e Reques t, and thus effectivel y stall the Configuration R equest until such

time that the subsystem has completed local initialization and is ready to communicate

with the host.

5.3.2 Error Events and Error Reporting

5.3.2.1 Data Parity Error

The PCI Host bus does not provide parity protection, but it does forward parity errors

from bridges. The LAN Controller recognizes parity errors through the internal bus

interface and will set the Parity Error bit in PCI Configur ation space. If parity errors are

enabled in configuration space, a system error will be indicated on the PCI Host bus to

the chipset. The offending cycle with a parity error will be dropped and not processed

by the LAN Controller.

5.3.2.2 Completion with Unsuccessful Completion Status

A completion with unsuccessful completion status (any status other than "000") will be

dropped and not processed by the LAN Controller. Furthermore, the request that

corresponds to the unsuccessful completion will not be retried. When this unsuccessful

completion status is received, the System Error bit in the PCI Configuration space will

be set. If the system errors are enabled in configuration space, a system error will be

indicated on the PCI Host bus to the chipset.

5.3.3 Ethernet Interface

The integrated LAN controller provides a complete CSMA/CD function supporting IEEE

802.3 (10Mb/s), 802.3u (100Mb/s) implementations. It also supports the IEEE 802.3z

and 802.3ab (1000Mb/s) implementations. The device performs all of the functions

required for transmission, reception and collision handling called out in the standards.

The mode used to communicate between the LAN controller and the LAN connect

device supports 10/100/1000 Mbps operation, with both half- and full-duplex oper ation

at 10/100 Mbps, and full-duplex operation at 1000 Mbps.

5.3.3.1 MAC/LAN Connect Interface

The integrated LAN controller and LAN Connect Device communicate through either the

platform LAN connect interface (LCI) or Gigabit LAN connect interface (GLCI). All

controller configuration is performed using device control registers mapped into system

memory or I/O space. The LAN Connect Device is configured via the LCI or Gigabit

Ethernet Lan connect interface.

The integrated MAC supports various modes as summarized in the following table

Table 5-4. LAN Mode Suppor t

Mode Interface Active Connections

Legacy 10/100 LCI 82562

Normal 10/100/1000 LCI, GLCI 82566

Functional Description

120 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.3.4 PCI Power Management

The LAN Controller supports the Advanced Configuration and Power Interface (ACPI)

specification as well as Advanced Power Management (APM). This allows the host to be

awoken (i.e. from Sx (S3-S5) to S0) by network-related activity via an internal host

wake signal.

The LAN controller contains power management registers for PCI, and supports D0 and

D3 states. PCI transactions are only allowed in the D0 state, except for host accesses

to the LAN controller’s PCI configuration registers.

5.3.4.1 Wake-Up

The LAN Controller supports two types of wakeup mechanisms:

1. Advanced Power Management (APM) Wakeup

2. ACPI Power Management Wakeup

Both mechanisms use an internal WAKE# signal to wake the system up. This signal is

connected to the suspend wake logic in the ICH9. The wake-up steps are as follows:

1. Host Wake Event occurs (note that packet is not delivered to host)

2. PME_STATUS bit is set

3. Internal WAKE# signal asserted by Host LAN function

4. System wakes from Sx state to S0 state

5. The Host LAN function is transitioned to D0

6. The Host clears the PME_STATUS bit

7. Internal WAKE# signal is deasserted by Host LAN function

5.3.4.1.1 Advanced Power Management Wakeup

Advanced P ower Management W akeup , or APM W akeup, was previously known as W ake

on LAN. It is a feature that has existed in the 10/100 Mbps NICs for several

generations. The basic premise is to receive a broadcast or unicast packet with an

explicit data pattern, and then to assert a signal to wake-up the system. In the earlier

generations, this was accomplished by using a special signal that ran across a cable to

a defined connector on the motherboard. The NIC would assert the signal for

approximately 50ms to signal a wakeup. The LAN Controller uses (if configured to) an

in-band PM_PME message for this.

On power-up, the LAN Controller will read the APM Enable bits from the NVM PCI Init

Control Word into the APM Enable (APME) bits of the Wakeup Control Register (WUC).

These bits control enabling of APM Wakeup.

When APM W akeup is enabled, the LAN Controller checks all incoming packets for Magic

Packets.

Once the LAN Controller receives a matching magic packet, it will:

• Set the Magic Packet Received bit in the Wake Up Status Register (WUS).

• Set the PME_Status bit in the Power Management Control / Status Register

(PMCSR) and assert the internal WAKE# signal.

APM Wakeup is supported in all power states and only disabled if a subsequent NVM

read results in the APM Wake Up bit being cleared or the software explicitly writes a 0

to the APM Wake Up (APM) bit of the WUC register.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 121

Functional Description

5.3.4.1.2 ACPI Power Management Wakeup

The LAN Controller supports ACPI P o wer Management based Wakeups. It can gener ate

system wake-up events from three sources:

• Reception of a Magic Packet.

• Reception of a Network Wakeup Packet.

• Detection of a link change of state.

Activating ACPI Power Management Wakeup requires the following steps:

• The driver programs the Wake Up Filter Control Register (WUFC) to indicate the

packets it wishes to wake up from and supplies the necessary data to the Ipv4

Address Table (IP4AT) and the Flexible Filter Mask Table (FFMT), Flexible Filter

Length Table (FFLT), and the Flexible Filter Value Table (FFVT). It can also set the

Link Status Change Wake Up Enable (LNKC) bit in the Wake Up Filter Control

• The OS (at configuration time) writes a 1 to the PME_EN bit of the Power

Management Control / Status Register (PMCSR.8).

Normally, after enabling wakeup, the OS will write 11b to the lower two bits of the

PMCSR to put the LAN Controller into low-power mode.

Once Wakeup is enabled, the LAN Controller monitors incoming packets, first filtering

them according to its standard address filtering method, then filtering them with all of

the enabled wakeup filters. If a packet passes both the standard address filtering and

at least one of the enabled wakeup filters, the LAN Controller will:

• Set the PME_Status bit in the Power Management Control / Status Register

(PMCSR)

• If the PME_EN bit in the Power Management Control / Status Register (PMCSR) is

set, assert the internal WAKE# signal.

• Set one or more of the Received bits in the Wake Up Status Register (WUS). (More

than one bit will be set if a packet matches more than one filter.)

If enabled, a link state change wakeup will cause similar results, setting PME_Status,

asserting the internal WAKE# signal and setting the Link Status Changed (LNKC) bit in

the Wake Up Status Register (WUS) when the link goes up or down.

The internal WAKE# signal will remain asserted until the OS either writes a 1 to the

PME_Status bit of the PMCSR register or writes a 0 to the PME_En bit.

After receiving a wakeup packet, the LAN Controller will igno re any subsequent wakeup

packets until the driver clears all of the Received bits in the Wake Up Status Register

(WUS). It will also ignore link change events until the driver clears the Link Status

Changed (LNKC) bit in the Wake Up Status Register (WUS).

5.3.5 Configu ra ble LEDs

The LAN Controller supports 3 controllable and configurable LEDs that are driven from

the LAN Connect Device. Each of the three LED outputs can be individually configured

to select the particular event, state, or activity, which will be indicated on that output.

In addition, each LED can be individually configured for output polarity as well as for

blinking versus non-blinking (steady-state) indication.

The configuration for LED outputs is specified via the LEDCTL register. Furthermore, the

hardware-default configur ation for all the LED outputs, can be specified via NVM fields,

thereby supporting LED displays configurable to a particular OEM preference.

Functional Description

122 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Each of the 3 LED's may be configured to use one of a variety of sources for output

indication. The MODE bits control the LED source:

• LINK_100/1000 is asserted when link is established at either 100 or 1000Mbps.

• LINK_10/1000 is asserted when link is established at either 10 or 1000Mbps.

• LINK_UP is asserted when any speed link is established and maintained.

ACTIVITY is asserted when link is established and packets are being tr ansmitted or

received.

• LINK/ACTIVITY is asserted when link is established AND there is NO transmit or

receive activity

• LINK_10 is asserted when a 10Mb ps link is established and maintained.

• LINK_100 is asserted whe n a 100 Mbps link is established and maintained.

• LINK_1000 is asserted when a 1000Mbps link is established and maintained.

• FULL_DUPLEX is asserted when the link is configured for full duplex operation.

• COLLISION is asserted when a collision is observed.

• PAUSED is asserted when the device's transmitter is flow controlled.

• LED_ON is always asserted; LED_OFF is always de-asserted.

The IVRT bits allow the LED source to be inverted before being output or observed by

the blink-control logic. LED outputs are assumed to normally be connected to the

negative side (cathode) of an external LED.

The BLINK bits control whether the LED should be blinked while the LED source is

asserted, and the blinking frequency (either 200ms on and 200ms off or 83ms on and

83ms off). The blink control may be especially useful for ensuring that certain events,

such as ACTIVITY indication, cause LED transitions, which are sufficiently visible to a

human eye. The same blinking rate is shared by all LEDs

5.3.6 Function Level Reset Support (FLR)

The Gigabit LAN Controller supports the Function Level Reset (FLR) capability. The FLR

capability can be used in conjunction with Intel® Virtualization Technology. FLR allows

an Operating System in a Virtual Machine to have complete control over a device,

including its initialization, without interfering with the rest of the platform. The device

provides a software interface that enables the Operating System to reset the whole

device as if a PCI reset was asserted.

5.3.6.1 FL R Steps

5.3.6.1.1 FLR Initialization

1) A FLR is initiated by software writing a ‘1’ to the Initiate FLR bit.

2) All subsequent requests targeting the Function will not be claimed and will be Master

Abort Immediate on the bus. This includes any configuration, I/O or Memory cycles,

however, the Function shall continue to accept completions targeting the Function.

5.3.6.1.2 FLR Operation

Function will Reset all configuration, I/O and memory registers of the Function except

those indicated otherwise and reset all internal states of the Function to the default or

initial condition.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 123

Functional Description

5.3.6.1.3 FLR Completion

The Initiate FLR bit is reset (cleared) when the FLR reset is completed. This bit can be

used to indicate to the software that the FLR reset is completed.

Note: From the time Initiate FLR bit is written to '1' software must wait at least 100ms

before accessing the function.

5.4 LPC Bridge (w/ System and Management

Functions) (D31:F0)

The LPC bridge function of the ICH9 resides in PCI Device 31:Function 0. In addition to

the LPC bridge function, D31:F0 contains other functional units including DMA,

Interrupt controllers, Timers, Power Management, System Management, GPIO, and

RTC. In this chapter, registers and functions associated with other functional units

(power management, GPIO, USB, etc.) are described in their respective sections.

Note: The LPC bridge cannot be configured as a subtractive decode agent.

5.4.1 LP C Interface

The ICH9 implements an LPC interface as described in the Low Pin Count Interface

Specification, Revision 1.1. The LPC interface to the ICH9 is shown in Figure 5-2. Note

that the ICH9 implements all of the signals that are shown as optional, but peripherals

are not required to do so.

Figure 5-2. LPC Interface Diag ram

Intel® ICH9

LPC Device

PCI Bus

PCI

CLK PCI

RST# PCI

SERIRQ PCI

PME#

LA D [3 :0]

LFRAME#

LPCP D#

(Optional)

SUS_STAT#

LDRQ [1:0]#

(Optional)

LSMI#

(Optional)

GPI

Functional Description

124 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.4.1.1 LPC C ycle Types

The ICH9 implements all of the cycle types described in the Low Pin Count Interface

Specification, Revision 1.0. Table 5-5 shows the cycle types supported by the ICH9.

NOTES:

1. Bus Master Read or Write cycles must be naturally aligned. For example, a 1-byte transfer

can be to any address. However, the 2-byte transfer must be word-aligned (i.e., with an

address where A0=0). A dword transfer must be dword-aligned (i.e., with an address

where A1 and A0 are both 0).

5.4.1.2 Sta rt Field Definition

NOTE: All other encodings are RESERVED.

Table 5-5. LPC Cycle Types Supported

Cycle Type Comment

I/O Read 1 byte only. Intel® ICH9 breaks up 16- and 32-bit processor cycles into

multiple 8-bit transfers.

I/O Write 1 byte only. ICH9 breaks up 16- and 32 -bit processor cycles into multiple

8-bit transfers.

DMA Read Can be 1, or 2 bytes

DMA Write Can be 1, or 2 bytes

Bus Master Read Can be 1, 2, or 4 bytes. (See Note 1 below)

Bus Master Write Can be 1, 2, or 4 bytes. (See Note 1 below)

Table 5-6. Start Field Bit Definitions

Bits[3:0]

Encoding Definition

0000 Start of cycle for a generic target

0010 Grant for bus master 0

0011 Grant for bus master 1

1111 Stop/Abort: End of a cycle for a

target.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 125

Functional Description

5.4.1.3 Cycle Type / Direction (CYCTYPE + DIR)

The ICH9 always drives bit 0 of this field to 0. Peripherals running bus master cycles

must also drive bit 0 to 0. Table 5-7 shows the valid bit encodings.

5.4.1.4 Size

Bits[3:2] are reserved. The ICH9 always drives them to 00. Peripherals running bus

master cycles are also supposed to drive 00 for bits 3:2; however, the ICH9 ignores

those bits. Bits[1:0] are encoded as listed in Table 5-8.

Table 5-7. Cycle Type Bit Definitions

Bits[3:2] Bit1 Definition

00 0 I/O Read

00 1 I/O Write

10 0 DMA Read

10 1 DMA Write

11 x Reserved. If a peripheral performing a bus master cycle generates this

value, the Intel® ICH9 aborts the cycle.

Table 5-8. Transfer Size Bit Definition

Bits[1:0] Size

00 8-bit transfer (1 byte)

01 16-bit transfer (2 bytes)

10 Reserved. The Intel® ICH9 never drives this combination. If a peripheral running

a bus master cycle drives this combination, the ICH9 may abort the transfer.

11 32-bit transfer (4 bytes)

Functional Description

126 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.4.1.5 SYNC

Valid values for the SYNC field are shown in Table 5-9.

NOTES:

1. All other co mbinations are RESERVED.

2. If the LPC controller receives any SYNC returned from the device other than short (0101),

long wait (0110), or ready (0000) when running a FWH cycle, indeterminate results may

occur. A FWH device is not allowed to assert an Error SYNC.

5.4.1.6 SYNC Time-Out

There are several error cases that can occur on the LPC interface. The ICH9 responds

as defined in section 4.2.1.9 of the Low Pin Count Interface Specification, Revision 1.1

to the stimuli described therein. There may be other peripheral failure conditions;

however, these are not handled by the ICH9.

5.4.1.7 SYNC Error Indication

The ICH9 responds as defined in section 4.2.1.10 of the Low Pin Count Interface

Specification, Revision 1.1.

Upon recognizing the SYNC field indicating an error, the ICH9 treats this as an SERR by

reporting this into the Device 31 Error Reporting Logic.

Table 5-9. SYNC Bit Definition

Bits[3:0] Indication

0000 Ready: SYNC achieved with no error. For DMA transfers, this also indicates DMA

request deassertion and no more transfers desired for that channel.

0101 Short Wait: Part indicating wait-states. For bus master cycles, the Intel® ICH9

does not use this enc oding . Inst ead, th e ICH 9 use s th e Long Wait encoding (see

next encoding below).

0110 Long Wait: Part in dicating wait -states, and many wait -states will be added. This

encoding driven by the ICH9 for bus master cycles, rather than the Short Wait

(0101).

1001

Ready More (Used only by peripheral for DMA cycle): SYNC achieved with

no error and more DMA transfers desired to continue after this transfer. This

value is valid only on DMA transfers and is not allowe d for any other type o f

cycle.

1010

Error: Sync achieved with error. This is generally used to replace the SERR# or

IOCHK# signal on the PCI/ISA bus. It indicates that the data is to be transferred,

but there is a serious error in this transfer. For DMA transfers, this not only

indicates an error, but also indicates DMA request deassertion and no more

transfers desired for that channel.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 127

Functional Description

5.4.1.8 LFRAME# Usage

The ICH9 follows the usage of LFRAME# as defined in the Low Pin Count Interface

Specification, Revision 1.1.

The ICH9 performs an abort for the following cases (possible failure cases):

• ICH9 starts a Memory, I/O, or DMA cycle, but no device drives a valid SYNC after

four consecutive clocks.

• ICH9 starts a Memory, I/O, or DMA cycle, and the peripher al drives an invalid SYNC

pattern.

• A peripheral drives an invalid address when performing bus master cycles.

• A peripheral drives an invalid value.

5.4.1.9 I/O Cycles

For I/O cycles targeting registers specified in the ICH9’s decode ranges, the ICH9

performs I/O cycles as defined in the Low Pin Count Interface Specification, Revision

1.1. These are 8-bit transfers. If the processor attempts a 16-bit or 32-bit transfer, the

ICH9 breaks the cycle up into multiple 8-bit transfers to consecutive I/O addresses.

Note: If the cycle is not claimed by any peripheral (and subsequently aborted), the ICH9

returns a value of all 1s (FFh) to the processor. This is to maintain compatibility with

ISA I/O cycles where pull-up resistors would keep the bus high if no device responds.

5.4.1.10 Bus Master Cycles

The ICH9 supports Bus Master cycles and requests (using LDRQ#) as defined in the

Low Pin Count Interf ace Specification, Revision 1.1. The ICH9 has two LDRQ# inputs,

and thus supports two separate bus master devices. It uses the associated STAR T fields

for Bus Master 0 (0010b) or Bus Master 1 (0011b).

Note: The ICH9 does not support LPC Bus Masters performing I/O cycles. LPC Bus Masters

should only perform memory read or memory write cycles.

5.4.1.11 LPC Power Management

CLKRUN# Protocol (Mobile Only)

The CLKRUN# protocol is same as the PCI Local Bus Specification. Stopping the PCI

clock stops the LPC clock.

LPCPD# Protocol

Same timings as for SUS_STAT#. Upon driving SUS_STAT# low, LPC peripherals drive

LDRQ# low or tri-state it. ICH9 shuts off the LDRQ# input buffers. After driving

SUS_STAT# active, the ICH9 drives LFRAME# low, and tri-states (or drive low)

LAD[3:0].

Note: The Low Pin Count Interface Specification, Revision 1.1 defines the LPCPD# protocol

where there is at least 30 µs from LPCPD# assertion to LRST# assertion. This

specification explicitly states that this protocol only applies to entry/exit of low power

states which does not include asynchronous reset events. The ICH9 asserts both

SUS_ST A T# (connects to LPCPD#) and PL TRST# (connects to LRST#) at the same time

when the core logic is reset (via CF9h, PWROK, or SYS_RESET#, etc.). This is not

inconsistent with the LPC LPCPD# protocol.

Functional Description

128 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.4.1.12 Configuration and Intel® ICH9 Implications

LPC I/F Decoders

To allow the I/O cycles and memory mapped cycles to go to the LPC interface, the ICH9

includes several decoders. During configuration, the ICH9 must be programmed with

the same decode ranges as the peripheral. The decoders are programmed via the

Device 31:Function 0 configuration space.

Note: The ICH9 cannot accept PCI write cycles from PCI-to-PCI bridges or devices with

similar characteristics (specifically those with a “Retry Read” feature which is enabled)

to an LPC device if there is an outstanding LPC read cycle towards the same PCI device

or bridge. These cycles are not part of normal system operation, but may be

encountered as part of platform validation testing using custom test fixtures.

Bus Master Device Mapping and START Fields

Bus Masters must have a unique START field. In the case of the ICH9 that supports two

LPC bus masters, it drives 0010 for the START field for grants to bus master #0

(requested via LDRQ0#) and 0011 for grants to bus master #1 (requested via

LDRQ1#.). Thus, no registers are needed to configure the START fields for a particular

bus master.

5.5 DMA Operation (D31:F0)

The ICH9 supports LPC DMA using the ICH9’s DMA controller. The DMA controller has

registers that are fixed in the lower 64 KB of I/O space. The DMA controller is

configured using registers in the PCI configuration space. Th ese registers allow

configuration of the channels for use by LPC DMA.

The DMA circuitry incorporates the functionality of two 82C37 DMA controllers with

seven independently programmable channels (Figure 5-3). DMA controller 1 (DMA-1)

corresponds to DMA channels 0–3 and DMA controller 2 (DMA-2) corresponds to

channels 5–7. DMA channel 4 is used to cascade the two controllers and defaults to

cascade mode in the DMA Channel Mode (DCM) Register. Channel 4 is not available for

any other purpose. In addition to accepting requests from DMA slaves, the DMA

controller also responds to requests that software initiates. Software may initiate a

DMA service request by setting any bit in the DMA Channel Request Register to a 1.

Each DMA channel is hardwired to the compatible settings for DMA device size:

channels [3:0] are hardwired to 8-bit, count-by -bytes transfers, and channels [7:5] are

hardwired to 16-bit, count-by-words (address shifted) transfers.

ICH9 provides 24-bit addressing in compliance with the ISA-Compatible specification.

Each channel includes a 16-bit ISA-Compatible Current Register which holds the 16

least-significant bits of the 24-bit address, an ISA-Compatible Page Register which

contains the eight next most significant bits of address.

Figure 5-3. Intel® ICH9 DMA Controller

Channel 0

Channel 1

Channel 2

Channel 3

Channel 4

Channel 5

Channel 6

Channel 7

DMA-1 DMA-2

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 129

Functional Description

The DMA controller also features refresh address generation, and auto-initialization

following a DMA termination.

5.5.1 Channel Priority

For priority resolution, the DMA consists of two logical channel groups: channels 0–3

and channels 4–7. Each group may be in either fixed or rotate mode, as determined by

the DMA Command Register.

DMA I/O slaves normally assert their DREQ line to arbitrate for DMA service. However,

a software request for DMA service can be presented through each channel's DMA

Request Register. A software request is subject to the same prioritization as any

hardware request. See the detailed register description for Request Register

programming information in Section 13.2.

5.5.1.1 Fixed Priority

The initial fixed priority structure is as follows:

The fixed priority ordering is 0, 1, 2, 3, 5, 6, and 7. In this scheme, channel 0 has the

highest priority, and channel 7 has the lowest priority. Channels [3:0] of DMA-1 assume

the priority position of channel 4 in DMA-2, t hus taking priority ov er channels 5, 6, and

5.5.1.2 Rotating Priority

R otation allows for “fairness” in priority resolution. The priority chain rotates so that the

last channel serviced is assigned the lowest priority in the channel group (0–3, 5–7).

Channels 0–3 rotate as a group of 4. They are always placed between channel 5 and

channel 7 in the priority list.

Channel 5–7 rotate as part of a group of 4. That is, channels (5–7) form the first three

positions in the rotation, while channel group (0–3) comprises the fourth position in the

arbitration.

5.5.2 Address Compatibility Mode

When the DMA is operating, the addresses do not increment or decrement through the

High and Low P age Registers. Therefore, if a 24-bit address is 01FFFFh and increments,

the next address is 010000h, not 020000h. Similarly, if a 24-bit address is 020000h

and decrements, the next address is 02FFFFh, not 01FFFFh. However, when the DMA is

operating in 16-bit mode, the addresses still do not increment or decrement through

the High and Low Page Registers but the page boundary is now 128 K. Therefore, if a

24-bit address is 01FFFEh and increments, the next address is 000000h, not

0100000h. Similarly, if a 24-bit address is 020000h and decrements, the next address

is 03FFFEh, not 02FFFEh. This is compatible with the 82C37 and Page Register

implementation used in the PC-AT. This mode is set after CPURST is valid.

High priority Low priority

0, 1, 2, 3 5, 6, 7

Functional Description

130 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.5.3 Summary of DMA Transfer Sizes

Table 5-10 lists each of the DMA device transfer sizes. The column labeled “Current

Byte/Word Count Register” indicates that the register contents represents either the

number of bytes to transfer or the number of 16-bit words to transfer. The column

labeled “Current Address Increment/Decrement” indicates the number added to or

taken from the Current Address register after each DMA transfer cycle. The DMA

Channel Mode Register determines if the Current Address Register will be incremented

or decremented.

5.5.3.1 Address S hifting When Programmed for 16-Bit I/O Count by Words

The ICH9 maintains compatibility with the implementation of the DMA in the PC A T that

used the 82C37. The DMA shifts the addresses for transfers to/from a 16-bit device

count-by-words.

Note: The least significant bit of the Low Page Register is dropped in 16-bit shifted mode.

When programming the Current Address Register (when the DMA channel is in this

mode), the Current Address must be programmed to an even address with the address

value shifted right by one bit.

The address shifting is shown in Table 5-11.

NOTE: The least significant bit of the Page Register is dropped in 16-bit shifted mode.

5.5.4 Autoinitialize

By programming a bit in the DMA Channel Mode Register, a channel may be set up as

an autoinitialize channel. When a channel undergoes autoinitialization, the original

values of the Current Page, Current Address and Current Byte/Word Count Registers

are automatically restored from the Base Page, Address, and Byte/Word Count

Registers of that channel following TC. The Base Registers are loaded simultaneously

with the Current Registers by the microprocessor when the DMA channel is

programmed and remain unchanged throughout the DMA service. The mask bit is not

set when the channel is in autoinitialize. Following autoinitialize, the channel is ready to

perform another DMA service, without processor interv en tion, as soon as a valid DREQ

is detected.

Table 5-10. DMA Transfer Size

DMA Device Date Size And Word Count Current Byte/Word

Count Register

Current Address

Increment/

Decrement

8-Bit I/O, Count By Bytes Bytes 1

16-Bit I/O, Count By Words (Address

Shifted) Words 1

Table 5-11. Address Shifting in 16-Bit I/O DMA Transfers

Output

Address 8-Bit I/O Programmed

Address (Ch 0–3)

16-Bit I/O Programmed

Address (Ch 5–7)

(Shifted)

A[16:1]

A[23:17]

A[16:1]

A[23:17]

A[15:0]

A[23:17]

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 131

Functional Description

5.5.5 Software Commands

There are three additional special software commands that the DMA controller can

execute. The three software commands are:

• Clear Byte Pointer Flip-Flop

•Master Clear

• Clear Mask Register

They do not depend on any specific bit pattern on the data bus.

5.6 LPC DMA

DMA on LPC is handled through the use of the LDRQ# lines from peripherals and

special encodings on LAD[3:0] from the host. Single, Demand, Verify, and Increment

modes are supported on the LPC interface. Channels 0–3 are 8 bit channels. Channels

5–7 are 16-bit channels.

Channel 4 is reserved as a generic bus master request.

5.6.1 Asserting DMA Requ es ts

Peripherals that need DMA service encode their requested channel number on the

LDRQ# signal. To simplify the protocol, each peripheral on the LPC I/F has its own

dedicated LDRQ# signal (they may not be shared between two separate peripherals).

The ICH9 has two LDRQ# inputs, allowing at least two devices to support DMA or bus

mastering.

LDRQ# is synchronous with LCLK (PCI clock). As shown in Figure 5-4, the peripheral

uses the following serial encoding sequence:

• Peripheral starts the sequence by asserting LDRQ# low (start bit). LDRQ# is high

during idle conditions.

• The next three bits contain the encoded DMA channel number (MSB first).

• The next bit (ACT) indicates whether the request for the indicated DMA channel is

active or inactive. The ACT bit is 1 (high) to indicate if it is active and 0 (low) if it is

inactive. The case where ACT is low is rare, and is only used to indicate that a

previous request for that channel is being abandoned.

• After the active/inactive indication, the LDRQ# signal must go high for at least 1

clock. After that one clock, LDRQ# signal can be brought low to the next encoding

sequence.

If another DMA channel also needs to request a transfer, another sequence can be sent

on LDRQ#. For example, if an encoded request is sent for channel 2, and then channel

3 needs a transfer before the cycle for channel 2 is run on the interface, the peripheral

can send the encoded request for channel 3. This allows multiple DMA agents behind an

I/O device to request use of the LPC interface, and the I/O device does not need to self -

arbitrate before sending the message.

Functional Description

132 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.6.2 Abandoning DMA Requests

DMA Requests can be deasserted in two fashions: on error conditions by sending an

LDRQ# message with the ‘ ACT’ bit set to 0, or normally through a SYNC field during the

DMA transfer. This section describes boundary conditions where the DMA request needs

to be removed prior to a data transfer.

There may be some special cases where the peripheral desires to abandon a DMA

transfer. The most likely case of this occurring is due to a floppy disk controller which

has overrun or underrun its FIFO, or software stopping a device prematurely.

In these cases, the peripheral wishes to stop further DMA activity. It may do so by

sending an LDRQ# message with the ACT bit as 0. However, since the DMA request was

seen by the ICH9, there is no assurance that the cycle has not been granted and will

shortly run on LPC. Therefore, peripherals must take into account that a DMA cycle may

still occur. The peripheral can choose not to respond to this cycle, in which case the

host will abort it, or it can choose to complete the cycle no rmally with any r andom data.

This method of DMA deassertion should be prevented whenever possible, to limit

boundary conditions both on the ICH9 and the peripheral.

5.6.3 General Flow of DMA Transfers

Arbitration for DMA channels is performed through the 8237 within the host. Once the

host has won arbitration on behalf of a DMA channel assigned to LPC, it asserts

LFRAME# on the LP C I/F and begins the DMA transfer. The general flow for a basic DMA

transfer is as follows:

1. ICH9 starts transfer by asserting 0000b on LAD[3:0] with LFRAME# asserted.

2. ICH9 asserts ‘cycle type’ of DMA, direction based on DMA transfer direction.

3. ICH9 asserts channel number and, if applicable, terminal count.

4. ICH9 indicates the size of the transfer: 8 or 16 bits.

5. If a DMA read…

— The ICH9 drives the first 8 bits of data and turns the bus around.

— The peripher al acknowledges the data with a valid SYNC.

— If a 16-bit transfer, the process is repeated for the next 8 bits.

6. If a DMA writ e …

— The ICH9 turns the bus around and waits for data.

— The peripheral indicates data ready through SYNC and transfers the first byte.

— If a 16-bit transfer, the peripheral indicates data ready and transfers the next

byte.

7. The pe ri p he ral turns around the bus.

Figure 5-4. DMA Request Assertion through LDRQ#

Start MSB LSB ACT Start

LCLK

LDRQ#

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 133

Functional Description

5.6.4 Terminal Count

Terminal count is communicated through LAD[3] on the same clock that DMA channel is

communicated on LAD[2:0]. This field is the CHANNEL field. Terminal count indicates

the last byte of transfer, based upon the size of the transfer.

For example, on an 8-bit tr ansfer size (SIZE field is 00b), if the TC bit is set, then this is

the last byte. On a 16-bit transfer (SIZE field is 01b), if the TC bit is set, then the

second byte is the last byte. The peripheral, therefore, must internalize the T C bit when

the CHANNEL field is communicated, and only signal TC when the last byte of that

transfer size has been transferred.

5.6.5 Verify Mode

Verify mode is supported on the LPC interface. A verify transfer to the peripheral is

similar to a DMA write, where the peripheral is transferring data to main memory. The

indication from the host is the same as a DMA write, so the peripheral will be driving

data onto the LPC interface. However, the host will not transfer this data into main

memory.

5.6.6 DMA Request Deassertion

An end of transfer is communicated to the ICH9 through a special SYNC field

transmitted by the peripheral. An LPC device must not attempt to signal the end of a

transfer by deasserting LDREQ#. If a DMA transfer is several bytes (e.g., a transfer

from a demand mode device) the ICH9 needs to know when to deassert the DMA

request based on the data currently being transferred.

The DMA agent uses a SYNC encoding on each byte of data being transferred, which

indicates to the ICH9 whether this is the last byte of transfer or if more bytes are

requested. To indicate the last byte of transfer, the peripheral uses a SYNC value of

0000b (ready with no error), or 1010b

(ready with error). These encodings tell the ICH9 that this is the last piece of data

transferred on a DMA read (ICH9 to peripheral), or the byte that follows is the last

piece of data transferred on a DMA write (peripheral to ICH9).

When the ICH9 sees one of these two encodings, it ends the DMA transfer after this

byte and deasserts the DMA request to the 8237. Therefore, if the ICH9 indicated a 16-

bit transfer, the peripheral can end the transfer after one byte by indicating a SYNC

value of 0000b or 1010b. The ICH9 does not attempt to transfer the second byte, and

deasserts the DMA request internally.

If the peripheral indicates a 0000b or 1010b SYNC pattern on the last byte of the

indicated size, then the ICH9 only deasserts the DMA request to the 8237 since it does

not need to end the transfer.

If the peripheral wishes to keep the DMA request active, then it uses a SYNC value of

1001b (ready plus more data). This tells the 8237 that more data bytes are requested

after the current byte has been transferred, so the ICH9 keeps the DMA request active

to the 8237. Therefore, on an 8-bit transfer size, if the peripheral indicates a SYNC

value of 1001b to the ICH9, the data will be transferred and the DMA request will

remain active to the 8237. At a later time, the ICH9 will then come back with another

START–CYCTYPE–CHANNEL–SIZE etc. combination to initiate another transfer to the

peripheral.

Functional Description

134 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

The peripheral must not assume that the next START indication from the ICH9 is

another grant to the peripheral if it had indicated a SYNC value of 1001b. On a single

mode DMA device, the 8237 will re-arbitrate after every transfer. Only demand mode

DMA devices can be assured that they will receive the next START indication from the

ICH9.

Note: Indicating a 0000b or 1010b encoding on the SYNC field of an odd byte of a 16-bit

channel (first byte of a 16-bit transfer) is an error condition.

Note: The host stops the transfer on the LPC bus as indicated, fills the upper byte with

random data on DMA writes (peripher al to memory), and indicates to the 8237 that the

DMA transfer occurred, incrementing the 8237’s address and decrementing its byte

count.

5.6.7 SYNC Field / LDRQ# Rules

Since DMA transfers on LPC are requested through an LDRQ# assertion message, and

are ended through a SYNC field during the DMA transfer, the peripheral must obey the

following rule when initiating back-to-back transfers from a DMA channel.

The peripheral must not assert another message for eight LCLKs after a deassertion is

indicated through the SYNC field. This is needed to allow the 8237, that typically runs

off a much slower internal clock, to see a message deasserted before it is re-asserted

so that it can arbitrate to the next agent.

Under default operation, the host only performs 8-bit transfers on 8-bit channels and

16-bit transfers on 16-bit channels.

The method by which this communication between h ost and peripheral through system

BIOS is performed is bey ond the scope of this specification. Since the LPC host and LPC

peripheral are motherboard devices, no “plug-n-play” registry is required.

The peripheral must n ot assume that the host is able to perform tr ansfer sizes that are

larger than the size allowed for the DMA channel, and be willing to accept a SIZE field

that is smaller than what it may currently have buffered.

To that end, it is recommended that future devices that may appear on the LPC bus,

that require higher bandwidth than 8-bit or 16-bit DMA allow, do so with a bus

mastering interface and not rely on the 8237.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 135

Functional Description

5.7 8254 Timers (D31:F0)

The ICH9 contains three counters that have fixed uses. All registers and functions

associated with the 8254 timers are in the core well. The 8254 unit is clocked by a

14.31818 MHz clock.

Counter 0, System Timer

This counter functions as the system timer by controlling the state of IRQ0 and is

typically programmed for Mode 3 operation. The counter produces a square wave with

a period equal to the product of the counter period (838 ns) and the initial count value.

The counter loads the initial count value 1 counter period after software writes the

count value to the counter I/O address. The counter initially asserts IRQ0 and

decrements the count value by two each counter period. The counter negates IRQ0

when the count value reaches 0. It then reloads the initial count value and again

decrements the initial count value by two each counter period. The counter then

asserts IRQ0 when the count value reaches 0, reloads the initial count value, and

repeats the cycle, alternately asserting and negating IRQ0.

Counter 1, Refresh Req uest Signal

This counter provides the refresh request signal and is typically programmed for Mode

2 operation and only impacts the period of the REF_TOGGLE bit in Port 61. The initial

count value is loaded one counter period after being written to the counter I/O address.

The REF_TOGGLE bit will have a square wa ve behavior (alternate between 0 and 1) and

will toggle at a rate based on the value in the counter. Programming the counter to

anything other than Mode 2 will result in undefined behavior for the REF_TOGGLE bit.

Counter 2, Speaker Tone

This counter provides the speaker tone and is typically programmed for Mode 3

operation. The counter provides a speaker frequency equal to the counter clock

frequency (1.193 MHz) divided by the initial count value. The speaker must be enabled

by a write to port 061h (see NMI Status and Control ports).

5.7.1 Timer Programming

The counter/timers are programmed in the following fashion:

1. Write a control word to select a counter.

2. Write an initial count for that counter.

3. Load the least and/or most significant bytes (as required by Control Word bits 5, 4)

of the

16-bit counter.

4. Repeat with other counters.

Only two conventions need to be observed when programming the counters. First, for

each counter, the control word must be written before the initial count is written.

Second, the initial count must follow the count format specified in the control word

(least significant byte only, most significant byte only, or least significant byte and then

most significant byte).

A new initial count may be written to a counter at any time without affecting the

counter's programmed m ode. Counting is affected as described in the mode definitions.

The new count must follow the programmed count format.

Functional Description

136 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

If a counter is programmed to read/write two-byte counts, the following precaution

applies: A program must not tr ansfer control between writing the first and second byte

to another routine which also writes into that same counter. Otherwise, the counter will

be loaded with an incorrect count.

The Control Word Register at port 43h controls the operation of all three counters.

Several commands are available:

•Control Word Command. Specifies which counter to read or write, the operating

mode, and the count format (binary or BCD).

•Counter Latch Command. Latches the current count so that it can be read by the

system. The countdown process continues.

•Read Back Command. Reads the count value, programmed mode, the current

state of the OUT pins, and the state of the Null Count Flag of the selected counter.

Table 5-12 lists the six operating modes for the interval counters.

5.7.2 Reading from the Interval Timer

It is often desirable to read the value of a counter without disturbing the count in

progress. There are three methods for reading the counters: a simple read operation,

counter Latch command, and the Read-Back command. Each is explained below.

With the simple read and counter latch command methods, the count must be read

according to the programmed format; specifically, if the counter is programmed for two

byte counts, two bytes must be read. The two bytes do not have to be read one right

after the other. Read, write, or programming operations for other counters may be

inserted between them.

5.7.2.1 Simple Read

The first method is to perform a simple read operation. The counter is selected through

port 40h (counter 0), 41h (counter 1), or 42h (counter 2).

Note: Performing a direct read from the counter does not return a determinate value,

because the counting process is asynchronous to read operations. Howev er, in the case

of counter 2, the count can be stopped by writing to the GATE bit in port 61h.

Table 5-12. Counter Operating Modes

Mode Function Description

0 O ut signal on end of count (=0) Output is 0. When count goes to 0, output goes to

1 and stays at 1 until counter is reprogrammed.

1 Hardware retriggerable one-shot Output is 0. When count goes to 0, output goes to

1 for one clock time.

2Rate generator (divide by n

counter) Output is 1. Output goes to 0 for one clock time,

then back to 1 and counter is reloaded.

3Square wave output

Output is 1. Output goes to 0 when counter rolls

over, and counter is reloaded. Output goes to 1

when counter rolls over, and counter is reloaded,

etc.

4 Software triggered strobe Output is 1. Output goes to 0 when count expires

for one clock time.

5 Hardware triggered strobe Output is 1. Output goes to 0 when count expires

for one clock time.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 137

Functional Description

5.7.2.2 Counter Latch Command

The Counter Latch command, written to port 43h, latches the count of a specific

counter at the time the command is received. This command is used to ensure that the

count read from the counter is accurate, particularly when reading a two-byte count.

The count value is then read from each counter’ s Count register as was programmed by

the Control register.

The count is held in the latch until it is read or the counter is reprogrammed. The count

is then unlatched. This allows reading the contents of the counters on the fly without

affecting counting in progress. Multiple Counter Latch Commands may be used to latch

more than one counter. Counter Latch commands do not affect the programmed mode

of the counter in any way.

If a Counter is latched and then, some time later, latched again before the count is

read, the second Counter Latch command is ignored. The count read is the count at the

time the first Counter Latch command was issued.

5.7.2.3 Read Back Command

The Read Back command, written to port 43h, latches the count value, programmed

mode, and current states of the OUT pin and Null Count flag of the selected counter or

counters. The value of the counter and its status may then be read by I/O access to the

counter address.

The Read Back command may be used to latch multiple counter outputs at one time.

This single command is functionally equiv alent to sever al counter latch commands, o ne

for each counter latched. Each counter's latched count is held until it is read or

reprogrammed. Once read, a counter is unlatched. The other counters remain latched

until they are read. If multiple count Read Back commands are issued to the same

counter without reading the count, all but the first are ignored.

The Read Back command may additionally be used to latch status information of

selected counters. The status of a counter is accessed by a read from that counter's I/

O port address. If multiple counter status latch operations are perform ed without

reading the status, all but the first are ignored.

Both count and status of the selected counters may be latched simultaneously. This is

functionally the same as issuing two consecutive, separate Read Back commands. If

multiple count and/or status Read Back commands are issued to the same counters

without any intervening reads, all but the first are ignored.

If both count and status of a counter are latched, the first read operation from that

counter returns the latched status, regardless of which was latched first. The next one

or two reads, depending on wheth er the co unter is programmed for one or two type

counts, returns the latched count. Subsequent reads return unlatched count.

Functional Description

138 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.8 8259 Interrupt Controllers (PIC) (D31:F0)

The ICH9 incorporates the functionality of two 8259 interrupt controllers that provide

system interrupts for the ISA compatible interrupts. These interrupts are: system

timer, keyboard controller, serial ports, parallel ports, floppy disk, mouse, and DMA

channels. In addition, this interrupt controller can support the PCI based interrupts, by

mapping the PCI interrupt onto the compatible ISA interrupt line. Each 8259 core

supports eight interrupts, numbered 0–7. Table 5-13 shows how the cores are

connected.

The ICH9 cascades the slave controller onto the master controller through master

controller interrupt input 2. This means there are only 15 possible interrupts for the

ICH9 PIC.

Interrupts can individually be programmed to be edge or level, except for IRQ0, IRQ2,

IRQ8#, and IRQ13.

Note: Active-low interrupt sources (e.g., the PIRQ#s) are inverted inside the ICH9. In the

following descriptions of the 8259s, the interrupt levels are in reference to the signals

at the internal interface of the 8259s, after the required inversions have occurred.

Therefore, the term “high” indicates “active,” which means “low” on an originating

PIRQ#.

Table 5-13. Interrupt Controller Core Connections

8259 8259

Input Typical Interrupt

Source Connected Pin / Function

Master

0 Internal Internal Timer / Counter 0 outp ut / HPET #0

1 Keyboard IRQ1 via SERIRQ

2 Internal Slave controller INTR output

3 Serial Port A IRQ3 via SERIRQ, PIRQ#

4 Serial Port B IRQ4 via S E RIRQ, PIRQ#

5 Parallel Port / Generic IRQ5 via SERIRQ, PIRQ#

6 Floppy Disk IRQ6 via SERIRQ, PIRQ#

7 Parallel Port / Generic IRQ7 via SERIRQ, PIRQ#

Slave

0Internal Real Time

Clock Internal RTC / HPET #1

1 Generic IRQ9 via SERIRQ, SCI, TCO, or PIRQ#

2 Generic IRQ10 via SERIRQ, SCI, TCO, or PIRQ#

3Generic IRQ11 via SERIRQ, SCI, TCO, or PIRQ#, or HPET

4PS/2 Mouse IRQ12 via SERIRQ, SCI, TCO, or PIRQ#, or HPET

5Internal State Machine output based on processor FERR#

assertion. May optionally be used for SCI or TCO

interrupt if FERR# not needed.

6SATA SATA Primary (legacy mode), or via SERIRQ or

PIRQ#

7SATA SATA Secondary (legacy mode) or via SERIRQ or

PIRQ#

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 139

Functional Description

5.8.1 Interrupt Handling

5.8.1.1 Generating Interrupts

The PIC interrupt sequence involves three bits, from the IRR, ISR, and IMR, for each

interrupt level. These bits are used to determine the interrupt vector returned, and

status of any other pending interrupts. Table 5-14 defines the IRR, ISR, and IMR.

5.8.1.2 Acknowledging Interrupts

The processor generates an interrupt acknowledge cycle that is translated by the host

bridge into a PCI Interrupt Acknowledge Cycle to the ICH9. The PIC translates this

command into two internal INTA# pulses expected by the 8259 cores. The PIC uses the

first internal INT A# pulse to freez e the state of the interrupts for priority resolution. On

the second INTA# pulse, the master or slave sends the interrupt vector to the

processor with the acknowledged interrupt code. This code is based upon bits [7:3] of

the corresponding ICW2 register, combined with three bits representing the interrupt

within that controller.

Table 5-14. Interrupt Status Registers

Bit Description

IRR Interrupt Request Register. This bit is se t on a low to high t ransi tion of the in terrupt

line in edge mode , and by an active high level in level mode. This bit is set whether or

not the interrupt is masked. However, a masked interrupt will not generate INTR.

ISR Interrupt Service Regist er. This bit is set, and the corresponding IRR bit cleared,

when an interrupt acknowledge cycle is seen, and the vector returned is for that

interrupt.

IMR Interrupt Mask Register. This bit determines whether an interrupt is masked.

Masked interrupts will not generate INTR.

Table 5-15. Content of Interrupt Vect or Byte

Master, Slave Interrup

tBits [7:3] Bits [2:0]

IRQ7,15

ICW2[7:3]

111

IRQ6,14 110

IRQ5,13 101

IRQ4,12 100

IRQ3,11 011

IRQ2,10 010

IRQ1,9 001

IRQ0,8 000

Functional Description

140 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.8.1.3 Hardware/Soft ware Interrupt Sequence

1. One or more of the Interrupt Request lines (IRQ) are raised high in edge mode, or

seen high in level mode, setting the corresponding IRR bit.

2. The PIC sends INTR active to the processor if an asserted interrupt is not masked.

3. The pr ocessor acknowledges the INTR and responds with an interrupt acknowledge

cycle. The cycle is translated into a PCI interrupt acknowledge cycle by the host

bridge. This command is broadcast over PCI by the ICH9.

4. Upon observing its own interrupt acknowledge cycle on PCI, the ICH9 converts it

into the two cycles that the internal 8259 pair can respond to. Each cycle appears

as an interrupt acknowledge pulse on the internal INTA# pin of the cascaded

interrupt controllers.

5. Upon receiving the first internally generated INTA# pulse, the highest priority ISR

bit is set and the corresponding IRR bit is reset. On the trailing edge of the first

pulse, a slave identification code is broadcast by the master to the slave on a

private, internal three bit wide bus. The slave controller uses these bits to

determine if it must respond with an interrupt vector during the second INTA#

pulse.

6. Upon receiving the second internally generated INTA# pulse, the PIC returns the

interrupt vector. If no interrupt request is present because the request was too

short in duration, the PIC returns vector 7 from the master controller.

7. This completes the interrupt cycle. In AEOI mode the ISR bit is reset at the end of

the second INTA# pulse. Otherwise, the ISR bit remains set until an appropriate

EOI command is issued at the end of the interrupt subroutine.

5.8.2 Initialization Command Words (ICWx)

Before operation can begin, each 8259 must be initialized. In the ICH9, this is a four

byte sequence. The four initialization command words are referred to by their

acronyms: ICW1, ICW2, ICW3, and ICW4.

The base address for each 8259 initialization command word is a fixed location in the

I/O memory space: 20h for the master controller, and A0h for the slave controller.

5.8.2.1 ICW1

An I/O write to the master or sla ve controller base address with data bit 4 equal to 1 is

interpreted as a write to ICW1. Upon sensing this write, the ICH9 PIC expects three

more byte writes to 21h for the master controller, or A1h for the slave controller, to

complete the ICW sequence.

A write to ICW1 starts the initialization sequence during which the following

automatically occur:

1. Following initialization, an interrupt request (IRQ) input must make a low-to-high

transition to generate an interrupt.

2. Th e Inte rrupt Mas k Regist er is cle ared .

3. IRQ7 input is assigned priority 7.

4. The slave mode address is set to 7.

5. Special mask mode is cleared and Status Read is set to IRR.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 141

Functional Description

5.8.2.2 ICW2

The second write in the sequence (ICW2) is programmed to provide bits [7:3] of the

interrupt vector that will be released during an interrupt acknowledge. A different base

is selected for each interrupt controller.

5.8.2.3 ICW3

The third write in the sequence (ICW3) has a different meaning for each controller.

• For the master controller, ICW3 is used to indicate which IRQ input line is used to

cascade the slave controller. Within the ICH9, IRQ2 is used. Therefore, bit 2 of

ICW3 on the master controller is set to a 1, and the other bits are set to 0s.

• For the slave controller, ICW3 is the slave identification code used during an

interrupt acknowledge cycle. On interrupt acknowledge cycles, the master

controller broadcasts a code to the slave controller if the cascaded interrupt won

arbitration on the master controller. The slave controller compares this

identification code to the value stored in its ICW3, and if it matches, the slave

controller assumes responsibility for broadcasting the interrupt vector.

5.8.2.4 ICW4

The final write in the sequence (ICW4) must be programmed for both controllers. At

the very least, bit 0 must be set to a 1 to indicate that the controllers are operating in

an Intel Architecture-based system.

5.8.3 Operation Command Words (OCW)

These command words reprogram the Interrupt controller to operate in various

interrupt modes.

• OCW1 masks and unmasks interrupt lines.

• OCW2 controls the rotation of interrupt priorities when in rotating priority mode,

and controls the EOI function.

• OCW3 sets up ISR/IRR reads, enables/disables the special mask mode (SMM), and

enables/disables polled interrupt mode.

5.8.4 Modes of Operation

5.8.4.1 Fully Nested Mode

In this mode, interrupt requests are ordered in priority from 0 through 7, with 0 being

the highest. When an interrupt is acknowledged, the highest priority request is

determined and its vector placed on the bus. Additionally, the ISR for the interrupt is

set. This ISR bit remains set until: the processor issues an EOI command immediately

before returning from the service routine; or if in AEOI mode, on the trailing edge of

the second INTA#. While the ISR bit is set, all further interrupts of the same or lower

priority are inhibited, while higher levels generate another interrupt. Interrupt priorities

can be changed in the rotating priority mode.

Functional Description

142 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.8.4.2 Special Fully-Nested Mode

This mode is used in the case of a system where cascading is used, and the priority has

to be conserved within each slave. In this case, the special fully-nested mode is

programmed to the master controller. This mode is similar to the fully-nested mode

with the following exceptions:

• When an interrupt request from a certain slave is in service, this slave is not locked

out from the master's priority logic and further interrupt requests from higher

priority interrupts within the slave are recognized by the master and initiate

interrupts to the processor. In the normal-nested mode, a slave is masked out

when its request is in service.

• When exiting the Interrupt Service routine, software has to check whether the

interrupt serviced was the only one from that slave. This is done by sending a Non-

Specific EOI command to the slave and then reading its ISR. If it is 0, a non-

specific EOI can also be sent to the master.

5.8.4.3 Autom atic Rotation Mode (Equal Priority Devices)

In some applications, there are a number of interrupting devices of equal priority.

Automatic rotation mode provides for a sequential 8-way rotation. In this mode, a

device receives the lowest priority after being serviced. In the worst case, a device

requesting an interrupt has to wait until each of seven other devices are serviced at

most once.

There are two ways to accomplish automatic rotation using OCW2; the Rotation on

Non-Specific EOI Command (R=1, SL=0, EOI=1) and the rotate in automatic EOI mode

which is set by (R=1, SL=0, EOI=0).

5.8.4.4 Specific Rotation Mode (Specific Priority)

Software can change interrupt priorities by programming the bottom priority. For

example, if IRQ5 is programmed as the bottom priority device, then IRQ6 is the highest

priority device. The Set Priority Command is issued in OCW2 to accomplish this, where:

R=1, SL=1, and LO–L2 is the binary priority level code of the bottom priority device.

In this mode, internal status is updated by software control during OCW2. However, it

is independent of the EOI command. Priority changes can be executed during an EOI

command by using the Rotate on Specific EOI Command in OCW2 (R=1, SL=1, EOI=1

and LO–L2=IRQ level to receive bottom priority.

5.8.4.5 Poll Mode

Poll mode can be used to conserve space in the interrupt vector table. Multiple

interrupts that can be serviced by one inter rupt serv ice routine do not need separate

vectors if the service routine uses the poll command. Poll mode can also be used to

expand the number of interrupts. The polling interrupt service routine can call the

appropriate service routine, instead of providing the interrupt vectors in the vector

table. In this mode, the INTR output is not used and the microprocessor internal

Interrupt Enable flip-flop is reset, disabling its interrupt input. Service to devices is

achieved by software using a Poll command.

The Poll command is issued by setting P=1 in OCW3. The PIC treats its next I/O read as

an interrupt acknowledge, sets the appropriate ISR bit if there is a request, and reads

the priority level. Interrupts are frozen from the OCW3 write to the I/O read. The byte

returned during the I/O read contains a 1 in bit 7 if there is an interrupt, and the binary

code of the highest priority level in bits 2:0.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 143

Functional Description

5.8.4.6 Cascade Mode

The PIC in the ICH9 has one master 8259 and one slave 8259 cascaded onto the

master through IRQ2. This configuration can ha ndle up to 15 separate priority levels.

The master controls the slaves through a three bit internal bus. In the ICH9, when the

master drives 010b on this bus, the slave controller takes responsibility for returning

the interrupt vector. An EOI command must be issued twice: once for the master and

once for the slave.

5.8.4.7 Edge and Level Triggered Mode

In ISA systems this mode is programmed using bit 3 in ICW1, which sets lev el or edge

for the entire controller. In the ICH9, this bit is disabled and a new register for edge and

level triggered mode selection, per interrupt input, is inc luded. This i s the Edge/Level

control Registers ELCR1 and ELCR2.

If an ELCR bit is 0, an interrupt request will be recognized by a low-to-high transition

on the corresponding IRQ input. The IRQ input can remain high without generating

another interrupt. If an ELCR bit is 1, an interrupt request will be recognized by a high

level on the corresponding IRQ input and there is no need for an edge detection. The

interrupt request must be removed before the EOI command is issued to prevent a

second interrupt from occurring.

In both the edge and level triggered modes, the IRQ inputs must remain active until

after the falling edge of the first internal INTA#. If the IRQ input goes inactive before

this time, a default IRQ7 vector is returned.

5.8.4.8 End of Interrupt (EOI) Operations

An EOI can occur in one of two fashions: by a command word write issued to the PIC

before returning from a service routine, the EOI command; or automatically when AEOI

bit in ICW4 is set to 1.

5.8.4.9 Normal End of Interrupt

In normal EOI, software writes an EOI command before leaving the interrupt service

routine to mark the interrupt as completed. There are two forms of EOI commands:

Specific and

Non-Specific. When a Non-Specific EOI command is issued, the PIC clears the highest

ISR bit of those that are set to 1. Non-Specific EOI is the normal mode of operation of

the PIC within the ICH9, as the interrupt being serviced currently is the interrupt

entered with the interrupt acknowledge. When the PIC is operated in modes that

preserve the fully nested structure, software can determine which ISR bit to clear by

issuing a Specific EOI. An ISR bit that is masked is not cleared by a Non- Specific EOI if

the PIC is in the special mask mode. An EOI command must be issued for both the

master and slave controller.

5.8.4.10 Automatic End of Interrupt Mode

In this mode, the PIC automatically performs a Non-Specific EOI operation at the

trailing edge of the last interrupt acknowledge pulse. From a system standpoint, this

mode should be used only when a nested mu lti-level interrupt structure is not required

within a single PIC. The AEOI mode can only be used in the master controller and not

the slave controller.

Functional Description

144 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.8.5 Masking Interrupts

5.8.5.1 Masking on an Individual Interrupt Request

Each interrupt request can be masked individually by the Interrupt Mask Register

(IMR). This register is programmed through OCW1. Each bit in the IMR masks one

interrupt channel. Masking IRQ2 on the master controller masks all requests for service

from the slave controller.

5.8.5.2 Special Mask Mode

Some applications may require an interrupt service routine to dynamically alter the

system priority structure during its execution under softw are control. For example, th e

routine may wish to inhibit lower priority requests for a portion of its execution but

enable some of them for another portion.

The special mask mode enables all interrupts not masked by a bit set in the Mask

issuing an EOI to clear the ISR bit, the interrupt controller inhibits all lower priority

requests. In the special mask mode, any interrupts may be selectively enabled by

loading the Mask Register with the appropriate pattern. The special mask mode is set

by OCW3 where: SSMM=1, SMM=1, and cleared where SSMM=1, SMM=0.

5.8.6 Steering PCI Interrupts

The ICH9 can be programmed to allow PIRQA#-PIRQH# to be routed internally to

interrupts 3–7, 9–12, 14 or 15. The assignment is programmable through the PIRQx

Route Control registers, located at 60–63h and 68–6Bh in Device 31:Function 0. One or

more PIRQx# lines can be routed to the same IRQx input. If interrupt steering is not

required, the Route registers can be programmed to disable steering.

The PIRQx# lines are defined as active low, level sensitive to allow multiple interrupts

on a PCI board to share a single line across the connector. When a PIRQx# is ro uted to

specified IRQ line, software must change the IRQ's corresponding ELCR bit to level

sensitive mode. The ICH9 internally inverts the PIRQx# line to send an activ e high level

to the PIC. When a PCI interrupt is routed onto the PIC, the selected IRQ can no longer

be used by an active high device (through SERIRQ). However, active low interrupts can

share their interrupt with PCI interrupts.

Internal sources of the PIRQs, including SCI and TCO interrupts, cause the ex ternal

PIRQ to be asserted. The ICH9 receives the PIRQ input, like all of the other external

sources, and routes it accordingly.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 145

Functional Description

5.9 Advanced Programmable Interrupt Controller

(APIC) (D31:F0)

In addition to the standard ISA-compatible PIC described in the previous chapter, the

ICH9 incorporates the APIC. While the standard interrupt controller is intended for use

in a uni-processor system, APIC can be used in either a uni-processor or multi-

processor system.

5.9.1 Interrupt Handling

The I/O APIC handles interrupts very differently than the 8259. Briefly, these

differences are:

•Method of Interrupt Transmission. The I/O APIC transmits interrupts through

memory writes on the normal datapath to the processor, and interrupts are handled

without the need for the processor to run an interrupt acknowledge cycle.

•Interrupt Priority. The priority of interrupts in the I/O APIC is independent of the

interrupt number. For example, interrupt 10 can be given a higher priority than

interrupt 3.

•More Interrupts. The I/O APIC in the ICH9 supports a total of 24 interrupts.

•Multiple Interrupt Controllers. The I/O APIC architecture allows for multiple I/O

APIC devices in the system with their own interrupt vectors.

5.9.2 Interrupt Mapping

The I/O APIC within the ICH9 supports 24 APIC interrupts. Each interrupt has its own

unique vector assigned by software. The interrupt vectors are mapped as follows, and

match “Config 6” of the Multi-Processor Specification.

Table 5-16. APIC Interrupt Mapping1 (Sheet 1 of 2)

IRQ # Via

SERIRQ Direct

from Pin Via PCI

Message Internal Modules

0NoNoNoCascade from 8259 #1

1Yes No Yes

2 No No No 8254 Counter 0, HPET #0 (legacy mode)

3Yes No Yes

4Yes No Yes

5Yes No Yes

6Yes No Yes

7Yes No Yes

8NoNoNoRTC, HPET #1 (legacy mode)

9 Yes No Yes Option for SCI, TCO

10 Yes No Yes Option for SCI, TCO

11 Yes No Yes HPET #2, Option for SCI, TCO (Note2)

12 Yes No Yes HPET #3 (Note 3)

13 No No No FERR# logic

14 Yes No Yes SATA Primary (legacy mode)

15 Yes No Yes SATA Sec on d ary (legacy mode)

Functional Description

146 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. When programming the polarity of internal interrupt sources on the APIC, interrupts 0

through 15 receive active-high internal interrupt sources, while interrupts 16 through 23

receive active-low internal interrupt sources.

2. If IRQ 11 is used for HPET #2, software shou ld ensure IRQ 11 is not shared with any other

devices to ensure the proper operation of HPET #2. ICH9 hardware does not prevent

sharing of IRQ 11.

3. If IRQ 12 is used for HPET #3, software shou ld ensure IRQ 12 is not shared with any other

devices to ensure the proper operation of HPET #3. ICH9 hardware does not prevent

sharing of IRQ 12.

4. PIRQ[E:H] are Mul tiplexed with GPIO pins. Interrupt s PIRQ[E:H] will not be exposed if they

are configured as GPIOs.

5.9.3 PCI / PCI Express* Message-Based Interrupts

When external devices through PCI / PCI Express wish to gener ate an interrupt, they

will send the message defined in the PCI Express* Base Specification, Revision 1.0a for

generating INT A# - INTD#. These will be translated internal assertions/de-assertions of

INTA# - INTD#.

5.9.4 Front Side Bus Interrupt Delivery

For processors that support Front Side Bus (FSB) interrupt delivery, the ICH9 requires

that the I/O APIC deliver interrupt messages to the processor in a parallel manner,

rather than using the I/O APIC seri al s c he me.

This is done by the ICH9 writing (via DMI) to a memory location that is snooped by the

processor(s). The processor(s) snoop the cycle to know which interrupt goes active.

The following sequence is used:

1. When the ICH9 detects an interrupt ev ent (active edge for edge-triggered mode or

a change for level-triggered mode), it sets or resets the internal IRR bit associated

with that interrupt.

2. Internally, the ICH9 requests to use the bus in a way that automatically flushes

upstream buffers. This can be internally implemented similar to a DMA device

request.

3. The I CH9 then deliv ers the message by performi ng a write cy cle to the appropriate

address with the appropriate data. The address and data formats are described

below in Section 5.9.4.4.

Note: FSB Interrupt Delivery compatibility with processor clock control depends on the

processor, not the ICH9.

16 PIRQA# PIRQA#

Yes Internal devices are routable; see

Section 10.1.56 though Section 10.1.62.

17 PIRQB# PIRQB#

18 PIRQC# PIRQC#

19 PIRQD# PIRQD#

20 N/A PIRQE#4

Yes Option for SCI, TCO, HPET #0,1,2, 3. Other

internal devices are routable; see

Section 10.1.56 through Section 10.1.62.

21 N/A PIRQF#4

22 N/A PIRQG#4

23 N/A PIRQH#4

Table 5-16. APIC Interrupt Mapping1 (Sheet 2 of 2)

IRQ # Via

SERIRQ Direct

from Pin Via PCI

Message Internal Modules

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 147

Functional Description

5.9.4.1 Edge-Triggered Operation

In this case, the “Assert Message” is sent when there is an inactive-to-active edge on

the interrupt.

5.9.4.2 Level-Triggered Op eration

In this case, the “Assert Message” is sent when there is an inactive-to-active edge on

the interrupt. If after the EOI the interrupt is still active, then another “ Assert Message”

is sent to indicate that the interrupt is still active.

5.9.4.3 Registers Associated with Front Side Bus Interrupt Delivery

Capabilities Indication: The capability to support Front Side Bus interrupt delivery is

indicated via ACPI configuration techniques. This involves the BIOS creating a data

structure that gets reported to the ACPI configuration software.

5.9.4.4 Interrupt Message Format

The ICH9 writes the message to PCI (and to the Host controller) as a 32-bit memory

write cycle. It uses the formats shown in Table 5-17 and Table 5-18 for the address and

data.

The local APIC (in the processor) has a delivery mode option to interpret Front Side Bus

messages as a SMI in which case the processor treats the incoming interrupt as a SMI

instead of as an interrupt. This does not mean that the ICH9 has any way to ha ve a SMI

source from ICH9 power management logic cause the I/O APIC to send an SMI

message (there is no way to do this). The ICH9’s I/O APIC can only send interrupts due

to interrupts which do not include SMI, NMI or INIT. This means that in IA -32/Intel® 64

based platforms, Front Side Bus interrupt message format delivery modes 010 (SMI/

PMI), 100 (NMI), and 101 (INIT) as indicated in this section, must not be used and is

not supported. Only the hardware pin connection is supported by ICH9.

Table 5-17. Interrupt Message Address Format

Bit Description

31:20 Will always be FEEh

19:12 Destination ID: This is the same as bits 63:56 of the I/O Redirection Table entry for

the interrupt associated with this message.

11:4 Extended Destination ID: This is the same as bits 55:48 of the I/O Redirection

Table entry for the interrupt associated with this message.

Redirection Hint: This bit is used by the processor host bridge to allow the interrupt

message to be redirected.

0 = The message will be delivered to the agent (processor) listed in bits 19:12.

1 = The message will be delivered to an agent with a lower interrupt priority This can

be derived from bits 10:8 in the Data Field (see below).

The Redirection Hint bit will be a 1 if bits 10:8 in the delivery mode field associated

with corresponding interrupt are encoded as 001 (Lowest Priority). Otherwise, the

Redirection Hint bit will be 0

Destination Mode: This bit is used only the Redirection Hint bit is set to 1. If the

Redirection Hint bit and the Destination Mode bit are both set to 1, then the logical

destination mode is used, and the redirection is limited only t o those processors that

are part of the logical group as based on the logical ID.

1:0 Will always be 00.

Functional Description

148 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.9.5 IOxAPIC Address Remapping

In order to support Intel® Virtualization Technology , interrupt messages are required to

go through similar address remapping as any other memory request. Address

remapping allows for domain isolation for interrupts, so a device assigned in one

domain is not allowed to generate an interrupt to another domain.

The address remapping is based on the Bus: Device: Function field associated with the

requests. The internal APIC is required to initiate the interrupt message using a unique

Bus: Device: function.

ICH9 allows BIOS to program the unique Bus: Device: Function address for the internal

APIC. This address field does not change the APIC functionality and the APIC is not

promoted as a stand-alone PCI device. See Device 31: Function 0 Offset 6Ch for

additional information.

5.9.6 External Interrupt Controller Support

The ICH9 supports external APICs off of PCI Express ports, and does not support APICs

on the PCI bus. The EOI special cycle is only forwarded to PCI Express ports.

Table 5-18. Interrupt Message Data Format

Bit Description

31:16 Will always be 0000h.

15 Trigger Mode: 1 = Level, 0 = Edge. Same as the corresponding bit in the I/O

Redirection Table for that interrupt.

14 Delivery Status: 1 = Assert, 0 = Deassert. Only Assert messages are sent. This bit

is always 1.

13:12 Will always be 00

11 Destination Mode: 1 = Logical. 0 = Physical. Same as the corresponding bit in the

I/O Redirection Table for that interrupt.

10:8

Delivery Mode: This is the same as the corresponding bits in the I/O Redirection

Table for that interrupt.

000 = Fixed 100 = NMI

001 = Lowest Priority 101 = INIT

010 = SMI/PMI 110 = Reserved

011 = Reserved 111 = ExtINT

7:0 Vector: This is the same as the corresponding bits in the I/O Redirection Table for

that interrupt.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 149

Functional Description

5.10 Serial Interrupt (D31:F0)

The ICH9 supports a serial IRQ scheme. This allows a single signal to be used to report

interrupt requests. The signal used to transmit this information is shared between the

host, the ICH9, and all peripherals that support serial interrupts. The signal line,

SERIRQ, is synchronous to PCI clock, and follows the sustained tri-state protocol that is

used by all PCI signals. This means that if a device has driven SERIRQ low, it will first

drive it high synchronous to PCI clock and release it the following PCI clock. The serial

IRQ protocol defines this sustained tri-state signaling in the following fashion:

•S – Sample Phase. Signal driven low

•R – Recovery Phase. Signal driven high

•T – Turn-around Phase. Signal released

The ICH9 supports a message for 21 serial interrupts. These represent the 15 ISA

interrupts (IRQ0–1, 2–15), the four PCI interrupts, and the control signals SMI# and

IOCHK#. The serial IRQ protocol does not support the additional APIC interrupts (20–

23).

Note: When the SATA controller is configured for legacy IDE mode, IRQ14 and IRQ15 are

expected to behave as ISA legacy interrupts, which cannot be shared, i.e. through the

Serial Interrupt pin. If IRQ14 and IRQ15 are shared with Serial Interrupt pin then

abnormal system behavior may occur. For example, IRQ14/15 may not be detected by

ICH9's interrupt controller. When the SA T A controller is not running in Native IDE mode,

IRQ14 and IRQ15 are used as special interrupts. If the SATA controller is in native

modes, these interrupts can be mapped to other devices accordingly.

5.10.1 Start Frame

The serial IRQ protocol has two modes of operation which affect the start frame. These

two modes are: Continuous, where the ICH9 is solely responsible for generating the

start frame; and Quiet, where a serial IRQ peripheral is responsible for beginning the

start frame.

The mode that must first be entered when enabling the serial IRQ protocol is

continuous mode. In this mode, the ICH9 asserts the start frame. This start fr ame is 4,

6, or 8 PCI clocks wide based upon the Serial IRQ Control Register, bits 1:0 at 64h in

Device 31:Function 0 configuration space. This is a polling mode.

When the serial IRQ stream enters quiet mode (signaled in the Stop Frame), the

SERIRQ line remains inactive and pulled up between the Stop and Start Frame until a

peripheral drives the SERIRQ signal low. The ICH9 senses the line low and continues to

drive it low for the remainder of the Start Frame. Since the first PCI clock of the start

frame was driven by the peripheral in this mode, the ICH9 drives the SERIRQ line low

for 1 PCI clock less than in continuous mode. This mode of operation allows for a quiet,

and therefore l owe r power, operati on.

Functional Description

150 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.10.2 Data Frames

Once the Start frame has been initiated, all of the SERIRQ peripherals must start

counting frames based on the rising edge of SERIRQ. Each of the IRQ/DAT A fr ames has

exactly 3 phases of 1 clock each:

•Sample Phase. During this phase, the SERIRQ device drives SERIRQ low if the

corresponding interrupt signal is low. If the corresponding interrupt is high, then

the SERIRQ devices tri-state the SERIRQ signal. The SERIRQ line remains high due

to pull-up resistors (there is no internal pull-up resistor on this signal, an external

pull-up resistor is required). A low level during the IRQ0–1 and IRQ2–15 frames

indicates that an active-high ISA interrupt is not being requested, but a low level

during the PCI INT[A:D], SMI#, and IOCHK# frame indicates that an active-low

interrupt is being requested.

•Recovery Phase. During this phase, the device drives the SERIRQ line high if in

the Sample Phase it was driven low. If it was not driven in the sample phase, it is

tri-stated in this phase.

•Turn-around Phase. The device tri-states the SERIRQ line

5.10.3 Stop Frame

After all data frames, a Stop Frame is driven by the ICH9. The SERIRQ signal is driven

low by the ICH9 for 2 or 3 PCI clocks. The number of clocks is determined by the

SERIRQ configuration register. The number of clocks determines the next mode:

5.10.4 Specific Interrupts Not Supported via SERIRQ

There are three interrupts seen through the serial stream that are not supported by the

ICH9. These interrupts are generated internally, and are not sharable with other

devices within the system. These interrupts are:

• IRQ0. Heartbeat interrupt ge nerated off of the internal 8254 counter 0.

• IRQ8#. RTC interrupt can only be generated internally.

• IRQ13. Floating point error interrupt generated off of the processor assertion of

FERR#.

The ICH9 ignores the state of these interrupts in the serial stream, and does not adjust

their level based on the level seen in the serial stream.

Table 5-19. Stop Frame Explanation

Stop Frame Width Next Mode

2 PCI clocks Quiet Mode. Any SERIRQ device may initiate a Start Frame

3 PCI clocks Continuous Mode. Only the host (Intel® ICH9) may initiate a Start

Frame

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 151

Functional Description

5.10.5 Data Frame Format

Table 5-20 shows the format of the data frames. For the PCI interrupts (A–D), the

output from the ICH9 is AND’d with the PCI input signal. This way, the interrupt can be

signaled via both the PCI interrupt input signal and via the SERIRQ signal (they are

shared).

Table 5-20. Data Frame Format

Data

Frame

#Interrupt Clocks Past

Start

Frame Comment

1IRQ0 2

Ignored. IRQ0 can only be generated via the internal

8524

2IRQ1 5

3 SMI# 8 Causes SMI # if low. Will set the SERIRQ_SMI_STS bit.

4IRQ3 11

5IRQ4 14

6IRQ5 17

7IRQ6 20

8IRQ7 23

9 IRQ8 26 Ignored. IRQ8# can only be generated internally.

10 IRQ9 29

11 IRQ10 32

12 IRQ11 35

13 IRQ12 38

14 IRQ13 41 Ignored. IRQ13 can only be generated from FERR#

15 IRQ1 4 44 N ot attached to SATA logic

16 IRQ1 5 47 N ot attached to SATA logic

17 IOCHCK# 50 Same as ISA IOCHCK# going active.

18 PCI INTA# 53 Drive PIRQA#

19 PCI INTB# 56 Drive PIRQB#

20 PCI INTC# 59 Drive PIRQ C#

21 PCI INTD# 62 Drive PIRQD#

Functional Description

152 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.11 Real Time Clock (D31:F0)

The Re al Time Clock (RT C) module provides a battery backed-up d ate and time keeping

device with two banks of static RAM with 128 bytes each, although the first bank has

114 bytes for general purpose usage. Three interrupt features are available: time of

day alarm with once a second to once a month range, periodic rates of 122 µs to

500 ms, and end of update cycle notification. Seconds, minutes, hours, days, day of

week, month, and year are counted. Daylight savings compensation is no longer

supported. The hour is represented in twelve or twenty-four hour format, and data can

be represented in BCD or binary format. T he design is functionally compatible with the

Motorola MS146818B. The time keeping comes from a 32.768 kHz oscillating source,

which is divided to achieve an update every second. The lower 14 bytes on the lower

RAM block has very specific functions. The first ten are for time and date information.

The next four (0Ah to 0Dh) are registers, which configure and report RTC functions.

The time and calendar data should match the data mode (BCD or binary) and hour

mode (12 or 24 hour) as selected in register B. It is up to the programmer to make

sure that data stored in these locations is within the reasonable values ranges and

represents a possible date and time. The exception to these ranges is to store a value

of C0–FFh in the Alarm bytes to indicate a don’t care situation. All Alarm conditions

must match to trigger an Alarm Flag, which could trigger an Alarm Interrupt if enabled.

The SET bit must be 1 while programming these locations to avoid clashes with an

update cycle. Access to time and date information is done through the RAM locations. If

a RAM read from the ten time and date bytes is attempted during an update cycle, the

value read do not necessarily represent the true contents of those locations. Any RAM

writes under the same conditions are ignored.

Note: The leap year determination for adding a 29th day to February does not take into

account the end-of-the-century exceptions. The logic simply assumes that all years

divisible by 4 are leap years. According to the Ro yal Observ atory Greenwich, y ears that

are divisible by 100 are typically not leap years. In every fourth century (years divisible

by 400, like 2000), the 100-year-exception is over-ridden and a leap-year occurs. Note

that the year 2100 will be the first time in which the current RTC implementation would

incorrectly calculate the leap-year.

The ICH9 does not implem ent month/year alarms.

5.11.1 Update Cycles

An update cycle occurs once a second, if the SET bit of register B is not asserted and

the divide chain is properly configured. During this procedure, the stored time and date

are incremented, overflow is checked, a matching alarm condition is checked, and the

time and date are rewritten to the RAM locations. The update cycle will start at least

488 µs after the UIP bit of register A is asserted, and the entire cycle does not take

more than 1984 µs to complete. The time and date RAM locations (0–9) are

disconnected from the external bus during this time.

To avoid update and data corruption conditions, external RAM access to these locations

can safely occur at two times. When a updated-ended interrupt is detected, almost 999

ms is available to read and write the valid time and date data. If the UIP bit of Register

A is detected to be low, there is at least 488 µs before the update cycle begins.

Warning: The overflow conditions for leap years adjustments are based on more than one date or

time item. To ensure proper operation when adjusting the time, the new time and data

values should be set at least two seconds before leap year occurs.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 153

Functional Description

5.11.2 Interrupts

The real-time clock interrupt is internally routed within the ICH9 both to the I/O APIC

and the 8259. It is mapped to interrupt vector 8. This interrupt does not leave the

ICH9, nor is it shared with any other interrupt. IRQ8# from the SERIRQ stream is

ignored. However, the High Performance Event Timers can also be mapped to IRQ8#;

in this case, the RTC interrupt is blocked.

5.11.3 Lockable RAM Ranges

The RTC’s battery-backed RAM supports two 8-byte ranges that can be locked via the

configuration space. If the locking bits are set, the corresponding r ange in the RAM will

not be readable or writable. A write cycle to those locations will have no effect. A read

cycle to those locations will not return the location’s actual value (resultant value is

undefined).

Once a range is locked, the range can be unlocked only by a hard reset, which will

invoke the BIOS and allow it to relock the RAM range.

5.11.4 Century Rollover

The ICH9 detects a rollover when the Year byte (RTC I/O space, index offset 09h)

transitions form 99 to 00. Upon detecting the rollover, the ICH9 sets the

NEWCENTURY_STS bit (TCOBASE + 04h, bit 7). If the system is in an S0 state, this

causes an SMI#. The SMI# handler can update registers in the RTC RAM that are

associated with century value. If the system is in a sleep state (S1–S5) when the

century rollover occurs, the ICH9 also sets the NEWCENTURY_STS bit, but no SMI# is

generated. When the system resumes from the sleep state, BIOS should check the

NEWCENTURY_STS bit and update the century value in the RTC RAM.

5.11.5 Clearing Battery-Backed RTC RAM

Clearing CMOS RAM in an ICH9-based platform can be done by using a jumper on

RTCRST# or GPI. Implementations should not attempt to clear CMOS by using a

jumper to pull VccRTC low.

Using RTCRST# to Clear CMOS

A jumper on RTCRST# can be used to clear CMOS values, as well as reset to default,

the state of those configuration bits that reside in the RTC power well. When the

RTCRST# is strapped to ground, the RTC_PWR_STS bit (D31:F0:A4h bit 2) will be set

and those configuration bits in the RTC power well will be set to their default state.

BIOS can monitor the state of this bit, and manually clear the RT C CMOS array once the

system is booted. The normal position would cause R T CRST# to be pulled up through a

weak pull-up resistor. Table 5-21 shows which bits are set to their default state when

R TCRST# is asserted. This RTCRST# jumper technique allows the jumper to be moved

and then replaced—all while the system is powered off. Then, once booted, the

RTC_PWR_STS can be detected in the set state.

Functional Description

154 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 5-21. Configuration Bits Re set by RTCRST # Assertion (Sheet 1 of 2)

Bit Name Register Location Bit(s) Default

State

Alarm Interrupt

Enable (AIE)

Regi ster B (Gener al

Configuration)

(RTC_REGB)

I/O space (RTC Index +

0Bh) 5X

Alarm Flag (AF) Register C (Flag

(RTC_REGC)

I/O space (RTC Index +

0Ch) 5X

SWSMI_RATE_SEL

General PM

Configuration 3

GEN_PMCON_3

D31:F0:A4h 7:6 0

SLP_S4# Minimum

Assertion Width

General PM

Configuration 3

GEN_PMCON_3

D31:F0:A4h 5:4 0

SLP_S4# Assertion

Stretch Enable

General PM

Configuration 3

GEN_PMCON_3

D31:F0:A4h 3 0

RTC Power Status

(RTC_PWR_STS)

General PM

Configuration 3

GEN_PMCON_3

D31:F0:A4h 2 0

Power Failure

(PWR_FLR)

General PM

Configuration 3

(GEN_PMCON_3)

D31:F0:A4h 1 0

AFTERG3_EN

General PM

Configuration 3

GEN_PMCON_3

D31:F0:A4h 0 0

Power Button Override

Status

(PWRBTNOR_STS)

Power Management 1

Status Register

(PM1_STS) PMBase + 00h 11 0

RTC Event Enable

(RTC_EN)

Power Management 1

Enable Register

(PM1_EN) PMBase + 02h 10 0

Sleep Type (SLP_TYP) Power Management 1

Control (PM1_CNT) PMBase + 04h 12:10 0

PME_EN General Purpose

Event 0 Enables

BATLOW_EN

(Mobile On ly)

General Purpose

Event 0 Enables

RI_EN General Purpose

Event 0 Enables

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 155

Functional Description

Using a GPI to Clear CMOS

A jumper on a GPI can also be used to clear CMOS values. BIOS would detect the

setting of this GPI on system boot-up , and manually clear the CMOS arr a y.

Note: The GPI strap technique to clear CMOS requires multiple steps to implement. The

system is booted with the jumper in new position, then powered back down. The

jumper is replaced back to the normal position, then the system is rebooted again.

Warning: Clearing CMOS, using a jumper on VccRTC, must not be implemented.

5.12 Processor Interface (D31:F0)

The ICH9 interfaces to the processor with a variety of signals

• Standard Outputs to processor: A20M#, SMI#, NMI, INIT#, INTR, STPCLK#,

IGNNE#, CPUPWRGD, DPSLP# (Mobile Only)

• Standard Input from processor: FERR#, THRMTRIP#

• Intel SpeedSte p® technology output to processor: CPUPWRGD (Mobile Only)

Most ICH9 outputs to the processor use standard buffers. The ICH9 has separate

V_CPU_IO signals that are pulled up at the system level to the processor voltage, and

thus determines VOH for the outputs to the processor.

5.12.1 Processor Interface Signals

This section describes each of the signals that interface between the ICH9 and the

processor(s). Note that the behavior of some signals may vary during processor reset,

as the signals are used for frequency strapping.

5.12.1.1 A20M# (Mask A20)

The A20M# signal is active (low) when both of the following conditions are true:

• The ALT_A20_GATE bit (Bit 1 of PORT92 register) is a 0

• The A20GATE input signal is a 0

The A20GATE input signal is expected to be generated by the external microcontroller

(KBC).

NEWCENTURY_STS TCO1 Status Register

(TCO1_STS) TCOBa se + 04h 7 0

Intruder Dete ct

(INTRD_DET) TCO2 Status Register

(TCO2_STS) TCOBa se + 06h 0 0

Top Swap (TS) Backed Up Control

Regist er (BUC) Chipset Config

Registers:Offset 3414h 0X

Table 5-21. Configuration Bits Reset by RTCRST# Assertion (Sheet 2 of 2)

Bit Name Register Location Bit(s) Default

State

Functional Description

156 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.12.1.2 INIT# (Initialization)

The INIT# signal is active (driven low) based on any one of sev eral events described in

Table 5-22. When any of these events occur, INIT# is driven low for 16 PCI clocks, then

driven high.

Note: The 16-clock counter for INIT# assertion halts while STPCLK# is active. Therefore, if

INIT# is supposed to go active while STPCLK# is asserted, it actually goes active after

STPCLK# goes inactiv e .

This section refers to INIT#, but applies to two signals: INIT# and INIT3_3V#

(Desktop Only), as INIT3_3V# (Desktop Only) is functionally identical to INIT#, but

signaling at 3.3 V.

5.12.1.3 FERR#/IGNNE# (Numeric Coprocessor Error/ Ignore Numeric Error)

The ICH9 supports the coprocessor error function with the FERR#/IGNNE# pins. The

function is enabled via the COPROC_ERR_EN bit (Chipset Config Registers:Offset

31FFh:bit 1). FERR# is tied directly to the Coprocessor Error signal of the processor. If

FERR# is driven active by the processor, IRQ13 goes active (internally). When it

detects a write to the COPROC_ERR register (I/O Register F0h), the ICH9 negates the

internal IRQ13 and drives IGNNE# active. IGNNE# remains active until FERR# is driven

inactive. IGNNE# is never driven active unless FERR# is active.

Table 5-22. INIT# Going Active

Cause of INIT# Going Active Comment

Shutdown special cycle from processor observed

on ICH-GMCH interconnect (from GMCH). INIT# assertion based on value of

Shutdown Policy Select register (SPS)

PORT92 write, where INIT_NOW (bit 0) tr ansitions

from a 0 to a 1.

PORTCF9 write, where SYS_RS T (bit 1) was a 0

and RST_CPU (bit 2) transitions from 0 to 1.

RCIN# input signal goes low. RCIN# is expected

to be driven by the external microcontroller

(KBC).

0 to 1 transition on RCIN# must occur

before the Intel® ICH9 will arm INIT# to be

generated again.

NOTE: RCIN# signal is expected to be low

during S3, S4, and S5 states.

Transition on the RCIN# signal in

those states (or the transition to

those states ) may not necessarily

cause the INIT# signal to be

generated to the processor.

CPU BIST To enter BIST, software sets CPU_BIST_EN

bit and then does a full processor reset

using the CF9 register.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 157

Functional Description

If COPROC_ERR_EN is not set, the assertion of FERR# will not generate an internal

IRQ13, nor will the write to F0h generate IGNNE#.

5.12.1.4 NMI (Non-Maskable Interrupt)

Non-Maskable Interrupts (NMIs) can be generated by several sources, as described in

Table 5-23.

5.12.1.5 Stop Clock Request (STPCLK#)

The ICH9 power management logic controls this active-low signal. Refer to

Section 5.13 for more information on the functionality of this signal.

5.12.1.6 CPU Power Good (CPUPWRGD)

This signal is connected to the processor’s PWRGOOD input. This signal represents a

logical AND of the ICH9’s PWROK and VRMPWRGD signals.

5.12.1.7 Deeper Sleep (DPSLP#) (Mobile Only)

This active-low signal controls the internal gating of the processor’s core clock. This

signal asserts before and deasserts after the STP_CPU# signal to effectively stop the

processor’s clock (internally) in the states in which STP_CPU# can be used to stop the

processor’s clock externally.

Figure 5-5. Coprocessor Error Timing Diagram

FERR#

Internal IRQ13

I/O Write to F0h

IGNNE#

Table 5-23. NMI Sources

Cause of NMI Comment

SERR# goes active (either inter nally,

externally via SERR# signal, or via

message from (G)MCH)

Can instead be routed to generate an SCI, through

the NMI2SCI_EN bit (Device 31:Function 0, TCO

Base + 08h, bit 11).

IOCHK# goes active via SERIRQ# stream

(ISA system Error)

Can instead be routed to generate an SCI, through

the NMI2SCI_EN bit (Device 31:Function 0, TCO

Base + 08h, bit 11).

Functional Description

158 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.12.2 Dual-Processor Issues (Desktop Only)

5.12.2.1 Signal Differences

In dual-processor designs, some of the processor signals are unused or used differently

than for uniprocessor designs.

5.12.2.2 Power Management

For multiple-processor (or Multiple-core) configurations in which more than one Stop

Grant cycle ma y be gener ated, the (G)MCH is expected to count Stop Gr ant cy cles and

only pass the last one through to the ICH9. This prevents the ICH9 from getting out o f

sync with the processor on multiple STPCLK# assertions.

Because the S1 state will have the STPCLK# signal active, the STPCLK# signal can be

connected to both processors. However, for ACPI implementations, the BIOS must

indicate that the ICH9 only supports the C1 state for dual-processor designs.

In going to the S1 state for desktop, multiple Stop-Grant cycles will be generated by

the processors. It is assumed that prior to setting the SLP_EN bit (which causes the

transition to the S1 state), the processors will not be executing code that is likely to

delay the Stop-Grant cycles.

In going to the S3, S4, or S5 states, the system will appear to pass through the S1

state; thus, STPCLK# and SLP# are also used. During the S3, S4, and S5 states, both

processors will lose power. Upon exit from those states, the processors will have their

power restored.

Table 5-24. DP Signal Differences

Signal Difference

A20M# / A20GATE Generally not used, but still supported by Intel® ICH9.

STPCLK# Used for S1 State as well as preparation for entry to S3–S5

Also allows for THERM# based throttling (not via ACPI control methods).

Should be connected to both processors.

FERR# / IGNNE# Generally not used, but still supported by ICH9.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 159

Functional Description

5.13 Power Management (D31:F0)

5.13.1 Features

• Support for Advanced Configuration and Power Interface, Version 3.0a (ACPI)

providing power and thermal management

— ACPI 24-Bit Timer

— Software initiated throttling of processor performance for Thermal and Power

Reduction

— Hardware Override to throttle processor performance if system too hot

—SCI and SMI# Generation

— ACPI C2 state Stop-Grant state (using STPCLK# signal) halts processor’s

instruction stream

• PCI PME# signal for Wake Up from Low-Power states

• System Clock Control

— (Mobile Only) ACPI C3 State: Ability to halt processor clock (but not memory

clock)

— (Mobile Only) ACPI C4 State: Ability to lower processor voltage.

— (Mobile Only) CLKRUN# Protocol for PCI Clock Starting/Stopping

• System Sleep State Control

— ACPI S1 state: Stop Grant (using STPCLK# signal) halts processor’s in struction

stream (only STPCLK# active)

— ACPI S3 state — Suspend to RAM (STR)

— ACPI S4 state — Suspend-to-Disk (STD)

— ACPI G2/S5 state — Soft Off (SOFF)

— Power Failure Detection and Recovery

• Management Engine Power Management Support

— New Wake events from the Management Engine (enabled from all S-States

including Catastrophic S5 conditions)

• Streamlined Legacy Power Management for APM-Based Systems

5.13.2 Intel® ICH9 and System Power States

Table 5-25 shows the power states defined for ICH9-based platforms. The state names

generally match the corresponding ACPI states.

Functional Description

160 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 5-25. General Power States for Systems Using Intel® ICH9

State/

Substates Legacy Name / Description

G0/S0/C0

Full On: Processor operating. Individual devices may be shut down to save

power. The different processor operating levels are defined by Cx states, as

shown in Table 5-26. Within the C0 state, the Intel® ICH9 can throttle the

processor using the STPCLK# signal to reduce power consumption. The thrott ling

can be initiated by software or by the operating system or BIOS.

G0/S0/C1 Auto-Halt: Processor has executed an AutoHalt instruction and is not executing

code. The processor snoops the bus and maintains cache coherency.

G0/S0/C2

Stop-Grant: The STPCLK# signal goes active to the processor. The processor

performs a Stop-Grant cycle, halts its instruction stream, and remains in that

state until the STPCLK# signal goes inactive. In the Stop-Grant state, the

processor snoops the bus and maintains cache coherency.

G0/S0/C3

(Mobile

Only)

Stop-Clock: The STPCLK# signal goes active t o the processor. The processor

performs a Stop-Grant cycle, halts its instruction stream. ICH9 then asserts

DPSLP# followed by STP_CPU#, which forces the clock generator to stop the

processor clock. This is also used for Intel SpeedStep® technology support.

Accesses to memory (b y graphics, PCI, or inte rnal units) is not permitt ed while in

a C3 state.

G0/S0/C4

(Mobile

Only)

Stop-Clock with Lower Processor Voltage: This closely resembles the G0/

S0/C3 state. However, after the ICH9 has asserted STP_CPU#, it then lowers the

voltage to the processor. This reduces the leakage on the processor. Prior to

exiting the C4 state, the ICH9 increases the voltage to the processor.

G0/S0/C5

(Mobile

Only)

Stop-Clock with Very Low Processor Voltage and Cache Flush: The

processor voltage is dropped to the minimum l evel need ed to maintain th e state.

Caches are flushed from the processor to main memory prior to entering C5,

allowing bus master activity while in C5.

G0/S0/C6

(Mobile

Only)

Stop-Clock with Partially Processor Power Down and Cache Flush: C6

includes a cache flush as in C5. The processor saves internal state to RAM

allowing the processor to partially turn off.

G1/S1 Stop-Grant: Similar to G0/S0/C2 state.

Note: The behavior for this state is slightly different when supporting Intel® 64

processors.

G1/S3 Suspend-To-RAM (STR): The system context is mai ntained in system DRAM,

but power is shut off to non-critical circuits. Memory is retained, and refreshes

continue. All clocks stop except RTC clock.

G1/S4 Suspend-To-Disk (S TD): The context of the system is maintained on the disk.

All power is then shut off to the system except for the logic required to resume.

G2/S5 Soft Off (SOFF): System context is not maintained. All power is shut off except

for the logic required to restart. A full boot is required when waking.

Mechanical OFF (MOFF): System context not maintained. All power is shut off

except for the RT C. No “W ake” events are possible, because the system does not

have any power. This state occurs if the user removes the batteries, turns off a

mechanical switch, or if the system power supply is at a level th at is insuffi cient

to power the “waking” logic. When system power returns, transition will depend

on the state just prior to the entry to G3 and the AFTERG3 _EN bit in the

GEN_PMCON3 register (D31:F0, offset A4). Refer to Table 5-33 for more details.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 161

Functional Description

Table 5-26 shows the transitions rules among the various states. Note that transitions

among the various states may appear to temporarily transition through intermediate

states. For example, in going from S0 to S1, it may appear to pass through the G0/S0/

C2 states. These intermediate transitions and states are not listed in the table.

NOTES:

1. Some wake events can be preserved through power failure.

2. Transitions from the S1–S5 or G3 states to the S0 state are deferred u ntil BATLOW# is

inactive in mobile configurations.

Table 5-26. State Transition Rules for Intel® ICH9

Present

State Transition Trigger Next State

G0/S0/C0

• Processor halt instruction

•Level 2 Read

• Level 3 Read (Mobile Only)

• Level 4 Read (Mobile Only)

•SLP_EN bit set

• Power Button Override

• Mechanical Off/Power Failure

•G0/S0/C1

•G0/S0/C2

• G0/S0/C2, G0/S0/C3 or G0/S0/C4 - depending

on C4onC3_EN bit (D31:F0:Offset A0h:bit 7)

and BM_STS_ZERO_EN bit (D31:F0:Offset

A9h:bit 2) (Mobile Only)

• G1/Sx or G2/S5 state

•G2/S5

•G3

G0/S0/C1

• Any Enabled Break Event

•STPCLK# goes active

• Power Button Override

• Power Failure

•G0/S0/C0

•G0/S0/C2

•G2/S5

•G3

G0/S0/C2

• Any Enabled Break Event

• Power Button Override

• Power Failure

• Previously in C3/C4 and bus maste rs

idle

•G0/S0/C0

•G2/S5

•G3

• C3 or C4 - depending on PDME bit (D31:F0:

Offset A9h: bit 4)

G0/S0/C3

(Mobile

Only)

• Any Enabled Break Event

• Any Bus Master Event

• Power Button Override

• Power Failure

• Previously in C4 and bus masters

idle

•G0/S0/C0

• G0/S0/C2 - if PUME bit (D31:F0: Offset A9h:

bit 3) is set, else G0/S0/C0

•G2/S5

•G3

• C4 - depending on PDME bit (D31:F0: Offset

A9h: bit 4

G0/S0/C4

(Mobile

Only)

• Any Enabled Break Event

• Any Bus Master Event

• Power Button Override

• Power Failure

•G0/S0/C0

• G0/S0/C2 - if PUME bit (D31:F0: Offset A9h:

bit 3) is set, else G0/S0/C0

•G2/S5

•G3

G0/S0/C5

(Mobile

Only)

• Any Enabled Break Event

• Any Bus Master Event

• Power Button Override

• Power Failure

•G0/S0/C0

•C5

•G2/S5

•G3

G0/S0/C6

(Mobile

Only)

• Any Enabled Break Event

• Any Bus Master Event

• Power Button Override

• Power Failure

•G0/S0/C0

•G6

•G2/S5

•G3

G1/S1,

G1/S3, or

G1/S4

•Any Enabled Wake Event

• Power Button Override

• Power Failure

• G0/S0/C0 (See Note 2)

•G2/S5

•G3

G2/S5 •Any Enabled Wake Event

• Power Failure • G0/S0/C0 (See Note 2)

•G3

G3 • Power Returns • Optional to go to S0/C0 (reboot) or G2/S5

(stay off until power button pressed or other

wake event). (See Note 1 and 2)

Functional Description

162 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.13.3 System Power Planes

The system has several independent power planes , as described in Table 5-27. Note

that when a particular power plane is shut off, it should go to a 0 V level.

5.13.4 SMI#/SCI Generation

On any SMI# event taking place, ICH9 asserts SMI# to the processor, which causes it

to enter SMM space. SMI# remains active until the EOS bit is set. When the EOS bit is

set, SMI# goes inactive for a minimum of 4 PCI clocks. If another SMI event occurs,

SMI# is driven active again.

The SCI is a level-mode interrupt that is typically handled by an ACPI-aware operating

system. In non-APIC systems (which is the default), the SCI IRQ is routed to one of the

8259 interrupts (IRQ 9, 10, or 11). The 8259 interrupt controller must be programmed

to level mode for that interrupt.

In systems using the APIC, the SCI can be routed to interrupts 9, 10, 11, 20, 21, 22, or

23. The interrupt polarity changes depending on whether it is on an interrupt shareable

with a PIRQ or not (see Section 13.1.3). The interrupt rem ain s asserted until all SCI

sources are removed.

Table 5-28 shows which events can cause an SMI# and SCI. Note that some events can

be programmed to cause either an SMI# or SCI. The usage of the event for SCI

(instead of SMI#) is typically associated with an ACPI -based system. Each SMI# or SCI

source has a corresponding enable and status bit.

Table 5-27. System Power Plane

Plane Controlled

By Description

CPU SLP_S3#

signal

The SLP_S3# signal can be used to cut the power to the processor

completely. For Mobile systems, the DPRSLPVR support allows

lowering the processor’s voltage during the C4 state.

MAIN SLP_S3#

signal

When SLP_S3# goes active, power can be shut off to any circuit

not required to wake the system from the S3 state. Since the S3

state requires that the memory context be preserved, power must

be retained to the main memory.

The processor, devices on the PCI bus, LPC I/F, and graphics will

typically be shut off when the Main power plane is shut, although

there may be small subsections powered.

MEMORY

SLP_S4#

signal

SLP_S5#

signal

When the SLP_S4# goes active, power can be shut off to any

circuit not required to wake the system from the S4. Since the

memory context does not need to be preserved in the S4 state,

the power to the memory can also be shut down.

When SLP_S5# goes active, power can be shut to any circuit not

required to wake the system from the S5 state. Since the memory

context does not need to be preserved in the S5 state, the power

to the memory c an also be shut.

Link

Controller SLP_M#

This pin is asserted when the manageability platform goes to MOff .

Depending on the platform, this pin may be used to control the

MCH, ICH controller link power planes, the clock chip power, and

the SPI flash power.

DEVICE[n] GPIO I ndividual subsystems may have their own power plane. For

example, GPIO signals may be used to control the power to disk

drives, audio amplifiers, or the display screen.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 163

Functional Description

Table 5-28. Causes of SMI# and SCI (Sheet 1 of 2)

Cause SCI SMI Additional Enables Where Reported

SW Generated GPE Yes Yes SWGPE_EN=1 SWGPE_STS

SPI Command Completed No Yes

FSMIE

(See SPI Hardware

Sequencing Flash Control

SPI_STS

PME# Yes Yes PME_EN=1 PME_STS

PME_B0 (Internal, Bus 0,

PME-Capable Agents) Yes Yes PME_B0_EN=1 PME_B0_STS

PCI Express* PME Messages Yes Yes PCI_EXP_EN=1

(Not enabled for SMI) PCI_EXP_STS

PCI Express Hot Plug Message Yes Yes HOT_PLUG_EN=1

(Not enabled for SMI) HOT_PLUG_STS

Power Button Press Yes Yes PWRBTN_EN=1 PWRBTN_ST S

Power Button Ov erride (Note

7) Yes No None PWRBTNOR_STS

RTC Ala rm Yes Yes RTC_EN=1 RTC_STS

Ring Indicate Yes Yes RI_EN=1 RI_STS

USB#1 wakes Yes Yes USB1_EN=1 USB1_STS

USB#2 wakes Yes Yes USB2_EN=1 USB2_STS

USB#3 wakes Yes Yes USB3_EN=1 USB3_STS

USB#4 wakes Yes Yes USB4_EN=1 USB4_STS

USB#5 wakes Yes Yes USB5_EN=1 USB5_STS

USB#6 wakes Yes Yes USB6_EN=1 USB6_STS

THRM# pin active Yes Yes THRM_EN=1 THRM_STS

ACPI Timer overflow (2.34

sec.) Yes Yes TMROF_EN=1 TMROF_STS

Any GPI Ye s Yes

GPI[x]_Route=10

(SCI)

GPI[x]_Route=01

(SMI)

GPE0[x]_EN=1

GPI[x]_STS

GPE0_STS

TCO SCI Logic Yes No TCOSCI_EN=1 T COSCI_ST S

TCO SCI message from

(G)MCH Yes No none MCHSCI_STS

TCO SMI Logic No Y es TCO_EN=1 TCO_STS

TCO SMI — Year 2000 R ollo ver No Y es none NEWCENTURY_STS

TCO SMI — TCO TIMEROUT No Yes none TIMEOUT

TCO SMI — OS writes to

TCO_DAT_IN register No Yes none OS_TCO_SMI

TCO SMI — Message from

(G)MCH No Yes none MCHSMI_STS

TCO SMI — NMI occurred (and

NMIs mapped to SMI) No Yes NMI2SMI_EN=1 NMI2SMI_STS

TCO SMI — INTRUDER# signal

goes active No Yes INTRD_SEL=10 INTRD_DET

TCO SMI — Change of the

BIOSWE bit from 0 to 1 No Yes BC.LE=1 BIOSWR_STS

Functional Description

164 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. SCI_EN must be 1 to enable SCI. SCI_EN must be 0 to enable SMI.

2. SCI can be routed to cause interrupt 9:11 or 20:23 (20:23 only available in APIC mode).

3. GBL_SMI_EN must be 1 to enable SMI.

4. EOS must be written to 1 to re-enable SMI for the next 1.

5. ICH9 must have SMI# fully enabled when ICH9 is also enabled to trap cycles. If SMI# is

not enabled in conjunction with the trap enabling, then hardware behavior is undefined.

6. Only GPI[15:0] may generate an SMI# or SCI.

7. When a power button override first occurs, the system will transition immediately to S5.

The SCI will only occur after the next wake to S0 if the residual status bit

(PWRBTNOR_STS) is not cleared prior to setting SCI_EN.

TCO SMI — Write attempte d

to BIOS No Yes BIOSWE=1 BIOSWR_STS

BIOS_RLS written to Yes No GBL_EN=1 GBL_STS

GBL_RLS written to No Yes BIOS_EN=1 BIOS_STS

Write to B2h register N o Yes APMC_EN = 1 APM_STS

Periodic timer expires No Yes PERIODIC_EN=1 PERIODIC_STS

64 ms timer expires No Yes SWSMI_TMR_EN=1 SWSMI_TMR_STS

Enhanced USB Legacy

Support Event No Yes LEGACY_USB2_EN = 1 LEGACY_USB2_STS

Enhanced USB Intel Specific

Event No Yes INTEL_USB2_EN = 1 INTEL_USB2_STS

UHCI USB Legacy logic No Yes LEGACY_USB_EN=1 LEGACY_USB_STS

Serial IRQ SMI reported No Yes none SERIRQ_SMI_STS

Device monitors match

address in its range No Yes none DEVMON_STS,

DEVACT_STS

SMBus Host Control le r No Yes SMB_SMI_EN

Host Controller

Enabled

SMBus host status

reg.

SMBus Slave SMI message No Yes none SMBUS_SMI_STS

SMBus SMBALERT# signal

active No Yes none SMBUS_SMI_STS

SMBus Host Notify message

received No Yes HOST_NOTIFY_INTRE

NSMBUS_SMI_STS

HOST_NOTIFY_STS

(Mobile Only) BATLOW#

assertion Yes Yes BATLOW_EN=1. BATLOW_STS

Access microcontroller 62h/

66h No Yes MCSMI_EN MCSMI_STS

SLP_EN bit written to 1 No Yes SMI_ON_SLP_EN=1 SMI_ON_SLP_EN_STS

USB Per-Port Registers Write

Enable bit changes to 1. No Yes USB2_EN=1,

Write_Enable_SMI_En

able=1

USB2_STS, Write

Enable Status

Write attempted to BIOS No Yes BIOSWE = 0 BIOSWR_STS

GPIO Lockdown Enable bit

changes from ‘1’ to ‘0’. No Yes GPIO_UNLOCK_SMI_E

N=1 GPIO_UNLOCK_SMI_S

Table 5-28. Causes of SMI# and SCI (Sheet 2 of 2)

Cause SCI SMI Additional Enables Where Reported

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 165

Functional Description

5.13.4.1 PCI Express* SCI

PCI Express ports and the (G)MCH (via DMI) have the ability to cause PME using

messages. When a PME message is received, ICH9 will set the PCI_EXP_STS bit. If the

PCI_EXP_EN bit is also set, the ICH9 can cause an SCI via the GPE1_STS register.

5.13.4.2 PCI Express* Hot-Plug

PCI Express has a Hot-Plug mechanism and is capable of generating a SCI via the GPE1

generating a wake event.

5.13.5 Dynamic Processor Clock Control

The ICH9 has extensive control for dynamically starting and stopping system clocks.

The clock control is used for tr ansitions among the v arious S0/Cx states, and processor

throttling. Each dynamic clock control method is described in this section. The various

sleep states may also perform types of non-dynamic clock control.

The ICH9 supports the ACPI C0, C1 and C2 states (in desktop) or C0, C1, C2, C3, C4,

C5 and C6 (in mobile) states.

The Dynamic Processor Clock control is handled using the following signals:

• STPCLK#: Used to halt processor instruction stream.

• (Mobile Only) STP_CPU#: Used to stop processor’s clock

• (Mobile Only) DPSLP#: Used to force Deeper Sleep for processor.

• (Mobile Only) DPRSLPVR: Used to lower voltage of VRM during C4 state.

• (Mobile Only) DPRSTP#: Used to alert the processor of C4 state. Also works in

conjunction with DPRSLPVR to communicate to the VRM whether a slow or fast

voltage ramp should be used.

The C1 state is entered based on the processor performing an auto halt instruction.

The C2 state is entered based on the processor reading the Level 2 register in the

ICH9.

(Mobile Only) The C2 state can also be entered from C3 or C4 states if bus masters

require snoops and the PUME bit (D31:F0: Offset A9h: bit 3) is set.

(Mobile Only) The C3 state is entered based on the processor reading the Level 3

This state can also be entered after a temporary return to C2 from a prior C3 or C4

state.

(Mobile Only) The C4 state is entered based on the processor reading the Level 4

This state can also be entered after a temporary return to C2 from a prior C4 state.

(Mobile Only) The C5 or C6 state is entered based on the processor reading the Level 5

or Level 6 register in the ICH9 or the processor sending the stop grant message. Note:

The ICH uses the same flow for both C5 and C6 states. The platform must only support

one or the other since the programmable exit timers for C5 and C6 are different, and

the flow uses the same timers for both which are statically configured.

A C1 or C2 state in desktop or a C1, C2, C3, C4, C5 or C6 state in mobile ends due to a

Break event. Based on the break event, the ICH9 returns the system to C0 state.

Functional Description

166 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 5-29 lists the possible break events from C2, C3, C4, C5 or C6. The break events

from C1 are indicated in the processor’s datasheet. The break events for C3, C4, C5

and C6 are Mobile Only.

5.13.5.1 Slow C4 and C5 Exit (Mobile Only)

In order to eliminate the audible noise caused by aggressive voltage ramps when

exiting C4 or C5 states at a regular, periodic frequency, the ICH9 supports a method to

slow down the voltage ramp at the processor VR for certain break events. If enabled for

this behavior, the ICH9 treats IRQ0 and IRQ8 as “slow” break events since both of

these can be the system timer tick interrupt. Rather than carefully tracking the

interrupt and timer configuration information to track the one correct interrupt, it was

deemed acceptable to simplify the logic and slow the break exit sequence for both

interrupts. Other break event sources invoke the normal exit timings.

The ICH9 indicates that a slow voltage ramp is desired by deasserting DPRSTP# (high)

and leaving DPRSLPVR asserted (high). The normal voltage ramp r ate is communicated

by deasserting DPRSTP# (high) and deasserting DPRSLPVR (low).

The ICH9 waits an additional delay before starting the normal voltage ramp timer

during the C4 or C5 exit sequence. If a “fast” break event occurs during the additional,

slow-Exit time delay, the ICH9 quickly deasserts DPRSLPVR (low), thereby speeding up

the voltage ramp and reducing the delay to a v alue that is typically seen by the device

in the past. In the event that a fast break event and a slow break event occur together,

the fast flow is taken.

The ICH9 provides separate enabled for Slow C4 Exit and Slow C5 exit.

Table 5-29. Break Events

Event Breaks

from Comment

Any unmasked interrupt goes

active C2, C3, C4,

C5, C6

IRQ[0:15] when using the 8259s, IRQ[0:23]

for I/O APIC. Since SCI is an interrupt, any SCI

will also be a break event.

Any internal event that cause an

NMI or SMI# C2, C3, C4,

C5, C6 Many possible sour ces

Any internal event that cause

INIT# to go active C2, C3, C4

C5, C6 Could be indicated by the keyboard controller

via the RCIN inpu t signal.

Any bus master request

(internal, external or DMA) goes

active and BM_RLD=1

(D31:F0:Offset PMBASE+04h:

bit 1)

C3, C4

Need to wake up processor so it can do snoops

Note: If the PUME bit (D31:F0: Offset A9h: bit

3) is set, then bus master activity will NOT be

treated as a break event. Instead, there will be

a return only to the C2 state.

Processor Pending Break Event

Indication C2, C3, C4 Only available if FERR# enabled for break event

indication (See FERR# Mux Enable in GCS,

Chipset Config Registers:Offset 3410h:bit 6)

REQ-C0 Message from MCH C2, C3, C4,

C5, C6

Can be sent at any time after the Ack-C2

message and before the Ack-C0 message,

when not in C0 state.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 167

Functional Description

5.13.5.2 Transition Rules among S0/Cx and Throttling States

The following priority rules and assumptions apply among the various S0/Cx and

throttling states:

• Entry to any S0/Cx state is mutually exclusive with entry to any S1–S5 state. This

is because the processor can only perform one register access at a time and Sleep

states have higher priority than thermal throttling.

• When the SLP_EN bit is set (system going to a S1–S5 sleep state), the THTL_EN

and FORCE_THTL bits can be internally treated as being disabled (no throttling

while going to sleep state).

• If the THTL_EN or FORCE_THTL bits are set, and a Level 2, Level 3 or Level 4 read

then occurs, the system should immediately go and stay in a C2, C3 or C4 state

until a break event occurs. A Level 2, Level 3 or Level 4 read has higher priority

than the software initiated throttling. C3 and C4 support is Mobile Only.

• After an exit from a C2, C3 or C4 state (due to a Break event), and if the THTL_EN

or FORCE_THTL bits are still set, the system will continue to throttle STPCLK#.

Depending on the time of break event, the first transition on STPCLK# active can

be delayed by up to one THRM period (1024 PCI clocks = 30.72 µs). C3 and C4

support is Mobile Only.

• The Host controller must post Stop-Grant cycles in such a way that the processor

gets an indication of the end of the special cycle prior to the ICH9 observing the

Stop-Grant cycle. This ensures that the STPCLK# signals stays active for a

sufficient period after the processor observes the response phase.

• If in the C1 state and the STPCLK# signal goes active, the processor will gener ate a

Stop-Grant cycle, and the system should go to the C2 state. When STPCLK# goes

inactive, it should return to the C1 state.

5.13.5.3 Deferred C3/C4 (Mobile Only)

Due to the new DMI protocol, if there is any bus master activity (other than true

isochronous), then the C0 to C3 transition will pause at the C2 state. ICH9 will keep the

processor in a C2 state until:

• ICH9 sees no bus master activity.

• A break event occurs. In this case, the ICH9 will perform the C2 to C0 sequence.

Note that bus master traffic is not a break event in this case.

To take advantage of the Deferred C3/C4 mode, the BM_STS_ZERO_EN bit must be

set. This will cause the BM_STS bit to read as 0 even if some bus master activity is

present. If this is not done, then the software may avoid even attempting to go to the

C3 or C4 state if it sees the BM_STS bit as 1.

If the PUME bit (D31:F0: Offset A9h: bit 3) is 0, then the ICH9 will treat bus master

activity as a break event. When reaching the C2 state, if there is any bus master

activity, the ICH9 will return the processor to a C0 state.

5.13.5.4 POPUP (Auto C3/C4 to C2) (Mobile Only)

When the PUME bit (D31:F0: Offset A9h: bit 3) is set, the ICH9 enables a mode of

operation where standard (non-isochronous) bus master activity will not be treated as

a full break event from the C3 or C4 states. Instead, these will be treated merely as

bus master events and return the platform to a C2 state, and thus allow snoops to be

performed.

After returning to the C2 state, the bus master cycles will be sent to the (G)MCH, even

if the ARB_DIS bit is set.

Functional Description

168 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.13.5.5 POPDOWN (Auto C2 to C3/C4) (Mobile Only)

After returning to the C2 state from C3/C4, it the PDME bit (D31:F0: Offset A9h: bit 4)

is set, the platform can return to a C3 or C4 state (depending on where it was prior to

going back up to C2). This behaves similar to the Deferred C3/C4 transition, and will

keep the processor in a C2 state until:

• Bus masters are no longer active.

• A break event occurs. Note: Bus master traffic is not a break event in this case.

5.13.5.6 C5 and C6 Entry/Exit (Mobile Only)

The ICH9 uses the same flow for both C5 and C6 states. However, the platform must

only support C5 or C6, since the same program mable exit times used are different, and

the timers are shared. The ICH essentially aliases the Level 5 and Level 6 reads

together and the Ack_C5 and Ack_C6 messages together.

C5/C6 Entry:

1. ICH receives Level 5 Read or Level 6 Read from MCH

2. ICH asserts STPCLK#

3. MCH receives Stop Grant message from processor

4. ICH receives Req C2 message from MCH

5. ICH asserts PMSYNC# to MCH

6. ICH receives Ack_C5 or Ack_C6 message from MCH after MCH has switched to No

snoop mode and asserts CPU_SLP. MCH must no send Req_C0 until after it sends

Ack_C5 or Ack_C6.

7. ICH asserts DPSL P#, ST PCPU#, DPRST P# and DPRSLPVR signals in sequ ence based

on timer values.

5.13.5.7 C5 Exit (Mobile Only)

When the ICH detects a break event after entering C5 due to an internal or external

event, it de- asserts DPRSLPVR, DPRSTP# , STPCPU#, DPSLP#, PMSYNC # and STPCLK#

signals in sequence based on timer values. The ICH does not attempt to abort the C5

entry sequence if a break event is detected while entering C5.

5.13.6 Dynamic PCI Clock Control (Mobile Only)

The PCI clock can be dynamically controlled independent of any other low-power state.

This control is accomplished using the CLKRUN# protocol as described in the PCI Mobile

Design Guide, and is transparent to software.

The Dynamic PCI Clock control is handled using the following signals:

• CLKRUN#: Used by PCI and LPC peripherals to request the system PCI clock to run

• STP_PCI#: Used to stop the system PCI clock

Note: The 33 MHz clock to the ICH9 is “free-running” and is not affected by the STP_PCI#

signal.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 169

Functional Description

5.13.6.1 Conditions for Checking the PCI Clock

When there is a lack of PCI activity the ICH9 has the capability to stop the PCI clocks to

conserve power. “PCI activity” is defined as any activity that would require the PCI

clock to be running.

Any of the following conditions will indicate that it is not okay to stop the PCI clock:

•Cycles on PCI or LPC

• Cycles of any internal device that would need to go on the PCI bus

• SERIRQ activity

Behavioral Description

• When there is a lack of activity (as defined above) for 29 PCI clocks, the ICH9

deasserts (drive high) CLKRUN# for 1 clock and then tri-states the signal.

5.13.6.2 Conditions for Maintaining the PCI Clock

PCI masters or LPC devices that wish to maintain the PCI clock running will observe the

CLKRUN# signal deasserted, and then must re-assert if (drive it low) within 3 clocks.

• When the ICH9 has tri-stated the CLKRUN# signal after dea sserting it, the ICH9

then checks to see if the signal has been re-asserted (externally).

• After observing the CLKRUN# signal asserted for 1 clock, the ICH9 again starts

asserting the signal.

• If an internal device needs the PCI bus, the ICH9 asserts the CLKRUN# signal.

5.13.6.3 Conditions for Stopping the PCI Clock

• If no device re-asserts CLKRUN# once it has been deasserted for at least 6 clocks,

the ICH9 stops the PCI clock by asserting the STP_PCI# signal to the clock

synthesizer.

5.13.6.4 Conditions for Re-Starting the PCI Clock

• A peripheral asserts CLKRUN# to indicate that it needs the PCI clock re-started.

• When the ICH9 observes the CLKRUN# signal asserted for 1 (free running) clock,

the ICH9 deasserts the STP_PCI# signal to the clock synthesizer within 4 (free

running) clocks.

• Observing the CLKRUN# signal asserted externally for 1 (free running) clock, the

ICH9 again starts driving CLKRUN# asserted.

If an internal source requests the clock to be re-started, the ICH9 re-asserts CLKRUN#,

and simultaneously deasserts the STP_PCI# signal.

5.13.6.5 LPC Devices and CLKRUN#

If an LPC device (of any type) needs the 33 MHz PCI clock, such as for LPC DMA or LPC

serial interrupt, then it can assert CLKRUN#. Note that LPC devices running DMA or bus

master cycles will not need to assert CLKRUN#, since the ICH9 asserts it on their

behalf.

The LDRQ# inputs are ignored by the ICH9 when the PCI clock is stopped to the LPC

devices in order to avoid misinterpreting the request. The ICH9 assumes that only one

more rising PCI clock edge occurs at the LPC device after the assertion of STP_PCI#.

Upon deassertion of STP_PCI#, the ICH9 assumes that the LPC device receives its first

clock rising edge corresponding to the ICH9’s second PCI clock rising edge after the

deassertion.

Functional Description

170 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.13.7 Sleep States

5.13.7.1 Sleep State Overview

The ICH9 directl y supports different sle ep states (S1–S5) , which are entered by setting

the SLP_EN bit, or due to a Power Button press. The entry to the Sleep states is based

on several assumptions:

• Entry to a Cx state is mutually exclusive with entry to a Sleep state. This is because

the processor can only perform one register access at a time. A request to Sleep

always has higher priority than throttling.

• Prior to setting the SLP_EN bit, the software turns off processor-controlled

throttling. Note that thermal throttling cannot be disabled, but setting the SL P_EN

bit disables thermal throttling (since S1–S5 sleep state has higher priority).

• The G3 state cannot be entered via any software mechanism. The G3 state

indicates a complete loss of power.

5.13.7.2 Initiating Sleep State

Sleep states (S1–S5) are initiated by:

• Masking interrupts, turning off all bus master enable bits, setting the desired type

in the SLP_TYP field, and then setting the SLP_EN bit. The hardware then attempts

to gracefully put the system into the corresponding Sleep state.

• Pressing the PWRBTN# Signal for more than 4 seconds to cause a Power Button

Override event. In this case the transition to the S5 state is less graceful, since

there are no dependencies on observing Stop-Grant cycles from the processor or

on clocks other than the RTC clock

• Assertion of the THRMTRIP# signal will cause a transition to the S5 state. This can

occur when system is in S0 or S1 state.

5.13.7.3 Exiting Sleep States

Sleep states (S1–S5) are exited based on Wake events. The Wake events forces the

system to a full on state (S0), although some non-critical subsystems might still be

shut off and have to be brought back manually. For example, the hard disk may be shut

off during a sleep state, and have to be enabled via a GPIO pin before it can be used.

Upon exit from the ICH9-controlled Sleep states, the WAK_STS bit is set. The possible

causes of Wake Events (and their restrictions) are shown in Table 5-31.

Note: (Mobile Only) If the BATLOW# signal is asserted, ICH9 does not attempt to wake from

an S1–S5 state, even if the power button is pressed. This prevents the system from

waking when the battery power is insufficient to wake the system. Wake events that

occur while BATLOW# is asserted are latched by the ICH9, and the system wake s after

BATLOW# is deasserted.

Table 5-30. Sleep Types

Sleep Type Comment

S1 Intel® ICH9 asserts the STPCLK# signal. This lowers the processor’s power

consumption. No snooping is possible in this stat e.

S3 ICH9 asserts SLP_S3#. The SLP_S3# signal controls the power to non-critical

circuits. Power is only retained to devices needed to wake from this sleeping

state, as well as to the memory.

S4 ICH9 asserts SLP_S3# and SLP_S4#. The SLP_S4# signal shuts off the power to

the memory subsystem. Only devices needed to wake from this state should be

powered.

S5 Same power state as S4. ICH9 asserts SLP_S3#, SLP_S4# and SLP_S5#.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 171

Functional Description

NOTES:

1. This is a wake event from S5 only if the sleep state was entered by setting the SLP_EN and

SLP_TYP bits via software, or if there is a power failure.

2. If in the S5 state due to a power button override or THRMTRIP#, the possible wake events

are due to Power Button, Hard Reset Without Cycling (See Command Type 3 in

Table 5-53), Hard Reset System (See Command Type 4 in Table 5-53), Wake SMBus Slave

Message (01h) and ME initiated non-maskable wake.

3. When the WAKE# pin is active and t he PC I Express devic e is en able d to wake th e sys te m,

the ICH9 will wake the platform.

Table 5-31. Causes of Wake Events

Cause States Can

Wake From How Enabled

RTC Alarm S1–S5

(Note 1) Set RTC_EN bit in PM1_EN register

Power B utton S 1–S5 Alway s ena bled as Wake event. (Note 2).

GPI[0:15] S1–S5

(Note 1)

GPE0_EN register

Note: GPI’s that are in the core well are not capable of

waking the system from sleep states when the core well is

not powered.

Classic USB S1–S4 Set USB1_EN, USB 2_EN, USB3_EN, USB4_EN, USB5_EN,

and USB6_EN bits in GPE0_EN register

LAN S1–S5 Will use PME#. Wake enable set with LAN logic.

RI# S1–S5

(Note 1) Set RI_EN bit in GPE0_EN register

Intel® High

Definition Audio S1–S5 Event sets PME_B0_STS bit; PM_B0_EN must be enabled.

Can not wake from S5 state if it was entered due to power

failure or power button override.

Primary PME# S1–S5

(Note 1) PME_B0_EN bit in GPE0_EN register

Secondary PME# S1–S5 Set PME_EN bit in GPE0_EN register.

PCI_EXP_WAKE# S1–S5 PCI_EXP_WAKE bit (Note 3)

PCI_EXP PME

Message S1 Must use the PCI Express* WAKE# pi n rather than messages

for wake from S3,S4, or S5.

SMBALERT# S1–S5 Always enabled as Wake event

SMBus Slave Wake

Message (01h) S1–S5

Wake/SMI# command always enabled as a Wake event.

Note: SMBus Slave Message can wake the system from S1–

S5, as well as from S5 due to Power Button Override. (Note

2).

SMBus Host Notify

message received S1–S5 HOST_NOTIFY_WKEN bit SMBus Slave Command register.

Reported in the SMB_WAK_STS bit in the GPEO_STS

ME Non-Maskable

Wake S1-S5 Always enabled as Wake event. (Note 2).

Functional Description

172 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

It is important to understand that the various GPIs ha ve different levels of functionality

when used as wake events. The GPIs that reside in the core power well can only

generate wake events from sleep states where the core well is powered. Also, only

certain GPIs are “ACPI Compliant,” meaning that their Status and Enable bits reside in

ACPI I/O space. Table 5-32 summarizes the use of GPIs as wake events.

The latency to exit the various Sleep states varies greatly and is heavily de p endent o n

power supply design, so much so that the exit latencies due to the ICH9 are

insignificant.

5.13.7.4 PCI Express* WAKE# Signal and PME Event Message

PCI Express ports can wake the platform from any sleep state (S1, S3, S4, or S5) using

the WAKE# pin. WAKE# is treated as a wake event, but does not cause any bits to go

active in the GPE_STS register.

PCI Express ports and the (G)MCH (via DMI) have the ability to cause PME using

messages. When a PME message is received, ICH9 will set the PCI_EXP_STS bit.

5.13.7.5 Sx-G3-Sx, Handling Power Failures

Depending on when the power failure occurs and how the system is designed, different

transitions could occur due to a power failure.

The AFTER_G3 bit provides the ability to program whether or not the system should

boot once power returns after a power loss event. If the policy is to not boot, the

system remains in an S5 state (unless previously in S4). There are only three possible

events that will wake the system after a power failure.

1. PWRBTN#: PWRBTN# is always enabled as a wake event. When RSMRST# is low

(G3 state), the PWRBTN_STS bit is reset. When the ICH9 exits G3 after power

returns (RSMRST# goes high), the PWRBTN# signal is already high (because VCC-

standby goes high before RSMRST# goes high) and the PWRBTN_STS bit is 0.

2. RI#: RI# does not have an internal pull-up . Therefore, if this signal is enabled as a

wake event, it is important to keep this signal powered during the power loss

event. If this signal goes low (active), when power return s the RI_STS bit is set and

the system interprets that as a wake event.

3. RTC Alarm: The RT C_EN bit is in the R T C well and is preserved after a power loss.

Like PWRBTN_STS the RTC_STS bit is cleared when RSMRST# goes low.

The ICH9 monitors both PWROK and RSMRST# to detect for power failures. If PWROK

goes low, the PWROK_FLR bit is set. If RSMRST# goes low, PWR_FLR is set.

Note: Although PME_EN is in the RTC well, this signal cannot wake the system after a power

loss. PME_EN is cleared by RTCRST#, and PME_STS is cleared by RSMRST#.

Table 5-32. GPI Wake Events

GPI Power Well Wake From Notes

GPI[7:0] Core S1 ACPI

Compliant

GPI[15:8] Suspend S1–S5 ACPI

Compliant

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 173

Functional Description

5.13.8 Thermal Management

The ICH9 has mechanisms to assist with managing thermal problems in the system.

5.13.8.1 THRM# Signal

The THRM# signal is used as a status input for a thermal sensor. Based on the THRM#

signal going active, the ICH9 generates an SMI# or SCI (depending on SCI_EN).

If the THRM_POL bit is set low, when the THRM# signal goes low, the THRM_STS bit

will be set. This is an indicator that the thermal threshold has been exceeded. If the

THRM_EN bit is set, then when THRM_STS goes active, either an SMI# or SCI will be

generated (depending on the SCI_EN bit being set).

The power management software (BIOS or ACPI) can then take measures to start

reducing the temperature. Examples include shutting off unwanted subsystems, or

halting the processor.

By setting the THRM_POL bit to high, another SMI# or SCI can optionally be gener ated

when the THRM# signal goes back high. This allows the software (BIOS or ACPI) to

turn off the cooling methods.

Note: THRM# assertion does not cause a TCO event message in S3 or S4. The level of the

signal is not reported in the heartbeat message.

5.13.8.2 Software Initiated Passive Cooling

This mode is initiated by software setting the THTL_EN or FORCE_THTL bits.

Software sets the THTL_DTY or THRM_DTY bits to select throttle ratio and THTL_EN or

FORCE_THTL bit to enable the throttling.

Throttling results in STPCLK# active for a minimum time of 12.5% and a maxi mum of

87.5%. The period is 1024 PCI clocks. Thus, the STPCLK# signal can be active for as

little as 128 PCI clocks or as much as 896 PCI clocks. The actual slowdown (and

cooling) of the processor depends on the instruction stream, because the processor is

allowed to finish the current instruction. Furthermore, the ICH9 waits for the STOP-

GRANT cycle before starting the count of the time the STPCLK# signal is active.

Table 5-33. Transitions Due to Power Failure

State at Power Failure AFTERG3_EN bit Transition When Power Returns

S0, S1, S3 1

0S5

S4 1

0S4

S5 1

0S5

Functional Description

174 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.13.8.3 THRM# Override Software Bit

The FORCE_THTL bit allows the BIOS to force passive cooling, independent of the ACPI

software (which uses the THTL_EN and THTL_DTY bits). If this bit is set, the ICH9

starts throttling using the ratio in the THRM_DTY field.

When this bit is cleared the ICH9 stops throttling, unless the THTL_EN bit is set

(indicating that ACPI software is attempting throttling).

If both the THTL_EN and FORCE_THTL bits are set, then the ICH should use the duty

cycle defined by the THRM_DTY field, not the THTL_DTY field.

5.13.8.4 Active Cooling

Active cooling inv olves fans. The GPIO signals from the ICH9 can be used to turn on/off

a fan.

5.13.9 Event Input Signals and Their Usage

The ICH9 has various input signals that trigger specific events. This section describes

those signals and how they should be used.

5.13.9.1 PWRBTN# (Power Button)

The ICH9 PWRBTN# signal operates as a “Fixed Power Button” as described in the

Advanced Configuration and Power Interface, Version 2.0b. PWRBTN# signal has a 16

ms de-bounce on the i nput. The state tr ansition descriptions are included in Table 5-34.

Note that the transitions start as soon as the PWRBTN# is pressed (but after the

debounce logic), and does not depend on when the Power Button is released.

Note: During the time that the SLP_S4# signal is stretched for the minimum assertion width

(if enabled), the Power Button is not a wake event. Refer to Power Button Override

Function section below for further detail.

Table 5-34. Transitions Due to Power Button

Present

State Event Transition/Action Comment

S0/Cx PWRBTN# goes low

SMI# or SCI generated

(depending on SCI_EN,

PWRBTN_INIT_EN,

PWRBTN_EN and

GLB_SMI_EN)

Software typically initiates a

Sleep state

S1–S5 PWRBTN# goes low Wake Event. Transitions to

S0 state Standard wakeup

G3 PWRBTN# pressed None No effect since no power

Not latched nor detected

S0–S4 PWRBTN# held low

for at least 4

consecutive seconds

Unconditio nal transition to

S5 state

No dependence on processor

(e.g., Stop-Grant cycles) or

any other subsystem

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 175

Functional Description

Power Button Override Function

If PWRB TN# is observed active for at least four consecutive seconds, the state machine

unconditionally transitions to the G2/S5 state, regardless of present state (S0–S4),

even if PWROK is not active. In this case, the transition to the G2/S5 state does not

depend on any particular response from the processor (e.g., a Stop-Grant cycle), nor

any similar dependency from any other subsystem.

The PWRBTN# status is readable to check if the button is currently being pressed or

has been released. The status is taken after the de-bounce, and is readable via the

PWRBTN_LVL bit.

Note: The 4-second PWRBTN# assertion should only be used if a system lock-up has

occurred. The

4-second timer starts counting when the ICH9 is in a S0 state. If the PWRBTN# signal

is asserted and held active when the system is in a suspend state (S1–S5), the

assertion causes a wake event. Once the system has resumed to the S0 state, the 4-

second timer starts.

Note: During the time that the SLP_S4# signal is stretched for the minimum assertion width

(if enabled by D31:F0:A4h bit 3), the Power Button is not a wake event. As a result, it

is conceivable that the user will press and continue to hold the P ower Button waiting for

the system to awak e. Since a 4-second press of the P ower Bu tton is already defined as

an Unconditional Power down, the power button timer will be forced to inactive while

the power-cycle timer is in progress. Once the power-cycle timer has expired, the

Power Button awakes the system. Once the minimum SLP_S4# power cycle expires,

the Power Button must be pressed for another 4 to 5 seconds to create the Override

condition to S5.

Sleep Button

The Advanced Configuration and Power Interface, Version 2.0b defines an optional

Sleep button. It differs from the power button in that it only is a request to go from S0

to S1–S4 (not S5). Also , in an S5 state, the P ower Button can wake the system, but the

Sleep Button cannot.

Although the ICH9 does not include a specific signal designated as a Sleep Button, one

of the GPIO signals can be used to create a “Control Method” Sleep Button. See the

Advanced Configuration and Power Interface, Version 2.0b for implementation details.

5.13.9.2 RI# (Ring Indicator)

The Ring Indicator can cause a wake event (if enabled) from the S1–S5 states.

Table 5-35 shows when the wake event is gener ated or ignored in different states. If in

the G0/S0/Cx states, the ICH9 generates an interrupt based on RI# active, and the

interrupt will be set up as a Break event.

Note: Filtering/Debounce on RI# will not be done in ICH9. Can be in modem or external.

Table 5-35. Transitions Due to RI# Signal

Present State Event RI_EN Event

S0 RI# Active X Ignored

S1–S5 RI# Active 0

1Ignored

Wake Even t

Functional Description

176 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.13.9.3 PME# (PCI Power Management Event)

The PME# signal comes from a PCI device to request that the system be restarted. The

PME# signal can gener ate an SMI# , SCI, or optionally a Wake event. The event occurs

when the PME# signal goes from high to low . No event is caused when it goes from low

to high.

There is also an internal PME_B0 bit. This is separate from the external PME# signal

and can cause the same effect.

5.13.9.4 SYS_RESET# Signal

When the SYS_RESET# pin is detected as active after the 16 ms debounce logic, the

ICH9 attempts to perform a “graceful” reset, by waiting up to 25 ms for the SMBus to

go idle. If the SMBus is idle when the pin is detected active, the reset occurs

immediately; otherwise, the counter starts. If at any point during the count the SMBus

goes idle the reset occurs. If , however, the counter expires and the SMBus is still active,

a reset is forced upon the system even though activity is still occurring.

Once the reset is asserted, it remains asserted for 5 to 6 ms regardless of whether the

SYSRESET# input remains asserted or not. It cannot occur again until SYS_RESET#

has been detected inactive after the debounce logic, and the system is back to a full S0

state with PLTRST# inactive. Note that if bit 3 of the CF9h I/O register is set then

SYS_RESET# will result in a full power cycle reset.

5.13.9.5 THRMTRIP# Signal

If THRMTRIP# goes active, the processor is indicating an overheat condition, and the

ICH9 immediately transitions to an S5 state. However, since the processor has

overheated, it does not respond to the ICH9’s STPCLK# pin with a stop grant special

cycle. Therefore, the ICH9 does not wait for one. Immediately upon seeing THRMTRIP#

low , the ICH9 initiates a transition to the S5 state, d rive SLP _S3#, SLP_S 4#, SLP_S5#

low, and set the CTS bit. The transition looks like a power button override.

When a THRMTRIP# event occurs, the ICH9 will power down immediately without

following the normal S0 -> S5 path. The ICH9 will immediately drive SLP_S3#,

SLP_S4#, and SLP_S5# low after sampling THRMTRIP# active.

If the processor is running extremely hot and is heating up, it is possible (although very

unlikely) that components around it, such as the ICH9, are no longer executing cycles

properly. Therefore, if THRMTRIP# goes active, and the ICH9 is relying on state

machine logic to perform the power down, the state machine may not be working, and

the system will not power down.

The ICH provides filtering for short low glitches on the THRMTRIP# signal in order to

prevent erroneous system shut downs from noise. Glitches shorter than 25nsec are

ignored.

During boot, THRMTRIP# is ignored until SLP_S3#, PWROK, VRMPWRGD/VGATE, and

PLTRST# are all ‘1’. During entry into a powered-down state (due to S3, S4, S5 entry,

power cycle reset, etc.) THRMTRIP# is ignored until either SLP_S3# = 0, or PWROK =

0, or VRMPWRGD/VGATE = 0.

Note: A thermal trip event will:

• Set the AFTERG3_EN bit

• Clear the PWRBTN_STS bit

• Clear all the GPE0_EN register bits

• Clear the SMB_WAK_STS bit only if SMB_SAK_STS was set due to SMBus slave

receiving message and not set due to SMBAlert

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 177

Functional Description

5.13.10 ALT Access Mode

Before entering a low power state, several registers from powered down parts may

need to be saved. In the majority of cases, this is not an issue, as registers have read

and write paths. However, several of the ISA compatible registers are either read only

or write only. To get data out of

write-only registers, and to restore data into read-only register s, th e I CH9 impl ements

an ALT access mode.

If the ALT access mode is entered and exited after reading the registers of the ICH9

timer (8254), the timer starts counting faster (13.5 ms). The following steps listed

below can cause problems:

1. BIOS enters ALT access mode for reading the ICH9 timer related registers.

2. BIOS exits ALT access mode.

3. BIOS continues through the execution of other needed steps and passes control to

the operating system.

After getting control in step #3, if the operating system does not reprogram the system

timer again, the timer ticks may be happening faster than expected. F or example DOS

and its associated softw are assume that the system tim er is running at 54.6 ms and as

a result the time-outs in the software may be happening faster than expected.

Operating systems (e.g., Microsoft Windows* 98, Windows* 2000, and Windows NT*)

reprogram the system timer and therefore do not encounter this problem.

For some other loss (e.g., Microsoft MS-DOS*) the BIOS should restore the timer back

to 54.6 ms before passing control to the operating system. If the BIOS is entering ALT

access mode before entering the suspend state it is not necessary to restore the timer

contents after the exit from ALT acce ss mode.

Functional Description

178 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.13.10.1 Write Only Registers with Read Paths in ALT Access Mode

The registers described in Table 5-36 have read paths in ALT access mode. The access

number field in the table indicates which register will be returned per access to that

port.

Table 5-36. Write Only Registers with Read Paths in ALT Access Mode (Sheet 1 of 2)

Restore Data Restore Data

I/O

Addr # of

Rds Access Data I/O

Addr # of

Rds Access Data

00h 2 1DMA Chan 0 base address

low byte

40h 7

1Timer Counter 0 status, bits

[5:0]

2DMA Chan 0 base address

high byte 2Timer Counter 0 base count

low byte

01h 2 1DMA Chan 0 base count low

byte 3Timer Counter 0 base count

high byte

2DMA Chan 0 base count high

byte 4Timer Counter 1 base count

low byte

02h 2 1DMA Chan 1 base address

low byte 5Timer Counter 1 base count

high byte

2DMA Chan 1 base address

high byte 6Timer Counter 2 base count

low byte

03h 2 1DMA Chan 1 base count low

byte 7Timer Counter 2 base count

high byte

2DMA Chan 1 base count high

byte 41h 1 Timer Counter 1 status, bits

[5:0]

04h 2 1DMA Chan 2 base address

low byte 42h 1 Timer Counter 2 status, bits

[5:0]

2DMA Chan 2 base address

high byte 70h 1 Bit 7 = NMI Enable,

Bits [6:0] = RT C Address

05h 2 1DMA Chan 2 base count low

byte C4h 2 1DMA Chan 5 base address

low byte

2DMA Chan 2 base count high

byte 2DMA Chan 5 base address

high byte

06h 2 1DMA Chan 3 base address

low byte C6h 2 1DMA Chan 5 base count low

byte

2DMA Chan 3 base address

high byte 2DMA Chan 5 base count

high byte

07h 2 1DMA Chan 3 base count low

byte C8h 2 1DMA Chan 6 base address

low byte

2DMA Chan 3 base count high

byte 2DMA Chan 6 base address

high byte

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 179

Functional Description

NOTES:

1. The OCW1 register must be read before entering ALT access mode.

2. Bits 5, 3, 1, and 0 return 0.

08h 6

1 DMA Chan 0–3 Command2

CAh 2 1DMA Chan 6 base count low

byte

2 DMA Chan 0–3 Request 2 DMA Chan 6 base count

high byte

3DMA Chan 0 Mode:

Bits(1:0) = 00 CCh 2 1DMA Chan 7 base address

low byte

4DMA Chan 1 Mode:

Bits(1:0) = 01 2DMA Chan 7 base address

high byte

5DMA Chan 2 Mode:

Bits(1:0) = 10 CEh 2 1DMA Chan 7 base count low

byte

6DMA Chan 3 Mode: Bits(1:0)

= 11. 2DMA Chan 7 base count

high byte

20h 12

1 PIC ICW2 of Master controller

D0h 6

1 DMA Chan 4–7 Command2

2 PIC ICW3 of Master controller 2 DMA Chan 4–7 Request

3 PIC ICW4 of Master controller 3 DMA Chan 4 Mode:

Bits(1:0) = 00

4PIC OCW1 of Master

controller14DMA Chan 5 Mode:

Bits(1:0) = 01

5PIC OCW2 of Master

controller 5DMA Chan 6 Mode:

Bits(1:0) = 10

6PIC OCW3 of Master

controller 6DMA Chan 7 Mode:

Bits(1:0) = 11.

7 PIC ICW2 of Slave controller

8 PIC ICW3 of Slave controller

9 PIC ICW4 of Slave controller

10 PIC OCW1 of Slave

controller1

11 PIC OCW2 of Slave controller

12 PIC OCW3 of Slave controller

Table 5-36. Write Only Registers with Read Paths in ALT Access Mode (Sheet 2 of 2)

Restore Data Restore Data

I/O

Addr # of

Rds Access Data I/O

Addr # of

Rds Access Data

Functional Description

180 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.13.10.2 PIC Reserved Bits

Many bits within the PIC are reserved, and must hav e certain values written in order for

the PIC to operate properly. Therefore, there is no need to return these values in ALT

access mode. When reading PIC registers from 20h and A0h, the reserved bits shall

return the values listed in Table 5-37.

5.13.10.3 Read Only Registers with Write Paths in ALT Access Mode

The registers described in Table 5-38 have write paths to them in ALT access mode.

Software restores these values after returning from a powered down state. These

registers must be handled special by software. When in normal mode, writing to the

base address/count register also writes to the current address/count register.

Therefore, the base address/count must be written first, then the part is put into ALT

access mode and the current address/count register is written.

Table 5-37. PIC Reserved Bits Return Values

PIC Reserved Bits Value Returned

ICW2(2:0) 000

ICW4(7:5) 000

ICW4(3:2) 00

ICW4(0) 0

OCW2(4:3) 00

OCW3(7) 0

OCW3(5) Reflects bit 6

OCW3(4:3) 01

Table 5-38. Register Write Accesse s in ALT Access Mode

I/O Address Register Write Value

08h DMA Status Register for channels 0–3.

D0h DMA Statu s Register for channels 4–7.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 181

Functional Description

5.13.11 System Power Supplies, Planes, and Signals

5.13.11.1 P ower Plane Control with SLP_S3#, SLP_S4#, SLP_S5# and SLP_M#

The SLP_S3# output signal can be used to cut power to the system core supply, since it

only goes active for the Suspend-to-RAM state (typically mapped to ACPI S3). Power

must be maintained to the ICH9 suspend well, and to any other circuits that need to

generate Wake signals from the Suspend-to-RAM state. During S3 (Suspend-to-RAM)

all signals attached to powered down plans will be tri-stated or driv en low, unless they

are pulled via a pull-up resistor.

Cutting power to the core may be done via the power supply, or by external FETs on the

motherboard.

The SLP_S4# or SLP_S5# output signal can be used to cut power to the system core

supply, as well as power to the system memory, since the context of the system is

saved on the disk. Cutting power to the memory may be done via the power supply, or

by external FETs on the motherboard.

The SLP_S4# output signal is used to re mo ve power to additional subsystems that are

powered during SLP_S3#.

SLP_S5# output signal can be used to cut power to the system core supply, as well as

power to the system memory, since the context of the system is saved on the disk.

Cutting power to the memory may be done via the power supply, or by external FETs

on the motherboard.

SLP_M# output signal can be used to cut power to the Controller Link, Clock chip and

SPI flash on a platform that supports Intel® AMT (Digital Office only) or ASF.

5.13.11.2 SLP_S4# and Suspend-To-RAM Sequencing

The system memory suspend voltage regulator is controlled by the Glue logic. The

SLP_S4# signal should be used to remove power to system memory rather than the

SLP_S5# signal. The SLP_S 4# logic in the ICH9 provides a mechanism to fully cycle

the power to the DRAM and/or detect if the power is not cycled for a minimum time.

Note: To utilize the minimum DRAM power-down feature that is enabled by the SLP_S4#

Assertion Stretch Enable bit (D31:F0:A4h bit 3), the DRAM power must be controlled

by the SLP_S4# signal.

Functional Description

182 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.13.11.3 PWROK Signal

The PWROK input should go active no sooner than 99 ms after the core supply voltages

becoming valid. PWROK must not glitch, even if RSMRST# is low.

Note:

1. SYSRESET# is recommended for implementing the system reset button. This saves

external logic that is needed if the PWROK input is used. Additionally, it allows for

better handling of the SMBus and processor resets, and avoids improperly

reporting power failures.

2. PWROK and RSMRST# are sampled using the RTC clock. Therefore, low times that

are less than one RTC clock period may not be detected by the ICH9.

3. In the case of true PWROK failure, PWROK will go low before VRMPWRGD.

4. When PWROK goes inactive, a host power cycle reset will occur. A host power cycle

is the assertion of SLP_S3#, SLP_S4#, and SLP_S 5#, and the deassertion of these

signals 3-5 seconds later. The Management Engine remains powered throughout

this cycle.

5.13.11.4 C PUPWRGD Signal

This signal is connected to the processor’s VRM via the VRMPWRGD signal and is

internally AND’d with the PWROK signal that comes from the system power supply.

5.13.11.5 VRMPWRGD Signal

VRMPWRGD is an input from the regulator indicating that all of the outputs from the

regulator are on and within specification. Platforms that use the VRMPWRGD signal to

start the clock chip PLLs assume that it asserts milliseconds before PWROK in order to

provide valid clocks in time for the PWROK rising.

Note: When VRMPWRGD goes inactive, a host power cycle reset will occur. A host power cycle

is the assertion of SLP_S3#, SLP_S4#, and SLP_S5#, and the deass ertion of these

signals 3-5 seconds later. The Management Engine remains powered throughout this

cycle.

5.13.11.6 BATLOW# (Battery Low) (Mobile Only)

The BATLOW# input can inhibit waking from S3, S4, and S5 states if there is not

sufficient power. It also causes an SMI# if the system is already in an S0 state.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 183

Functional Description

5.13.12 Clock Generators

The clock generator is expected to provide the frequencies shown in Table 5-39.

5.13.12.1 Clock Control Signals from Intel® ICH9 to Clock

Synthesizer (Mobile Only)

The clock generator is assumed to hav e direct connect from the following ICH9 signals:

• STP_CPU#: Stops processor clocks in C3 and C4 states

• STP_PCI#: Stops system PCI clocks (not the ICH9 free-running 33 MHz clock) due

to CLKRUN# protocol

• SLP_S3#: Expected to drive clock chip PWRDOWN (through inverter), to stop

clocks in S3 to S5.

Table 5-39. Intel® ICH9 Clock Inputs

Clock

Domain Frequency Source Usage

SATA_CLK 100 MHz

Differential Main Clock

Generator Used by SATA controller. Stopped in S3 – S based on

SLP_S3# assertion.

DMI_CLK 100 MHz

Differential Main Clock

Generator Used by DMI and PCI Express*. Stopped in S3 – S5

based on SLP_S3# assertion.

PCICLK 33 MHz Main Clock

Generator

Desktop: Free-running PCI Clock to ICH9. Stopped in

S3 – S5 based on SLP_S3# assertion.

Mobile: Free-running (not affected by STP_PCI# PCI

Clock to ICH9. Th is is not the sy stem PCI clock. This

clock must keep running in S0 while the system PCI

clock may stop based on CLKRUN# protocol. Stopped

in S3 – S5 based on SLP_S3# assertion.

CLK48 48.000 MHz Main Clock

Generator

Used by USB controllers and Int el® High Definition

Audio controller. Stopped in S3 – S5 based on

SLP_S3# assertion.

CLK14 14.318 MHz Main Clock

Generator Used by ACPI timers. Stopped in S3 – S5 based on

SLP_S3# assertion.

GLAN_CLK 5 to

62.5 MHz

Platform

LAN

Connect

LAN Connect Interface and Gigabit LAN Connect

Interface. Control policy is determined by the clock

source.

Functional Description

184 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.13.13 Legacy Power Management Theory of Operation

Instead of relying on ACPI software, legacy power management uses BIOS and v arious

hardware mechanisms. The scheme relies on the concept of detecting when individual

subsystems are idle, detecting when the whole system is idle, and detecting when

accesses are attempted to idle subsystems.

However, the operating system is assumed to be at least APM enabled. Without APM

calls, there is no quick way to know when the system is idle between keystrokes. The

ICH9 does not support burst modes.

5.13.13.1 APM Power Management (Desktop Only)

The ICH9 has a timer that, when enabled by the 1MIN_EN bit in the SMI Control and

Enable register, ge nerates an SMI# once per minute. The SMI handler can check for

system activity by reading the DEVACT_STS register. If none of the system bits are set,

the SMI handler can increment a software counter. When the counter reaches a

sufficient number of consecutive minutes with no activity, the SMI handler can then put

the system into a lower power state.

If there is activity, various bits in the DEVACT_STS register will be set. Software clears

the bits by writing a 1 to the bit position.

The DEVACT_STS register allows for monitoring various internal devices, or Super I/O

devices (SP, PP, FDC) on LPC or PCI, keyboard controller accesses, or audio functions

on LPC or PCI. Other PCI activity can be monitored by checking the PCI interrupts.

5.13.13.2 Mo bile APM Power Management (Mobile Only)

In mobile systems, there are additional requirements associated with device power

management. To handle this, the ICH9 has specific SMI# traps a v ailable. The following

algorithm is used:

1. The periodic SMI# timer checks if a device is idle for the require time. If so, it puts

the device into a low-power state and sets the associated SMI# trap.

2. When software (not the SMI# handler) attempts to access the device, a trap occurs

(the cycle does not really go to the device and an SMI# is generated).

3. The SM I# hand l er turns on the device and turns off the trap.

The SMI# handler exits with an I/O restart. This allows the original software to

continue.

5.13.14 Reset Behavior

When a reset is triggered, the ICH will send a warning message to the MCH to allow the

MCH to attempt to complete any outstanding memory cycles and put memory into a

safe state before the platform is reset. When the MCH is ready, it will send an

acknowledge message to the ICH. Once the message is received the ICH asserts

PLTRST#.

The ICH does not require an ackn owl e dg e mess a ge from the MCH to trigger PLTRST#.

A global reset will occur after 4 seconds if an acknowledge from the MCH is not

received.

Note: When the ICH causes a reset by asserting PLTRST# its output signals will go to their

reset states as defined in Chapter 3.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 185

Functional Description

A reset in which the host platform is reset and PLTRST# is asserted is called a Host

Reset or Host Partition Reset. Depending on the trigger a host reset may also result in

power cycling see Table 5-40 for details. If a host reset is triggered and the ICH times

out before receiving an acknowledge message from the MCH a Global R eset with power

cycle will occur. A reset in which the host and ME partitions of the platform are reset is

called a Global Reset.

The following table shows the various reset triggers:

NOTES:

1. Trigger will result in Global Reset with power cycle if the acknowledge message is not

received by the ICH.

2. ICH does not send warning message to MCH, reset occurs without delay.

3. ICH waits for enabled wake event to complete reset.

Table 5-40. Causes of Host and Global Resets

Trigger

Host Reset

without

Power

Cycle

Host Reset

with Power

Cycle

Global

Reset with

Power Cycle

Write of 0Eh to CF9h Register when Global Reset

bit = 0b No Yes No (Note 1)

Write of 06h to CF9h Register when Global Reset

bit = 0b Yes No No (Note 1)

Write of 06h or 0Eh to CF9h register when Global

Reset bit = 1b No No Yes

SYS_RESET# Asserted and CF9h bit 3 = 0 Yes No No (Note 1)

SYS_RESET# Asserted and CF9h bit 3 = 1 No Yes No (Note 1)

SMBus Slave Message received for Reset with

Power Cycle No Yes No (Note 1)

SMBus Slave Message received for Reset without

Power Cycle Yes No No (Note 1)

TCO Watchdog timer reaches zero two times Yes No No (Note 1)

Power F ail ure: PWROK signal or VRMP WROK signal

goes inactive or RSMRST# asserts No No Yes (Note 2)

Special shutdown cycle from CPU causes CF9h-like

PLTRST# and CF9h Global Reset bit = 1 No No Yes

Special shutdown cycle from CPU causes CF9h-like

PLTRST# and CF9h bit 3 = 1 No Yes No (Note 2)

Special Shutdown Cycle from CPU causes CF9h-

like PLTRST# and CF9h Global Reset bit = 0 Ye s No No (Note 1)

ME Triggered Host Reset without power cycle Yes No No (Note 1)

ME Triggered Host Reset with power cycle No Yes No (Note 1)

ME Triggered Global Reset No No Yes

ME Initiated Host Reset with power down No Yes (Note 3) No (Note 1)

Functional Description

186 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.14 System Management (D31:F0)

The ICH9 provides various functions to make a system easier to manage and to lower

the Total Cost of Ownership (TCO) of the system. In addition , ICH9 provides integr ated

ASF Management support, requires use of SPI Flash and Management Engine firmware.

Features and functions can be augmented via external A/D converters and GPIO, as

well as an external microcontroller.

The following features and functions are supported by the ICH9:

• Processor present detection

— Detects if processor fails to fetch the first instruction after reset

• Various Error detection (such as ECC Errors) indicated by host controller

— Can generate SMI#, SCI, SERR, NMI, or TCO interrupt

• Intruder Detect input

— Can generate TCO interrupt or SMI# when the system cover is removed

— INTRUDER# allowed to go active in any power state, including G3

• Detection of bad BIOS Flash (FWH or Flash on SPI) programming

— Detects if data on first read is FFh (indicates that BIOS flash is not

programmed)

• Ability to hide a PCI device

— Allows software to hide a PCI device in terms of configuration space through

the use of a device hide register (See Section 10.1.75)

Note: Vo ltage ID from the processor can be read via GPI signals. ASF functionality with the

integrated ICH9 ASF controller requires a correctly configured system, including an

appropriate component of the ICH9 (see Section 1.3), (G)MCH with Management

Engine, Management Engine Firmware, system BIOS support, and appropriate Platform

LAN Connect Device.

5.14.1 T heory of Operation

The System Management functions are designed to allow the system to diagnose failing

subsystems. The intent of this logic is that some of the system management

functionality can be provided without the aid of an external microcontroller.

5.14.1.1 Detecting a System Lockup

When the processor is reset, it is expected to fetch its first instruction. If the processor

fails to fetch the first instruction after reset, the TCO timer times out twice and the

ICH9 asserts PLTRST#.

5.14.1.2 Handling an Intruder

The ICH9 has an input signal, INTRUDER#, that can be attached to a switch that is

activated by the system’ s case being open. This input has a two R TC clock debounce. If

INTRUDER# goes active (after the debouncer), this will set the INTRD_DET bit in the

TCO_STS register. The INTRD_SEL bits in the TCO_CNT register can enable the ICH9 to

cause an SMI# or interrupt. The BIOS or interrupt handler can then cause a transition

to the S5 state by writing to the SLP_EN bit.

The software can also directly read the status of the INTRUDER# signal (high or low) by

clearing and then reading the INTRD_DET bit. This allows the signal to be used as a GPI

if the intruder function is not required.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 187

Functional Description

If the INTRUDER# signal goes inactive some point after the INTRD_DET bit is written

as a 1, then the INTRD_DET signal will go to a 0 when INTRUDER# input signal goes

inactive. Note that this is slightly different than a classic sticky bit, since most sticky

bits would remain active indefinitely when the signal goes active and would

immediately go inactive when a 1 is written to the bit.

Note: The INTRD_DET bit resides in the ICH9’s RTC well, and is set and cleared

synchronously with the RTC clock. Thus, when softw are attem pts to clear INTRD_DET

(by writing a 1 to the bit location) there may be as much as two RTC clocks (about 65

µs) delay before the bit is actually cleared. Also, the INTRUDER# signal should be

asserted for a minimum of 1 ms to ensure that the INTRD_DET bit will be set.

Note: If the INTRUDER# signal is still active when software attempts to clear the INTRD_DET

bit, the bit remains set and the SMI is generated again immediately. The SMI handler

can clear the INTRD_SEL bits to avoid further SMIs. Howev er, if the INTRUDER# signal

goes inactive and then active again, there will not be further SMIs, since the

INTRD_SEL bits would select that no SMI# be generated.

5.14.1.3 Detecting Improper Firmware Hub Programming

The ICH9 can detect the case where the BIOS flash is not programmed. This results in

the first instruction fetched to have a value of FFh. If this occurs, the ICH9 sets the

BAD_BIOS bit. The BIOS flash may reside in FWH or flash on the SPI bus.

5.14.1.4 Heartbeat and Event Reporting via SMLink/SMBus

Heartbeat and event reporting via SMLink/SMBus is no longer supported. The AMT logic

in ICH9 (Digital Office Only) can be programmed to generate an interrupt to the

Management Engine when an event occurs. The Management Engine will poll the TCO

registers to gather appropriate bits to send the event message to the Gigabit Ethernet

controller, if Management Engine is programmed to do so.

The Management Engine is responsible for sending ASF 2.0 messages if programmed to

do so.

In Advanced TCO BMC mode, the external micro-controller (BMC) accesses the TCO

info through SMBus.

5.14.2 TCO Modes

5.14.2.1 TCO Legacy/Compatible Mod e

In TCO Legacy/Compatible mode the Intel Management Engine and Intel AMT logic

(Digital Office only) and AMT SMBus controllers are disabled. To enable Legacy/

Compatible TCO mode the TCOMODE bit 7 in the ICHSTRP0 register in the SPI device

must be 0.

Note: SMBus and SMLink may be tied together externally, if a device has a single SMBus

interface and needs access to the TCO slave and be visisble to the host SMBus

controller.

Functional Description

188 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

In TCO Legacy/Compatible mode the Intel ICH9 can function directly with the

integrated Gigabit Ethernet controller or equivalent external LAN controller to report

messages to a network management console without the aid of the system processor.

This is crucial in cases where the processor is malfunctioning or cannot function due to

being in a low-power state. Table 5-41 includes a list of events that will report

messages to the network management console.

NOTE: The GPIO11/SMBALERT# pin will trigger an event message (when enabled by the

GPIO11_ALERT_DISABLE bit) regardless of whether it is configured as a GPI or not.

Figure 5-6. TCO Legacy/Compatible Mode SMBus Configuration

Host SMBus

TCO Slave

Intel® ICH9

SPD

(Slave) uCtrl

Legacy

Sensors

(Master or

Slave with

ALERT)

ASF

Sensors

(Master or

Slave)

TCO Compatible Mode

SMBus

Intel® AMT

SMBus

Controller 1

Intel® AMT

SMBus

Controller 2

SMLink

Table 5-41. Event Transitions that Cause Messages

Event Assertion? Deassertion? Comments

INTRUDER# pin yes no Must be in “S1 or hung S0” state

THRM# pin yes yes

Must be in “S1 or hung S0” state. Note

that the THRM# pin is isolated when

the core power is off, thus preventing

this event in S3-S5.

Watchdog Timer

Expired yes no (NA) “S1 or hung S0” state entered

GPIO[11]/

SMBALERT# pin yes yes Must be in “S1 or hung S0” state

BATLOW#

(Mobile On ly) yes yes Must be in “S1 or hung S0” state

CPU_PWR_FLR yes no “S1 or hung S0” state entered

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 189

Functional Description

5.14.2.2 Advanced TCO Mode

Intel ICH9 supports two modes of Advanced TCO. Intel® Active Management

Technology mode (Digital Office only) and BMC mode. To enable Advance TCO mode

(AMT or BMC mode) the TCOMODE bit 7 in the ICHSTRP0 register in the SPI device

must be 1.

5.14.2.2.1 Advanced TCO Intel® Active Management Technolo gy mode (Digital Office

Only)

In this mode, AMT SMBus Con troller 1, Host SMBus and SMLink are connected together

internally. See Figure 5-7. This mode is enabled when the BMCMODE bit 15 in the

ICHSTRP0 register in the SPI device is 0.

The AMT SMBus Controller 2 can be connected to either the SMBus pins or the SMLink

pins by the MESM2SEL bit 23 in the ICHSTRP0 register in the SPI device. The default is

to have the AMT SMBus Controller 2 connected to SMLink. The AMT SMBus Controller 2

has no connection to LINKALERT#.

5.14.2.2.2 Advanced TCO BMC Mode

In this mode, the external microcontroller (BMC) is connected to both SMLink and

SMBus. The BMC communicates with Management Engine through AMT SMBus

connected to SMLink. The host and TCO sla ve communicated with BMC through SMBus.

See Figure 5-8. This mode is enabled when the BMCMODE bit 15 in the ICHSTRP0

Figure 5-7. Advanced TCO Intel® AMT Mode SMBus/SMLink Configuration

AMT SMBus

Co n troller 1

Host SMBus

Intel® ICH9

SPD

(Slave) uCtrl

Legacy

Sensors

(Mas ter or

Slave with

ALERT)

ASF

Sensors

(Master or

Slave)

Advanced TCO AMT Mode

AMT SMBus

Co n troller 2

SMBus

TCO Slave

Embedded

Controller

SMLink

Intel® AMT

SMBus

Co n troller 1

Host SMBus

SPD

(Slave) uCtrl

Legacy

Sensors

(Mas ter or

Slave with

ALERT)

ASF

Sensors

(Master or

Slave)

Advanced TCO AMT Mode

Intel® AMT

SMBus

Co n troller 2

SMBus

TCO Slave

Embedded

Controller

SMLink

Functional Description

190 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.15 General Purpose I/O (D31:F0)

The ICH9 contains up to 61 General Purpose Input/Output (GPIO) signals. Each GPIO

can be configured as an input or output signal. The number of inputs and outputs

varies depending on ICH9 configuration.

5.15.1 Power Wells

Some GPIOs exist in the suspend power plane. Care must be taken to make sure GPIO

signals are not driven high into powered-down planes. Some ICH9 GPIOs may be

connected to pins on devices that exist in the core well. If these GPIOs are outputs,

there is a danger that a loss of core power (PWROK low) or a Power Button Override

event results in the ICH9 driving a pin to a logic 1 to another device that is powered

down.

5.15.2 SMI# and SCI Routing

The routing bits for GPIO[0:15] allow an input to be routed to SMI# or SCI, or neither.

Note that a bit can be routed to either an SMI# or an SCI, but not both.

Figure 5-8. Advanced TC O BMC Mode SM Bus/SMLink Configurat ion

Host SMBu s

TCO Slave

Intel® ICH9

SPD

(Slave)

Legacy

Sensors

(Master or

Slave with

ALERT)

ASF

Sensors

(Master or

Slave)

Advanced TCO BMC Mode

Intel® AMT

SMBus

Controller 1

SMBus

BMC

SMLink

Intel® AMT

SMBus

Controller 2

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 191

Functional Description

5.15.3 Triggering

GPIO[1:15] have “sticky” bits on the input. Refer to the GPE0_STS register. As long as

the signal goes active for at least 2 clock cycles, the ICH9 keeps the sticky status bit

active. The active level can be selected in the GP_LVL register. If the system is in an S0

or an S1 state, the GPI inputs are sampled at 33 MHz, so the signal only needs to be

active for about 60 ns to be latched. In the S3–S5 states, the GPI inpu ts are sampled at

32.768 kHz, and thus must be active for at least 61 microseconds to be latched. If the

input signal is still active when the latch is cleared, it will again be set. Another edge

trigger is not required. This makes these signals “level” triggered inputs.

5.15.4 Serial POST Codes Over GPIO

ICH9 adds the extended capability allowing system software to serialize POST or other

messages on GPIO. This capability negates the requirement for dedicated diagnostic

LEDs on the platform. Additionally, based on the newer BTX form factors, the PCI bus

as a target for POST codes is increasingly difficult to support as the total number of PCI

devices supported are decreasing.

5.15.4.1 Theory of operatio n

For the ICH9 generation POST code serialization logic will be shared with GPIO. These

GPIOs will likely be shared with LED control offered by the Super I/O (SIO) component.

The following reference diagram shows a likely configuration.

The anticipated usage model is that either the ICH9 or the SIO can drive a pin low to

turn off an LED. In the case of the power LED, the SIO would normally leave its

corresponding pin in a high-Z state to allow the LED to turn on. In this state, the ICH9

can blink the LED by driving its corresponding pin low and subsequently tri-stating the

buffer.

An external optical sensing device can detect the on/off state of the LED. By externally

post-processing the information from the optical device, the serial bit stream can be

recovered. The hardware will supply a ‘sync’ byte before the actual data transmission

to allow external detection of the transmit frequency. The frequency of transmission

should be limited to 1 transition every 1μs to ensure the detector can reliably sample

Figure 5-9. Serial Post over GPIO Reference Circuit

ICH SIO

V_3P3_STBY

LED

Note: The pull-up value is based on the brightness required.

Functional Description

192 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

the on/off state of the LED. To allow flexibility in pull-up resistor values for power

optimization, the frequency of the transmission is programmable via the DRS field in

the GP_SB_CMDSTS register (Section 13.10.6).

The serial bit stream is Manchester encoded. This choice of transmission ensures that a

transition will be seen on every clock. The 1 or 0 data is based on the transmission

happening during the high or low phase of the clock.

A simplified hardware/software register interface provides control and status

information to track the activity of this block. Software enabling the serial blink

capability should implement an algorithm referenced below to send the serialized

message on the enabled GPIO.

1. Read the Go/Busy status bit in the GP_SB_CMDSTS register and verify it is cleared.

This will ensure that the GPIO is idled and a previously requested message is still

not in progress.

2. Write the data to serialize into the GP_SB_DATA register (Section 13.10.7).

3. W rite the DLS and DRS values into the GP_SB_CMDSTS register and set the Go bit.

This may be accomplished using a single write.

The reference diagram shows the LEDs being powered from the suspend supply. By

providing a generic capability that can be used both in the main and the suspend power

planes maximum flexibility can be achieved. A key point to make is that the ICH will not

unintentionally drive the LED control pin low unless a serialization is in progress.

System board connections utilizing this serialization capability are required to use the

same power plane controlling the LED as the ICH9 GPIO pin. Otherwise, the ICH9 GPIO

may float low during the message and prevent the LED from being controlled from the

SIO. The hardware will only be serializing messages when the core power well is

powered and the processor is operational.

Care should be taken to prevent the ICH9 from driving an active ‘1’ on a pin sharing the

serial LED capability. Since the SIO could be driving the line to 0, having the ICH drive

a 1 would create a high current path. A recommendation to avoid this condition

involves choosing a GPIO defaulting to an input. The GP_SER_BLINK register

(Section 13.10.7) should be set first before changing the direction of the pin to an

output. This sequence ensures the open-drain capability of the buffer is properly

configured before enabling the pin as an output.

5.15.4.2 Serial Message Format

In order to serialize the data onto the GPIO, an initial state of high-Z is assumed. The

SIO is required to have its LED control pin in a high-Z state as well to allow ICH9 to

blink the LED (refer to the reference diagram).

The three components of the serial message include the sync, data, and idle fields. The

sync field is 7 bits of ‘1’ data followed by 1 bit of ‘0’ data. Starting from the high-Z state

(LED on) provides external hardw are a know n initial condition and a known pattern. In

case one or more of the leading 1 sync bits are lost, the 1s followed by 0 provide a

clear indication of ‘end of sync’. This pattern will be used to ‘lock’ external sampling

logic to the encoded clock.

The data field is shifted out with the highest byte first (MSB). Within each byte, the

most significant bit is shifted first (MSb).

The idle field is enforced by the hardware and is at least 2 bit times long. The hardware

will not clear the Busy and Go bits until this idle time is met. Supporting the idle time in

hardware prev ents time-based coun ting in BIOS as the hardware is immediately ready

for the next serial code when the Go bit is cleared. Note that the idle state is

represented as a high-Z condition on the pin. If the last transmitted bit is a 1, retu rning

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 193

Functional Description

to the idle state will result in a final 0-1 transition on the output Manchester data. Two

full bit times of idle correspond to a count of 4 time intervals (the width of the time

interval is controlled by the DRS field).

The following waveform shows a 1-byte serial write with a data byte of 5Ah. The

internal clock and bit position are for reference purposes only. The Manchester D is the

resultant data generated and serialized onto the GPIO. Since the buffer is operating in

open-drain mode the transitions are from high-Z to 0 and back.

5.15.5 Controller Link GPIOs (Digital Office Only)

The following GPIOs can be used as Controller Link GPIOs: GPIO9/WOL_EN, GPIO10/

CLGPIO1 (Desktop)/SUS_PWR_ACK (Mobile), GPIO14/CLGPIO2 (Desktop)/

AC_PRESENT (Mobile), GPIO24/MEM_LED, GPIO60/CLGPIO4, GPIO57/CLGPIO5 and

GPIO58/CLGPIO6. Controller Link GPIOs are only available on Intel® AMT or ASF

enabled platforms with supporting Management Engine Firmware. Controller Link

GPIOs are owned by the management engine and are configured by Management

Engine firmware. When configured a a Controller Link GPIO the GPIO_USE_SEL bit is

ignored. If the Controller Link GPIO is utilized in a platform, its associated GPIO

functionality is no longer av ailable to the host. If the Controller Link GPIO is not utilized

in a platform, the signal can instead be used as its associated General Purpose I/O.

5.16 SATA Host Controller (D31:F2, F5)

The SATA function in the ICH9 has three modes of operation to support different

operating system conditions. In the case of Native IDE enabled operating systems, the

ICH9 utilizes two controllers to enable all six ports of the bus. The first controller

(Device 31: Function 2) supports ports 0 -3 and the second controller (Device 31:

Function 5) supports ports 4 and 5. When using a legacy operating system, only one

controller (Device 31: Function 2) is available that supports ports 0 - 3. In AHCI or

RAID mode, only one controller (Device 31: Function 2) is utilized enabling all six ports.

The MAP register, Section 15.1.29, provides the ability to share PCI functions. When

sharing is enabled, all decode of I/O is done through the SATA registers. Device 31,

Function 1 (IDE controller) is hidden by software writing to the Function Disable

The ICH9 SATA controllers feature six (desktop only) / four (mobile only) sets of

interface signals (ports) that can be independently enabled or disabled (they cannot be

tri-stated or driven low). Each interface is supported by an independent DMA controller.

The ICH9 SATA controllers interact with an attached mass storage device through a

The host software follows existing standards and conventions when accessing the

Note: SATA interface transfer rates are independent of UDMA mode settings. SATA interface

transfer rates will operate at the bus’s maximum speed, regardless of the UDMA mode

reported by the SATA device or the system BIOS.

I nt ernal Clo c k

M anchest e r D

8-bit sync field

(1111_1110)

Bit 7 0123456

5A data byte 2 clk

idle

Functional Description

194 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.16.1 SATA Feature Support

Feature ICH9

(AHCI/RAID

Disabled)

ICH9

(AHCI/RAID

Enabled)

Native Command Queuing (NCQ) N/A Supported

Auto Activate for DMA N/A Supported

Hot Plug Support N/A Supported

Asynchronous Signal Recovery N/A Supported

3 Gb/s Transfer Rate Supported Supported

ATAPI Asynchronous Notification N/A Supported

Host & Link Initiated Power

Management N/A Supported

Staggered Spin-Up Supported Supported

Command Completion Coalescing N/A N/A

External SATA N/A Supported

Feature Description

Native Command Queuing

(NCQ) Allows the device to reorder commands for more efficient data

transfers

Auto Activate for DMA Collapses a DMA Setup then DMA Activate sequence into a DMA

Setup only

Hot Plug Support Allows for device detection without power being applied and

ability to connect and disconnect devices without prior

notification to the system

Asynchronous Signal

Recovery Provides a recovery from a loss of signal or establishing

communication afte r hot plug

3 Gb/s Transfer Rate Capable of data transfers up to 3Gb/s

ATAPI Asynchronous

Notification A mechanism for a device to send a notification to the host that

the device requires attention

Host & Link Initiated Power

Management Capability for the host controller or device to request Partial and

Slumber interface power states

Staggered Spin-Up Enables the host the ability to spin up hard drives se quentially

to prevent power load problems on boot

Command Completion

Coalescing

Reduces interrupt and completion overhead by allowing a

specified number of commands to complete and then generating

an interrupt to process the commands

External SATA Technology that allows for an outside the box connection of up

to 2 meters (when usin g the cable defined in SATA-IO)

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 195

Functional Description

5.16.2 Theory of Operation

5.16.2.1 Standard ATA Emulation

The ICH9 contains a set of registers that shadow the contents of the legacy IDE

registers. The behavior of the Command and Control Block registers, PIO, and DMA

data transfers, resets, and interrupts are all emulated.

Note: The ICH9 will assert INTR when the master device completes the EDD command

regardless of the command completion status of the slave device. If the master

completes EDD first, an INTR is generated and BSY will remain '1' until the slave

completes the command. If the slave completes EDD first, BSY will be '0' when the

master completes the EDD command and asserts INTR. Software must wait for busy to

clear (0) before completing an EDD command, as required by the ATA5 through ATA7

(T13) industry standards.

5.16.2.2 48-Bit LBA Operation

The SATA host controller supports 48-bit LBA through the host-to-device register FIS

when accesses are performed via writes to the task file. The SATA host controller will

ensure that the correct data is put into the correct byte of the host-to-device FIS.

There are special considerations when reading from the task file to support 48-bit LBA

operation. Software may need to read all 16-bits. Since the registers are only 8-bits

wide and act as a FIFO, a bit must be set in the device/control register, which is at

offset 3F6h for primary and 376h for secondary (or their native counterparts).

If software clears bit 7 of the control register before performing a read, the last item

written will be returned from the FIFO. If software sets bit 7 of the control register

before performing a read, the first item written will be returned from the FIFO.

5.16.3 SATA Swap Bay Support

The ICH9 provides for basic SATA swap bay support using the PSC register

configuration bits and power management flows. A device can be powered down by

software and the port can then be disabled, allowing removal and insertion of a new

device.

Note: This SATA swap bay operation requires board hardware (implementation specific),

BIOS, and oper ating system support.

5.16.4 Hot Plug Operation

ICH9 supports Hot Plug Surprise removal and Insertion Notification in the PARTIAL,

SLUMBER and Listen Mode states when used with Low Power Device Presence

Detection. Software can take advantage of power savings in the low power states while

enabling hot plug operation. Refer to chapter 7 of the AHCI specification for details.

5.16.4.1 Low Power Device Presence Detection

Low Power Device Presence Detection enables SATA Link Power Management to co-

exist with hot plug (insertion and removal) without interlock switch or cold presence

detect. The detection mechanism allows Hot Plug events to be detectable by hardware

across all link power states (Active, PARTIAL, SLUMBER) as well as AHCI Listen Mode.

If the Low Power Device Presence Detection circuit is disabled the ICH9 reverts to Hot

Plug Surprise Removal Notification (without an interlock switch) mode that is mutually

exclusive of the PARTIAL and SLUMBER power management states.

Functional Description

196 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.16.5 Function Level Reset Support (FLR)

The SATA Host Controller supports the Function Level Reset (FLR) capability. The FLR

capability can be used in conjunction with Intel® Virtualization Technology. FLR allows

an Operating System in a Virtual Machine to have complete control over a device,

including its initialization, without interfering with the rest of the platform. The device

provides a software interface that enables the Operating System to reset the whole

device as if a PCI reset was asserted.

5.16.5.1 FLR Steps

5.16.5.1.1 FLR Initialization

1. A FLR is initiated by software writing a ‘1’ to the Initiate FLR bit.

2. All subsequent requests targeting the Function will not be claimed and will be

Master Abort Immediate on the bus. This includes any configuration, I/O or

Memory cycles, however, the Function shall continue to accept completions

targeting the Function.

5.16.5.1.2 FLR Operation

The Function will Reset all configuration, I/O and memory registers of the Function

except those indicated otherwise and reset all internal states of the Function to the

default or initial condition.

5.16.5.1.3 FLR Completion

The Initiate FLR bit is reset (cleared) when the FLR reset is completed. This bit can be

used to indicate to the software that the FLR reset is completed.

Note: From the time Initiate FLR bit is written to '1' software must wait at least 100 ms

before accessing the function.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 197

Functional Description

5.16.6 Intel® Matrix Storage Technology Configuration (Intel®

ICH9R, ICH9DH, ICH9DO, ICH9M and ICH9M-E Only)

The Intel® Matrix Storage Technology offers several diverse options for RAID

(redundant array of independent disks) to meet the needs of the end user. AHCI

support provides higher performance and alleviates disk bottlenecks by taking

advantage of the independent DMA engines that each SATA port offers in ICH9.

• RAID Level 0 performance scaling up to 4 drives, enabling higher throughput for

data intensive applications such as video editing.

• Data security is offered through RAID Level 1, which performs mirroring.

• RAID Level 10 provides high levels of storage performance with data protection,

combining the fault-tolerance of RAID Level 1 with the performance of RAID Level

0. By striping RAID Level 1 segments, high I/O rates can be achieved on systems

that require both performance and fault-tolerance. RAID Level 10 requires 4 hard

drives, and provides the capacity of two drives.

• RAID Level 5 provides highly efficient storage while maintaining fault-tolerance on

3 or more drives. By striping parity, and rotating it across all disks, fault tolerance

of any single drive is achieved while only consuming 1 drive worth of capacity. That

is, a 3 drive RAID 5 has the capacity of 2 drives, or a 4 drive RAID 5 has the

capacity of 3 drives. RAID 5 has high read transaction rates, with a medium write

rate. RAID 5 is well suited for applications that require high amounts of storage

while maintaining fault tolerance.

Note: Intel® Matrix Storage Technology RAID functionality not supported on ICH9M base

component.

By using the ICH9’s built-in Intel Matrix Storage Technology, there is no loss of PCI

resources (request/grant pair) or add-in card slot.

Intel® Matrix Storage Technology functionality requires the following items:

1. ICH9 component enabled for Intel Matrix Storage Technology (see Section 1.3)

2. Intel Matrix Storage Manager RAID Option ROM must be on the platform

3. Intel Matrix Storage Manager drivers, most recent revision.

4. At least two SATA hard disk drives (minimum depends on RAID configuration).

Intel Matrix Storage Technology is not available in the following configurations:

1. The SATA controller is in compatible mode.

5.16.6.1 Intel® Matrix Storage Manager RAID Option ROM

The Intel Matrix Storage Manager RAID Option ROM is a standard PnP Option ROM that

is easily integrated into any System BIOS. When in place, it provides the following

three primary functions:

• Provides a text mode user interface that allows the user to manage the RAID

configuration on the system in a pre-oper ating system environment. Its feature set

is kept simple to keep size to a minimum, but allows the user to create & delete

RAID volumes and select recovery options when problems occur.

• Provides boot support when using a RAID volume as a boot disk. It does this by

providing Int13 services when a RAID volume needs to be accessed by DOS

applications (such as NTLDR) and by exporting the RAID volumes to the System

BIOS for selection in the boot order.

• At each boot up, provides the user with a status of the RAID volumes and the

option to enter the user interface by pressing CTRL-I.

Functional Description

198 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.16.7 Power Management Operation

Power management of the ICH9 SATA controller and ports will cover operations of the

host controller and the SATA wire.

5.16.7.1 Power State Mappings

The D0 PCI power management state for device is supported by the ICH9 SATA

controller.

SATA devices may also have multiple power states. From parallel ATA, three device

states are supported through ACPI. They are:

•D0 – Device is working and instantly available.

•D1 – device enters when it receives a ST ANDBY IMMEDIA TE command. Exit latency

from this state is in seconds

•D3 – from the SATA device’s perspective, no different than a D1 state, in that it is

entered via the STANDBY IMMEDIATE command. However, an ACPI method is also

called which will reset the device and then cut its power.

Each of these device states are subsets of the host controller’s D0 state.

Finally, SA TA defines three PHY layer power states, which hav e no equivalent mappings

to parallel ATA. They are:

•PHY READY – PHY logic and PLL are both on and active

•Partial – PHY logic is powered, but in a reduced state. Exit latency is no longer

than 10 ns

•Slumber – PHY logic is powered, but in a reduced state. Exit latency can be up to

10 ms.

Since these states have much lower exit latency than the ACPI D1 and D3 states, the

SATA controller defines these states as sub-states of the device D0 state.

Figure 5-10. SATA Power States

Intel® ICH SATA Controller = D0

Device = D3

Power

Resume Latency

Device = D0

PHY =

Ready

Device = D1

PHY =

Slumber

PHY =

Partial PHY =

Off (port

disabled)

PHY =

Slumber PHY =

Off (port

disabled)

PHY =

Slumber PHY =

Off (port

disabled)

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 199

Functional Description

5.16.7.2 Power State Transitions

5.16.7.2.1 Partial and Slumber State Entry/Exit

The partial and slumber states save interface power when the interface is idle. It would

be most analogous to PCI CLKRUN# (in power savings, not in mechanism), where the

interface can have power saved while no commands are pending. The SATA controller

defines PHY layer power management (as performed via primitives) as a driver

operation from the host side, and a device proprietary mechanism on the device side.

The SATA controller accepts device transition types, but does not issue any transitions

as a host. All received requests from a SATA device will be ACKed.

When an operation is performed to the SATA controller such that it needs to use the

SATA cable, the controller must check whether the link is in the Partial or Slumber

states, and if so, must issue a COM_WAKE to bring the link back online. Similarly, the

SATA device must perform the same action.

5.16.7.2.2 Device D1, D3 States

These states are entered after some period of time when software has determined that

no commands will be sent to this device for some time. The mechanism for putting a

device in these states does not involve any work on the host controller, other then

sending commands over the interface to the device. The command most likely to be

used in ATA/ATAPI is the “STANDBY IMMEDIATE” command.

5.16.7.2.3 Host Controller D3HOT State

After the interface and device have been put into a low power state, the SATA host

controller may be put into a low power state. This is performed via the PCI power

management registers in configuration space. There are two very important aspects to

note when using PCI power manageme nt.

1. When the power state is D3, only accesses to configur ation space are allowed. An y

attempt to access the memory or I/O spaces will result in master abort.

2. When the power state is D3, no interrupts may be generated, even if they are

enabled. If an interrupt status bit is pending when the controller transitions to D0,

an interrupt may be generated.

When the controller is put into D3, it is assumed that software has properly shut down

the device and d isabled the ports. Ther efore, there is no need to sustain an y v alues on

the port wires. The interface will be treated as if no device is present on the cable, and

power will be minimized.

When returning from a D3 state, an internal reset will not be performed.

5.16.7.2.4 Non-AHCI Mode PME# Generation

When in non-AHCI mode (legacy mode) of operation, the SATA controller does not

generate PME#. This includes attach events (since the port must be disabled), or

interlock switch events (via the SATAGP pins).

Functional Description

200 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.16.7.3 SMI Trapping (APM)

Device 31:Function2:Offset C0h (see Section 14.1.37) contain control for generating

SMI# on accesses to the IDE I/O spaces. These bits map to the legacy ranges (1F0–

1F7h, 3F6h, 170–177h, and 376h) and native IDE r anges defined by PCMDBA, PCTLBA,

SCMDBA an SCTLBA. If the SATA controller is in legacy mode and is using these

addresses, accesses to one of these ranges with the appropriate bit set causes the

cycle to not be forwarded to the S A T A controller, and for an SMI# to be gener ated. If an

access to the Bus-Master IDE registers occurs while trapping is enabled for the device

being accessed, then the register is updated, an SMI# is generated, and the device

activity status bits (Section 14.1.38) are updated indicating that a trap occurred.

5.16.8 SATA Device Presence

In legacy mode, the SATA controller does not generate interrupts based on hot plug/

unplug events. However, the SA TA PHY does know when a device is connected (if not in

a partial or slumber state), and it s beneficial to communicate this information to host

software as this will greatly reduce boot times and resume times.

The flow used to indicate SATA device presence is shown in Figure 5-11. The ‘PxE’ bit

refers to PCS.P[3:0]E bits, depending on the port being checked and the ‘PxP’ bits refer

to the PCS.P[3:0]P bits, depending on the port being checked. If the PCS/PxP bit is set

a device is present, if the bit is cleared a device is not present. If a port is disabled,

software can check to see if a new device is connected by periodically reenabling the

port and observing if a device is present, if a device is not present it can disable the

port and check again later. If a port remains enabled, software can periodically poll

PCS.PxP to see if a new device is connected.

5.16.9 SATA LED

The SATALED# output is driven whenever the BSY bit is set in any SATA port. The

SATALED# is an active-low open-drain output. When SATALED# is low, the LED shou ld

be active. When SATALED# is high, the LED should be inactive.

Figure 5-11. Flow for Port Enable / Device Present Bits

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 201

Functional Description

5.16.10 AHCI Operation

The ICH9 provides hardware support for Advanced Host Controller Interface (AHCI), a

programming interface for SATA host controllers developed through a joint industry

effort. AHCI defines transactions between the SA T A controller and software and enables

advanced performance and usability with SATA. Platforms supporting AHCI may take

advantage of performance features such as no master/slave designation for SATA

devices—each device is treated as a master—and hardware assisted native command

queuing. AHCI also provides usability enhancements such as Hot-Plug. AHCI requires

appropriate software support (e.g., an AHCI driver) and for some features, hardware

support in the SATA device or additional platform hardware.

The ICH9 supports all of the mandatory features of the Serial ATA Advanced Host

Controller Interface Specification, Revision 1.2 and many optional features, such as

hardware assisted native command queuing, aggressive power management, LED

indicator support, and Hot-Plug through the use of interlock switch support (additional

platform hardware and softw are may be required depending upon the implementation).

Note: For reliable device removal notification while in AHCI operation without the use of

interlock switches (surprise removal), interface power management should be disabled

for the associated port. See Section 7.3.1 of the AHCI Specification for more

information.

5.16.11 Serial ATA Reference Clock Low Power Request

(SATACLKREQ#)

The 100 MHz Serial A T A R eference Clock (SA TACLKP, SA TACLKN) is implemented on the

system as a ground-terminated low-v oltage differential signal pair driven by the system

Clock Chip. When all the SATA links are in Slumber or disabled, the SATA Reference

Clock is not needed and may be stopped and tri-stated at the clock chip allowing

system-level power reductions.

The ICH9 uses the SAT A CLKREQ# output signal to communicate with the system Clock

Chip to request either SATA clock running or to tell the system clock chip that it can

stop the SATA Reference Clock. ICH9 drives this signal low to request clock running,

and tristates the signal to indicate that the SATA Reference Clock may be stopped (the

ICH9 never drives the pin high). When the SATACLKREQ# is tristated by the ICH9, the

clock chip may stop the SATA Reference Clock within 100 ns, anytime after 100 ns, or

not at all. If the SATA Reference Clock is not already running, it will start within 100 ns

after a SATACLKREQ# is driven low by the ICH9.

To enable SATA Reference Clock Low Power Request:

1. Configure GPIO35 to native function

2. Set SATA Clock Request Enable (SCRE) bit to ‘1’ (Dev 31:F2:Offset 94h:bit 28).

Note: The reset default for SATACLKREQ# is low to insure that the SATA Reference Clock is

running after system reset.

5.16.12 SGPIO Signals

The SGPIO signals, in accordance to the SFF-8485 specification, support per-port LED

signaling. These signals are not related to SATALED#, which allows for simplified

indication of SATA command activity. The SGPIO group interfaces with an external

controller chip that fetches and serializes the data for driving across the SGPIO bus.

The output signals then control the LEDs. This feature is only v alid in AHCI/RAID mode.

Functional Description

202 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.16.12.1 Mechanism

The enclosure management for SATA Controller 1 (Device 31: Function 2) involves

sending messages that control LEDs in the enclosure. The messages for this function

are stored after the normal registers in the AHCI BAR, at Offset 400h bytes for ICH9

from the beginning of the AHCI BAR as specified by the EM_LOC global register

(Section 14.4.1.8).

Software creates messages for transmission in the enclosure management message

buffer. The data in the message buffer should not be changed if CTL.TM bit is set by

software to transmit an update message. Software should only update the message

buffer when CTL.TM bit is cleared by hardware otherwise the message transmitted will

be indeterminate. Software then writes a register to cause hardware to transmit the

message or take appropriate action based on the message content. The software

should only create message types supported by the controller, which is LED messages

for ICH9. If the software creates other non LED message types (e.g. SAF-TE, SES-2),

the SGPIO interface may hang and the result is indeterminate.

During reset all SGPIO pins will be in tri-state state. The interface will continue to be in

tri-state state after reset until the first transmission occurs when software programs

the message buffer and sets the transmit bit CTL.TM. The SATA Host controller will

initiate the transmission by driving SCLOCK and at the same time drive the SLOAD to

‘0’ prior to the actual bit stream transmission. The Host will drive SLOAD low for at

least 5 SCLOCK then only start the bit stream by driving the SLOAD to high. SLOAD will

be driven high for 1 SCLOCK follow by vendor specific pattern that is default to “0000”

if software has yet to program the value. A total of 18-bit stream from 6 ports (Port0,

Port1, Port2, Port3, Port4 and Port5) of 3-bit per port LED message will be transmitted

on SDATAOUT0 pin after the SLOAD is driven high for 1 SCLOCK. Only 2 ports (port4

and port5) of 6 bit total LED message follow by 12 bits of tri-state value will be

transmitted out on SDATAOUT1 pin.

All the default LED message values will be high prior to software setting them, except

the Activity LED message that is configured to be hardware driven that will be

generated based on the activity from the respective port. All the LED message values

will be driven to ‘1’ for the port that is unimplemented as indicated in the Port

Implemented register regardless of the software programmed value through the

message buffer.

There are 2 different ways of resetting ICH SGPIO interface, asynchronous reset and

synchronous reset. Asynchronous reset is caused by platform reset to cause the SGPIO

interface to be tri-state asynchronously. Synchronous reset is caused by setting the

CTL.RESET bit, clearing the GHC.AE bit or HBA reset, where Host Controller will

complete the existing full bit stream transmission then only tri-state all the SGPIO pins.

After the reset, both synchronous and asynchronous, the SGPIO pins will stay tri-

stated.

Note: ICH Host Controller does not ensure to cause the target SGPIO device or controller to

be reset. Software is responsible to keep ICH SGPIO interface in tri-state stated for 2

second in order to cause a reset on the target of the SGPIO interface.

5.16.12.2 Message Format

Messages shall be constructed with a one Dword header that describes the message to

be sent followed by the actual message contents. The first Dword shall be constructed

as follows:

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 203

Functional Description

The SAF-TE, SES-2, and SGPIO message formats are defined in the corresponding

specifications, respectively. The LED message type is defined in Section 5.16.12.3. It is

the responsibility of software to ensure the content of the message format is correct. If

the message type is not progr ammed as 'LED' for this controller, the controller shall not

take any action to update its LEDs. Note that for LED message type, the message size

is always consisted of 4 bytes.

5.16.12.3 LED Message Type

The LED message type specifies the status of up to three LEDs. Typically, the usage for

these LEDs is activity, fault, and locate. Not all implementations necessarily contain all

LEDs (for example, some implementations may not have a locate LED). The message

identifies the HBA port number and the Port Multiplier port number that the slot status

applies to. If a Port Multiplier is not in use with a particular device, the Port Multiplier

port number shall be ‘0’. The format of the LED message type is defined in Table 5-42.

The LEDs shall retain their values until there is a following update for that particular

slot.

Bit Description

31:28 Reserved

27:24

Message Type (MTYPE): Specifies the type of the message.

The message types are:

0h = LED

1h = SAF-TE

2h = SES-2

3h = SGPIO (register based interface)

All other values reserved

23:16

Data Size (DSIZE): Specifies the data size in bytes. If t he message (enclosure

services command) has a data buffer that is associated with it that is transferred, the

size of that data buffer is specified in this field. If there is no separate data buffer, this

field shall have a value of ‘0’. The data directly follows the message in the message

buffer. For ICH9, this value should always be ‘0’.

15:8 Message Size (MSIZE): Specifies the size of the message i n by te s. Th e mes s age si ze

does not incl ude th e one Dword header. A value of ‘0’ i s inva li d. For IC H9, the message

size is always 4 bytes.

7:0 Reserved

Functional Description

204 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 5-42. Multi-activity LED Message Type

Byte Description

3-2

Value (VAL): This field describes the state of each LED for a particular location. There

are three LEDs that may be supported by the HBA. Each LED has 3 bits of control.

LED values are:

000b - LED shall be off

001b - LED shall be solid on as perceived by human eye

All other values reserved

The LED bit locations are:

Bits 2:0 - Activity LED (may be driven by hardware)

Bits 5:3 - Vendor Specific LED (e.g. locate)

Bits 8:6 - Vendor Specific LED (e.g. fau lt)

Bits 15:9 - Reserved

Vendor specific message is:

Bit 3:0 - Vendor Specific Pattern

Bit 15:4 - Reserved

Note: If Activity LED Hardware Driven (ATTR.ALHD) bit is set, host will output the

hardware LED v alue sampled internally and wi ll ignore software writte n activity v alue on

bit [2:0]. Since ICH9 E nclosure Management does not support port multiplier based LED

message, the LED message will be generated independently based on respective port’s

operation activity. Vendor specific LED values Locate (Bits 5:3) and Fault (Bits 8:6)

always are driven by software.

Port Multiplier Information: Specifies slot specific in formation related to Port

Multiplier.

Bits 3:0 specify the Port Multiplier port number for the slot that requires the status

update. If a Port Multiplier is not attached to the device in the affected slot, the Port

Multiplier port number shall be '0'. Bits 7:4 are reserved. ICH9 does not support LED

messages for devices behind a Port MUltiplier. This byte should be 0.

HBA Inform ati on: Specifies slot specific information related to the HBA.

Bits 4:0 - HBA port number for the slot that requires the status update.

Bit 5 - If set to '1', Value is a vendor specific message that applies to the entire

enclosure. If cleared to '0', Value applies to the port specified in bits 4:0.

Bits 7:6 - Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 205

Functional Description

5.16.12.4 SGPIO Waveform

Figure 5-12. Serial Data transmitted over the SGPIO Interface

Functional Description

206 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.16.13 External SATA

ICH9 supports external SATA. External SATA utilizes the SATA interface outside of the

system box. The usage model for this feature must comply with the Serial ATA II

Cables and Connectors Volume 2 Gold specification at www.sata-io.org. Intel validates

two configurations:

1. The cable-up solution involves an internal SATA cable that connects to the SATA

motherboard connector and spans to a back panel PCI bracket with an e-SATA

connector. A se parate e-SATA cable is required to connect an e-SATA device.

2. The back-panel solution involves running a trace to the I/O back panel and

connecting a device via an external SATA connector on the board.

5.17 High Precision Event Timers

This function provides a set of timers that can be used by the operating system. The

timers are defined such that in the future, the operating system may be able to assign

specific timers to used directly by specific applications. Each timer can be configured to

cause a separate interrupt.

ICH9 provides four timers. The four timers are implemented as a single counter each

with its own comparator and v alue register. This counter increases monotonically. Each

individual timer can generate an interrupt when the value in its value register matches

the value in the main counter.

The registers associated with these timers are mapped to a memory space (much like

the I/O APIC). However, it is not implemented as a standard PCI function. The BIOS

reports to the operating system the location of the register space. The hardware can

support an assignable decode space; however, the BIOS sets this space prior to

handing it over to the operating system

(See Section 9.4). It is not expected that the operating system will move the location

of these timers once it is set by the BIOS.

5.17.1 Timer Accuracy

1. The timers are accurate ov er any 1 ms period to within 0.05% of the time specified

in the timer resolution fields.

2. Within any 100 microsecon d period, the timer reports a time that is up to two ticks

too early or too late. Each tick is less than or equal to 100 ns, so this represents an

error of less than 0.2%.

3. The timer is monotonic. It does not return the same value on two consecutive

reads (unless the counter has rolled over and reached the same value).

The main counter is clocked by the 14.31818 MHz clock, synchronized into the 66.666

MHz domain. This results in a non-uniform duty cycle on the synchronized clock, but

does have the correct aver age period. The accur acy of the main counter is as accurate

as the 14.3818 MHz clock.

5.17.2 Interrupt Mapping

Mapping Option # 1 (Legacy Replacem ent Option)

In this case, the Legacy Replacement Rout bit (LEG_RT_CNF) is set. This forces the

mapping found in Table 5-43.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 207

Functional Description

Mapping Option #2 (Standard Option)

In this case, the Legacy Replacement Rout bit (LEG_RT_CNF) is 0. Each timer has its

own routing control. The interrupts can be routed to various interrupts in the 8259 or

I/O APIC. A capabilities field indicates which interrupts are valid options for routing. If a

timer is set for edge-triggered mode, the timers should not be share with any PCI

interrupts.

For the Intel ICH9, the only supported interrupt values are as follows:

Timer 0 and 1: IRQ20, 21, 22 & 23 (I/O APIC only).

Timer 2: IRQ11 (8259 or I/O APIC) and IRQ20, 21, 22 & 23 (I/O APIC only).

Timer 3: IRQ12 (8259 or I/O APIC) and IRQ 20, 21, 22 & 23 (I/O APIC only).

5.17.3 Periodic vs. Non-Periodic Modes

Non-Periodic Mode

Timer 0 is configurable to 32 (default) or 64-bit mod e, wh ereas Timers 1, 2 and 3 on ly

support 32-bit mode (See Section 21.1.5).

All four timers support non-periodic mode.

Consult Section 2.3.9.2.1 of the IA-PC HPET Specification for a description of this

mode.

Periodic Mode

Timer 0 is the only timer that supports periodic mode. Consult Section 2.3.9.2.2 of the

IA-PC HPET Specification for a description of this mode.

The following usage model is expected:

1. Software clears the ENABLE_CNF bit to prevent any interrupts

2. Software Clears the main counter by writing a value of 00h to it.

3. Software sets the TIMER0_VAL_SET_CNF bit.

4. Software writes the new value in the TIMER0_COMPARATOR_VAL register

5. Software sets the ENABLE_CNF bit to enable interrupts.

Table 5-43. Legacy Replacement Routing

Timer 8259 Mapping APIC Mapping Comment

0IRQ0 IRQ2

In this case, the 8254 timer will

not cause any interrupts

1IRQ8 IRQ8

In this case, the RT C will not cause

any interrupts.

2 & 3 Per IRQ Routing Field. Per IRQ Routing Field

Functional Description

208 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

The Timer 0 Comparator Value register cannot be programmed reliably by a single

64-bit write in a 32-bit environment except if only the periodic rate is being changed

during run-time. If the actual Timer 0 Comparator Value needs to be reinitialized, then

the following software solution will always work regardless of the environment:

1. Set TIMER0_VAL_SET_CNF bit

2. Set the lower 32 bits of the Timer0 Comparator Value register

3. Set TIMER0_VAL_SET_CNF bit

4. Set the upper 32 bits of the Timer0 Comparator Value register

5.17.4 Enabling the Timers

The BIOS or operating system PnP code should route the interrupts. This includes the

Legacy Rout bit, Interrupt Rout bit (for each timer), interrupt type (to select the edge

or level type for each timer)

The Device Driver code should do the following for an available timer:

1. Set the Overall Enable bit (Offset 04h, bit 0).

2. Set the timer type field (selects one-shot or periodic).

3. Set the interrupt enable

4. Set the comparator value

5.17.5 Interrupt Levels

Interrupts directed to the internal 8259s are active high. See Section 5.9 for

information regarding the polarity programming of the I/O APIC for detecting internal

interrupts.

If the interrupts are mapped to the 8259 or I/O APIC and set for level-triggered mode,

they can be shared with PCI interrupts. They may be shared although it’s unlikely for

the operating system to attempt to do this.

If more than one timer is configured to share the same IRQ (using the

TIMERn_INT_ROUT_CNF fields), then the software must configure the timers to level-

triggered mode. Edge-triggere d interrupts cannot be shared.

5.17.6 Handling Interrupts

If each timer has a unique interrupt and the timer has been configured for edge-

triggered mode, then there are no specific steps required. No read is required to

process the interrupt.

If a timer has been configured to level-triggered mode, then its interrupt must be

cleared by the software. This is done by reading the interrupt status register and

writing a 1 back to the bit position for the interrupt to be cleared.

Independent of the mode, software can read the value in the main counter to see how

time has passed between when the interrupt was generated and when it was first

serviced.

If Timer 0 is set up to generate a periodic interrupt, the software can check to see how

much time remains until the next interrupt by checking the timer value register.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 209

Functional Description

5.17.7 Issues Related to 64-Bit Timers with 32-Bit Processors

A 32-bit timer can be read directly using processors that are capable of 32-bit or 64-bit

instructions. However, a 32-bit processor may not be able to directly read 64-bit timer.

A race condition comes up if a 32-bit processor reads the 64-bit register using two

separate 32-bit reads. The danger is that just after reading one half, the other half rolls

over and changes the first half.

If a 32-bit processor needs to access a 64-bit timer, it must first halt the timer before

reading both the upper and lower 32-bits of the timer. If a 32-bit processor does not

want to halt the timer, it can use the 64-bit timer as a 32-bit timer by setting the

TIMERn_32MODE_CNF bit. This causes the timer to behave as a 32-bit timer. The upper

32-bits are always 0.

Alternatively, software may do a multiple read of the counter while it is running.

Software can read the high 32 bits, then the low 32 bits, the high 32 bits again. If the

high 32 bits have not changed between the two reads, then a rollover has not

happened and the low 32 bits are valid. If the high 32 bits have changed between

reads, then the multiple reads are repeated until a valid read is performed.

Note: On a 64-bit platform, if software attempts a 64 bit read of the 64-bit counter,

software must be aware that some platforms may split the 64 bit read into two 32 bit

reads. The read maybe inaccurate if the low 32 bits roll over between the high and low

reads.

5.18 USB UHCI Host Controllers (D29:F0, F1, F2, F3

and D26:F0, F1 and F2)

The ICH9 contains six USB full/low-speed host controllers that support the standard

Universal Host Controller Interface (UHCI), Revision 1.1. Each UHCI Host Controller

(UHC) includes a root hub with two separate USB ports each, for a total of twelve USB

ports.

• Overcurrent detection on all twelve USB ports is supported. The ov ercurrent inputs

are not 5 V tolerant, and can be used as GPIs if not needed.

• The ICH9’s UHCI host controllers are arbitrated differently than standard PCI

devices to improve arbitration latency.

• The UHCI controllers use the Analog Front End (AFE) embedded cell that allows

support for USB full-speed signaling rates, instead of USB I/O buffers.

Note: D26:F2 can be configured as D29:F3 during BIOS Post.

5.18.1 Data Structures in Main Memory

Section 3.1 - 3.3 of the Universal Host Controller Interface Specification, Revision 1.1

details the data structures used to communicate control, status, and data between

software and the ICH9.

5.18.2 Data Transfers to/from Main Memory

Section 3.4 of the Universal Host Controller Interface Specification, Revision 1.1

describes the details on how HCD and the ICH9 communicate via the Schedule data

structures.

Functional Description

210 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.18.3 Data Encoding and Bit Stuffing

The ICH9 USB employs NRZI data encoding (Non-Return to Zero Inverted) when

transmitting packets. Full details on this implementation are given in the Universal

Serial Bus Specification, Revision 2.0.

5.18.4 Bus Protocol

5.18.4.1 Bit Ordering

Bits are sent out onto the bus least significant bit (LSb) first, followed by next LSb,

through to the most significant bit (MSb) last.

5.18.4.2 SYNC Field

All packets begin with a synchronization (SYNC) field, which is a coded sequence that

generates a maximum edge transition density. The SYNC field appears on the bus as

IDLE followed by the binary string “KJKJKJKK,” in its NRZI encoding. It is used by the

input circuitry to align incoming data with the local clock and is defined to be 8 bits in

length. SYNC serves only as a synchronization mechanism. The last two bits in the

SYNC field are a marker that is used to identify the first bit of the PID. All subsequent

bits in the packet must be indexed from this point.

5.18.4.3 Packet Field Formats

All packets hav e distinct start and end of pack et delimiters. Full details are given in the

Universal Serial Bus Specification, Revision 2.0, in Section 8.3.1.

5.18.4.4 Address Fields

Function endpoints are addressed using the function address field and the endpoint

field. Full details on this are given in the Universal Serial Bus Specification, Revision

2.0, in Section 8.3.2.

5.18.4.5 Frame Number Field

The frame number field is an 11-bit field that is incremented by the host on a per fr ame

basis. The frame number field rolls over upon reachin g its maximum value of 7FFh, and

is sent only for SOF tokens at the start of each frame.

5.18.4.6 Data Field

The data field may range from 0 to 1023 bytes and must be an integral numbers of

bytes. Data bits within each byte are shifted out LSB first.

5.18.4.7 Cyclic Redundancy Check (CRC)

CRC is used to protect the all non-PID fields in token and data packets. In this context,

these fields are considered to be protected fields. Full details on this are given in the

Universal Serial Bus Specification, Revision 2.0, in Section 8.3.5.

5.18.5 Packet Formats

The USB protocol calls out several packet types: token, data, and handshake packets.

Full details on this are given in the Universal Serial Bus Specification, Revision 2.0, in

section 8.4.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 211

Functional Description

5.18.6 USB Interrupts

There are two general groups of USB interrupt sources, those resulting from execution

of transactions in the schedule, and those resulting from an ICH9 operation error. All

transaction-based sources can be masked by software through the ICH9’s Interrupt

Enable register. Additionally, individual transfer descriptors can be marked to generate

an interrupt on completion.

When the ICH9 driv es an inte rrupt for U SB , it internally drives the PIRQA# pin for USB

function #0 and USB function #3, PIRQD# pin for USB function #1, and the PIRQC#

pin for USB function #2, until all sources of the interrupt are cleared. In order to

accommodate some operating systems, the Interrupt Pin register must contain a

different value for each function of this new multi-function device.

5.18.6.1 Transaction-Based Interrupts

These interrupts are not signaled until after the status for the last complete transaction

in the frame has been written back to host memory. This ensures that software can

safely process through (Frame List Current Index -1) when it is servicing an interrupt.

CRC Error / Time-Out

A CRC/Time-Out error occurs when a packet tr ansmitted from the ICH9 to a USB device

or a packet tr ansmitted from a USB device to the ICH9 generates a CRC error. The ICH9

is informed of this event by a time-out from the USB device or by the ICH9’s CRC

checker generating an error on reception of the packet. Additionally, a USB bus time-

out occurs when USB devices do not respond to a transaction phase within 19-bit times

of an EOP. Either of these conditions causes the C_ERR field of the TD to decrement.

When the C_ERR fi el d dec r em ents to 0, the followi n g oc c urs :

• The Active bit in the TD is cleared

• The Stalled bit in the TD is set

• The CRC/Time-out bit in the TD is set.

• At the end of the frame, the USB Error Interrupt bit is set in the HC status register.

If the CRC/Time out interrupt is enabled in the Interrupt Enable register, a hardware

interrupt will be signaled to the system.

Interrupt on Completion

Transfer Descriptors contain a bit that can be set to cause an interrupt on their

completion. The completion of the transaction associated with that block causes the

USB Interrupt bit in the HC Status Register to be set at the end of the frame in which

the transfer completed. When a TD is encount ered with the IOC bit set to 1, the IOC bit

in the HC Status register is set to 1 at the end of the frame if the active bit in the TD is

set to 0 (even if it was set to 0 when initially read).

If the IOC Enable bit of Interrupt Enable register (bit 2 of I/O offset 04h) is set, a

hardware interrupt is signaled to the system. The USB Interrupt bit in the HC status

completion is because of errors, the USB Error bit in the HC status register is also set.

Functional Description

212 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Short Packet Detect

A transfer set is a collection of data which requires more than one USB transaction to

completely move the data across the USB . An example might be a large print file which

requires numerous TDs in multiple frames to completely transfer the data. R eception of

a data packet that is less than the endpoint’s Max Packet size during Control, Bulk or

Interrupt transfers signals the completion of the transfer set, even if there are active

TDs remaining for this transfer set. Setting the SPD bit in a TD indicates to the HC to

set the USB Interrupt bit in the HC status register at the end of the frame in which this

event occurs. This feature streamlines the processing of input on these transfer types.

If the Short Packet Interrupt Enable bit in the Interrupt Enable register is set, a

hardware interrupt is signaled to the system at the end of the frame where the event

occurred.

Serial Bus Babble

When a device transmits on the USB for a time greater than its assigned Max Length, it

is said to be babbling. Since isochrony can be destroyed by a babbling device, this error

results in the Active bit in the TD being cleared to 0 and the Stalled and Babble bits

being set to 1. The C_ERR field is not decremented for a babble. The USB Error

Interrupt bit in the HC Status register is set to 1 at the end of the frame. A hardware

interrupt is signaled to the system.

If an EOF babble was caused by the ICH9 (due to incorrect schedule for instance), the

ICH9 forces a bit stuff error followed by an EOP and the start of the next frame.

Stalled

This event indicates that a device/endpoint returned a STALL handshake during a

transaction or that the transaction ended in an error condition. The TDs Stalled bit is

set and the Active bit is cleared. Reception of a STALL does not decrement the error

counter. A hardware interrupt is signaled to the system.

Data Buffer Error

This event indicates that an overrun of incoming data or a under-run of outgoing data

has occurred for this transaction. This would gener ally be caused by the ICH9 not being

able to access required data buffers in memory within necessary latency requirements.

Either of these conditions causes the C_ERR field of the TD to be decremented.

When C_ERR decrements to 0, the Active bit in the TD is cleared, the Stalled bit is set,

the USB Error Interrupt bit in the HC Status register is set to 1 at the end of the frame

and a hardware interrupt is signaled to the system.

Bit Stuff Error

A bit stuff error results from the detection of a sequence of more that six 1s in a row

within the incoming data stream. This causes the C_ERR field of the TD to be

decremented. When the C_ERR field decrements to 0, the Active bit in the TD is cleared

to 0, the Stalled bit is set to 1, the USB Error Interrupt bit in the HC Status register is

set to 1 at the end of the frame and a hardware interrupt is signaled to the system.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 213

Functional Description

5.18.6.2 Non-Transaction Based Interrupts

If an ICH9 process error or system error occurs, the ICH9 halts and immediately issues

a hardware interrupt to the system.

Resume Received

This event indicates that the ICH9 receiv ed a RE SUME signal from a device on the USB

bus during a global suspend. If this interrupt is enabled in the Interrupt Enable register,

a hardware interrupt is signaled to the system allowing the USB to be brought out of

the suspend state and returned to normal operation.

ICH9 Process Error

The HC monitors certain critical fields during operation to ensure that it does not

process corrupted data structures. These include checking for a valid PID and verifying

that the MaxLength field is less than 1280. If it detects a condition that would indicate

that it is processing corrupted data structures, it immediately halts processing, sets the

HC Process Error bit in the HC Status register and signals a hardware interrupt to the

system.

This interrupt cannot be disabled through the Interrupt Enable register.

Host System Error

The ICH9 sets this bit to 1 when a Parity error, Master Abort, or Target Abort occurs.

When this error occurs, the ICH9 clears the Run/Stop bit in the Command register to

prevent further execution of the scheduled TDs. This interrupt cannot be disabled

through the Interrupt Enable register.

5.18.7 USB Power Management

The Host controller can be put into a suspended state and its power can be removed.

This requires that certain bits of information are retained in the suspend power plane of

the ICH9 so that a device on a port may wake the system. Such a device may be a fax-

modem, which will wake up the machine to receive a fax or take a voice message. The

settings of the following bits in I/O space will be maintained when the ICH9 enters the

S3, S4, or S5 states.

When the ICH9 detects a resume event on any of its ports, it sets the corresponding

USB_STS bit in ACPI space. If USB is enabled as a wake/break event, the system

wakes up and an SCI generated.

Table 5-44. Bits Maintained in Low Power States

Command 00h 3 Enter Global Suspend Mode (EGSM)

Status 02h 2 Resume Detect

Port Status and

Control 10h & 12h

2 Port Enabled/Disabled

6 Resume Detect

8 Low-speed Device Attached

12 Suspend

Functional Description

214 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.18.8 USB Legacy Keyboard Operation

When a USB keyboard is plugged into the system, and a standard keyboard is not, the

system may not boot, and MS-DOS legacy softw are will not run, because the keyboard

will not be identified. The ICH9 implements a series of trapping operations which will

snoop accesses that go to the keyboard controller, and put the expected data from the

USB keyboard into the keyboard controller.

Note: The scheme described below assumes that the keyboard controller (8042 or

equivalent) is on the LPC bus.

This legacy operation is performed through SMM space. Figure 5-13 shows the Enable

and Status path. The latched SMI source (60R, 60W, 64R, 64W) is available in the

Status Register. Because the enable is after the latch, it is possible to check for other

events that didn't necessarily cause an SMI. It is the software's responsibility to

logically AND the value with the appropriate enable bits.

Note also that the SMI is generated before the PCI cycle completes (e.g. , before TRDY#

goes active) to ensure that the processor doesn't complete the cycle before the SMI is

observed.

The logic also needs to block the accesses to the 8042. If there is an external 8042,

then this is simply accomplished by not activ ating the 8042 CS. This is done by logically

ANDing the four enables (60R, 60W, 64R, 64W) with the 4 types of accesses to

determine if 8042CS should go active. An additional term is required for the “pass-

through” case.

The state table for Figure 5-13 is shown in Table 5-45.

Figure 5-13. USB Legacy Keyboard Flow Diagram

KBC Accesses

PCI Config

Read , Wr ite

60 READ

Cl ear S MI_60_R

EN_SMI_ON_60R

Comb.

Decoder AND

Same for 60W, 64R, 64W

SMI

To Individual

"Caused By"

"Bits"

To PIRQD#

To " C a used By " B it

AND

EN_PIRQD#

USB_IRQ

Clear U SB _IRQ

EN_SMI_ON_IRQ

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 215

Functional Description

Table 5-45. USB Legacy Keyboard State Transitions

Current

State Action Data

Value Next

State Comment

IDLE 64h /

Write D1h GateState1 Standard D1 command. Cycle passed

through to 8042. SMI# doesn't go active.

PSTATE (offset C0, bit 6) goes to 1.

IDLE 64h /

Write Not D1h IDLE Bit 3 in Config Register determines if cycle

passed through to 8042 and if SMI#

generated.

IDLE 64h / Read N/A IDLE Bit 2 in Config Register determines if cycle

passed through to 8042 and if SMI#

generated.

IDLE 60h /

Write Don't

Care IDLE Bit 1 in Config Register determines if cycle

passed through to 8042 and if SMI#

generated.

IDLE 60h / Read N/A IDLE Bit 0 in Config Register determines if cycle

passed through to 8042 and if SMI#

generated.

GateState1 60h /

Write XXh GateState2

Cycle passed through to 8042, even if trap

enabled in Bit 1 in Config R egister. No SMI#

generated. PSTATE remains 1. If data value

is not DFh or DDh then the 8042 ma y chose

to ignore it.

GateState1 64h /

Write D1h GateState1

Cycle passed through to 8042, even if trap

enabled via Bit 3 in Config Register. No

SMI# generated. PST ATE remains 1. Stay in

GateState1 because this is part of the

double-trigger sequence.

GateState1 64h /

Write Not D1h ILDE

Bit 3 in Config space determines if cycle

passed through to 8042 and if SMI#

generated. PSTATE goes to 0. If Bit 7 in

Config Register is set, then SMI# should be

generated.

GateState1 60h / R ead N/A IDLE

This is an invalid sequence. Bit 0 in Conf ig

to 8042 and if SMI# generated. PSTATE

goes to 0. If Bit 7 in Config Register is set,

then SMI# should be generated.

GateState1 64h / R ead N/A GateState1 Just stay in same state. Generate an SMI#

if enabled in Bit 2 of Config Register. PST ATE

remains 1.

GateState2 64 / Write FFh IDLE

Standard end of sequence. Cycle passed

through to 8042. PSTATE goes to 0. Bit 7 in

Config Space determines if SMI# should be

generated.

GateState2 64h /

Write Not FFh IDLE

Improper end of sequence. Bit 3 in Config

to 8042 and if SMI# generated. PSTATE

goes to 0. If Bit 7 in Config Register is set,

then SMI# should be generated.

Functional Description

216 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.18.9 Function Level Reset Support (FLR)

The USB UHCI Controllers support the Function Level Reset (FLR) capability. The FLR

capability can be used in conjunction with Intel® Virtualization Technology. FLR allows

an Operating System in a Virtual Machine to have complete control over a device,

including its initialization, without interfering with the rest of the platform. The device

provides a software interface that enables the Operating System to reset the whole

device as if a PCI reset was asserted.

5.18.9.1 FLR Steps

5.18.9.1.1 FLR Initialization

1. A FLR is initiated by software writing a 1 to the Initiate FLR bit.

2. All subsequent requests targeting the Function will not be claimed and will be

Master Abort Immediate on the bus. This includes any configuration, I/O or

Memory cycles, however, the Function shall continue to accept completions

targeting the Function.

5.18.9.1.2 FLR Operation

The Function will Reset all configuration, I/O and memory registers of the Function

except those indicated otherwise and reset all internal states of the Function to the

default or initial condition.

5.18.9.1.3 FLR Completion

The Initiate FLR bit is reset (cleared) when the FLR reset is completed. This bit can be

used to indicate to the software that the FLR reset is completed.

Note: From the time Initiate FLR bit is written to 1, software must wait at least 100 ms before

accessing the function.

GateState2 64h / Read N/A GateState2 Just stay in same state. Generate an SMI#

if enabled in Bit 2 of Config Register. PST A TE

remains 1.

GateState2 60h /

Write XXh IDLE

Improper end of sequence. Bit 1 in Config

to 8042 and if SMI# generated. PSTATE

goes to 0. If Bit 7 in Config Register is set,

then SMI# should be generated.

GateState2 60h / Read N/A IDLE

Improper end of sequence. Bit 0 in Config

to 8042 and if SMI# generated. PSTATE

goes to 0. If Bit 7 in Config Register is set,

then SMI# should be generated.

Table 5-45. USB Legacy Keyboard State Transitions

Current

State Action Data

Value Next

State Comment

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 217

Functional Description

5.19 USB EHCI Host Controllers (D29:F7 and D26:F7)

The ICH9 contains two Enhanced Host Controller Interface (EHCI) host controllers

which support up to twelve USB 2.0 high-speed root ports. USB 2.0 allows data

transfers up to 480 Mb/s using the same pins as the twelve USB full-speed/low-speed

ports. The ICH9 contains port-routing logic that determines whether a USB port is

controlled by one of the UHCI controllers or by one of the EHCI controllers. USB 2.0

based Debug Port is also implemented in the ICH9.

A summary of the key architectural differences between the USB UHCI host controllers

and the EHCI host controller are shown in Table 5-46.

5.19.1 EHC Initializati on

The following descriptions step through the expected ICH9 Enhanced Host Controller

(EHC) initialization sequence in chronological order, begi nning with a complete power

cycle in which the suspend well and core well have been off.

5.19.1.1 BIOS Initialization

BIOS performs a number of platform customization steps after the core well has

powered up. Contact your Intel Field Representative for additional ICH9 BIOS

information.

5.19.1.2 Driver Initialization

See Chapter 4 of the Enhanced Host Controller Interface Specification for Universal

Serial Bus, Revision 1.0.

Table 5-46. UHCI vs. EHCI

Parameter USB UHCI USB EHCI

Accessible by I/O space Memory Space

Memory Data Struc ture Single linked list Separated into Periodic and Asynchronous

lists

Differential Signal ing Voltage 3.3 V 400 mV

Ports per Controller 2 6 or 8 (controller #1) and 6 or 4

(Controller #2)

Functional Description

218 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.19.1.3 EHC Resets

In addition to the standard ICH9 hardware resets, portions of the EHC are reset by the

HCRESET bit and the tr ansition from th e D3 HOT device power management state to the

D0 state. The effects of each of these resets are:

If the detailed register descriptions give exceptions to these rules, those exceptions

override these rules. This summary is provid ed to help explain the reasons for the reset

policies.

5.19.2 Data Structures in Main Memory

See Section 3 and Appendix B of the Enhanced Host Controller Interface Specification

for Universal Serial Bus, Revision 1.0 for details.

5.19.3 USB 2.0 Enhanced Host Controller DMA

The ICH9 USB 2.0 EHC implements three sources of USB packets. They are, in order of

priority on USB during each microframe:

1. The USB 2.0 Debug Port (see Section USB 2.0 Based Debug Port),

2. T he Periodi c DM A engine, and

3. T he As y n ch ronous DM A engine.

The ICH9 always performs any currently -pen ding debug port transaction at the

beginning of a microframe, followed by any pending periodic traffic for the current

microframe. If there is time left in the microframe, then the EHC performs any pending

asynchronous traffic until the end of the microframe (EOF1). Note that the debug port

traffic is only presented on one port (P ort #0), while the other ports are idle during this

time.

5.19.4 Data Encoding and Bit Stuffing

See Chapter 8 of the Universal Serial Bus Specification, Revision 2.0.

Reset Does Reset Does not Reset Comments

HCRESET bit set.

Memory space

registers except

Structural

Parameters (which is

written by BIOS).

Configuration

registers.

The HCRESET must only affect

registers that the EHCI driver

controls. PCI Configuration

space and BIOS-programmed

parameters can not be reset.

Software writes

the Device Power

State from D3HOT

(11b) to D0

(00b).

Core well registers

(except BIOS-

programmed

registers).

Suspend well

registers; BIOS-

programmed core

well registers.

The D3-to-D0 transition must

not cause wake information

(suspend well) to be lost. It also

must not clear BIOS-

programmed registers because

BIOS may not be invoked

following the D3-to-D0

transition.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 219

Functional Description

5.19.5 Packet Formats

See Chapter 8 of the Universal Serial Bus Specification, Revision 2.0.

The ICH9 EHCI allows entrance to USB test modes, as defined in the USB 2.0

specification, including Test J, Test Packet, etc. However note that the ICH9 Test P acket

test mode interpacket gap timing may not meet the USB 2.0 specification.

5.19.6 USB 2.0 Interrupts and Error Conditions

Section 4 of the Enhanced Host Controller Interface Specification for Universal Serial

Bus, Revision 1.0 goes into detail on the EHC interrupts and the error conditions that

cause them. All error conditions that the EHC detects can be reported through the EHCI

Interrupt status bits. Only ICH9-specific interrupt and error-reporting behavior is

documented in this section. The EHCI Interrupts Section must be read first, followed by

this section of the datasheet to fully comprehend the EHC interrupt and error-reporting

functionality.

• Based on the EHC’s Buffer sizes and buffer management policies, the Data Buffer

Error can never occur on the ICH9.

• Master Abort and Target Abort responses from hub interface on EHC-initiated read

packets will be treated as Fatal Host Errors. The EHC halts when these conditions

are encountered.

• The ICH9 may assert the interrupts which are based on the interrupt threshold as

soon as the status for the last complete transaction in the interrupt interval has

been posted in the internal write buffers. The requirement in the Enhanced Host

Controller Interface Specification for Universal Serial Bus, Revision 1.0 (that the

status is written to memory) is met internally, even though the write may not be

seen on DMI before the interrupt is asserted.

• Since the ICH9 supports the 1024-element Frame List size, the Frame List Rollover

interrupt occurs every 1024 milliseconds.

• The ICH9 delivers interrupts using PIRQH#.

• The ICH9 does not modify the CERR count on an Interrupt IN when the “Do

Complete-Split” execution criteria are not met.

• For complete-split transactions in the P eriodic list, the “Missed Microfr ame” bit does

not get set on a control-structure-fetch that fails the late-start test. If subsequent

accesses to that control structure do not fail the late-start test, then the “Missed

Microframe” bit will get set and written back.

5.19.6.1 Aborts on USB 2.0-Initiated Memory Reads

If a read initiated by the EHC is aborted, the EHC treats it as a fatal host error. The

following actions are taken when this occurs:

• The Host System Error status bit is set

• The DMA engines are halted after completing up to one more transaction on the

USB interface

• If enabled (by the Host System Error Enable), then an interrupt is generated

• If the status is Master Abort, then the Received Master Abort bit in configuration

space is set

• If the status is Target Abort, then the Received Target Abort bit in configuration

space is set

• If enabled (by the SERR Enable bit in the function’ s configuration space), then the

Signaled System Error bit in configuration bit is set.

Functional Description

220 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.19.7 USB 2.0 Power Management

5.19.7.1 Pause Feature

This feature allows platforms (especially mobile systems) to dynamically enter low-

power states during brief periods when the system is idle (i.e., between keystrokes).

This is useful for enabling power management features like Intel SpeedStep®

technology in the ICH9. The policies for entering these states typically are based on the

recent history of system bus activity to incrementally enter d eeper power manag ement

states. Normally, when the EHC is enabled, it regularly accesses main memory while

traversing the DMA schedules looking for work to do; this activity is viewed by the

power management software as a non-idle system, thus preventing the power

managed states to be entered. Suspending all of the enabled ports can prevent the

memory accesses from occurring, but there is an inherent latency overhead with

entering and exiting the suspended state on the USB ports that makes this

unacceptable for the purpose of dynamic power management. As a result, the EHCI

software drivers are allowed to pause the EHC’s DMA engines when it knows that the

traffic patterns of the attached devices can afford the delay. The pause only prevents

the EHC from generating memory accesses; the SOF packets continue to be generated

on the USB ports (unlike the suspended state).

5.19.7.2 Suspend Feature

The Enhanced Host Controller Interface (EHCI) For Universal Serial Bus Specification,

Section 4.3 describes the details of Port Suspend and Resume.

5.19.7.3 ACPI Device States

The USB 2.0 function only supports the D0 and D3 PCI Power Management states.

Notes regarding the ICH9 implementation of the Device States:

1. The EHC hardware does not inherently consume any more power when it is in the

D0 state than it does in the D3 state. However, software is required to suspend or

disable all ports prior to entering the D3 state such that the maximum power

consumption is reduced.

2. In the D0 state, all implemented EHC features are enabled.

3. In the D3 state, accesses to the EHC memory-mapped I/O r ange will master abort.

Note that, since the Debug Port uses the same memory range, the Debug Port is

only operational when the EHC is in the D0 state.

4. In the D3 state, the EHC interrupt must never assert for any reason. The internal

PME# signal is used to signal wake events, etc.

5. When the Device Power State field is written to D0 from D3, an internal reset is

generated. See section EHC Resets for general rules on the effects of this reset.

6. A ttempts to write an y o ther value into the Device Power State field other than 00b

(D0 state) and 11b (D3 state) will complete normally without changing the current

value in this field.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 221

Functional Description

5.19.7.4 ACPI System States

The EHC behavior as it relates to other power management states in the system is

summarized in the following list:

— The S ystem is always in the S0 state when the EHC is in the D0 state. However,

when the EHC is in the D3 state, the system may be in any power management

state (including S0).

— When in D0, the Pause feature (See Section 5.19.7.1) enables dynamic

processor low-power states to be entered.

— The PLL in the EHC is disabled when entering the S3/S4/S5 states (core power

turns off).

— All core well logic is reset in the S3/S4/S5 states.

5.19.7.5 Mobile Considerations

The ICH9 USB 2.0 implementation does not behave differently in the mobile

configurations versus the desktop configurations. However, some features may be

especially useful for the mobile configurations.

• If a system (e.g., mobile) does not implement all twelve USB 2.0 ports, the ICH9

provides mechanisms for changing the structur al parameters of the EHC and hiding

unused UHCI controllers. See the Intel® ICH9 BIOS Specification for information on

how BIOS should configure the ICH9.

• Mobile systems may want to minimize the conditions that will wake the system.

The ICH9 implements the “Wake Enable” bits in the Port Status and Control

registers, as specified in the EHCI spec, for this purpose.

• Mobile systems may want to cut suspend well power to some or all USB ports when

in a low-power state. The ICH9 implements the optional Port Wake Capability

R egister in the EHC Configuration Space for this platform-specific information to be

communicated to software.

5.19.8 Interaction with UHCI Host Controllers

The Enhanced Host controllers share its ports with UHCI Host controllers in the ICH9.

The UHC at D29:F0 shares ports 0 and 1; the UHC at D29:F1 shares ports 2 and 3; the

UHC at D29:F2 shares ports 4 and 5 with the EHC at D29:F7, while the UHC at D26:F0

shares ports 6 and 7, the UHC at D26:F1 shares ports 8 and 9, and the UHC at D26:F2

shares ports 10 and 11 with EHC at D26:F7. There is very little inter action between the

Enhanced and the UHCI controllers other than the muxing control which is provided as

part of the EHC. Figure 5-14 shows the USB Port Connections at a conceptual level.

Note: D26:F2 can be configured as D29:F3 during BIOS post.

Functional Description

222 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.19.8.1 Port-Routing Logic

Integrated into the EHC functionality is port-routing logic, which performs the muxing

between the UHCI and EHCI host controllers. The ICH9 conceptually implements this

logic as described in Section 4.2 of the Enhanced Host Controller Interface Specification

for Universal Serial Bus, Revision 1.0. If a device is connected that is not capable of

USB 2.0’ s high-speed signaling protocol or if th e EHC I softw are d riv ers are not prese nt

as indicated by the Configured Flag, then the UHCI controller owns the port. Owning

the port means that the differential output is driven by the owner and the input stream

is only visible to the owner. The host controller that is not the owner of the port

internally sees a disconnected port.

Note that the port-routing logic is the only block of logic within the ICH9 that observes

the physical (real) connect/disconnect information. The port status logic inside each of

the host controllers observes the electrical connect/disconnect information that is

generated by the port-routing logic.

Only the differential signal pairs are mult iplexed/de-multiplex ed between the UHCI and

EHCI host controllers. The other USB functional signals are handled as follows:

• The Overcurrent inputs (OC[11:0]#) are directly routed to both controllers. An

overcurrent event is recorded in both controllers’ status registers.

Figure 5-14. Intel® ICH9-USB Port Connections Default Six and Six Configuration

Figure 5-15. Intel® ICH9-USB Port Connections Eight and Four Configuration

UHCI UHCI

EHCI #1

Port 5Port 4Port 3Port 2Port 1Port 0

UHCI UHCI UHCI UHCI

EHCI #2

Port 11Port 10Port 9Port 8Po rt 7Port 6

UHCI UHCI

EHCI #1

Port 5Port 4Port 3Port 2Port 1Port 0

UHCI UHCI

EHCI #1

Port 5Port 4Port 3Port 2Port 1Port 0

UHCI UHCI UHCI UHCI

EHCI #2

Port 11Port 10Port 9Port 8Po rt 7Port 6

UHCI UHCI

EHCI #2

Port 11Port 10Port 9Port 8Po rt 7Port 6

UHCI UHCI

Port 5Port 4Port 3Port 2Port 1Port 0

UHCI UHCI UHCI UHCI

EHCI #2

Port 9Port 8Port 7Port 6Port 11Port 10

UHCI UHCI

EHCI #1

UHCI UHCI

Port 5Port 4Port 3Port 2Port 1Port 0

UHCI UHCI UHCI UHCI

EHCI #2

Port 9Port 8Port 7Port 6Port 11Port 10

UHCI UHCI

EHCI #1

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 223

Functional Description

The Port-Routing logic is implemented in the Suspend power well so that re-

enumeration and re-mapping of the USB ports is not required following entering and

exiting a system sleep state in which the core power is turned off.

The ICH9 also allows the USB Debug Port tr affi c to be routed in and out of Port #0 and

Port#6. When in this mode, the Enhanced Host controller is the owner of Port #0 and

Port#6.

5.19.8.2 Device Connects

The Enhanced Host Controller Interface Specification for Universal Serial Bus, Revision

1.0 describes the details of handling Device Connects in Section 4.2. There are four

general scenarios that are summarized below.

1. Configure Flag = 0 and a full-speed/low-speed-only Device is connected

— In this case, the UHC is the owner of the port both before and after the connect

occurs. The EHC (except for the port-routing logic) never sees the connect

occur. The UHCI driver handles the connection and initialization process.

2. Configure Flag = 0 and a high-speed-capable Device is connected

— In this case, the UHC is the owner of the port both before and after the connect

occurs. The EHC (except for the port-routing logic) never sees the connect

occur. The UHCI driver handles the connection and initialization process. Since

the UHC does no t perform the high-speed chirp handsh ake, the device operates

in compatible mode.

3. Configure Flag = 1 and a full-speed/low-speed-only Device is connected

— In this case, the EHC is the owner of the port before the connect occurs. The

EHCI driver handles the connection and performs the port reset. After th e reset

process completes, the EHC hardware has cleared (not set) the Port Enable bit

in the EHC’s PORTSC register. The EHCI driver then writes a 1 to the Port Owner

bit in the same register, causing the UHC to see a connect event and the EHC to

see an “electrical” disconnect event. The UHCI driver and hardware handle the

connection and initialization process from that point on. The EHCI driver and

hardware handle the perceived disconnect.

4. Configure Flag = 1 and a high-speed-capable Device is connected

— In this case, the EHC is the owner of the port before, and remains the owner

after, the connect occurs. The EHCI driver handles the connection and performs

the port reset. After the reset process completes, the EHC hardw are has set the

P ort Enable bit in the EHC’s POR TSC register. The port is functional at this point.

The UHC continues to see an unconnected port.

Functional Description

224 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.19.8.3 Device Disconnects

The Enhanced Host Controller Interface Specification for Universal Serial Bus, Revision

1.0 describes the details of handling Device Connects in Section 4.2. There are three

general scenarios that are summarized below.

1. Configure Flag = 0 and the device is disconnected

— In this case, the UHC is the owner of the port both before and after the

disconnect occurs. The EHC (except for the port-routing logic) never sees a

device attached. The UHCI driver handles disconnection process.

2. Configure Flag = 1 and a full-speed/low-speed-capable Device is disconnected

— In this case, the UHC is the owner of the port before the disconnect occurs. The

disconnect is reported by the UHC and serviced by the associated UHCI driver.

The port-routing logic in the EHC cluster forces the Port Owner bit to 0,

indicating that the EHC owns the unconnected port.

3. Configure Flag = 1 and a high-speed-capable Device is disconnected

— In this case, the EHC is the owner of the port before, and remains the owner

after, the disconnect occurs. The EHCI hardware and driver handle the

disconnection process. The UHC never sees a device attached.

5.19.8.4 Effect of Resets on Port-Routing Logic

As mentioned above, the Port Routing logic is implemented in the suspend power well

so that remuneration and re-mapping of the USB ports is not required following

entering and exiting a system sleep state in which the core power is turned off.

5.19.9 USB 2.0 Legacy Keyboard Operation

The ICH9 must support the possibility of a keyboard downstream from either a full-

speed/low-speed or a high-speed port. The description of the legacy keyboard support

is unchanged from USB 1.1 (See Section 5.18.8).

The EHC provides the basic ability to generate SMIs on an interrupt event, along with

more sophisticated control of the generation of SMIs.

Reset Event Effect on Configure Flag Effect on Port Owner Bits

Suspend Well Reset cleared (0) set (1)

Core Well Reset no effect no effect

D3-to-D0 Reset no effect no effect

HCRESET cleared (0) set (1)

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 225

Functional Description

5.19.10 USB 2.0 Based Debug Port

The ICH9 supports the elimination of the legacy COM ports by providing the ability for

new debugger software to interact with devices on a USB 2.0 port.

High-level restrictions and features are:

• Operational before USB 2.0 drivers are loaded.

• Functions even when the port is disabled.

• Works even though non-configured port is default-routed to the UHCI. Note that

the Debug Port can not be used to debug an issue that requires a full-speed/low-

speed device on Port #0 using the UHCI drivers.

• Allows normal system USB 2.0 traffic in a system that may only have one USB port.

• Debug Port device (DPD) must be high-speed capable and connect directly to Port

#0 and Port#6 on ICH9 systems (e.g., the DPD cannot be connected to

Port #0/Port#6 through a hub).

• Debug Port FIFO always makes forward progress (a bad status on USB is simply

presented back to software).

• The Debug Port FIFO is only given one USB access per microframe.

The Debug port facilitates operating system and device driver debug. It allows the

software to communicate with an external console using a USB 2.0 connection.

Because the interface to this link does not go through the normal USB 2.0 stack, it

allows communication with the external console during cases where the operating

system is not loaded, the USB 2.0 software is broken, or where the USB 2.0 software is

being debugged. Specific features of this implementation of a debug port are:

• Only works with an external USB 2.0 debug device (console)

• Implemented for a specific port on the host controller

• Operational anytime the port is not suspended AND the host controller is in D0

power state.

• Capability is interrupted when port is driving USB RESET

5.19.10.1 Theory of Operation

There are two operational modes for the USB debug port:

1. Mode 1 is when the USB port is in a disabled state from the viewpoint of a standard

host controller driver. In Mode 1, the Debug P ort controller is required to generate a

“keepalive” packets less than 2 ms apart to keep the attached debug device from

suspending. The keepalive packet should be a standalone 32-bit SYNC field.

2. Mode 2 is when the host controller is running (i.e., host controller’s Run/Stop# bit

is 1). In Mode 2, the normal transmission of SOF packets will keep the debug

device from suspending.

Behavioral Rules

1. In both modes 1 and 2, the Debug Port controller must check for software

requested debug transactions at least every 125 microseconds.

2. If the debug port is enabled by the debug driver, and the standard host controller

driver resets the USB port, USB debug transactions are held off for the duration of

the reset and until after the first SOF is sent.

3. If the standard host controller driver suspends the USB port, then USB debug

transactions are held off for the duration of the suspend/resume sequence and until

after the first SOF is sent.

4. The ENABLED_CNT bit in the debug register space is independent of the similar

port control bit in the associated Port Status and Control register.

Functional Description

226 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 5-47 shows the debu g port behavior related to the state of bits in the debug

registers as well as bits in the associated Port Status and Control register.

5.19.10.1.1 OUT Transactions

An Out transaction sends data to the debug device. It can occur only when the

following are true:

• The debug port is enabled

• The debug software sets the GO_CNT bit

• The WRITE_READ#_CNT bit is set

The sequence of the transaction is:

1. Sof tware sets the appropri ate values in th e foll owi ng bits:

— USB_ADDRESS_CNF

—USB_ENDPOINT_CNF

— DATA_BUFFER[63:0]

— TOKEN_PID_CNT[7:0]

—SEND_PID_CNT[15:8]

—DATA_LEN_CNT

— WRITE_READ#_CNT: (note: this will always be 1 for OUT transactions)

— GO_CNT: (note: this will always be 1 to initiate the transaction)

Table 5-47. Debug Port Behavior

OWNER_CN

TENABLED_C

TPort

Enable Run /

Stop Suspen

d Debug Port Behavior

0XXXX

Debug port is not being used.

Normal operation.

10XXX

Debug port is not being used.

Normal operation.

1100X

Debug port in Mode 1. SYNC

keepalives sent plus debug traffic

1101X

Debug port in Mode 2. SOF (and

only SOF) is sent as keepalive.

Debug traffic is also sent. Note

that no other normal traffic is

sent out this port, because the

port is not enabled.

11100

Invalid. Host controller driver

should never put controller into

this state (enabled, not running

and not suspended).

11101

Port is suspended. No debug

traffic sent.

11110

Debug port in Mode 2. Debug

traffic is interspersed with

normal traffic.

11111

Port is suspended. No debug

traffic sent.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 227

Functional Description

2. The debug port controller sends a token packet consisting of:

—SYNC

— TOKEN_PID_CNT field

— USB_ADDRESS_CNT field

—USB_ENDPOINT_CNT field

— 5-bit CRC field

3. After sending the token packet, the debug port controller sends a data packet

consisting of:

—SYNC

— SEND_PID_CNT field

— The number of data bytes indicated in DATA_LEN_CNT from the DATA_BUFFER

— 16-bit CRC

NOTE: A DATA_LEN_CNT value of 0 is valid in which case no data bytes would be

included in the packet.

4. After sending the data packet, the controller waits for a handshake response from

the debug device.

• If a handshake is received, the debug port controller:

— a. Places the received PID in the RECEIVED_PID_STS field

— b. Resets the ERROR_GOOD#_STS bit

— c. Sets the DONE_STS bit

• If no handshake PID is received, the debug port controller:

— a. Sets the EXCEPTION_STS field to 001b

— b. Sets the ERROR_GOOD#_STS bit

— c. Sets the DONE_STS bit

5.19.10.1.2 IN Transactions

An IN transaction receives data from the debug device. It can occur only when the

following are true:

• The debug port is enabled

• The debug software sets the GO_CNT bit

• The WRITE_READ#_CNT bit is reset

The sequence of the transaction is:

1. Software sets the appropriate values in the following bits:

—USB_ADDRESS_CNF

—USB_ENDPOINT_CNF

— TOKEN_PID_CNT[7:0]

—DATA_LEN_CNT

— WRITE_READ#_CNT: (note: this will always be 0 for IN transactions)

— GO_CNT: (note: this will always be 1 to initiate the transaction)

Functional Description

228 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

2. The debug port controller sends a token packet consisting of:

—SYNC

— TOKEN_P I D _CNT field

— USB_ADDRESS_CNT field

— USB_ENDPOINT_CNT field

— 5-bit CRC field.

3. After sending the tok en packet, the debug port controller waits for a response from

the debug device.

If a response is received:

— The received PID is placed into the RECEIVED_PID_STS field

— Any subsequent bytes are placed into the DATA_BUFFER

— The DATA_LEN_CNT field is updated to show the number of bytes that were

received after the PID.

4. If a valid packet was received from the device that was one byte in length

(indicating it was a handshake packet), then the debug port controller:

— Resets the ERROR_GOOD#_STS bit

— Sets the DONE_STS bit

5. If a valid packet was received from the device that was more than one byte in

length (indicating it was a data packet), then the debug port controller:

— Transmits an ACK handshake packet

— Resets the ERROR_GOOD#_STS bit

— Sets the DONE_STS bit

6. If no valid packet is received, then the debug port controller:

— Sets the EXCEPTION_STS field to 001b

— Sets the ERROR_GOOD#_STS bit

— Sets the DONE_STS bit.

5.19.10.1.3 Debug Software

Enabling the Debug Port

There are two mutually exclusive conditions that debug software must address as part

of its startup processing:

• The EHCI has been initialized by system software

• The EHCI has not been initialized by system software

Debug software can determine the current ‘initialized’ state of the EHCI by examining

the Configure Flag in the EHCI USB 2.0 Command Register. If this flag is set, then

system software has initialized the EHCI. Otherwise the EHCI should not be considered

initialized. Debug software will initialize the debug port registers depending on the

state of the EHCI. However, before this can be accomplished, debug software must

determine which root USB port is designated as the debug port.

Determining the Debug Port

Debug software can easily determine which USB root port has been designated as the

debug port by examining bits 20:23 of the EHCI Host Controller Structural Parameters

0000=port 0).

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 229

Functional Description

Debug Software Startup with Non-Initialized EHCI

Debug software can attempt to use the debug port if after setting the OWNER_CNT bit,

the Current Connect Status bit in the appropriate (See Determining the Debug Port)

PORTSC register is set. If the Current Connect Status bit is not set, then debug

software may choose to terminate or it may choose to wait until a device is connected.

If a device is connected to the port, then debug software must reset/enable the port.

Debug software does this by setting and then clearing the Port Reset bit the PORTSC

clearing the Port Reset bit. Due to possible delays, this bit may not change to 0

immediately; reset is complete when this bit reads as 0. Software must not continue

until this bit reads 0.

If a high-speed device is attached, the EHCI will automatically set the Port Enabled/

Disabled bit in the PORTSC register and the debug software can proceed. Debug

software should set the ENABLED_CNT bit in the Debug Port Control/Status register,

and then reset (clear) the Port Enabled/Disabled bit in the POR TSC register (so that the

system host controller driver does not see an enabled port when it is first loaded).

Debug Software Startup with Initialized EHCI

Debug software can attempt to use the debug port if the Current Connect Status bit in

the appropriate (See Determining the Debug Port) PORTSC register is set. If the

Current Connect Status bit is not set, then debug software may choose to terminate or

it may choose to wait until a device is connected.

If a device is connected, then debug software must set the OWNER_CNT bit and then

the ENABLED_CNT bit in the Debug Port Control/Status register.

Determining Debug Peripheral Presence

After enabling the debug port functionality, debug software can determine if a debug

peripheral is attached by attempting to send data to the debug peripheral. If all

attempts result in an error (Exception bits in the Debug Port Control/Status register

indicates a Transaction Error), then the attached device is not a debug peripheral. If the

debug port peripheral is not present, then debug software may choose to terminate or

it may choose to wait until a debug peripheral is connected.

5.19.11 USB Pre-Fetch Based Pause

The Pre-Fetch Based Pause is a power management feature in USB (EHCI) host

controllers to ensure maximum C3/C4 processor power state time with C2 popup. This

feature applies to the period schedule, and works by allowing the DMA engine to

identify periods of idleness and preventing the DMA engine from accessing memory

when the periodic schedule is idle. Typically in the presence of periodic devices with

multiple millisecond poll periods, the periodic schedule will be idle for several frames

between polls.

The USB Pre-Fetch Based Pause feature is disabled by setting bit 4 of EHCI

Configuration Register Section 17.1.30.

Functional Description

230 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.19.12 Function Level Reset Support (FLR)

The USB EHCI Controllers support the Function Level Reset (FLR) capability. The FLR

capability can be used in conjunction with Intel® Virtualization Technology. FLR allows

an Operating System in a Virtual Machine to have complete control over a device,

including its initialization, without interfering with the rest of the platform. The device

provides a software interface that enables the Operating System to reset the whole

device as if a PCI reset was asserted.

5.19.12.1 FLR Steps

5.19.12.1.1 FLR Initialization

1. A FLR is initiated by software writing a ‘1’ to the Initiate FLR bit.

2. All subsequent requests targeting the Function will not be claimed and will be

Master Abort Immediate on the bus. This includes any configuration, I/O or

Memory cycles, however, the Function shall continue to accept completions

targeting the Function.

5.19.12.1.2 FLR Operation

The Function will Reset all configuration, I/O and memory registers of the Function

except those indicated otherwise and reset all internal states of the Function to the

default or initial condition.

5.19.12.1.3 FLR Completion

The Initiate FLR bit is reset (cleared) when the FLR reset is completed. This bit can be

used to indicate to the software that the FLR reset is completed.

Note: From the time Initiate FLR bit is written to 1, software must wait at least 100 ms before

accessing the function.

5.20 SMBus Controller (D31:F3)

The ICH9 provides an System Management Bus (SMBus) 2.0 host controller as well as

an SMBus Slave Interface. The host controller provides a mechanism for the pro cessor

to initiate communications with SMBus peripherals (sla ves). The ICH9 is also capable of

operating in a mode in which it can communicate with I2C compatible devices.

The ICH9 can perform SMBus messages with either packet error checking (PEC)

enabled or disabled. The actual PEC calculation and checking is performed in hardware

by the ICH9.

The Slave Interface allows an external master to read from or write to the ICH9. W rite

cycles can be used to cause certain events or pass messages, and the read cycles can

be used to determine the state of various status bits. The ICH9’s internal host

controller cannot access the ICH9’s internal Slave Interface.

The ICH9 SMBus logic exists in Device 31:Function 3 configuration space, and consists

of a transmit data path, and host controller. The transmit data path provides the data

flow logic needed to implement the seven different SMBus command protocols and is

controlled by the host controller. The ICH9 SMBus controller logic is clocked by RTC

clock.

The SMBus Address Resolution Protocol (ARP) is supported by using the existing host

controller commands through software, except for the new Host Notify command

(which is actually a received message).

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 231

Functional Description

The programming model of the host controller is combined into two portions: a PCI

configuration portion, and a system I/O mapped portion. All static configuration, such

as the I/O base address, is done via the PCI configuration space. Real-time

programming of the Host interface is done in system I/O space.

The ICH9 SMBus host controller checks for parity errors as a target. If an error is

detected, the detected parity error bit in the PCI Status Register (Device 31:Function

3:Offset 06h:bit 15) is set. If bit 6 and bit 8 of the PCI Command Register (Device

31:Function 3:Offset 04h) are set, an SERR# is generated and the signaled SERR# bit

in the PCI Status Register (bit 14) is set.

Note: The ICH9 SMBus Controller may stop responding if an SMBus device suddenly stops

transmitting in the middle of a packet. This could result in unexpected system behavior,

including a system hang.

5.20.1 Host Controller

The SMBus host controller is used to send commands to other SMBus slave devices.

Software sets up the host controller with an address, command, and, for writes, data

and optional PEC; and then tells the controller to start. When the controller has finished

transmitting data on writes, or receiving data on reads, it generates an SMI# or

interrupt, if enabled.

The host controller supports 8 command protocols of the SMBus interface (see System

Management Bus (SMBus) Specification, Version 2.0): Quick Command, Send Byte,

Receiv e Byte, W rite Byte/Word, Read Byte/Word, Process Call, Block Read/Write, Block

Write–Block Read Process Call, and Host Notify.

The SMBus host controller requires that the various data and command fields be setup

for the type of command to be sent. When softw are sets the ST AR T bit, the SMBus Host

controller performs the requested transaction, and interrupts the processor (or

generates an SMI#) when the transaction is completed. Once a START command has

been issued, the values of the “active registers” (Host Control, Host Command,

Transmit Slave Address, Data 0, Data 1) should not be changed or read until the

interrupt status bit (INTR) has been set (indicating the completion of the command).

Any register values needed for computation purposes should be saved prior to issuing

of a new command, as the SMBus host controller updates all registers while completing

the new command.

The ICH9 supports the System Management Bus (SMBus) Specification, Version 2.0.

Slave functionality, including the Host Notify protocol, is available on the SMBus pins.

The SMLink and SMBus signals can be tied together externally depending on the TCO

mode used. Refer to Section 5.14.2 for more details.

Using the SMB host controller to send commands to the ICH9’s SMB slave port is not

supported.

5.20.1.1 Command Protocols

In all of the following commands, the Host Status Register (offset 00h) is used to

determine the progress of the command. While the command is in operation, the

HOST_BUSY bit is set. If the command completes successfully, the INTR bit will be set

in the Host Status Register. If the device does not respond with an acknowledge, and

the transaction times out, the DEV_ERR bit is set. If software sets the KILL bit in the

Host Control Register while the command is running, the transaction will stop and the

FAILED bit will be set.

Functional Description

232 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Quick Command

When programmed for a Quick Command, the Transmit Slave Address R egister is sent.

The PEC byte is never appended to the Quick Protocol. Software should force the

PEC_EN bit to 0 when performing the Quick Command. Software must force the

I2C_EN bit to 0 when running this command. See section 5.5.1 of the System

Management Bus (SMBus) Specification, Version 2.0 for the format of the protocol.

Send Byte / Receive Byte

For the Send Byte command, the Transmit Slave Address and Device Command

Registers are sent

For the Receive Byte command, the Transmit Slave Address Register is sent. The data

received is stored in the DATA0 register. Software must force the I2C_EN bit to 0 when

running this command.

The Receive Byte is similar to a Send Byte, the only difference is the direction of data

transfer. See sections 5.5.2 and 5.5.3 of the System Management Bus (SMBus)

Specification, Version 2.0 for the format of the protocol.

Write Byte/Word

The first byte of a Write Byte/Word access is the command code. The next 1 or 2 bytes

are the data to be written. When programmed for a Write Byte/Word command, the

Transmit Slave Address, Device Command, and Data0 Registers are sent. In addition,

the Data1 Register is sent on a W rite Word command. Software must force the I2C_EN

bit to 0 when running this command. See section 5.5.4 of the System Management Bus

(SMBus) Specification, Version 2.0 for the format of the protocol.

Read Byte/Word

Reading data is slightly more complicated than writing data. First the ICH9 must write a

command to the slave device. Then it must follow that command with a repeated start

condition to denote a read from that device's address. The slave then returns 1 or 2

bytes of data. Software must force the I2C_EN bit to 0 when running this command.

When programmed for the read byte/word command, the Transmit Slave Address and

Device Command Re gisters are sent. Data is received into the DAT A0 on the read byte,

and the DAT0 and DATA1 registers on the read word. See section 5.5. 5 of the System

Management Bus (SMBus) Specification, Version 2.0 for the format of the protocol.

Process Call

The process call is so named because a command sends data and waits for the slave to

return a value dependent on that data. The protocol is simply a W rite Word followed by

a Read Word, but without a second command or stop condition.

When programmed for the Process Call command, the ICH9 tr ansm its the Transmit

Slave Address, Host Command, DATA0 and DATA1 registers. Data received from the

device is stored in the DATA0 and DATA1 registers. The Process Call command with

I2C_EN set and the PEC_EN bit set produces undefined results. Software must force

either I2C_EN or PEC_EN to 0 when running this command. See section 5.5.6 of the

System Management Bus (SMBus) Specification, Version 2.0 for the format of the

protocol.

Note: For process call command, the value written into bit 0 of the Transmit Slave Address

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 233

Functional Description

Note: If the I2C_EN bit is set, the protocol sequence changes slightly: the Command Code

(bits 18:11 in the bit sequence) are not sent - as a result, the slave will not

acknowledge (bit 19 in the sequence).

Block Read/Wri te

The ICH9 contains a 32-byte buffer for read and write data which can be enabled by

setting bit 1 of the Auxiliary Control register at offset 0Dh in I/O space, as opposed to a

single byte of buffering. This 32-byte buffer is filled with write data before

transmission, and filled with read data on reception. In the ICH9, the interrupt is

generated only after a transmission or reception of 32 bytes, or when the entire byte

count has been transmitted/received.

The byte count field is transmitted but ignored by the ICH9 as software will end the

transfer after all bytes it cares about have been sent or received.

For a Block Write, software must either force the I2C_EN bit or both the PEC_EN and

AAC bits to 0 when running this command.

The block write begins with a slave address and a write condition. After the command

code the ICH9 issues a byte count describing how many more bytes will follow in the

message. If a slave had 20 bytes to send, the first byte would be the number 20 (14h),

followed by 20 bytes of data. The byte count may not be 0. A Block Read or Write is

allowed to transfer a maximum of 32 data bytes.

When programmed for a block write command, the Transmit Slave Address, Device

Command, and Data0 (count) registers are sent. Data is then sent from the Block Data

Byte register; the total data sent being the v alue stored in the Data0 R egister. On block

read commands, the first byte received is stored in the Data0 register, and the

remaining bytes are stored in the Block Data Byte register. See section 5.5.7 of the

System Management Bus (SMBus) Specification, Versi on 2.0 for the format of the

protocol.

Note: For Block Write, if the I2C_EN bit is set, the format of the command changes slightly.

The ICH9 will still send the number of bytes (on writes) or receive the number of bytes

(on reads) indicated in the DAT A0 register. However, it will not send the contents of the

DATA0 register as part of the message. Also, the Block Write protocol sequence

changes slightly: the Byte Count (bits 27:20 in the bit sequence) are not sent - as a

result, the slave will not acknowledge (bit 28 in the sequence).

I2C Read

This command allows the ICH9 to perform block reads to certain I2C devices, such as

serial E2PROMs. The SMBus Block Read supports the 7-bit addressing mode only.

However, this does not allow access to devices using the I2C “Combined Format” that

has data bytes after the address. Typically these data bytes correspond to an offset

(address) within the serial memory chips.

Note: This command is supported independent of the setting of the I2C_EN bit. The I2C Read

command with the PEC_EN bit set produces undefined results. Software must force

both the PEC_EN and AAC bit to 0 when running this command.

For I2C Read command, the value written into bit 0 of the Transmit Slave Address

The format that is used for the command is shown in Table 5-48.

Functional Description

234 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

The ICH9 will continue reading data from the peripheral until the NAK is received.

Block Write–Block Read Process Call

The block write-block read process call is a two-part message. The call begins with a

slave address and a write condition. After the command code the host issues a write

byte count (M) that describes how many more bytes will be written in the first part of

the message. If a master has 6 bytes to send, the byte count field will have the value 6

(0000 0110b), followed by the 6 bytes of data. The write byte count (M) cannot be 0.

The second part of the message is a block of read data beginning with a repeated start

condition followed by the slave address and a Read bit. The next byte is the read byte

count (N), which may differ from the write byte count (M). The read byte count (N)

cannot be 0.

The combined data payload must not exceed 32 bytes. The byte length restrictions of

this process call are summarized as follows:

•M ≥ 1 byte

•N ≥ 1 byte

•M + N ≤ 32 bytes

The read byte count does not include the PEC byte. The PEC is computed on the total

message beginning with the first slave address and using the normal PEC

computational rules. It is highly recommended that a PEC byte be used with the Block

Write-Block Read Process Call. Software must do a read to the command register

(offset 2h) to reset the 32 byte buffer pointer prior to reading the block data register.

Table 5-48. I2C Block Read

Bit Description

1Start

8:2 Slave Address — 7 bits

9Write

10 Acknowledge from slave

18:11 Send DATA1 register

19 Acknowledge from slave

20 Repeated Start

27:21 Slave Address — 7 bits

28 Read

29 Acknowledge from slave

37:30 Data byte 1 from slave — 8 bits

38 Acknowledge

46:39 Data byte 2 from slave — 8 bits

47 Acknowledge

– Data bytes from slave / Acknowledge

– Data byte N from slave — 8 bits

– NOT Acknowledge

–Stop

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 235

Functional Description

Note that there is no STOP condition before the repeated START condition, and that a

NACK signifies the end of the read transfer.

Note: E32B bit in the Auxiliary Control register must be set when using this protocol.

See section 5.5.8 of the System Management Bus (SMBus) Specification, Version 2.0

for the format of the protocol.

5.20.2 Bus Arbitration

Several masters may attempt to get on the bus at the same time by driving the

SMBDATA line low to signal a start condition. The ICH9 continuously monitors the

SMBDAT A line. When the ICH9 is attempting to drive the bus to a 1 by letting go of the

SMBDA TA line, and it samples SMBDA TA low, then some other master is driving the bus

and the ICH9 will stop transferring data.

If the ICH9 sees that it has lost arbitration, the condition is called a collision. The ICH9

will set the BUS_ERR bit in the Host Status Register, and if enabled, generate an

interrupt or SMI#. The processor is responsible for restarting the transaction.

When the ICH9 is a SMBus master, it drives the clock. When the ICH9 is sending

address or command as an SMBus master, or data bytes as a master on writes, it drives

data relative to the clock it is also driving. It will not start toggling the clock until the

start or stop condition meets proper setup and hold time. The ICH9 will also ensure

minimum time between SMBus transactions as a master.

Note: The ICH9 supports the same arbitration protocol for both the SMBus and the System

Management (SMLINK) interfaces.

5.20.3 Bus Timing

5.20.3.1 Clock Stretching

Some devices may not be able to handle their clock toggling at the rate that the ICH9

as an SMBus master would like. They have the capability of stretching the low time of

the clock. When the ICH9 attempts to releas e the clock (allowing the clock to go high),

the clock will remain low for an extended period of time.

The ICH9 monitors the SMBus clock line after it releases the bus to determine whether

to enable the counter for the high time of the clock. While the bus is still low, the high

time counter must not be enabled. Similarly, the low period of the clock can be

stretched by an SMBus master if it is not ready to send or receive data.

5.20.3.2 Bus Time Out (Intel® ICH9 as SMBus Master)

If there is an error in the transaction, such that an SMBus device does not signal an

acknowledge, or holds the clock lower than the allowed time-out time, the transaction

will time out. The ICH9 will discard the cycle and set the DEV_ERR bit. The time out

minimum is 25 ms (800 RTC clocks). The time-out counter inside the ICH9 will start

after the last bit of data is transferred by the ICH9 and it is waiting for a response.

The 25 ms timeout counter will not count under the following conditions:

1. BYTE_DONE_STATUS bit (SMBus I/O Offset 00h, bit 7) is set

2. The SECOND_TO_STS bit (TCO I/O Offset 06h, bit 1) is not set (this indicates that

the system has not locked up).

Functional Description

236 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.20.4 Interrupts / SMI#

The ICH9 SMBus controller uses PIRQB# as its interrupt pin. However, the system can

alternatively be set up to generate SMI# instead of an interrupt, by setting the

SMBUS_SMI_EN bit (Device 31:Function 0:Offset 40h:bit 1).

Table 5-50 and Table 5-51 specify how the various enable bits in the SMBus function

control the generation of the interrupt, Host and Sla v e SMI, and Wake internal signals.

The rows in the tables are additive, which means that if more than one row is true for a

particular scenario then the Results for all of the activated rows will occur.

Table 5-49. Enable for SMBALERT#

Event

INTREN

(Host Control

I/O Register,

Offset 02h,

Bit 0)

SMB_SMI_EN

(Host

Configuration

D31:F3:Offset

40h, Bit 1)

SMBALERT_DIS

(Slave Command

I/O Register,

Offset 11h, Bit 2)

Result

SMBALERT#

asserted low

(always

reported in

Host Status

Re gister, Bit

XX XWake generated

X1 0

Slave SMI#

generated

(SMBUS_SMI_STS)

10 0

Interrupt

generated

Table 5-50. Enables for SMBus Slave Write and SMBus Host Events

Event

INTREN (Host

Control I/O

02h, Bit 0)

SMB_SMI_EN (Host

Configuration

D31:F3:Offset 40h,

Bit1)

Event

Slave Write to

Wake/SMI#

Command XX

Wake generated when

asleep.

Slave SMI# generated when

awak e (SM BU S_S MI_STS).

Slave Write to

SMLINK_SLAVE_S

MI Command XX

Slave SMI# generated when

in the S0 state

(SMBUS_SMI_STS)

Any combination of

Host Status

asserted

0XNone

1 0 Interrupt generated

11Host SMI# generated

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 237

Functional Description

5.20.5 SMBALERT#

SMBALER T# is multiplexed with GPIO[11]. When enable and the signal is asserted, The

ICH9 can generate an interrupt, an SMI#, or a wake event from S1–S5.

5.20.6 SMBus CRC Generation and Checking

If the AAC bit is set in the Auxiliary Control register, the ICH9 automatically calculates

and drives CRC at the end of the transmitted pack et for write cycles, and will check the

CRC for read cycles. It will not transmit the contents of the PEC register for CRC. The

PEC bit must not be set in the Host Control register if this bit is set, or unspecified

behavior will result.

If the read cycle results in a CRC error, the DEV_ERR bit and the CRCE bit in the

Auxiliary Status register at offset 0Ch will be set.

5.20.7 SMBus Slave Interface

The ICH9’s SMBus Sla ve interface is accessed via the SMBus. The SMBus slave logic will

not generate or handle receiving the PEC byte and will only act as a Legacy Alerting

Protocol device. The slave interface allows the ICH9 to decode cycles, and allows an

external microcontroller to perform specific actions. Key features and capabilities

include:

• Supports decode of three types of messages: Byte Write, Byte Read, and Host

Notify.

• Receive Slave Address register: This is the address that the ICH9 decodes. A

default value is provided so that the slave interface can be used without the

processor having to program this register.

• Receive Slave Data register in the SMBus I/O space that includes the data written

by the external microcontroller.

• Registers that the external microcontroller can read to get the state of the ICH9.

• Status bits to indicate that the SMBus slave logic caused an interrupt or SMI# due

to the reception of a message that matched the slave address.

— Bit 0 of the Slave Status Register for the Host Notify command

— Bit 16 of the SMI Status Register (Section 13.8.3.15) for all others

Table 5-51. Enables for the Host Notify Command

HOST_NOTIFY_INTRE

N (Slave Cont rol I/O

bit 0)

SMB_SMI_EN

(Host Config

D31:F3:Off40h, Bit

HOST_NOTIFY_WKEN

(Slave Control I/O

bit 1)

Result

0X0None

XX1Wake generated

1 0 X Interrupt generated

11X

Slave SMI#

generated

(SMBUS_SMI_STS)

Functional Description

238 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Note: The external microcontroller should not attempt to access the Intel ICH9’s SMBu s slave

logic until either:

— 800 milliseconds after both: RTCRST# is high and RSMRST# is high, OR

— The PLTRST# de-asserts

If a master leaves the clock and data bits of the SMBus interface at 1 for 50 µs or more

in the middle of a cycle, the ICH9 slave logic's behavior is undefined. This is interpreted

as an unexpected idle and should be avoided when performing management activities

to the slave logic.

Note: When an external microcontroller accesses the SMBus Slave Interface over the SMBus

a translation in the address is needed to accommodate the least significant bit used for

read/write control. For example, if the ICH9 slave address (RCV_SLVA) is left at 44h

(default), the external micro controller would use an address of 88h/89h (write/read).

5.20.7.1 Format of Slave Write Cycle

The external mas te r pe rforms Byte Writ e commands to the ICH9 SMBus Slave I/F. The

“Command” field (bits 11:18) indicate which register is being accessed. The Data field

(bits 20:27) indicate the value that should be written to that register.

Table 5-52 has the values associated with the registers.

NOTE: The external microcontroller is responsible to make sure that it does not update the

contents of the data b yte registers until th ey hav e been read by the syste m processor. The

ICH9 overwrites the old value with any new value received. A race condition is possible

where the new value is being written to the register just at th e t ime it is being read. ICH9

will not attem p t to cover this race condition (i.e., unpredictable results in this case).

Table 5-52. Slave Write Registers

0Command Register. See Table 5-53 below for valid values written to this

1–3 Reserved

4 Data Message Byte 0

5 Data Message Byte 1

6–7 Reserved

8Reserved

9–FFh Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 239

Functional Description

Table 5-53. Command Types

Command

Type Description

0 Reserved

WAKE/SMI#. This command wakes the system if it is not already awake. If

system is already awake, an SMI# is generated.

NOTE: The S MB_WAK_STS bit will be set by this command, even if the system is

already awake. The SMI handler should then clear this bit.

2Unconditional Powerdo wn. This command sets the PWRBTNOR_STS bit, and

has the same effect as the Powerbutton Override occurring.

3HARD RESET WITHOUT CYCLING: This command causes a hard reset of the

system (does not include cycling of the power supply). This is equivalent to a write

to the CF9h register with bits 2:1 set to 1, but bit 3 set to 0.

4HARD RESET SYSTEM. This command causes a hard reset of the system

(including cycling of the power supply). This is equivalent to a write to the CF9h

Disable the TCO Messages. This command will disable the Intel® ICH9 from

sending Heartbeat and Event messages (as described in Section 5.14). Once this

command has been executed, Heartbeat and Event message reporting can only be

re-enabled by assertion and deassertion of the RSMRST# signal.

6WD RELOAD: Reload watchdog timer.

7 Reserved

SMLINK_SLV_SMI. When ICH9 detects this command type while in the S0 state,

it sets the SMLINK_SLV_SMI_STS bit (see Section 13.9.5). This command should

only be used if the system is in an S0 state. If the message is received during S1–

S5 states, the ICH9 ac knowledges it, but the SMLINK_SLV_SMI_STS bit does not

get set.

NOTE: It is possible that the system transitions out of the S0 state at the same

time that the SM LINK_SLV_SMI command is received. In this case, the

SMLINK_SLV_SMI_STS bit may get set but not serviced before the system

goes to sleep. Once the system returns to S0, the SMI associated with this

bit would then be gener ated. Software must be able to handle this scenario.

9-FFh Reserved.

Functional Description

240 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.20.7.2 Format of Read Command

The external master performs Byte Read commands to the ICH9 SMBus Slave

interface. The “Command” field (bits 18:11) indicate which register is being accessed.

The Data field (bits 30:37) contain the value that should be read from that register.

Table 5-54. Slave Read Cycle Format

Bit Description Driven by Comment

1 Start External Microcontroller

2-8 Slave Address - 7 bits External Microcontroller Must match value in Receive Slave

Address register

9 Write External Microcontroller Always 0

10 ACK Intel ICH9

11-18 Command code – 8 bits External Microcontroller Indicates which register is being

accessed. See Table 5-55 below

for list of implemented registers.

19 ACK Intel ICH9

20 Repeated Start External Microcontroller

21-27 Slave Address - 7 bits External Microcontroller Must match value in Receive Slave

Address register

28 Read External Microcontroller Always 1

29 ACK Intel ICH9

30-37 Data Byte Intel ICH9 Value depends on register being

accessed. Table 5-55 below for list

of implemented registers.

38 NOT ACK External Microcontroller

39 Stop External Microcontroller

Table 5-55. Data Values for Slave Read Registers (Sheet 1 of 3)

07:0

Reserved for capabilities indication. Should always return 00h. Future

chips may return another value to indicate different capabilities.

12:0

System Power State

000 = S0 001 = S1 010 = Reserved 011 = S3

100 = S4 101 = S5 110 = Reserved 111 = Reserved

7:3 Reserved

23:0 Reserved

7:4 Reserved

35:0

Watchdog Timer current value Note that Watchdog Timer has 10 bits,

but this field is only 6 bits. If the current value is greater than 3Fh, ICH9

will always report 3Fh in this field.

7:6 Reserved

1 = The Intruder Detect (I NTRD_DET) bit is set. This in dicates that the

system cover has probably been opened.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 241

Functional Description

1 = BTI Temperature Event occurred. This bit will be set if the Intel

ICH9’s THRM# input signal is at a valid low voltage state. This bit will be

clear if the THRM# input signal is at a valid high voltage state.

NOTE: This bit interprets the behavior if the THRM# pin as active low.

This bit is set independent of the TRM#_POL bit setting.

2 DOA CPU Status. This bit will be 1 to indicate that the process or is dead

31 = SECOND_TO_STS bit set. This bit wil l be set after the second t im e-

out (SECOND_TO_STS bit) of the Watchdog Timer occurs.

6:4 Reserved. Will always be 0, but software should ignore.

Reflects the value of the GPIO[11]/SMBALERT# pin (and is dependent

upon the value of the GPI_INV[11] bit. If the GPI_INV[11] bit is 1, then

the value in this bit equals the level of the GPI[11]/SMBALERT# pin

(high = 1, low = 0).

If the GPI_INV[11] bit is 0, then the value of this bit will equal the inverse

of the level of the GPIO[11]/SMBALERT# pin (high = 0, low = 1).

5 0

FWH bad bit. This bit will be 1 to indicate that the FWH read returned

FFh, which indicates that it is pro b ably blank.

1Battery Low Status. ‘1’ if the BATLOW# pin is a ‘0’.(Mobile Only)

2CPU Power Failure Status: ‘1’ if the CPUPWR_FLR bit in the

GEN_PMCON_2 register is set.

INIT# due to receiving Shutdown message: This event is visible from

the reception of the shutdown m essage until a platform reset is done if

the Shutdown Policy Select bit (SPS) is configured to drive INIT#. When

the SPS bit is configured to generate PLTRST# based on shutdown, this

Events on signal will not create a event message

4Reserved

5POWER_OK_BAD: Indicates the failure core power well ramp during

boot/resum e. Thi s bit will be active if the SLP_S3# pin is de-asserted and

PWROK pin is not asserted.

6Thermal Trip: This bit will shadow the state of processor Thermal Trip

status bit (CTS) (16.2.1.2, GEN_PMCON_2, bit 3). Events on signal will

not create a event mes sage

7Reserved: Default value is “X”

Note: Software should not expect a consistent value when this bit is read

through SMBUS/SMLINK

67:0

Contents of the Message 1 register. Refer to Section 13.9.8 for the

description of this register.

77:0

Contents of the Message 2 register. Refer to Section 13.9.8 for the

description of this register.

87:0

Contents of the TCO_WDCNT register. Refer to Section 13.9.9 for the

description of this register.

97:0Seconds of the RTC

A 7:0 Minutes of the RTC

B7:0Hours of the RTC

C 7:0 “Day of Week” of the RTC

Table 5-55. Data Values for Slave Read Register s (Sheet 2 of 3)

Functional Description

242 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.20.7.2.1 Behavioral Notes

According to SMBus protocol, Read and Write messages always begin with a Start bit –

Address– Write bit sequence. When the ICH9 detects that the address matches the

value in the Receive Slave Address register, it will assume that the protocol is always

followed and ignore the Write bit (bit 9) and signal an Acknowledge during bit 10. In

other words, if a Start – Address–R ead occurs (which is inv alid for SMBus Read or W rite

protocol), and the address matches the ICH9’s Slave Address, the ICH9 will still grab

the cycle.

Also according to SMBus protocol, a Read cycle contains a Repeated Start–Address–

Read sequence beginning at bit 20. Once again, if the Address matches the ICH9’s

Receive Slave Address, it will assume that the protocol is followed, ignore bit 28, and

proceed with the Slave Read cycle.

Note: An external microcontroller must not attempt to access the ICH9’s SMBus Slave logic

until at least 1 second after both RTCRST# and RSMRST# are deasserted (high).

5.20.7.3 Slave Read of RTC Time Bytes

The ICH9 SMBus slave interface allows external SMBus master to read the internal

RTC’s time byte registers.

The R TC time bytes are internally latched by the ICH9’s hardware whenever R TC time is

not changing and SMBus is idle. This ensures that the time byte delivered to the slave

read is always v alid and it does not change when the read is still in progress on the bus.

The RTC time will change whenever hardware update is in progress, or there is a

software write to the RTC time bytes.

The ICH9 SMBus slave interface only supports Byte Read operation. The external

SMBus master will read the RTC time bytes one after another. It is software’s

responsibility to check and manage the possible time rollover when subsequent time

bytes are read.

For example, assuming the RTC time is 11 hours: 59 minutes: 59 seconds. When the

external SMBus master reads the hour as 11, then proceeds to read the minute, it is

possible that the rollover happens between the reads and the minute is read as 0. This

results in 11 hours: 0 minute instead of the correct time of 12 hours: 0 minutes. Unless

it is certain that rollover will not occur, software is required to detect the possible time

rollover by reading multiple times such that the read time bytes can be adjusted

accordingly if needed.

D 7:0 “Day of Month” of the RTC

E 7:0 Month of the RTC

F7:0Year of the RTC

10h–FFh 7:0 Reserved

Table 5-55. Data Values for Slave Read Registers (Sheet 3 of 3)

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 243

Functional Description

5.20.7.4 Format of Host Notify Command

The ICH9 tracks and responds to the standard Host Notify command as specified in the

System Management Bus (SMBus) Specification, Version 2.0. The host address for this

command is fixed to 0001000b. If the ICH9 already has data for a previously-received

host notify command which has not been serviced yet by the host software (as

indicated by the HOST_NOTIFY_STS bit), then it will NACK following the host address

byte of the protocol. This allows the host to communicate non-acceptance to the

master and retain the host notify address and data values for the previous cycle until

host software completely services the interrupt.

Note: Host software must always clear the HOST_NOTIFY_STS bit after completing any

necessary reads of the address and data registers.

Table 5-56 shows the Host Notify format.

Table 5-56. Host Notify Format

Bit Description Driven By Comment

1 Start External Master

8:2 SMB Host Address — 7 bits External Master Always 0001_000

9 Write External Master Always 0

10 ACK (or NACK) Intel® ICH9 ICH9 NACKs if HOST_NOTIFY_STS is 1

17:11 Device Address – 7 bits External Master Indicates the address of the master;

loaded into the Notify Dev ice Address

18 Unused — Always 0 External Master 7-bit-only a ddress; this bit is inserted

to complete the byte

19 ACK ICH9

27:20 Data Byte Low — 8 bits External Master Loaded into the Notify Data Low Byte

28 ACK ICH9

36:29 Data Byte High — 8 bits External Master Loaded into the Notify Data High Byte

37 ACK ICH9

38 Stop External Master

Functional Description

244 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.21 Intel® High Definition Audio Overview

The ICH9’s High Definition Audio (HDA) controller communicates with the external

codec(s) over the Intel High Definition Audio serial link. The controller consists of a set

of DMA engines that are used to move samples of digitally encoded data between

system memory and an external codec(s). The ICH9 implements four output DMA

engines and 4 input DMA engines. The output DMA engines move digital data from

system memory to a D-A converter in a codec. ICH9 implements a single Serial Data

Output signal (HDA_SDOUT) that is connected to all external codecs. The input DMA

engines move digital data from the A-D conv erter in the codec to system memory. The

ICH9 implements four Serial Digital Input signals (HDA_SDI[3:0]) supporting up to

four codecs.

Audio software renders outbound and processes inbound data to/from buffers in

system memory. The location of individual buffers is described by a Buffer Descriptor

List (BDL) that is fetched and processed by the controller. The data in the buffers is

arranged in a predefined format. The output DMA engines fetch the digital data from

memory and reformat it based on the programmed sample rate, bit/sample and

number of channels. The data from the output DMA engines is then combined and

serially sent to the external codecs over the Intel High Definition Audio link. The input

DMA engines receive data from the codecs ov er the Intel High Definition Audio link and

format the data based on the programmable attributes for that stream. The data is

then written to memory in the predefined format for software to process. Each DMA

engine moves one stream of data. A single codec can accept or generate multiple

streams of data, one for each A-D or D-A converter in the codec. Multiple codecs can

accept the same output stream processed by a single DMA engine.

Codec commands and responses are also transported to and from the codecs via DMA

engines.

5.21.1 Intel® High Definition Audio Docking (Mobile Only)

5.21.1.1 Dock Sequence

Note that this sequence is followed when the system is running and a docking event

occurs.

1. Since the ICH9 supports docking, the Docking Supported (DCKSTS. DS) bit defaults

to a 1. POST BIOS and ACPI BIOS software uses this bit to determine if the HD

Audio controller supports docking. BIOS may write a 0 to this RWO bit during POST

to effectively turn off the docking feature.

2. After reset in the undocked quiescent state, the Dock Attach (DCKCTL.DA) bit and

the Dock Mate (DCKSTS.DM) bit are both de- asserted. The HDA_DOCK_EN# signal

is de-asserted and HDA_DOCK_RST# is asse rted. Bit Clock, SYNC and SDO signals

may or may no be running at the point in time that the docking event occurs.

3. The physical docking event is signaled to ACPI BIOS software via ACPI control

methods. This is normally done through a GPIO signal on the ICH9 and is outside

the scope of this section of the spec.

4. ACPI BIOS software first checks that the docking is supported via DCKSTS.DS=1

and that the DCKSTS.DM=0 and then initiates the docking sequence by writing a 1

to the DCKCTL.DA bit.

5. The HD Audio controller then asserts the HDA_DOCK_EN# signal so that the Bit

Clock signal begins toggling to the dock codec. HDA_DOCK_EN# shall be asserted

synchronously to Bit Clock and timed such that Bit Clock is low, SYNC is low, and

SDO is low. Pull-down resistors on these signals in the docking station discharge

the signals low so that when the state of the signal on both sides of the switch is

the same when the switch is turned on. This reduces the potential for charge

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 245

Functional Description

coupling glitches on these signals. Note that in the ICH9 the first 8 bits of the

Command field are “reserved” and always driven to 0's. This creates a predictable

point in time to always assert HDA_DOCK_EN#. Note that the HD Audio link reset

exit specification that requires that SYNC and SDO be driven low during Bit Clock

startup is not ensured. Note also that the SDO and Bit Clock signals may not be low

while HDA_DOCK_RST# is asserted which also violates the spec.

6. After the controller asserts HDA_DOCK_EN# it waits for a minimum of 2400 Bit

Clocks (100us) and then de-asserts HDA_DOCK_RST#. This is done in such a way

to meet the HD Audio link reset exit specification. HDA_DOCK_RST# de-assertion

should be synchronous to Bit Clock and timed such that there are least 4 full Bit

ClockS from the de-assertion of HDA_DOCK_RST# to the first frame SYNC

assertion.

7. The Connect/Turnaround/Address Frame hardware initialization sequence will now

occur on the dock codecs' SDI signals. A dock codec is detected when SDI is high

on the last Bit Clock cycle of the Frame Sync of a Connect Frame. The appropriate

bit(s) in the State Change Status (STATESTS) register will be set. The Turnaround

and Address Frame initialization sequence then occurs on the dock codecs' SDI(s).

8. After this hardware initialization sequence is complete (approximately 32 frames),

the controller hardware sets the DCKST S.DM bit to 1 indicating that the dock is now

mated. ACPI BIOS polls the DCKSTS.DM bit and when it detects it is set to 1,

conveys this to the OS through a plug-N-play IRP. This eventually invokes the HD

Audio Bus Driver, which then begins it's codec discovery, enumeration, and

configuration process.

9. Alternatively to step #8, the HD Audio Bus Driver may choose to enable an

interrupt by setting the WAKEEN bits for SDINs that didn't originally have codecs

attached to them. When a corresponding STA TESTS bit gets set an interrupt will be

generated. In this case the HD Audio Bus Driver is called directly by this interrupt

instead of being notified by the plug-N-play IRP.

10.HD Audio Bus Driver software “discovers” the dock codecs by comparing the bits

now set in the STATESTS register with the bits that were set prior to the docking

event.

5.21.1.2 Exiting D3/CRST# when Docked

1. In D3/CRST#, CRST# is asserted by the HD Audio Bus Driver. CRST# asserted

resets the dock state machines, but does not reset the DCKCTL.DA bit. Because the

dock state machines are reset, the dock is electrically isolated (HDA_DOCK_EN#

de-asserted) and DOCK_RST# is asserted.

2. The Bus Driver clears the STATESTS bits, then de-asserts CRST#, waits

approximately 7ms, then checks the STATESTS bits to see which codecs are

present.

3. When CRST# is de-asserted, the dock state machine detects that DCKCTL.DA is

still set and the controller hardware sequences through steps to electrically connect

the dock by asserting HDA_DOCK_EN# and then eventually de-asserts

DOCK_RST#. This completes within the 7ms mentioned in step 2).

4. The Bus Driver enumerates the codecs present as indicated via the STATESTS bits.

5. Note that this process did not require BI OS or ACPI BIOS to set the DCKCTL.DA bit.

Functional Description

246 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.21.1.3 Cold Boot/Resume from S3 When Docked

1. When booting and resuming from S3, PLTRST# switches from asserted to de-

asserted. This clears the DCKCTL.DA bit and the dock state machines. Because the

dock state machines are reset, the dock is electrically isolated (HDA_DOCK_EN#

de-asserted) and DOCK_RST# is asserted.

2. POST BIOS detects th at the dock is attached and sets the DCKCTL.DA bit to 1. Note

that at this point CRST# is still asserted so the dock state machine will remain in

it's reset state.

3. The Bus Driver clears the STATESTS bits, then de-asserts CRST#, waits

approximately 7ms, then checks the STATESTS bits to see which codecs are

present.

4. When CRST# is de-asserted, the dock state machine detects that DCKCTL.DA is

still set and the controller hardware sequences through steps to electrically connect

the dock by asserting HDA_DOCK_EN# and then eventually de-asserts

DOCK_RST#. This completes within the 7ms mentioned in step 3).

5. The Bus Dri ver enumerates the codecs present as i nd icate d via the STA T ES T S bits .

5.21.1.4 Undock Sequence

There are two possible undocking scenarios. The first is the one that is initiated by the

user that invokes software and gracefully shuts down the dock codecs before they are

undocked. The second is referred to as the “surprise undock” where the user undocks

while the dock codec is running. Both of these situations appear the same to the

controller as it is not cognizant of the “surprise removal”. But both sequences will be

discussed here.

5.21.1.4.1 Normal Undock

1. In the docked quiescent state, the Dock Attach (DCKCTL.DA) bit and the Dock Mate

(DCKSTS.DM) bit are both asserted. The HDA_DOCK_EN# signal is asserted and

HDA_DOCK_RST# is de-asserted.

2. The user initiates an undock event through the GUI interface or by pushing a

button. This mechanism is outside the scope of this section of the document. Either

way ACPI BIOS software will be invoked to manage the undock process.

3. ACPI BIOS will call the HD A udio Bus Driver software in order to halt the stream to

the dock codec(s) prior to electrical undocking. If the HD Audio Bus Driver is not

capable of halting the stream to the docked codec, ACPI BIOS will initiate the

hardware undocking sequence as described in the n ext step while the dock stream

is still running. From this standpoint, the result is similar to the “surprise undock”

scenario where an audio glitch may occur to the docked codec(s) during the undock

process.

4. The ACPI BIOS initiates the hardware undocking sequence by writing a 0 to the

DCKCTL.DA bit.

5. The HD Audio controller asserts HDA_DOCK_RST#. HDA_DOCK_RST# assertion

shall be synchronous to Bit Clock. There are no other timing requirements for

HDA_DOCK_RST# assertion. Note that the HD Audio link reset specification

requirement that the last Frame sync be skipped will not be met.

6. A minimum of 4 Bit Clocks after HDA_DOCK_RST# the controller will de-assert

HDA_DOCK_EN# to isolate the dock codec signals from the ICH9 HD Audio link

signals. HDA_DOCK_EN# is de-asserted synchron ously to Bit Clock and timed such

that Bit Clock, SYNC, and SDO are low.

7. After this hardw are undocking sequence is complete the controller hardware clears

the DCKSTS.DM bit to 0 indicating that the dock is now un-mated. ACPI BIOS

software polls DCKSTS.DM and when it sees DM set, conveys to the end user that

physical undocking can proceed. The controller is now ready for a subsequent

docking event.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 247

Functional Description

5.21.1.4.2 Surprise Undock

1. In the surprise undock case the user undocks before software has had the

opportunity to gracefully halt the stream to the dock codec and initiate the

hardware undock sequence.

2. A signal on the docking connector is connected to the switch that isolates th e dock

codec signals from the ICH9 HD Audio link signals (DOCK_DET# in the conceptual

diagram). When the undock event begins to occur the switch will be put into isolate

mode.

3. The undock event is communicated to the ACPI BIOS via ACPI control methods that

are outside the scope of this section of the document.

4. ACPI BIOS software writes a 0 to the DCKCTL.DA bit. ACPI BIOS then calls the HD

Audio Bus Driver via plug-N-play IRP. The Bus Driver then posthumously cleans up

the dock codec stream.

5. The HD Audio controller hardware is oblivious to the fact that a surprise undock

occurred. The flow from this point on is identical to the normal undocking sequence

described in section 0 starting at step 3). It finishes with the hardware clearing the

DCKSTS.DM bit set to 0 indicating that the dock is now un-mated. The controller is

now ready for a subsequent docking event.

5.21.1.5 Interaction Between Dock/Undock and Power Management States

When exiting from S3, PLTRST# will be asserted. The POST BIOS is responsible for

initiating the docking sequence if the dock is already attached when PLTRST# is de-

asserted. POST BIOS writes a 1 to the DCKCTL.DA bit prior to the HD Audio driver de-

asserting CRTS# and detecting and enumerating the codecs attached to the

HDA_DOCK_RST# signal. The HD Audio controller does not directly monitor a hardware

signal indicating that a dock is attached. Therefore a method outside the scope of this

document must be used to cause the POST BIOS to initiate the docking sequence.

When exiting from D3, CRST# will be asserted. When CRST# bit is “0” (asserted), the

DCKCTL.DA bit is not cleared. Th e dock state machine will be reset such that

HDA_DOCK_EN# will be de-asserted, HDA_DOCK_RST# will be asserted and the

DCKSTS.DM bit will be cleared to reflect this state. When the CRST# bit is de-asserted,

the dock state machine will detect that DCKCTL.DA is set to “1” and will begin

sequencing through the dock process. Note that this does not require any software

intervention.

5.21.1.6 Relationship between HDA_DOCK_RST# and HDA_RST#

HDA_RST# will be asserted when a PLTRST# occurs or when the CRST# bit is 0. As

long as HDA_RST# is asserted, the DOCK_RST# signal will also be asserted.

When PLTRST# is asserted, the DCKCTL.DA and DCKSTS.DM bits will be get cleared to

their default state (0's), and the dock state machine will be reset such that

HDA_DOCK_EN# will be de-asserted, and HDA_DOCK_RST# will be asserted. After any

PLTRST#, POST BIOS software is responsible for detecting that a dock is attached and

then writing a “1” to the DCKCTL.DA bit prior to the HD Audio Bus Driver de-asserting

CRST#.

When CRST# bit is “0” (asserted), the DCKCTL.DA bit is not cleared. The dock state

machine will be reset such that HDA_DOCK_EN# will be de-asserted,

HDA_DOCK_RST# will be asserted and the DCKSTS.DM bit will be cleared to reflect this

state. When the CRST# bit is de-asserted, the dock state machine will detect that

DCKCTL.DA is set to “1” and will begin sequencing through the dock process. Note that

this does not require any software intervention.

Functional Description

248 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.21.2 Function Level Reset Support (FLR)

The Intel® High Definition Audio Controller supports the Function Level Reset (FLR)

capability. The FLR capability can be used in conjunction with Intel Virtualization

Technology. FLR allows an Operating System in a Virtual Machine to have complete

control over a device, including its initialization, without interfering with the rest of the

platform. The device provides a software interface that enables the Operating System

to reset the whole device as if a PCI reset was asserted.

5.21.2.1 FLR Steps

5.21.2.1.1 FLR Initialization

1. A FLR is initiated by software writing a ‘1’ to the Initiate FLR bit.

2. All subsequent requests targeting the Function will not be claimed and will be

Master Abort Immediate on the bus. This includes any configuration, I/O or

Memory cycles, however, the Function shall continue to accept completions

targeting the Function.

5.21.2.1.2 FLR Operation

The Function will Reset all configuration, I/O and memory registers of the Function

except those indicated otherwise and reset all internal states of the Function to the

default or initial condition.

5.21.2.1.3 FLR Completion

The Initiate FLR bit is reset (cleared) when the FLR reset is completed. This bit can be

used to indicate to the software that the FLR reset is completed.

Note: From the time Initiate FLR bit is written to 1, software must wait at least 100 ms before

accessing the function.

5.22 Intel® Active Management Technology (Intel®

AMT) (Digital Office Only)

Intel Active Management Technology is a set of advanced manageability features

developed as a direct result of IT customer feedback gained through Intel market

research. Reducing the Total Cost of Ownership (TCO) throu gh improved asset tracking,

remote manageability, and fewer desk-side visits were identified as key IT priorities.

Intel AMT extends the capabilities of existing management solutions by making the

asset information, remote diagnostics, recovery and contain capabilities always

available, or Out of Band (OOB), even when the system is in a low-power “off” state or

the OS is hung.

Another feature of Intel AMT is System Defense. System Defense is used to stop the

propagation of worms and viruses. Programmable packet filters in the integrated LAN

Controller are used to accomplish this. These filters inspect all incoming and all

outgoing packets and decide whether to block or pass the packets as configured. There

is no indication to the host that a packet has been blocked or accepted.

The logic can be used to accept or block reception to host or transmission to network

paths. Additionally, counter logic can be used to count the number or filter matches for

a given filter. This feature allows for statistical sampling of connections as well as rate

limiting of connections.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 249

Functional Description

5.22.1 Intel® AMT Features

• E-Asset Tag

• OOB HW and SW Inventory Logs

•OOB Alerts

•IDE Redirect

• Serial over LAN for Remote Control

• Remote Diagnostics Execution

• OS Lock-Up Alert

•OS Repair

• Remote BIOS Recovery and Update

5.22.2 Intel® AMT Requirements

Intel AMT is a platform-level solution that utilizes multiple system components

including:

•Intel AMT-Ready ICH9 component

• Intel Gigabit Ethernet PHY (Intel® 82566 Gigabit Platform LAN Connect device)

with Intel Active Management Technology for remote access

• SPI flash memory with 4KB or 8KB sector erase that meets requirements set in

Section 5.23.4 (32 Mb minimum for Intel AMT) to store asset information,

management software code, and logs

• BIOS to provide asset detection and POST diagnostics (BIOS and Intel AMT can

optionally share same flash memory device)

• Familiar ISV software packages to take advantage of Intel AMT’s platform

management capabilities

5.23 Serial Peripheral Interface (SPI)

The Serial Peripheral Interface (SPI) is a 4-pin interface that provides a potentially

lower-cost alternative for system flash versus the Firmware Hub on the LPC bus.

The 4-pin SPI interface consists of clock (CLK), master data out (Master Out Slave In

(MOSI)), master data in (Master In Slave Out (MISO)) and an active low chip select

(SPI_CS[1:0]#).

The ICH9 supports up to two SPI flash devices using two separate Chip Select pins.

Each SPI flash device can be up to 16 MBytes. The ICH9 SPI interface supports 20 MHz

and 33 MHz SPI devices.

Communication on the SPI bus is done with a Master – Slave protocol. The Slave is

connected to the ICH9 and is impl emented as a tri-state bus.

Note: When SPI is selected by the Boot BIOS Destination Strap and a SPI device is detected

by the ICH9, LPC based BIOS flash is disabled.

5.23.1 SPI Supported Feature Overview

SPI Flash on the ICH9 has two operational modes, descriptor and non-descriptor.

Functional Description

250 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.23.1.1 Non-Descriptor Mode

Non-descriptor mode is similar to the flash functionality of ICH7. In this mode, SPI

Flash can only be used for BIOS. Direct read and writes are not supported. BIOS has

read/write access only through register accesses. Through those register accesses

BIOS can read and write to the entire flash without security checking. There is also no

support for the integrated Gigabit Ethernet, Management Engine, as well multiple SPI

Flash components.

5.23.1.2 Descriptor Mode

Descriptor Mode enables many new features of the chipset:

• Integrated Gigabit Ethernet and Host processor for Gigabit Ethernet Software

•Intel

® Active Management Technology (Digital Office Only)

•Intel

® Quiet System Technology

• Supports two SPI Flash components using two separate chip select pins

• Hardware enforced security restricting master accesses to different regions

• Chipset Soft Strap region provides the ability to use Flash NVM as an alternative to

hardware pull-up/pull-down resistors for both ICH and MCH

• Supports the SPI Fast Read instruction and frequencies of 33 MHz

• Uses standardized Flash Instruction Set

5.23.1.2.1 SPI Flash Regions

In Descriptor Mode the Flash is divided into five separate regions:

Only three masters can access the four regions: Host processor running BIOS code,

Integrated Gi gabit Ethernet and Host processor running Gigabit Ethernet Sof tware, and

Management Engine. The only required region is Region 0, the Flash Descriptor. Region

0 must be located in the first sector of device 0 (offset 0).

Flash Region Sizes

SPI flash space requirements differ by platform and configuration. The Flash Descriptor

requires one 4 KB or larger block. G bE requires two 4 KB or larger blocks . The Platform

Data Region is 32 KB. The amount of flash space consumed is dependent on the erase

granularity of the flash part and the platform requirements for the ME and BIOS

regions. The ME region will contain firmware to support Intel® Advanced Fan Speed

Control, Intel® Active Management Technology (Digital Office only), ASF 2.0 and

integrated Trusted Platform Module (mobile only).

Region Content

0 Flash Descriptor

1BIOS

2 Management Engine

3 Gigabit Ethernet

4Platform Data

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 251

Functional Description

5.23.1.3 Device Partitioning

The ICH9 SPI Flash controller supports two sets of attributes in SPI flash space. This

allows for supporting an asymmetric flash component that has two separate sets of

attributes in the upper and lower part of the memory array. An example of this is a

flash part that has different erase granularities in two different parts of the memory

array. This allows for the usage of two separate flash vendors if using two different

flash parts.

5.23.2 Flash Descriptor

The maximum size of the Flash Descriptor is 4 KB. If the block/sector size of the SPI

flash device is greater than 4 KB, the flash descriptor will only use the first 4 KB of the

first block. The flash descriptor requires its own block at the bottom of memory

(0x00h). The information stored in the Flash Descriptor can only be written during the

manufacturing process as its read/write permissions must be set to Read only when the

computer leaves the manufacturing floor.

The Flash Descriptor is made up of eleven sections:

Table 5-57. Region Size versu s Erase Granularity of Flash Components

Region Size with 4 KB

Blocks

Size with 8 KB

Blocks (Mobi le

Only)

Size with 64 KB

Blocks

Descriptor 4 KB 8 KB 64 KB

GbE 8 KB 16 KB 128 KB

Platform Data Region 32 KB 32 KB Not Supported

BIOS Varies by Platform Varies by Platform Varies by Platform

ME Varies by Platform Varies by Platform Varies by Platform

Figure 5-16. Flash Partition Boundary

Lower

Flash

Partitio n

Upper Flash

Partitio n

…

Flash Partition

Boundary

Functional Description

252 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

1. The Flash signature selects Descriptor Mode as well as verifies if the flash is

programmed and functioning. The data at the bottom of the flash (offset 0) must be

0FF0A55Ah in order to be in Descriptor mode.

2. The Descriptor map has pointers to the other five descriptor sections as well as the

size of each.

Figure 5-17. Flash Descriptor Sections

Descriptor

MAP

Component

Signature

Region

Master

ICH Soft

Straps

Reserved

4KB

Managem ent

Engine VSCC

Table

Descriptor

Upper MAP

OEM Section

MCH Soft

Straps

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 253

Functional Description

3. The component section has information about the SPI flash in the system including:

the number of components, density of each, invalid instructions (such as chip

erase), and frequencies for read, fast read and write/erase instructions.

4. The Region section points to the three other regions as well as the size of each

region.

5. The master region contains the security settings for the flash, granting read/write

permissions for each region and identifying each master by a requestor ID. See

Section 5.23.2.1 for more information.

6 & 7. The MCH and ICH chipset soft strap sections contain MCH and ICH configurable

parameters.

8. The Reserved region between the top of the MCH strap section and the bottom of

the OEM Section is reserved for future chipset usages.

9 . The Descriptor Upper MAP determine s the length and base address of the

Management Engine VSCC Table.

10. The Management Engine VSCC Table holds the JEDEC ID and the VSCC information

of the entire SPI Flash supported by the NVM image.

11. OEM Section is 256 Bytes reserved at the top of the Flash Descriptor for use by

OEM.

5.23.2.1 Descriptor Master Region

The master region defines read and write access setting for each region of the SPI

device. The master region recognizes three masters: BIOS, Gigabit Ethernet, and

Management Engine. Each master is only allowed to do direct reads of its primary

regions.

Table 5-58. Region Access Control Table

Master Read/Write Access

Region CPU and BIOS ME/MCH GbE Controller

Descriptor N/A N/A N/A

BIOS CPU and BIOS can

always read from and

write to BIOS Region Read / Write Read / Write

Management

Engine Read / Write ME can always read

from and write to ME

Region Read / Write

Gigabit Ethernet Re ad / Writ e Read / Write GbE software can

always read from and

write to GbE region

Platform Data

Region N/A N/A N/A

Functional Description

254 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.23.3 Flash Access

There are two types of flash accesses:

Direct Access:

• Masters are allowed to do direct read only of their primary region

— Gigabit Ethernet region can only be directly accessed by the Gigabit Ethernet

controller. Gigabit Ethernet software must use Program R egisters to access the

Gigabit Ethernet region.

• Master's Host or Management Engine virtual read address is converted into the SPI

Flash Linear Address (FLA) using the Flash Descriptor Region Base/Limit registers

Progra m Register Access:

• Program Register Accesses are not allowed to cross a 4KB boundary and can not

issue a command that might extend across two components

• Software programs the FLA corresponding to the region desired

— Software must read the devices Primary Region Base/Limit address to create a

FLA.

5.23.3.1 Direct Access Security

• Requester ID of the device must match that of the primary Requester ID in the

Master Section

• Calculated Flash Linear Addre ss must fall between primary region base/limit

• Direct Write not allowed

• Direct Read Cache contents are reset to 0's on a read from a different master

— Supports the same cache flush mechanism in ICH7 which includes Program

Re g i s t er Writes

5.23.3.2 Register Access Security

• Only primary region masters can access the registers

Note: Processor running Gigabit Ethernet software can access Gigabit Ethernet registers

• Masters are only allowed to read or write those regions they have read/write

permission

• Using the Flash Region Access Permissions, one master can give another master

read/write permissions to their area

• Using the five Protected Range registers, each master can add separate read/write

protection above that granted in the Flash Descriptor for their own accesses

— Example: BIOS may want to protect different regions of BIOS from being

erased

— Ranges can extend across region boundaries

5.23.4 Serial Flash Device Compatibility Requirements

A variety of serial flash devices exist in the market. For a serial flash device to be

compatible with the Intel ICH9 SPI bus, it must meet the minimum requirements

detailed in the following sections.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 255

Functional Description

5.23.4.1 Intel® ICH9 SPI Based BIOS Requirements

A serial flash device must meet the following minimum requirements when used

explicitly for system BIOS storage.

• Erase size capability of at least one of the following: 64 Kbytes, 8 Kbytes, 4 Kbytes,

or 256 bytes.

• Device must support multiple writes to a page without requiring a preceding erase

cycle (Refer to Section 5.23.5)

• Serial flash device must ignore the upper address bits such that an address of

FFFFFFh aliases to the top of the flash memory.

• SPI Compatible Mode 0 support (clock phase is 0 and data is latched on the rising

edge of the clock).

• If the device receives a command that is not supported or incomplete (less than 8

bits), the device must complete the cycle gracefully without any impact on the flash

content.

• An erase command (page, sector, block, chip, etc.) must set all bits inside the

designated area (page, sector, block, chip, etc.) to 1 (Fh).

• Status Register bit 0 must be set to 1 when a write, erase or write to status register

is in progress and cleared to 0 when a write or erase is NOT in progress.

• Devices requiring the Write Enable command mst automatically clear the Write

Enable Latch at the end of Data Program instructions.

• Byte write must be supported. The flexibility to perform a write between 1 byte to

64 bytes is recommended.

• Hardware Sequencing requirements are optional in BIOS only platforms.

• SPI flash parts that do not meet Hardware sequencing command set requirements

may work in BIOS only platforms via software sequencing.

5.23.4.2 Integrated LAN Firmware SPI Flash Requirements

A serial flash device that will be used for system BIOS and Integrated LAN or

Integrated LAN only must meet all the SPI Based BIOS Requirements plus:

• Hardware sequencing

• 4, 8 or 64 KBytes erase capability must be supported.

5.23.4.2.1 SPI Flash Unlocking Requirements for Integrated LAN

BIOS must ensure there is no SPI flash based read/write/erase protection on the GbE

region. GbE firmware and drivers for the integrated LAN need to be able to read, write

and erase the GbE region at all times.

5.23.4.3 Intel® Management Engine Firmware SPI Flash R eq uire m ents

Intel Management Engine Firmw are must meet the SPI fl ash based BIOS R equirements

plus:

• Hardware Sequencing.

• Flash part must be uniform 4 KB er asable block throu ghout the entire device or for

desktop platform only, the flash part may have 64 KB blocks with the first block

(lowest address) divided into 4 KB or 8 KB blocks.

• Write protection scheme must meet SPI flash unlocking requirements for

Management Engine.

Functional Description

256 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.23.4.3.1 SPI Flash Unlocking Requirements for Management Engine

Flash devices must be globally unlocked (read, write and erase access on the ME

region) from power on by writing 00h to the flash’s status register to disable write

protection.

If the status register must be unprotected, it must use the enable write status register

command 50h or write enable 06h.

Opcode 01h (write to status register) must then be used to write a single byte of 00h

into the status register. This must unlock the entire part. If the SPI flash’s status

If there is no need to execute a write enable on the status register, then opcodes 06h

and 50h must be ignored.

After global unlock, BIOS has the ability to lock down small sections of the flash as long

as they do not involve the ME or GbE region.

5.23.4.4 Hardware Sequencing Requirements

The following table contains a list of commands and the associated opcodes that a SPI-

based serial flash device must support in order to be compatible with hardware

sequencing.

5.23.4.4.1 JEDEC ID

Since each serial flash device may have unique capabilities and commands, the JEDEC

ID is the necessary mechanism for identifying the device so the uniqueness of the

device can be comprehended by the controller (master). The JEDEC ID uses the opcode

9Fh and a specified implementation and usage model. This JEDEC Standard

Manufacturer and Device ID read method is defined in Standard JESD21-C, PRN03-NV.

Table 5-59. Hardware Sequencing Commands and Opcode Requirements

Commands Opcode Notes

Write to Status Register 01h Writes a byte to SPI flash’s status register. Enable Write

to Status Register command must be run prior to this

command.

Program Data 02h Single byte or 64 byte write as determined by flash part

capabilities and software.

Read Data 03h

Write Disable 04h

Read Status 05h Outputs contents of SPI flash’s status register

Write Enable 06h

Fast Read 0Bh

Enable Write to Status

06h Enabl es a b it in the sta t us r egi ster to allow an update to

the status register

Erase Program

mable 256B, 4 Kbyte, 8 Kbyte or 64 Kbyte

Full Chip Erase C7h

JEDEC ID 9Fh See Section .

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 257

Functional Description

5.23.5 Multiple Page Write Usage Model

The system BIOS and Intel Active Management Technology firmware (Digital Office

only) usage models require that the serial flash device support multiple writes to a

page (minimum of 512 writes) without requiring a preceding erase command. BIOS

commonly uses capabilities such as counters that are used for error logging and system

boot progress logging. These counters are typically implemented by using byte-writes

to ‘increment’ the bits within a page that have been designated as the counter. The

Intel AMT firmware usage model requires the capability for multiple data updates within

any given page. These data updates occur via byte-writes without executing a

preceding erase to the given page. Both The BIOS and Intel AMT firmware multiple

page write usage models applies to sequential and non-sequential data writes.

Note: This usage model requirement is based on any given bit only being written once from a

‘1’ to a ‘0’without requiring the preceding erase. An er ase would be required to change

bits back to the 1 state.

5.23.5.1 Soft Flash Protection

There are two types of flash protection that are not defined in the flash descriptor

supported by ICH9:

1. BIOS Range Write Protection

2. SMI#-Based Global Write Protection

Both mechanisms are logically OR’d together such that if any of the mechanisms

indicate that the access should be blocked, then it is blocked. Table 5-60 provides a

summary of the mechanisms.

A blocked command will appear to software to finish, except that the Blocked Access

status bit is set in this case.

5.23.5.2 BIOS Range Write Protection

The ICH9 provides a method for blocking writes to specific ranges in the SPI flash when

the Protected BIOS Ranges are enabled. This is achieved by checking the Opcode type

information (which can be locked down by the initial Boot BIOS) and the address of the

requested command against the base and limit fields of a Write Protected BIOS range.

Note: Once BIOS has locked down the Protected BIOS Range registers, this mechanism

remains in place until the next system reset.

Table 5-60. Flash Protection Mechanism Summary

Mechanism Accesses

Blocked Range

Specific?

Reset-Override

or SMI#-

Override?

Equivalent Function on

FWH

BIOS Range

Write

Protection Writes Yes Reset Override FWH Sector Protection

Write Protect Writes No SMI# Override Same as Write Protect in

previous ICHs for FWH

Functional Description

258 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.23.5.3 SMI# Based Global Write Protection

The ICH provides a method for blocking writes to the SPI flash when the Write

Protected bit is cleared (i.e., protected). This is achieved by checking the Opcode type

information (which can be locked down by the initial Boot BIOS) of the requested

command.

The Write Protect and Lock Enable bits interact in the same manner for SPI BIOS as

they do for the FWH BIOS.

5.23.6 Flash Device Configurations

The ICH9-based platform may use the serial flash in multiple configurations. The

following table focuses on the supported configurations involving the ICH9 and Intel

Active Management Technology (Digital Office only).

Note: When SPI is selected for BIOS and a SPI device is detected by the ICH9, LPC based

BIOS flash is disabled.

Note: Firmware includes Intel Activ e Management Technology (Digital Office only), ASF, Intel

Quiet System Technology and Gigabit Ethernet.

5.23.7 SPI Flash Device Recommended Pinout

The table below contains the recommended serial flash device pin-out for an 8-pin

device. Use of the recommended pin-out on an 8-pin device reduces complexities

involv ed with designing the serial flash device onto a motherboard and allows for

support of a common footprint usage model (refer to Section 5.23.8.1).

Although an 8-pin device is preferred over a 16-pin device due to footprint

compatibility, the following table contains the recommended serial flash device pin-out

for a 16-pin SOIC.

Configuration System BIOS

Storage Intel® ICH9

Firmware Minimum Number

of SPI Device(s)

1SPINo 1

2Non-SPIYes 1

3SPIYes 1

4Non-SPINo 0

Table 5-61. Recommended Pinout for 8-Pin Serial Flash Device

Pin # Signal

1Chips Select

2 Data Output

3 Write Protect

4Ground

5 Data Input

6Serial Clock

7Hold / Reset

8 Supply Voltage

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 259

Functional Description

5.23.8 Serial Flash Device Package

5.23.8.1 Common Footprint Usage Model

In order to minimize platform motherboard redesign and to enable platform Bill of

Material (BOM) selectability, many PC System OEM’s design their motherboard with a

single common footprint. This common footprint allows population of a soldered down

device or a socket that accepts a leadless device. This enables the board manufacturer

to support, via selection of the appropriate BOM, either of these solutions on the same

system without requiring any board redesign.

The common footprint usage model is desirable during system debug and by flash

content developers since the leadless device can be easily removed and reprogrammed

without damage to device leads. When the board and flash content is mature for high-

volume production, both the socketed leadless solution and the soldered down leaded

solution are available through BOM selection.

5.23.8.2 Serial Flash Device Package Recommendations

It is highly recommended that the common footprint usage model be supported. An

example of how this can be accomplished is as follows:

• The recommended pinout for 8-pin serial flash devices is used (refer to

Section 5.23.7).

• The 8-pin device is supported in either an 8-contact VDFPN (6x5 mm MLP) package

or an 8-contact WSON (5x6 mm) package. These packages can fit into a socket

that is land pattern compatible with the wide body SO8 package.

• The 8-pin device is supported in the SO8 (150 mil) and in the wide-body SO8 (200

mil) packages.

The 16-pin device is supported in the SO16 (300 mil) package.

Table 5-62. Recommended Pinout for 16-Pin Serial Flash Device

Pin # Signal Pin # Signal

1 Hold / Reset 9 Write Protect

2 Supply Voltage 10 Ground

3 No Connect 11 No Connect

4 No Connect 12 No Connect

5 No Connect 13 No Connect

6 No Connect 14 No Connect

7 Chip Select 15 Serial Data In

8 Serial Data Out 16 Serial Clock

Functional Description

260 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

5.24 Intel® Quiet System Technology (Intel® QST)

(Desktop Only)

The ICH9 implements three PWM and 4 T ACH signals for Intel Quiet System Technology

(QST).

Note: Intel Quiet System Technology functionality requires a correctly configured system,

including an appropriate (G)MCH with ME, ME Firmware, and system BIOS support.

5.24.1 PWM Outputs

This signal is driven as open-drain. An external pull-up resistor is integrated into the

fan to provide the rising edge of the PWM output signal. The PWM output is driven low

during reset, which represents 0% duty cycle to the fans. After reset de-assertion, the

PWM output will continue to be driven low until one of the following occurs:

• The internal PWM control register is programmed to a non-zero value by the Intel

QST firmware.

• The watchdog timer expires (enabled and set at 4 seconds by default).

• The polarity of the signal is inverted by the Intel QST firmware.

Note that if a PWM output will be programmed to inverted polarity for a particular fan,

then the low voltage driven during reset represents 100% duty cycle to the fan.

5.24.2 TACH Inputs

This signal is driven as an open-collector or open-drain output from the fan. An

external pull-up is expected to be implemented on the motherboard to provide the

rising edge of the T ACH input. This signal has analog hysteresis and digital filtering due

to the potentially slow rise and fall times. This signal has a weak internal pull-up

resistor to keep the input buffer from floating if the TACH input is not connected to a

fan.

5.25 Thermal Sensors

ICH9 integrates two thermal sensors that monitor the temperature within its die. The

thermal sensors are used for Intel®Quiet System Technology (Intel®QST). The Intel

QST firmware can internally access the temperature measured by the sensors and use

the data as a factor to determine how to control the fans.

The ICH9 thermal sensors also provide the capability to protect the ICH9 under a

catastrophic thermal situation. When the sensors are enabled and correctly

programmed by the system BIOS, the ICH9 will shut down the system when the ICH9

thermal limit is reached. Refer to the Thermal Memory Mapped Configuration R egisters

Section 23.2 for more info on the catastrophic settings.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 261

Functional Description

5.26 Feature Capability Mechanism

A set of registers is included in the ICH9 LPC Interface (Device 31, Function 0, offset

E0h - EBh) that allows the system software or BIOS to easily determine the features

supported by ICH9. These registers can be accessed through LPC PCI configuration

space, thus allowing for convenient single point access mechanism for chipset feature

detection.

This set of registers consists of:

Capability ID (FDCAP)

Capability Length (FDLEN)

Capability Version and Vendor-Specific Capability ID (FDVER)

Feature Vector (FVECT)

5.27 Integrated Trusted Platform Module (Mobile Only)

The integrated TPM (TPM) implementation consists of firmware, Intel® Management

Engine resources and dedicated hardware within the ICH and the (G)MCH. The

integrated TPM supports all requirements of the TPM Specification Version 1.2, Level 2

Revision 103, as published by the Trusted Computing Group.

Note: Integrated TPM functionality requires a correctly configured system, including an

appropriate mobile (G)MCH with Intel Management Engine firmware, ICH9M and SPI

Flash.

5.27.1 Integrated TPM Hardware Requirements

The following hardware components are required for TPM 1.2 functionality :

1. SPI Flash Memory: The SPI flash component connected to the ICH (SPI interface)

provides non-volatile storage requirement for the integrated TPM. It contains the

FW code which is loaded by the Intel Management Engine upon power on.

2. Monotonic Counters: The ICH9M contains four TPM 1.2 compliant monotonic

counters that reside in the RTC well which maintains values programmed by the

integrated TPM across power cycles. The counters are only incremented by TPM

software (host or ME) and are not controlled by the ICH hardware.

3. Physical Presence: Physical presence indication is required in order to enable

certain TPM commands. These commands are generally used to bypass owner

authorized commands when the authorization data is unavailable or to set the

integrated TPM to a non-owner state. The Management Engine Firm ware uses the

CLGPIO5 pin on the ICH9M to indicate Physical Presence to the platform when

pulled high. In addition, Physical Presence flags can be set to force Physical

Presence by firmware.

4. Chipset: An ICH9M and (G)MCH with Intel Management Engine enabled is required

for integrated TPM support.

5.27.2 Enabling integrated TPM

The integrated TPM is enabled based on the combination of a functional strap on both

the ICH and the MCH and a soft strap bit found in the SPI Descriptor. When the

integrated TPM is enabled, Front Side Bus cycles that would otherwise propagate to the

LPC bus will be routed by the Config Bus Decoder to the integrated TPM Host Decoder.

Either Functional strap or the soft strap bit may be used to disable the integrated TPM.

•ICH Functional St rap: Th e ICH9M enables Integrated TPM when SPI_MOSI is

sampled high on the rising edge of CLPWROK and disabled if the SPI_MOSI signal is

sampled low. See Section 2.24.1 for details. The SPI_MOSI signal requires an

Functional Description

262 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

external pull-up resistor to enable the integrated TPM. SPI_MOSI has an integrated

pull-down resistor enabled at reset only and does not require an external pull-down

resistor to disable integrated TPM.

•Soft Stra p: The integrated TPM Disable bit (bit 2) in the MCHSTRP0 register

(FSMBA + 0h) within the flash descriptor can act as an override to the functional

straps on both the ICH and MCH. When set, the integrated TPM will be disabled

regardless of the values of the functional straps on the ICH and/or MCH. This bit

along with both functional straps must be appropriately configured to enable

integrated TPM.

•(G)MCH Funct ional Strap: For (G)MCH functional strap information, consult the

appropriate MCH EDS.

§ §

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 263

Ballout Definition

6 Ballout Definition

This chapter contains the Intel® ICH9 ballout information.

6.1 Intel® ICH9 Ballout (Desktop Only)

This section contains the ICH9 ballout. Figure 6-1 and Figure 6-2 show the ballout from

a top of the package view . Table 6-1 is the BGA ball list, sorted alphabetically by signal

name.

Ballout Definition

264 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Figure 6-1. Intel® ICH9 Ballout (Top view–Left Side) (Desktop Only)

123456789101112131415

AVss Vcc3_3 PIRQD# AD11 AD4 V5REF GNT1# /

GPIO51 GPIO12 GPIO14 /

CLGPIO2 VccLAN1_0

5GPIO27 VccLAN3_3 SLP_S3# GPIO24 /

MEM_LED SMLINK0 A

BVcc3_3 Vss PCICLK AD9 Vss AD8 AD7 Vss Vcc3_3 VccLAN1_0

5Vss VccLAN3_3 SLP_S4# Vss SMLINK1 B

CAD24 AD25 AD26 C/BE2# AD14 DEVSEL# GNT2# /

GPIO53 AD1 AD3 AD0 S4_STATE#

/ GPIO26 GPIO57 /

CLGPIO5 TP0 PLTRST# STP_PCI# /

GPIO15 C

DAD27 AD15 AD21 D

EPIRQB# Vss PAR AD16 TRDY# AD10 C/BE3# AD2 AD6 AD18 AD5 LAN_RXD2 LAN_RSTS

YNC Vss E

FPIRQC# PIRQG# /

GPIO4 AD29 PERR# Vss GNT3# /

GPIO55 AD13 Vss STOP# C/BE0# Vss REQ2# /

GPIO52 LAN_TXD1 LAN_TXD0 F

GAD30 PIRQH# /

GPIO5 Vcc3_3 AD23 AD20 AD17 REQ3# /

GPIO54 C/BE1# AD19 Vcc3_3 FRAME# REQ1# /

GPIO50 LAN_TXD2 LAN_RXD0 G

HFWH1 /

LAD1 Vss AD31 GNT0# AD22 Vcc3_3 PLOCK# Vss Vcc1_5_A Vcc1_5_A AD12 Vss LAN_RXD1 VccSus3_3 H

JFWH3 /

LAD3 Vcc3_3 LDRQ1# /

GPIO23 PIRQA# Vss AD28 IRDY# J

KGPIO18 GPIO32 FWH0 /

LAD0 SERR# PIRQE# /

GPIO2 REQ0# Vcc3_3 K

LSATACLKR

EQ# /

GPIO35 Vss RCIN# FWH4 /

LFRAME# LDRQ0# PIRQF# /

GPIO3 Vcc3_3 L

MOC7# /

GPIO31 GPIO16 INIT3_3V# CLK14 Vss FWH2 /

LAD2 Vss Vcc1_05 Vcc1_05 Vss Vcc1_05 M

NOC5# /

GPIO29 OC4# /

GPIO43 OC1# /

GPIO40 OC6# /

GPIO30 SERIRQ GPIO0 SPKR Vcc1_05 Vss Vss Vss N

POC11# /

GPIO47 Vss OC8# /

GPIO44 OC0# /

GPIO59 Vss OC2# /

GPIO41 A20GATE Vss Vss Vss Vss P

RSUS_STAT

# / LPCPD PCIRST# PME# SUSCLK OC9# /

GPIO45 OC3# /

GPIO42 Vss Vcc1_05 Vss Vss Vss R

TVcc1_5_A Vss PWRBTN# Vss CLPWROK OC10# /

GPIO46 CK_PWRG

DVss Vss Vss Vss T

UVccSus3_3 VccSus3_3 VccSus3_3 VccSus3_3 VccSus3_3 VccSus3_3 VccSus3_3 Vcc1_05 Vss Vss Vss U

VUSBP11N USBP11P Vss USBP9P USBP9N Vss VccSus3_3 Vcc1_05 Vss Vss Vss V

WVss USBP10N USBP10P Vss Vss VccSus3_3 VccSus3_3 Vcc1_05 Vcc1_05 Vss Vcc1_05 W

YUSBP8N USBP8P Vss USBP6P USBP6N Vss VccSus3_3 Y

AA Vss USBP7P USBP7N Vss Vss Vcc1_5_A Vcc1_5_A AA

AB USBP5N USBP5P Vss USBP3P USBP3N Vcc1_5_A Vcc1_5_A AB

AC Vss USBP4P USBP4N Vss Vss VccSus1_05 Vss VccSusHDA VccHDA Vcc1_5_A Vss Vcc1_5_A Vcc1_5_A Vcc1_5_A AC

AD USBP2N USBP2P Vss USBP0P USBP0N Vss VccSus1_5 Vss Vcc3_3 Vcc1_5_A Vcc1_5_A Vcc1_5_A Vss Vss AD

AE Vss USBP1P USBP1N Vss Vss SATALED# Vss Vss Vss Vcc1_5_A Vss Vss Vss Vss AE

AF V5REF_Sus VccSus3_3 Vss GPIO20 GPIO33 Vss SATA5TXN Vss SATA4TXN Vcc1_5_A SATA3TXN Vss SATA2TXP Vss AF

AG USBRBIAS# USBRBIAS CLK48 AG

AH HDA_SDIN2 Vss HDA_BIT_C

LK HDA_SDIN1 GPIO34 Vss SATA5TXP Vss SATA4TXP Vcc1_5_A Vcc1_5_A SATA3TXP Vss SATA2TXN Vss AH

AJ HDA_RST# HDA_SDOU

THDA_SDIN3 Vss Vss SATARBIAS SATA5RXN Vss SATA4RXN Vcc1_5_A SATA3RXN Vss SATA2RXN Vss SATA1RXN AJ

AK HDA_SYNC Vss HDA_SDIN0 Vcc3_3 VccUSBPLL SATARBIAS

#SATA5RXP Vss SATA4RXP Vcc1_5_A SATA3RXP Vss SATA2RXP Vss SATA1RXP AK

123456789101112131415

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 265

Ballout Definition

Figure 6-2. Intel® ICH9 Ballout (Top view–Right Side) (Desktop Only)

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

ATP6 VccSus3_3 GPIO9 /

WOL_EN GPIO13 GPIO8 RTCX1 VccRTC VccCL1_05 Vcc1_05 RTCRST# VccCL1_5 VccGLAN3_

3VccGLANPL

LGLAN_COM

PO Vss A

BTP7 Vss STP_CPU# /

GPIO25 Vss VccSus3_3 RTCX2 Vss VccCL3_3 Vcc1_05 Vss SPI_MISO Vss Vss GLAN_COM

PI VccGLAN1_

CSMBALERT

# / GPIO11 GPIO10 /

CLGPIO1 TP5 SST VccSus3_3 LAN_RST# VRMPWRG

DVccCL3_3 Vcc1_05 PWROK SPI_MOSI CL_VREF0 VccGLAN1_

5VccGLAN1_

DVss PERn6 /

GLAN_RXN PERp6 /

GLAN_RXP D

ESMBDATA VccSus3_3 Vss TP4 WAKE# LAN100_SL

PVss INTVRMEN Vcc1_05 SPI_CS0# PETn6 /

GLAN_TXN PETp6 /

GLAN_TXP Vss Vss E

FGPIO56 SLP_M# LINKALERT#

/ GPIO60 /

CLGPIO4

SYS_RESE

T# TP3 Vss RSMRST# SPI_CS1# /

GPIO58 /

CLGPIO6 Vcc1_05 GLAN_CLK Vss Vss PERp5 PERn5 F

GVss SLP_S5# GPIO28 RI# CL_RST0# INTRUDER# CL_CLK0 SPI_CLK Vcc1_05 Vss PETn5 PETp5 Vss Vss G

HSMBCLK VccSus1_05 VccSus1_5 Vss SRTCRST# CL_DATA0 Vss Vcc1_05 Vcc1_05 Vss Vss Vss PERp4 PERn4 H

JVcc1_05 Vcc1_5_B Vcc1_5_B PETn4 PETp4 Vss Vss J

KVcc1_5_B Vcc1_5_B Vcc1_5_B Vss Vss PERp3 PERn3 K

LVss Vcc1_5_B Vcc1_5_B PETn3 PETp3 Vss Vss L

MVss Vcc1_05 Vcc1_05 Vcc1_05 Vcc1_5_B Vcc1_5_B Vcc1_5_B Vss Vss PERp2 PERn2 M

NVss Vss Vss Vcc1_05 Vss Vcc1_5_B Vcc1_5_B PETn2 PETp2 Vss Vss N

PVss Vss Vss Vss Vcc1_5_B Vcc1_5_B Vcc1_5_B Vss Vss PERp1 PERn1 P

RVss Vss Vss Vcc1_05 Vss Vcc1_5_B Vcc1_5_B PETn1 PETp1 Vss Vss R

TVss Vss Vss Vss Vcc1_5_B Vcc1_5_B Vcc1_5_B Vcc1_5_B Vcc1_5_B Vss VccDMIPLL T

UVss Vss Vss Vcc1_05 Vss Vcc1_5_B DMI_CLKP DMI_CLKN Vcc1_5_B Vcc1_5_B Vcc1_5_B U

VVss Vss Vss Vcc1_05 Vcc1_5_B Vcc1_5_B Vcc1_5_B Vss Vss DMI0TXP DMI0TXN V

WVss Vcc1_05 Vcc1_05 Vcc1_05 Vss Vcc1_5_B Vcc1_5_B DMI0RXP DMI0RXN Vss Vss W

YVcc1_5_B Vcc1_5_B Vcc1_5_B Vss Vss DMI1TXP DMI1TXN Y

AA Vcc1_5_B Vcc1_5_B Vcc1_5_B DMI1RXN DMI1RXP Vss Vss AA

AB Vcc1_5_A Vcc1_5_B Vcc1_5_B Vss Vss DMI2TXP DMI2TXN AB

AC Vcc1_5_A Vcc1_5_A Vcc1_5_A Vcc3_3 Vcc1_5_A Vcc3_3 IGNNE# PECI Vss Vcc1_5_B DMI2RXN DMI2RXP Vss Vss AC

AD Vss Vcc1_5_A Vss Vss SDATAOUT

1 / GPIO48 SATA5GP Vss CPUPWRG

DTHRMTRIP

#Vcc1_5_B Vcc1_5_B Vcc1_5_B DMI3TXN DMI3TXP AD

AE Vss Vcc1_5_A Vss Vss SATA1GP /

GPIO19 SATA2GP /

GPIO36 SATA3GP /

GPIO37 INIT# TP2 Vss DMI3RXP Vcc1_5_B Vcc1_5_B Vcc1_5_B AE

AF SATA1TXP Vcc1_5_A SATA_CLKN SATA_CLK

PVss Vcc3_3 SATA4GP Vss NMI Vss DMI3RXN DMI_IRCO

MP Vss DMI_ZCOM

PAF

AG Vss VccDMI VccDMI AG

AH SATA1TXN Vcc1_5_A Vcc1_5_A Vss Vss TACH0 /

GPIO17 TACH2 /

GPIO6 SDATAOUT

0 / GPIO39 Vcc3_3 MCH_SYNC

#SMI# INTR V_CPU_IO Vss Vcc3_3 AH

AJ Vss SATA0RXP Vcc1_5_A SATA0TXP Vss PWM0 PWM1 Vss SCLOCK /

GPIO22 GPIO49 Vss FERR# A20M# STPCLK# V_CPU_IO AJ

AK Vss SATA0RXN Vcc1_5_A SATA0TXN VccSATAPL

LTACH1 /

GPIO1 PWM2 TACH3 /

GPIO7 SLOAD /

GPIO38 SATA0GP /

GPIO21 THRM# Vss TP1 Vss Vss AK

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

266 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Ballout Definition

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

A20GATE P8

A20M# AJ28

AD0 C10

AD1 C8

AD2 E9

AD3 C9

AD4 A5

AD5 E12

AD6 E10

AD7 B7

AD8 B6

AD9 B4

AD10 E7

AD11 A4

AD12 H12

AD13 F8

AD14 C5

AD15 D2

AD16 E5

AD17 G7

AD18 E11

AD19 G10

AD20 G6

AD21 D3

AD22 H6

AD23 G5

AD24 C1

AD25 C2

AD26 C3

AD27 D1

AD28 J7

AD29 F3

AD30 G1

AD31 H3

C/BE0# F11

C/BE1# G9

C/BE2# C4

C/BE3# E8

CK_PWRGD T8

CL_CLK0 G22

CL_DATA0 H21

CL_RST0# G20

CL_VREF0 C27

CLK14 M5

CLK48 AG3

CLPWROK T6

CPUPWRGD AD23

DEVSEL# C6

DMI_CLKN U26

DMI_CLKP U25

DMI_IRCOMP AF28

DMI_ZCOMP AF30

DMI0RXN W28

DMI0RXP W26

DMI0TXN V30

DMI0TXP V29

DMI1RXN AA26

DMI1RXP AA28

DMI1TXN Y30

DMI1TXP Y29

DMI2RXN AC26

DMI2RXP AC28

DMI2TXN AB30

DMI2TXP AB29

DMI3RXN AF26

DMI3RXP AE26

DMI3TXN AD29

DMI3TXP AD30

FERR# AJ27

FRAME# G12

FWH0 / LAD0 K3

FWH1 / LAD1 H1

FWH2 / LAD2 M7

FWH3 / LAD3 J1

FWH4 / LFRAME# L5

GLAN_CLK F25

GLAN_COMPI B29

GLAN_COMPO A29

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

GNT0# H5

GNT1# / GPIO51 A7

GNT2# / GPIO53 C7

GNT3# / GPIO55 F7

GPIO0 N7

GPIO8 A20

GPIO9 / WOL_EN A18

GPIO10 / CLGPIO1 C17

GPIO12 A8

GPIO13 A19

GPIO14 / CLGPIO2 A9

GPIO16 M2

GPIO18 K1

GPIO20 AF5

GPIO24 / MEM_LED A14

GPIO27 A11

GPIO28 G18

GPIO32 K2

GPIO33 AF6

GPIO34 AH5

GPIO49 AJ25

GPIO56 F16

GPIO57 / CLGPIO5 C12

HDA_BIT_CLK AH3

HDA_RST# AJ1

HDA_SDIN0 AK3

HDA_SDIN1 AH4

HDA_SDIN2 AH1

HDA_SDIN3 AJ3

HDA_SDOUT AJ2

HDA_SYNC AK1

IGNNE# AC22

INIT# AE23

INIT3_3V# M3

INTR AH27

INTRUDER# G21

INTVRMEN E23

IRDY# J8

LAN_RST# C21

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 267

Ballout Definition

LAN_RSTSYNC E14

LAN_RXD0 G15

LAN_RXD1 H14

LAN_RXD2 E13

LAN_TXD0 F15

LAN_TXD1 F14

LAN_TXD2 G14

LAN100_SLP E21

LDRQ0# L6

LDRQ1# / GPIO23 J3

LINKALERT# /

GPIO60 / CLGPIO4 F18

MCH_SYNC# AH25

NMI AF24

OC0# / GPIO59 P5

OC1# / GPIO40 N3

OC2# / GPIO41 P7

OC3# / GPIO42 R7

OC4# / GPIO43 N2

OC5# / GPIO29 N1

OC6# / GPIO30 N5

OC7# / GPIO31 M1

OC8# / GPIO44 P3

OC9# / GPIO45 R6

OC10# / GPIO46 T7

OC11# / GPIO47 P1

PAR E3

PCICLK B3

PCIRST# R2

PECI AC23

PERn1 P30

PERn2 M30

PERn3 K30

PERn4 H30

PERn5 F30

PERn6 / GLAN_RXN D29

PERp1 P29

PERp2 M29

PERp3 K29

Table 6-1. Intel® ICH9

Ballout by Signal Nam e

(Desktop Only)

Ball Name Ball #

PERp4 H29

PERp5 F29

PERp6 / GLAN_RXP D30

PERR# F5

PETn1 R26

PETn2 N26

PETn3 L26

PETn4 J26

PETn5 G26

PETn6 / GLAN_TXN E26

PETp1 R28

PETp2 N28

PETp3 L28

PETp4 J28

PETp5 G28

PETp6 / GLAN_TXP E28

PIRQA# J5

PIRQB# E1

PIRQC# F1

PIRQD# A3

PIRQE# / GPIO2 K6

PIRQF# / GPIO3 L7

PIRQG# / GPIO4 F2

PIRQH# / GPIO5 G2

PLOCK# H8

PLTRST# C14

PME# R3

PWM0 AJ21

PWM1 AJ22

PWM2 AK22

PWRBTN# T3

PWROK C25

RCIN# L3

REQ0# K7

REQ1# / GPIO50 G13

REQ2# / GPIO52 F13

REQ3# / GPIO54 G8

RI# G19

RSMRST# F22

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

RTCRST# A25

RTCX1 A21

RTCX2 B21

S4_STATE# /

GPIO26 C11

SATA_CLKN AF18

SATA_CLKP AF19

SATA0GP / GPIO21 AK25

SATA0RXN AK17

SATA0RXP AJ17

SATA0TXN AK19

SATA0TXP AJ19

SATA1GP / GPIO19 AE20

SATA1RXN AJ15

SATA1RXP AK15

SATA1TXN AH16

SATA1TXP AF16

SATA2GP / GPIO36 AE21

SATA2RXN AJ13

SATA2RXP AK13

SATA2TXN AH14

SATA2TXP AF14

SATA3GP / GPIO37 AE22

SATA3RXN AJ11

SATA3RXP AK11

SATA3TXN AF12

SATA3TXP AH12

SATA4GP AF22

SATA4RXN AJ9

SATA4RXP AK9

SATA4TXN AF10

SATA4TXP AH9

SATA5GP AD21

SATA5RXN AJ7

SATA5RXP AK7

SATA5TXN AF8

SATA5TXP AH7

SATACLKREQ# /

GPIO35 L1

SATALED# AE7

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

268 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Ballout Definition

SATARBIAS AJ6

SATARBIAS# AK6

SCLOCK / GPIO22 AJ24

SDATAOUT0 /

GPIO39 AH23

SDATAOUT1 /

GPIO48 AD20

SERIRQ N6

SERR# K5

SLOAD / GPIO38 AK24

SLP_M# F17

SLP_S3# A13

SLP_S4# B13

SLP_S5# G17

SMBALERT# /

GPIO11 C16

SMBCLK H16

SMBDATA E16

SMI# AH26

SMLINK0 A15

SMLINK1 B15

SPI_CLK G23

SPI_CS0# E25

SPI_CS1# /

GPIO58 / CLGPIO6 F23

SPI_MISO B26

SPI_MOSI C26

SPKR N8

SRTCRST# H20

SST C19

STOP# F10

STP_CPU# /

GPIO25 B18

STP_PCI# / GPIO15 C15

STPCLK# AJ29

SUS_STAT# /

LPCPD R1

SUSCLK R5

SYS_RESET# F19

TACH0 / GPIO17 AH21

TACH1 / GPIO1 AK21

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

TACH2 / GPIO6 AH22

TACH3 / GPIO7 AK23

THRM# AK26

THRMTRIP# AD24

TP0 C13

TP1 AK28

TP2 AE24

TP3 F20

TP4 E19

TP5 C18

TP6 A16

TP7 B16

TRDY# E6

USBP0N AD6

USBP0P AD5

USBP1N AE3

USBP1P AE2

USBP2N AD1

USBP2P AD2

USBP3N AB6

USBP3P AB5

USBP4N AC3

USBP4P AC2

USBP5N AB1

USBP5P AB2

USBP6N Y6

USBP6P Y5

USBP7N AA3

USBP7P AA2

USBP8N Y1

USBP8P Y2

USBP9N V6

USBP9P V5

USBP10N W2

USBP10P W3

USBP11N V1

USBP11P V2

USBRBIAS AG2

USBRBIAS# AG1

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

V_CPU_IO AH28

V_CPU_IO AJ30

V5REF A6

V5REF_Sus AF1

Vcc1_05 A24

Vcc1_05 B24

Vcc1_05 C24

Vcc1_05 E24

Vcc1_05 F24

Vcc1_05 G24

Vcc1_05 H23

Vcc1_05 H24

Vcc1_05 J23

Vcc1_05 M12

Vcc1_05 M13

Vcc1_05 M15

Vcc1_05 M17

Vcc1_05 M18

Vcc1_05 M19

Vcc1_05 N12

Vcc1_05 N19

Vcc1_05 R12

Vcc1_05 R19

Vcc1_05 U12

Vcc1_05 U19

Vcc1_05 V12

Vcc1_05 V19

Vcc1_05 W12

Vcc1_05 W13

Vcc1_05 W15

Vcc1_05 W17

Vcc1_05 W18

Vcc1_05 W19

Vcc1_5_A AA7

Vcc1_5_A AA8

Vcc1_5_A AB7

Vcc1_5_A AB8

Vcc1_5_A AB23

Vcc1_5_A AC11

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 269

Ballout Definition

Vcc1_5_A AC13

Vcc1_5_A AC14

Vcc1_5_A AC15

Vcc1_5_A AC16

Vcc1_5_A AC17

Vcc1_5_A AC18

Vcc1_5_A AC20

Vcc1_5_A AD11

Vcc1_5_A AD12

Vcc1_5_A AD13

Vcc1_5_A AD17

Vcc1_5_A AE11

Vcc1_5_A AE17

Vcc1_5_A AF11

Vcc1_5_A AF17

Vcc1_5_A AH10

Vcc1_5_A AH11

Vcc1_5_A AH17

Vcc1_5_A AH18

Vcc1_5_A AJ10

Vcc1_5_A AJ18

Vcc1_5_A AK10

Vcc1_5_A AK18

Vcc1_5_A H10

Vcc1_5_A H11

Vcc1_5_A T1

Vcc1_5_B AA23

Vcc1_5_B AA24

Vcc1_5_B AA25

Vcc1_5_B AB24

Vcc1_5_B AB25

Vcc1_5_B AC25

Vcc1_5_B AD25

Vcc1_5_B AD26

Vcc1_5_B AD28

Vcc1_5_B AE28

Vcc1_5_B AE29

Vcc1_5_B AE30

Vcc1_5_B J24

Table 6-1. Intel® ICH9

Ballout by Signal Nam e

(Desktop Only)

Ball Name Ball #

Vcc1_5_B J25

Vcc1_5_B K23

Vcc1_5_B K24

Vcc1_5_B K25

Vcc1_5_B L24

Vcc1_5_B L25

Vcc1_5_B M23

Vcc1_5_B M24

Vcc1_5_B M25

Vcc1_5_B N24

Vcc1_5_B N25

Vcc1_5_B P23

Vcc1_5_B P24

Vcc1_5_B P25

Vcc1_5_B R24

Vcc1_5_B R25

Vcc1_5_B T23

Vcc1_5_B T24

Vcc1_5_B T25

Vcc1_5_B T26

Vcc1_5_B T28

Vcc1_5_B U24

Vcc1_5_B U28

Vcc1_5_B U29

Vcc1_5_B U30

Vcc1_5_B V23

Vcc1_5_B V24

Vcc1_5_B V25

Vcc1_5_B W24

Vcc1_5_B W25

Vcc1_5_B Y23

Vcc1_5_B Y24

Vcc1_5_B Y25

Vcc3_3 AC19

Vcc3_3 AC21

Vcc3_3 AD10

Vcc3_3 AF21

Vcc3_3 AH24

Vcc3_3 AH30

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

Vcc3_3 AK4

Vcc3_3 A2

Vcc3_3 B1

Vcc3_3 B9

Vcc3_3 G3

Vcc3_3 G11

Vcc3_3 H7

Vcc3_3 J2

Vcc3_3 K8

Vcc3_3 L8

VccCL1_05 A23

VccCL1_5 A26

VccCL3_3 B23

VccCL3_3 C23

VccDMI AG29

VccDMI AG30

VccDMIPLL T30

VccGLAN1_5 B30

VccGLAN1_5 C28

VccGLAN1_5 C29

VccGLAN1_5 C30

VccGLAN3_3 A27

VccGLANPLL A28

VccHDA AC10

VccLAN1_05 A10

VccLAN1_05 B10

VccLAN3_3 A12

VccLAN3_3 B12

VccRTC A22

VccSATAPLL AK20

VccSus1_05 AC7

VccSus1_05 H17

VccSus1_5 AD8

VccSus1_5 H18

VccSus3_3 AF2

VccSus3_3 A17

VccSus3_3 B20

VccSus3_3 C20

VccSus3_3 E17

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

270 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Ballout Definition

VccSus3_3 H15

VccSus3_3 U1

VccSus3_3 U2

VccSus3_3 U3

VccSus3_3 U5

VccSus3_3 U6

VccSus3_3 U7

VccSus3_3 U8

VccSus3_3 V8

VccSus3_3 W7

VccSus3_3 W8

VccSus3_3 Y8

VccSusHDA AC9

VccUSBPLL AK5

VRMPWRGD C22

Vss AA1

Vss AA5

Vss AA6

Vss AA29

Vss AA30

Vss AB3

Vss AB26

Vss AB28

Vss AC1

Vss AC5

Vss AC6

Vss AC8

Vss AC12

Vss AC24

Vss AC29

Vss AC30

Vss AD3

Vss AD7

Vss AD9

Vss AD14

Vss AD15

Vss AD16

Vss AD18

Vss AD19

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

Vss AD22

Vss AE1

Vss AE5

Vss AE6

Vss AE8

Vss AE9

Vss AE10

Vss AE12

Vss AE13

Vss AE14

Vss AE15

Vss AE16

Vss AE18

Vss AE19

Vss AE25

Vss AF3

Vss AF7

Vss AF9

Vss AF13

Vss AF15

Vss AF20

Vss AF23

Vss AF25

Vss AF29

Vss AG28

Vss AH2

Vss AH6

Vss AH8

Vss AH13

Vss AH15

Vss AH19

Vss AH20

Vss AH29

Vss AJ4

Vss AJ5

Vss AJ8

Vss AJ12

Vss AJ14

Vss AJ16

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

Vss AJ20

Vss AJ23

Vss AJ26

Vss AK2

Vss AK8

Vss AK12

Vss AK14

Vss AK16

Vss AK27

Vss AK29

Vss AK30

Vss A1

Vss A30

Vss B2

Vss B5

Vss B8

Vss B11

Vss B14

Vss B17

Vss B19

Vss B22

Vss B25

Vss B27

Vss B28

Vss D28

Vss E2

Vss E15

Vss E18

Vss E22

Vss E29

Vss E30

Vss F6

Vss F9

Vss F12

Vss F21

Vss F26

Vss F28

Vss G16

Vss G25

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 271

Ballout Definition

Vss G29

Vss G30

Vss H2

Vss H9

Vss H13

Vss H19

Vss H22

Vss H25

Vss H26

Vss H28

Vss J6

Vss J29

Vss J30

Vss K26

Vss K28

Vss L2

Vss L23

Vss L29

Vss L30

Vss M6

Vss M8

Vss M14

Vss M16

Vss M26

Vss M28

Vss N13

Vss N14

Vss N15

Vss N16

Vss N17

Vss N18

Vss N23

Vss N29

Vss N30

Vss P2

Vss P6

Vss P12

Vss P13

Vss P14

Table 6-1. Intel® ICH9

Ballout by Signal Nam e

(Desktop Only)

Ball Name Ball #

Vss P15

Vss P16

Vss P17

Vss P18

Vss P19

Vss P26

Vss P28

Vss R8

Vss R13

Vss R14

Vss R15

Vss R16

Vss R17

Vss R18

Vss R23

Vss R29

Vss R30

Vss T2

Vss T5

Vss T12

Vss T13

Vss T14

Vss T15

Vss T16

Vss T17

Vss T18

Vss T19

Vss T29

Vss U13

Vss U14

Vss U15

Vss U16

Vss U17

Vss U18

Vss U23

Vss V3

Vss V7

Vss V13

Vss V14

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

Vss V15

Vss V16

Vss V17

Vss V18

Vss V26

Vss V28

Vss W1

Vss W5

Vss W6

Vss W14

Vss W16

Vss W23

Vss W29

Vss W30

Vss Y3

Vss Y7

Vss Y26

Vss Y28

WAKE# E20

Table 6-1. Intel® ICH9

Ballout by Signal Name

(Desktop Only)

Ball Name Ball #

Ballout Definition

272 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

6.2 Intel® 82801IBM ICH9M and 82801IEM ICH9M-E

Ballout (Mobile Only)

This section contains the 82801IBM ICH9M and 82801IEM ICH9M-E ballout. Figure 6-3

and Figure 6-4 show the ballout from the top of the package view . Table 6-2 is the BGA

ball list, sorted alphabetically by signal name.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 273

Ballout Definition

Figure 6-3. Intel® ICH9M and ICH9M-E Ballout (Top View–Left Side) (Mobile Only)

1234567 8 9101112131415

A VSS VSS AD14 STOP# C/BE3# V5REF GNT1# /

GPIO51 GPIO57 /

CLGPIO5 GPIO27 VccLAN1_0

5VccLAN1_

05 VccLAN3_

3SMBDATA STP_PCI# Vcc1_05 A

B VSS VSS AD19 C/BE1# VSS REQ1# /

GPIO50 AD7 VSS Vcc3_3 GPIO56 VSS VccLAN3_

3BATLOW# VSS Vcc1_05 B

C AD24 PLOCK# AD21 PIRQD# AD9 DEVSEL# AD8 AD1 AD5 S4_STATE#

/ GPIO26

GPIO14 /

AC_PRESE

LAN_PHY_

PWR_CTRL

/ GPIO12

LAN_RSTS

YNC PLTRST# Vcc1_05 C

D AD27 AD15 IRDY# PCICLK AD17 C/BE2# FRAME# C/BE0# AD2 AD18 AD0 LAN_TXD1 LAN_TXD0 LAN_RXD2 Vcc1_05 D

E PIRQB# VSS PAR PERR# VSS REQ3# /

GPIO54 AD13 VSS AD4 AD6 VSS AD3 LAN_TXD2 VSS Vcc1_05 E

FREQ0#

PIRQG# /

GPIO4 AD22 AD23 TRDY# GNT3# /

GPIO55 AD20 AD11 Vcc3_3 AD16 AD12 GNT2# /

GPIO53 REQ2# /

GPIO52 LAN_RXD0 Vcc1_05 F

GAD30

PIRQH# /

GPIO5 Vcc3_3 GNT0# AD28 Vcc3_3 AD25 VSS Vcc1_5_A Vcc1_5_A AD10 VSS LAN_RXD1 VSS G

HCLK14 VSS AD31

PIRQE# /

GPIO2 VSS AD29 AD26 H

JLDRQ1#

/ GPIO23 Vcc3_3 LDRQ0# SERR# PIRQA# PIRQC# Vcc3_3 J

KGPIO18

FWH3 /

LAD3 FWH4 /

LFRAME# FWH1 /

LAD1 FWH0 /

LAD0 PIRQF# /

GPIO3 Vcc3_3 K

LSATACLK

REQ# /

GPIO35 VSS RCIN# CLKRUN# VSS FWH2 /

LAD2 VSS Vcc1_05 Vcc1_05 VSS Vcc1_05 VSS L

MOC4# /

GPIO43 DPRSLPVR

/ GPIO16 OC7# /

GPIO31 OC6# /

GPIO30 SERIRQ PMSYNC#

/ GPIO0 SPKR Vcc1_05 VSS VSS VSS VSS M

NOC9# /

GPIO45 OC5# /

GPIO29 OC8# /

GPIO44 OC0# /

GPIO59 OC1# /

GPIO40 OC2# /

GPIO41 A20GATE VSS VSS VSS VSS VSS N

PSUSCLK VSS OC11# /

GPIO47 VSS OC10# /

GPIO46 OC3# /

GPIO42 VSS Vcc1_05 VSS VSS VSS VSS P

R PCIRST# PME# PWRBTN# SUS_STAT

# / LPCPD CK_PWRG

DCLPWROK VSS VSS VSS VSS VSS R

TVccSus3

_3 VccSus3_3 VccSus3_3 VccSus3_3 VccSus3_3 VccSus3_3 VccSus3_3 Vcc1_05 VSS VSS VSS VSS T

U USBP11N USBP11P VSS USBP10P USBP10N VccSus3_3 VccSus3_3 Vcc1_05 VSS VSS VSS VSS U

V VSS USBP9N USBP9P VSS VSS VccSus3_3 VccSus3_3 Vcc1_05 Vcc1_05 VSS Vcc1_05 VSS V

W USBP8N USBP8P VSS USBP6P USBP6N VccSus3_3 VccSus3_3 W

Y VSS USBP7P USBP7N VSS VSS VccSus3_3 VccSus3_3 Y

AA USBP5N USBP5P VSS USBP3P USBP3N VSS Vcc1_5_A AA

AB VSS USBP4N USBP4P VSS VSS Vcc1_5_A Vcc1_5_A AB

AC USBP2N USBP2P VSS USBP0P USBP0N Vcc1_5_A Vcc1_5_A VccSus1_0

5Vcc1_5_A Vcc3_3 Vcc1_5_A Vcc1_5_A Vcc1_5_A Vcc1_5_A AC

AD VSS USBP1P USBP1N VSS VSS VSS VSS VccSus1_5 VSS VSS Vcc1_5_A VSS VSS VSS Vcc1_5_A AD

AE V5REF_S

us VSS VSS VSS HDA_SDIN

3VSS HDA_RST# HDA_DOCK

_RST# /

GPIO34 VSS SATA5TXN Vcc1_5_A VSS VSS VSS Vcc1_5_A AE

AF VccSus3

_3 VSS CLK48 HDA_SDIN

0VSS HDA_BIT_

CLK VSS GPIO20 VSS SATA5TXP Vcc1_5_A SATA4TXP VSS SATA1TXP Vcc1_5_A AF

AG USBRBIA

S# USBRBIAS VSS HDA_SDIN

1HDA_SDO

UT VSS HDA_DOC

K_EN# /

GPIO33 SATALED# VSS Vcc1_5_A Vcc1_5_A SATA4TXN VSS SATA1TXN Vcc1_5_A AG

AH VSS VSS HDA_SDIN

2HDA_SYN

CVSS VSS SATARBIAS VSS SATA5RXN Vcc1_5_A SATA4RXN VSS SATA1RXN VSS Vcc1_5_A AH

AJ VSS VSS VccSusHD

AVccHDA VccUSBPL

LVcc3_3 SATARBIAS

#VSS SATA5RXP Vcc1_5_A SATA4RXP VSS SATA1RXP VSS Vcc1_5_A AJ

1234567 8 9101112131415

Ballout Definition

274 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Figure 6-4. Intel® ICH9M and ICH9M-E Ballout (Top View–Right Side) (Mobile Only)

16 17 18 19 20 21 22 23 24 25 26 27 28 29

AGPIO24 /

MEM_LED SMBALERT#

/ GPIO11 VccSus3_3 CL_VREF1 TP11 GPIO8 LAN100_SL

PVccRTC VccCL3_3 RTCRST# VccGLAN3_

3VccGLANPL

LVSS VSS A

B SLP_M# VSS SMLINK1 CL_CLK1 VSS TP3 INTVRMEN VSS VccCL3_3 VSS VSS GLAN_COM

PO GLAN_COM

PI VSS B

C SLP_S3# SMLINK0 GPIO10 /

SUS_PWR_

ACK CL_DATA1 GPIO9 /

WOL_EN

ENERGY_D

ETECT /

GPIO13

INTRUDER

#RTCX1 RTCX2 CL_VREF0 VSS VSS PERp6 /

GLAN_RXP PERn6 /

GLAN_RXN C

D VccSus3_3 VccSus3_3 CL_RST1# GPIO28 LAN_RST# VRMPWRG

DRSMRST# SPI_CLK SPI_CS0# SPI_MOSI PETp6 /

GLAN_TXP PETn6 /

GLAN_TXN VccGLAN1_

5VccGLAN1_

E SLP_S4# LINKALERT#

/ GPIO60 /

CLGPIO4 VSS STP_CPU# WAKE# VSS VccSus3_3 SPI_MISO VSS GLAN_CLK VccGLAN1_

5VccGLAN1_

5PERp5 PERn5 E

F VSS VccSus1_05 VccSus1_5 RI# SRTCRST# CL_RST0# CL_DATA0 SPI_CS1# CL_CLK0 Vcc1_5_B PETp5 PETn5 VSS VSS F

G SMBCLK SLP_S5# VSS SYS_RESET

#PWROK VSS VccCL1_05 VccCL1_5 VSS Vcc1_5_B VSS VSS PERp4 PERn4 G

HVSS Vcc1_5_B Vcc1_5_B PETp4 PETn4 VSS VSS H

JVSS Vcc1_5_B Vcc1_5_B VSS VSS PERp3 PERn3 J

KVcc1_5_B Vcc1_5_B Vcc1_5_B PETp3 PETn3 VSS VSS K

L Vcc1_05 Vcc1_05 Vcc1_05 Vcc1_5_B Vcc1_5_B Vcc1_5_B VSS VSS PERp2 PERn2 L

M VSS VSS Vcc1_05 VSS Vcc1_5_B Vcc1_5_B PETp2 PETn2 VSS VSS M

N VSS VSS VSS Vcc1_5_B Vcc1_5_B Vcc1_5_B VSS VSS PERp1 PERn1 N

P VSS VSS Vcc1_05 VSS Vcc1_5_B Vcc1_5_B PETp1 PETn1 VSS VSS P

R VSS VSS VSS Vcc1_5_B Vcc1_5_B Vcc1_5_B Vcc1_5_B VSS VccDMIPLL R

T VSS VSS Vcc1_05 VSS Vcc1_5_B DMI_CLKP DMI_CLKN Vcc1_5_B Vcc1_5_B Vcc1_5_B T

U VSS VSS Vcc1_05 Vcc1_5_B Vcc1_5_B Vcc1_5_B VSS VSS DMI0TXP DMI0TXN U

V Vcc1_05 Vcc1_05 Vcc1_05 VSS Vcc1_5_B Vcc1_5_B DMI0RXP DMI0RXN VSS VSS V

WVccDMI Vcc1_5_B Vcc1_5_B VSS VSS DMI1TXP DMI1TXN W

YVccDMI Vcc1_5_B Vcc1_5_B DMI1RXP DMI1RXN VSS VSS Y

AA VSS Vcc1_5_B Vcc1_5_B VSS VSS DMI2TXP DMI2TXN AA

AB V_CPU_IO Vcc1_5_B Vcc1_5_B DMI2RXP DMI2RXN VSS VSS AB

AC Vcc1_5_A VSS Vcc1_5_A Vcc1_5_A Vcc3_3 Vcc1_5_A VSS V_CPU_IO Vcc1_5_B Vcc1_5_B VSS VSS DMI3TXP DMI3TXN AC

AD Vcc1_5_A VSS VSS Vcc3_3 SA T A5GP /

GPIO37 VSS CPUPWRGD VSS Vcc1_5_B Vcc1_5_B DMI3RXP DMI3RXN VSS VSS AD

AE VSS VSS GPIO17 SLOAD /

GPIO38 VSS SAT A4GP /

GPIO36 INIT# DPSLP# VSS Vcc1_5_B Vcc1_5_B Vcc1_5_B Vcc1_5_B Vcc1_5_B AE

AF VSS SATA0TXN VSS SA T A1GP /

GPIO19 Vcc3_3 SDATAOUT

1 / GPIO48 VSS NMI SMI# IGNNE# VSS VSS DMI_IRCO

MP DMI_ZCOM

PAF

AG VSS SATA0TXP VSS GPIO1 VSS GPIO7 SDATAOUT

0 / GPIO39 VSS Vcc3_3 INTR THRMTRIP

#TP12 VSS Vcc3_3 AG

AH SATA0RXP VSS SATA_CLKN VSS TP8 GPIO6 VSS SA T A0GP /

GPIO21 GPIO49 VSS VSS STPCLK# VSS VSS AH

AJ SATA0RXN VSS SATA_CLKP VccSATAPL

LTP9 TP10 SCLOCK /

GPIO22 THRM# MCH_SYNC# DPRSTP# FERR# A20M# VSS VSS AJ

16 17 18 19 20 21 22 23 24 25 26 27 28 29

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 275

Ballout Definition

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

A20GATE N7

A20M# AJ27

AD0 D11

AD1 C8

AD2 D9

AD3 E12

AD4 E9

AD5 C9

AD6 E10

AD7 B7

AD8 C7

AD9 C5

AD10 G11

AD11 F8

AD12 F11

AD13 E7

AD14 A3

AD15 D2

AD16 F10

AD17 D5

AD18 D10

AD19 B3

AD20 F7

AD21 C3

AD22 F3

AD23 F4

AD24 C1

AD25 G7

AD26 H7

AD27 D1

AD28 G5

AD29 H6

AD30 G1

AD31 H3

BATLOW# B13

C/BE0# D8

C/BE1# B4

C/BE2# D6

C/BE3# A5

CK_PWRGD R5

CL_CLK0 F24

CL_CLK1 B19

CL_DATA0 F22

CL_DATA1 C19

CL_RST0# F21

CL_RST1# D18

CL_VREF0 C25

CL_VREF1 A19

CLK14 H1

CLK48 AF3

CLKRUN# L4

CLPWROK R6

CPUPWRGD AD22

DEVSEL# C6

DMI_CLKN T26

DMI_CLKP T25

DMI_IRCOMP AF28

DMI_ZCOMP AF29

DMI0RXN V27

DMI0RXP V26

DMI0TXN U29

DMI0TXP U28

DMI1RXN Y27

DMI1RXP Y26

DMITXN W29

DMI1TXP W28

DMI2RXN AB27

DMI2RXP AB26

DMI2TXN AA29

DMI2TXP AA28

DMI3RXN AD27

DMI3RXP AD26

DMI3TXN AC29

DMI3TXP AC28

DPRSLPVR /

GPIO16 M2

DPRSTP# AJ25

DPSLP# AE23

FERR# AJ26

FRAME# D7

FWH0 / LAD0 K5

FWH1 / LAD1 K4

FWH2 / LAD2 L6

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

FWH3 / LAD3 K2

FWH4 / LFRAME# K3

GLAN_CLK E25

GLAN_COMPI B28

GLAN_COMPO B27

GNT0# G4

GNT1# / GPIO51 A7

GNT2# / GPIO53 F12

GNT3# / GPIO55 F6

GPIO1 AG19

GPIO6 AH21

GPIO7 AG21

GPIO8 A21

GPIO9 / WOL_EN C20

GPIO10 /

SUS_PWR_ACK C18

GPIO12 C12

GPIO13 C21

GPIO14 /

AC_PRESENT C11

GPIO17 AE18

GPIO18 K1

GPIO20 AF8

GPIO24 / MEM_LED A16

GPIO27 A9

GPIO28 D19

GPIO49 AH24

GPIO56 B10

GPIO57 / CLGPIO5 A8

HDA_BIT_CLK AF6

HDA_DOCK_EN# /

GPIO33 AG7

HDA_DOCK_RST# /

GPIO34 AE8

HDA_RST# AE7

HDA_SDIN0 AF4

HDA_SDIN1 AG4

HDA_SDIN2 AH3

HDA_SDIN3 AE5

HDA_SDOUT AG5

HDA_SYNC AH4

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

276 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Ballout Definition

IGNNE# AF25

INIT# AE22

INTR AG25

INTRUDER# C22

INTVRMEN B22

IRDY# D3

LAN_RST# D20

LAN_RSTSYNC C13

LAN_RXD0 F14

LAN_RXD1 G13

LAN_RXD2 D14

LAN_TXD0 D13

LAN_TXD1 D12

LAN_TXD2 E13

LAN100_SLP A22

LDRQ0# J3

LDRQ1# / GPIO23 J1

LINKALERT# /

GPIO60 / CLGPIO4 E17

MCH_SYNC# AJ24

NMI AF23

OC0# / GPIO59 N4

OC1# / GPIO40 N5

OC2# / GPIO41 N6

OC3# / GPIO42 P6

OC4# / GPIO43 M1

OC5# / GPIO29 N2

OC6# / GPIO30 M4

OC7# / GPIO31 M3

OC8# / GPIO44 N3

OC9# / GPIO45 N1

OC10# / GPIO46 P5

OC11# / GPIO47 P3

PAR E3

PCICLK D4

PCIRST# R1

PERn1 N29

PERn2 L29

PERn3 J29

PERn4 G29

PERn5 E29

PERn6 / GLAN_RXN C29

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

PERp1 N28

PERp2 L28

PERp3 J28

PERp4 G28

PERp5 E28

PERp6 / GLAN_RXP C28

PERR# E4

PETn1 P27

PETn2 M27

PETn3 K27

PETn4 H27

PETn5 F27

PETn6 / GLAN_TXN D27

PETp1 P26

PETp2 M26

PETp3 K26

PETp4 H26

PETp5 F26

PETp6 / GLAN_TXP D26

PIRQA# J5

PIRQB# E1

PIRQC# J6

PIRQD# C4

PIRQE# / GPIO2 H4

PIRQF# / GPIO3 K6

PIRQG# / GPIO4 F2

PIRQH# / GPIO5 G2

PLOCK# C2

PLTRST# C14

PME# R2

PMSYNC# / GPIO0 M6

PWRBTN# R3

PWROK G20

RCIN# L3

REQ0# F1

REQ1# / GPIO50 B6

REQ2# / GPIO52 F13

REQ3# / GPIO54 E6

RI# F19

RSMRST# D22

RTCRST# A25

RTCX1 C23

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

RTCX2 C24

S4_STATE# /

GPIO26 C10

SATA_CLKN AH18

SATA_CLKP AJ18

SATA 0GP / GPIO21 AH23

SATA0RXN AJ16

SATA0RXP AH16

SATA0TXN AF17

SATA0TXP AG17

SATA1GP / GPIO19 AF 19

SATA1RXN AH13

SATA1RXP AJ13

SATA1TXN AG14

SATA1TXP AF14

SATA4GP / GPIO36 AE21

SATA4RXN AH11

SATA4RXP AJ11

SATA4TXN AG12

SATA4TXP AF12

SATA5GP / GPIO37 AD20

SATA5RXN AH9

SATA5RXP AJ9

SATA5TXN AE10

SATA5TXP AF10

SATA CLKREQ# /

GPIO35 L1

SATALED# AG8

SATARBIAS AH7

SATARBIAS# AJ7

SCLOCK / GPIO22 AJ22

SDATAOUT0 /

GPIO39 AG22

SDATAOUT1 /

GPIO48 AF21

SERIRQ M5

SERR# J4

SLOAD / GPIO38 AE19

SLP_M# B16

SLP_S3# C16

SLP_S4# E16

SLP_S5# G17

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 277

Ballout Definition

SMBALERT# /

GPIO11 A17

SMBCLK G16

SMBDATA A13

SMI# AF24

SMLINK0 C17

SMLINK1 B18

SPI_CLK D23

SPI_CS0# D24

SPI_CS1# F23

SPI_MISO E23

SPI_MOSI D25

SPKR M7

SRTCRST# F20

STOP# A4

STP_CPU# E19

STP_PCI# A14

STPCLK# AH27

SUS_STAT# /

LPCPD R4

SUSCLK P1

SYS_RESET# G19

THRM# AJ23

THRMTRIP# AG26

TP3 B21

TP8 AH20

TP9 AJ20

TP10 AJ21

TP11 A20

TP12 AG27

TRDY# F5

USBP0N AC5

USBP0P AC4

USBP1N AD3

USBP1P AD2

USBP2N AC1

USBP2P AC2

USBP3N AA5

USBP3P AA4

USBP4N AB2

USBP4P AB3

USBP5N AA1

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

USBP5P AA2

USBP6N W5

USBP6P W4

USBP7N Y3

USBP7P Y2

USBP8N W1

USBP8P W2

USBP9N V2

USBP9P V3

USBP10N U5

USBP10P U4

USBP11N U1

USBP11P U2

USBRBIAS AG2

USBRBIAS# AG1

V_CPU_IO AB23

V_CPU_IO AC23

V5REF A6

V5REF_Sus AE1

Vcc1_05 A15

Vcc1_05 B15

Vcc1_05 C15

Vcc1_05 D15

Vcc1_05 E15

Vcc1_05 F15

Vcc1_05 L11

Vcc1_05 L12

Vcc1_05 L14

Vcc1_05 L16

Vcc1_05 L17

Vcc1_05 L18

Vcc1_05 M11

Vcc1_05 M18

Vcc1_05 P11

Vcc1_05 P18

Vcc1_05 T11

Vcc1_05 T18

Vcc1_05 U11

Vcc1_05 U18

Vcc1_05 V11

Vcc1_05 V12

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

Vcc1_05 V14

Vcc1_05 V16

Vcc1_05 V17

Vcc1_05 V18

Vcc1_5_A AA7

Vcc1_5_A AB6

Vcc1_5_A AB7

Vcc1_5_A AC11

Vcc1_5_A AC12

Vcc1_5_A AC13

Vcc1_5_A AC14

Vcc1_5_A AC16

Vcc1_5_A AC18

Vcc1_5_A AC19

Vcc1_5_A AC21

Vcc1_5_A AC6

Vcc1_5_A AC7

Vcc1_5_A AC9

Vcc1_5_A AD11

Vcc1_5_A AD15

Vcc1_5_A AD16

Vcc1_5_A AE11

Vcc1_5_A AE15

Vcc1_5_A AF11

Vcc1_5_A AF15

Vcc1_5_A AG10

Vcc1_5_A AG11

Vcc1_5_A AG15

Vcc1_5_A AH10

Vcc1_5_A AH15

Vcc1_5_A AJ10

Vcc1_5_A AJ15

Vcc1_5_A G10

Vcc1_5_A G9

Vcc1_5_B AA24

Vcc1_5_B AA25

Vcc1_5_B AB24

Vcc1_5_B AB25

Vcc1_5_B AC24

Vcc1_5_B AC25

Vcc1_5_B AD24

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

278 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Ballout Definition

Vcc1_5_B AD25

Vcc1_5_B AE25

Vcc1_5_B AE26

Vcc1_5_B AE27

Vcc1_5_B AE28

Vcc1_5_B AE29

Vcc1_5_B F25

Vcc1_5_B G25

Vcc1_5_B H24

Vcc1_5_B H25

Vcc1_5_B J24

Vcc1_5_B J25

Vcc1_5_B K23

Vcc1_5_B K24

Vcc1_5_B K25

Vcc1_5_B L23

Vcc1_5_B L24

Vcc1_5_B L25

Vcc1_5_B M24

Vcc1_5_B M25

Vcc1_5_B N23

Vcc1_5_B N24

Vcc1_5_B N25

Vcc1_5_B P24

Vcc1_5_B P25

Vcc1_5_B R24

Vcc1_5_B R25

Vcc1_5_B R26

Vcc1_5_B R27

Vcc1_5_B T24

Vcc1_5_B T27

Vcc1_5_B T28

Vcc1_5_B T29

Vcc1_5_B U23

Vcc1_5_B U24

Vcc1_5_B U25

Vcc1_5_B V24

Vcc1_5_B V25

Vcc1_5_B W24

Vcc1_5_B W25

Vcc1_5_B Y24

Vcc1_5_B Y25

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

Vcc3_3 AC10

Vcc3_3 AC20

Vcc3_3 AD19

Vcc3_3 AF20

Vcc3_3 AG24

Vcc3_3 AG29

Vcc3_3 AJ6

Vcc3_3 B9

Vcc3_3 F9

Vcc3_3 G3

Vcc3_3 G6

Vcc3_3 J2

Vcc3_3 J7

Vcc3_3 K7

VccCL1_05 G22

VccCL1_5 G23

VccCL3_3 A24

VccCL3_3 B24

VccDMI W23

VccDMI Y23

VccDMIPLL R29

VccGLAN1_5 D28

VccGLAN1_5 D29

VccGLAN1_5 E26

VccGLAN1_5 E27

VccGLAN3_3 A26

VccGLANPLL A27

VccHDA AJ4

VccLAN1_05 A10

VccLAN1_05 A11

VccLAN3_3 A12

VccLAN3_3 B12

VccRTC A23

VccSATAPLL AJ19

VccSus1_05 AC8

VccSus1_05 F17

VccSus1_5 AD8

VccSus1_5 F18

VccSus3_3 A18

VccSus3_3 AF1

VccSus3_3 D16

VccSus3_3 D17

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

VccSus3_3 E22

VccSus3_3 T1

VccSus3_3 T2

VccSus3_3 T3

VccSus3_3 T4

VccSus3_3 T5

VccSus3_3 T6

VccSus3_3 T7

VccSus3_3 U6

VccSus3_3 U7

VccSus3_3 V6

VccSus3_3 V7

VccSus3_3 W6

VccSus3_3 W7

VccSus3_3 Y6

VccSus3_3 Y7

VccSusHDA AJ3

VccUSBPLL AJ5

VRMPWRGD D21

Vss AA3

Vss AA6

Vss AA23

Vss AA26

Vss AA27

Vss AB1

Vss AB4

Vss AB5

Vss AB28

Vss AB29

Vss AC3

Vss AC17

Vss AC22

Vss AC26

Vss AC27

Vss AD1

Vss AD4

Vss AD5

Vss AD6

Vss AD7

Vss AD9

Vss AD10

Vss AD12

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 279

Ballout Definition

Vss AD13

Vss AD14

Vss AD17

Vss AD18

Vss AD21

Vss AD23

Vss AD28

Vss AD29

Vss AE2

Vss AE3

Vss AE4

Vss AE6

Vss AE9

Vss AE12

Vss AE13

Vss AE14

Vss AE16

Vss AE17

Vss AE20

Vss AE24

Vss AF2

Vss AF5

Vss AF7

Vss AF9

Vss AF13

Vss AF16

Vss AF18

Vss AF22

Vss AF26

Vss AF27

Vss AG3

Vss AG6

Vss AG9

Vss AG13

Vss AG16

Vss AG18

Vss AG20

Vss AG23

Vss AG28

Vss AH1

Vss AH2

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

Vss AH5

Vss AH6

Vss AH8

Vss AH12

Vss AH14

Vss AH17

Vss AH19

Vss AH22

Vss AH25

Vss AH26

Vss AH28

Vss AH29

Vss AJ1

Vss AJ2

Vss AJ8

Vss AJ12

Vss AJ14

Vss AJ17

Vss AJ28

Vss AJ29

Vss A1

Vss A2

Vss A28

Vss A29

Vss B1

Vss B2

Vss B5

Vss B8

Vss B11

Vss B14

Vss B17

Vss B20

Vss B23

Vss B25

Vss B26

Vss B29

Vss C26

Vss C27

Vss E2

Vss E5

Vss E8

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

Vss E11

Vss E14

Vss E18

Vss E21

Vss E24

Vss F16

Vss F28

Vss F29

Vss G8

Vss G12

Vss G14

Vss G18

Vss G21

Vss G24

Vss G26

Vss G27

Vss H2

Vss H5

Vss H23

Vss H28

Vss H29

Vss J23

Vss J26

Vss J27

Vss K28

Vss K29

Vss L2

Vss L5

Vss L7

Vss L13

Vss L15

Vss L26

Vss L27

Vss M12

Vss M13

Vss M14

Vss M15

Vss M16

Vss M17

Vss M23

Vss M28

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

280 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Ballout Definition

Vss M29

Vss N11

Vss N12

Vss N13

Vss N14

Vss N15

Vss N16

Vss N17

Vss N18

Vss N26

Vss N27

Vss P2

Vss P4

Vss P7

Vss P12

Vss P13

Vss P14

Vss P15

Vss P16

Vss P17

Vss P23

Vss P28

Vss P29

Vss R11

Vss R12

Vss R13

Vss R14

Vss R15

Vss R16

Vss R17

Vss R18

Vss R28

Vss T12

Vss T13

Vss T14

Vss T15

Vss T16

Vss T17

Vss T23

Vss U3

Vss U12

Vss U13

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

Vss U14

Vss U15

Vss U16

Vss U17

Vss U26

Vss U27

Vss V1

Vss V4

Vss V5

Vss V13

Vss V15

Vss V23

Vss V28

Vss V29

Vss W3

Vss W26

Vss W27

Vss Y1

Vss Y4

Vss Y5

Vss Y28

Vss Y29

WAKE# E20

Table 6-2. Intel® ICH9M

and ICH9M-E Ballout by

Signal Name (Mobile

Only)

Ball Name Ball #

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 281

Ballout Definition

6.3 Intel® ICH9M-SFF Ballout (Mobile Only)

This section contains the ICH9 Mobile Small Form Factor (ICH9M-SFF) ballout.

Figure 6-5 and Figure 6-6 show the ballout from the top of the package view . Table 6-3

is BGA ball list, sorted alphabetically by signal name.

Ballout Definition

282 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Figure 6-5. Intel® ICH9M SFF Preliminary Ballout(Top view–Left Side)

12345678910111213

AVSS TRDY# AD12 AD10 C/BE1# STOP# DEVSEL# AD4 REQ1# /

GP50 AD2 AD0 AD5 LAN_TXD2 A

BPAR AD25 AD17 VSS PCICLK AD19 VSS FRAME# AD8 VSS REQ2# /

GP52 AD1 VSS B

CAD27 AD15 IRDY# AD26 PLOCK# GNT3# /

GP55 PIRQD# AD14 C/BE3# GNT2# /

GP53 AD7 AD3 LAN_TXD1 C

DAD28 VSS AD21 PERR# AD20 REQ3# /

GP54 AD16 AD9 AD13 C/BE0# AD18 LAN_RXD1 LAN_TXD0 D

EGNT0# AD29 AD23 AD24 VSS C/BE2# VSS AD11 VSS AD6 VSS GNT1# /

GP51 VSS E

FPIRQA# PIRQC# GPIO4 /

PIRQG# AD22 PIRQB# F

GGPIO3 /

PIRQF# VSS GPIO2 /

PIRQE# REQ0# VSS V5REF Vcc3_3 Vcc1_5_A VSS VccLAN1_05 VccLAN3_3 VSS G

HLDRQ0# AD31 LAD0 GPIO5 /

PIRQH# SERR# Vcc3_3 Vcc3_3 Vcc1_5_A VSS VccLAN1_05 VSS VccLAN3_3 H

JLDRQ1# /

GP23 LFRAME# LAD1 AD30 VSS VccSus3_3 VccSus3_3 VSS VSS VSS VSS VSS J

KCLK14 VSS GPIO18 SPKR LAD2 VccSus3_3 VccSus3_3 VSS VSS VSS VSS VSS K

LRCIN# PMSYNC# /

GPIO0 LAD3 SERIRQ VSS VccSus3_3 VccSus3_3 VSS VSS Vcc1_05 Vcc1_05 Vcc1_05 L

MDPRSLPVR /

GP16 OC7# /

GPIO31 OC6# /

GPIO30 SATACLKRE

Q# / GP35 CLKRUN# /

GP32 VccSus3_3 VccSus3_3 VSS VSS Vcc1_05 VSS VSS M

NOC2# /

GPIO41 VSS A20GATE OC1# /

GPIO40 VSS VccSus3_3 VccSus3_3 VSS VSS Vcc1_05 VSS VSS N

POC4# /

GPIO43 OC5# /

GPIO29 OC8# /

GPIO44 OC0# /

GPIO59 OC3# /

GPIO42 VccSus3_3 VccSus3_3 VSS VSS Vcc1_05 VSS VSS P

ROC9# /

GPIO45 OC11# /

GPIO47 SUSCLK OC10# /

GPIO46 VSS VSS VSS VSS VSS Vcc1_05 Vcc1_05 Vcc1_05 R

TPME# VSS PCIRST# CL_PWROK SUS_STAT#

/LPCPD# VccSus1_05 VSS Vcc1_5_A VSS VSS VSS VSS T

UCK_PWRGD USBP10P USBP10N PWRBTN# VSS V5REF_SUS VCCUSBPLL Vcc1_5_A VSS Vcc1_5_A Vcc1_5_A Vcc1_5_A U

VUSBP8N USBP8P VSS USBP11N USBP11P VccSus1_5 VSS VSS VccSusHDA Vcc1_5_A Vcc1_5_A Vcc1_5_A V

WVSS USBP7N USBP7P VSS VSS VSS VCCSUS3_3 VSS VCC1_5_A VSS Vcc1_5_A Vcc1_5_A W

YUSBP6N USBP6P VSS USBP9P USBP9N Y

AA VSS USBP5P USBP5N VSS HDA_SDIN3 VSS HDA_RST# VSS Vcc3_3 SATA5TXP VSS SATA4TXP VSS AA

AB USBP4P USBP4N VSS USBP3P CLK48 HDA_SDIN0 HDA_SYNC GPIO34 /

HAD_DOCK

_RST# VSS SATA5TXN VSS SATA4TXN VSS AB

AC VSS USBP2N USBP2P VSS USBP3N HDA_SDIN2 HDA_SDOUT GPIO20 SATALED# VSS SATA5RXN VSS SATA1RXP AC

AD USBP0P VSS USBP1N USBP1P USBRBIASN VSS VccHDA GPIO33 /

HDA_DOCK

_EN# VSS SATARBIAS# SATA5RXP SATA4RXN SATA1RXN AD

AE VSS USBP0N VSS VSS USBRBIASP HDA_SDIN1 HDA_BIT_CL

KVSS Vcc3_3 SATARBIAS VSS SATA4RXP VSS AE

12345678910111213

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 283

Ballout Definition

Figure 6-6. Intel® ICH9M-SFF Preliminary Ballout(To p view–Rig ht Side)

14 15 16 17 18 19 20 21 22 23 24 25

ALAN_RXD0 GPIO14 /

AC_PRESENT GPIO57 /

CLGPIO5 CL_VREF1 CL_CLK1 TP11 STPCPU# /

GP25 PLTRST# GPIO24 /

MEM_LED SMBALERT#

/ GP11 SMLINK1 VSS A

BLAN_RXD2 STPPCI# /

GP15 VSS CL_ST1# CL_DATA1 VSS SLP_S4# LINKALER T# /

GPIO60 /

CLGPIO4 VSS SLP_M# VRMPWRGD GPIO8 B

CGPIO12 /

LAN_PHY_PWR

_CTRL SMBDATA BATLOW# CL_RST0# SMBCLK TP3 RI# WAKE# CL_CLK0 INTRUDER# SRTCRST# SYS_RESET# C

DLAN_RSTSYNC GPIO56 /

GBEDOCK# SLP_S5# GPIO27 SLP_S3# RSMRST# GPIO13 GPIO9 /

WOL_EN LAN_RST# PWROK VSS LAN100_SLP D

EGPIO26 /

S4_STATE# VSS GPIO10 /

SUS_PWR_A

CK VSS SMLINK0 VSS GPIO28 VSS CL_DATA0 SPI_CS0# SPI_CLK INTVRMEN E

FCL_VREF0 SPI_MOSI GPIO58 /

SPI_CS1# /

CLGPIO6 VSS RTCX1 F

GVCCSUS3_3 VCCSUS3_3 VSS VccRTC VccCL1_05 VSS VSS GLAN_CLK SPI_MISO RTCRST# RTCX2 G

HVCCSUS3_3 VccSus1_05 VccSus1_5 VccCL1_5 VSS VccGLAN1_5 GLAN_COMPO GLAN_COMPI VSS PERn6/

GLAN_RXn PERp6/

GLAN_RXp H

JVccCL3_3 VSS VSS VccGLANPLL VccGLAN1_5 Vcc1_5_B VSS VSS PETp6/

GLAN_TXp PETn6/

GLAN_TXn VSS J

KVccCL3_3 VSS VccGLAN3_3 VSS Vcc1_5_B Vcc1_5_B PETn5 PETp5 VSS PERn5 PERp5 K

LVcc1_05 Vcc1_05 VSS VSS Vcc1_5_B Vcc1_5_B VSS VSS PETp4 PETn4 VSS L

MVSS Vcc1_05 VSS VSS Vcc1_5_B Vcc1_5_B PETn3 PETp3 VSS PERp4 PERn4 M

NVSS Vcc1_05 VSS VSS Vcc1_5_B Vcc1_5_B VSS VSS PERn3 PERp3 VSS N

PVSS Vcc1_05 VSS VSS Vcc1_5_B VccDMIPLL PETn2 PETp2 VSS PERp2 PERn2 P

RVcc1_05 Vcc1_05 VSS VSS Vcc1_5_B VSS VSS VSS PETp1 PETn1 VSS R

TVSS VSS VSS VccDMI Vcc1_5_B Vcc1_5_B DMI_CLKN DMI_CLKP VSS PERp1 PERn1 T

UVSS Vcc1_5_A V_CPU_IO VccDMI Vcc1_5_B Vcc1_5_B VSS VSS DMI0TXP DMI0TXN VSS U

VVCC3_3 Vcc1_5_A V_CPU_IO VSS Vcc3_3 VSS DMI1TXN DMI1TXP VSS DMI0RXP DMI0RXN V

WVCC3_3 VSS VSS VccSATAPLL Vcc1_5_A VSS VSS VSS DMI1RXN DMI1RXP VSS W

YDMI2TXN DMI2TXP VSS DMI2RXN DMI2RXP Y

AA SATA1TXN VSS VSS VSS GPIO19 /

SATA1GP VSS GPIO37 /

SATA5GP VSS VSS DMI3TXN DMI3TXP VSS AA

AB SATA1TXP VSS SATA_CLKP TP8 GPIO38 /

SLOAD GPIO48 /

SDATAOUT1 MCH_SYNC# DMI_ZCOMP DMI_IRCOMP A20M# DMI3RXN DMI3RXP AB

AC VSS SATA0TXN SATA_CLKN TP9 GPIO39 /

SDATAOUT0 GPIO22 /

SCLOCK GPIO49 SMI# TP11 THRMTRIP# VSS STPCLK# AC

AD SATA0RXP SATA0TXP VSS TP10 GPIO7 VSS THRM# NMI VSS IGNNE# INTR FERR# AD

AE SATA0RXN VSS GPIO1 /

TACH1 GPIO17 GPIO6 GPIO21 /

SATA0GP GPIO 36 /

SATA4GP INIT# CPUPWRGD DPRSTP# DPSLP# VSS AE

14 15 16 17 18 19 20 21 22 23 24 25

284 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Ballout Definition

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

A20GATE N3

A20M# AB23

AD0 A11

AD1 B12

AD10 A4

AD11 E8

AD12 A3

AD13 D9

AD14 C8

AD15 C2

AD16 D7

AD17 B3

AD18 D11

AD19 B6

AD2 A10

AD20 D5

AD21 D3

AD22 F4

AD23 E3

AD24 E4

AD25 B2

AD26 C4

AD27 C1

AD28 D1

AD29 E2

AD3 C12

AD30 J4

AD31 H2

AD4 A8

AD5 A12

AD6 E10

AD7 C11

AD8 B9

AD9 D8

BATLOW# C16

C/BE0# D10

C/BE1# A5

C/BE2# E6

C/BE3# C9

CK_PWRGD U1

CL_CLK0 C22

CL_CLK1 A18

CL_DATA0 E22

CL_DATA1 B18

CL_PWROK T4

CL_RST0# C17

CL_ST1# B17

CL_VREF0 F21

CL_VREF1 A17

CLK14 K1

CLK48 AB5

CLKRUN# / GPIO32 M5

CPUPWRGD AE22

TP11 AC22

DEVSEL# A7

DMI_CLKN T21

DMI_CLKP T22

DMI_IRCOMP AB22

DMI_ZCOMP AB21

DMI0RXN V25

DMI0RXP V24

DMI0TXN U24

DMI0TXP U23

DMI1RXN W23

DMI1RXP W24

DMI1TXN V21

DMI1TXP V22

DMI2RXN Y24

DMI2RXP Y25

DMI2TXN Y21

DMI2TXP Y22

DMI3RXN AB24

DMI3RXP AB25

DMI3TXN AA23

DMI3TXP AA24

DPRSLPVR / GPIO16 M1

DPRSTP# AE23

DPSLP# AE24

FERR# AD25

FRAME# B8

GLAN_CLK G22

GLAN_COMPI H22

GLAN_COMPO H21

GNT0# E1

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

GNT1# / GPIO51 E12

GNT2# / GPIO53 C10

GNT3# / GPIO55 C6

GPIO1 / TACH1 AE16

GPIO10 /

SUS_PWR_ACK E16

GPIO12 /

LAN_PHY_PWR_CTRL C14

GPIO13 D20

GPIO14 /

AC_PRESENT A15

GPIO17 AE17

GPIO18 K3

GPIO19 / SATA1GP AA18

GPIO2 / PIRQE# G3

GPIO20 AC8

GPIO21 / SATA0GP AE19

GPIO22 / SCLOCK AC19

GPIO24 / MEM_LED A22

GPIO26 /

S4_STATE# E14

GPIO27 D17

GPIO28 E20

GPIO3 / PIRQF# G1

GPIO33 /

HDA_DOCK_EN# AD8

GPIO34 /

HDA_DOCK_RST# AB8

GPIO36 / SATA4GP AE20

GPIO37 / SATA5GP AA20

GPIO38 / SLOAD AB18

GPIO39 /

SDATAOUT0 AC18

GPIO4 / PIRQG# F3

GPIO48 /

SDATAOUT1 AB19

GPIO49 AC20

GPIO5 / PIRQH# H4

GPIO56 D15

GPIO57 / CLGPIO5 A16

GPIO6 AE18

GPIO7 AD18

GPIO8 B25

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 285

Ballout Definition

GPIO9 / WOL_EN D21

HDA_BIT_CLK AE7

HDA_RST# AA7

HDA_SDIN0 AB6

HDA_SDIN1 AE6

HDA_SDIN2 AC6

HDA_SDIN3 AA5

HDA_SDOUT AC7

HDA_SYNC AB7

IGNNE# AD23

INIT# AE21

INTR AD24

INTRUDER# C23

INTVRMEN E25

IRDY# C3

LAD0 H3

LAD1 J3

LAD2 K5

LAD3 L3

LAN_RST# D22

LAN_RSTSYNC D14

LAN_RXD0 A14

LAN_RXD1 D12

LAN_RXD2 B14

LAN_TXD0 D13

LAN_TXD1 C13

LAN_TXD2 A13

LAN100_SLP D25

LDRQ0# H1

LDRQ1# / GPIO23 J1

LFRAME# J2

LINKALERT# /

GPIO60 / CLGPIO4 B21

MCH_SYNC# AB20

NMI AD21

OC0# / GPIO59 P4

OC1# / GPIO40 N4

OC10# / GPIO46 R4

OC11# / GPIO47 R2

OC2# / GPIO41 N1

OC3# / GPIO42 P5

OC4# / GPIO43 P1

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

OC5# / GPIO29 P2

OC6# / GPIO30 M3

OC7# / GPIO31 M2

OC8# / GPIO44 P3

OC9# / GPIO45 R1

PAR B1

PCICLK B5

PCIRST# T3

PERn1 T25

PERn2 P25

PERn3 N23

PERn4 M25

PERn5 K24

PERn6/GLAN_RXn H24

PERp1 T24

PERp2 P24

PERp3 N24

PERp4 M24

PERp5 K25

PERp6/GLAN_RXp H25

PERR# D4

PETn1 R24

PETn2 P21

PETn3 M21

PETn4 L24

PETn5 K21

PETn6/GLAN_TXn J24

PETp1 R23

PETp2 P22

PETp3 M22

PETp4 L23

PETp5 K22

PETp6/GLAN_TXp J23

PIRQA# F1

PIRQB# F5

PIRQC# F2

PIRQD# C7

PLOCK# C5

PLTRST# A21

PME# T1

PMSYNC# / GPIO0 L2

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

PWRBTN# U4

PWROK D23

RCIN# L1

REQ0# G4

REQ1# / GPIO50 A9

REQ2# / GPIO52 B11

REQ3# / GPIO54 D6

RI# C20

RSMRST# D19

RTCRST# G24

RTCX1 F25

RTCX2 G25

SATA_CLKN AC16

SATA_CLKP AB16

SATA0RXN AE14

SATA0RXP AD14

SATA0TXN AC15

SATA0TXP AD15

SATA1RXN AD13

SATA1RXP AC13

SATA1TXN AA14

SATA1TXP AB14

SATA4RXN AD12

SATA4RXP AE12

SATA4TXN AB12

SATA4TXP AA12

SATA5RXN AC11

SATA5RXP AD11

SATA5TXN AB10

SATA5TXP AA10

SATACLKREQ# /

GPIO35 M4

SATALED# AC9

SATARBIAS AE10

SATARBIAS# AD10

SERIRQ L4

SERR# H5

SLP_M# B23

SLP_S3# D18

SLP_S4# B20

SLP_S5# D16

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

286 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Ballout Definition

SMBALERT# /

GPIO11 A23

SMBCLK C18

SMBDATA C15

SMI# AC21

SMLINK0 E18

SMLINK1 A24

SPI_CLK E24

SPI_CS0# E23

SPI_CS1# F23

SPI_MISO G23

SPI_MOSI F22

SPKR K4

SRTCRST# C24

STOP# A6

STPCLK# AC25

STPCPU# / GPIO25 A20

STPPCI# / GPIO15 B15

SUS_STAT#/LPCPD# T5

SUSCLK R3

SYS_RESET# C25

THRM# AD20

THRMTRIP# AC23

TP10 AD17

TP11 A19

TP3 C19

TP8 AB17

TP9 AC17

TRDY# A2

USBP0N AE2

USBP0P AD1

USBP10N U3

USBP10P U2

USBP11N V4

USBP11P V5

USBP1N AD3

USBP1P AD4

USBP2N AC2

USBP2P AC3

USBP3N AC5

USBP3P AB4

USBP4N AB2

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

USBP4P AB1

USBP5N AA3

USBP5P AA2

USBP6N Y1

USBP6P Y2

USBP7N W2

USBP7P W3

USBP8N V1

USBP8P V2

USBP9N Y5

USBP9P Y4

USBRBIASN AD5

USBRBIASP AE5

V_CPU_IO U16

V_CPU_IO V16

V5REF G7

V5REF_SUS U7

Vcc1_05 L11

Vcc1_05 L12

Vcc1_05 L13

Vcc1_05 L14

Vcc1_05 L15

Vcc1_05 M11

Vcc1_05 M15

Vcc1_05 N11

Vcc1_05 N15

Vcc1_05 P11

Vcc1_05 P15

Vcc1_05 R11

Vcc1_05 R12

Vcc1_05 R13

Vcc1_05 R14

Vcc1_05 R15

Vcc1_5_A U13

Vcc1_5_A V13

Vcc1_5_A W13

Vcc1_5_A U12

Vcc1_5_A V12

Vcc1_5_A W12

Vcc1_5_A U15

Vcc1_5_A V15

Vcc1_5_A W18

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

Vcc1_5_A G9

Vcc1_5_A H9

Vcc1_5_A U11

Vcc1_5_A V11

Vcc1_5_A T9

Vcc1_5_A U9

VCC1_5_A W10

Vcc1_5_B J19

Vcc1_5_B K18

Vcc1_5_B K19

Vcc1_5_B L18

Vcc1_5_B L19

Vcc1_5_B M18

Vcc1_5_B M19

Vcc1_5_B N18

Vcc1_5_B N19

Vcc1_5_B P18

Vcc1_5_B R18

Vcc1_5_B T18

Vcc1_5_B T19

Vcc1_5_B U18

Vcc1_5_B U19

Vcc3_3 V18

Vcc3_3 AE9

Vcc3_3 AA9

Vcc3_3 G8

Vcc3_3 H7

Vcc3_3 H8

VCC3_3 V14

VCC3_3 W14

VCCSATAPLL W17

VccCL1_05 G18

VccCL1_5 H17

VccCL3_3 J14

VccCL3_3 K14

VccDMI T17

VccDMI U17

VccDMIPLL P19

VccGLAN1_5 H19

VccGLAN3_3 K16

VccGLANPLL J17

VccHDA AD7

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 287

Ballout Definition

VccGLAN1_5 J18

VccLAN1_05 G11

VccLAN1_05 H11

VccLAN3_3 G12

VccLAN3_3 H13

VccRTC G17

VccSus1_05 T7

VccSus1_05 H15

VccSus1_5 H16

VccSus1_5 V7

VCCSUS3_3 W8

VCCSUS3_3 G14

VCCSUS3_3 G15

VCCSUS3_3 H14

VccSus3_3 J7

VccSus3_3 J8

VccSus3_3 K7

VccSus3_3 K8

VccSus3_3 L7

VccSus3_3 L8

VccSus3_3 M7

VccSus3_3 M8

VccSus3_3 N7

VccSus3_3 N8

VccSus3_3 P7

VccSus3_3 P8

VccSusHDA V10

VCCUSBPLL U8

VRMPWRGD B24

VSS B4

VSS B7

VSS B10

VSS B13

VSS B16

VSS B19

VSS B22

VSS D2

VSS D24

VSS E5

VSS E7

VSS E9

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

VSS E11

VSS E13

VSS E15

VSS E17

VSS E19

VSS E21

VSS F24

VSS G2

VSS G5

VSS G10

VSS G13

VSS G16

VSS G19

VSS G21

VSS H10

VSS H12

VSS H18

VSS H23

VSS J5

VSS J9

VSS J10

VSS J11

VSS J12

VSS J13

VSS J15

VSS J21

VSS J22

VSS J25

VSS K2

VSS K9

VSS K10

VSS K11

VSS K12

VSS K13

VSS K15

VSS K17

VSS K23

VSS L5

VSS L9

VSS L10

VSS L16

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

VSS L17

VSS L21

VSS L22

VSS L25

VSS M9

VSS M10

VSS M12

VSS M13

VSS M14

VSS M16

VSS M17

VSS M23

VSS N2

VSS N5

VSS N9

VSS N10

VSS N12

VSS N13

VSS N14

VSS N16

VSS N17

VSS N21

VSS N22

VSS N25

VSS P9

VSS P10

VSS P12

VSS P13

VSS P14

VSS P16

VSS P17

VSS P23

VSS R5

VSS R7

VSS R8

VSS R9

VSS R10

VSS R16

VSS R17

VSS R19

VSS R21

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

288 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Ballout Definition

§ §

VSS R22

VSS R25

VSS T2

VSS T8

VSS T10

VSS T11

VSS T12

VSS T13

VSS T14

VSS T15

VSS T16

VSS T23

VSS U5

VSS U10

VSS U14

VSS U21

VSS U22

VSS U25

VSS V3

VSS V8

VSS V19

VSS V23

VSS W1

VSS W4

VSS W5

VSS W7

VSS W9

VSS W11

VSS W15

VSS W16

VSS W19

VSS W21

VSS W22

VSS W25

VSS Y3

VSS Y23

VSS AA1

VSS AA4

VSS AA6

VSS AA8

VSS AA11

VSS AA13

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

VSS AA15

VSS AA16

VSS AA17

VSS AA19

VSS AA21

VSS AA22

VSS AA25

VSS AB3

VSS AB9

VSS AB11

VSS AB13

VSS AB15

VSS AC1

VSS AC4

VSS AC10

VSS AC12

VSS AC14

VSS AC24

VSS AD2

VSS AD6

VSS AD9

VSS AD16

VSS AD19

VSS AD22

VSS AE4

VSS AE11

VSS AE13

VSS AE15

VSS AE3

VSS A1

VSS A25

VSS AE1

VSS AE25

VSS V17

VSS AE8

VSS V9

VSS J16

WAKE# C21

Table 6-3. Intel®

ICH9M-SFF Ballout by

Signal Name - (Mobile

Only)

Names Ball

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 289

Package Information

7 Package Information

7.1 Intel® ICH9 Package (Desktop Only)

The ICH9 package information is shown in Figure 7-1, Figure 7-2, and Figure 7-3.

Note: All dimensions, unless otherwise specified, are in millimeters

Figure 7-1. Intel® ICH9 Package (Top View)

TOP VIEW

PIN #1 I.D (SHINY)

1.0 DIA X 0.15 DEPTH

9.0 X 9.0 FROM CENTER LINE

0.127 A//

A0.127

-A-

-B-

22.10 R EF

4 X 45°

Package Information

290 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Figure 7-2. Intel® ICH9 Package (Bottom View)

Figure 7-3. Intel® ICH9 Package (Side View)

SIDE VIEW

-C-

C//

0.20

0.15

SEATING PLANE

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 291

Package Information

7.2 Intel® ICH9 Mobile Package (Mobile Only)

7.2.1 Intel® 82801IBM ICH9M and 82801IEM ICH9M-E Package

The ICH9M package information is shown in Figure 7-4, Figure 7-5, and Figure 7-6.

Note: All dimensions unless otherwise specified are in millimeters

Figure 7-4. Intel® ICH9M Package (Top View)

Package Information

292 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Figure 7-5. Intel® ICH9M Package (Bott o m View)

Figure 7-6. Intel® ICH9M Package (Side View)

SIDE VIEW

-C-

C//

0.20

0.15

SEATING PLANE

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 293

Package Information

7.2.2 Intel® ICH9M-SSF Package

§ §

Figure 7-7. Intel® ICH9M-SSF Package Drawing

Package Information

294 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 295

Electrical Characteristics

8 Electrical Characteristics

This chapter contains the DC and AC characteristics for the ICH9. AC timing diagrams

are included

8.1 Thermal Specifications

Re fer to the Intel® I/O Controller Hub (ICH9) Thermal Design Guidelines document for

ICH9 thermal information.

8.2 Absolute Maximum Ratings

8.3 DC Characteristics

Table 8-1. Intel® ICH9 Absolute Maximum Ratings

Parameter Maximum Limits

Voltage on any 3.3 V Pin with respect to Ground -0.5 to Vcc3_3 + 0.5 V

Voltage on any 5 V Tolerant Pin with respect to Ground (V5REF = 5 V) -0.5 to V5REF + 0.5 V

1.05 V Supply Voltage with respect to VSS -0.5 to 2.1 V

1.25 V Supply Voltage with respect to VSS -0.5V to 2.1V

1.5 V Supply Voltage with respect to VSS -0.5 to 2.1 V

3.3 V Supply Voltage with respect to VSS -0.5 to 4.6 V

5.0 V Supply Voltage with respect to VSS -0.5 to 5.5 V

V_CPU_IO Supply Voltage with respect to VSS -0.5 to 2.1 V

Table 8-2. DC Current Character i stics1 (Desktop Only)

Power Plane Maximum Power Consu m p ti on

Symbol S0 S3 S4/S5 G3

V5REF 2 mA N/A N/A N/A

V5REF_Sus 2 mA 1 mA 1 mA N/A

Vcc3_3 308 mA N/A N/A N/A

VccSus3_3 212 mA 53 mA 53 mA N/A

VccHDA632mA N/A N/A N/A

VccSusHDA632 mA 1 mA 1 mA N/A

VccGLAN3_3 1 mA N/A N/A N/A

VccGLAN1_5 80 mA N/A N/A N/A

VccLAN3_3519 mA 78 mA 78 mA N/A

Electrical Characteristics

296 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. These are estimated DC current numbers.

2. Internal voltage regulators power these wells inside the Intel® ICH9 and current for these

rails are accounted for in the sourcing voltage rail current requirements.

3. Only the G3 state of this rail is shown to provide an estimate of battery l ife.

4. Icc (RTC) data is taken with VccRTC at 3.0 V while the system is in a mechanical off (G3 )

state at room temperature.

5. The current for this rail in S3 and S4/S5 is based on the integrated LAN running at 10/100.

6. The current for this rail was measured with VccHDA and VccSusHDA set to 3.3 V.

7. The current for this rail was measured with VccDMI set to 1.5 V.

VccLAN1_052, 5 Powered by

Vcc1_05 in S0 Powered by

VccLAN3_3 in S3

VccLAN3_3 in S4/

S5 N/A

VccCL3_3 19 mA 73 mA 73 mA N/A

VccCL1_52Powered by

Vcc1_5_A in S0 Powered by

VccCL3_3 in S3 Powered by

VccCL3_3 in S4/S5 N/A

VccCL1_052Powered by

Vcc1_05 in S0 Powered by

VccCL3_3 in S3 Powered by

VccCL3_3 in S4/S5 N/A

Vcc1_5_A 1.644 A N/A N/A N/A

Vcc1_5_B 646 mA N/A N/A N/A

VccSus1_52Powere d by

Vcc1_5_A in S0 Powered by

VccSus3_3 in S3 Powered by

VccSus3_3 in S4/S5 N/A

Vcc1_05 1.634 A N/A N/A N/A

VccSus1_052Powered by

Vcc1_05 in S0 Powered by

VccSus3_3 in S3 Powered by

VccSus3_3 in S4/S5 N/A

VccRTC3, 4 N/A N/A N/A 6 μA

VccDMI750 mA N/A N/A N/A

V_CPU_IO 2 mA N/A N/A N/A

VccGLANPLL 23 mA N/A N/A N/A

VccUSBPLL 11 mA N/A N/A N/A

VccDMIPLL723 mA N/A N/A N/A

VccSATAPLL 47 mA N/A N/A N/A

Table 8-2. DC Curr ent Characteristics1 (Desktop Only)

Power Plane Maximum Power Consumption

Symbol S0 S3 S4/S5 G3

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 297

Electrical Characteristics

NOTES:

1. These are preliminary DC current numbers and are subject to change.

2. Internal voltage regulators power these wells inside the Intel® ICH9 and current for this

rail is accounted for in the sourcing voltage rail current requirements.

3. Only the G3 state of this rail is shown to provide an estimate of battery life.

4. Icc (RTC) data is taken with VccRTC at 3.0 V while the system is in a mechanical off (G3)

state at room temperature.

5. The current for this rail in S3 and S4/S5 is based on the integrated LAN running at 10/100.

6. The current for this rail was measured with VccHDA and VccSusHDA se t to 1.5 V.

7. The current for this rail was measured with VccDMI set to 1.25 V.

Table 8-3. Preliminary DC Current Characteristics (Mobile Only)1

Power Plane Maximum Power Consumption

Symbol S0 S3 S4/S5 G3

V5REF 2 mA N/A N/A N/A

V5REF_Sus 2 mA 1 mA 1 mA N/A

Vcc3_3 308 mA N/A N/A N/A

VccSus3_3 212 mA 53 mA 53 mA N/A

VccHDA611 mA N/A N/A N/A

VccSusHDA611 mA 1 mA 1 mA N/A

VccGLAN3_3 1 mA N/A N/A N/A

VccGLAN1_5 80 mA N/A N/A N/A

VccLAN3_3519 mA 78 mA 78 mA N/A

VccLAN1_052, 5 Powered by

Vcc1_05 in S0 Powered by

VccLAN3_3 in S3 Powered by

VccLAN3_3 in S4/S5 N/A

VccCL3_3 19 mA 73 mA 73 mA N/A

VccCL1_52Powered by

Vcc1_5_A in S0 Powered by

VccCL3_3 in S3 Powered by

VccCL3_3 in S4/S5 N/A

VccCL1_052Powered by

Vcc1_05 in S0 Powered by

VccCL3_3 in S3 Powered by

VccCL3_3 in S4/S5 N/A

Vcc1_5_A 1.342 A N/A N/A N/A

Vcc1_5_B 646 mA N/A N/A N/A

VccSus1_52Powered by

Vcc1_5_A in S0 Powered by

VccSus3_3 in S3 Powered by

VccSus3_3 in S4/S5 N/A

Vcc1_05 1.634 A N/A N/A N/A

VccSus1_052Powered by

Vcc1_05 in S0 Powered by

VccSus3_3 in S3 Powered by

VccSus3_3 in S4/S5 N/A

VccRTC3, 4 N/A N/A N/A 6 μA

VccDMI748 mA N/A N/A N/A

V_CPU_IO 2 mA N/A N/A N/A

VccGLANPLL 23 mA N/A N/A N/A

VccUSBPLL 11 mA N/A N/A N/A

VccDMIPLL723 mA N/A N/A N/A

VccSATAPLL 47 mA N/A N/A N/A

Electrical Characteristics

298 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 8-4. DC Characteristic Input Signal Association (Sheet 1 of 2)

Symbol Associated Signals

VIH1/VIL1

(5V Tolerant)

PCI Signals: AD[31:0], C/BE[3 :0]#, DEVSEL#, F RAME#, IRDY#, PAR,

PERR#, PLOCK#, REQ[3:0]#, SERR#, STOP#, TRDY#

Interrupt Signals: PIRQ[D:A]#, PIRQ[H:E]#

GPIO Signals: GPIO[54, 52, 50, 5:2]

VIH2/VIL2 Gigabit LAN Connect Signals: GLAN_RX[p,n]

VIH3/VIL3

Clock Signals: CLK48

Power Management Signals: MCH_SYNC#, THRM#, VRMPWRGD,

LAN_RST#, CLPWROK

Mobile Only: CLKRUN#

SATA Signals: SATAGP[5:4, 1:0]

Desktop Only: SATAGP[3:2]

Interrupt Signals: SERIRQ

Processor Signals: RCIN#, A20 GATE

USB Signals: OC[11:0]#

GPIO Signals: GPIO[59, 55, 53, 51, 49:36, 35, 31:29, 22:16, 7:6, 1, 0],

Desktop Only: GPIO32

Intel® Quiet Syste m Technology Signals: TACH[3:0]

Strap Signals: GNT[3:0]#,SPKR, SATALED# (Strap purposes only)

VIH4/VIL4

Clock Signals: CLK14, PCICLK

LPC/Firmware Hub Signals: LAD[3:0]/FWH[3:0], LDRQ0#, LDRQ1#

PCI Signals: PME#

SPI Signals: SPI_MISO

GPIO Signals: GPIO[33, 23]

Strap Signals: SPI_MOSI, GNT0# (Strap purposes only)

VIH5/VIL5

SMBus Signals: SMBCLK, SMBDATA, SMBALERT#

System Management Signals: SMLINK[1:0], LINKALERT#,

CLGPIO4 (Digital Office Only)

GPIO Signals: GPIO[60, 11]

VIH6/VIL6 LAN Signals: GLAN_CLK, LAN_RXD[2:0]

VIH7/VIL7 Processor Signals: FERR#, THRMTRIP#

VIMIN8/VIMAX8 PCI Express* Data RX Signals: PER[p,n][6:1]

VIH9/VIL9 Real Time Clock Signals: RTCX1

VIMIN10/VIMAX10 SATA Signals: SATA[3 :0]RX[P,N],

Desktop Only: SATA[5:4]RX[P,N]

VIH11/VIL11

Intel® High Definition Audio Signals: HDA_SDIN[3:0]

Strap Signals: HDA_SDOUT, HDA_SYNC (Strap purposes only)

GPIO Signals: GPIO34

NOTE: See VIL_HDA/VIH_HDA for High Definition Audio Low Voltage M ode

VIH12/VIL12/

Vcross(abs) Clock Signals: DMI_CLKN, DMI_CLKP, SATA_CLKN, SATA_CLKP

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 299

Electrical Characteristics

NOTES:

1. VDI = | USBPx[P] – USBPx[N]

2. Includes VDI range

3. Applies to Low-Speed/High-Speed USB

4. PCI Express mVdiff p-p = 2*|PETp[x] – PETn[x]|

5. GLAN mVdiff p-p = 2* |GLAN_RXp – GLAN_RXn|

6. SATA Vdiff, RX (VIMAX10/MIN10) is measured at the SATA connector on the receiver side (generally,

the motherboard connector), where SATA mVdiff p-p = 2*|SATA[x]RXP – SATA[x]RXN|

7. VccRTC is the voltage applied to the VccRTC well of the ICH9. When the system is in a G3 state, this is

generally supplied by the coin cell battery, but for S5 and greater, this is generally VccSus3_3.

8. CL_Vref = 0.27 (VccCL1_5). CL_VREF0 applies to Desktop configurations. CL_VREF1 applies to

Mobile configurations.

9. Applies to Ultra DMA Modes greater than Ultra DMA Mode 4.

10. This is an AC Characteristic that represents transient values for these signals.

11. Applies to Hogh-Speed USB 2.0.

VIH13/VIL13

Power Management Signals: PWRBTN#, RI#, SYS_RESET#, WAKE#

Mobile Only : BATLOW#

GPIO Signals: GPIO[60, 57:56, 28:26, 24, 14:12, 10:8],

Desktop Only: GPIO[25, 15]

System Management Signals:

Desktop Only: CLGPIO1, CLGPIO2, CLGPIO4 (Digital Office Only)

Mobile Only: AC_PRESENT

VIH14/VIL14

Power Management Signals: PWROK, RSMRST#

System Management Signals: INTRUDER#

Miscellaneous Signals: INTVRMEN, LAN100_SLP, RTCRST#, SRTCRST#

VIH_CL/VIL_CL Controller Link: CL_CLK0, CL_DATA0

Mobile Only: CL_CLK1, CL_DATA1

VIH_CL2/VIL_CL2 GPIO Signals: GPIO58 (Desktop Only)

System Management Signals: CLGPIO6 (Digital Office Only

VDI / VCM / VSE

(5V Tolerant) USB Signals: USBP[11:0][P,N] (Low-speed and Full-speed)

VHSSQ / VHSDSC /

VHSCM

(5V Tolerant) USB Signals: USBP[11:0][P,N] (in High-speed Mode)

VIH_HDA / VIL_HDA

Intel® High Definition Audio Signals: HDA_SDIN[3:0]

Strap Signals: HDA_SDOUT, HDA_SYNC (Strap purposes only)

NOTE: Only applies when running in Low Voltage Mode (1.5 V)

VIH_SST/VIL_SST Intel® Quiet System Technology Signals:

Desktop Only: SST

VIH_PECI/VIL_PECI Intel® Quiet System Technology Signals:

Desktop Only: PECI

Table 8-4. DC Characteristic Input Signal Association (Sheet 2 of 2)

Symbol Associated Si gn al s

Electrical Characteristics

300 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 8-5. DC Input Characteristics (Sheet 1 of 2)

Symbol Parameter Min Max Unit Notes

VIL1 Input Low Voltage –0.5 0.3(3.3 V) V Note 12

VIH1 Input High Voltage 0.5(3.3 V) V5REF + 0.5 V Note 12

VIL2 Minimum Input Voltage 200 — mVdiff

p-p Note 5

VIH2 Maximum Input Voltage — 1350 mVdiff

p-p Note 5

VIL3 Input Low Voltage –0.5 0.8 V

VIH3 Input High Voltage 2.0 3.3 V + 0.5 V Note 12

VIL4 Input Low Voltage –0.5 0.3(3.3 V) V Note 12

VIH4 Input High Voltage 0.5(3.3 V) 3.3 V + 0.5 V Note 12

VIL5 Input Low Voltage –0.5 0.8 V

VIH5 Input High Voltage 2.1 3.3 V + 0.5 V Note 12

VIL6 Input Low Voltage -0.5 0.3(3.3 V) V Note 12

VIH6 Input High Voltage 0.6(3.3 V) 3.3 V + 0.5 V Note 12

VIL7 Input Low Voltage –0.5 0.58(V_CPU_IO) V

VIH7 Input High Voltage 0.73(V_CPU_IO) V_CPU_IO + 0.5 V

VIMIN8 Minimum Input Voltage 175 — mVdiff

p-p Note 4

VIMAX8 Maximum Input Voltage — 1200 mVdiff

p-p Note 4

VIL9 Input Low Voltage –0.5 0 .10 V

VIH9 Input High Voltage 0.40 1.2 V

VIMIN10- Gen1i Minimum Input Voltage - 1.5 Gb/s

internal SATA 325 —mVdiff

p-p 6

VIMAX10-Gen1i Maximum Input Voltage - 1.5 Gb/s

internal SATA —600 mVdiff

p-p 6

VIMIN10-Gen1m Minimum Input Voltage - 1.5 Gb/s

eSATA 240 —mVdiff

p-p 6

VIMAX10-Gen1m Maximum Input Voltage - 1.5 Gb/s

eSATA —600 mVdiff

p-p 6

VIMIN10-Gen2i Minimum Input Voltage - 3.0 Gb/s

internal SATA 275 —mVdiff

p-p 6

VIMAX10-Gen2i Maximum Input Voltage - 3.0 Gb/s

internal SATA —750 mVdiff

p-p 6

VIMIN10-Gen2m Minimum Input Voltage - 3.0 Gb/s

eSATA 240 —mVdiff

p-p 6

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 301

Electrical Characteristics

NOTES:

1. VDI = | USBPx[P] – USBPx[N]

2. Includes VDI range

3. Applies to Low-Speed/Full-Speed USB

4. PCI Express mVdiff p-p = 2*|PETp[x] - PETn[x]|

5. GLAN mVdiff p-p = 2* |GLAN_RXp - GLAN_RXn|

6. SATA Vdiff, RX (VIMAX10/MIN10) is measured at the SATA connector on the receiver side

(generally, the motherboard connector), where SATA mVdiff p-p = 2*|SATA[x]RXP -

SATA[x]RXN|

VIMAX10-Gen2m Maximum Input Voltage - 3.0 Gb/s

eSATA —750 mVdiff

p-p 6

VIL11 Input Low Voltage –0.5 0.35(3.3 V) V Note 12

VIH11 Input High Voltage 0.65(3.3 V) 3.3 V + 0.5 V Note 12

VIL12 Input Low Voltage -0.150 0.150 V

VIH12 Input High Voltage 0.660 0.850 V

VIL13 Input Low Voltage –0.5 0.8 V

VIH13 Input High Voltage 2.0 3.3 V + 0.5 V Note 12

VIL14 Input Low Voltage –0.5 0.78 V

VIH14 Input High Voltage 2.0 VccRTC + 0.5 V Note 7

VIL_CL Input Low Voltage –0.3 (CL_VREF - 0.075) V Note 8

VIH_CL Input High Voltage (CL_VREF + 0.075) 1.2 V Note 8

VIL_CL2 Input Low Voltage –0.5 0.3(VccCL3_3) V

VIH_CL2 Input High Voltage 0.5(VccCL3_3) VccCL3_3 + 0.5 V

Vcross(abs) Absolute Crossing Point 0.250 0.550 V

VDI Differential Input Sensitivity 0.2 — V Note 1,3

VCM Differential Common Mode Range 0.8 2.5 V Note 2,3

VSE Single-Ended Receiver Threshold 0.8 2.0 V Note 3

VHSSQ HS Squelch Detection Threshold 100 150 mV N ote 11

VHSDSC HS Disconnect Detection

Threshold 525 625 mV Note 11

VHSCM HS Data Signaling Common Mode

Voltage Range –50 500 mV Note 11

VIL_HDA Input Low Voltage — 0.4(VccHDA) V

VIH_HDA Input High Voltage 0.6(VccHDA ) — V

VIL_SST Input Low Voltage -0.5 0.4 V

VIH_SST Input High Voltage 1.1 Vcc + 0.5 V

VIL_PECI Input Low Voltage -0.5 0.275(V_CPU_IO) V

VIH_PECI Input High Voltage 0.725(V_CPU_IO) V_CPU_IO + 0.5 V

Table 8-5. DC Input Characteristics (Sheet 2 of 2)

Symbol Parameter Min Max Unit Notes

Electrical Characteristics

302 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

7. VccRTC is the voltage applied to the VccRTC well of the ICH9. When the system is in a G3

state, this is generally supplied by the coin cell battery, but for S5 and greater, this is

generally VccSus3_3.

8. CL_Vref = 0.27 (VccCL1_5). CL_VREF0 applies to Desktop configurations. CL_VREF1 applies to

Mobile configurations.

9. Applies to Ultra DMA Modes greater than Ultra DMA Mode 4

10. This is an AC Characteristic that represents transient values for these signals

11. Applies to Hogh-Speed USB 2.0.

12. 3.3 V refers to VccSus3_3 for signals in the suspend well and to Vcc3_3 for signals in the

core well. See Table 3-2 and Table 3-3 for signal and power well association.

Table 8-6. DC Characteristic Output Signal Association (Sheet 1 of 2)

Symbol Associated Signals

VOH1/VOL1

Processor Signals: A20M#, IGNNE#, INIT#, INTR, NMI, SMI#, STPCLK#,

CPUPWRGD

Mobile Only: DPSLP#

Power Management Signals:

Mobile Only: DPRSTP#

VOH2/VOL2

PCI Signals: AD[31:0], C/BE[3 :0]#, DEVSEL#, F RAME#, IRDY#, PAR,

PERR#, PLOCK#, SERR#(1), STOP#, TRDY#

Intel® High Definition Audio Signals: HDA_RST#, HDA_SDOUT,

HDA_SYNC, HDA_BIT_CLK

NOTE: See VOH_HDA/VOL_HDA for High Definition Audio Low Voltage Mode

GPIO Signals: GPIO33

VOH3/VOL3

SMBus Signals: SMBCLK (1), SMBDATA (1)

System Management Signals: SMLINK[1:0](1), LINKALERT#

GPIO Signals: GPIO[60, 11]

VOH4/VOL4

Power Management Signals: SLP_S3#, SLP_S4#, SLP_S5#, SLP_M#,

SUSCLK, SUS_STAT#/LPCPD#, CK_PWRGD, S4_STATE#

Mobile Only: DPRSLPVR, CLKRUN#, PMSYNC#

SATA Signals: SATACLKREQ #, SATALED#, SLOAD, SDATAOUT[1:0]

GPIO Signals: GPIO[49:48, 39:35, 32:31, 26, 21:18, 16, 7:6, 0],

Desktop Only: GPIO32

Intel® High Definition Audio Signals: HDA_DOCK_EN# (Mobile Only)

Other Signals: SPKR

Interrupt Signals: SERIRQ

VOH5/VOL5 USB Signals: USBP[11:0][P,N] in Low-speed and Full-speed Modes

VOMIN6/VOMAX6 PCI Express* Data TX Signals: PET[p,n][6:1]

VOMIN7/VOMAX7 SATA Signals: SATA[5:4, 1:0]TX[P,N],

Desktop Only: SATA[3:2]TX[P,N]

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 303

Electrical Characteristics

NOTE:

1. These signals a re open drain.

VOH8/VOL8

LPC/Firmware Hub Signals: LAD[3:0]/FWH[3:0], LFRAME#/FWH[4],

Desktop Only: INIT3_3V#

Power Management Signal: PLTRST#

PCI Signals: PCIRST#, GNT[3:0]#, PME#(1)

Interrupt Signals: PIRQ[D:A ], PIRQ[H:E]#(1)

GPIO Signals: GPIO[ 58, 55:50, 34, 23:22, 17, 5:2, 1]

SATA Signals: SCLOCK

System Management Signals: CLGPIO6 (Digital Office Only)

Intel® High Definition Audio Signals: HDA_DOCK_RST# (Mobile Only)

SPI Signals: SPI_CS0#, SPI_MOSI, SPI_CLK

LAN Signals: LAN_RSTSYNC, LAN_TXD[2:0]

VOH9/VOL9

Power Management Signals: STP_CPU#, STP_PCI#

GPIO Signals: GPIO[60, 59, 57:56, 47:40, 31:27, 24, 15:12, 10:8],

Desktop Only: GPIO[25, 15]

System Management Signals: LINKALERT#, WOL_EN, MEM_LED

Digital Office Only (Desktop): CLGPIO1, CLGPIO2, CLGPIO04, CLGPIO5

Mobile Only: SUS_PWR_ACK

Gigabit LAN Signals: LAN_PHY_PWR_CTRL

Controller Link Signals:

Mobile Only: CL_RST1#

VOMIN10/VOMAX10 Gigabit Lan Connect Signals: GLAN_TX[p,n]

VHSOI

VHSOH

VHSOL

VCHIRPJ

VCHIRPK

USB Signals: USBP[11:0][P:N] in High-speed Mode

VOH_HDA/VOL_HDA

Intel® High Definition Audio Signals: HDA_RST#, HDA_SDOUT,

HDA_SYNC

NOTE: Only applies when running in Low Voltage Mode (1.5 V)

VOH_PWM/

VOL_PWM

Intel® Quiet System Technology PWM:

Desktop Only: PWM[2:0](1)

VOH_CL1/VOL_CL1 Link Controller Signals: CL_CLK0, CL_DATA0

Mobile Only: CL_CLK1, CL_DATA1

VOH_CL2/VOL_CL2 Link Controller Signals: CL_RST0#

VOH_CL3/VOL_CL3

SPI Signals: SPI_CS1#

GPIO Signals: GPIO58 (Desktop Only)

System Management Signals: CLGPIO6 (Digital Office Only)

VOH_SST/VOL_SST SST signal:

Desktop Only: SST

VOH_PECI/

VOL_PECI

PECI signal:

Desktop Only: PECI

Table 8-6. DC Characteristic Output Signal Association (Sheet 2 of 2)

Symbol Associated Si gn al s

Electrical Characteristics

304 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 8-7. DC Output Characteristics (Sheet 1 of 2)

Symbol Parameter Min Max Unit IOL / IOH Notes

VOL1 Output Low Voltage — 0.255 V 3 mA Note 4

VOH1 Output High Voltage V_CPU_IO - 0.3 — V -3 mA

VOL2 Output Low Voltage — 0.1(3.3 V) V 1.5 mA Note 7

VOH2 Output High Voltage 0.9(3.3 V) — V -0.5 mA Note 7

VOL3 Output Low Voltage — 0.4 V 4 mA

VOH3 Output High Voltage 3.3 V - 0.5 — V -2 mA Note1

Note 7

VOL4 Output Low Voltage — 0.4 V 6 mA

VOH4 Output High Voltage 3.3 V - 0.5 — V -2 mA Note 7

VOL5 Output Low Voltage — 0.4 V 5 mA

VOH5 Output High Voltage 3.3 V – 0.5 — V -2 mA Note 7

VOMIN6 Minimum Output Voltage 800 — mVdif

fp-p Note 2

VOMAX6 Maximum Output Voltage — 1200 mVdif

fp-p Note 2

VOMIN7-Gen1i,m Minimum Output Voltage 400 — mVdif

fp-p Note 3

VOMAX7-Gen1i,m Maximum Output Voltage — 600 mVdif

fp-p Note 3

VOMIN7-Gen2i,m Minimum Output Voltage 400 — mVdif

fp-p Note 3

VOMAX7-Gen2i,m Maximum Output Voltage — 700 mVdif

fp-p Note 3

VOL8 Output Low Voltage — 0.1(3.3 V) V 1.5 mA Note 7

VOH8 Output High Voltage 0.9(3.3 V) — V -0.5 mA Note 1

Note 7

VOL9 Output Low Voltage — 0.4 V 6 mA

VOH9 Output High Voltage 3.3 V - 0.5 — V -0.5 mA Note 7

VOMIN10 Minimum Output Voltage 750 — mVdif

fp-p Note 6

VOMAX10 Maximum Output Voltage — 1350 mVdif

fp-p Note 6

VHSOI HS Idle Level –10 .0 10.0 mV

VHSOH HS Data Signaling High 360 440 mV

VHSOL HS Data Signaling Low –10.0 10.0 mV

VCHIRPJ Chirp J Level 700 1100 mV

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 305

Electrical Characteristics

NOTES:

1. The SERR#, PIRQ[H:A], S MBDATA, SMBCLK, LINKALERT#, SMLINK[1:0], and PWM[2:0]

signal has an open drain driver and SATALED# has an open collector driver, and the VOH

spec does not apply. This signal must have external pull up resistor.

2. PCI Express mVdiff p-p = 2*|PETp[x] – PETn[x]|

3. SATA Vdiff, tx (VOMIN7/VOMAX7) is measured at the SATA connector on the transmit side

(generally, the motherboard connector), where SATA mVdiff p-p = 2*|SATA[x]TXP –

SATA[x]TXN|

4. Maximum Iol for CPUPWRGD is 12mA for short durations (<500 mS per 1.5 s) and 9 m A

for long durations.

5. For INIT3 _3V only, for low current devices, the following applies: VOL5 Max is 0.15 V at an

IOL5 of 2 mA.

6. GLAN mVdiff p-p = 2*|GLAN_TXp – GLAN_T Xn|

7. 3.3 V refers to VccSus3_3 for signals in the suspend well and to Vcc3_3 for signals in the

core well. See Table 3-2 and Table 3-3 for signal and power well association.

VCHIRPK Chirp K Level –900 –500 mV

VOL_HDA Output Low Voltage — 0.1(VccHDA) V 1.5 mA

VOH_HDA Output High Voltage 0.9(VccHDA) — V -0.5 mA

VOL_PWM Output Low Voltage — 0.4 V 5 mA

VOH_PWM Output Hi gh Voltage — — Note 1

VOL_CL1 Output Low Voltage — 0.15 V 1 mA

VOH_CL1 Output High Voltage 0.485(VccCL1_5) — V

VOL_CL2 Output Low Voltage — 0.1(VccCL1_5) V 1.5 mA

VOH_CL2 Output High Voltage 0.9(VccCL1_5) — V -1.5 mA

VOL_CL3 Output Low Voltage — 0.4 V 6 mA

VOH_CL3 Output High Voltage VccCL3_3 -0.5 — V -0.5 mA

VOL_SST Output Low Voltage — 0.3 V 0.5 mA

VOH_SST Output High Voltage 1.1 — V -6 mA

VOL_PECI Output Low Voltage — 0.25(V_CPU_IO) V 0.5 mA

VOH_PECI Output High Voltage 0.75(V_CPU_IO) — -6 mA

Table 8-7. DC Output Characteristics (Sheet 2 of 2)

Symbol Parameter Min Max Unit IOL / IOH Notes

Electrical Characteristics

306 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 8-8. Other DC Characteristics (Sheet 1 of 2)

Symbol Parameter Min Nom Max Unit Notes

V_CPU_IO Processor I/F 0.945 — 1.3 V 1

V5REF ICH9 Core Well Reference Volt a ge 4.75 5 5.25 V 1

CL_VREF Controller Link Reference Voltage 0.385 0.405 0.425 V 1

Vcc3_3 I/O Buffer Voltage 3.135 3.3 3.465 V 1

Vcc1_5_A,

Vcc1_5_B,

VccUSBPLL,

VccSATAPLL,

VccDMIPLL

VccGLANPLL

Internal Logic and I/O Buffer Voltage 1.425 1.5 1.575 V 1

V5REF_Sus Suspend Well Reference Voltage 4.75 5 5.25 V 1

VccSus3_3 Suspend Well I/O Buffer Voltage 3.135 3.3 3.465 V 1

Vcc1_05 Internal Logic Voltage 0.998 1.05 1.102 V 1

VccHDA High Definition Audio Controller Core

Voltage 3.135 3.3 3.465 V 1

VccHDA (low

voltage 1.5 V ) High Definition Audio Controller Low

Voltage Mode Core Voltage 1.425 1.5 1.575 V 1

Vcc_DMI

(Mobile Only) DMI Buffer Voltage 0.998 1.05 1.102 V

Vcc_DMI

(Desktop Only) DMI Buffer Voltage 1.188 1.25 1.312 V

Vcc_DMI

(ESI Mode Only) DMI Buffer Voltage 1.425 1.5 1.575 V

VccLAN3_3 LAN Controller I/O Buffer Voltage 3.135 3.3 3.465 V 1

VccGLAN1_5 Gigabit Lan Transmitter and Receiver

Voltage 1.425 1.5 1.575 V 1

VccGLAN3_3 Gigabit Lan Internal Logic and I/O

Buffer Voltage 3.135 3.3 3.465 V 1

VccCL3_3 Controller Link Buffer Voltage 3.135 — 3.465 V 1

VccRTC (G3-S0) Battery Voltage 2 — 3.465 V 1

VccSusHDA High Definition Audio Controller

Suspend Voltage 3.135 3.3 3.465 V 1

VccSusHDA (low

voltage) High Definition Audio Controller Low

Voltage Mode Suspend Voltage 1.425 1.5 1.575 V 1

VDI Differential Input Sensitivity 0.2 — — V |(USBPx+,USB

Px–)|

VCM Differential Common Mode Range 0.8 — 2.5 V Includes VDI

VCRS Output Signal Crossover Voltage 1.3 — 2.0 V

VSE Single Ended Rcvr Threshold 0.8 — 2.0 V

ILI1 ATA Input Leakage Current –200 — 200 µA (0 V < VIN <

5V)

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 307

Electrical Characteristics

NOTES:

1. The I/O buffer supply voltage is measured at the ICH package pins. The tolerances shown

in Table 9 -8 are inclusive of all noise from DC up to 20 MHz. In testing, the voltage rails

should be measured with a bandwidth limited oscilloscope that has a rolloff of 3 dB/dec ade

above 20 MHz.

2. Includes CLK14, CLK48, GLAN_CLK and PCICLK

ILI2 PCI_3V Hi-Z State Data Line Leakage –10 — 10 µA (0 V < VIN <

Vcc3_3)

ILI3 PCI_5V Hi-Z State Data Line Leakage –70 — 70 µA Max VIN = 2.7

V Min VIN =

0.5 V

ILI4 Input Leakage Current – Clock signals –100 — +100 µA 2

ILI5 Input Leakage Current – SPI signals -10 — +10 µA

CIN Input Capacitance – All Other — — 12 pF FC = 1 MHz

COUT Output Capacitance — — 12 pF FC = 1 MHz

CI/O I/O Capacitance — — 12 pF FC = 1 MHz

Typical Value

CLXTAL1 6 pF

CLXTAL2 6 pF

Table 8-8. Other DC Characteri stics (Sheet 2 of 2)

Symbol Parameter Min Nom Max Unit Notes

Electrical Characteristics

308 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

8.4 AC Characteristics

Table 8-9. Clock Timings (Sheet 1 of 2)

Sym Parameter Min Max Unit Notes Figure

PCI Clock (PCICLK)

t1 Period 30 33.3 ns 8-1

t2 High Time 12 — ns 8-1

t3 Low Time 12 — ns 8-1

t4 Rise Time — 3 ns 8-1

t5 Fall Time — 3 ns 8-1

14 MHz Clock (CLK14)

t6 Period 67 70 ns 8-1

t7 High Time 20 — ns 8-1

t8 Low Time 20 — ns 8-1

t41 Rising Edge Rate 1.0 4.0 V/ns 5

t42 Falling Edge Rate 1.0 4.0 V/ns 5

48 MHz Clock (CLK48)

fclk48 Operating Frequency 48.000 — MHz 1

t9 Frequency Tolerance — 100 ppm

t10 High Time 7 — ns 8-1

t11 Low Time 7 — ns 8-1

t12 Rise Time — 1.2 ns 8-1

t13 Fall Time — 1.2 ns 8-1

SMBus Clock (SMB CLK )

fsmb Operating Frequency 10 100 KHz

t18 High time 4.0 50 μs28-10

t19 Low time 4.7 — μs8-10

t20 Rise time — 1000 ns 8-10

t21 Fall time — 300 ns 8-10

HDA_BIT_CLK (I ntel® High Definition Audio)

fHDA Operating Frequency 24.0 MHz

Frequency Tolerance — 100 ppm

t26a Input Jitter (refer to Clock Chip

Specification) — 300 ppm

t27a High Time (Measured at 0.75 Vcc) 18.75 22.91 ns 8-1

t28a Low Time (Measured at 0.3 5 Vcc) 18.75 22.91 ns 8-1

SATA Clock (SATA_CLKP, SATA_CLKN) / DMI Clock (DMI_CLKP, DMI_CLKN)

t36 Period 9.997 10.0533 ns

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 309

Electrical Characteristics

NOTES:

1. The CLK48 expects a 40/60% duty cycle.

2. The maximum high time (t18 Max) provide a simple ensured method for devices to detect

bus idle conditions.

3. BITCLK Rise and Fall times are measured from 10%VDD and 90%VDD.

4. SUSCLK duty cycle ca n range from 30 % minimum to 70% maximum.

5. CLK14 edge rates in a system as measured from 0.8 V to 2.0 V.

6. The active frequency can be 5 MHz, 50 MHz or 62.5 MHz depending on the interface speed.

Dynamic changes of the normal operating frequency are not allowed.

7. See CK505 Clock Synthesizer Specification for measurement procedure.

tsatasl Slew rate 2.5 8 V/ns 7

Suspend Clock (SUSCLK)

fsusclk Operating Frequency 32 kHz 4

t39 High Time 10 — μs4

t39a Low Time 10 — μs4

Gigabit Internet Clock (GLAN_CLK)

tglanclk Operating Fequency 5 62.5 MHz 6

tglanhi High Time 6.4 — ns

tglanlo Low Time 6.4 — ns

tglansl Slew rate 1.0 4 V/ns

Intel®Quiet System Technology

fpwm PWM Operating Frequency 10 28,000 Hz

Table 8-9. Clock Timings (Sheet 2 of 2)

Sym Parameter Min Max Unit Notes Figure

Table 8-10. PCI Interface Timing

Sym Parameter Min Max Units Notes Figure

t40 AD[31:0] Valid Dela y 2 11 ns 1 8-2

t41 AD[31:0] Setup Time to PCICLK Rising 7 — ns 8-3

t42 AD[31:0] Hold Time from PCICLK Rising 0 — ns 8-3

t43 C/BE[3:0]#, FRAME#, TRDY#, IRDY#,

STOP#, PAR, PERR#, PLOCK#, DEVSEL#

Valid Delay from P CICLK Rising 211ns 1 8-2

t44

C/BE[3:0]#, FRAME#, TRDY#, IRDY#,

STOP#, PAR, PERR#, PLOCK#, IDSEL,

DEVSEL# Output Enable Delay from

PCICLK Rising

2ns 8-6

t45

C/BE[3:0]#, FRAME#, TRDY#, IRDY#,

STOP#, PERR#, PLOCK#, DEVSEL#,

GNT[A:B]# Float Delay from PCICLK

Rising

228ns 8-4

t46 C/BE[3:0]#, FRAME#, TRDY#, IRDY#,

STOP#, SERR#, PERR#, DEVSEL#, Setup

Time to PCICLK Rising 7ns 8-3

Electrical Characteristics

310 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE:

1. Refer to note 3 of table 4- 4 in Section 4.2.2.2 and not e 2 of table 4-6 in Sec tion 4.2.3.2 of

the PCI Local Bus Specification, Revision 2.3 for measurement details.

t47 C/BE[3:0]#, FRAME#, TRDY#, IRDY#,

STOP#, SERR#, PERR#, DEVSEL#,

REQ[A:B]# Hold Time from PCLKIN Rising 0—ns 8-3

t48 PCIRST# Low Pulse Width 1 ms 8-5

t49 GNT[3:0]# Valid Delay from PCICLK

Rising 212ns

t50 REQ[3:0]# Setup Time to PCICLK Rising 12 — ns

Table 8-10. PCI Interface Timing

Sym Parameter Min Max Units Notes Figure

Table 8-11. Universal Serial Bus Timing

Sym Parameter Min Max Units Notes Fig

Full-speed Source (Note 7)

t100 USBPx+, USBPx- Driver Rise Time 4 20 ns 1, C L = 50

pF 8-7

t101 USBPx+, USBPx- Driver Fall Time 4 20 ns 1, CL = 50

pF 8-7

t102 Source Differential Driver Jitter

- To Next Transition

- For Paired Transitions –3.5

–4 3.5

4ns

ns 2, 3 8-8

t103 Source SE0 interval of EOP 160 175 ns 4 8-9

t104 Source Jitter for Differential

Transition to SE0 Transition –2 5 ns 5

t105 Receiver Data Jitter Tolerance

- T o Next Transition

- For Paired Transitions –18.5

–9 18.5

9ns

ns 38-8

t106 EOP Width: Must accept as EOP 82 — ns 4 8-9

t107 Width of SE0 interval during

differential transition —14 ns

Low-speed Source (Note 8)

t108 USBPx+, USBPx – Driver Rise Time 75 300 ns 1, 6

CL = 50 pF

CL = 350 pF 8-7

t109 USBPx+, USBPx – Driver Fall Time 75 300 ns 1,6

CL = 50 pF

CL = 350 pF 8-7

t110 Source Differential Driver Jitter

To Next Transition

For Paired Transitions –25

–14 25

14 ns

ns 2, 3 8-8

t111 Source SE0 interval of EOP 1.25 1.50 µs 4 8-9

t112 Source Jitter for Differential

Transition to SE0 Transition –40 100 ns 5

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 311

Electrical Characteristics

NOTES:

1. Driver output resistance under steady state drive is spec’d at 28 ohms at minimum and

43 ohms at maximum.

2. Timing difference between the differential data signals.

3. Measured at cros sover point of differential data signals.

4. Measured at 50% swing point of data signals.

5. Measured from last crossover point to 50% swing point of data line at leading edge of EOP.

6. Measured from 10% to 90% of the data signal.

7. Full-speed Data Rate has minimum of 11.97 Mb/s and maximum of 12.03 Mb/s.

8. Low-speed Data Rate has a minimum of 1.48 Mb/s and a maximum of 1.52 Mb/s.

NOTES:

1. 20% – 80% at transmitter

2. 80% – 20% at transmitter

3. As measured from 100 mV differential crosspoints of last and first edges of burst.

4. Operating data period during Out-Of-Band burst transmissions.

t113 Receiver Data Jitter Tolerance

- To Next Transition- For Paired

Transitions –152

–200 152

200 ns

ns 38-8

t114 EOP Width: Must accept as EOP 670 — ns 4 8-9

t115 Width of SE0 interval during

differential transition — 210 ns

Table 8-11. Universal Serial Bus Timing

Sym Parameter Min Max Units Notes Fig

Full-speed Source (Note 7)

Table 8-12. SATA Interface Timings

Sym Parameter Min Max Units Notes Figure

UI Gen I Operating Data Period 666.43 670.23 ps

UI-2 Gen II Operating Data Period

(3Gb/s) 333.21 335.11 ps

t120 Rise Ti me 0.15 0.41 UI 1

t121 Fall Time 0.15 0.41 UI 2

t122 TX differential skew — 20 ps

t123 COMRESET 310.4 329.6 ns 3

t124 COMWAKE transmit spacing 103.5 109.9 ns 3

t125 OOB Operating Data period 646.67 686.67 ns 4

Electrical Characteristics

312 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. A device will timeout when any clock low exceeds this value.

2. t137 is the cumulative time a slave device is allowed to extend the clock cycles in one

message from the init ial st art to s top . If a sla ve device e x ceeds this t ime, it is expect ed to

release both its clock and data lines and reset itself.

3. t138 is the cumulative time a master device is allowed to extend its clock cycles within

each byte of a message as defined from start-to-ack, ack-to-ack or ack-to-stop.

4. t134 has a minimum ti ming for I2C of 0 ns, whil e the minimum ti ming for SMBus is 300 ns.

Table 8-13. SMBus Timing

Sym Parameter Min Max Units Notes Fig

t130 Bus Tr ee Time Between Stop an d Start

Condition 4.7 — µs 8-10

t131 Hold Time after (repeated) Start Condition.

After this period, the first clock is

generated. 4.0 — µs 8-10

t132 Repeated Start Condition Setup Time 4.7 — µs 8-10

t133 Stop Condition Setup Time 4.0 — µs 8-10

t134 Data Hold Time 0 — ns 4 8-10

t135 Data Setup Time 250 — ns 8-10

t136 Device Time Out 25 35 ms 1

t137 Cumulative Clock Low Extend Time (slave

device) —25 ms 28-11

t138 Cumulative Clock Low Extend Time

(master device) —10 ms 38-11

Table 8-14. Intel® High Definition Audio Timing

Sym Parameter Min Max Units Notes Fig

t143 Time duration for which HDA_SDOUT is valid

before HDA_BIT_CLK edge. 7— ns 8-13

t144 Time duration for which HDA_SDOUT is valid

after HDA_BIT_CLK edge. 7— ns 8-13

t145 Setup time f or HDA_SDIN[3:0] at rising edge

of HDA_BIT_CLK 15 — ns 8-13

t146 Hold time for HDA_SDIN[3:0] at rising edge

of HDA_BIT_CLK 0— ns 8-13

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 313

Electrical Characteristics

NOTE:

1. The typical clock frequency driven by the ICH9 is 17.86 MHz.

Table 8-15. LPC Timing

Sym Parameter Min Max Units Notes Fig

t150 LAD[3:0] Valid Delay from PCIC LK Rising 2 11 ns 8-2

t151 LAD[3:0] Output Enable Delay from PCICLK

Rising 2ns 8-6

t152 LAD[3:0] Float Delay from PCICLK Rising — 28 ns 8-4

t153 LAD[3:0] Setup Time to PCICLK Rising 7 — ns 8-3

t154 LAD[3:0] Hold Time from PCICLK Rising 0 — ns 8-3

t155 LDRQ[1:0]# Setup Time to PCICLK Rising 12 — ns 8-3

t156 LDRQ[1:0]# Hold Time from PCICLK Rising 0 — ns 8-3

t157 LFRAME# Valid Delay from PCICLK Rising 2 12 ns 8-2

Table 8-16. Miscellaneous Timings

Sym Parameter Min Max Units Notes Fig

t160 SERIRQ Setup Time to PCICLK Rising 7 — ns 8-3

t161 SERIRQ Hold Time from PCICLK Rising 0 — ns 8-3

t162 RI#, EXTSMI#, GPIO, USB Resume Pulse

Width 2 — RTCCLK 8-5

t163 SPKR Valid Delay from OSC Rising — 200 ns 8-2

t164 SERR# Active to NMI Active — 200 ns

t165 IGNNE# Inactive from FERR# Inactive — 230 ns

Table 8-17. SPI Timings (20 MHz)

Sym Parameter Min Max Units Notes Fig

t180 Serial Clock Frequency - 20MHz Operation 17.2 18.4 MHz 1

t182 SPI Clock Duty cycle at the host 40% 60% 8-12

t183 Tco of SPI_MOSI with respect to serial

clock falling edge at the host -5 13 ns 8-12

t184 Setup of SPI_MISO with respect to serial

clock falling edge at the host 16 — ns 8-12

t185 Hold of SPI_MISO with respect to serial

clock falling edge at the host 0—ns 8-12

t186 Setup of SPI_CS[1:0]# assertion with

respect to serial clock rising at the host 30 — ns 8-12

t187 Hold of SPI_CS[1:0]# deassertion with

respect to serial clock falling at the host 30 — ns 8-12

Electrical Characteristics

314 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE:

1. The typical clock frequency driven by the ICH9 is 31.25 MHz.

NOTES:

1. The originator must drive a more restrictive ti me to allow f or quantized sampling errors by

a client yet still attain the minimum time less than 500 µs. tBIT limits apply equally to

tBIT-A and tBIT-M. ICH9 is targeted on 1 Mbps which is 1 µs bit time.

2. The minimum and maximum bit times are relative to tBIT defined in the Timing

Negotiation pulse.

Table 8-18. SPI Timings (33 MHz)

Sym Parameter Min Max Units Notes Fig

t180b Serial Clock Frequency - 33MHz

Operation 30.3 32.19 MHz 1

t182b SPI Clock Duty cycle at the host 48% 52% 8-12

t183b Tco of SPI_MOSI with respect to serial

clock falling edge at the host -5 5 ns 8-12

t184b Setup of SPI_MISO with respect to serial

clock falling edge at the host 8—ns 8-12

t185b Hold of SPI_MISO with respect to serial

clock falling edge at the host 0—ns 8-12

t186b Setup of SPI_CS[1:0]# assertion with

respect to serial clock rising at the host 30 — ns 8-12

t187b Hold of SPI_CS[1:0]# deassertion with

respect to serial clock falling at the host 30 — ns 8-12

Table 8-19. SST Timings

Sym Parameter Min Max Units Notes Fig

tBIT Bit time (overall time evident on SST)

Bit time driven by an originator 0.495

0.495 500

250 µs

µs 1-

tBIT,jitter Bit time jitter between adjacen t bits in an

SST message header or data bytes after

timing has been negotiated ——%

tBIT,drift

Change in bit time across a SST address

or SST message bits as driven by the

originator. This li mit only applies across

tBIT-A bit drift and tBIT-M drift.

——%

tH1 High level time for logic '1' 0.6 0.8 x

tBIT 2

tH0 High level time for logic '0' 0.2 0.4 x tBIT

tSSTR Rise time (measured from VOL = 0.3V to

VIH,min)—25 + 5

ns/

node

tSSTF Fall time (measured from VOH = 1.1V to

VIL,max)—33

ns/

node

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 315

Electrical Characteristics

NOTES:

1. The originator must driv e a mo re restrictive time to allow for quantize d sampling errors by

a client yet still attain the minim um time less than 500 µs. tBIT limits apply eq ually to

tBIT-A and tBIT-M. ICH9 is targeted on 2 MHz which is 500 ns bit time.

2. The minimum and maximum bit times are relative to tBIT defined in the Timing

Negotiation pulse.

3. Extended trace lengths may appear as additional nodes.

Table 8-20. PECI Timings

Sym Parameter Min Max Units Notes Fig

tBIT Bit time (overall time evident on

PECI)

Bit time driven by an originator

0.495

0.495 500

250 µs

µs 1

tBIT,jitter

Bit time jitter between adjacent bits

in an PECI message header or data

bytes after timing has been

negotiated

——%

tBIT,drift

Change in bit time across a PECI

address or PECI message bits as

driven by the originator. This limit

only applies across tBIT-A bit drift

and tBIT-M drift.

——%

tH1 High level time for logic '1' 0.6 0.8 x tBIT 2

tH0 High level time for logic '0' 0.2 0.4 x tBIT

tPECIR Rise time (measured from VOL to

VIH,min, Vtt(nom) -5%) —30 + 5

ns/

node 3

tPECIF Fall time (measured from VOH to

VIL,max, Vtt(nom) +5%) —30

ns/

node 3

Table 8-21. Power Sequencing and Reset Signal Timings (Sheet 1 of 2)

Sym Parameter Min Max Units Notes Fig

t200 VccRTC active to RTCRST# inactive 18 — ms 8-14

8-15

t201 V5REF_Sus active to VccSus3_3

active 0—ms1

8-14

8-15

t202 VccSus3_3 active to VccSus1_05

active —— – 2

8-14

8-15

t203 VccRTC supply active to VccSus

supplies active 0—ms3

8-14

8-15

t204 VccSus supplies active to LAN_RST#

inactive, RSMRST# inactive 10 — ms 8-14

8-15

t205 VccSus3_3 active to VccSus1_5

active ——— 9

t206 VccLAN3_3 active to VccLAN1_05

active ——— 6

t207 VccCL3_3 active to VccCL1_05 active — — ms 7

t208 VccCL3_3 active to VccCL1_5 active — — ms 8

Electrical Characteristics

316 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. V5REF must be powered up before Vc c3_3, or after Vc c3_3 within 0.7 V. Also, V5REF mus t

power down after Vcc3_3, or before Vcc3_3 within 0.7 V.

2. The associated 3.3 V and 1.05 V supplies are assumed to power up or down ‘together’.

3. The VccSus su pplies must never be active while the VccRTC supply is inactive.

4. Vcc1_5 must power up before V_CPU_IO or after V_CPU_IO within 0.7 V, b) V_CPU_IO

must power down before Vcc1_5 or after Vcc1_5 within 0.7 V.

5. INIT# value determined by value of the CPU BISTEnable bit (Chipset Configuration

6. The associated 3.3 V and 1.05 V supplies are assumed to power up or down ‘together’.

7. The associated 3.3 V and 1.05 V supplies are assumed to power up or down ‘together’.

8. The associated 3.3 V and 1.5 V supplies are assumed to power up or down ‘together’.

9. The associated 3.3 V and 1.5 V supplies are assumed to power up or down ‘together’.

10. These transitions are clocked off the internal RTC. 1 RTC clock is approximately from

28.992 µs to 32.044 µs

11. “VccGLANPLL inactive" is defined for this timing to be when VccGLANPLL drops to 1.425 V

or less, as measured at the ICH9. This timing applies only to platforms using ICH9

integrated GbE LAN.

12. Maximum timing may be exceeded in a management engine enabled system.

t209 V5REF active to Vcc3_3 active 0 — ms 1 8-14

t211 Vcc1_5 active to V_CPU_IO a ctive — — – 4 8-14

t212 VRMPWRGD active to PWROK active 3 — ms 8-15

8-17

8-18

t213 VccSus supplies active to Vcc supplies

active 0—ms38-14

t214

Vcc supplies active to PWROK

Note: PWROK assertion indicates that

PCICLK has been stable for at least

1ms.

99 — ms

8-14

8-15

8-17

8-18

t217

PWROK and VRMPWRGD active to

SUS_STAT# inactive and Processor

interface signals latched to strap

value

33 71 RTCCLK 5, 10,

8-15

8-17

8-18

8-20

t218 SUS_STAT# inactive to PLTRST#

inactive 2 3 RTCCLK 10

8-15

8-17

8-18

8-20

t219 PLTRST# assertion to VccGLANPLL

inactive for platforms using ICH9

integrated GbE LAN 200 — μs11

t228 HDA_RST# active low pulse width 1 — μs

t229 HDA_RST# inactive to HDA_BIT_CLK

startup delay 162.8 — ns

Table 8-21. Power Sequencing and Reset Signal Timings (Sheet 2 of 2)

Sym Parameter Min Max Units Notes Fig

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 317

Electrical Characteristics

Table 8-22. Power Management Timings (Sheet 1 of 3)

Sym Parameter Min Max Units Notes Fig

t230 VccSus active to SLP_S5#, SLP_S4#,

SLP_S3#, SUS_STAT#, PLTRST# and

PCIRST#active —50 ns 8-15

t231

t232 RSMRST# inactive to SUSCLK running,

SLP_S5# inactive — 110 ms 6, 22 8-15

t233 SLP_S5# inactive to SLP_S 4# i nactive See Note Below 8 8-15

8-23

t234 SLP_S4# inactive to SLP_S3# i nactive 1 Not e 16 RTCCLK 1

8-15

8-17

8-18

8-23

8-24

t250 Processor I/F signals latched prior to

STPCLK# active

(Mobile On ly) 0— 9

8-19

8-21

8-22

t251 Bus Master Idle to DPSLP# active

(Mobile On ly) 3.36 — µs 3, 11 8-20

8-21

8-22

t252 DMI message to PMSYNC# assertion

(Mobile On ly) 0—PCICLK 8-22

t253 DPSLP# active to STP_CPU# active

(Mobile On ly) 11PCICLK3

8-20

8-21

8-22

t254 STP_CPU# active to processor clock

stopped

(Mobile On ly) 0 — PCICLK 3, 10 8-21

8-22

t255 STP_CPU# active to DPRSTP#, DPRSLPVR

active

(Mobile On ly) 0— 8-21

8-22

t265

Break Event to DPRSTP#, DPRSLPVR

inactive

(C4 Exit)

(Mobile On ly)

1.5 1.8 µs 12 8-21

8-22

t266a DPRSLPVR, DPRSTP# inactive to

STP_CPU# inactive and CPU Vcc ramped

(Mobile On ly)

Programable.

See D31:F0:AA,

bits 3:2 µs 8-21

t266b DPRSLPVR, DPRSTP# inactive to

STP_CPU# inactive and CPU Vcc ramped

(Mobile On ly)

Programable.

See D31:F0:A8

bits 2:0 µs 8-22

t267 Break Event to STP_CPU# inactive

(C3 Exit)

(Mobile On ly) 6Note 14PCICLK

3, 13,

14 8-20

t268 STP_CPU# inactive to processor clock

running

(Mobile On ly) 0 3 PCICLK 3, 10 8-21

8-22

Electrical Characteristics

318 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

t269 STP_CPU# inactive to DPSLP# inactive

(Mobile Only) 11PCICLK3, 7

8-20

8-21

8-22

t270 DPSLP# inactive to STPCLK# inacti ve

(Mobile Only) 0µs

8-20

8-21

8-22

t273 Break Event to STPCLK# inactive

(C2 Exit)

(Mobile Only) 0ns8-19

t274 STPCLK# inactive to processor I/F signals

unlatched

(Mobile Only) 89PCICLK3, 9

8-19

8-21

8-22

t275 PMSYNC# de-assert to STPCLK# de-

assert. (Mobile Only)

Programable.

See

D31:F0:A8

bits 5:3

µs 8-22

t280 STPCLK# active to DMI Message 0 PCICLK 2

8-16

8-17

8-18

8-22

t281 DMI Message to CPUSLP# active 60 63 PCICLK 3 8-16

t283 DMI Message to SUS_STAT# active 2 RTCCLK 1 8-17

8-18

t284 SUS_STAT# active to PLTRST#, PCIRST#

active

(Desktop Only) 7 17 RTCCLK 1 8-17

t285 SUS_STAT# active to STP_PCI# active

(Mobile Only) 2 10 RTCCLK 1 8-18

t286 STP_PCI# active to PLTRST# and

PCIRST# active

(Mobile Only) 5 7 RTCCLK 1 8-18

t287 PLTRST#, PCIRST# active to SLP_S3#

active 1 2 RTCCLK 1 8-17

8-18

t288 SLP_S3# active to PWROK, VRMPWRGD

inactive

(Mobile Only) 0ms48-18

t289 SLP_S3# active to PWROK, VRMPWRGD

inactive

(Desktop Only) 0ms48-17

t290 PWROK, VRMPWRGD inactive to Vcc

supplies inactive (nominal voltage -5%)

(Mobile Only) 20 ns 23 8-18

8-28

t291 SLP_S3# active to SLP_S4# active 1 2 RTCCLK 1 8-17

8-18

Table 8-22. Power Management Timings (Sheet 2 of 3)

Sym Parameter Min Max Units Notes Fig

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 319

Electrical Characteristics

t294 PWROK, VRMPWRGD inac tive to Vcc

supplies inactive (nominal voltage -5%)

(Desktop Only ) 20 ns 23 8-17

8-27

t295 SLP_S4# active to SLP_S5# active 1 2 RTCCLK 1, 5 8-17

8-18

t296 Wake Event to SLP_S5# inactive 1 10 RTCCLK 1 8-17

8-18

t297 SLP_S5# inactive to SLP_S 4# i nactive See Note Below 8

8-17

8-18

8-23

8-24

8-25

t298 S4_STATE# inactive to SLP_S3# inactive 1 Note 16 RTCCLK 1 8-25

t299 S4 Wake Event to SLP_S4# inactive (S4

Wake) See Note Below 8 8-17

8-18

t300 S3 Wake Event to SLP_S3# inactive (S3

Wake) 0small as

possible RTCCLK 1 8-17

8-18

t301 S1 Wake Event to STPCLK# inactive 9 PCICLK 8-16

t302 SLP_M# inactive to SLP_S3# inactive ±10 ns

t303 SLP_S4# inactive to SLP_M# inactive

when Intel® AMT enabled

(Digital Office Only) ±10 ns 15

t304 RSMRST# deassertion to LAN_RST#

deassertion 0ms17

t305a LAN Power Rails active to LAN_RST#

deassertion 1ms18

t305b LAN_RST# assertion to LAN power rails

inactive 20 ns 25

t306 LANRST# assertion to PWROK assertion 0 ms

t307 SLP_S3# active to Vcc suppli es inactive

(nominal voltage -5%) 5us24

8-17

8-18

t308a RSMRST# deassertion to CLPWROK

assertion 0ms

t308b Controller Link Power Rails active to

CLPWROK assertion 1ms

t308c CLPWROK assertion to PWROK assertion 0 ms

Other Timings

t310 THRMTRIP# active to SLP_S3#, SLP_S4#,

SLP_S5# active 175 ns

t311 RSMRST# rising edge tr ansition from 20%

to 80% 50 μs

t312 RSMRST# fallin g edge transition 21

t313 SLP_M# active to RSMRST# active 500 μs8-18

Table 8-22. Power Management Timings (Sheet 3 of 3)

Sym Parameter Min Max Units Notes Fig

Electrical Characteristics

320 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. These transitions are clocked off the internal RTC . 1 RTC clock is approximately from

28.992 µs to 32.044 µs.

2. The ICH9 STPCLK# assertion will trigger the processor to send a stop grant acknowledge

cycle. The timing for this cycle getting to the ICH9 is dependant on the processor and the

memory controller.

3. These transitions are clocked off the 33 MHz PCICLK. 1 PCICLK is approximately 30 ns.

4. The ICH9 has no maximum timing requirement for this transition. It is up to the system

designer to determine if the SLP_S3#, SLP_S4# and SLP_S5# signals are used to control

the power planes.

5. If the transition to S5 is due to Power Button Override, SLP_S3#, SLP_S4# and SLP_S5#

are asserted together similar to timing t287 (PCIRST# active to SLP_S3# active).

6. If there is no RTC battery in the system, so VccRTC and the VccSus supplies come up

together, the delay from RTCRST# and RSMRST# inactive to SUSCLK toggling may be as

much as 2.5 s.

7. This value is programmable in multiples of 1024 PCI CLKs. Maximum is 8192 PCI CLKs

(245.6 µs).

8. The Min/Max times depend on the programming of the “SLP_S4# Minimum Assertion

Width” and the “SLP_S4# Assertion Stretch Enable bits (D31:F0:A4h bits 5:3)”.

9. Note tha t this does not apply for synchrono us SMIs.

10. This is a clock generator specifi cation

11. If the (G)MCH does not have the CPUSLP# signal, then the minimum value can be

16 PCICLK.

12. This is non-z ero to enforce the minimum assert time for DPRSLPVR. If the minimum assert

time for DPRSLPVR has been met, then this is permitted to be 0.

13. This is non- zero to enforce the minimum assert time for STP_CPU#. If the minimum assert

time for STP_CPU# has been met, then this is permitted to be 0.

14. This value should be at most a few clocks greater than the minimum.

15. When AMT enabled, S4_STATE# indicates if system is in S4 state or below. (Digital Office

Only).

16. For t234 and t298, the SLP_M# stretching logic can push the Max value much larger than

the Min (e.g., up to 3 seconds). With the installation of the Intel Manageability Engi ne

firmware, the Max value of t234 and t298 is 99 ms. Without the installation of the

firmware, the Max value is 4 RTC clocks.

17. RSMRST# must de-assert at or before LAN_RST# de-assertion.

18. Measured from VccLAN3_3 or VccLAN1_05 power within voltage spec (which ever is later

in time) to LAN_RST# = (Vih+Vil)/2. It is acceptable to use an RC circuit sourced from

VccLAN3_3 to create LAN_RST#. The rising edge of LAN_RST# needs to be a clean,

monotonic edge for frequency content below 10 MHz.

19. If Integrated LAN is supported, LAN_RST# must be de-asserted at or before PWROK

assertion.

20. If Integrated LAN is not supported, LANRST# should be tied to ground and must never de-

assert

21. RSMRST# falling edge must transition to 0.8 V or less before VccSus3_3 drops to 2.1 V

22. If bit 0 of Section 13.8.1.3 is set to a 1, SLP_S5# will not be de-asserted unti l a wake

event is detected. If bi t 0 is set to 0, SLP_S5# will de -assert within the sp ec ifi c ation liste d

in the table.

23. t290 and t294 are not applied to V5REF. V5REF timi ngs are bonded by power sequencing.

t290 and t294 apply during S0 to G3 transitions only.

24. t307 is applicable in S0 to Sx transitions.

25. A power rail is consi dered to be inactiv e when the rai l is at its normal v oltage minus 5% or

less.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 321

Electrical Characteristics

8.5 Timing Diagrams

Figure 8-1. Clock Timing

Figure 8-2. Valid Delay from Rising Clock Edge

Figure 8-3. Setup and Hold Times

2.0V

0.8V

Period

High Time

Low Time

Fall Tim e Rise Tim e

Clock 1.5V

Valid Delay

Output

Clock

VTInput

Hold T imeSet up Time

1.5V

Electrical Characteristics

322 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Figure 8-4. Float Delay

Figure 8-5. Pulse Width

Figure 8-6. Output Enable Delay

Figure 8-7. USB Rise and Fall Times

Input VT

Output

Float

Delay

Pulse Wi dth

Clock

Output

Enable

Delay

1.5V

Differential

Data Lines

90%

10% 10%

90%

tRtF

Rise Time Fall Time

Low-speed: 75 ns at CL = 50 pF, 300 ns at CL = 350 pF

Full-speed: 4 to 20 ns at CL = 50 pF

High-speed: 0.8 to 1.2 ns at CL = 10 pF

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 323

Electrical Characteristics

Figure 8-8. USB Jitter

Figure 8-9. USB EOP Width

Figure 8-10. SMBus Transaction

Paired

Transitions

Consecutive

Transitions

Crossover

Points

T period

Differential

Data Lines

Jitter

Differential

Data Lines

EOP

Width

Data

Crossover

Level

Tperiod

t130

SMBCLK

SMBDATA

t131

t19

t134

t20 t21

t135 t132 t18 t13

Electrical Characteristics

324 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Figure 8-11. SMBus Timeout

Figure 8-12. SPI Timings

Start Stop

t137

CLK

ack

CLK

ack

t138 t138

SMBCLK

SMBDATA

t182

SPI_CLK

SPI_MOSI

SPI_MISO

t184

t183

t185

SPI_CS#

t186 t187

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 325

Electrical Characteristics

NOTES:

1. Other power includes VccUSBPLL, VccDMIPLL, and VccSATAPLL. All of these power signals

must independently meet the timings shown in the figure. There are no timing

interdependencies between Vcc1_05 and these other power signals. There are also no

timing interdependencies for these power signals, including Vcc1_05, to Vcc3_3 and

Vcc1_5_A/Vcc1_5_B.

2. PWROK must not glitch, even if RSMRST# is low.

Figure 8-13. Intel® High Definition Audio Input and Output Timings

Figure 8-14. Power Sequen cing and Reset Signal Timings

HDA_SDOUT

HDA_SDIN[3:0]

HDA_BIT_CLK

t143 t143

t144 t144

t145 t146

VccRTC

V_CPU_IO

VccSus3_3

RTCRST#

LAN_RST#,

RSMRST#

t200

t201

ICH

Dkt

V5REF_Sus

V5REF

PWROK

Vcc3_3

VccSus1_05 t203 t204

t209

t211

t214

t202

t213

Vcc1_5_A,

Vcc1_5_B

Vcc1_05

and other

power1

Electrical Characteristics

326 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE:

1. Vcc includes Vcc1_5_A, Vcc1_5_B, Vcc3_3, Vcc1_05, VccUSBPLL, VccDMIPLL,

VccSATAPLL, V5REF and V_CPU_IO.

Figure 8-15. G3 (Mechanical Off) to S0 Timings

VccSus1_05

Running

SUSCLK

SLP_S3#

Vcc1

PWROK

SUS_STAT#

PLTRST#

Pro c e s so r I/F

signals

STPCLK#

DMI message

RSMRST#

LAN_RST# t204

t214

T212

t218

t230

t231

G3 S3 S0 S0 stateG 3 S5

System

State S4

SLP_S4#

SLP_S5# t232

t233 t234

VccSus3_3

Strap Values Normal Operation

VRMPWRGD t217

t202

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 327

Electrical Characteristics

NOTE:

1. Vcc includes Vcc1_5_A, Vcc1_5_B, Vcc3_3, Vcc1_05, VccUSBPLL, VccDMIPLL, and

VccSATAPLL.

Figure 8-16. S0 to S1 to S0 Timing

Figure 8-17. S0 to S5 to S0 Timings (Desktop Only)

t280

S0 S0 S1 S1 S1 S0 S0

STATE

STPCLK#

DMI Message

Wake E vent

t301

STPCLK#

DM I Message

SUS_STAT#

PLTRST#

SLP_S3#

SLP_S5#

Wake Event

PWROK

Vcc1

S0 S0 S 3 S3 S5 S0

t283

t284

t287

t214 t217

t218

t280

SLP_S4#

t291

t295 t297

t234

S4 S4 S3 S3/S4 /S5 S 0

t296

t300

t299

VRMPWRGD

t289

t212

SLP_M#

t307

Electrical Characteristics

328 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE: Vcc includes Vcc1_5_A, Vcc1_5_B, Vcc3_3, Vcc1_05, VccUSBPLL, VccDMIPLL, and

VccSATAPLL.

Figure 8-18. S0 to S5 to S0 Timings (Mobile Only)

STP_CPU#,

CPUSLP#,

DPSLP#,

DPRSTP#

PLTRST#

PCIRST#

SLP_S3#

SLP_S5#

Wake Event

PWROK

Vcc

S0 S0 S 3 S3 S5 S 3 /S4/ S 5 S 0 S0

t295

t288

t296

t214

t217

t218

STP_PCI#

STPCLK#

DMI Message

DPRSLPVR

t280

t283

t285

t287

t286

SUS_STAT#

SLP_S4#

t291 t297

t300

t234

t299

t302

SLP_M#

RSMRST#

t313

t307

Figure 8-19. C0 to C2 to C0 Timings (Mobile Only)

Unlatched Latched Unlatched

CPU I/F

Signals

STPCLK#

Break

Event t250 t273 t274

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 329

Electrical Characteristics

Figure 8-20. C0 to C3 to C0 Timings (Mobile Only)

Figure 8-21. C0 to C4 to C0 Timings (Mobile Only)

Unlatched Latched

CPU I/F

Signals

STPCLK#

Break Event

Bus Master

STP_CPU#

t250

t251

t253

t268

t269

t274

Active Idle

DPSLP# t270

Unlatched

CPU Clocks Running Running

Stopped

t267

t254

Unlatched

CPU I/F

Signals

STPCLK#

Break Event

Bus Master

STP_CPU#

t250

t251

t253

t266a

t269

t274

t270

DPRSTP#

DPSLP#

Active Idle

DPRSLPVR

Unlatched

CPU Clocks Running Running

t254

t255

CPU Vcc

t265

Stopped t268

Latched

Electrical Characteristics

330 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. t290 is also applicable when the system transitions from S0 to G3.

Figure 8-22. C0 to C5/C6 to C0 Timings (Mobile Only)

Figure 8-23. Sleep control signal relationship - Host boots and Management Engine off

Unlatched Latched

CPU I/F

Signals

STPCLK#

Unlatched

PMSYNC#

DPSLP#

STP_CPU#

DPRSTP#

DPRSLPVR

ActiveB us M aster

Stopped Running

RunningCPU Clocks

CPU Vcc

Break Event

t250

t251

t253

t254

t255

t265

t266b

t268

t269

t274

t275

t270

DMI

Message t280 t252

SLP_M#

SLP_S5#

SLP_S4#

SLP_S3#

t297

t234

S4_STATE#

t302

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 331

Electrical Characteristics

NOTE: When both the host and Management Engine boot after G3, SLP_M# does not have any

timing dependency on other sleep control signals. SLP_M# will be de-asserted some time

between SLP_S5# de-assertion and SLP_S3# de-assertion.

Figure 8-24. Sleep control signal relationship - Host and Management Engine boot after G3

SLP_M#

SLP_S5#

SLP_S4#

SLP_S3#

t234

S4_STATE#

t297

Figure 8-25. Sleep control signal relationship - Host stays in S5 and Management Engine

boots after G3

SLP_M#

SLP_S5#

SLP_S4#

SLP_S3#

Wake event

S4_STATE#

t298

t297

t303

Electrical Characteristics

332 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE: Vcc includes Vcc1_5_A, Vcc1_5_B, Vcc3_3, Vcc1_05, VccUSBPLL, VccDMIPLL, and

VccSATAPLL.

NOTE: Vcc includes Vcc1_5_A, Vcc1_5_B, Vcc3_3, Vcc1_05, VccUSBPLL, VccDMIPLL, and

VccSATAPLL.

§ §

Figure 8-26. S4, S5/M1 to S0/M0

SLP_M#

SLP_S5#

SLP_S4#

SLP_S3#

Wake event

S4_STATE#

t298

t297

t303

Figure 8-27. S0 to G3 Timings (Desktop Only)

Figure 8-28. S0 to G3 Timings (Mobile Only)

PWROK

Vcc

t294

PWROK

Vcc

t290

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 333

9 Register and Memory Mapping

The ICH9 contains registers that are located in the processor’s I/O space and memory

space and sets of PCI configuration registers that are located in PCI configuration

space. This chapter describes the ICH9 I/O and memory maps at the register-set lev el.

bit descriptions are provided in the following chapters. The following notations and

definitions are used in the register/instruction description chapters.

RO Read Only . In some cases, if a register is read only , writes to this

separate registers are located at the same location where a read

accesses one of the registers and a write accesses the other

WO Write Only . In some cases, if a register is write only , reads to this

separate registers are located at the same location where a read

accesses one of the registers and a write accesses the other

R/W Read/Write. A register with this attribute can be read and

written.

R/WC Read/Write Clear. A register bit with this attribute can be read

and written. However, a write of 1 clears (sets to 0) the

corresponding bit and a write of 0 has no effect.

R/WO Read/Write-Once. A register bit with this attribute can be

written only once after power up. After the first write, the bit

becomes read only.

R/WLO R ead/W rite, Lock-Once. A register bit with this attribute can be

written to the non-locked value multiple times, but to the locked

value only once. After the locked v alue has been written, the bit

becomes read only.

Reserved The value of reserved bits must never be changed. For details

see Section 9.2.

Default When ICH9 is reset, it sets its registers to predetermined default

states. The default state represents the minimum functionality

feature set required to successfully bring up the system. Hence,

it does not represent the optimal system configur ation. It is the

responsibility of the system initialization software to determine

configuration, operating parameters, and optional system

features that are applicable, and to program the ICH9 registers

accordingly.

Bold Register bits that are highlighted in bold text indicate that the

bit is implemented in the ICH9. Register bits that are not

implemented or are hardwired will remain in plain text.

334 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

9.1 PCI Devices and Functions

The Intel ICH9 incorporates a variety of PCI devices and functions, as shown in

Table 9-1. They are divided into seven logical devices. The first is the DMI-To-PCI

bridge (Device 30). The second device (Device 31) contains most of the standard PCI

functions that always existed in the PCI-to-ISA bridges (South Bridges), such as the

Intel PIIX4. The third and fourth (Device 29 and Device 26) are the USB and USB2 host

controller devices. The fifth (Device 28) is PCI Express device. The sixth (Device 27) is

HD Audio controller device, and the seventh (Device 25) is the Gigabit Ethernet

controller device.

If for some reason, the particular system platform does not want to support any one of

the Device Functions, with the exception of D30:F0, they can individually be disabled.

The integrated Gigabit Ethernet controller will be disabled if no Platform LAN Connect

component is detected (See Chapter 5.3). When a function is disabled, it does not

appear at all to the software. A disabled function will not respond to an y register reads

or writes, insuring that these devices appear hidden to software.

NOTES:

1. The PCI-to-LPC bridge contains registers that control LPC, Power Management, System

Management, GPIO, Processor Interface, RTC, Interrupts, Timers, and DMA.

Table 9-1. PCI Devices and Functions

Bus:Device:Function Function Description

Bus 0:Device 30:Function 0 PCI-to-PCI Bridge

Bus 0:Device 31:Function 0 LPC Controller1

Bus 0:Device 31:Function 2 SATA Controller #1

Bus 0:Device 31:Function 3 SMBus Controller

Bus 0:Device 31: Function 5 SATA Controller #23

Bus 0:Device 31:Function 6 Thermal Subsystem

Bus 0:Device 29:Function 0 USB UHCI Controller #1

Bus 0:Device 29:Function 1 USB UHCI Controller #2

Bus 0:Device 29:Function 2 USB UHCI Controller #3

Bus 0:Device 29:Function 3 USB UHCI Controller #62

Bus 0:Device 29:Fu nction 7 USB EHCI Controller #1

Bus 0:Device 26:Function 0 USB UCHI Controller #4

Bus 0:Device 26:Function 1 USB UHCI Controller #5

Bus 0:Device 26:Function 2 USB UHCI Controller #62

Bus 0:Device 26 :Fucntion 7 USB EHCI Controller #2

Bus 0:Device 28: Function 0 PCI Express* Port 1

Bus 0:Device 28:Function 1 PCI Express Port 2

Bus 0:Device 28:Function 2 PCI Express Port 3

Bus 0:Device 28:Function 3 PCI Express Port 4

Bus 0:Device 28:Function 4 PCI Express Port 5

Bus 0:Device 28:Function 5 PCI Express Port 6

Bus 0:Device 27 :Function 0 Intel® High Definition Audio Controller

Bus 0:Device 25:Function 0 Gigabit E thernet Contr oller

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 335

2. The ICH9 can optionally configure the USB ports from a 6-6 configuration into a 8-4

configuration, with 8 ports on D29:F7 EHCI and 4 ports on D26:F7 EHCI. In the 8-4

configuration UHCI #6 will be mapped to D29:F3. In the 6-6 configuration UHCI #6 will be

mapped to D26:F2.

3. SATA controller 2 (D31:F5) is only visible in ICH9 desktop components and when D31:F2

CC.SCC=01h.

9.2 PCI Configuration Map

Each PCI function on the ICH9 has a set of PCI configuration registers. The register

address map tables for these register sets are included at the beginning of the chapter

for the particular function.

Configuration Space registers are accessed through configuration cy cles on the PCI bus

by the Host bridge using configuration mechanism #1 detailed in the PCI Local Bus

Specification, Revision 2.3.

Some of the PCI registers contain reserved bits. Software must deal correctly with

fields that are reserved. On reads, software must use appropriate masks to extr act the

defined bits and not rely on reserved bits being any particular value. On writes,

software must ensure that the values of reserved bit position s are pres e rved. That is,

the values of reserv ed bit positions mu st first be read, merged with the new values for

other bit positions and then written back. Note the software does not need to perform

read, merge, write operation for the configuration address register.

In addition to reserved bits with in a register, the configuration space contains reserved

locations. Software should not write to reserved PCI configuration locations in the

device-specific region (above address offset 3Fh).

9.3 I/O Map

The I/O map is divided into Fixed and Variable address ranges. Fixed ranges cannot be

moved, but in some cases can be disabled. Variable ranges can be moved and can also

be disabled.

9.3.1 Fixed I/O Address Ranges

Table 9-2 shows the Fixed I/O decode ranges from the processor perspective. Note that

for each I/O range, there may be separate behavior for reads and writes. DMI (Direct

Media Interface) cycles that go to target r anges that are marked as “R eserved” will not

be decoded by the ICH9, and will be passed to PCI unless the Subtractive Decode P olicy

bit is set (D31:F0:Offset 42h, bit 0). If a PCI master targets one of the fixed I/O target

ranges, it will be positively decoded by the ICH9 in medium speed.

Address ranges that are not listed or marked “Reserved” are not decoded by the ICH9

(unless assigned to one of the variable ranges).

336 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Table 9-2. Fixed I/O Ranges Decoded by Intel® ICH9 (Sheet 1 of 2)

I/O

Address Read Target Write Target Internal Unit

00h–08h DMA Controller DMA Controller DMA

09h–0Eh RESERVED DMA Controller DMA

0Fh DMA Controller DMA Controller DMA

10h–18h DMA Controller DMA Controller DMA

19h–1Eh RESERVED DMA Controller DMA

1Fh DMA Controller DMA Controller DMA

20h–21h Interrupt Controller Interrupt Controller Interrupt

24h–25h Interrupt Controller Interrupt Controller Interrupt

28h–29h Interrupt Controller Interrupt Controller Interrupt

2Ch–2Dh Interrupt Controller Interrupt Controller Interrupt

2E–2F LPC SIO LPC SIO Forwarded to LPC

30h–31h Interrupt Controller Interrupt Controller Interrupt

34h–35h Interrupt Controller Interrupt Controller Interrupt

38h–39h Interrupt Controller Interrupt Controller Interrupt

3Ch–3Dh Interrupt Controller Interrupt Controller Interrupt

40h–42h Timer/Counter Timer/Counter PIT (8254)

43h RESERVED Timer/Counter PIT

4E–4F LPC SIO LPC SIO Forwarded to LPC

50h–52h Timer/Counter Timer/Counter PIT

53h RESERVED Timer/Counter PIT

60h Microcontroller Microcontroller Forwarded to LPC

61h NMI Controller NMI Controller Processor I/F

62h Microcontroller Microcontroller Forwarded to LPC

64h Microcontroller Microcontroller Forwarded to LPC

66h Microcontroller Microcontroller Forwarded to LPC

70h RESERVED NMI and RTC Controller RTC

71h RTC Controller RTC Controller RTC

72h RTC Controller NMI and RTC Controller RTC

73h RTC Controller RTC Controller RTC

74h RTC Controller NMI and RTC Controller RTC

75h RTC Controller RTC Controller RTC

76h RTC Controller NMI and RTC Controller RTC

77h RTC Controller RTC Controller RTC

80h DMA Controller, or LPC, or

PCI DMA Controller and LPC or

PCI DMA

81h–83h DMA Controller DMA Controller DMA

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 337

NOTE:

1. A read to this address will subtractively go to PCI, where it will master abort.

84h–86h DMA Controller DMA Controller and LPC or

PCI DMA

87h DMA Controller DMA Controller DMA

88h DMA Controller DMA Controller and LPC or

PCI DMA

89h–8Bh DMA Controller DMA Controller DMA

8Ch–8Eh D MA Controller DMA Controller and LPC or

PCI DMA

08Fh DMA Controller DMA Controller DMA

90h–91h DMA Controller DMA Controller DMA

92h Reset Generator Reset Generator Processor I/F

93h–9Fh DMA Controller DMA Controller DMA

A0h–A1h Interrupt Controller Interrupt Controller Interrupt

A4h–A5h Interrupt Controller Interrupt Controller Interrupt

A8h–A9h Interrupt Controller Interrupt Controller Interrupt

ACh–ADh Interrupt Controller Interrupt Controller Interrupt

B0h–B1h Interrupt Controller Interrupt Controller Interrupt

B2h–B3h Power Management Power Management Power

Management

B4h–B5h Interrupt Controller Interrupt Controller Interrupt

B8h–B9h Interrupt Controller Interrupt Controller Interrupt

BCh–BDh Interrupt Controller Interrupt Controller Interrupt

C0h–D1h DMA Controller DMA Controller DMA

D2h–DDh RESERVED DMA Controller DMA

DEh–DFh DMA Controller DMA Controller DMA

F0h PCI and Master Abort1FERR#/IGNNE# / Interrupt

Controller Processor I/F

170h–177h SATA Controller or PCI SATA Controller or PCI Forwarded to

SATA

1F0h–1F7h SATA Controller or PCI SATA Controller or PCI Forwarded to

SATA

376h SATA Controller or PCI SATA Controller or PCI Forwarded to

SATA

3F6h SATA Controller or PCI SATA Controller or PCI Forwarded to

SATA

4D0h–4D1h Interrupt Controller Interrupt Controller Interrupt

CF9h Reset Generator Reset Generator Processor I/F

Table 9-2. Fixed I/O Ranges Decoded by Intel® ICH9 (Sheet 2 of 2)

I/O

Address Read Target Writ e Target Internal Unit

338 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

9.3.2 Variable I/O Decode Ranges

Table 9-3 shows the Variable I/O Decode Ranges. They are set using Base Address

Registers (BARs) or other configuration bits in the various PCI configuration spaces.

The PNP software (PCI or ACPI) can use their configuration mechanisms to set and

adjust these values.

Warning: The Variable I/O Ranges should not be set to conflict with the Fixed I/O Ranges.

Unpredictable results if the configuration software allows conflicts to occur. The ICH9

does not perform any checks for conflicts.

NOTE:

1. Decode range size determined by D31:F0:ADh:bits 5:4

Table 9-3. Variable I/O Decode Ranges

Range Name Mappable Size

(Bytes) Target

ACPI Anywhere in 64 KB I/O Space 64 Power Management

IDE Bus Master Anywhere in 64 KB I/O Space 16 IDE Unit

Native IDE Command Anywhere in 64 KB I/O Space 8 IDE Unit

Native IDE Control Anywhere in 64 KB I/O Space 4 IDE Unit

USB UHCI Controller #1 Anywhere in 64 KB I/O Space 32 USB Unit 1

USB UHCI Controller #2 Anywhere in 64 KB I/O Space 32 USB Unit 2

USB UHCI Controller #3 Anywhere in 64 KB I/O Space 32 USB Unit 3

USB UHCI Controller #4 Anywhere in 64 KB I/O Space 32 USB Unit 4

USB UHCI Controller #5 Anywhere in 64 KB I/O Space 32 USB Unit 5

USB UHCI Controller #6 Anywhere in 64 KB I/O Space 32 USB Unit 6

SMBus Anywhere in 64 KB I/O Space 32 SMB Unit

TCO 96 Bytes above ACPI Base 32 TCO Unit

GPIO Anywhere in 64 KB I/O Space 64 GPIO Unit

Parallel Port 3 Ranges in 64 KB I/O Space 8 LPC Peripheral

Serial Port 1 8 Ranges in 64 KB I/O Space 8 LPC Peripheral

Serial Port 2 8 Ranges in 64 KB I/O Space 8 LPC Peripheral

Floppy Disk Controller 2 Ranges in 64 KB I/O Space 8 LPC Peripheral

LAN Anywhere in 64 KB I/O Space 32 LAN Unit

LPC Generic 1 Anywhere in 64 KB I/O Space 4 to 256 LPC Peripheral

LPC Generic 2 Anywhere in 64 KB I/O Space 4 to 256 LPC Peripheral

LPC Generic 3 Anywhere in 64 KB I/O Space 4 to 256 LPC Peripheral

LPC Generic 4 Anywhere in 64 KB I/O Space 4 to 256 LPC Peripheral

I/O Trapping Ranges Anywhere in 64 KB I/O Space 1 to 256 Trap on Backbone

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 339

9.4 Memory Map

Table 9-4 shows (from the proce ssor perspective) the memory ranges that the ICH9

decodes. Cycles that arrive from DMI that are not directed to any of the internal

memory targets that decode directly from DMI will be driven out on PCI unless the

Subtractive Decode Policy bit is set (D31:F0:Offset 42h, bit 0).

PCI cycles generated by external PCI masters will be positively decoded unless they fall

in the PCI-to-PCI bridge memory forwarding ranges (those addresses are reserved for

PCI peer-to-peer traffic). If the cycle is not in the internal LAN controller’s r ange, it will

be forwarded up to DMI. Software must not attempt locks to the ICH9’s memory-

mapped I/O ranges for EHCI and HPET. If attempted, the lock is not honored which

means potential deadlock conditions may occur.

Table 9-4. Memory Decode Ranges from Processor Perspective (Sheet 1 of 2)

Memory Range Target Dependency/Comments

0000 0000h–000D FFFFh

0010 0000h–TOM

(Top of Memory) Main Memory TOM registers in Host controller

000E 0000h–000E FFFFh Firmware Hub Bit 6 in Firmware Hub Decode Enable register

is set

000F 0000h–000F FFFFh Firmware Hub Bit 7 in Firmware Hub Decode Enable register

is set

FEC0 x000h–FEC0 x040h IO(x) APIC inside

ICH9 X is controlled via APIC Range Select (ASEL)

field and APIC Enable (AEN) bit

FEC1 0000h–FEC1 7FFF PCI Express* Port 1 PCI Express* Root Port 1 I/OxAPIC Enable

(PAE) set

FEC1 8000h–FEC1 8FFFh PCI Express* Port 2 PCI Express* Root Port 2 I/OxAPIC Enable

(PAE) set

FEC2 0000h–FEC2 7FFFh PCI Express* Port 3 PCI Express* Root Port 3 I/OxAPIC Enable

(PAE) set

FEC2 8000h–FEC2 8FFFh PCI Express* Port 4 PCI Express* Root Port 4 I/OxAPIC Enable

(PAE) set

FEC3 0000h–FEC3 7FFFh PCI Express* Port 5 PCI Express* Root Port 5 I/OxAPIC Enable

(PAE) set

FEC3 8000h–FEC3 8FFFh PCI Express* Port 6 PCI Express* Root Port 6 I/OxAPIC Enable

(PAE) set

FED4 0000h–FED4 BFFFh TPM on LPC

FFC0 0000h–FFC7 FFFFh

FF80 0000h–FF87 FFFFh Firmware Hub (or

PCI)2Bit 8 in Firmware Hub Decode Enable register

is set

FFC8 0000h–FFCF FFFFh

FF88 0000h–FF8F FFFFh Firmware Hub (or

PCI)2Bit 9 in Firmware Hub Decode Enable register

is set

FFD0 0000h–FFD7 FFFFh

FF90 0000h–FF97 FFFFh Firmware Hub (or

PCI)2Bit 10 in Firmware Hub Decode Enable register

is set

FFD8 0000h–FFDF FFFFh

FF98 0000h–FF9F FFFFh Firmware Hub (or

PCI)2Bit 11 in Firmware Hub Decode Enable register

is set

FFE0 000h–FFE7 FFFFh

FFA0 0000h–FFA7 FFFFh Firmware Hub (or

PCI)2Bit 12 in Firmware Hub Decode Enable register

is set

340 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTES:

1. Software must not attempt locks to memory mapped I/O ranges for USB EHCI or High

Precision Event Timers. If attempted, the lock is not honored, which means potential

deadlock conditions may occur.

2. PCI is the target when the Boot BIOS Destination selection bits are set to 10b (Chipset

Config Registers:Offset 3401 bits 11:10). When PCI selected, the Firmware Hub Decode

Enable bits have no effect.

9.4.1 Boot-Block Update Scheme

The ICH9 supports a “top-block swap” mode that has the ICH9 swap the top block in

the Firmware Hub (the boot block) with another location. This allows for safe update of

the Boot Block (even if a power failure occurs). When the “TOP_SWAP” Enable bit is

set, the ICH9 will invert A16 for cycles targeting Firmware Hub space. When this bit is

0, the ICH9 will not invert A16. This bit is automatically set to 0 by RTCRST#, but not

by PLTRST#.

The scheme is based on the concept that the top block is reserved as the “boot” block,

and the block immediately below the top block is reserved for doing boot-block

updates.

FFE8 0000h–FFEF FFFFh

FFA8 0000h–FFAF FFFFh Firmware Hub (or

PCI)3Bit 13 in Firmware Hub Decode Enable register

is set

FFF0 0000h–FFF7 FFFFh

FFB0 0000h–FFB7 FFFFh Firmware Hub (or

PCI)2Bit 14 in Firmware Hub Decode Enable register

is set

FFF8 0000h–FFFF FFFFh

FFB8 0000h–FFBF FFFFh Firmware Hub (or

PCI)2

Always enabled.

The top two , 64 KB blocks of thi s range can be

swapped, as described in Section 7.4.1.

FF70 0000h–FF7F FFFFh

FF30 0000h–FF3F FFFFh Firmware Hub (or

PCI)2Bit 3 in Firmware Hub Decode Enable register

is set

FF60 0000h–FF6F FFFFh

FF20 0000h–FF2F FFFFh Firmware Hub (or

PCI)2Bit 2 in Firmware Hub Decode Enable register

is set

FF50 0000h–FF5F FFFFh

FF10 0000h–FF1F FFFFh Firmware Hub (or

PCI)2Bit 1 in Firmware Hub Decode Enable register

is set

FF40 0000h–FF4F FFFFh

FF00 0000h–FF0F FFFFh Firmware Hub (or

PCI)2Bit 0 in Firmware Hub Decode Enable register

is set

128 KB anywhere in 4- GB

range Integrated LAN

Controller Enable via BAR in Device 25:Function 0

(Integrated LAN Controller)

1 KB anywhere in 4-GB

range USB EHCI

Controller #11Enable via standard PCI mechanism (Device

29, Function 7)

1 KB anywhere in 4-GB

range USB EHCI

Controller #21Enable via standard PCI mechanism (Device

26, Function 7)

512 B anywhere in 64 -bi t

addressing space

Intel® High

Definition Audio

Host Controller

Enable via standard PCI mechanism (Device

27, Function 0)

FED0 X000h–FED0 X3FFh High Precision

Event Timers 1

BIOS determines the “fixed” location wh ich is

one of four, 1-KB ranges where X (in the first

column) is 0h, 1h, 2h, or 3h.

All other PCI None

Table 9-4. Memory Decode Ranges from Processor Perspective (Sheet 2 of 2)

Memory Range Target Dependency/Comments

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 341

The algorithm is:

1. Software copies the top block to the block immediately below the top

2. Software checks that the copied block is correct. This could be done by performing

a checksum calculation.

3. Software sets the TOP_SWAP bit. This will invert A16 for cycles going to the

Firmware Hub. processor access to FFFF_0000h through FFFF_FFFFh will be

directed to FFFE_0000h through FFFE_FFFFh in the Fi rmware Hub, and processor

accesses to FFFE_0000h through FFFE_FFFF will be directed to FFFF_0000h

through FFFF_FFFFh.

4. Software erases the top block

5. Software writes the new top block

6. Software checks the new top block

7. Software clears the TOP_SWAP bit

8. Software sets the Top_Swap Lock-Down bit

If a power failure occurs at any point after step 3, the system will be able to boot from

the copy of the boot block that is stored in the block below the top. This is because the

TOP_SWAP bit is backed in the RTC well.

Note: The top-block swap mode may be forced by an external strapping option (See

Section 2.24.1). When top-block swap mode is forced in this manner, the TOP_SWAP

bit cannot be cleared by software. A re-boot with the str ap remov e d will be required to

exit a forced top-block swap mode.

Note: Top-block swap mode only affects accesses to the Firmware Hub space, not feature

space.

Note: The top-block swap mode has no effect on accesses below FFFE_0000h.

§ §

342 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 343

Chipset Configuration Registers

10 Chipset Configuration Registers

This section describes all registers and base functionality that is related to chipset

configuration and not a specific interface (such as LPC, PCI, or PCI Express*). It

contains the root complex register block, which describes the behavior of the upstream

internal link.

This block is mapped into memory space, using the Root Complex Base Address (RCBA)

quantities. Burst accesses are not allowed.

All Chipset Configuration Registers are located in the core well unless otherwise

indicated.

10.1 Chipset Configuration Registers (Memory Space)

Note: Address locations that are not shown should be treated as Reserved (see Section 9.2

for details).

Table 10-1. Chipset Configuration Register Memory Map (Memory Space) (Sheet 1 of 4)

Offset Mnemonic Register Name Default Type

0000–0003h VCH Virtual Channe l Capability

Header 10010002h R/WO

0004–0007h VCAP1 Virtual Channel Capability #1 00000801h RO, R/WO

0008–000Bh VCAP2 Virtual Channel Capability #2 00000001h RO

000C–000Dh PVC Port VC Control 0000h RO, R/W

000E–000Fh PVS Port VC Status 0000h RO

0010–0013h V0CAP VC 0 Resource Capability 00000001h RO

0014–0017h V0CTL VC 0 Resource Control 800000FFh R/W, RO

001A–001Bh V0STS VC 0 Resource Status 0000h RO

001C–001Fh V1CAP VC 1 Resource Capability 03008011h R/WO, RO

0020–0023h V1CTL VC 1 Resource Control 00000000h R/W

0026–0027h V1STS VC 1 Resource Status 0000h RO

0030-006Fh PAT Port Arbitration Table

0088-008Bh CIR1 Chipset Initialization Register 1 00000000h R/WO

00AC-00AFh REC Root Error Command 0000h R/W

0100–0103h RCTCL Root Complex Topology

Capability List 1A010005h RO

0104–0107h ESD Element Self Description 00000802h R/WO, RO

0110–0113h ULD Upstream Link Descriptor 00000001h R/WO, RO

0118–011Fh ULBA Upstream Link Base Address 0000000000000000h R/WO

0120–0123h RP1D Root Port 1 Descriptor 01xx0002h R/WO, RO

0128–012Fh RP1BA Root Port 1 Base Address 00000000000E0000h RO

0130–0133h RP2D Root Port 2 Descriptor 02xx0002h R/WO, RO

Chipset Configuration Registers

344 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

0138–013Fh RP2BA Root Port 2 Base Address 00000000000E1000h RO

0140–0143h RP3D R oot Port 3 Descriptor 03xx0002h R/WO, RO

0148–014Fh RP3BA Root Port 3 Base Address 00000000000E2000h RO

0150–0153h RP4D R oot Port 4 Descriptor 04xx0002h R/WO, RO

0158–015Fh RP4BA Root Port 4 Base Address 00000000000E3000h RO

0160–0163h HDD Intel® High Definition Audio

Descriptor 15xx0002h R/WO, RO

0168–016Fh HDBA Intel High Definition Audio

Base Address 00000000000D8000h RO

0170–0173h RP5D R oot Port 5 Descriptor 05xx0002h R/WO, RO

0178–017Fh RP5A Root Por t 5 Base Address 00000000000E4000h RO

0180–0183h RP6D R oot Port 6 Descriptor 06xx0002h R/WO, RO

0188–018Fh RP6BA Root Port 6 Base Address 00000000000E5000h RO

01A0–01A3h ILCL Internal Link Capability List 00010006h RO

01A4–01A7h LCAP Link Capabilities 00012841h RO, R/WO

01A8–01A9h LCTL Link Control 0000h R/W

01AA–01ABh LSTS Link Status 0041h RO

01F4-01F7h CIR2 Chipset Initialization Register 2 00000000h R/W

01FC- 01F Dh CIR3 Chipset Initialization R egi st er 3 0000h R/W

0220-0223h BCR Backbone Configuration 00000000h R/W

0224–0227h RPC Root Port Configuration 0000000yh R/W, RO

0234-0327h DMIC DMI Control 00000000h R/W, RO

0238–023Bh RPFN Root P ort Function Number for

PCI Express Root Ports 00543210h R/WO, RO

0290-0293h FPSS Function Leve l Reset Pending

Status Summary 00000000h RO

0F20-0F23h CIR13 Chipset Initialization Register

13 B2B477CCh R/W

1D40-1D47h CIR5 Chipset Initialization Register 5 0000000000000000h R/W

1E00–1E03h TRSR Trap Status Register 00000000h R/WC, RO

1E10–1E17h TRCR Trapped Cycle Register 0000000000000000h RO

1E18-1E1Fh TWDR Trapped Write Data Register 0000000000000000h RO

1E80-1E87h IOTR0 I/O Trap Register 0 0000000000000000h R/W

1E88-1E8Fh IOTR1 I/O Trap Register 1 0000000000000000h R/W

1E90-1E97h IOTR2 I/O Trap Register 2 0000000000000000h R/W

1E98-1E9Fh IOTR3 I/O Trap Register 3 0000000000000000h R/W

2010-2013h DMC DMI Miscellaneous Control

2024-2027h CIR6 Chipset Initialization Register 6

(Mobile On ly) 0B4030C0h R/W

Table 10-1. Chipset Configuration Register Memory Map (Memory Space) (Sheet 2 of 4)

Offset Mnemonic Register Name Default Type

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 345

Chipset Configuration Registers

2034-2037h CIR7 Chipset Initialization R e gis ter 7 B2B477CCh R/W

20C4-20C5h CIR11 Chipset Initialization Register

11 (Mobile Only) 0000h R/W

20E4-20E5h CIR12 Chipset Initializa tion Register

12 (Mobile Only) 0000h R/W

3000–3000h TCTL TCO Control 00h R/W

3100–3103h D31IP Device 31 Interrupt Pin 03243200h R/W, RO

3104–3107h D30IP Device 30 Interrupt Pin 00000000h RO

3108–310Bh D29IP Device 29 Interrupt Pin 10004321h R/W

310C–310Fh D 28IP Device 28 Interrupt Pin 00214321h R/W

3110–3113h D27IP Device 27 Interrupt Pin 00000001h R/W

3114–3117h D26IP Device 26 Interrupt Pin 30000321h R/W

3118–311Bh D25IP Device 25 Interrupt Pin 00000001h R/W

3140–3141h D31IR Device 31 Interrupt Route 3210h R/W

3142–3143h D30IR Device 30 Interrupt Route 0000h RO

3144–3145h D29IR Device 29 Interrupt Route 3210h R/W

3146–3147h D28IR Device 28 Interrupt Route 3210h R/W

3148–3149h D27IR Device 27 Interrupt Route 3210h R/W

314C–314Dh D26IR Device 26 Interrupt Route 3210h R/W

3150–3151h D25IR Device 25 Interrupt Route 3210h R/W

31FF–31FFh OIC Other Interrupt Control 00h R/W

3300-3303h SBEMC3 Scheduled Break Event C3

(Mobile Only) 00000000h R/W

3304-3307h SBEMC4 Schedule Break Event C4

(Mobile Only) 00000000h R/W

3400–3403h RC RTC Configuration 00000000h R/W,

R/WLO

3404–3407h HPTC High Precision Timer

Configuration 00000000h R/W

3410–3413h GCS General Control and Status 000000yy0h R/W,

R/WLO

3414–3414h BUC Backed Up Control 00h R/W

3418–341Bh FD F unction Disable 00000000h R/W

341C–341Fh CG Clock Gating 00000000h R/W

3420–3420h PDSW Function Disable SUS Well 00h R/W

3430-3433h CIR8 Chipset Initiali zati on Regis te r 8 00000000h R/W

350C -3 50F h CIR9 Chipset Initiali zation R e gis te r 9 00000000h R/W

Table 10-1. Chipset Configuration Register Memory Map (Memory Space) (Sheet 3 of 4)

Offset Mnemonic Register Name Default Type

Chipset Configuration Registers

346 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.1 VCH—Virtual Channel Capabil ity Header Register

Offset Address: 0000–0003h Attribute: R/WO

Default Value: 10010002h Size: 32-bit

10.1.2 VCAP1—Virtual Channel Capability #1 Register

Offset Address: 0004–0007h Attribute: RO, R/WO

Default Value: 00000801h Size: 32-bit

3524–3525h PPO USB Port Power Off 0000h R/W

352C-352Fh CIR10 Chipset Initialization Register

10 0008C008hh R/W

35F0-35F3h MAP USB Remap Control 00000000h R/WO

Table 10-1. Chipset Configuration Register Memory Map (Memory Space) (Sheet 4 of 4)

Offset Mnemonic Register Name Default Type

Bit Description

31:20 Next Capability Offset (NCO) — R/WO. Indicates the next item in the list.

19:16 Capability Version (CV) — R/WO. Indicates support as a version 1 capability

structure.

15:0 Capability ID (CID) — R/WO. Indicates this is the Virtual Channel capability item.

Bit Description

31:12 Reserved

11:10 Port Arbitration Table Entry Size (PATS) — RO. Indicates the size of the port

arbitration table is 4 bits (to allow up to 8 ports).

9:8 Reference Clo ck (RC) — RO. Fixed at 100 ns.

7 Reserved

6:4 Low Priority Extended VC Count (LPEVC) — RO. Indicates that there are no

additional VCs of low priority with extended capabilities.

3 Reserved

2:0 Extended VC Count (EVC) — R/WO. Indicates th at there is one additi onal VC (VC1)

that exists with extended capabilities.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 347

Chipset Configuration Registers

10.1.3 VCAP2—Virtual Channel Capability #2 Register

Offset Address: 0008–000Bh Attribute: RO

Default Value: 00000001h Size: 32-bit

10.1.4 PVC—Port Virtual Channel Control Register

Offset Address: 000C–000Dh A ttribute: RO, R/W

Default Value: 0000h Size: 16-bit

10.1.5 PVS—Port Virtual Channel Status Register

Offset Address: 000E–000Fh A ttribute: RO

Default Value: 0000h Size: 16-bit

Bit Description

31:24 VC Arbitr ation Tabl e Off set (ATO ) — RO. Indicates that no table is present for VC

arbitration since it is fixed.

23:8 Reserved

7:0 VC Arbitration Capability (AC) — RO. Indicates that the VC arbitration is fixed in

the root complex.

Bit Description

15:04 Reserved

3:1 VC Arbitration Select (AS) — R/W. Indicates which VC should be programmed in

the VC arbitration table. The root complex takes no action on the setting of this field

since there is no arbitration table.

0Load VC Arbitration Table (LAT) — RO. Indicates that the table programmed

should be loaded into the VC arbitration table. This bit is defined as read/write with

always returning 0 on reads.

Bit Description

15:1 Reserved

0VC Arbitration Table Status (VAS) — RO. Indicates the coherency status of the VC

Arbitration table when it is being updated. This field is always 0 in the root complex

since there is no V C arbitration table.

Chipset Configuration Registers

348 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.6 V0CAP—Virtual Channel 0 Resource Capability Register

Offset Address: 0010–0013h Attribute: RO

Default Value: 00000001h Size: 32-bit

Bit Description

31:24 Port Arbitration Table Offset (AT) — RO. This VC implements no port arbitration

table since the arbitration is fixed.

23 Reserved

22:16 Maximum Time Slots (MTS) — RO. This VC implements fixed arbitration, and

therefore this field is not used.

15 Reject Snoop Transactions (RTS) — RO. This VC must be able to take snoopable

transactions.

14 Advanced Packet Switching (APS) — RO. This VC is capable of all transactions,

not just advanced packet switching transactions.

13:8 Reserved

7:0 Port Arbitration Capability (PAC) — RO. Indicates that this VC uses fixed port

arbitration.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 349

Chipset Configuration Registers

10.1.7 V0CTL—Virtual Channel 0 Resource Control Register

Offset Address: 0014–0017h Attribute: R/W, RO

Default Value: 800000FFh Size: 32-bit

10.1.8 V0STS—Virtual Channel 0 Resource Status Register

Offset Address: 001A–001Bh Attribute: RO

Default Value: 0000h Size: 16-bit

Bit Description

31 Virtual Channel Enable (EN) — RO. Always set to 1. VC0 is always enabled and

cannot be disabled.

30:27 Reserved

26:24 Virtual Channel Identifier (ID) — RO. Indicates the ID to use for this virtual

channel.

23:20 Reserved

19:17 Port Arbitration Select (PAS) — R/W. Indicates which port table is being

programmed. The root complex tak es no action on this setting since the arbitration is

fixed and there is no arbitration table.

16 Load Port Arbitration Table (LAT) — RO. The root complex does not impleme nt

an arbitration table for this virtual channel.

15:8 Reserved

7:1 Transaction Class / Virtual Channel Map (TVM) — R/W. Indicates which

transaction classes are mapped to this virtual channel. Whe n a bit is set, this

transaction class is mapped to the virtual channel.

0 Reserved

Bit Description

15:2 Reserved

1VC Negotiation Pending (NP) — RO. When set, indicates t he virtual channel is st ill

being negotiated with ingress ports.

0Port Arbitration Tables Status (ATS) — RO. There is no port arbitration table for

this VC, so this bit is reserved at 0.

Chipset Configuration Registers

350 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.9 V1CAP—Virtual Channel 1 Resource Capability Register

Offset Address: 001C–001Fh Attribute: R/WO, RO

Default Value: 03008011h Size: 32-bit

10.1.10 V1CTL—Virtual Channel 1 Resource Control Register

Offset Address: 0020–0023h Attribute: R/W

Default Value: 00000000h Size: 32-bit

Bit Description

31:24 Port Arbitration Table Offset (AT) — RO. Indicates the location of the port

arbitration table in the root complex . A value o f 3h indicates th e table is at offset

30h.

23 Reserved

22:16 Maximum Time Slots (MTS) — R/WO. This value is updated by platform BIOS

based upon the determination of the number of time slots available in the platform.

15 Reject Snoop Transactions (RTS) — RO. All snoopable transactions on VC1 are

rejected. This VC is for isochronous transfers only.

14 Advanced Packet Switching (APS) — RO. This VC is capable of all transactions,

not just advanced packet switching transactions.

13:8 Reserved

7:0 Port Arbitration Capability ( PAC) — RO. Indicates the port arbitration capability is

time-based WRR of 128 phases.

Bit Description

31 Virtual Channel Enable (EN) — R/W. Enables the VC when set. Disables the VC

when cleared.

30:27 Reserved

26:24 Virtual Channel Identifier (ID) — R/W. Indicates the ID to use for this virtual

channel.

23:20 Reserved

19:17 Port Arbitr ation Select (PAS) — R/W. Indicates which port table is being

programmed. The only permissible value of this field is 4h for the time-based WRR

entries.

16 Load Port Arbitration Table (LAT) — R/W. When set, the po rt arbitration table

loaded based upon the PAS field in this register. This bit always returns 0 when read.

15:8 Reserved

7:1 Transaction Class / Virtual Channel Map (TVM) — R/W. Indicates which

transaction classes are mapped to this virtual channel. When a bit is set, this

transaction class is mapped to the virtual channel.

0 Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 351

Chipset Configuration Registers

10.1.11 V1STS—Virtual Channel 1 Resource Status Register

Offset Address: 0026–0027h Attribute: RO

Default Value: 0000h Size: 16-bit

10.1.12 PAT—Port Arbitration Table

Offset Address: 0030-006Fh Attribute:

Default Value: Size: 64-Byte

This a 64-byte register that contains the arbitration table to be loaded into the port

arbitration table. Every 4-bits contains an entry for one of the downstream PCI

Express* ports or a 0h to indicate idol. The ports are mapped as follows:

• Port 1: Value used is 1h.

• Port 2: Value used is 2h.

• Port 3: Value used is 3h.

• Port 4: Value used is 4h.

• Port 5: Value used is 5h.

• Port 6: Value used is 6h.

•Intel

® High Definition Audio: Value used is Fh.

Bit Description

15:2 Reserved

1VC Negotiation Pending (NP) — RO. When set, indicates t he virtual channel is st ill

being negotiated with ingress ports.

Port Arbitration Tables Status (ATS) — RO. Indicates the coherency status of the

port arbitration table. This bit is set when LAT (offset 000Ch:bit 0) is written with

value 1 and P AS (offset 0014h:bits1 9:17) has value of 4h. This bit is cleared after the

table has been updated.

Chipset Configuration Registers

352 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.13 CIR1—Chipset Initialization Register 1

Offset Address: 0088–008Bh Attribute: R/WO

Default Value: 00000000h Size: 32-bit

10.1.14 REC—Root Error Command Register

Offset Address: 00AC–00AFh Attribute: R/W

Default Value: 0000h Size: 32-bit

10.1.15 RCTCL—Root Complex Topology Capabilities List Register

Offset Address: 0100–0103h Attribute: RO

Default Value: 1A010005h Size: 32-bit

Bit Description

31:21 Reserved

20 CIR1 Field 3 — R/WO. BIOS must set this bit.

19:16 Reserved

15 CIR1 Field 2 — R/WO. BIOS must set this bit.

14:13 Reserved

12 CIR1 Field 1— R/WO. BIOS must set this bit.

11:0 Reserved

Bit Description

Drop Poisoned Downstream Pac kets (DPDP) — R/W. Determines how

downstream packets on DMI are handled that are received with the EP field set,

indicating poisoned data:

1: This packet and all subsequent packets with data received on DMI for any VC will

have their Unsupported Transaction (UT) field set causing them to master Abort

downstream. P a ck ets wit hout data such as memory, IO and config read requests are

allowed to proceed.

0: Packets are forwarded downstream without forcing the UT field set.

30:0 Reserved

Bit Description

31:20 Next Capability (NEXT) — RO. Indica tes the next ite m in the list.

19:16 Capability Version (CV) — RO. Indicates the version of the capability structure.

15:0 Capability ID (CID) — RO. Indicates this is a PCI Express* link capability section of

an RCRB.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 353

Chipset Configuration Registers

10.1.16 ESD—Element Self Description Register

Offset Address: 0104–0107h Attribute: R/WO, RO

Default Value: 00000802h Size: 32-bit

10.1.17 ULD—Upstream Link Descriptor Register

Offset Address: 0110–0113h Attribute: R/WO, RO

Default Value: 00000001h Size: 32-bit

10.1.18 ULBA—Upstream Link Base Address Register

Offset Address: 0118–011Fh Attribute: R/WO

Default Value: 0000000000000000h Size : 64-bit

Bit Description

31:24 Port Number (PN) — RO. A value of 0 to indicate the egress port for the Intel®

ICH9.

23:16 Component ID (CID) — R/WO. Indicates the compone nt ID assigned to this

element by software. This i s written once by platform BIOS and is locked until a

platform reset.

15:8 Number of Link Entries (NLE) — RO. Indicates that on e li nk e ntr y (corres p ondin g

to DMI), 6 root port entries (for the downstream ports), and the Intel® High

Definition Audio device are described by this RCRB.

7:4 Reserved

3:0 Element Type (ET) — RO. Indicates that the element type is a root complex

internal link.

Bit Description

31:24 Target Port Number (PN) — R/WO. This field is programmed by platform BIOS to

match the port n umber of the (G)MCH RCRB that is attached to this RCRB.

23:16 Target Component ID (TCID) — R/WO . This field is programmed b y platform BIOS

to match the component ID of the (G)MCH RCRB that is attached to this RCRB.

15:2 Reserved

1Link Type (LT) — RO. Indicates that the link points to the (G)MCH RCRB.

0Link Valid (LV) — RO. Indicates that the li nk entry is valid.

Bit Description

63:32 Base Address Upper (BAU) — R/WO. This field is programmed by platform BIOS to

match the upper 32-bits of base address of the (G)MCH RCRB that is attached to this

RCRB.

31:0 Base Address Lower (BAL) — R/WO. This field is programmed by platform BIOS to

match the lowe r 32-bi ts of base address of the ( G)M CH RCRB that is attac hed to this

RCRB.

Chipset Configuration Registers

354 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.19 RP1D—Root Port 1 Descriptor Register

Offset Address: 0120–0123h Attribute: R/WO, RO

Default Value: 01xx0002h Size: 32-bit

10.1.20 RP1BA—Root Port 1 Base Address Register

Offset Address: 0128–012Fh Attribute: RO

Default Value: 00000000000E0000h Size: 64-bit

10.1.21 RP2D—Root Port 2 Descriptor Register

Offset Address: 0130–0133h Attribute: R/WO, RO

Default Value: 02xx0002h Size: 32-bit

Bit Description

31:24 Target Port Number (PN) — RO. Indicates the target port number is 1h (root port

#1).

23:16 Target Component ID (TCID) — R/WO. This field returns the v alue of the ESD.CID

(offset 0104h, bits 23:16) fie ld progr ammed by platfo rm BIOS, since the root port is

in the same compone nt as the RCRB.

15:2 Reserved

1Link Type (LT) — RO. Indicates that the link points to a root port.

0Link Valid (LV) — RO. When FD.PE1D (offset 3418h, bit 16) is set, this link is not

valid (returns 0). When FD.PE1D is cleared, this link is valid (returns 1).

Bit Description

63:28 Reserved

27:20 Bus Number (BN) — RO. Indicates the root port is on bus #0.

19:15 Device Number (DN) — RO. Indicates the root port is on device #28.

14:12 Function Number (FN) — RO. Indicates the root port is on function #0.

11:0 Reserved

Bit Description

31:24 Target Port Number (PN) — RO. Indicates the target port number is 2h (root port

#2).

23:16 Target Component ID (TCID) — R/WO. This field returns the v alue of the ESD.CID

(offset 0104h, bits 23:16) fie ld progr ammed by platfo rm BIOS, since the root port is

in the same compone nt as the RCRB.

15:2 Reserved

1Link Type (LT) — RO. Indicates that the link points to a root port.

Link Valid (LV) — RO. When RPC.PC (offset 0224h, bits 1:0) is ‘01’, ‘10’, or ‘11’, or

FD. PE2D (offset 3418h, bit 17) is set, the link for this root port is no t valid (return 0).

When RPC.PC is ‘00’ and FD.PE2D is cleared, the link for this root port is valid (return

1).

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 355

Chipset Configuration Registers

10.1.22 RP2BA—Root Port 2 Base Address Register

Offset Address: 0138–013Fh Attribute: RO

Default Value: 00000000000E1000h Size: 64-bit

10.1.23 RP3D—Root Port 3 Descriptor Register

Offset Address: 0140–0143h Attribute: R/WO, RO

Default Value: 03xx0002h Size: 32-bit

10.1.24 RP3BA—Root Port 3 Base Address Register

Offset Address: 0148–014Fh Attribute: RO

Default Value: 00000000000E2000h Size: 64-bit

Bit Description

63:28 Reserved

27:20 Bus Number (BN) — RO. Indicates the root port is on bus #0.

19:15 Device Number (DN) — R O. Indicates the root port is on device #28.

14:12 Function Number (FN) — RO. Indicates the root port is on function #1.

11:0 Reserved

Bit Description

31:24 Target Port Number (PN) — RO. Indicates the target port number is 3h (root port

#3).

23:16 Target Compo nent ID (TCID ) — R/WO. This field returns the value of the ESD .CID

(offset 0104h, bi ts 23 :16 ) field progr amm ed by platform BIOS, since the root port is

in the same component as the RCRB.

15:2 Reserved

1Link Type (LT) — RO. Indicates that the link points to a root port.

Link Valid (LV) — RO. When RPC.PC (offset 0224h, bits 1:0) is ‘11’, or FD.PE3D

(offset 3418h, bit 18) is set, the link for this root port is not valid (return 0). When

RPC.PC is ‘00’, ‘01’, or “10’, and FD.PE3D is cleared, the link for this root port is valid

(return 1).

Bit Description

63:28 Reserved

27:20 Bus Number (BN) — RO. Indicates the root port is on bus #0.

19:15 Device Number (DN) — R O. Indicates the root port is on device #28.

14:12 Function Number (FN) — RO. Indicates the root port is on function #2.

11:0 Reserved

Chipset Configuration Registers

356 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.25 RP4D—Root Port 4 Descriptor Register

Offset Address: 0150–0153h Attribute: R/WO, RO

Default Value: 04xx0002h Size: 32-bit

10.1.26 RP4BA—Root Port 4 Base Address Register

Offset Address: 0158–015Fh Attribute: RO

Default Value: 00000000000E3000h Size: 64-bit

10.1.27 HDD—Intel® High Definition Audio Descriptor Register

Offset Address: 0160–0163h Attribute: R/WO, RO

Default Value: 0Fxx0002h Size: 32-bit

Bit Description

31:24 Target Port Number (PN) — RO. Indicates the target port number is 4h (root port

#4).

23:16 Target Component ID (TCID) — R/WO. This field returns the v alue of the ESD.CID

(offset 0104h, bits 23:16) fie ld progr ammed by platfo rm BIOS, since the root port is

in the same compone nt as the RCRB.

15:2 Reserved

1Link Type (LT) — RO. Indicates that the link points to a root port.

Link Valid (LV) — RO. When RPC.PC (offset 0224h, bits 1:0) is ‘10’ or ‘11’, or

FD. PE4D (offset 3418h, bit 19) is set, the link for this root port is no t valid (return 0).

When RPC.PC is ‘00’ or ‘01’ and FD.PE4D is cleared, the link for this root port is v ali d

(return 1).

Bit Description

63:28 Reserved

27:20 Bus Number (BN) — RO. Indicates the root port is on bus #0.

19:15 Device Number (DN) — RO. Indicates the root port is on device #28.

14:12 Function Number (FN) — RO. Indicates the root port is on function #3.

11:0 Reserved

Bit Description

31:24 Target Port Number (PN) — RO. Indicates the ta rget port number is 15h (Intel®

High Definition Audio).

23:16 Target Component ID (TCID) — R/WO. This field returns the v alue of the ESD.CID

(offset 0104h, bits 23:16) fie ld progr ammed by platfo rm BIOS, since the root port is

in the same compone nt as the RCRB.

15:2 Reserved

1Link Type (LT) — RO. Indicates that the link points to a root port.

0Link Valid (LV) — RO. Whe n FD.ZD (offset 3418h, bit 4) is set, the link to Intel High

Definition Audio is not valid (return 0). When FD.ZD is cleared, the link to Intel High

Definition Audio is valid (return 1).

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 357

Chipset Configuration Registers

10.1.28 HDBA—Intel® High Definition Audio Base Address Register

Offset Address: 0168–016Fh Attribute: RO

Default Value: 00000000000D8000h S i ze: 64-bit

10.1.29 RP5D—Root Port 5 Descriptor Register

Offset Address: 0170–0173h Attribute: R/WO, RO

Default Value: 05xx0002h Size: 32-bit

10.1.30 RP5BA—Root Port 5 Base Address Register

Offset Address: 0178–017Fh Attribute: RO

Default Value: 00000000000E4000h Size: 64-bit

Bit Description

63:28 Reserved

27:20 Bus Number (BN) — RO. Indicates the root port is on bus #0.

19:15 Device Number (DN) — R O. Indicates the root port is on device #27.

14:12 Function Number (FN) — RO. Indicates the root port is on function #0.

11:0 Reserved

Bit Description

31:24 Target Port Number (PN) — RO. Indicates the target port number is 5h (root port

#5).

23:16 Target Compo nent ID (TCID ) — R/WO. This field returns the value of the ESD .CID

(offset 0104h, bi ts 23 :16 ) field progr amm ed by platform BIOS, since the root port is

in the same component as the RCRB.

15:2 Reserved

1Link Type (LT) — RO. Indicates that the link points to a root port.

0Link Valid (LV) — RO. When FD.PE5D (offset 3418h, bit 20) is set, the link for this

root port is not valid (return 0). When FD.PE5D is cleared, the link for this root port is

valid (return 1).

Bit Description

63:28 Reserved

27:20 Bus Number (BN) — RO. Indicates the root port is on bus #0.

19:15 Device Number (DN) — R O. Indicates the root port is on device #28.

14:12 Function Number (FN) — RO. Indicates the root port is on function #4.

11:0 Reserved

Chipset Configuration Registers

358 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.31 RP6D—Root Port 6 Descriptor Register

Offset Address: 0180–0183h Attribute: R/WO, RO

Default Value: 06xx0002h Size: 32-bit

10.1.32 RP6BA—Root Port 6 Base Address Register

Offset Address: 0188–018Fh Attribute: RO

Default Value: 00000000000E5000h Size: 64-bit

10.1.33 ILCL—Internal Link Capabilities List Register

Offset Address: 01A0–01A3h Attribute: RO

Default Value: 00010006h Size: 32-bit

Bit Description

31:24 Target Port Number (PN) — RO. Indicates the target port number is 6h (root port

#6).

23:16 Target Component ID (TCID) — R/WO. This field returns the v alue of the ESD.CID

(offset 0104h, bits 23:16) fie ld progr ammed by platfo rm BIOS, since the root port is

in the same compone nt as the RCRB.

15:2 Reserved

1Link Type (LT) — RO. Indicates that the link points to a root port.

0Link Valid (LV) — RO. When RPC.PC2 (offset 0224h, bits 1:0) is ‘01’ or FD.PE6D

(offset 3418h, bit 21) is set, the link for this root port is not valid (return 0). When

RPC.PC is ‘00’ and FD.PE6D is cleared, the link for this root port is valid (return 1).

Bit Description

63:28 Reserved

27:20 Bus Number (BN) — RO. Indicates the root port is on bus #0.

19:15 Device Number (DN) — RO. Indicates the root port is on device #28.

14:12 Function Number (FN) — RO. Indicates the root port is on function #5.

11:0 Reserved

Bit Description

31:20 Next Capability Offset (NEXT) — RO. Indicates this is the last item in the list.

19:16 Capability Version (CV) — RO. Indicates the version of the capability structure.

15:0 Capability ID (CID) — RO. Indicates this is capability for DMI.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 359

Chipset Configuration Registers

10.1.34 LCAP—Link Capabilities Register

Offset Address: 01A4–01A7h Attribute: R/WO, RO

Default Value: 00012841h Size: 32-bit

10.1.35 LCTL—Link Control Register

Offset Address: 01A8–01A9h Attribute: R/W

Default Value: 0000h Size: 16-bit

10.1.36 LSTS—Link Status Register

Offset Address: 01AA–01ABh Attribute: RO

Default Value: 0041h Size: 16-bit

Bit Description

31:18 Reserved

17:15

(Desktop

Only) Reserved

17:15

(Mobile

Only) L1 Exit Latency (EL1) — RO. L1 is supported on DMI.

14:12 L0s Exit Latency (EL0) — R/WO. This field indic ates that exi t latency is 128 ns to

less than 256 ns.

11:10 Active State Link PM Support (APMS) — R/WO. Indicates that L0s and L1

(Mobile only) are supported on DMI.

9:4 Maximum Link Width (MLW) — RO. Indicates the maximum link width is 4 ports.

3:0 Maximum Link Speed (MLS) — RO. Indicates the link speed is 2.5 Gb/s.

Bit Description

15:8 Reserved

7Extended Synch (ES) — R/W. When set, forces extended transmission of FTS

ordered sets when exiting L0s prior to entering L0.

6:2 Reserved

1:0

Active State Link PM Control (APMC) — R/W. Indicates whether DMI should enter

L0s.

00 = Disabled

01 = L0s entry enabled

10 = Reserved

11 = Reserved

Bit Description

15:10 Reserved

9:4 Negotiated Link Width (NLW) — RO. Negotiated link width is x4 (000100b).

ICH9M may also indicate x2 (000010b), depending on (G)MCH configuration.

3:0 Link Speed (LS) — RO. Link is 2.5 Gb/s.

Chipset Configuration Registers

360 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.37 CIR2 — Chipset Initialization Register 2

Offset Address: 01F4–01F7h Attribute: R/W

Default Value: 00000000h Size: 32-bit

10.1.38 CIR3 — Chipset Initialization Register 3

Offset Address: 01FC–01FDh Attribute: R/W

Default Value: 0000h Size: 16-bit

10.1.39 BCR — Backbone Configuration Register

Offset Address: 0220–0223h Attribute: R/W

Default Value: 00000000h Size: 32-bit

Bit Description

31:0 CIR2 Field 1 — R/W. BIOS shall program to 86000040h

Bit Description

15:11 Reserved

10:8 CIR3 Field 3 — R/W. BIOS must program this field to 110b.

7:4 Reserved

3CIR3 Field 2 — R/W. BIOS must set this bit.

2 Reserved

1:0 CIR3 Field 1 — R/W. BIOS must program this field to 11b.

Bit Description

31:7 Reserved

6BCR Field 2 — R/W. BIOS must set this bit.

5:3 Reserved

2:0 BCR Field 1 — R/W. BIOS program this field to 101b

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 361

Chipset Configuration Registers

10.1.40 RPC—Root Port Configuration Register

Offset Address: 0224–0227h Attribute: R/W, RO

Default Value: 0000000yh (y = 00xxb) Size: 32-bit

Bit Description

31:8 Reserved

High Priority Port Enable (HPE) — R/W.

0 = The high priority path is not enabled.

1 = The port selected by the HPP field in this register is enabled for high priority. It

will be arbitrated above all other VC0 (including integrated VC0) devices.

6:4

High Priorit y Port (HPP) — R/W. This controls which port is enabled for high

priority when the HPE bit in this register is set.

111 = Reserved

110 = Reserved

101 = Port 6

100 = Port 5

101 = Port 4

010 = Port 3

001 = Port 2

000 = Port 1

3 Reserved

Port Configuration2 (PC2) — R/W. This controls how the PCI bridges are organized

in various modes of operation for Ports 5 and 6.

1 = Reserved

0 = 2 x1s, Port 5 (x1), Port 6 (x1)

This bit is in the resume well and is only reset by RSMRST#.

NOTE: Writing to this bit is for debug/testing only. This bit should be treate d as R ead

Only and modifiable only through the GNT2# / GPIO53 pin strap.

1:0

Port Configuration (PC) — R/ W. This controls how the PCI bridges are organized in

various modes of operation for Ports 1-4. For the following mappings, if a port is not

shown, it is considered a x1 port with no connection.

These bits represent the strap values of HDA_SDOUT (bit 1) and HDA_SYNC (bit 0)

when TP[3] is not pulled low at the rising edge of PWROK.

11 = 1 x4, Port 1 (x4)

10 = Reserved

01 = Reserved (Desktop Only)

01 = 1x2 and 2x1s , Port 1 (x2), Port 3 (x1) and Port 4 (x1) (Mobil e Only)

00 = 4 x1s, Port 1 (x1), Port 2 (x1), Port 3 (x1) and Port 4 (x1)

These bits live in the resume well and are only reset by RSMRST#.

NOTE: Writing to these bits is for debug/testing only. These bits should be treated

as Read Only and modifiable only through the HDA_SDOUT and HDA_SYNC

pin straps.

Chipset Configuration Registers

362 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.41 DMIC—DMI Control Register

Offset Address: 0234–0237h Attribute: R/W

Default Value: 00000000h Size: 32-bit

10.1.42 RPFN—Root Port Function Number and Hide for PCI

Express* Root Ports

Offset Address: 0238–023Ch Attribute: R/WO, RO

Default Value: 00543210h Size: 32-bit

For the PCI Express root ports, the assignment of a function number to a root port is

not fixed. BIOS may re-assign the function numbers on a port by port basis. This

capability will allow BIOS to disable/hide any root port and still have functions 0 thru N-

1 where N is the total number of enabled root ports.

Port numbers will remain fixed to a physical root port.

The existing root port Function Disable registers operate on physical ports (not

functions).

Port Configuration (1x4, 4x1, etc.) is not affected by the logical function number

assignment and is associated with physical ports.

Bit Description

31:2 Reserved

1:0 DMI Clock Gate Enable (DMICGEN) — R/W. BIOS must program this field to 11b.

Bit Description

31:24 Reserved

23 Root Port 6 Config Hide (R P6CH) — RW. This bit is used to hide the root port and

any devices behind it from being discov ered by the OS. When set to ‘1’ the root port

will not claim any downstream configuration transactions.

22:20 Root Port 6 Function Number (RP6FN) — R/WO. These bits set the function

number for PCI Express Root Port 6. This root port function number must be a

unique value from the other root port function numbers

19 Root Port 5 Config Hide (RP5CH) — RW. This bit is used to hide the root port and

any devices behind it from being discov ered by the OS. When set to ‘1’ the root port

will not claim any downstream configuration transactions.

18:16 Root Port 5 Function Number (RP5FN) — R/WO. These bits set the function

number for PCI Express Root Port 5. This root port function number must be a

unique value from the other root port function numbers

15 Root Port 4 Config Hide (RP4CH) — RW. This bit is used to hide the root port and

any devices behind it from being discov ered by the OS. When set to ‘1’ the root port

will not claim any downstream configuration transactions.

14:12 Root Port 4 Function Number (RP4FN) — R/WO. These bits set the function

number for PCI Express Root Port 4. This root port function number must be a

unique value from the other root port function numbers

11 Root Port 3 Config Hide (RP3CH) — RW. This bit is used to hide the root port and

any devices behind it from being discov ered by the OS. When set to ‘1’ the root port

will not claim any downstream configuration transactions.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 363

Chipset Configuration Registers

10.1.43 FLRSTAT—FLR Pending Status Register

Offset Address: 0290–0293h Attribute: RO

Default Value: 00000000h Size: 32-bit

10:8 Root Port 3 Function Number (RP3FN) — R/WO. These bits set the function

number for PCI Express Root Port 3. This root port function number must be a

unique value from the other root port function numbers

7Root Port 2 Config Hide (RP2CH) — RW . This bit is used to hide the root port and

any devices behind it from being discovered by the OS . When set to ‘1’ the root port

will not claim any downstream configuration transactions.

6:4 Root Port 2 Function Number (RP2FN) — R/WO. These bits set the function

number for PCI Express Root Port 2. This root port function number must be a

unique value from the other root port function numbers

3Root Port 1 Config Hide (RP1CH) — RW . This bit is used to hide the root port and

any devices behind it from being discovered by the OS . When set to ‘1’ the root port

will not claim any downstream configuration transactions.

2:0 Root Port 1 Function Number (RP1FN) — R/WO. These bits set the function

number for PCI Express Root Port 1. This root port function number must be a

unique value from the other root port function numbers

Bit Description

31:24 Reserved.

23 FLR Pending Status for D29:F7, EHCI #1 — R0.

0 = Function Level Reset is not pending.

1 = Function Level Reset is pending.

22:20 Reserved.

19 FLR Pending Status for D29:F3, UHCI #6 — R0.

0 = Function Level Reset is not pending.

1 = Function Level Reset is pending.

18 FLR Pending Status for D29:F2, UHCI #3 — R0.

0 = Function Level Reset is not pending.

1 = Function Level Reset is pending.

17 FLR Pending Status for D29:F1, UHCI #2 — R0.

0 = Function Level Reset is not pending.

1 = Function Level Reset is pending.

16 FLR Pending Status for D29:F0, UHCI #1 — R0.

0 = Function Level Reset is not pending.

1 = Function Level Reset is pending.

15 FLR Pending Status for D26:F7, EHCI #2 — R0.

0 = Function Level Reset is not pending.

1 = Function Level Reset is pending.

14:11 Reserved.

10 FLR Pending Status for D26:F2, UHCI #6 — R0.

0 = Function Level Reset is not pending.

1 = Function Level Reset is pending.

Chipset Configuration Registers

364 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.44 CIR13—Chipset Initialization Register 13

Offset Address: 0F20h–0F23h Attribute: R/W

Default Value: B2B477CCh Size: 32-bit

10.1.45 CIR5—Chipset Initialization Register 5

Offset Address: 1D40h–1D47h Attribute: R/W

Default Value: 0000000000000000h Size: 64-bit

10.1.46 TRSR—Trap Status Register

Offset Address: 1E00–1E03h Attribute: R/WC, RO

Default Value: 00000000h Size: 32-bit

9FLR Pending Status for D26:F1, UHCI #5 — R0.

0 = Function Level Reset is not pending.

1 = Function Level Reset is pending.

8FLR Pending Status for D26:F0, UHCI #4 — R0.

0 = Function Level Reset is not pending.

1 = Function Level Reset is pending.

7:0 Reserved.

Bit Description

31:20 Reserved

19:16 CIR13 Field 1 — R/W. BIOS must program this field to 0101b.

15:0 Reserved

Bit Description

63:1 Reserved

0CIR5 Field 1 — R/W. BIOS must program this field to 1b.

Bit Description

31:4 Reserved

3:0

Cycle Trap SMI# Status (CTSS ) — R/WC. These bits are set by hardware when the

corresponding Cycle Trap register is enabled and a matching cycle is received (and

trapped). These bits are OR’ed together to create a single status bit in the Power

Management register space.

Note that the SMI# and trapping must be enabled in order to set these bits.

These bits are set before the completion is generated for the trapped cycle, thereby

ensuring that the processor can enter the SMI# handler when the instruction

completes. Each status bit is cleared by writing a 1 to the corresponding bit location

in this register.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 365

Chipset Configuration Registers

10.1.47 TRCR—Trapped Cycle Register

Offset Address: 1E10–1E17h Attribute: RO

Default Value: 0000000000000000h Size : 64-bit

This register saves information about the I/O Cycle that was tr apped and generated the

SMI# for software to read.

10.1.48 TWDR—Trapped Write Data Register

Offset Address: 1E18–1E1Fh Attribute: RO

Default Value: 0000000000000000h Size : 64-bit

This register saves the data from I/O write cycles that are trapped for software to read.

Bit Description

63:25 Reserved

24 Read/Write# (RWI) — RO.

0 = Trapped cycle was a write cycle.

1 = Trapped cycle was a read cycle.

23:20 Reserved

19:16 Active-high Byte Enables (AHBE) — RO. This is the dword-aligned byte enables

associated with the trapped cycle. A 1 in any bit locatio n indicates that the

corresponding byte is enabled in the cycle.

15:2 Trapped I/O Address (TIOA) — RO. This is the dword-aligned address of the

trapped cycle.

1:0 Reserved

Bit Description

63:32 Reserved

31:0 Trapped I/O Data (TIOD) — RO. Dword of I/O write data. This field is undefined

after trapping a read cycle.

Chipset Configuration Registers

366 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.49 IOTRn — I/O Trap Register (0-3)

Offset Address: 1E80–1E87h Register 0 Attribute: R/W

1E88–1E8Fh Register 1

1E90–1E97h Register 2

1E98–1E9Fh Register 3

Default Value: 0000000000000000h Size: 64-bit

These registers are used to specify the set of I/O cycles to be trapped and to enable

this functionality.

Bit Description

63:50 Reserved

49 Read/Write Mask (RWM) — R/W.

0 = The cycle must ma tch the type specified in bit 48.

1 = Trapping logic will operate on both read and write cycles.

Read/Write# (RWIO) — R/W.

0 = Write

1 = Read

NOTE: The value in this field does not ma tter if bit 49 is set.

47:40 Reserved

39:36 Byte Enable Mask (BEM) — R/W. A 1 in any bit position indicates that any value in

the corresponding byte enable bit in a received cycle will be treated as a match. The

corresponding bit in the Byte Enables field, below, is ignored.

35:32 Byte Enables (TBE) — R/W. Active-high dword-aligned byte enables.

31:24 Reserved

23:18

Address[7:2] Mask (ADMA) — R/W. A 1 in any bit position indicates that any v alue

in the corresponding address bit in a received cycle will be treated as a match. The

corresponding bit in the Address field, below, is ignored. The mask is only provided

for the lower 6 bits of the dword address, allowing for traps on address ranges up to

256 bytes in size.

17:16 Reserved

15:2 I/O Address[15:2] (IOAD) — R/W. dword-aligned address

1 Reserved

0Trap and SMI# Enable (TRSE) — R/W.

0 = Trapping and SMI# logic disabled.

1 = The trapping logic specified in this register is enabled.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 367

Chipset Configuration Registers

10.1.50 DMC—DMI Miscellaneous Control Register

Offset Address: 2010–2013h Attribute: R/W

Default Value: 00000002h Size: 32-bit

10.1.51 CIR6—Chipset Initialization Register 6

Offset Address: 2024–2027h Attribute: R/W

Default Value: 0B4030C0h Size: 32-bit

Bit Description

31:20 Reserved

DMI Misc. Control Field 1 — R/W. BIOS shall always program this field as per the

BIOS Specification.

0 = Disable DMI Power Savings.

1 = Enable DMI Power Savings.

18:12 Reserved

11:10

(Mobile

Only) DMI Misc. Control Field 2 — R/W. BIOS shall set these bits to 11b

11:10

(Desktop

Only) Reserved

9:0 Reserved

Bit Description

31:24

(Mobile

Only) Reserved

23:21

(Mobile

Only) CIR6 Field 2 — R/W. BIOS must program this field to 011b.

20:8

(Mobile

Only) Reserved

31:8

(Desktop

Only) Reserved

7CIR6 Field 1 — R/W. BIOS must clear this bit.

6:0 Reserved

Chipset Configuration Registers

368 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.52 CIR7—Chipset Initialization Register 7

Offset Address: 2034–2037h Attribute: R/W

Default Value: B2B477CCh Size: 32-bit

10.1.53 CIR11—Chipset Initialization Register 11 (Mobile Only)

Offset Address: 20C4–20C5h Attrib ute: R/W

Default Value: 0000h Size: 16-bit

10.1.54 CIR12—Chipset Initialization Register 12 (Mobile Only)

Offset Address: 20E4–20E5h Attribute: R/W

Default Value: 0000h Size: 16-bit

Bit Description

31:20 Reserved

19:16 CIR7 Field 1 — R/W. BIOS must program this field to 0101b.

15:0 Reserved

Bit Description

15 CIR11 Field 1— R/W. BIOS may program this field to 1b.

14:0 Reserved

Bit Description

15 CIR12 Field 1— R/W. BIOS may program this field to 1b.

14:0 Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 369

Chipset Configuration Registers

10.1.55 TCTL—TCO Configuration Register

Offset Address: 3000–3000h Attribute: R/W

Default Value: 00h Size: 8-bit

10.1.56 D31IP—Device 31 Interrupt Pin Register

Offset Address: 3100–3103h Attribute: R/W, RO

Default Value: 03243200h Size: 32-bit

Bit Description

7TCO IRQ Enable (IE) — R/W.

0 = TCO IRQ is disabled.

1 = TCO IRQ is en abled, as selected by the TCO_IRQ_SEL field.

6:3 Reserved

2:0

TCO IRQ Select (IS) — R/W. Specifies on whic h IRQ the TCO wil l inte rnall y appear.

If not using the APIC, the TCO interrupt must be routed to IRQ9-11, and that

interrupt is not sharable with the SERIRQ stream, but is shareable with other PCI

interrupts. If using the APIC, the TCO interrupt can also be mapped to IRQ20-23, and

can be shared with other interrupt.

000 = IRQ 9

001 = IRQ 10

010 = IRQ 11

011 = Reserved

100 = IRQ 20 (only if APIC enabled)

101 = IRQ 21 (only if APIC enabled)

110 = IRQ 22 (only if APIC enabled)

111 = IRQ 23 (only if APIC enabled)

When setting the these bits, the IE bit should be cleared to prevent glitching.

When the interrupt is mapped to APIC interrupts 9, 10 or 11, the APIC should be

programmed for active-high reception. When the interrupt is mapped to APIC

interrupts 20 through 23, the APIC should be programmed for active-low reception.

Bit Description

31:28 Reserved

27:24

Thermal Throttle Pin (TTIP) — R/W. Indicates which pin the Th ermal Throttle

controller drives as its interrupt

0h = No interrupt

1h = INTA#

2h = INTB# (Default)

3h = INTC#

4h = INTD#

5h–Fh = Reserved

23:20

SATA Pin 2 (SIP2) — R/W. Indicates which pin the SATA controller 2 drives as its

interrupt.

0h = No interrupt

1h = INTA#

2h = INTB# (Default)

3h = INTC#

4h = INTD#

5h–Fh = Reserved

19:16 Reserved

Chipset Configuration Registers

370 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.57 D30IP—Device 30 Interrupt Pin Register

Offset Address: 3104–3107h Attribute: RO

Default Value: 00000000h Size: 32-bit

15:12

SM Bus Pin (SMIP) — R/W. Indicates which pin the SMBus controller drives as its

interrupt.

0h = No interrupt

1h = INTA#

2h = INTB# (Default)

3h = INTC#

4h = INTD#

5h–Fh = Reserved

11:8

SATA Pin (SIP) — R/W. Indicates which pin the SATA controller drives as its

interrupt.

0h = No interrupt

1h = INTA#

2h = INTB# (Default)

3h = INTC#

4h = INTD#

5h–Fh = Reserved

7:4 Reserved

3:0 LPC Bridge Pin (LIP) — RO. Currently, the LPC bridge does not gener ate an in terrupt,

so this field is read-only and 0.

Bit Description

31:4 Reserved

3:0 PCI Bridge Pin (PIP) — RO. Currentl y, the PCI bridge does not generate an interrupt,

so this field is read-only and 0.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 371

Chipset Configuration Registers

10.1.58 D29IP—Device 29 Interrupt Pin Register

Offset Address: 3108–310Bh Attribute: R/W

Default Value: 10004321h Size: 32-bit

Bit Description

31:28

EHCI Pin (EIP) — R/W. Indicates which pin the EHCI controller #1 drives as its

interrupt.

0h = No interrupt

1h = INTA# (Default)

2h = INTB#

3h = INTC#

4h = INTD#

5h-7h = Reserved

27:16 Reserved

15:12

UHCI #6 Pin (U3P) — R/W. Indicat es which pin the UHCI controller #6 (Device 29

Function 3) drives as its interrupt, if contro ller exists

0h = No interrupt

1h = INTA#

2h = INTB#

3h = INTC#

4h = INTD# (Default)

5h-7h = Reserved

NOTE: This field should be set to 0h when UHCI Controller #6 Remap bit (RCBA

offset 35F0h:bit 0) is set to 0.

11:8

UHCI #3 Pin (U2P) — R/W. Indicat es which pin the UHCI controller #3 (Device 29

Function 2) drive s as its interrup t.

0h = No interrupt

1h = INTA#

2h = INTB#

3h = INTC# (Default)

4h = INTD#

5h-7h = Reserved

7:4

UHCI #2 Pin (U1P) — R/W. Indicat es which pin the UHCI controller #2 (Device 29

Function 1) drive s as its interrup t.

0h = No interrupt

1h = INTA#

2h = INTB# (Default)

3h = INTC#

4h = INTD#

5h-7h = Reserved

3:0

UHCI #1 Pin (U0P) — R/W. Indicat es which pin the UHCI controller #1 (Device 29

Function 0) drive s as its interrup t.

0h = No interrupt

1h = INTA# (Default)

2h = INTB#

3h = INTC#

4h = INTD#

5h-7h = Reserved

Chipset Configuration Registers

372 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.59 D28IP—Device 28 Interrupt Pin Register

Offset Address: 310C–310Fh Attribute: R/W

Default Value: 00214321h Size: 32-bit

Bit Description

31:16 Reserved

23:20

PCI Express* #6 Pin (P6IP) — R/W. Indicates which pin the PCI Express* port #6

drives as its interrupt.

0h = No interrupt

1h = INTA#

2h = INTB# (Default)

3h = INTC#

4h = INTD#

5h-7h = Reserved

19:16

PCI Express #5 Pin (P5 I P ) — R/W. Indicates which pin the PCI Express port #5

drives as its interrupt.

0h = No interrupt

1h = INTA# (Default)

2h = INTB#

3h = INTC#

4h = INTD#

5h-7h = Reserved

15:12

PCI Express #4 Pin (P4 I P ) — R/W. Indicates which pin the PCI Express* port #4

drives as its interrupt.

0h = No interrupt

1h = INTA#

2h = INTB#

3h = INTC#

4h = INTD# (Default)

5h-7h = Reserved

11:8

PCI Express #3 Pin (P3 I P ) — R/W. Indicates which pin the PCI Express port #3

drives as its interrupt.

0h = No interrupt

1h = INTA#

2h = INTB#

3h = INTC# (Default)

4h = INTD#

5h-7h = Reserved

7:4

PCI Express #2 Pin (P2 I P ) — R/W. Indicates which pin the PCI Express port #2

drives as its interrupt.

0h = No interrupt

1h = INTA#

2h = INTB# (Default)

3h = INTC#

4h = INTD#

5h-7h = Reserved

3:0

PCI Express #1 Pin (P1 I P ) — R/W. Indicates which pin the PCI Express port #1

drives as its interrupt.

0h = No interrupt

1h = INTA# (Default)

2h = INTB#

3h = INTC#

4h = INTD#

5h-7h = Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 373

Chipset Configuration Registers

10.1.60 D27IP—Device 27 Interrupt Pin Register

Offset Address: 3110–3113h Attribute: R/W

Default Value: 00000001h Size: 32-bit

Bit Description

31:4 Reserved

3:0

Intel® High Definition Audio Pin (ZIP) — R/W. Indicates which pin the Intel High

Definition Audio controller drives as its interrupt.

0h = No interrupt

1h = INTA# (Default)

2h = INTB#

3h = INTC#

4h = INTD#

5h-Fh = Reserved

Chipset Configuration Registers

374 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.61 D26IP—Device 26 Interrupt Pin Register

Offset Address: 3114–3117h Attribute: R/W

Default Value: 30000321h Size: 32-bit

Bit Description

31:28

EHCI #2 Pin (E2IP) — R/W. Indicates which pin the EHCI controller #2 drives as its

interrupt:

0h = No Interrupt

1h = INTA#

2h = INTB#

3h = INTC# (Default)

4h = INTD#

5h-Fh = Reserved

27:12 Reserved

11:8

UHCI #6 Pin (U2P) — R/W. Indicates which pin UHCI controller #6 (Device 26

Function 2) drives as its interrupt, if controller exists.

0h = No Interrupt

1h = INTA#

2h = INTB#

3h = INTC# (Default)

4h = INTD#

5h-Fh = Reserved

NOTE: This field should be set to 0h when UHCI Controller #6 Remap bit (RCBA

offset 35F0h:bit 0) is set to 1.

7:4

UHCI #5 Pin (U1P) — R/W. Indicates which pin UHCI controller #5 (Device 26

Function 1), drives as its interrupt.

0h = No Interrupt

1h = INTA#

2h = INTB# (Default)

3h = INTC#

4h = INTD#

5h-Fh = Reserved

3:0

UHCI #4 Pin (U0P) — R/W. Indicates which pin UHCI controller #4 (Device 26

Function 0) , drives as its interrupt.

0h = No Interrupt

1h = INTA# (Default)

2h = INTB#

3h = INTC#

4h = INTD#

5h-Fh = Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 375

Chipset Configuration Registers

10.1.62 D25IP—Device 25 Interrupt Pin Register

Offset Address: 3118–311Bh Attribute: R/W

Default Value: 00000001h Size: 32-bit

10.1.63 D31IR—Device 31 Interrupt Route Register

Offset Address: 3140–3141h Attribute: R/W

Default Value: 3210h Size: 16-bit

Bit Description

31:4 Reserved

3:0

GBE LAN Pin (LIP) — R/W. Indicates which pin the in ternal GbE LAN controller

drives as its interrupt

0h = No Interrupt

1h = INTA# (Default)

2h = INTB#

3h = INTC#

4h = INTD#

5h-Fh = Reserved

Bit Description

15 Reserved

14:12

Interrupt D Pin Route (IDR) — R/W. Indicates which physical pin on the Intel®

ICH is connected to the INTD# pin reported for device 31 functions.

0h = PIRQA#

1h = PIRQB#

2h = PIRQC#

3h = PIRQD# (Default)

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

11 Reserved

10:8

Interrupt C Pin Route (ICR) — R/W. Indicates which physical pin on the ICH is

connected to th e INTC# pin reported for device 31 functions.

0h = PIRQA#

1h = PIRQB#

2h = PIRQC# (Default)

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

7 Reserved

Chipset Configuration Registers

376 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.64 D30IR—Device 30 Interrupt Route Regist er

Offset Address: 3142–3143h Attribute: RO

Default Value: 0000h Size: 16-bit

6:4

Interrupt B Pin Route (IBR) — R/W. Indicates which physical pi n on the ICH is

connected to the INTB# pin reported for device 31 functions.

0h = PIRQA#

1h = PIRQB# (Default)

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

3 Reserved

2:0

Interrupt A Pin Route (IAR) — R/W. Indicates which physical pin on the ICH is

connected to the INTA# pin reported for device 31 functions.

0h = PIRQA# (Defau lt)

1h = PIRQB#

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

Bit Description

15:0 Reserved. No interrupts generated from Device 30.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 377

Chipset Configuration Registers

10.1.65 D29IR—Device 29 Interrupt Route Register

Offset Address: 3144–3145h Attribute: R/W

Default Value: 3210h Size: 16-bit

Bit Description

15 Reserved

14:12

Interrupt D Pin Route (IDR) — R/W. Indicates which physical pin on the Intel®

ICH is connected to the INTD# pin reported for device 29 functions.

0h = PIRQA#

1h = PIRQB#

2h = PIRQC#

3h = PIRQD# (Default)

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

11 Reserved

10:8

Interrupt C Pin Route (ICR) — R/W. Indicates which physical pin on the ICH is

connected to th e INTC# pin reported for device 29 functions.

0h = PIRQA#

1h = PIRQB#

2h = PIRQC# (Default)

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

7 Reserved

6:4

Interrupt B Pin Route (IBR) — R/W. Indicates which physical pin on the ICH is

connected to th e INTB# pin reported for device 29 functions.

0h = PIRQA#

1h = PIRQB# (Default)

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

3 Reserved

2:0

Interrupt A Pin Route (IAR) — R/W. In dicates which physical pin o n the ICH is

connected to th e INTA# pin reported for device 29 functions.

0h = PIRQA# (Default)

1h = PIRQB#

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

Chipset Configuration Registers

378 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.66 D28IR—Device 28 Interrupt Route Regist er

Offset Address: 3146–3147h Attribute: R/W

Default Value: 3210h Size: 16-bit

Bit Description

15 Reserved

14:12

Interrupt D Pin Route (IDR) — R/W. Indicates which physical pin on the Intel®

ICH is connected to the INTD# pin reported for device 28 functions.

0h = PIRQA#

1h = PIRQB#

2h = PIRQC#

3h = PIRQD# (Default)

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

11 Reserved

10:8

Interrupt C Pin Route (ICR) — R/W. Indicates which physical pin on the ICH is

connected to the INTC# pin reported for device 28 functions.

0h = PIRQA#

1h = PIRQB#

2h = PIRQC# (Default)

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

7 Reserved

6:4

Interrupt B Pin Route (IBR) — R/W. Indicates which physical pi n on the ICH is

connected to the INTB# pin reported for device 28 functions.

0h = PIRQA#

1h = PIRQB# (Default)

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

3 Reserved

2:0

Interrupt A Pin Route (IAR) — R/W. Indicates which physical pin on the ICH is

connected to the INTA# pin reported for device 28 functions.

0h = PIRQA# (Defau lt)

1h = PIRQB#

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 379

Chipset Configuration Registers

10.1.67 D27IR—Device 27 Interrupt Route Register

Offset Address: 3148–3149h Attribute: R/W

Default Value: 3210h Size: 16-bit

Bit Description

15 Reserved

14:12

Interrupt D Pin Route (IDR) — R/W. Indicates which physical pin on the Intel®

ICH is connected to the INTD# pin reported for device 27 functions.

0h = PIRQA#

1h = PIRQB#

2h = PIRQC#

3h = PIRQD# (Default)

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

11 Reserved

10:8

Interrupt C Pin Route (ICR) — R/W. Indicates which physical pin on the ICH is

connected to th e INTC# pin reported for device 27 functions.

0h = PIRQA#

1h = PIRQB#

2h = PIRQC# (Default)

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

7 Reserved

6:4

Interrupt B Pin Route (IBR) — R/W. Indicates which physical pin on the ICH is

connected to th e INTB# pin reported for device 27 functions.

0h = PIRQA#

1h = PIRQB# (Default)

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

3 Reserved

2:0

Interrupt A Pin Route (IAR) — R/W. In dicates which physical pin o n the ICH is

connected to th e INTA# pin reported for device 27 functions.

0h = PIRQA# (Default)

1h = PIRQB#

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

Chipset Configuration Registers

380 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.68 D26IR—Device 26 Interrupt Route Regist er

Offset Address: 314C–314Dh Attribute: R/W

Default Value: 3210h Size: 16-bit

Bit Description

15 Reserved

14:12

Interrupt D Pin Route (IDR) — R/W. Indicates which physical pin on the ICH is

connected to the INTD# pin reported for device 26 functions:

0h = PIRQA#

1h = PIRQB#

2h = PIRQC#

3h = PIRQD# (Default)

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

11 Reserved

10:8

Interrupt C Pin Route (ICR) — R/W. Indicates which physical pin on the ICH is

connected to the INTC# pin reported for device 26 functions.

0h = PIRQA#

1h = PIRQB#

2h = PIRQC# (Default)

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

7 Reserved

6:4

Interrupt B Pin Route (IBR) — R/W. Indicates which physical pi n on the ICH is

connected to the INTB# pin reported for device 26 functions.

0h = PIRQA#

1h = PIRQB# (Default)

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

3 Reserved

2:0

Interrupt A Pin Route (IAR) — R/W. Indicates which physical pin on the ICH is

connected to the INTA# pin reported for device 26 functions.

0h = PIRQA# (Defau lt)

1h = PIRQB#

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 381

Chipset Configuration Registers

10.1.69 D25IR—Device 25 Interrupt Route Register

Offset Address: 3150–3151h Attribute: R/W

Default Value: 3210h Size: 16-bit

Bit Description

15 Reserved

14:12

Interrupt D Pin Route (IDR): — R/W. Indicates which physical pin on the ICH is

connected to the INTD# pin reported for device 25 functions:

0h = PIRQA#

1h = PIRQB#

2h = PIRQC#

3h = PIRQD# (Default)

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

11 Reserved

10:8

Interrupt C Pin Route (ICR) — R/W. Indicates which physical pin on the ICH is

connected to th e INTC# pin reported for device 25 functions.

0h = PIRQA#

1h = PIRQB#

2h = PIRQC# (Default)

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

7 Reserved

6:4

Interrupt B Pin Route (IBR) — R/W. Indicates which physical pin on the ICH is

connected to th e INTB# pin reported for device 25 functions.

0h = PIRQA#

1h = PIRQB# (Default)

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

3 Reserved

2:0

Interrupt A Pin Route (IAR) — R/W. In dicates which physical pin o n the ICH is

connected to th e INTA# pin reported for device 25 functions.

0h = PIRQA# (Default)

1h = PIRQB#

2h = PIRQC#

3h = PIRQD#

4h = PIRQE#

5h = PIRQF#

6h = PIRQG#

7h = PIRQH#

Chipset Configuration Registers

382 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.70 OIC—Other Interrupt Control Register

Offset Address: 31FF–31FFh Attribute: R/W

Default Value: 00h Size: 8-bit

10.1.71 SBEMC3—Scheduled Break Event C3 Exit Latency (Mobile

Only)

Offset Address: 3300–3303h Attribute: R/W

Default Value: 00000000h Size: 32-bit

Bit Description

7:4

APIC Range Sele ct (AS E L) — R/W.These bits define address bits 15:12 for the

IOxAPIC range. The default value of 0h enables compatibility with prior ICH products

as an initial value. This value must not be changed unless the IOxAPIC Enable bit is

cleared.

3:2 Reserved

Coprocessor Error Enable (CEN) — R/W.

0 = FERR# will not generate IRQ13 nor IGNNE#.

1 = If FERR# is low, the Intel® ICH9 gener ates IRQ13 internally and holds it until an

I/O port F0h write. It will also drive IGNNE# active.

APIC Enable (AEN) — R/W.

0 = The internal IOxAPIC is disabled.

1 = Enables the internal IOxAPIC and its address decode.

NOTE: SW should read this register afte r modifying APIC enable bit prior to access to

the IOxAPIC address range.

Bit Description

31:23 Reserved.

22:16 Present State C3 Future State C3 Exit Laten cy ( C3C3EL) — R/W.

Sets exit latency if present and future C-state is C3.

15 Reserved.

14:8 Present State C2 Future State C3 Exit Laten cy (C2C3EL) — R/W.

Sets exit latency if present c-state is C2 and future C-state is C3.

7 Reserved.

6:0 Present State C0 Future State C3 Exit Latency (C0C3EL) — R/W.

Sets exit latency if present c-state is C0 and future C-state is C3.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 383

Chipset Configuration Registers

10.1.72 SBEMC4—Scheduled Break Event C4 Exit Latency (Mobile

Only)

Offset Address: 3304–3307h Attribute: R/W

Default Value: 00000000h Size: 32-bit

10.1.73 RC—RTC Configuration Register

Offset Address: 3400–3403h Attribute: R/W, R/WLO

Default Value: 00000000h Size: 32-bit

Bit Description

31 Reserved.

30:24 Present State C4 Future State C4 E x it Latency (C4C4EL) — R/W.

Sets exit latency if present and fu ture c-state is C4.

22:16 Present State C3 Future State C4 E x it Latency (C3C4EL) — R/W.

Sets exit latency if present c-st ate is C3 and future C-state is C4.

15 Reserved.

14:8 Present State C2 Future State C4 E x it Latency (C2C4EL) — R/W.

Sets exit latency if present c-st ate is C2 and future C-state is C4.

7 Reserved.

6:0 Present State C0 Future State C4 E x it Latency (C0C4EL) — R/W.

Sets exit latency if present c-st ate is C0 and future C-state is C4.

Bit Description

31:5 Reserved

Upper 128 Byte Lock (UL) — R/WLO.

0 = Bytes not locked.

1 = Bytes 38h-3Fh in the upper 128-byte bank of R T C RAM are locked and cannot be

accessed. Writes will be dropped and reads will not return any ensured data. Bit

reset on system reset.

Lower 128 Byte Lock (LL) — R/WLO.

0 = Bytes not locked.

1 = Bytes 38h-3Fh in the lower 128-byte ba nk of RT C RAM are lock ed and cannot be

accessed. Writes will be dropped and reads will not return any ensured data. Bit

reset on system reset.

2Upper 128 Byte Enable (UE) — R/W.

0 = Bytes locked.

1 = The upper 128-byte bank of RTC RAM can be accessed.

1:0 Reserved

Chipset Configuration Registers

384 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.74 HPTC—High Precision Timer Configuration Register

Offset Address: 3404–3407h Attribute: R/W

Default Value: 00000000h Size: 32-bit

Bit Description

31:8 Reserved

Address Enable (AE) — R/W.

0 = Address disabled.

1 = The Intel® ICH9 will decode the High Precision Timer memory address range

selected by bits 1:0 below.

6:2 Reserved

1:0

Address Select (AS) — R/W. This 2-bit field select s 1 of 4 possible memory address

ranges for the High Precision Timer functionality. The encodings are:

00 = FED0_0000h – FED0_03FFh

01 = FED0_1000h – FED0_13FFh

10 = FED0_2000h – FED0_23FFh

11 = FED0_3000h – FED0_33FFh

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 385

Chipset Configuration Registers

10.1.75 GCS—General Control and Status Register

Offset Address: 3410–3413h Attribute: R/W, R/WLO

Default Value: 00000yy0h (yy = xx0000x0b)Size: 32-bit

Bit Description

31:13 Reserved.

Function Level Reset Capability Structure Select (FLRCSSEL) — R/W.

0 = Function Level Reset (FLR) will utilize the standard capability structure with

unique capability ID assigned by PCISIG.

1 = Vendor Specific Capability Structure is selected for FLR.

11:10

Boot BIOS Straps (BBS) — R/W. This field determines the destination of accesses

to the BIOS memory range. The defau lt values for these bits represent the strap

values of GNT0# (bit 11) at the rising edge of PWROK and SPI_CS1#/GPIO58

(Desktop Only) /CLGPIO6 (Digital Office Only) (bit 10) at the rising edge of

CLPWROK.

When PCI is selected, the top 16MB of memory below 4GB (FF00_0000h to

FFFF_FFFFh) is accepted by the primary side of the PCI P2P bridge and forwarded to

the PCI bus. This allo ws systems with co rrupted or unprogrammed flash to boot from

a PCI device. The PCI-to-PCI bridge Memory Space Enable bit does not need to be set

(nor any other bits) in order for these cycles to go to PCI. Note that BIOS decode

range bits and the other BIOS protection bits have no effect when PCI is selected.

This functionality is intended for debug/testing only.

When SPI or LPC is selected, the range that is decoded is further qualified by other

configuration bits described in the respective sections.

The value in this field can be overwritten by software as long as the BIOS Interface

Lock-Down (bit 0) is not set .

NOTE: Booting to PCI is intended for debug/testing only. Boot BIOS Destination

Select to LPC/PCI by functional strap or via Boot BIOS Destination Bit will not

affect SPI accesses initiated by Management Engine or Integrated GbE LAN.

Server Error Reporting Mode (SERM) — R/W.

0 = The Intel® ICH9 is the final target of all erro rs. The (G)MCH sends a messages to

the ICH for the purpose of generating NMI.

1 = The (G)MCH is the final target of all errors from PCI Express* and DMI. In this

mode, if the ICH9 detects a fatal, non-fatal, or correctable error on DMI or its

downstream ports, it sen d s a message to the (G)MCH. If the ICH9 receives an

ERR_* message from the downstream port, it sends that message to the

(G)MCH.

8:7 Reserved

FERR# MUX Enable (FME) — R/W. This bit enables FERR# to be a processor break

event indication.

0 = Disabled.

1 = The ICH9 examines FERR# during a C2, C3, or C4 state as a break event.

See Chapter 5.13.5 for a functional description.

Bits 11:10 Description

0xb SPI

10b PCI

11b LPC

Chipset Configuration Registers

386 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

No Reboot (NR) — R/W. This bit is set when the “No Reboot” strap (SPKR pin on

ICH9) is sampled high on PWROK. This bit may be set or cleared by software if the

strap is sampled low but may not override the strap when it indicates “No Reboot”.

0 = System will reboot upon the second timeout of the TCO timer.

1 = The TCO timer will count down and generate the SMI# o n the first timeout, but

will not reboot on the second timeout.

Alternate Access Mode Enable (AME) — R/W.

0 = D isabled.

1 = Alternate access read only registers can be written, and write only registers can

be read. Before entering a low power state, sev eral regi sters from powered down

parts may need to be saved. In the majority of cases, this is not an issue, as

registers have read and write paths. However, several of the ISA compa t ible

registers are either read only or write only. To get data out of write-only

registers, and to restore data into read-only registers, the ICH implements an

alternate access mode. For a list of these registers see Section 5.13.10.

Shutdown Policy Sele ct (SPS) — R/W. When cl eared ( def aul t), t he ICH9 will driv e

INIT# in response to the shutdown Ven dor Defined Message (VDM). When set to 1,

ICH9 will treat the shutdown VDM similar to receiving a CF9h I/O write with data

value06h, and will drive PLTRST# active.

Reserved Page Route (RPR) — R/W. Determines where to send the reserved page

registers. These addresses are sent to PCI or LPC for the purpose of generating POST

codes. The I/O addresses modified by this field are: 80h, 84h, 85h, 86h, 88h, 8Ch,

8Dh, and 8Eh.

0 = Writes will be forwarded to LPC, shadowed within the ICH, and reads will be

returned from the internal shadow

1 = Writes will be forwarded to PCI, shadowed within the ICH, and reads will be

returned from the internal shadow.

Note, if some writes are do ne to LPC/PCI to these I/O ranges, and then thi s bit is

flipped, such that writes will now go to the other interface, the reads will not return

what was last written. Shadowing is performed on each interface.

The aliases for these registers, at 90h, 94h, 95h, 96h, 98h, 9Ch, 9Dh, and 9Eh, are

always decoded to LPC.

1 Reserved

BIOS Interface Lock-Down (BILD) — R/WLO.

0 = D isabled.

1 = Prevents BUC.TS (offset 3414, bit 0) and GCS.BBS (offset 3410h, bits 11:10)

from being changed. This bit can only be written from 0 to 1 once.

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 387

Chipset Configuration Registers

10.1.76 BUC—Backed Up Control Register

Offset Address: 3414–3414h Attribute: R/W

Default Value: 0000000xb Size: 8-bit

All bits in this register are in the RTC well and only cleared by RTCRST#

Bit Description

7:6 Reserved

LAN Disable — R/W.

0 = LAN is Enabled

1 = LAN is Disabled.

This bit is locked by the Function Disable SUS Well Lockdown register. Once locked

this bit can not be changed by software.

Daylight Sav ings Override (SDO) — R/W.

0 = Daylight Savings is Enabled.

1 = The DSE bit in RTC Register B is set to Read-only with a value of 0 to disable

daylight savings.

3Reserved

CPU BIST Enable (CBE) — R/W. This bit is in the resume well and is reset by

RSMRST#, but not PLTRST# nor CF9h writes.

0 = Disabled.

1 = The INIT# signals will be driven active when CPURST# is active. INIT# and

INIT3_3V# will go inactive with the same timings as the other processor

interface signals (hold time after CPURST# inactive).

1 Reserved

Top Swap (TS) — R/W.

0 = Intel® ICH9 will not invert A16.

1 = ICH9 will invert A16 for cycles going to the BIOS space (but not the feature

space) in the FWH.

If ICH is strapped for Top-Swap (GNT3# is low at rising edge of PWROK), then this bit

cannot be cleared by software. The strap jumper should be removed and the system

rebooted.

Chipset Configuration Registers

388 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.77 FD—Function Disable Register

Offset Address: 3418–341Bh Attribute: R/W

Default Value: See bit description Size: 32-bit

The UHCI functions must be disabled from highest function number to lowest within

each PCI device (Device 29 or Device 26). For example, if only two UHCIs are wanted

on Device 29, software must disable UHCI #3 (UD3 bit set). When disabling UHCIs, the

EHCI Structural Parameters Registers must be updated with coherent information in

“Number of Companion Controllers” and “N_Ports” fields.

When disabling a function, only the configuration space is disabled. Software must

ensure that all functionality within a controller that is not desired (such as memory

spaces, I/O spaces, and DMA engines) is disabled prior to disabli ng the function.

When a function is disabled, software must not attempt to re-enable it. A disabled

function can only be re-enabled by a platform reset.

Bit Description

31:26 Reserved

25 Serial ATA Disable 2 (SAD2) — R/W. Default is 0.

0 = The SATA controller #2 (D31:F5) is enabled.

1 = The SATA controller #2 (D31:F5) is disabled.

24 Thermal Throttle Disable (TTD) — R/W. Default is 0.

0 = Thermal Throttle is enabled.

1 = Thermal Throttle is disabled.

23:22 Reserved

PCI Express* 6 Disable (PE6D) — R/W. Default is 0. When disabled, the link for

this port is put into the “link down” state.

0 = PCI Express* port #6 is enabled.

1 = PCI Express port #6 is disabled.

PCI Express 5 Disable (PE5D) — R/W. Default is 0. When disabled, the link for this

port is put into the link down state.

0 = PCI Express port #5 is enabled.

1 = PCI Express port #5 is disabled.

PCI Express 4 Disable (PE4D) — R/W. Default is 0. When disabled, the link for this

port is put into the “link down” state.

0 = PCI Express port #4 is enabled.

1 = PCI Express port #4 is disabled.

NOTE: This bit must be set when Port 1 is configured as a x4.

PCI Express 3 Disable (PE3D) — R/W. Default is 0. When disabled, the link for this

port is put into the link down state.

0 = PCI Express port #3 is enabled.

1 = PCI Express port #3 is disabled.

NOTE: This bit must be set when Port 1 is configured as a x4.

PCI Express 2 Disable (PE2D) — R/W. Default is 0. When disabled, the link for this

port is put into the link down state.

0 = PCI Express port #2 is enabled.

1 = PCI Express port #2 is disabled.

NOTE: This bit must be set when Port 1 is configured as a x4 or a x2.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 389

Chipset Configuration Registers

PCI Express 1 Disable (PE1D) — R/W. Default is 0. When disabled, the link for this

port is put into the link down state.

0 = PCI Express port #1 is enabled.

1 = PCI Express port #1 is disabled.

15 EHCI #1 Disable (EHCI1D) — R/W. Default is 0.

0 = The EHCI #1 is enabled.

1 = The EHCI #1 is disabled.

LPC Bridge Disable (LBD ) — R/W. Default is 0.

0 = The LPC bridge is enabled.

1 = The LPC bridge is disabled. Unlike the other disables in this register, the following

additional spaces will no longer be decoded by the LPC bridge:

• · Memory cycles below 16 MB (1000000h)

• · I/O cycles below 64 KB (10000h)

• · The Internal I/OxAPIC at FEC0_0000 to FECF_FFFF

Memory cycles in the LPC BIOS range below 4 GB will still be decoded when this bit is

set, but the aliase s at the top of 1 MB (the E and F segment) no longer will be

decoded.

EHCI #2 Disable (EHCI2D) — R/W. Default is 0.

0 = The EHCI #2 is enabled.

1 = The EHCI #2 is disabled.

Note: When th is bit is set, the U H CI #5 function is not available and the UHCI #4

must be disabled by setting bit 11 in this register.

UHCI #5 Disable (U5D) — R/W. Default is 0

0 = The UHCI #5 is enabled.

1 = The UHCI #5 is disabled.

When the EHCI #2 Device Disable (EHCI2D) is set, this bit is a don’t care

UHCI #4 Disable (U4D) — R/W. Default is 0.

0 = The 4th UHCI (ports 6 and 7) is enabled.

1 = The 4th UHCI (ports 6 and 7) is disabled.

Note that UHCI #4 must be disabled when EHCI #2 is disabled with bit 13 in this

10 UHCI #3 Disable (U3D) — R/W. Default is 0.

0 = The 3rd UHCI (ports 4 and 5) is enabled.

1 = The 3rd UHCI (ports 4 and 5) is disabled.

9UHCI #2 Disable (U2D) — R/W. Default is 0.

0 = The 2nd UHCI (ports 2 and 3) is enabled.

1 = The 2nd UHCI (ports 2 and 3) is disabled.

8UHCI #1 Disable (U1D) — R/W. Default is 0.

0 = The 1st UHCI (ports 0 and 1) is enabled.

1 = The 1st UHCI (ports 0 and 1) is disabled.

7UHCI #6 Disable (U6D) — R/W. Default is 0.

0 = The 6th UHCI (ports 10 and 11) is enabled.

1 = The 6th UHCI (ports 10 and 11) is disabled.

6:5 Reserved

Intel® High Definition Audio Disable (HDAD) — R/W. Default is 0.

0 = The Intel High Definition Audio controller is enabled.

1 = The Intel High Definition Audio controller is disabled and its PCI configuration

space is not accessible.

Bit Description

Chipset Configuration Registers

390 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.78 CG—Clock Gating

Offset Address: 341C–341Fh Attribute: R/W

Default Value: 00000000h Size: 32-bit

SM Bus Disable (SD) — R/W. Default is 0.

0 = The SM Bus controller is enabled.

1 = The SM Bus controller is disabled. In ICH5 and previous, this also disabled the I/

O space. In ICH9, it only disables the configuration space.

2Serial ATA Disable 1 (SAD1) — R/W. Default is 0.

0 = The SATA controller #1 (D31:F2) is enabled.

1 = The SATA controller #1 (D31:F2) is disabled.

1 Reserved

0 BIOS must set thi s bit to 1b.

Bit Description

31 Le g a cy (L PC) Dynamic Clock Gat e E nable — R/W.

0 = Legacy Dynamic Clock Gating is Disabled

1 = Legacy Dynamic Clock Gating is Enabled

30 Reserved

29:28

USB UHCI Dynamic Clock Gate Enable — R/W.

0 = USB UH CI Dynamic Clock Gating is Disabled

1 = USB UH CI Dynamic Clock Gating is Enabled

0 = Reserved

1 = Reserved

(Desktop

Only)

SATA Port 3 Dynamic Clock Gate Enable — R/W.

0 = SATA Port 3 Dynamic Clock Gating is Disabled

1 = SATA Port 3 Dynamic Clock Gating is Enabled

(Desktop

Only)

SATA Port 2 Dynamic Clock Gate Enable — R/W.

0 = SATA Port 2 Dynamic Clock Gating is Disabled

1 = SATA Port 2 Dynamic Clock Gating is Enabled

27:26

(Mobile

Only) Reserved

25 SATA Port 1 Dynamic Clock Gate Enable — R/W.

0 = SATA Port 1 Dynamic Clock Gating is Disabled

1 = SATA Port 1 Dynamic Clock Gating is Enabled

24 SATA Port 0 Dynamic Clock Gate Enable — R/W.

0 = SATA Port 0 Dynamic Clock Gating is Disabled

1 = SATA Port 0 Dynamic Clock Gating is Enabled

LAN Static Clock Gating Enable (LANSCGE) — R/W.

0 = LAN Static Clock Gating is Disabled

1 = LAN Static Clock Gating is Enabled when the LAN Disable bit is set in the Backe d

Up Control RTC register.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 391

Chipset Configuration Registers

22 High Definition Audio Dynamic Cloc k Gate Enab le — R/W.

0 = High Definition Audio Dynamic Clock Gating is Disabled

1 = High Definition Audio Dynamic Clock G a ting is Enabled

21 High Definition Audio Static Cloc k Gate Enab le — R/W.

0 = High Definition Audio Static Clock Gating is Disabled

1 = High Definition Audio Static Clock Gat ing is Enabled

20 USB EHCI Static Clock Gate Enable — R/W.

0 = USB EHCI Static Clock Gating is Disabled

1 = USB EHCI Static Clock Gating is Enabled

19 USB EHCI Dynamic Clock Gate Enable — R/W.

0 = USB EHCI Dynamic Clock Gating is Disabled

1 = USB EHCI Dynamic Clock Gating is Enabled

18 SATA Port 5 Dynamic Clock Gate Enable — R/W.

0 = SATA Port 5 Dynamic Clock Gating is Disabled

1 = SATA Port 5 Dynamic Clock Gating is Enabled

17 SATA Port 4 Dynamic Clock Gate Enable — R/W.

0 = SATA Port 4 Dynamic Clock Gating is Disabled

1 = SATA Port 4 Dynamic Clock Gating is Enabled

16 PCI Dynamic Gate Enable — R/W.

0 = PCI Dynamic Gating is Disabled

1 = PCI Dynamic Gating is Enabled

15:6 Reserved

5SMBus Clock Gating Enable (SMBCGEN ) — R/W.

0 = SMBus Clock Gating is Disabled.

1 = SMBus Clock Gating is Enabled.

4PCI Express* RX Clock Gating Enable (PRXCGEN) — R/W.

0 = AFE RX Clock Gating is Disabled

1 = AFE RX Clock Gating is Enabled whenever all PCIe ports RX are in squelch

3DMI and PCI Express* RX Dynamic Clock Gate Enable — R/W.

0 = DMI and PCI Express root port RX Dynamic Clock Gating is Disabled

1 = DMI and PCI Express root port RX Dynamic Clock Gating is Enabled

2PCI Express TX Dynamic Clock Gate Enable — R/W.

0 = PCI Express root port TX Dynamic Cl ock Gating is Disabled

1 = PCI Express root port TX Dynamic Clock Gating is Enabled

1DMI TX Dynamic Clock Gate Enable — R/W.

0 = DMI TX Dynamic Clock Gating is Disabled

1 = DMI TX Dynamic Clock Gating is Enabled

0PCI Express Root Port Static Clock Gate Enable — R/W.

0 = PCI Express root port Static Clock Gating is Disabled

1 = PCI Express root port Static Clock Gating is Enabled

Bit Description

Chipset Configuration Registers

392 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

10.1.79 FDSW—Function Disable SUS Well

Offset Address: 3420h Attribute: R/W

Default Value: 00h Size: 8-bit

10.1.80 CIR8—Chipset Initialization Register 8

Offset Address: 3430-3433h Attribute: R/W

Default Value: 00000000h Size: 32-bit

10.1.81 CIR9—Chipset Initialization Register 9

Offset Address: 350Ch–350Fh Attribute: R/W

Default Value: 00000000h Size: 32-bit

10.1.82 PPO - Port Power Off

Offset Address: 3524–3525h Attribute: R/W

Default Value: 0000h Size: 16-bit

Bit Description

Function Disable SUS Well Lockdown (FDSWL)— R/W

0 = FDSW registers are not locked down

1 = FDSW registers are locked down

NOTE: This bit must be set when Intel® Active Management Techn ology is enabled.

6:0 Reserved

Bit Description

7:2 Reserved

1:0 CIR8 Field 1 — R/W. BIOS must program this field to 10b.

Bit Description

31:28 Reserved

27:26 CIR9 Field 1 — R/W. BIOS must program this field to 10b.

25:0 Reserved

Bit Description

15:12 Reserved

11:0

USB Port Power Off— R/W

1 = The corresponding EHCI and UHCI ports are electrically disconnected in this

mode.

Warning: The platform must ensure that the powered off ports are not routed

to any internal USB header or external USB connector. The ICH

provides pull-down termination resistors.

This register can not be written when the USB Per-Port Registers Write Enable bit

(UPRWC register, PMBASE + 3C, bit 1) is 0.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 393

Chipset Configuration Registers

10.1.83 CIR10 - Chipset Initialization Register 10

Offset Address: 352C–352Fh Attribute: R/W

Default Value: 0008C008h Size: 32-bit

10.1.84 MAP - Remap Control Register

Offset Address: 35F0-35F3h Attribute: R/WO

Default Value: 00000000h Size: 32-bit

§ §

Bit Description

32:18 Reserved

17:16 CIR10 Field 1— R/W. BIOS must program this field to 11b.

15:0 Reserved

Bit Description

31:01 Reserved

UHCI Controller # 6 Remap — R/WO

1 = UHCI Controller #6 is mapped to Device 29 Function 3

0 = UHCI Controller #6 is mapped to Device 26 Function 2

Note: When this bit is set, SW should reprogram the HCSPARAMS register

(Section 17.2.1.3) to reflect the correct value for N_CC (bits 15:12) and N_Ports

(bits 3:0) in each EHCI controller.

Chipset Configuration Registers

394 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 395

PCI-to-PCI Bridge Registers (D30:F0)

11 PCI-to-PCI Bridge Registers

(D30:F0)

The ICH9 PCI bridge resides in PCI Device 30, Function 0 on bus #0. This implements

the buffering and control logic between PCI and the backbone. The arbitration for the

PCI bus is handled by this PCI device.

11.1 PCI Configuration Registers (D30:F0)

Note: Address locations that are not shown should be treated as Reserved (see Section 9.2

for details).

Table 11-1. PCI Bridge Register Address Map (PCI-PCI—D30:F0) (Sheet 1 of 2)

Offset Mnemonic Register Name Default Type

00h–01h VID Vendor Identification 8086h RO

02h–03h DID Device Identification See register

description RO

04h–05h PCICMD PCI Command 0000h R/W, RO

06h–07h PSTS PCI Status 0010h R/WC, RO

08h R I D Revision Identification See register

description RO

09h–0Bh CC Class Code 060401h RO

0Dh PMLT Primary Master Latency Timer 00h RO

0Eh HEADTYP Header Type 01h RO

18h–1Ah BNUM Bus Number 000000h RO

1Bh SMLT Secondary Master Latency Timer 00h R/W

1Ch–1Dh IOBASE_LIMIT I/O Base and Limit 0000h R/W, RO

1Eh–1Fh SECSTS Secondary Status 0280h R/WC, RO

20h–23h MEMBASE_LIMIT Memory Base and Limit 00000000h R/W

24h–27h PREF_MEM_BASE

_LIMIT Prefetchable Memory Base and

Limit 00010001h R/W, RO

28h–2Bh PMBU32 Prefetchable Memory Upper 32

Bits 00000000h R/W

2Ch–2Fh PMLU32 Prefetchable Me mory Li mit Upper

32 Bits 00000000h R/W

34h CAPP Capability List Pointer 50h RO

3Ch–3Dh INTR Interrupt Information 0000h R/W, RO

3Eh–3Fh BCTRL Bridge Control 0000h R/WC, RO,

R/W

40h–41h SPDH Secondary PCI Device Hiding 0000h R/W, RO

44h–47h DTC Delayed Transaction Control 00000000h R/W

48h–4Bh BPS Bridge Proprietary Status 00000000h R/WC, RO

PCI-to-PCI Bridge Register s (D30:F0)

396 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

11.1.1 VID— Vendor Identification Register (PCI-PCI—D30:F0)

Offset Address: 00h–01h Attribute: RO

Default Value: 8086h Size: 16 bits

11.1.2 DID— Device Identification Register (PCI-PCI—D30:F0)

Offset Address: 02h–03h Attribute: RO

Default Value: See bit description Size: 16 bits

4Ch–4Fh BPC Bridge Policy Configuration 00001200h R/W RO

50–51h SVCAP Subsystem Vendor Capability

Pointer 000Dh RO

54h–57h SVID Subsystem Vendor IDs 00000000 R/WO

Table 11-1. PCI Bridge Register Address Map (PCI-PCI —D3 0:F 0) (She et 2 of 2)

Offset Mnemonic Register Name Default Type

Bit Description

15:0 Vendor ID — RO. This is a 16-bit value assigned to Intel. Intel VID = 8086h.

Bit Description

15:0 Device ID — RO.This is a 16-bit value assigned to the PCI bridge . Refer to the Intel®

I/O Controller Hub (ICH9) Family Specification Update for the value of the Device ID

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 397

PCI-to-PCI Bridge Registers (D30:F0)

11.1.3 PCICMD—PCI Command (PCI-PCI—D30:F0)

Offset Address: 04h–05h Attribute: R/W, RO

Default Value: 0000h Size: 16 bits

11.1.4 PSTS—PCI Status Register (PCI-PCI—D30:F0)

Offset Address: 06h–07h Attribute: R/WC, RO

Default Value: 0010h Size: 16 bits

Note: For the writable bits, software must write a 1 to clear bits that are set. Writing a 0 to

the bit has no effect.

Bit Description

15:11 Reserved

10 Interrupt Disable (ID) — RO. Hardwired to 0. The PCI bridge has no interrupts to

disable

9Fast Back to Back Enable (FBE) — RO. Hardwired to 0, per the PCI Express* Base

Specification, Revision 1.0a.

SERR# Enable (SERR_EN) — R/W.

0 = Disable.

1 = Enable the ICH9 to generate an NMI (or SMI# if NMI routed to SMI#) when the

D30:F0 SSE bit (offset 06h, bit 14) is set.

7Wait Cycle Control (WCC) — RO. Hardwired to 0, per the PCI Express* Base

Specification, Revision 1.0a.

Parity Error Response (PER) — R/W.

0 = The ICH9 ignores parity errors on the PCI bridge.

1 = The ICH9 will set the SSE bit (D30:F0, offset 06h, bit 14) when parity errors are

detected on the PCI bridge.

5VGA Palette Snoop (VPS) — RO. Hardwired to 0, per the PCI Express* Base

Specification, Revision 1.0a.

4Memory Write and Invalidate Enable (MWE) — RO. Hardwired to 0, per the PCI

Express* Base Specification, Revision 1.0a

3Special Cycle Enable (SCE) — RO. Hardwired to 0, per the PCI Express* Base

Specification, Revision 1.0a and the PCI- to-PCI Bridge Specification.

2Bus Master Enable (BME) — R/W.

0 = Disable

1 = Enable. Allows the PCI-to-PCI bridge to accept cycles from PCI.

Memory Space Enable (MSE) — R/W. Controls the response as a target for memory

cycles targeting PCI.

0 = Disable

1 = Enable

I/O Space Enable (IOSE) — R/W. Controls the response as a target for I/O cycles

targeting PCI.

0 = Disable

1 = Enable

PCI-to-PCI Bridge Register s (D30:F0)

398 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Bit Description

Detected Parity Error (DPE) — R/WC.

0 = Parity error Not detected.

1 = Indicates that the ICH9 detected a parity error on the internal backbone. Th is bit

gets set even if the Parity Error Response bit (D30:F0:04 bit 6) is not set.

Signaled System Error (SSE) — R/WC. Several internal and external sources of the

bridge can cause SERR#. The first class of errors is parity errors related to the

backbone. The PCI bridge captures generic data parity errors (errors it finds on the

backbone) as well as errors returned on backbone cycles where the bridge was the

master. If either of these two conditions is met, and the primary side of the bridge is

enabled for parity error response, SERR# will be captured as shown below.

As with the backbone, the PCI bus captures the same sets of errors. The PCI bridge

captures generic data parity errors (errors it finds on PCI) as well as errors returned on

PCI cycles where the bridge was the master. If either of these two conditions is met,

and the secondary side of the bridge is enabled for parity error response, SERR# will be

captured as shown below.

The final class of errors is system bus errors. There are three status bits associated with

system bus er rors, each with a corres p onding enable . The diagram capturing this is

shown below.

After checking for the three above classes of errors, an SERR# is generated, and

PSTS.SSE logs the generation of SERR#, if CMD.SEE (D30:F0:04, bit 8) is set, as shown

below.

13 Received Master Abort (RMA) — R/WC.

0 = No master abort received.

1 = S et when the bridge receives a master abort status from the backbone.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 399

PCI-to-PCI Bridge Registers (D30:F0)

11.1.5 RID—Revision Identification Register (PCI-PCI—D30:F0)

Offset Address: 08h Attribute: RO

Default Value: See bit description Size: 8 bits

11.1.6 CC—Class Code Register (PCI-PCI—D30:F0)

Offset Address: 09h-0Bh Attribute: RO

Default Value: 060401h Size: 24 bits

12 Received Target Abort (RTA) — R/WC.

0 = No target abort received.

1 = Set when the bridge receives a target abort status from the backbone.

Signaled Target Abort (STA) — R/WC.

0 = No signaled target abort

1 = Set when the bridge gener ate s a c ompleti on pack et with targ et abort statu s on the

backbone.

10:9 Reserved.

Data Parity Error Detected (DPD) — R/WC.

0 = D ata parity error Not dete cted.

1 = Set when the bridge receives a completion packet from the backbone from a

previous request, and detects a parity error, and CMD.PERE is set (D3 0:F0:04 bit

6).

7:5 Reserved.

4Capabilities List (CLIST) — RO. Hardwired to 1. Capability list exist on the PCI

bridge.

3Interrupt Status (IS) — RO. Hardwired to 0. The PCI bridge does not generate

interrupts.

2:0 Reserved

Bit Description

7:0 Revision ID — RO. R e fer to the Intel® I/O Controller Hub (ICH9) Family Specification

Update for the value of the Revision ID Register

Bit Description

23:16 Base Class Code (BCC) — RO. Hardwired to 06h. Indicates this is a bridge device.

15:8 Sub Class Code (SCC) — RO. Hardwired to 04h. Indicates this device is a PCI-to-PCI

bridge.

7:0 Programming Interface (PI) — RO. Hardwired to 01h. Indicates the bridge is

subtractive decode

PCI-to-PCI Bridge Register s (D30:F0)

400 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

11.1.7 PMLT—Primary Master Latency Timer Register

(PCI-PCI—D30:F0)

Offset Address: 0Dh Attribute: RO

Default Value: 00h Size: 8 bits

11.1.8 HEADTYP—Header Type Register (PCI-PCI—D30:F0)

Offset Address: 0Eh Attrib ute: RO

Default Value: 01h Size: 8 bits

11.1.9 BNUM—Bus Number Register (PCI-PCI—D30:F0)

Offset Address: 18h-1Ah Attribute: R/W

Default Value: 000000h Size: 24 bits

Bit Description

7:3 Master Latency Timer Count (MLTC) — RO. Reserved per the PCI Express* Base

Specification, Revision 1.0a.

2:0 Reserved

Bit Description

7Multi-Function Device (MFD) — RO. ‘0’ indicates a single function device

6:0 Header Type (HTYPE) — RO. This 7-bit field identifies the header layout of the

configuration space, which is a PCI-to-PCI bridge in this case.

Bit Description

23:16 Subordinate Bus Numb er (SBBN) — R/W. Indicates the highest PCI bus number

below the bridge.

15:8 Secondary Bus Number (SCBN) — R/W. Indicates the bus number of PCI.

7:0

Primary Bus Number (PBN) — R/W. This field is default to 00h. In a multiple-ICH

system, programmable PBN allows an ICH to be located on any bus. System

configuration software is responsible for initializing these registers to appropriate

values. PBN is not used by hardware in determining its bus number.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 401

PCI-to-PCI Bridge Registers (D30:F0)

11.1.10 SMLT—Secondary Master Latency Timer Register

(PCI-PCI—D30:F0)

Offset Address: 1Bh Attribute: R/W

Default Value: 00h Size: 8 bits

This timer controls the amount of time the ICH9 PCI-to-PCI bridge will burst data on its

secondary interface. The counter starts counting down from the assertion of FRAME#.

If the grant is removed, then the expiration of this counter will result in the de-

assertion of FRAME#. If the grant has not been removed, then the ICH9 PCI-to-PCI

bridge may continue ownership of the bus.

11.1.11 IOBASE_LIMIT—I/O Base and Limit Register

(PCI-PCI—D30:F0)

Offset Address: 1Ch-1Dh Attribute: R/W, RO

Default Value: 0000h Size: 16 bits

Bit Description

7:3 Master Latency Timer Count (MLTC) — R/W. This 5-bit field indicates the number of

PCI clocks, in 8-clock increments, that the ICH9 remains as master of the bus.

2:0 Reserved

Bit Description

15:12 I/O Limit Address Limit bits[15 :12 ] — R/W. I/O Base bits corresponding to address

lines 15:12 for 4-KB alignment. Bits 11:0 are assumed to be padded to FFFh.

11:8 I/O Limit Address Capability (IOLC) — RO. Indicates that the bridge does not

support 32-bit I/O addressing.

7:4 I/O Base Address (IOBA) — R/W. I/O Base bits corresponding to address lines 15:12

for 4-KB alignment. Bits 11:0 are assumed to be padded to 000h.

3:0 I/O Base Address Capability (IOBC) — RO. Indicates that the bridge does not

support 32-bit I/O addressing.

PCI-to-PCI Bridge Register s (D30:F0)

402 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

11.1.12 SECSTS—Secondary Status Register (PCI-PCI—D30:F0)

Offset Address: 1Eh–1Fh Attribute: R/WC, RO

Default Value: 0280h Size: 16 bits

Note: For the writable bits, software must write a 1 to clear bits that are set. Writing a 0 to

the bit has no effect.

Bit Description

15 Detected Parity Error (DPE) — R/WC.

0 = Pari ty error not detected.

1 = Intel® ICH9 PCI bridge detected an address or data parity error on the PCI bus

14 Received System Error (RSE) — R/WC.

0 = SERR# assertion not received

1 = SERR# assertion is received on PCI.

Received Master Abort (RMA) — R/WC.

0 = No master abort.

1 = This bit is set whene ver the bridge is acting as an initiator on the PCI bus and the

cycle is master-aborted. For (G)MCH/ICH9 interface packets that have completion

required, th is must also cause a target abort to be returned and sets PSTS.STA.

(D30:F0:06 bit 11)

Received Target Abort (RTA) — R/WC.

0 = No target abort.

1 = This bit is set whenever the bridge is acting as an initiator on PCI and a cycle is

target-aborted on PCI. For (G)MCH/ICH9 interface packets that have completion

required, this event must also cause a target abort to be returned, and sets

PSTS.STA. (D30:F0:06 bit 11).

Signaled Target Abort (STA) — R/WC.

0 = No target abort.

1 = Thi s bit is set when the bridge is acting as a target on the PCI Bus and signals a

target abort.

10:9 DEVSEL# Timing (DEVT) — RO.

01h = Medium decode timing.

Data Parity Error Detected (DPD) — R/WC.

0 = Conditions described below not met.

1 = The ICH9 sets this bit when all of the foll owing three conditions are met:

• The bridge is the initiator on PCI.

• PERR# is detected asserted or a parity error is detected internally

• BCTRL.PERE (D30:F0:3E bit 0) is set.

7Fast Back to Back Capable (FBC) — RO. Hardwired to 1 to indicate that the PCI to PCI

target logic is capable of receiving fast back-to-back cycles.

6 Reserved

566 MHz Capable (66MHZ_CAP) — RO. Hardwired to 0. This bridge is 33 MHz capable

only.

4:0 Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 403

PCI-to-PCI Bridge Registers (D30:F0)

11.1.13 MEMBASE_LIMIT—Memory Base and Limit Register

(PCI-PCI—D30:F0)

Offset Address: 20h–23h Attribute: R/W

Default Value: 00000000h Size: 32 bits

This register defines the base and limit, aligned to a 1-MB boundary, of the non-

prefetchable memory area of the bridge. Accesses that are within the ranges specified

in this register will be sent to PCI if CMD.MSE is set. Accesses from PCI that are outside

the ranges specified will be accepted by the bridge if CMD.BME is set.

11.1.14 PREF_MEM_BASE_LIMIT—Prefetchable Memory Base

and Limit Register (PCI-PCI—D30:F0)

Offset Address: 24h–27h Attribute: R/W, RO

Default Value: 00010001h Size: 32-bit

Defines the base and limit, aligned to a 1-MB boundary, of the prefetchable memory

area of the bridge. Accesses that are within the ranges specified in this register will be

sent to PCI if CMD.MSE is set. Accesses from PCI that are outside the ranges specified

will be accepted by the bridge if CMD.BME is set.

Bit Description

31:20 Memory Limit (ML) — R/W. These bits are compared wi th bits 31:20 of the incoming

address to determine the upper 1-MB aligned value (exclusive) of the range. The

incoming address must be less than this value.

19:16 Reserved

15:4 Memory Base (MB) — R/W. These bits are compared with bits 31:20 of the incoming

address to determine the lower 1-MB aligned value (inclusive) of the range. The

incoming address must be greater than or equal to this value.

3:0 Reserved

Bit Description

31:20 Prefetchabl e Memory Limi t (PML) — R/W. These bi ts are compared with bi ts 31: 20

of the incoming address to determine the upper 1-MB aligned value (exclusive) of the

range. The incoming address must be less than this value.

19:16 64-bit Indicator (I64L) — RO. Indicates support for 64-bit addressing.

15:4 Prefetchabl e Me mory B ase ( PMB) — R/W. These bits are compared with bits 31:20

of the incoming address to determine the lower 1-MB aligned value (inclusive) of the

range. The incoming address must be greate r than or equal to this value.

3:0 64-bit Indicator (I64B) — RO. Indicates support for 64-bit addressing.

PCI-to-PCI Bridge Register s (D30:F0)

404 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

11.1.15 PMBU32—Prefetchable Memory Base Upper 32 Bits

Offset Address: 28h–2Bh Attribute: R/W

Default Value: 00000000h Size: 32 bits

11.1.16 PMLU32—Prefetchable Memory Limit Upper 32 Bits

Offset Address: 2C–2Fh Attribute: R/W

Default Value: 00000000h Size: 32 bits

11.1.17 CAPP—Capability List Pointer Register (PCI-PCI—D30:F0)

Offset Address: 34h Attribute: RO

Default Value: 50h Size: 8 bits

11.1.18 INTR—Interrupt Information Register (PCI-PCI—D30:F0)

Offset Address: 3Ch–3Dh Attribute: R/W, RO

Default Value: 0000h Size: 16 bits

Bit Description

31:0 Prefetchable Memory Base Upper Portion (PMBU) — R/W. Upper 32-bits of the

prefetchable address base.

Bit Description

31:0 Prefetchable Memory Limit Upper Portion (PMLU) — R/W. Upper 32-bits of the

prefetchable address limit.

Bit Description

7:0 Capabilities Pointer (PTR) — RO. Indicates that the pointer for the first entry in the

capabilities list is at 50h in configuration space.

Bit Description

15:8 Interrupt Pin (IPIN ) — RO. The PCI bridge does not assert an interrupt.

7:0

Interrupt Line (ILINE) — R /W. Software written value to indicate which interrupt line

(vector) the interrupt is connected to. No hardware action is taken on this registe r.

Since the bridge does not gener ate an interrupt , BIOS should progr am this valu e to FFh

as per the PCI bridge specification.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 405

PCI-to-PCI Bridge Registers (D30:F0)

11.1.19 BCTRL—Bridge Control Register (PCI-PCI—D30:F0)

Offset Address: 3Eh–3Fh Attribute: R/WC, RO, R/W

Default Value: 0000h Size: 16 bits

Bit Description

15:12 Reserved

Discard Timer SERR# Enable (DTE) — R/W. Controls the generation of SERR# on

the primary interface in response to the DTS bit being set:

0 = Do not generate SERR# on a secondary timer discard

1 = Generate SERR# in response to a secondary timer discard

10 Discard Timer Status (DTS) — R/WC. This bit is set to 1 when the secondary discard

timer (see the SDT bit below) expires for a delayed transaction in the hard state.

Secondary Discard Timer (SDT) — R/W. This bit sets the maximum number of PCI

clock cycles that the Intel® ICH9 waits for an initiator on PCI to repeat a delayed

transaction request. The counter starts once the delayed transaction data is has been

returned by the system and is in a buffer in the ICH9 PCI bridge. If the master has not

repeated the transaction at least once before the counter expires, the ICH9 PCI bridge

discards the transaction from its queue.

0 = The PCI master timeout value is between 215 and 216 PCI clocks

1 = The PCI master timeout value is between 210 and 211 PCI clocks

8Primary Discard Timer (PDT) — R/W. This bit is R/W for software compatibility only.

7Fast Back to Back Enable (FBE) — RO. Hardwired to 0. The PCI logic will not generate

fast back-to-back cycles on the PC I bus.

Secondary Bus Reset (SBR) — R/W. Controls PCIRST# assertion on PCI.

0 = Bridge de-asserts PCIRST#

1 = Bridge asserts PCIRST#. When PCIRST# is assert ed, the delayed transaction

buffers, posting buffers, and the PCI bus are initialized back to reset conditions.

The rest of the part and the configuration registers are not affected.

Master Abort Mode (MAM) — R/W. Controls the ICH9 PCI bridge’s behavior when a

master abort occu rs :

Master Abort on (G)MCH/ICH9 Interconnect (DMI):

0 = Bridge asserts TRDY# on PCI. It drives all 1s for reads, and discards data on writes.

1 = Bridge returns a target abort on PCI.

Master Abort PCI (non-locked cycles):

0 = Normal completion status will be returned on the (G)MCH/ICH9 interconnect.

1 = Target abort completion status will be returned on the (G)M CH/ICH9 interconnec t.

NOTE: All locked reads will return a completer abort completion status on the (G)MCH/

ICH9 interconnect.

4VGA 16-Bit Deco de (V16D) — R/W. Enables the ICH9 PCI bridge to provide 16-bits

decoding of VGA I/O address precluding the decode of VGA alias addresses every 1 KB.

This bit requires the VGAE bit in this register be set.

PCI-to-PCI Bridge Register s (D30:F0)

406 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

11.1.20 SPDH—Secondary PCI Device Hiding Register

(PCI-PCI—D30:F0)

Offset Address: 40h–41h Attribute: R/W, RO

Default Value: 0000h Size: 16 bits

This register allows software to hide the PCI devices, either plugged into slots or on the

motherboard.

VGA Enable (VGAE) — R/W. When set to a 1, the ICH9 PCI bridge forwards the

following tr ansactions to PCI r egardless of th e v alue of the I/O base and li mit registers .

The transactions are qualified by CMD.MSE (D30:F0:04 bit 1) and CMD.IOSE

(D30:F0:04 bit 0) being set.

• Memory addresses: 000A0000h-000BFFFFh

• I/O addresses: 3B0h-3BBh and 3C0h-3DFh. For the I/O addresses, bits [63:16] of the address

must be 0, and bits [15:10] of the address are ignored (i.e., aliased).

The same holds true from secon dary acce sses t o the pri mary inter face in rev erse. That

is, when the bit is 0, memory and I/O addresses on the secondary interface between

the above ranges will be claimed.

ISA Enable (IE) — R/W. This bit only applies to I/O addresses that are enabled by the

I/O Base and I/O Limit registers and are in the first 64 KB of PCI I/O space. If this bit is

set, the ICH9 PCI bridge will block any forwarding from primary to secondary of I/O

transactions addressing the last 768 bytes in each 1-KB block (offsets 100h to 3FFh).

SERR# Enable (SEE) — R/W. Controls the forwarding of secondary interface SERR#

assertions on the primary interface. When set, the PCI bridge will forward SERR# pin.

• SERR# is asserted on the secondary interface.

• This bit is set.

• CMD.SEE (D30:F0:04 bit 8) is set.

Parity Error Response Enable (PERE) — R/W.

0 = Disable

1 = The ICH9 PCI bridge is enabled for parity error reporting based on parity errors on

the PCI bus.

Bit Description

15:4 Reserved

3Hide Device 3 (HD3) — R/W, RO. Same as bit 0 of this register, except for device 3

(AD[19])

2Hide Device 2 (HD 2) — R/W, RO. Same as bit 0 of this register, except for device 2

(AD[18])

1Hide Device 1 (HD1) — R/W, RO. Same as bit 0 of this register, except for device 1

(AD[17])

Hide Device 0 (HD 0) — R/W, RO.

0 = The PC I configuration cycles for this slot are not affected.

1 = Intel® ICH9 hides device 0 on the PCI bus. This is done by masking the IDSEL

(keeping it low) for configuration c ycles to that device. Sinc e the device will not see

its IDSEL go active, it will not respond to PCI con f iguration cycles and the

processor will thin k the device is not present. AD[16] is used as IDSEL for device 0.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 407

PCI-to-PCI Bridge Registers (D30:F0)

11.1.21 DTC—Delayed Transacti o n Co ntrol Register

(PCI-PCI—D30:F0)

Offset Address: 44h–47h Attribute: R/W

Default Value: 00000000h Size: 32 bits

Bit Description

Discard Delayed Transactions (DDT) — R/W.

0 = Logged delayed transactions are kept.

1 = The ICH9 PCI bridge will discard any delayed transactions it has logged. This

includes transactions in the pending queue, and any transactions in the active

queue, whether in the hard or soft DT state. The prefetchers will be disabled and

return to an idle state.

NOTES:If a transac tion is running on PCI at the ti me this bit is set, that tr ansac tion will

continue until either the PCI master disconnects (by de-asserting FRAME#) or

the PCI bridge disconne cts (by asserting STOP#). This bit is cleared by the PCI

bridge when the delayed transaction queues are empty and have returned to an

idle state. Software sets this bit and polls for its completion

Block Delayed Transactions (BDT) — R/W.

0 = Delayed transactions accepted

1 = The ICH9 PCI bridge will not acce pt incoming transactio ns which will res ult in

delayed transactions. It will blindly retry these cycles by asserting STOP#. All

postable cycles (memory writes) will still be accepted.

29:8 Reserved

7:6

Maximum Delayed Transactions (MDT) — R/W. Controls the maximum number of

delayed transactions that the ICH9 PCI bridge will run. Encodings are:

00 =) 2 Active, 5 pending

01 =) 2 active, no pending

10 =) 1 active, no pending

11 =) Reserved

5 Reserved

Auto Flush After Disconnect Enable (AFADE) — R/W.

0 = The PCI bridge will retain any fetched data until required to discard by producer/

consumer rules.

1 = The PCI bridge will flush any prefetched data after either the PCI master (by de-

asserting FRAME#) or the PCI bridge (by asserting STOP#) disconnects the PCI

transfer.

Never Prefetc h (NP) — R/W.

0 = Prefetch enabled

1 = The ICH9 will only fetch a single DW and will not enable prefetching, regardless of

the command being an Memory read (MR), Memory read line (MRL), or Memory

read multiple (MRM).

PCI-to-PCI Bridge Register s (D30:F0)

408 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

11.1.22 BPS—Bridge Proprietary Status Register

(PCI-PCI—D30:F0)

Offset Address: 48h–4Bh Attribute: R/WC, RO

Default Value: 00000000h Size: 32 bits

Memory Read Multiple Prefetch Disable (MRMPD) — R/W.

0 = MRM commands will fetch multiple cache lines as defined by the prefetch

algorithm.

1 = Memory read multiple (MRM) commands will fetch only up to a single, 64-byte

aligned cache line.

Memory Read Line Prefetch Disable (MRLPD) — R/W.

0 = MRL commands will fetch multiple cache lines as defined by the prefetch algorithm.

1 = Memory read line (MRL) commands will fetch only up to a single, 64-byte aligned

cache line.

0Memory Read Prefetch Disabl e (MRPD) — R/W.

0 = MR commands will fetch up to a 64-byte aligned cache line.

1 = Memory read (MR) commands will fetch only a single DW.

Bit Description

31:17 Reserved

PERR# Assertion Dete cted (PAD) — R/WC. Th is bit is set b y hardware whenev er the

PERR# pin is asserted on the rising edge of PCI clock. This includes cases in which the

chipset is the agent driving PERR#. It remains asserted until cleared by software

writing a 1 to this location. When enabled by the PERR#- to-SERR# Enable bit (i n the

Bridge Policy Configuration regi ster), a 1 in this bit can generate an internal SERR# and

be a source for the NMI logic.

This bit can be used by software to determine the source of a system problem.

15:7 Reserved

6:4

Number of Pending Transactions (NPT) — RO. This read-only indicator tells debug

software how many transactions are in the pending queue. Possible values are:

000 = No pending transaction

001 = 1 pending transaction

010 = 2 pending transactions

011 = 3 pending transactions

100 = 4 pending transactions

101 = 5 pending transactions

110 - 111 = Reserved

NOTE: This field is not valid if DTC.MDT (offset 44h:bits 7:6) is any value other than

‘00’.

3:2 Reserved

1:0

Number of Active Transactio ns (N AT) — RO. This read-only indicator tells debug

software how many transactions are in the active queue. Possible values are:

00 = No active transactions

01 = 1 active transaction

10 = 2 active transactions

11 = Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 409

PCI-to-PCI Bridge Registers (D30:F0)

11.1.23 BPC—Bridge Policy Configurati on Register

(PCI-PCI—D30:F0)

Offset Address: 4Ch–4Fh Attribute: R/W

Default Value: 00001200h Size: 32 bits

Bit Description

31:14 Reserved

13:8

Upstream Read Latency Threshold (URLT) — R/W: This field specifies the number

of PCI clocks after internally enqueuing an upstream memory read request at which

point the PCI target logic s hould insert w ait state s in order to optimi ze lead-off late ncy.

When the master returns after this threshold has been reached and data has not

arrived in the Delayed Transaction completion queue, then the PCI target logic will

insert wait states instead of immediately retrying the cycle. The PCI target logic will

insert up to 16 clocks of target initial latency (from FRAME# assertion to TRDY# or

STOP# assertion) before retrying the PCI read cycle (if the read data has not arrived

yet).

Note that the starting event for this Read Latency Timer is not explicitly visible

externally.

A value of 0h disables this policy completely such that wait states will never be inserted

on the read lead-off data phase.

The default value (12h) specifies 18 PCI clocks (540 ns) and is approximately 4 clocks

less than the typical idle lead-off latency expected for desktop ICH9 systems. This value

may need to be changed by BIOS, depending on the platform.

Subtractive Decode Policy (SDP) — R/W.

0 = The PCI bridge always forwards memory and I/O cycles that are not claimed by any

other device on the backbone (primary interface) to the PCI bus (secondary

interface).

1 = The PCI bridge will not claim and forward memory or I/O cycles at all unless the

corresponding Space Enable bit is set in the Command register.

NOTE: The Boot BIOS Destination Selection strap can force the BIOS accesses to PCI.

PERR#-to-SERR# Enable (PSE) — R/W. When this bit is set, a 1 in the PERR#

Assertion status bit (in the Bridge Proprietary Status register) will result in an internal

SERR# assertion on the primary side of the bridge (if also enabled by the SERR#

Enable bit in the primary Command register). SERR# is a sou r ce of NMI.

Secondary Discard Timer Testmode (SDTT) — R/W.

0 = The secondary discard timer ex piration will be defined in BCTRL.SDT (D30:F0:3E,

bit 9)

1 = The secondary discard timer will expire after 128 PCI clocks.

4:3 Reserved

CMD.MSE BPC.SDP Range For warding Policy

00Don’t Care

Forward unclaimed

cycles

0 1 Don’t Care Forwarding Prohibited

1XWithin range

Positive decode and

forward

1XOutside

Subtractive decode &

forward

PCI-to-PCI Bridge Register s (D30:F0)

410 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

11.1.24 SVCAP—Subsystem Vendor Capability Register

(PCI-PCI—D30:F0)

Offset Address: 50h–51h Attribute: RO

Default Value: 000Dh Size: 16 bits

11.1.25 SVID—Subsystem Vendor IDs Register (PCI-PCI—D30:F0)

Offset Address: 54h–57h Attribute: R/WO

Default Value: 00000000h Size: 32 bits

§ §

Peer Decode Enable (PDE) — R/W.

0 = The PCI bridge assumes that all memory cycles target main memory, and all I/O

cycles are not claimed.

1 = The PCI bridge will perform peer decode on any memory or I/O cy cle from PCI th at

falls outside of the memory and I/O window registers

1Reserved

0Received Target Abort SERR# Enable (RTAE) — R/W. When set, the PCI bridge will

report SERR# when PSTS.RTA (D30:F0:06 bit 12) or SSTS.RTA (D30:F0:1E bit 12) are

set, and CMD.SEE (D30:F0:04 bit 8) is set.

Bit Description

15:8 Next Capability (NEXT) — RO. Value of 00h indicates this is the last item in the list.

7:0 Capability Identifier (CID) — RO. Value of 0Dh indicates this is a PC I bridge

subsystem vendor capability.

Bit Description

31:16 Subsystem Identifier (SID) — R/WO. Indicates the subsystem as identified by the

vendor. This field is write onc e and is locked down until a bridge reset occurs (not the

PCI bus reset).

15:0 Subsystem Vendor Identifier (SVID) — R/WO. Indicates the manufacturer of the

subsystem. This field is write once and is locked down until a bridge reset occurs (not

the PCI bus reset).

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 411

Gigabit LAN Configuration Registers

12 Gigabit LAN Configuration

Registers

12.1 Gigabit LAN Configuration Registers

(Gigabit LAN — D25:F0)

Note: Register address locations that are not shown in Table 12-1 should be treated as

Reserved.

Table 12-1. Gigabit LAN Configuration Registers Address Map

(Gigabit LAN —D25:F0) (Sheet 1 of 2)

Offset Mnemonic Register Name Default Type

00h–01h VID Vendor Identification 8086h RO

02h–03h DID Device Identification See register

description RO

04h–05h PCICMD PCI Command 0000h R/W, RO

06h–07h PCISTS PCI Status 0010h R/WC, RO

08h R ID Revision Identification See register

description RO

09h–0Bh CC Class Code 020000h RO

0Ch CLS Cache Line Size 00h R/W

0Dh PLT Primary Latency Timer 00h RO

0Eh HEADTYP Header Type 00h RO

10h–13h MBARA Memory Base Address A 00000000h R/W, RO

14h–17h MBARB Memory Base Address B 00000000h R/W, RO

18h–1Bh MBARC Memory Base Address C 00000001h R/W, RO

2Ch–2Dh SID Subsystem ID See register

description RO

2Eh–2Fh SVID Subsystem Ve ndor ID See register

description RO

30h–33h ERBA Expansion ROM Base Address See register

description RO

34h CAPP Capabilities List Pointer C8h RO

3Ch–3Dh INTR Interrupt Information See register

description R/W, RO

3Eh MLMG Maximum Latency/Minimum

Grant 00h RO

C8h–C9h CLIST1 Capabilities List 1 D001h RO, R/WO

CAh–CBh PMC PCI Power Management

Capability See register

description RO

CCh–CDh PMCS PCI Power Management Control

and Status See register

description R/WC, R/W,

Gigabit LAN Configuration Registers

412 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

12.1.1 VID—Vendor Identification Register

(Gigabit LAN—D25:F0)

Address Offset: 00h–01h Attribute: RO

Default Value: 8086h Size: 16 bits

12.1.2 DID—Device Identi fication Register

(Gigabit LAN—D25:F0)

Address Offset: 02h–03h Attribute: RO

Default Value: See bit description Size: 16 bits

CFh DR Data Register See register

description RO

D0h–D1h CLIST2 Capa bilities List 2 E005h R/WO, RO

D2h–D3h MCTL Message Control 0080h R/W, RO

D4h–D7h MADDL Message Address Low See register

description R/W

D8h–DBh MADDH Message Address High See register

description R/W

DCh–DDh MDAT Message Data See register

description R/W

E0h–E1h FLRCAP Function Level Reset Capability 0009h RO

E2h–E3h FLRCLV Function Level Reset Capability

Length and Value See register

description R/WO, RO

E4h–E5h DEVCTRL Device Control 0000h R/W, RO

Table 12-1. Gigabit LAN Configuration Registers Address Map

(Gigabit LAN —D25:F0) (Sheet 2 of 2)

Offset Mnemonic Register Name Default Type

Bit Description

15:0 Vendor ID — RO. This is a 16-bit value assigned to Intel. The field may be auto-loaded

from the NVM at address 0Eh during init time depending on the "Load Vendor/Device

ID" bit field in NVM word 0Ah with a default value of 8086h.

Bit Description

15:0 Device ID — RO. This is a 16-bit value assigned to the Intel® ICH9 Gigabit LAN

controller. The field may be auto-loaded from the NVM word 0Dh during init ialization

time depending on the "Load Vendor/Device ID" bit field in NVM word 0Ah.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 413

Gigabit LAN Configuration Registers

12.1.3 PCICMD—PCI Command Register

(Gigabit LAN—D25:F0)

Address Offset: 04h–05h Attribute: R/W, RO

Default Value: 0000h Size: 16 bits

Bit Description

15:11 Reserved

Interrupt Disable — R/W. This disables pin-based INTx# interrupts on enabled Hot-

Plug and power management events. This bit has no effect on MSI operation.

0 = Internal INTx# messages are generated if there is an interrupt for Hot-Plug or

power management and MSI is not enabled.

1 = Internal INTx# messages will not be generated.

This bit does not affect interrupt forwarding from devices connected to the root port.

Assert_INTx and Deassert_INTx messages will still be forwarded to the internal

interrupt c ontrollers if thi s bit is set.

9 Fast Back to Back Enable (FBE) — RO. Hardwired to ‘0’.

SERR# Enable (SEE) — R/W.

0 = Disable

1 = Enables the Gb LAN controller to generate an SERR# message when PSTS.SSE is

set.

7 Wait Cycle Control (WCC) — RO. Hardwired to ‘0’.

Parity Error Response (PER) — R/W.

0 = Disable.

1 = Indicates that the device is capable of reporting parity errors as a master on the

backbone.

5 Palette Snoop Enable (PSE) — RO. Hardwired to ‘0’.

4 Postable Memory Write Enable (PMWE) — RO. Hardwired to ‘0’.

3 Special Cycle Enable (SCE) — RO. Hardwired to ‘0’.

Bus Master Enable (BME) — R/W.

0 = Disable. All cycles from the devi ce are master aborted

1 = Enable. Allows the root port to forward cycles onto the backbone from a Gigabit

LAN* device.

Memory Space Enable (MSE) — R/W.

0 = D isable. Memory cycles with in the range specified by the memory base and limit

registers are master aborte d on the backbone.

1 = Enable. Allows memory cycles within the range specified by the memory base and

limit registers can be forwarded to the Gigabit LAN device.

I/O Space Enable (IOSE) — R/W. This bit controls ac cess to t he I/O spac e regist ers.

0 = Disable. I/O cycles within the range specified by the I/O base and limit registers

are master aborted on the backbone.

1 = Enable. Allows I/O cycles within the range specified by the I/O base and limit

registers can be forwarded to the Gigabit LAN devi ce.

Gigabit LAN Configuration Registers

414 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

12.1.4 PCISTS—PCI Status Register

(Gigabit LAN—D25:F0)

Address Offset: 06h–07h Attribute: R/WC, RO

Default Value: 0010h Size: 16 bits

Bit Description

Detected Parity Error (DPE) — R/WC.

0 = No parity error detected.

1 = Set when the Gb LAN controller receives a command or data from the backbone

with a parity error. This is set even if PCIMD.PER (D25:F0, bit 6) is not set.

14 Signaled System Error (SSE) — R/WC.

0 = No system error signaled.

1 = Set when the Gb LAN controller s ignals a system error to the internal SERR# logic.

Received Master Abort (RMA) — R/WC.

0 = Root port has not received a completion with unsupported request status from the

backbone.

1 = Set when the Gb LAN controller receives a completi on with unsupported request

status from the backbone.

Received Target Abort (RTA) — R/WC.

0 = Root port has not received a completion with completer abort from the backbone.

1 = Set when the Gb LAN controller receives a completion with completer abort from

the backbone.

Signaled Target Abort (STA) — R/WC .

0 = No target abort received.

1 = S et whenever the Gb LAN co ntroller forwards a target abort received from the

downstream device onto the backbone.

10:9 DEVSEL# Timing Status (DEV_STS) — RO. Hardwired to ‘0’.

Master Data Parity Error Detected (DPED) — R/WC.

0 = No data parity error received.

1 = Set when the Gb LAN Controller receives a completion with a data parity error on

the backbone and PCIMD.PER (D25:F0, bit 6) is set.

7 Fast Back to Back Capable (FB2BC) — RO. Hardwired to ‘0’.

6Reserved

5 66 MHz Capable — RO. Hardwired to ‘0’.

4 Capabilities List — RO. Hardwired to ‘1’. Indicates the presence of a capabilities list.

Interrupt Status — RO. Indicates status of Hot-Plug and power management

interrupts on the root port that result in INTx# message generation.

0 = Interrupt is deasserted.

1 = Interrupt is asserted.

This bit is not set if MSI is enabled. If MSI is not enabled, this bit is set regardless of the

state of PCICMD.Interrupt Disable bit (D25:F0:04h:bit 10).

2:0 Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 415

Gigabit LAN Configuration Registers

12.1.5 RID—Revision Identification Register

(Gigabit LAN—D25:F0)

Offset Address: 08h Attribute: RO

Default Value: See bit description Size: 8 bits

12.1.6 CC—Class Code Register

(Gigabit LAN—D25:F0)

Address Offset: 09h–0Bh Attribute: RO

Default Value: 020000h Size: 24 bits

12.1.7 CLS—Cache Line Size Register

(Gigabit LAN—D25:F0)

Address Offset: 0Ch Attribute: R/W

Default Value: 00h Size: 8 bits

12.1.8 PLT—Primary Latency Timer Register

(Gigabit LAN—D25:F0)

Address Offset: 0Dh Attribute: RO

Default Value: 00h Size: 8 bits

12.1.9 HT—Header Type Register

(Gigabit LAN—D25:F0)

Address Offset: 0Eh Attribute: RO

Default Value: 00h Size: 8 bits

Bit Description

7:0 Revision ID — RO. R e fer to the Intel® I/O Controller Hub (ICH9) Family Specification

Update for the value of the Revision ID Register

Bit Description

23:0 Class Code— RO. Identifies the device as an Ethernet Adapter.

020000h = Ethernet Adapter.

Bit Description

7:0 Cache Line Size — R/W. This field is implemented by PCI devices as a read write field

for legacy compatibility purposes but has no impact on any device functionality.

Bit Description

7:0 Latency Timer (LT) — RO. Hardwired to ‘0’.

Bit Description

7:0 Header Type (HT) — RO.

00h = Indicates this is a single function device.

Gigabit LAN Configuration Registers

416 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

12.1.10 MBARA—Memory Base Address Register A

(Gigabit LAN—D25:F0)

Address Offset: 10h–13h Attribute: R/W, RO

Default Value: 00000000h Size: 32 bits

The internal CSR registers and memories are accessed as direct memory mapped

offsets from the base address register. SW may only access whole DWord at a time.

12.1.11 MBARB—Memory Base Address Register B

(Gigabit LAN—D25:F0)

Address Offset: 14h–17h Attribute: R/W, RO

Default Value: 00000000h Size: 32 bits

The internal registers that are used to access the LAN Space in the External FLASH de-

vice. Access to these registers are direct memory mapped offsets from the base address

Bit Description

31:17 Base Address (BA) — R/W. Software programs this field with the base address of

this region.

16:4 Memory Size (MSIZE) — R/W. Memory size is 128K Bytes.

3Prefetchable Memory (P M) — RO. The GbE LAN control ler does not implement

prefetchable memory.

2:1 Memory Type (MT) — RO. Set to 00b indicating a 32 bit BAR.

0Memory / IO Space (MIOS) — RO. Set to ‘0’ indicating a Memory Space BAR.

Bit Description

31:12 Base Address (BA) — R/W. Software programs this field with the base address of

this region.

11:4 Memory Size (MSIZE) — R/W. Memory size is 4K Bytes.

3Prefetchable Memory (P M) — RO. The Gb LAN control ler does not implem ent

prefetchable memory.

2:1 Memory Type (MT) — RO. Set to 00b indicating a 32 bit BAR.

0Memory / IO Space (MIOS) — RO. Set to ‘0’ indicating a Memory Space BAR.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 417

Gigabit LAN Configuration Registers

12.1.12 MBARC—Memory Base Address Register C

(Gigabit LAN—D25:F0)

Address Offset: 18h–1Bh Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

Internal registers, and memories, can be accessed using I/O operations. There are two

4B registers in the IO mapping window: Addr Reg and Data Reg. SW may only access a

Dword at a time.

12.1.13 SVID—Subsystem Vendor ID Register

(Gigabit LAN—D25:F0)

Address Offset: 2Ch –2Dh Attribute: RO

Default Value: See bit description Size: 16 bits

12.1.14 SID—Subsystem ID Register

(Gigabit LAN—D25:F0)

Address Offset: 2Eh–2Fh Attribute: RO

Default Value: See bit description Size: 16 bits

12.1.15 ERBA—Expansion ROM Base Address Register

(Gigabit LAN—D25:F0)

Address Offset: 30h–33h Attribute: RO

Default Value: See bit description Size: 32 bits

Bit Description

31:5 Base Address (BA) — R/W. Software programs this field with the base address of

this region.

4:1 I/O Size (IOSIZE) — RO. I/O space size is 32 Bytes.

0Memory / IO Space (MIOS) — RO. Set to ‘1’ indicating an IO Space BAR.

Bit Description

15:0

Subsystem Vendor ID (SVID) — RO. This value may be loaded automatically from

the NVM Word 0Ch upon power up depending on the "Load Subsystem ID" bit field in

NVM word 0Ah. A value of 8086h i s default for this field upon power up if the NVM does

not respond or is not programmed. All functions are initialized to the same value.

Bit Description

15:0

Subsystem ID (SID) — RO. This value may be loaded automatica lly from the NVM

Word 0Bh upon power up or reset depending on the “Load Subsystem ID” bit field in

NVM word 0Ah with a default value of 0000h. This value is loadable from NVM word

location 0Bh.

Bit Description

32:0 Expansion ROM Base Address (ERBA) — RO. This register is used to define the

address and size information for boot-time ac cess to the optional F LASH memory. If no

Flash memory exists this register reports 00000000h.

Gigabit LAN Configuration Registers

418 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

12.1.16 CAPP—Capabilities List Pointer Register

(Gigabit LAN—D25:F0)

Address Offset: 34h Attribute: R0

Default Value: C8h Size: 8 bits

12.1.17 INTR—Interrupt Information Register

(Gigabit LAN—D25:F0)

Address Offset: 3Ch–3Dh Attribute: R/W, RO

Default Value: 0100h Size: 16 bits

Function Level Reset: No

12.1.18 MLMG—Maximum Latency/Minimum Grant Register

(Gigabit LAN—D25:F0)

Address Offset: 3Eh Attribute: RO

Default Value: 00h Size: 8 bits

12.1.19 CLIST 1—Capabilities List Register 1

(Gigabit LAN—D25:F0)

Address Offset: C8h–C9h Attribute: RO, R/WO

Default Value: D001h Size: 16 bits

Bit Description

7:0 Capabilities Pointer (PTR) — RO. Indicates that the pointer for the first entry in the

capabilities list is at C8h in configuration space.

Bit Description

15:8 Interrupt Pin (IPIN) — RO. Indicates the interrupt pin driven by the Gb LAN

controller.

01h = The Gb LAN controller implements legacy inte rrupts on INTA.

7:0 Interrupt Line (ILINE) — R/W. Default = 00h. Software written value to indicate

which interrupt line (vector) the interrupt is connect ed to. No hardware action is taken

on this register.

Bit Description

7:0 Maximum Latency/Minimum Grant (MLMG) — RO. Not used. Hardwired to 00h.

Bit Description

15:8 Next Capability (NEXT) — RO . Value of D0h indicates the location of the next point er.

7:0 Capability ID (CID) — RO. Indicates the linked list item is a PCI Power Management

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 419

Gigabit LAN Configuration Registers

12.1.20 PMC—PCI Power Management Capabilities Register

(Gigabit LAN—D25:F0)

Address Offset: CAh–CBh Attribute: RO

Default Value: See bit descriptions Size: 16 bits

Function Level Reset: No (Bits 15:11 only)

Bit Description

15:11

PME_Support (PMES) — RO. This five-bit field indicates the power states in which the

function may assert PME#. It depend on PM Ena and AUX-PWR bits in word 0Ah in the

NVM:

These bits are not reset by Function Level Reset.

10 D2_Support (D2S) — RO. The D2 state is not su pported.

9D1_Support (D1S) — RO. The D1 state is not supported.

8:6 Aux_Current (AC) — RO. Required current defined in the Data Register.

5Device Specific Initialization (DSI) — RO. Set to ‘1’. The GbE LAN Controller

requires its device driver to be executed following transition to the D0 un-initialized

state.

4 Reserved

3 PME Clock (PMEC) — RO. Hardwired to ‘0’.

2:0 Version (VS) — RO. Hardwired to 010b to indicate support for Revision 1.1 of the PCI

Power Management Specification.

Condition Function Value

PM Ena=0 No PME at all states 0000b

PM Ena & AUX-PWR=0 PME at D0 and D3hot 01001b

PM Ena & AUX-PWR=1 PME at D0, D3hot and

D3cold 11001b

Gigabit LAN Configuration Registers

420 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

12.1.21 PMCS—PCI Power Management Control and Status

Address Offset: CCh–CDh Attribute: R/WC, R/W, RO

Default Value: See bit description Size: 16 bits

Function Level Reset: No (Bit 8 only)

Bit Description

15 PME Status (PMES) — R/WC. This bit is set to ‘1’ when the function detects a wake-

up event independent of the state of the PMEE bit. Writing a “1” will clear this bit.

14:13

Data Scale (DSC) — R/W. This field indic a tes the scaling factor to be used when

interpreting the value of the Data register.

For the GbE LAN and co mmon func tions t his fi eld equal s 01b (indicati ng 0.1 wat t units)

if the PM is enabled in the NVM, and the Data_Select field is set to 0, 3, 4, 7, (or 8 for

Function 0). Else it equals 00b.

For the manageability functions this field equals 10b (indicating 0.01 watt units) if the

PM is enabled in the NVM, and the Data_Select field is set to 0, 3, 4, 7. Else it equals

00b.

12:9

Data Select (DSL) — R/W. This four-bit field is used to select which data is to be

reported through the Data register (offset CFh) and Data_Scale field. These bits are

writeable only when the Power Management is enabled via NVM.

0h = D0 Power Consumption

3h = D3 Power Consumption

4h = D0 Power Dissipation

7h = D3 Power Dissipation

8h = Common Power

All other values are reserved.

PME Enable (PMEE) — R/W. If Power Management is enabled in the NVM, writing a ‘1’

to this register will enable Wakeup. If Power Management is disabled in the NVM,

writing a “1” to this bit has no affect, and will not set the bit to “1”. This bit is not reset

by Function Level Reset.

7:2 Reserved - Returns a value of ‘000000’.

1:0

Power State (PS) — R/W. This field is used both to determine the current power state

of the GbE LAN Controller and to set a new power state. The values are:

00 – D0 state (default)

01 – Ignored

10 – Ignored

11 – D3 state (Power Management must be enables in the NVM or this cycle will be

ignored).

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 421

Gigabit LAN Configuration Registers

12.1.22 DR—Data Register

(Gigabit LAN—D25:F0)

Address Offset: CFh Attribute: RO

Default Value: See bit description Size: 8 bits

12.1.23 CLIST 2—Capabilities List Register 2

(Gigabit LAN—D25:F0)

Address Offset: D0h–D1h Attribute: R/W O, RO

Default Value: E005h Size: 16 bits

Function Level Reset: No (Bits 15:8 only)

12.1.24 MCTL—Message Control Register

(Gigabit LAN—D25:F0)

Address Offset: D2h–D3h Attribute: R/W, RO

Default Value: 0080h Size: 16 bits

Bit Description

7:0

Reported Data (RD) — RO. This register is used to report power consumption and

heat dissipation . This r egister is controll ed by the Dat a_Selec t field i n the PM CS (Offset

CCh, bits 12:9), and the power scale is reported in the Data_Scale field in the PMCS

(Offset CCh, bits 14:13). The data of this field is loaded from the NVM if PM is enabled

in the NVM or with a default value of 0x00 otherwise.

Bit Description

15:8 Next Capability (NEXT) — R/WO. Value of E0h points to the Function Level Reset

capability structure.

These bits are not reset by Function Level Reset.

7:0 Capability ID (CID) — RO. Indicates the linked list item is a Mes sage Signaled

Interrupt Register.

Bit Description

15:8 Reserved

764-bit Capable (CID) — RO. Set to ‘1’ to indicate that the GbE LAN Con tro ller is

capable of generating 64-bit message addresses.

6:4 Multiple Message Enable (MME) — RO. Returns 000b to indicate that the GbE LAN

controller only supports a single message.

3:1 Multiple Message Capable (MMC) — RO. The GbE LAN cont roller does not support

multiple messages.

MSI Enable (MSIE) — R/W.

0 = MSI generation is disabled.

1 = The Gb LAN controller will generate MSI for interrupt assertion instead of INTx

signaling.

Gigabit LAN Configuration Registers

422 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

12.1.25 MADDL—Message Address Low Register

(Gigabit LAN—D25:F0)

Address Offset : D4h–D7h Attribute: R/W

Default Value: See bit description Size: 32 bits

12.1.26 MADDH—Message Address High Register

(Gigabit LAN—D25:F0)

Address Offset: D8h–DBh Attribute: R/W

Default Value: See bit description Size: 32 bits

12.1.27 MDAT—Message Data Register

(Gigabit LAN—D25:F0)

Address Offset: DCh–DDh Attribute: R/W

Default Value: See bit description Size: 16 bits

12.1.28 FLRCAP—Function Level Reset Capability

(Gigabit LAN—D25:F0)

Address Offset: E0h–E1h Attribute: RO

Default Value: 0009h Size: 16 bits

Bit Description

31:0 Message Address Low (MADDL) — R/W. Written by the system to indi cate the lower

32 bits of the address to use for the MSI memory write transaction. The lower two bits

will always return 0 regardless of the write operation.

Bit Description

31:0 Message Address High (MADDH) — R/W. Written by the system to indicate the

upper 32 bits of the address to use for the MSI memory write transaction.

Bit Description

31:0 Message Data (MDAT) — R/W. W ritte n by the sys tem to indi cate th e lower 16 bits of

the data writte n in the MS I memory writ e DW ORD transaction. The upper 16 bits of the

transaction are written as 0000h.

Bit Description

15:8 Next Pointer — RO. This field provides an offset to the ne xt capabil ity item in the

capability list. The value of 00h indicates the last item in the list.

7:0 Capability ID — RO. The value of this field depends on the FLRCSSEL bit.

13h = If FLRCSSEL = 0

09h = If FLRCSSEL = 1, indicating vendor specific capability.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 423

Gigabit LAN Configuration Registers

12.1.29 FLRCLV—Function Level Reset Capability Length and

Version

(Gigabit LAN—D25:F0)

Address Offset: E2h–E3h Attribute: R/WO, RO

Default Value: See Description. Size: 1 6 bits

Function Level Reset: No (Bits 9:8 Only When FLRCSSEL = 0)

When FLRCSSEL = 0, this register is defined as follows:

When FLRCSSEL = 1, this register is defined as follows:

12.1.30 DEVCTRL—Device Control (Gigabit LAN—D25:F0)

Address Offset: E 4-E5h Attribute: R/W, RO

Default Value: 0000h Size: 16 bits

Bit Description

15:10 Reserved.

9Function Level Reset Capability — R/WO.

1 = Support for Function Level Reset.

This bit is not reset by Function Level Reset.

8TXP Capability — R/WO.

1 = Indicates support for the Transactions Pending (TXP) bit. TXP must be supported if

FLR is supported.

7:0 Capability Length — RO. The value of this field indicates the number of bytes of the

vendor specific capability as require by the PCI spec. It has the value of 06h for the

Function Level Reset capability.

Bit Description

15:12 Vendor Specific Capability ID — RO. A value of 2h in this field identifies this

capability as Func tion Level Reset.

11:8 Capability Version— RO. The value of this field indicates the version of the Function

Level Reset Capability. Default is 0h.

7:0 Capability Length — RO. The value of this field indicates the number of bytes of the

vendor specific capability as require by the PCI spec. It has the value of 06h for the

Function Level Reset capability.

Bit Description

15:9 Reserved.

Transactions Pending (TXP) — R/W.

1 = Indi cates the controller has issued Non-Posted requests which have not been

completed.

0 = Indicates that completions for all Non-Posted requests have been received.

7:1 Reserved

0Initiate Function Level Reset — RO. This bit is used to initiate an FLT transition. A

write of ‘1’ initiates the transition. Since hardware must not respond to any cycles until

Function Level Reset completion, the value read by software from this bit is 0.

Gigabit LAN Configuration Registers

424 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

12.2 MBARA—Gigabit LAN Base Address A Registers

The internal CSR registers and memories are accessed as direct memory mapped

offsets from the base address register. This block is mapped into memory space, using

the MBARA Base Address register see Section 12.1.10. SW may only access whole

DWord at a time.

12.2.1 LDR4—LAN Device Initialization Register 4

(Gigabit LAN Memory Mapped Base A ddress Reg ister)

Address Offset: MBAR A + 0h Attribute: RO

Default Value: 14200100h Size: 32 bits

12.2.2 LDR3—LAN Device Initialization Register 3

(Gigabit LAN Memory Mapped Base A ddress Reg ister)

Address Offset: MBAR A + 8h Attribute: RO

Default Value: 00080xxxh Size: 32 bits

Table 12-2. Gigabit LAN Base Address A Registers Address Map (Gigabit LAN— D25:F0)

MBARA+Offset Mnemonic Register Name Default Type

00–03h LDR4 LAN Device Initialization 4 14200100h R/W

08–0Bh LDR3 LAN Device Initialization 3 00080xxxh RO

18–1Bh LDCR2 LAN Device Control 2 01500000h R/W

20–23h LDCR4 LAN Device Control 4 1000xxxxh R/W

F00h-F03h LDCR5 LAN Device Control 5 00000000h R/W

3004–3007h LDR2 LAN Device Initialization 2 B2B577CCh R/W

3024-3027h LDR1 LAN Device Initialization 1 600060006h R/W

Bit Description

31:25 Reserved

24 LDR4 Field 1 — R/W. BIOS may set this bit to 1.

23:0 Reserved

Bit Description

31 LDR3 Field 1 — RO. When set, this bit enables the automatic reduction of DMA

frequency. This bit is loaded from word 13h in the NVM.

30:0 Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 425

Gigabit LAN Configuration Registers

12.2.3 LDCR2—LAN Device Control Register 2

(Gigabit LAN Memory Mapped Base Address Register)

Address Offset: MBARA + 18h Attribute: R/W

Default Value: 01500000h Size: 32 bits

12.2.4 LDCR4—LAN Device Control Register 4

(Gigabit LAN Memory Mapped Base Address Register)

Address Offset: MBARA + 20h Attribute: R/W

Default Value: 1000xxxxh Size: 32 bits

12.2.5 LDR5—LAN Device Control Register 5

(Gigabit LAN Memory Mapped Base Address Register)

Address Offset: MBARA + F00h Attribute: R/W

Default Value: 00000000h Size: 32 bits

12.2.6 LDR2—LAN Device Initialization Register 1

(Gigabit LAN Memory Mapped Base Address Register)

Address Offset: MBARA + 3024h Attribute: R/W

Default Value: 60006006h Size: 32 bits

Bit Description

31:21 Reserved

20 LAN PHY Power Down Enable (LPPDE) — R/W. When set, enables the PH Y to ent er

a low-power state when the LAN controller is at the DMoff / D3 or Dr and no WoL.

This bit is loaded from word 13h in the NVM.

19 LDCR2 Field 1 — R/W. This bit is loaded from word 13h in the NVM.

19:0 Reserved

Bit Description

31:0 BIOS may program this field.

Bit Description

31:6 Reserved

5LDCR5 Field 1 — R/W. BIOS may set this bit.

4:0 Reserved

Bit Description

31:17 Reserved

16 LDR1 Field 1 — R/W. BIOS must program this field to 1b.

15:0 Reserved

Gigabit LAN Configuration Registers

426 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

§ §§

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 427

LPC Interface Bridge Registers (D31:F0)

13 LPC Interface Bridge Registers

(D31:F0)

The LPC bridge function of the ICH9 resides in PCI Device 31:Function 0. This function

contains many other functional units, such as DMA and Interrupt controllers, Timers,

Power Management, System Management, GPIO, RTC, and LPC Configuration

Registers.

Registers and functions associated with other functional units (EHCI, UHCI, etc.) are

described in their respective sections.

13.1 PCI Configuration Registers (LPC I/F—D31:F0)

Note: Address locations that are not shown should be treated as Reserved.

Table 13-1. LPC Interface PCI Register Address Map (LPC I/F—D31:F0) (Sheet 1 of 2)

Offset Mnemonic Register Name Default Type

00h–01h VID Vendor Identification 8086h RO

02h–03h DID Device Identification See register

description RO

04h–05h PCICMD PCI Command 0007h R/W, RO

06h–07h PCISTS PCI Status 0210h R/WC, RO

08h RID Revision Identification See register

description RO

09h PI Programming Interface 00h RO

0Ah SCC Sub Class Code 01h RO

0Bh BCC Base Class Code 06h R O

0Dh PLT Primary Latency Timer 00h RO

0Eh HEADTYP Header Type 80h RO

2Ch–2Fh SS Sub System Identifiers 00000000h R/WO

34h CAPP Capability List Pointer E0h RO

40h–43h PMBASE ACPI Base Address 00000001h R/W, RO

44h ACPI_CNTL ACPI Control 00h R/W

48h–4Bh GPIOBASE GPIO Base Address 00000001h R/W, RO

4C GC GPIO Control 00h R/W

60h–63h PIRQ[n]_ROUT PIRQ[A–D] Routing Control 80808080h R/W

64h SIRQ_CNTL Serial IRQ Control 10h R/W, RO

68h–6Bh PIRQ[n]_ROUT PIRQ[E–H] Routing Control 80808080h R/W

6C–6Dh LPC_IBDF IOxAPIC Bus:Device:Function 00F8h R/W

80h LPC_I/O_DEC I/O Decode Ranges 0000h R/W

82h–83h LPC_EN LPC I/F Enables 0000h R/W

84h–87h GEN1_DEC LPC I/F Generic Decode Range 1 00000000h R/W

LPC Interface Bridge Registers (D31 :F 0)

428 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.1.1 VID—Vendor Identification Register (LPC I/F—D31:F0)

Offset Address: 00h–01h Attribute: RO

Default Value: 8086h Size: 16-bit

Lockable: No Power Well: Core

13.1.2 DID—Device Identification Register (LPC I/F—D31:F0)

Offset Address: 02h–03h Attribute: RO

Default Value: See bit description Size: 16-bit

Lockable: No Power Well: Core

88h–8Bh GEN2_DEC LPC I/F Generic Decode Range 2 00000000h R/W

8Ch–8Eh GEN3_DEC LPC I/F Generic Decode Range 3 00000000h R/W

90h–93h GEN4_DEC LPC I/F Generic Decode Range 4 00000000h R/W

A0h–CFh Power Management (See

Section 13.8.1)

D0h–D3h FWH_SEL1 Firmware Hub Select 1 00112233h R/W, RO

D4h–D5h F WH_SEL2 Firmware Hub Select 2 4567h R/W

D8h–D9h FWH_DEC_EN1 Firmware Hub Decode Enable 1 FFCFh R/W, RO

DCh BIOS_CNTL B IOS Control 00h R/WLO, R/W ,

E0h-E1h FDCAP Feature Detection Capability ID 0009h RO

E2h FDLEN Feature Detection Capability

Length 0Ch RO

E3h FDVER Feature Detection Version 10h RO

E4h-EBh FDVCT Feature Vector See

Description RO

F0h-F3h RCBA Root Complex Base Address 00000000h R/W

Table 13-1. LPC Interface PCI Register Address Map (LPC I/F—D31:F0) (Sheet 2 of 2)

Offset Mnemonic Register Name Default Type

Bit Description

15:0 Vendor ID — RO. This is a 16-bit value assigned to Intel. Intel VID = 8086h

Bit Description

15:0 Device ID — RO. Thi s is a 16-bit value assigned to the Intel ® ICH9 LPC bridge. Refer

to the Intel® I/O Controller Hub (ICH9) Family Specification Update for the value of

the Device ID Register.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 429

LPC Interface Bridge Registers (D31:F0)

13.1.3 PCICMD—PCI COMMAND Register (LPC I/F—D31:F0)

Offset Address: 04h–05h Attribute: R/W, RO

Default Value: 0007h Size: 16-bit

Lockable: No Power Well: Core

Bit Description

15:10 Reserved

9 Fast Back to Back Enable (FBE) — RO. Hardwired to 0.

8SERR# Enable (SERR_EN) — R/W. The LPC bridge generates SERR# if this bit is set.

7 Wait Cycle Control (WCC) — RO. Hardwired to 0.

Parity Error Response Enable (PERE) — R/W.

0 = N o action is taken when detecting a parity error.

1 = Enables the ICH9 LPC bridge to respond to parity errors detected on backbone

interface.

5 VGA Palette Snoop (VPS) — RO. Hardwired to 0.

4 Memory Write and Invalidate Enable (MWIE) — RO. Hardwired to 0.

3 Special Cycle Enable (SCE) — RO. Hardwired to 0.

2 Bus Master Enable (BME) — RO. Bus Masters cannot be disabled.

1 Memory Space Enable (MSE) — RO. Memory space cannot be disabled on LPC.

0 I/O Space En able (IOSE) — RO. I/O space cannot be disabled on LPC.

LPC Interface Bridge Registers (D31 :F 0)

430 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.1.4 PCISTS—PCI Status Register (LPC I/F—D31:F0)

Offset Address: 06h–07 h Attribute: RO, R/WC

Default Value: 0210h Size: 16-bit

Lockable: No Power Well: Core

Note: For the writable bits, software must write a 1 to clear bits that are set. Writing a 0 to

the bit has no effect.

Bit Description

Detected Parity Error (DPE) — R/WC. Set when the LPC bridge detects a parity

error on the int ernal backbone. Set ev en if the PCICMD .PERE bi t (D31:F0:04, bit 6) is

0 = Parity Error Not detected.

1 = Parity Error detected.

14 Signaled System Error (SSE)— R/WC. Set wh en the LPC bridge signals a system

error to the internal SERR# logic.

Master Abort Status (RMA) — R/WC.

0 = Unsupported request status not received.

1 = The bridge received a completion with unsupported request status from the

backbone.

12 Received Target Abort (RTA) — R/WC.

0 = Completion abort not received.

1 = Completion wit h completion abort received from the backbone.

Signaled Target Abort (STA) — R/WC.

0 = Target abort Not generated on the backbone.

1 = LPC bridge generated a completion packet with target abort status on the

backbone.

10:9 DEVSEL# Timing Status (DEV_STS) — RO.

01 = Medium Timing.

Data Parity Error Detected (DPED) — R/WC.

0 = All conditions listed below Not met.

1 = Set when all three of the following conditions are met:

• LPC bridge receives a completion packet from the backbone from a previous request,

• Parity error has been detected (D31:F0:06, bit 15)

• PCICMD.PERE bit (D31:F0:04, bit 6) is set.

7Fast Back to Back Capable (FBC): Reserved – bit has no meaning on the internal

backbone.

6 Reserved.

566 MHz Capable (66MHZ_CAP) — Reserved – bit has no meaning on the internal

backbone.

4Capabilities List (CLIST) — RO. Capability list exists on the LPC bridge.

3Interrupt Status (IS) — RO. The LPC bridge does not generate interrupts.

2:0 R eserved.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 431

LPC Interface Bridge Registers (D31:F0)

13.1.5 RID—Revision Identification Register (LPC I/F—D31:F0)

Offset Address: 08h Attribute: RO

Default Value: See bit description Size: 8 bits

13.1.6 PI—Programming Interface Register (LPC I/F—D31:F0)

Offset Address: 09h Attribute: RO

Default Value: 00h Size: 8 bits

13.1.7 SCC—Sub Class Code Register (LPC I/F—D31:F0)

Offset Address: 0Ah Attribute: RO

Default Value: 01h Size: 8 bits

13.1.8 BCC—Base Class Code Register (LPC I/F—D31:F0)

Offset Address: 0Bh Attribute: RO

Default Value: 06h Size: 8 bits

13.1.9 PLT—Primary Latency Timer Register (LPC I/F—D31:F0)

Offset Address: 0Dh Attribute: RO

Default Value: 00h Size: 8 bits

Bit Description

7:0 Revision ID (RID) — RO. Refer to the Intel® I/O Controller Hub (ICH9) Family

Specification Update for the value of the Revision ID Register

Bit Description

7:0 Programming Interface — RO.

Bit Description

7:0 Sub Class Code — RO. 8-bit value that indicates the category of bridge for the LPC

bridge.

01h = PCI-to-ISA bridge.

Bit Description

7:0 Base Class Code — RO. 8-bit value that indicates the type of device for the LPC

bridge.

06h = Bridge device.

Bit Description

7:3 Master Latency Count (MLC) — Reserved.

2:0 Reserved.

LPC Interface Bridge Registers (D31 :F 0)

432 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.1.10 HEADTYP—Header Type Register (LPC I/F—D31:F0)

Offset Address: 0Eh Attrib ute: RO

Default Value: 80h Size: 8 bits

13.1.11 SS—Sub System Identifiers Register (LPC I/F—D31:F0)

Offset Address: 2Ch–2Fh Attribute: R/WO

Default Value: 00000000h Size: 32 bits

This register is initialized to logic 0 by the assertion of PLTRST#. This register can be

written only once after PLTRST# de-assertion.

13.1.12 CAPP—Capability List Pointer (LPC I/F—D31:F0)

Offset Address: 34h Attribute: RO

Default Value: E0h Size: 8 bits

13.1.13 PMBASE—ACPI Base Address Register (LPC I/F—D31:F0)

Offset Address: 40h–43h Attribute: R/W, RO

Default Value: 00000001h Size: 32 bit

Lockable: No Usage: ACPI, Legacy

Power Well: Core

Sets base address for ACPI I/O registers, GPIO registers and TCO I/O registers. These

registers can be mapped anywhere in the 64-K I/O space on 128-byte boundaries.

Bit Description

7Multi-Function Device — RO. This bit is 1 to indicate a multi-function device.

6:0 Header Type — RO. This 7-bit field identifies the header layout of the configuration

space.

Bit Description

31:16 Subsystem ID (SSID) — R/WO. This is written by BIOS. No hardware action taken on

this value.

15:0 Subsystem Vendor ID (SSVID) — R/WO. This is written by BIOS. No hardware

action taken on this value.

Bit Description

7:0 Capability Pointer (CP) — RO. Indicates the offset of the of the first capability item.

Bit Description

31:16 Reserved

15:7 Base Address — R/W. This field provides 128 bytes of I/O space for ACPI, GPIO, and

TCO logic. This is placed on a 128-byte boundary.

6:1 R eserved

0 Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate I/O space.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 433

LPC Interface Bridge Registers (D31:F0)

13.1.14 ACPI_CNTL—ACPI Control Register (LPC I/F — D31:F0)

Offset Address: 44h Attribute: R/W

Default Value: 00h Size: 8 bit

Lockable: No Usage: ACPI, Legacy

Power Well: Core

Bit Description

ACPI Enable (ACPI_EN) — R/W.

0 = Disable.

1 = Decode of the I/O range pointed to by the ACPI base register is enabled, and the

ACPI power management function is enabled. Note that the APM power

management ranges (B2/B3h) are always enabled and are not affected by this bit.

6:3 Reserved

2:0

SCI IRQ Sele ct (SCI_IRQ_SEL) — R/W.

Specifies on which IRQ the SCI will internally appear. If not using the APIC, the SCI

must be routed to IRQ9–11, and th at interrupt is no t shar able with the SERIRQ stream,

but is shareable with other PCI inte rrupts. If using the APIC, the SCI can also be

mapped to IRQ20–23, and can be shared with other interrupts.

When the interrupt is mapped to APIC interrupts 9, 10 or 11, the APIC should be

programmed for activ e-high reception. When the interrupt is mapped to APIC interrupts

20 through 23, the APIC should be programmed for active-low reception.

Bits SCI Map

000b IRQ9

001b IRQ10

010b IRQ11

011b Reserved

100b IRQ20 (Only available if APIC

enabled)

101b IRQ21 (Only available if APIC

enabled)

LPC Interface Bridge Registers (D31 :F 0)

434 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.1.15 GPIOBASE—GPIO Base Address Register (LPC I/F —

D31:F0)

Offset Address: 48h–4Bh Attribute: R/W, RO

Default Value: 00000001h Size: 32 bit

Bit Description

31:16 Reserved. Always 0.

15:7

(Mobile

Only) Base Address (BA) — R/W. Provides the 128 bytes of I/O space for GPIO.

15:6

(Desktop

Only) Base Address (BA) — R/W. Provides the 64 bytes of I/O space for GPIO.

6:1

(Mobile

Only) Reserved. Always 0.

5:1

(Desktop

Only) Reserved. Always 0.

0 RO. Hardwired to 1 to indicate I/O space.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 435

LPC Interface Bridge Registers (D31:F0)

13.1.16 GC—GPIO Control Register (LPC I/F — D31:F0)

Offset Address: 4Ch Attribute: R/W

Default Value: 00h Size: 8 bit

Bit Description

7:5 Reserved.

GPIO Enable (EN) — R/W. This bit enables/disables decode of the I/O range pointed

to by the GPIO Base Address register (D31:F0:48h) and enables the GPIO function.

0 = Disable.

1 = Enable.

3:1 Reserved.

GPIO Lockdown Enable (GLE) — R/W. This bit enables lockdown of the followin g

GPIO registers:

• Offset 00h: GPIO_USE_SEL[31:0]

• Offset 04h: GP_IO_SEL[31:0]

• Offset 0Ch: GP_LVL[31:0]

• Offset 30h: GPIO_USE_SEL[63:32]

• Offset 34h: GP_IO_SEL[63:32]

• Offset 38h: GP_LVL[63:32]

0 = Disable.

1 = Enable.

When this bit is written from a ‘1’ to a ‘0’ an SMI# is generated if enabled. This ensures

that only SMM code can change the above GPIO registers after they are locked down.

LPC Interface Bridge Registers (D31 :F 0)

436 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.1.17 PIRQ[n]_ROUT—PIRQ[A,B,C,D] Routing Control Register

(LPC I/F—D31:F0)

Offset Address: PIRQA – 60h, PIRQB – 61h,Attribute: R/W

PIRQC – 62h, PIRQD – 63h

Default Value: 80h Size: 8 bit

Lockable: No Power Well: Core

Bit Description

Interrupt Routing Enable (IRQEN) — R/W.

0 = The corresponding PIRQ is routed to one of the ISA-compatible interrupts

specified in bits[3:0].

1 = The PIRQ is not routed to the 8259.

NOTE: BIOS must program this bit to 0 during POST for any of the PIRQs that are

being used. The value of this bit may subsequently be changed by the OS

when setting up for I/O APIC interrupt delivery mode.

6:4 R eserved

3:0

IRQ Routing — R/W. (ISA compatible.)

Value IRQ Value IRQ

0000b Reserved 1000b Reserved

0001b Reserved 1001b IRQ9

0010b Reserved 1010b IRQ10

0011b IRQ3 1011b IRQ11

0100b IRQ4 1100b IRQ12

0101b IRQ5 1101b Reserved

0110b IRQ6 1110b IRQ14

0111b IRQ7 1111b IRQ15

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 437

LPC Interface Bridge Registers (D31:F0)

13.1.18 SIRQ_CNTL—Serial IRQ Control Register

(LPC I/F—D31:F0)

Offset Address: 64h Attribute: R/W, RO

Default Value: 10h Size: 8 bit

Lockable: No Power Well: Core

Bit Description

7Serial IRQ Enable (SIRQEN) — R/W.

0 = The buffer is input only and internally SERIRQ will be a 1.

1 = Serial IRQs will be recognized. The SERIRQ pin will be co nfigured as SERIRQ.

Serial IRQ Mode Select (SIRQMD) — R/W.

0 = The serial IRQ machine will be in quiet mode.

1 = The serial IRQ machine will be in continuous mode.

NOTE: F or sys tems u sing Q uiet Mode, thi s bit s hould be set to 1 (Con tin uous Mo de) for

at least one frame after coming out of reset before switching back to Quiet

Mode. Failure to do so will result in the ICH9 not recognizing SERIRQ interrupts.

5:2 Serial IRQ Frame Size (SIRQSZ) — RO. Fixed field that indicates the size of the

SERIRQ frame as 21 frames.

1:0

Start Frame Pulse Width (SFPW) — R/W. This is the number of PCI clocks that the

SERIRQ pin will be driven low by the serial IRQ machine to signal a start frame. In

continuous mode, the ICH9 will drive the start fr ame for the number of cloc ks specifie d.

In quiet mode, the ICH9 will drive the start frame for the number of clocks specified

minus one, as the first clock was driven by the peripheral.

00 = 4 clocks

01 = 6 clocks

10 = 8 clocks

11 = Reserved

LPC Interface Bridge Registers (D31 :F 0)

438 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.1.19 PIRQ[n]_ROUT—PIRQ[E,F,G,H] Routing Control Register

(LPC I/F—D31:F0)

Offset Address: PIRQE – 68h, PIRQF – 69h, Attribute: R/W

PIRQG – 6Ah, PIRQH – 6Bh

Default Value: 80h Size: 8 bit

Lockable: No Power Well: Core

Bit Description

Interrupt Routing Enable (IRQEN) — R/W.

0 = The corresponding PIRQ is routed to one of the ISA-compatible interrupts specified

in bits[3:0].

1 = The PIRQ is not routed to the 8259.

NOTE: BIOS must program this bit to 0 during POST for any of the PIRQs that are

being used. The value of this bit may subsequently be changed by the OS when

setting up for I/O APIC interrupt delivery mode.

6:4 Reserved

3:0

IRQ Routing — R/W. (ISA compatible.)

Value IRQ Value IRQ

0000b Reserved 1000b Reserved

0001b Reserved 1001b IRQ9

0010b Reserved 1010b IRQ10

0011b IRQ3 1011b IRQ11

0100b IRQ4 1100b IRQ12

0101b IRQ5 1101b Reserved

0110b IRQ6 1110b IRQ14

0111b IRQ7 1111b IRQ15

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 439

LPC Interface Bridge Registers (D31:F0)

13.1.20 LPC_IBDF—IOxAPIC Bus:Device:Function

(LPC I/F—D31:F0)

Offset Address: 6Ch-6Dh Attribute: R/W

Default Value: 00F8h Size: 16 bit

13.1.21 LPC_I/O_DEC—I/O Decode Ranges Register

(LPC I/F—D31:F0)

Offset Address: 80h Attribute: R/W

Default Value: 0000h Size: 16 bit

Bit Description

15:0

IOxAPIC Bus:Device:Functi on (I BDF)— R/W. this field specifies the

bus:device:function that ICH9’s IOxAPIC will be using for the following:

• As the Requester ID when initiating Interrupt Messages to the processor.

• As the Completer ID when responding to the reads targeting the IOxAPIC’s Memory-Mapped I/

O registers.

The 16-bit field comprises the following:

This field defaults to Bus 0: Device 31: Function 0 after reset. BIOS can program this

field to provide a unique bus:device:function number for the internal IOxAPIC.

Bits Description

15:8 Bus Number

7:3 Devic e Number

2:0 Function Number

Bit Description

15:13 Reserved

12 FDD Decode Range — R/W. Determines which range to decode for the FDD Port

0 = 3F0h – 3F5h, 3F7h (Primary)

1 = 370h – 375h, 377h (Secondary)

11:10 Reserved

9:8

LPT Decode Range — R/W. This field determines which range to decode for the LPT

Port.

00 = 378h – 37Fh and 778h – 77Fh

01 = 278h – 27Fh (port 279h is read only) and 678h – 67Fh

10 = 3BCh –3BEh and 7BCh – 7BEh

11 = Reserved

7Reserved

LPC Interface Bridge Registers (D31 :F 0)

440 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.1.22 LPC_EN—LPC I/F Enables Register (LPC I/F—D31:F0)

Offset Address: 82h – 83h Attribute: R/W

Default Value: 0000h Size: 16 bit

Power Well: Core

6:4

COMB Decode Range — R/W. This field determines which range to decode for the

COMB Port.

000 = 3F8h – 3FFh (COM1)

001 = 2F8h – 2FFh (COM2)

010 = 220h – 227h

011 = 228h – 22Fh

100 = 238h – 23Fh

101 = 2E8h – 2EFh (COM4)

110 = 338h – 33Fh

111 = 3E8h – 3EFh (COM3)

3 Reserved

2:0

COMA Decode Range — R/W. This field determines which range to decode for the

COMA Port.

000 = 3F8h – 3FFh (COM1)

001 = 2F8h – 2FFh (COM2)

010 = 220h – 227h

011 = 228h – 22Fh

100 = 238h – 23Fh

101 = 2E8h – 2EFh (COM4)

110 = 338h – 33Fh

111 = 3E8h – 3EFh (COM3)

Bit Description

15:14 Reserved

CNF2_LPC_EN — R/W. Microcontroller Enable # 2.

0 = Disable.

1 = Enables the decoding of the I/O locations 4Eh and 4Fh to the LPC interface. This

range is used for a microcontroller.

CNF1_LPC_EN — R/W. Super I/O Enable.

0 = Disable.

1 = Enables the decoding of the I/O locations 2Eh and 2Fh to the LPC interface. This

range is used for Super I/O devices.

MC_LPC_EN — R/W. M icrocontroller Enable # 1.

0 = Disable.

1 = Enables the decoding of the I/O locations 62h and 66h to the LPC interface. This

range is used for a microcontroller.

KBC_LPC_EN — R/W. Keyboard Enable.

0 = Disable.

1 = Enables the decoding of the I/O locations 60h and 64h to the LPC interface. This

range is used for a microcontroller.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 441

LPC Interface Bridge Registers (D31:F0)

13.1.23 GEN1_DEC—LPC I/F Generic Decode Range 1 Register

(LPC I/F—D31:F0)

Offset Address: 84h – 87h Attribute: R/W

Default Value: 00000000h Size: 32 bit

Power Well: Core

GAMEH_LPC_EN — R/W. High Gameport Enable

0 = Disable.

1 = Enables the decoding of the I/O locations 208h to 20Fh to the LPC interface. This

range is used for a gameport.

GAMEL_LPC_EN — R/W. Low Gameport Enable

0 = Disable.

1 = E nables the decoding of the I/O locations 200h to 207h to the LPC interface. This

range is used for a gameport.

7:4 Reserved

FDD_LPC_EN — R/W. Floppy Drive Enable

0 = Disable.

1 = Enables the decoding of the FDD range to the LPC interface. This range is selected

in the LPC_FDD/LPT Decode Range Register (D31:F0:80h, bit 12).

LPT_LPC_EN — R/W. Parallel Port Enable

0 = Disable.

1 = Enables the decoding of the LPT r ange to the LPC interface. This range is selected in

the LPC_FDD/LPT Decode Range Register (D31:F0:80h, bit 9:8).

COMB_LPC_EN — R/W. Com Port B Enable

0 = Disable.

1 = Enables the decoding of the COMB range to the LPC interface. This range is

selected in the LPC_COM Decode Range Register (D31:F0:80h, bits 6:4).

COMA_LPC_EN — R/W. Com Port A Enable

0 = Disable.

1 = Enables the decoding of the COMA range to the LPC interface. This range is

selected in the LPC_COM Decode Range Register (D31:F0:80h, bits 3:2).

Bit Description

31:24 Reserved

23:18

Generic I/O Decode Range Address[7:2] Mask — R/W. A ‘1’ in any bit position

indicates that any value in the corresponding address bit in a received cycle will be

treated as a match. The corresponding bit in the Address field, below, is ignored. The

mask is only provided for the lower 6 bits of the DW ord address, allowing for decoding

blocks up to 256 bytes in size.

17:16 Reserved

15:2 Generic I/O Decode Range 1 Base Address (GEN1_BASE) — R/W. This address is

aligned on a 128-byte boundary, and must have address lines 31:16 as 0.

NOTE: The ICH Does not provide decode down to the word or byte level

1Reserved

0Generic Decode Range 1 Enable (GEN1_EN) — R/W.

0 = Disable.

1 = Enable the GEN1 I/O range to be forwarded to the LPC I/F

LPC Interface Bridge Registers (D31 :F 0)

442 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.1.24 GEN2_DEC—LPC I/F Generic Decode Range 2 Register

(LPC I/F—D31:F0)

Offset Address: 88h – 8Bh Attribute: R/W

Default Value: 00000000h Size: 32 bit

Power Well: Core

13.1.25 GEN3_DEC—LPC I/F Generic Decode Range 3 Register

(LPC I/F—D31:F0)

Offset Address: 8Ch – 8Eh Attribute: R/W

Default Value: 00000000h Size: 32 bit

Power Well: Core

Bit Description

31:24 Reserved

23:18

Generic I/O Decode Range Address[7:2] Mask — R/W. A ‘1’ in any bit position

indicates that any value in the cor responding address bit in a received cycle will be

treated as a match. The corresponding bit in the Address field, below, is ignored. The

mask is only pr ovided for the lowe r 6 bi ts of the DWord address, allowing for decoding

blocks up to 256 bytes in size.

17:16 Reserved

15:2 Generic I/O Decode Range 2 Base Address (GEN1_BASE) — R/W.

NOTE: The ICH Does not provide decode down to the word or byte level

1 Reserved

0Generic Decode Range 2 Enable (GEN2_EN) — R/W.

0 = Disable.

1 = Enable the GEN2 I/O range to be forwarded to the LPC I/F

Bit Description

31:24 Reserved

23:18

Generic I/O Decode Range Address[7:2] Mask — R/W. A ‘1’ in any bit position

indicates that any value in the cor responding address bit in a received cycle will be

treated as a match. The corresponding bit in the Address field, below, is ignored. The

mask is only pr ovided for the lowe r 6 bi ts of the DWord address, allowing for decoding

blocks up to 256 bytes in size.

17:16 Reserved

15:2 Generic I/O Decode Range 3 Base Address (GEN3_BASE) — R/W.

NOTE: The ICH Does not provide decode down to the word or byte level

1 Reserved

0Generic Decode Range 3 Enable (GEN3_EN) — R/W.

0 = Disable.

1 = Enable the GEN3 I/O range to be forwarded to the LPC I/F

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 443

LPC Interface Bridge Registers (D31:F0)

13.1.26 GEN4_DEC—LPC I/F Generic Decode Range 4 Register

(LPC I/F—D31:F0)

Offset Address: 90h – 93h Attribute: R/W

Default Value: 00000000h Size: 32 bit

Power Well: Core

Bit Description

31:24 Reserved

23:18

Generic I/O Decode Range Address[7:2] Mask — R/W. A ‘1’ in any bit position

indicates that any value in the corresponding address bit in a received cycle will be

treated as a match. The corresponding bit in the Address field, below, is ignored. The

mask is only provided for the lower 6 bits of the DW ord address, allowing for decoding

blocks up to 256 bytes in size.

17:16 Reserved

15:2 Generic I/O Decode Range 4 Base Address (GEN4_BASE) — R/W.

NOTE: The ICH Does not provide decode down to the word or byte level

1Reserved

0Generic Decode Range 4 Enable (GEN4_EN) — R/W.

0 = Disable.

1 = Enable the GEN4 I/O range to be forwarded to the LPC I/F

LPC Interface Bridge Registers (D31 :F 0)

444 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.1.27 FWH_SEL1—Firmware Hub Select 1 Register

(LPC I/F—D31:F0)

Offset Address: D0h–D3h Attribute: R/W, RO

Default Value: 00112233h Size: 32 bits

Bit Description

31:28

FWH_F8_IDSEL — RO. IDSEL for two 512-KB Firm ware Hub memory r anges and one

128-KB memory range. This field is fixed at 0000. The IDSEL programmed in this field

addresses the followin g memory ranges:

FFF8 0000h – FFFF FFFFh

FFB8 0000h – FFBF FFFFh

000E 0000h – 000F FFFFh

27:24

FWH_F0_IDSEL — R/W. IDSEL for two 512-KB Firmware Hub memory ranges. The

IDSEL programmed in this field addresses the following memory ranges:

FFF0 0000h – FFF7 FFFFh

FFB0 0000h – FFB7 FFFFh

23:20

FWH_E8_IDSEL — R/W. IDSEL for two 512-KB Firmware Hub memory ranges. The

IDSEL programmed in this field addresses the following memory ranges:

FFE8 0000h – FFEF FFFFh

FFA8 0000h – FFAF FFFFh

19:16

FWH_E0_IDSEL — R/W. IDSEL for two 512-KB Firmware Hub memory ranges. The

IDSEL programmed in this field addresses the following memory ranges:

FFE0 0000h – FFE7 FFFFh

FFA0 0000h – FFA7 FFFFh

15:12

FWH_D8_IDSEL — R/W. IDSEL for two 512-KB Firmware Hub memory ranges. The

IDSEL programmed in this field addresses the following memory ranges:

FFD8 0000h – FFDF FFFFh

FF98 0000h – FF9F FFFFh

11:8

FWH_D0_IDSEL — R/W. IDSEL for two 512-KB Firmware Hub memory ranges. The

IDSEL programmed in this field addresses the following memory ranges:

FFD0 0000h – FFD7 FFFFh

FF90 0000h – FF97 FFFFh

7:4

FWH_C8_IDSEL — R/W. IDSEL for two 512-KB Firmware Hub memory ranges. The

IDSEL programmed in this field addresses the following memory ranges:

FFC8 0000h – FFCF FFFFh

FF88 0000h – FF8F FFFFh

3:0

FWH_C0_IDSEL — R/W. IDSEL for two 512-KB Firmware Hub memory ranges. The

IDSEL programmed in this field addresses the following memory ranges:

FFC0 0000h – FFC7 FFFFh

FF80 0000h – FF87 FFFFh

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 445

LPC Interface Bridge Registers (D31:F0)

13.1.28 FWH_SEL2—Firmware Hub Select 2 Register

(LPC I/F—D31:F0)

Offset Address: D4h–D5h Attribute: R/W

Default Value: 4567h Size: 16 bits

13.1.29 FWH_DEC_EN1—Firmware Hub Decode Enable Register

(LPC I/F—D31:F0)

Offset Address: D8h–D9h Attribute: R/W, RO

Default Value: FFCFh Size: 16 bits

Bit Description

15:12

FWH_70_IDSEL — R/W. IDSEL for two, 1-M Firmware Hub memory ranges.

The IDSEL programmed in this field addresses the following memory ranges:

FF70 0000h – FF7F FFFFh

FF30 0000h – FF3F FFFFh

11:8

FWH_60_IDSEL — R/W. IDSEL for two, 1-M Firmware Hub memory ranges.

The IDSEL programmed in this field addresses the following memory ranges:

FF60 0000h – FF6F FFFFh

FF20 0000h – FF2F FFFFh

7:4

FWH_50_IDSEL — R/W. IDSEL for two, 1-M Firmware Hub memory ranges.

The IDSEL programmed in this field addresses the following memory ranges:

FF50 0000h – FF5F FFFFh

FF10 0000h – FF1F FFFFh

3:0

FWH_40_IDSEL — R/W. IDSEL for two, 1-M Firmware Hub memory ranges.

The IDSEL programmed in this field addresses the following memory ranges:

FF40 0000h – FF4F FFFFh

FF00 0000h – FF0F FFFFh

Bit Description

FWH_F8_EN — RO. This bit enables decoding two 512-KB Firmware Hub memory

ranges, and one

128-KB memory range.

0 = Disable

1 = Enable the following ranges for the Firmware Hub

FFF80000h – FFFFFFFFh

FFB80000h – FFBFFFFFh

FWH_F0_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub:

FFF00000h – FFF7FFFFh

FFB00000h – FFB7FFFFh

FWH_E8_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub:

FFE80000h – FFEFFFFh

FFA80000h – FFAFFFFFh

LPC Interface Bridge Registers (D31 :F 0)

446 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

FWH_E0_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub:

FFE00000h – FFE7FFFFh

FFA00000h – FFA7FFFFh

FWH_D8_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FFD80000h – FFDFFFFFh

FF980000h – FF9FFFFFh

FWH_D0_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FFD00000h – FFD7FFFFh

FF900000h – FF97FFFFh

FWH_C8_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FFC80000h – FFCFFFFFh

FF880000h – FF8FFFFFh

FWH_C0_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FFC00000h – FFC7FFFFh

FF800000h – FF87FFFFh

FWH_Legacy_F_EN — R/W. This enables the decoding of the legacy 64KB range at

F0000h – FFFFFh.

0 = Disable.

1 = Enable the following legacy ranges for the Firmware Hub

F0000h – FFFFFh

Note: The decode for the BIOS legacy F segment is enabled only by this bit and is no t

affected by the GEN_PMCON_1.iA64_EN bit.

FWH_Legacy_E_EN — R/W. This enables the decoding of the legacy 64KB range at

E0000h – EFFFFh.

0 = Disable.

1 = Enable the following legacy ranges for the Firmware Hub

E0000h – EFFFFh

Note: The decode for the BIOS legacy E segment is enabled only by this bit and is not

affected by the GEN_PMCON_1.iA64_EN bit.

5:4 Reserved

FWH_70_EN — R/W. Enables decoding two 1-M Firmware Hub memory ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FF70 0000h – FF7F FFFFh

FF30 0000h – FF3F FFFFh

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 447

LPC Interface Bridge Registers (D31:F0)

FWH_E0_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub:

FFE00000h – FFE7FFFFh

FFA00000h – FFA7FFFFh

FWH_D8_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FFD80000h – FFDFFFFFh

FF980000h – FF9FFFFFh

FWH_D0_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FFD00000h – FFD7FFFFh

FF900000h – FF97FFFFh

FWH_C8_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FFC80000h – FFCFFFFFh

FF880000h – FF8FFFFFh

FWH_C0_EN — R/W. This bit enables decoding two 512-KB Firmware Hub memory

ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FFC00000h – FFC7FFFFh

FF800000h – FF87FFFFh

FWH_Legacy_F_EN — R/W. This enables the decoding of the legacy 64KB range at

F0000h – FFFFFh.

0 = Disable.

1 = Enable the following legacy ranges for the Firmware Hub

F0000h – FFFFFh

Note: The decode for the BIOS legacy F segment is enabled only by this bit and is no t

affected by the GEN_PMCON_1.iA64_EN bit.

FWH_Legacy_E_EN — R/W. This enables the decoding of the legacy 64KB range at

E0000h – EFFFFh.

0 = Disable.

1 = Enable the following legacy ranges for the Firmware Hub

E0000h – EFFFFh

Note: The decode for the BIOS legacy E segment is enabled only by this bit and is not

affected by the GEN_PMCON_1.iA64_EN bit.

5:4 Reserved

FWH_70_EN — R/W. Enables decoding two 1-M Firmware Hub memory ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FF70 0000h – FF7F FFFFh

FF30 0000h – FF3F FFFFh

Bit Description

LPC Interface Bridge Registers (D31 :F 0)

448 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE: This register effects the BIOS decode regardless of whether the BIOS is resident

on LPC or SPI. The concept of Feature Space does not apply to SPI-based flash. The

ICH simply decodes these ranges as memory accesses when enabled for the SPI flash

interface.

FWH_60_EN — R/W. Enables decoding two 1-M Firmware Hub memory ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FF60 0000h – FF6F FFFFh

FF20 0000h – FF2F FFFFh

FWH_50_EN — R/W. Enables decoding two 1-M Firmware Hub memory ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FF50 0000h – FF5F FFFFh

FF10 0000h – FF1F FFFFh

FWH_40_EN — R/W. Enables decoding two 1-M Firmware Hub memory ranges.

0 = Disable.

1 = Enable the following ranges for the Firmware Hub

FF40 0000h – FF4F FFFFh

FF00 0000h – FF0F FFFFh

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 449

LPC Interface Bridge Registers (D31:F0)

13.1.30 BIOS_CNTL—BIOS Control Register

(LPC I/F—D31:F0)

Offset Address: DCh A ttribute: R/WLO, R/W, RO

Default Value: 00h Size: 8 bit

Lockable: No Power Well: Core

Bit Description

7:5 Reserved

4Top Swap Status (TSS) — RO . This bit provides a read-only path to view the state of

the Top Swap bit that is at offset 3414h, bit 0.

3:2

SPI Read Configuration (SRC) — R/W. This 2-bit field controls two policies related to

BIOS reads on the SPI interface:

Bit 3- Prefetch Enable

Bit 2- Cache Disable

Settings are summarized below:

BIOS Lock Enable (BLE) — R/WLO.

0 = Setting the BIOSWE will not cause SMIs.

1 = Enables settin g the BIOSWE bit to cause SMIs. Once set, t his bit can only be

cleared by a PLTRST#

BIOS Write Enable (BIOSWE) — R/W.

0 = Only read cycles result in Firmware Hub I/F cycles.

1 = Access to the BIOS space is enabled for both read and write cycles. When this bit is

written from a 0 to a 1 and BIOS Lock Enable (BLE) is also set, an SMI# is

generated. This ensures that only SMI code can update BIOS.

Bits 3:2 Description

00b No prefetching, but caching enabled. 64B demand reads load

the read buffer cache with “valid” data, allowing repeated code

fetches to t he same line to complete quic kly

01b No prefetching and no caching. One-to-one correspondence of

host BIOS reads to SPI cycles. This value can be used to invalidate

the cache.

10b Prefetching and Caching enabled. This mode is used for long

sequences of short reads to consecutive addresses (i.e. , shadowing).

11b Reserved. This is an invalid configuration, caching must be

enabled when prefetching is enabled.

LPC Interface Bridge Registers (D31 :F 0)

450 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.1.31 FDCAP—Feature Detection Capability ID

(LPC I/F—D31:F0)

Offset Address: E0h-E1h Attribute: RO

Default Value: 0009h Size: 16 bit

Power Well: Core

13.1.32 FDLEN—Feature Detection Capability Length

(LPC I/F—D31:F0)

Offset Address: E2h Attribute: RO

Default Value: 0Ch S i ze: 8 bit

Power Well: Core

13.1.33 FDVER—Feature Detection Version

(LPC I/F—D31:F0)

Offset Address: E3h Attribute: RO

Default Value: 10h Size: 8 bit

Power Well: Core

Bit Description

15:8 Next Item Pointer (NEXT) — RO. Configuration offset of the next Capability Item.

00h indica tes the last item in the Capability List.

7:0 Capability ID — RO. Indicates a Vendor Specific Capability

Bit Description

7:0 Capability Length — RO. Indicates the length of this Vendor Specific capability, as

required by PCI Spec.

Bit Description

7:4 Vendor-Specific Capability ID — RO. A value of 1h in this 4-bit field identifies this

Capability as Feature Detection Type. This field allows software to differentiate the

Feature Detection Capability from other Vendor-Specific capabilities

3:0 Capability Version — RO. This field indicates the version of the Feature Detection

capability

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 451

LPC Interface Bridge Registers (D31:F0)

13.1.34 FDVCT—Feature Vector

(LPC I/F—D31:F0)

Offset Address: E4h-EBh Attribute: RO

Default Value: See Description Size: 64 bit

Power Well: Core

13.1.35 RCBA—Root Complex Base Address Register

(LPC I/F—D31:F0)

Offset Address: F0-F3h Attribute: R/W

Default Value: 00000000h Size: 32 bit

Bit Description

63:39 Reserved

38:37 Intel Active Management Technology Capability — RO.

00 = Capable

11 = Disabled

36:28 Reserved

27 Desktop SATA Ports 2 & 3 Capability — RO.

0 = Capable

1 = Disabled

26:10 Reserved

(Desktop

Only) Reserved

(Mobile

Only)

Mobile Features Capability— RO.

0 = Disabled

1 = Capable

8:6 Reserved

5SATA RAID 0/1/5/10 Capability— RO:

0 = Capable

1 = Disabled

4:0 Reserved

Bit Description

31:14 Base Address (BA) — R/W. Base Address for the root complex register block decode

range. This address is aligned on a 16-KB boundary.

13:1 Reserved

0Enable (EN) — R/W. When set, enables the range specified in BA to be claimed as the

Root Complex Register Block.

LPC Interface Bridge Registers (D31 :F 0)

452 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.2 DMA I/O Registers (LPC I/F—D31:F0)

Table 13-2. DMA Registers (Sheet 1 of 2)

Port Alias Register Name Default Type

00h 10h Channel 0 DMA Base & Current Address Undefined R/W

01h 11h Channel 0 DMA Base & Current Count Undefined R/W

02h 12h Channel 1 DMA Base & Current Address Undefined R/W

03h 13h Channel 1 DMA Base & Current Count Undefined R/W

04h 14h Channel 2 DMA Base & Current Address Undefined R/W

05h 15h Channel 2 DMA Base & Current Count Undefined R/W

06h 16h Channel 3 DMA Base & Current Address Undefined R/W

07h 17h Channel 3 DMA Base & Current Count Undefined R/W

08h 18h Channel 0–3 DMA Command Undefined WO

Channel 0–3 DMA Status Undefined RO

0Ah 1Ah Channel 0–3 DMA Write Single Mask 000001XXb WO

0Bh 1Bh Channel 0–3 DMA Channel Mode 000000XXb WO

0Ch 1Ch Channel 0–3 DMA Clear Byte Pointer Undefined WO

0Dh 1Dh Channel 0–3 DMA Master Clear Undefined WO

0Eh 1Eh Channel 0–3 DMA Clear Mask Undefined WO

0Fh 1Fh Channel 0–3 DMA Write All Mask 0Fh R/W

80h 90h Reserved Page Undefined R/W

81h 91h Channel 2 DMA Memory Low Page Undefined R/W

82h — Channel 3 DMA Memory Low Page Undefined R/W

83h 93h Channel 1 DMA Memory Low Page Undefined R/W

84h–86h 94h–96h Reserved Pages Undefined R/W

87h 97h Channel 0 DMA Memory Low Page Undefined R/W

88h 98h Reserved Page Undefined R/W

89h 99h Channel 6 DMA Memory Low Page Undefined R/W

8Ah 9Ah Channel 7 DMA Memory Low Page Undefined R/W

8Bh 9Bh Channel 5 DMA Memory Low Page Undefined R/W

8Ch–8Eh 9Ch–9Eh Reserved Page Undefined R/W

8Fh 9Fh Refresh Low Page Undefined R/W

C0h C1h Channel 4 DMA Base & Current Address Undefined R/W

C2h C3h Channel 4 DMA Base & Current Count Undefined R/W

C4h C5h Channel 5 DMA Base & Current Address Undefined R/W

C6h C7h Channel 5 DMA Base & Current Count Undefined R/W

C8h C9h Channel 6 DMA Base & Current Address Undefined R/W

CAh CBh Channel 6 DMA Base & Current Count Undefined R/W

CCh CDh Channel 7 DMA Base & Current Address Undefined R/W

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 453

LPC Interface Bridge Registers (D31:F0)

13.2.1 DMABASE_CA—DMA Base and Current Address

Registers (LPC I/F—D31:F0)

I/O Address: Ch. #0 = 00h; Ch. #1 = 02h Attribute: R/W

Ch. #2 = 04h; Ch. #3 = 06h Size: 1 6 bit (per channel),

Ch. #5 = C4h Ch. #6 = C8h but accessed in two 8-bit

Ch. #7 = CCh; quantities

Default Value: Undefined

Lockable: No Power Well:Core

CEh CFh Channel 7 DMA Base & Current Count Undefined R/W

D0h D1h Channel 4–7 DMA Command Undefined WO

Channel 4–7 DMA Status Undefined RO

D4h D5h Channel 4–7 DMA Write Single Mask 000001XXb WO

D6h D7h Channel 4–7 DMA Channel Mode 000000XXb WO

D8h D9h Channel 4–7 DMA Clear Byte Pointer Undefined WO

DAh DBh C hannel 4–7 DMA Master Clear Undefined WO

DCh DDh Channel 4–7 DMA Clear Mask Undefined WO

DEh DFh Channel 4–7 DMA Write All Mask 0Fh R/W

Table 13-2. DMA Registers (Sheet 2 of 2)

Port Alias Register Name Default Type

Bit Description

15:0

Base and Current Address — R/W. This register determines the address for the

transfers to be performed. The address specified points to two separate registers. On

writes, the value is stored in the Base Address register and copied to the Current

Address register. On reads, the value is returned from the Current Address register.

The address i ncrements/decrement s in the Current Address re gister after each tr ansfer,

depending on the mode of the transfer. If the channel is in auto-initialize mode, the

Current Address register will be reloaded from the Base Address register after a

terminal count is generated.

For transfers to/from a 16-bit slave (channel’s 5-7), the address is shifted left one bit

location. Bit 15 will be shifted into Bit 16.

The register is accessed in 8 bit quantities. The byte is pointed to by the current byte

pointer flip/flop. Before accessing an address register, the byte pointer flip/ flop should

be cleared to ensure that the low byte is accessed first

LPC Interface Bridge Registers (D31 :F 0)

454 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.2.2 DMABASE_CC—DMA Base and Current Count Registers

(LPC I/F—D31:F0)

I/O Address: Ch. #0 = 01h; Ch. #1 = 03h Attribute: R/W

Ch. #2 = 05h; Ch. #3 = 07h Size: 16-bit (per channel),

Ch. #5 = C6h; Ch. #6 = CAh but accessed in two 8-bit

Ch. #7 = CEh; quantities

Default Value: Undefined

Lockable: No Power Well:Core

13.2.3 DMAMEM_LP—DMA Memory Low Page Registers

(LPC I/F—D31:F0)

I/O Address: Ch. #0 = 87h; Ch. #1 = 83h

Ch. #2 = 81h; Ch. #3 = 82h

Ch. #5 = 8Bh; Ch. #6 = 89h

Ch. #7 = 8Ah; Attribute: R/W

Default Value: Undefined Size: 8-bit

Lockable: No Power Well: Core

Bit Description

15:0

Base and Current Count — R/W. This register determines the number of transfers to

be performed. The address specified points to two separate registers. On writes, the

value is store d in the Base Count register and copied to the Current Count register. On

reads, the value is returned from the Current Count register.

The actual number of transfers is one more than the number programmed in the Base

Count Register (i.e., programming a count of 4h results in 5 transfers). The count is

decrements in the Current Count register after each t ransfer. When the value in the

initialize mode, the Current Count register will be reloaded from the Base Count

For transfers to/from an 8-bit slave (channels 0–3), the count register indicates the

number of bytes to be transferred. For transfers to/from a 16-bit slave (channels 5–7),

the count regist er indicates the number of words to be transferred.

The register is accessed in 8 bit quantities. The byte is pointed to by the current byte

pointer flip/flop. Before accessing a count register, the byte pointer flip/flop should be

cleared to ensure that the low byte is accessed first.

Bit Description

7:0

DMA Low Page (ISA Address bits [23:16]) — R/W. This register works in conjunction

with the DMA controller's Current Address Register to define the complete 24-bit

address for the DMA channel. Thi s register remain s static throughou t the DMA trans fer.

Bit 16 of this register is ignored when in 16 bit I/O count by words mode as it is

replaced by the bit 15 shifted out from the current address register.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 455

LPC Interface Bridge Registers (D31:F0)

13.2.4 DMACMD—DMA Command Register (LPC I/F—D31:F0)

I/O Address: Ch. #0–3 = 08h;

Ch. #4–7 = D0h Attribute: WO

Default Value: Undefined Size: 8-bit

Lockable: No Power Well: Core

13.2.5 DMASTA—DMA Status Register (LPC I/F—D31:F0)

I/O Address: Ch. #0–3 = 08h;

Ch. #4–7 = D0h Attribute: RO

Default Value: Undefined Si ze: 8-bit

Lockable: No Power Well: Core

Bit Description

7:5 Reserved. Must be 0.

DMA Group Arbitration Priority — WO. Each channel group is individually assigned

either fixed or rotating arbitration priority. At part reset, each group is initialized in

fixed priority.

0 = F ixed priority to the channel group

1 = Rotating priority to the group.

3 Reserved. Must be 0.

DMA Channel Group Enable — WO. Both channel groups are enabled following part

reset.

0 = Enable the DMA channel group.

1 = Disable. Disabling chan nel group 4–7 also disables channel group 0–3, which is

cascaded through channel 4.

1:0 Reserved. Must be 0.

Bit Description

7:4

Channel Request Status — RO. When a valid DMA request is pending for a channel,

the corresponding bit is set to 1. When a DMA request is not pending for a particular

channel, the corresponding bit is set to 0. The source of the DREQ may be hardware or

a software request. Note that channel 4 is the cascade channel, so the request status of

channel 4 is a lo gical OR of the request status for channels 0 through 3.

4 = Channel 0

5 = Channel 1 (5)

6 = Channel 2 (6)

7 = Channel 3 (7)

3:0

Channel Terminal Count Status — RO. When a channel reaches terminal count (TC),

its status bit is set to 1. If TC has not been reached, the status bit is set to 0. Channel 4

is programmed for cascade, so the TC bit response for channel 4 is irrelevant:

0 = Channel 0

1 = Channel 1 (5)

2 = Channel 2 (6)

3 = Channel 3 (7)

LPC Interface Bridge Registers (D31 :F 0)

456 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.2.6 DMA_WRSMSK—DMA Write Single Mask Register

(LPC I/F—D31:F0)

I/O Address: Ch. #0–3 = 0Ah;

Ch. #4–7 = D4h Attribute: WO

Default Value: 0000 01xx Size: 8-bit

Lockable: No Power Well: Core

Bit Description

7:3 Reserved. Must be 0.

Channel Mask Select — WO.

0 = Enable DREQ for the selected channel. The channel is selected through bits [1:0].

Therefore, only one channel can be masked / unmasked at a time.

1 = Disable DREQ for the selected channel.

1:0

DMA Channel Select — WO. These bits select the DMA Channel Mode Register to

program.

00 = Channel 0 (4)

01 = Channel 1 (5)

10 = Channel 2 (6)

11 = Channel 3 (7)

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 457

LPC Interface Bridge Registers (D31:F0)

13.2.7 DMACH_MODE—DMA Channel Mode Register

(LPC I/F—D31:F0)

I/O Address: Ch. #0–3 = 0Bh;

Ch. #4–7 = D6h Attribute: WO

Default Value: 0000 00xx Size: 8 -bit

Lockable: No Power Well: Core

Bit Description

7:6

DMA Transfer Mode — WO. Each DMA channel can be programmed in one of four

different modes:

00 = Demand mode

01 = Single mode

10 = Reserved

11 = Cascade mode

Address Increment/Decrement Select — WO. This bit controls address incre ment/

decrement during DMA t ransfers.

0 = Address increment. (default after part reset or Master Clear)

1 = Address decrement.

Autoinitialize Enable — WO.

0 = Autoinitialize feature is disabled and DMA transfers terminate on a terminal count.

A part reset or Master Clear disables autoinitialization.

1 = DMA restores the Base Address and Count registers to the current registers

following a terminal count (TC).

3:2

DMA Transfer Type — WO. These bits represent the di rection of the DMA transfer.

When the channel is progr ammed for cascade mode , (bits[7 :6] = 11) the tr ans fer type

is irrelevant.

00 = Verify – No I/O or memory strobes generated

01 = Write – Data transferred from the I/O devices to memory

10 = Read – Data transferred from memory to the I/O device

11 = Invalid

1:0

DMA Channel Select — WO. These bits select the DMA Channel Mode Register that

will be written by bits [7:2].

00 = Channel 0 (4)

01 = Channel 1 (5)

10 = Channel 2 (6)

11 = Channel 3 (7)

LPC Interface Bridge Registers (D31 :F 0)

458 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.2.8 DMA Clear Byte Pointer Register (LPC I/F—D31:F0)

I/O Address: Ch. #0–3 = 0Ch;

Ch. #4–7 = D8h Attribute: WO

Default Value: xxxx xxxx Size: 8-bit

Lockable: No Power Well: Core

13.2.9 DMA Master Clear Register (LPC I/F—D31:F0)

I/O Address: Ch. #0–3 = 0Dh;

Ch. #4–7 = DAh Attribute: WO

Default Value: xxxx xxxx Size: 8-bit

13.2.10 DMA_CLMSK—DMA Clear Mask Register (LPC I/F—D31:F0)

I/O Address: Ch. #0–3 = 0Eh;

Ch. #4–7 = DCh Attribute: WO

Default Value: xxxx xxxx Size: 8-bit

Lockable: No Power Well: Core

Bit Description

7:0

Clear Byte Pointer — WO. No specific pattern. Command enabled with a write to the

I/O port address. Writing to this re gister i nitiali z es the byte pointer flip/ flop to a known

state. It clears the internal latch used to address the upper or lower byte of the 16-bit

Address and Word Count Registers. The latch is also cleared by part reset and by the

Master Clear command. Thi s command precedes the first access to a 16-bit DMA

controller register. The first access to a 16-bit register will then access the significant

byte, and the second access automatically accesses the most significant byte.

Bit Description

7:0 Master Clea r — WO. No specific pattern. Enabled with a write to the port. This has the

same effect as the hardware Reset. The Command, Status, Request, and Byte Pointer

flip/flop registers are cleared and the Mask Register is set.

Bit Description

7:0 Clear Mask Register — WO . No specific pattern. Command e nabled with a write to the

port.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 459

LPC Interface Bridge Registers (D31:F0)

13.2.11 DMA_WRMSK—DMA Write All Mask Register

(LPC I/F—D31:F0)

I/O Address: Ch. #0–3 = 0Fh;

Ch. #4–7 = DEh Attribute: R/W

Default Value: 0000 1111 Size: 8-bit

Lockable: No Power Well: Core

Bit Description

7:4 Reserved. Must be 0.

3:0

Channel Mask Bits — R/W. This register permits all four channels to be

simultaneously enabled/disabled instead of ena bling/disabli ng each channel

individually, as is the case with the Mask Register – Write Single Mask Bit. In addition,

this register has a read path to allow the status of the channel mask bits to be read. A

channel's mask bit is automatically set to 1 when the Current Byte/Word Count Register

reaches terminal count (unless the channel is in auto-initialization mode).

Setting the bit(s) to a 1 disables the corresponding DREQ(s). Setting the bit(s) to a 0

enables the corresponding DREQ(s). Bits [3:0] are set to 1 upon part reset or Master

Clear. When read, bits [3:0] indicate the DMA channel [3:0] ([7:4]) mask status.

Bit 0 = Channel 0 (4) 1 = Masked, 0 = Not Masked

Bit 1 = Channel 1 (5) 1 = Masked, 0 = Not Masked

Bit 2 = Channel 2 (6) 1 = Masked, 0 = Not Masked

Bit 3 = Channel 3 (7) 1 = Masked, 0 = Not Masked

NOTE: Disabling channel 4 also disables channels 0–3 due to the cascade of channel’s

0 – 3 through channel 4.

LPC Interface Bridge Registers (D31 :F 0)

460 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.3 Timer I/O Registers (LPC I/F—D31:F0)

Port Aliases Register Name Default Value Type

40h 50h Counter 0 Interval Time Status Byte Format 0XXXXXXXb RO

Counter 0 Counter Access Port Undefined R/W

41h 51h Counter 1 Interval Time Status Byte Format 0XXXXX XXb RO

Counter 1 Counter Access Port Undefined R/W

42h 52h Counter 2 Interval Time Status Byte Format 0XXXXX XXb RO

Counter 2 Counter Access Port Undefined R/W

43h 53h

Timer Control Word Undefined WO

Timer Control Word Register XXXXXXX0b WO

Counter Latch Command X0h WO

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 461

LPC Interface Bridge Registers (D31:F0)

13.3.1 TCW—Timer Control Word Register (LPC I/F—D31:F0)

I/O Address: 43h Attribute: WO

Default Value: All bits undefined Size: 8 bits

This register is programmed prior to any counter being accessed to specify counter

modes. Following part reset, the control words for each register are undefined and each

counter output is 0. Each timer must be programmed to bring it into a known state.

There are two special commands that can be issued to the counters through this

commands are chosen, several bits within this register are redefined. These register

formats are described below:

Bit Description

7:6

Counter Select — WO. The Counter Selection bits sel ect the counter the control word

acts upon as shown below. The Read Back Command is selected when bits[7:6] are

both 1.

00 = Counter 0 select

01 = Counter 1 select

10 = Counter 2 select

11 = Read Back Command

5:4

Read/Write Select — WO. These bits are the read/write control bits. The actual

counter programming is done through the counter port (40h for counter 0, 41h for

counter 1, and 42h for counter 2).

00 = Counter Latch Co mmand

01 = Read/Write Least Significant Byte (LSB)

10 = Read/Write Most Significant Byte (MSB)

11 = Read/Write LSB then MSB

3:1

Counter Mode Selection — WO. These bits select one of six possible modes of

operation for the selected counter.

0Binary/BCD Countdown Select — WO.

0 = Binary countdown is used. The largest possible binary count is 216

1 = Binary coded decimal (BCD) count is used. The largest possible BCD count is 104

Bit Value Mode

000b Mode 0 Out signal on end of count (=0)

001b Mode 1 Hardware retriggerable one-shot

x10b Mode 2 Rate generator (divide by n counter)

x11b M ode 3 Square wave output

100b Mode 4 Software triggered strobe

101b Mode 5 Hardware triggered strobe

LPC Interface Bridge Registers (D31 :F 0)

462 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.3.2 RDBK_CMD—Read Back Command (LPC I/F—D31:F0)

The R ead Back Comm and is used to determine the c ount value, programmed mode,

and current states of the OUT pin and Null count flag of the selected counter or

counters. Status and/or count may be latched in any or all of the counters by selecting

the counter during the register write. The count and status remain latched until read,

and further latch commands are ignored until the count is read. Both count and status

of the selected counters may be latched simultaneously by setting both bit 5 and bit 4

to 0. If both are latched, the first read operation from that counter returns the latched

status. The next one or two reads, depending on whether the counter is programmed

for one or two byte counts, returns the latched count. Subsequent reads return an

unlatched count.

LTCH_CMD—Counter Latch Command (LPC I/F—D3 1:F0)

The Counter Latch Command latches the current cou nt v alue. This command is used to

insure that the count read from the counter is accurate. The count value is then read

from each counter's count register through the Counter Ports Access Ports Register

(40h for counter 0, 41h for counter 1, and 42h for counter 2). The count must be read

according to the programmed format, i.e., if the counter is programmed for two byte

counts, two bytes must be read. The two bytes do not have to be read one right after

the other (read, write, or programming operations for other counters may be inserted

between the reads). If a counter is latched once and then latched again before the

count is read, the second Counter Latch Command is ignored.

Bit Description

7:6 Read Back Command. Must be 11 to select the Read Back Command

5Latch Count of Selected Counters.

0 = Current count value of the selected counters will be latched

1 = Current count will not be latched

4Latch Status of Selected Counters.

0 = Status of the selected counters will be latched

1 = Status will not be latched

3Counter 2 Select.

1 = Counter 2 count and/or status will be latched

2Counter 1 Select.

1 = Counter 1 count and/or status will be latched

1Counter 0 Select.

1 = Counter 0 count and/or status will be latched.

0 Reserved. Must be 0.

Bit Description

7:6

Counter Selection. These bits select the counte r for latching. If “11” is written, then

the write is interpreted as a read back command.

00 = Counter 0

01 = Counter 1

10 = Counter 2

5:4 Counter Latch Command.

00 = Selects the Counter Latch Command.

3:0 Reserved. Must be 0.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 463

LPC Interface Bridge Registers (D31:F0)

13.3.3 SBYTE_FMT—Interval Timer Status Byte Format Register

(LPC I/F—D31:F0)

I/O Address: Counter 0 = 40h,

Counter 1 = 41h, Attribute: RO

Counter 2 = 42h Size: 8 bits per counter

Default Value: Bits[6:0] undefined, Bit 7=0

Each counter's status byte can be read following a Re ad Back Command. If latch status

is chosen (bit 4=0, Read Back Command) as a read back option for a given counter, the

next read from the counter's Counter Access Ports Register (40h for counter 0, 41h for

counter 1, and 42h for counter 2) returns the status byte. The status byte returns the

following:

Bit Description

7Counter OUT Pin State — RO.

0 = OUT pin of the counter is also a 0

1 = OUT pin of the counter is also a 1

Count Register Status — RO. This bit indicates when the last count written to the

Count Register (CR) has been loaded into the counting element (CE). The exact time

this happens depends on the counter mode, but unti l the count is loaded into the

counting elemen t (CE), the count value will be incorrect.

0 = Count has been transferred from CR to CE and is available for reading.

1 = Null Count. Count has not been transferred from CR to CE and is not yet available

for reading.

5:4

Read/Write Selection Status — RO. These reflect the read/write selection made

through bits[5:4] of the control register. The binary codes returned during the status

read match the co des used to program the counter read/write selection.

00 = Counter Latch Co mmand

01 = Read/Write Least Significant Byte (LSB)

10 = Read/Write Most Significant Byte (MSB)

11 = Read/Write LSB then MSB

3:1

Mode Selection Status — RO. These bits return the counter mode programming. The

binary code returned matches the code used to program the counter mode, as listed

under the bit function above.

000 = Mode 0 — Out signal on end of count (=0)

001 = Mode 1 — Hardware retriggerable one-shot

x10 = Mode 2 — Rate generator (divide by n counter)

x11 = Mode 3 — Square wave output

100 = Mode 4 — Software triggered strobe

101 = Mode 5 — Hardware triggered strobe

0Countdown Type Status — RO. This bit reflects the current countdown type.

0 = Binary countdown

1 = Binary Coded Decimal (BCD) countdown.

LPC Interface Bridge Registers (D31 :F 0)

464 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.3.4 Counter Access Ports Register (LPC I/F—D31:F0)

I/O Address: Counter 0 – 40h,

Counter 1 – 41h, Attribute: R/W

Counter 2 – 42h

Default Value: All bits undefined Size: 8 bit

Bit Description

7:0

Counter Port — R/W. Each counter port address is used to program the 16-bit Count

defined with the Interval Counter Control Register at port 43h. The counter port is also

used to read the current count from the Count Register, and return the status of the

counter programming following a Read Back Command.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 465

LPC Interface Bridge Registers (D31:F0)

13.4 8259 Interrupt Controller (PIC) Registers

(LPC I/F—D31:F0)

13.4.1 Interrupt Controller I/O MAP (LPC I/F—D31:F0)

The interrupt controller registers are located at 20h and 21h for the master controller

(IRQ 0–7), and at A0h and A1h for the slave controller (IRQ 8–13). These registers

have multiple functions, depending upon the data written to them. Table 13-3 shows

the different register possibilities for each address.

Note: R efer to note addressing active-low interrupt sources in 8259 Interrupt Controllers

section (Chapter 5.8).

Table 13-3. PIC Registers (LPC I/F—D31:F0)

Port Aliases Register Name Default

Value Type

20h 24h, 28h,

2Ch, 30h,

34h, 38h, 3Ch

Master PIC ICW1 Init. Cmd Word 1 Undefined WO

Master PIC OCW2 Op Ctrl Word 2 001XXXXXb WO

Master PIC OCW3 Op Ctrl Word 3 X01XXX10b WO

21h

25h, 29h,

2Dh, 31h,

35h, 39h,

3Dh

Master PIC ICW2 Init. Cmd Word 2 Undefined WO

Master PIC ICW3 Init. Cmd Word 3 Undefined WO

Master PIC ICW4 Init. Cmd Word 4 01h WO

Master PIC OCW1 Op Ctrl Word 1 00h R/W

A0h

A4h, A8h,

ACh, B0h,

B4h, B8h,

BCh

Slave PIC ICW1 Init. Cmd Wo rd 1 Undefined WO

Slave PIC OCW2 Op Ctrl Word 2 001XXXXXb WO

Slave PIC OCW3 Op Ctrl Word 3 X01XXX10b WO

A1h

A5h, A9h,

ADh, B1h,

B5h, B9h,

BDh

Slave PIC ICW2 Init. Cmd Wo rd 2 Undefined WO

Slave PIC ICW3 Init. Cmd Wo rd 3 Undefined WO

Slave PIC ICW4 Init. Cmd Word 4 01h WO

Slave PIC OCW1 Op Ctrl Word 1 00h R/W

4D0h – Master PIC Edge/Level Triggered 00h R/W

4D1h – Slave PIC Edge/Level Triggered 00h R/W

LPC Interface Bridge Registers (D31 :F 0)

466 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.4.2 ICW1—Initialization Command Word 1 Register

(LPC I/F—D31:F0)

Offset Address: Master Controller – 20h Attribute: WO

Slave Controller

– A0h Size: 8 bit /controller

Default Value: All bits undefined

A write to Initialization Command Word 1 starts the interrupt controller initialization

sequence, during which the following occurs:

1. The Interrupt Mask register is cleared.

2. IRQ7 input is assigned priority 7.

3. The slave mode address is set to 7.

4. Special mask mode is cleared and Status Read is set to IRR.

Once this write occurs, the controller expects writes to ICW2, ICW3, and ICW4 to

complete the initialization sequence.

Bit Description

7:5 ICW/OCW Se lect — WO. These bits are MCS-85 specific, and not needed.

000 = Should be programmed to “000”

4ICW/OCW Sele ct — W O.

1 = This bit must be a 1 to select ICW1 and enable the ICW2, ICW3, and ICW4

sequence.

3Edge/Level Bank Select (LTIM) — WO. Disabled. Replaced by the edge/level

triggered control registers (ELCR, D31:F0: 4D0h, D31:F0:4D1h).

2ADI — WO.

0 = Ignored for the ICH9. Should be programmed to 0.

1Single or Cascade (SNGL) — WO.

0 = Must be programmed to a 0 to indicate two controllers operating in cascade mode.

0ICW4 Write Re quired (IC4) — WO.

1 = This bit must be programmed to a 1 to indicate that ICW4 needs to be

programmed.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 467

LPC Interface Bridge Registers (D31:F0)

13.4.3 ICW2—Initialization Command Word 2 Register

(LPC I/F—D31:F0)

Offset Address: Master Controller – 21h Attribute: WO

Slave Controller

– A1h Size: 8 bit /controller

Default Value: All bits undefined

ICW2 is used to initialize the interrupt controller with the five most significant bits of

the interrupt vector address. The value programmed for bits[7:3] is used by the

processor to define the base address in the interrupt vector table for the interrupt

routines associated with each IRQ on the controller. Typical ISA ICW2 values are 08h

for the master controller and 70h for the slave controller.

Bit Description

7:3 Interrupt Vector Base Address — WO. Bi ts [7:3] define the base address in the

interrupt vector table for the interrupt routines associated with each interrupt request

level input.

2:0

Interrupt Request Level — WO. When writing ICW2, these bits should all be 0.

During an interrupt acknowledge cycle, these bits are programmed by the interrupt

controller with the interrupt to be serviced. This is combined with bits [7:3] to form the

interrupt vector driven onto the data bus during the second INTA# cycle. The code is a

three bit binary code:

Code Master Interrupt Slave Interrupt

000b IRQ0 IRQ8

001b IRQ1 IRQ9

010b IRQ2 IRQ10

011b IRQ3 IRQ11

100b IRQ4 IRQ12

101b IRQ5 IRQ13

110b IRQ6 IRQ14

111b IRQ7 IRQ15

LPC Interface Bridge Registers (D31 :F 0)

468 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.4.4 ICW3—Master Controller Initialization Command

Word 3 Register (LPC I/F—D31:F0)

Offset Address: 21h Attribute: WO

Default Value: All bits undefined Size: 8 bits

13.4.5 ICW3—Slave Controller Initializ ation Command

Word 3 Register (LPC I/F—D31:F0)

Offset Address: A1h Attribute: WO

Default Value: All bits undefined Size: 8 bits

Bit Description

7:3 0 = These bits must be programmed to 0.

Cascaded Interrupt Controller IRQ Connectio n — WO. This bit indicates that the

slave controller is cascaded on IRQ2. When IRQ8#–IRQ15 is asserted, it goes through

the slave controller’s priority resolver. The slave controller’s INTR output onto IRQ2.

IRQ2 then goes through the master controller’s priority solver. If it wins, the INTR

signal is asserted to the processor, and the returning interrupt acknowledge returns the

interrupt vector for the slave controller.

1 = This bit must always be programmed to a 1.

1:0 0 = These bits must be programmed to 0.

Bit Description

7:3 0 = These bits must be programmed to 0.

2:0

Slave Identific a tion Code — WO. These bits are compared against the slave

identification code broadcast by the master controller from the trailing edge of the first

internal INTA# pulse to the tr ailing e dge of the secon d internal INTA# pulse. These bi ts

must be programmed to 02h to match the code broadcast by the master controller.

When 02h is broadcast by the master controller during the INTA# sequence, the slave

controller assumes responsibility for broadcasting the interrupt vector.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 469

LPC Interface Bridge Registers (D31:F0)

13.4.6 ICW4—Initialization Command Word 4 Register

(LPC I/F—D31:F0)

Offset Address: Master Controller – 021h Attribute: WO

Slave Controller

– 0A1h Size: 8 bits

Default Value: 01h

13.4.7 OCW1—Operational Control Word 1 (Interrupt Mask)

Offset Address: Master Controller – 021h Attribute: R/W

Slave Controller

– 0A1h Size: 8 bits

Default Value: 00h

Bit Description

7:5 0 = These bits must be programmed to 0.

4Special Fully Nested Mode (SFNM) — WO.

0 = Should normally be disabled by writing a 0 to this bit.

1 = Special fully nested mode is programmed.

3Buffered Mode (BUF) — WO.

0 = Must be programmed to 0 for the ICH9. This is non-buffered mode.

2Master/Slave in Buffered Mode — WO. Not used.

0 = Should always be programmed to 0.

1Automatic End of Interrupt (AEOI) — WO.

0 = This bit should normally be programmed to 0. This is the normal end of interrupt.

1 = Automatic End of Interrupt (AEOI) mode is programmed.

0Microprocessor Mode — WO.

1 = Must be programmed to 1 to indicate that the controller is operating in an Intel

Architecture-bas ed system.

Bit Description

7:0

Interrupt Request Mask — R/W. When a 1 is written to any bit in this register, the

corresponding IRQ line is masked. When a 0 is written to any bit in this register, the

corresponding IRQ mask bit is cleared, and interrupt requests will again be accepted by

the controller. Masking IRQ2 on the m a ster controller will also mask the interrupt

requests from the slave controller.

LPC Interface Bridge Registers (D31 :F 0)

470 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.4.8 OCW2—Operational Control Word 2 Register

(LPC I/F—D31:F0)

Offset Address: Master Controller – 020h Attribute: WO

Slave Controller

– 0A0h Size: 8 bits

Default Value: Bit[4:0]=undefined, Bit[7:5]=001

Following a part reset or ICW initialization, the controller enters the fully nested mode

of operation. Non-specific EOI without rotation is the default. Both rotation mode and

specific EOI mode are disabled following initialization.

Bit Description

7:5

Rotate and EOI Codes (R, SL, EOI) — WO. These three bits control the Rotate and

End of Interrupt modes and combinations of the two.

000 = Rotate in Auto EOI Mode (Cle ar)

001 = Non-specific EOI command

010 = No Operation

011 = *Specific EOI Command

100 = Rotate in Auto EOI Mode (Set)

101 = Rotate on Non-Specific EOI Comman d

110 = *Set Priority Command

111 = *Rotate on Specific EOI Command

*L0 – L2 Are Used

4:3 OCW2 Select — WO. When selecting OCW2, bits 4:3 = “00”

2:0

Interrupt Level Select (L2, L1, L0) — WO. L2, L1, and L0 determine the interrupt

level acted u pon when the SL bit is active. A simple binary co de, outlined below , select s

the channel for the com mand to act upon. When the SL bit is inactiv e, these bits do not

have a defined function; programming L2, L1 and L0 to 0 is sufficient in this case.

Code Interrupt Level Code Interrupt Level

000b IRQ0/8 000b IRQ4/12

001b IRQ1/9 001b IRQ5/13

010b IRQ2/10 010b IRQ6/14

011b IRQ3/11 011b IRQ7/15

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 471

LPC Interface Bridge Registers (D31:F0)

13.4.9 OCW3—Operational Control Word 3 Register

(LPC I/F—D31:F0)

Offset Address: Master Controller – 020h Attribute: WO

Slave Controller

– 0A0h Size: 8 bits

Default Value: Bit[6,0]=0, Bit[7,4:2]=undefined,

Bit[5,1]=1

Bit Description

7 Reserved. Must be 0.

Special Mask Mode (SMM) — WO.

1 = The Special Mask Mode can be u sed by an interrupt service routine to dynamica l ly

alter the system priority structure while the routine is executing, through selective

enabling/disabling of the other channel's mask bits. Bit 5, the ESMM bit, must be

set for this bit to have any meaning.

5Enable Special Mask Mo de (E SMM) — WO.

0 = D isable. The SMM bit becomes a “don't ca re”.

1 = Enable the SMM bit to set or reset the S p ecial Mask Mode.

4:3 OCW3 Select — WO. When selecting OCW3, bits 4:3 = 01

Poll Mode Command — WO.

0 = D isable. Poll Command is not issued.

1 = Enable. The next I/O read to the interrupt controller is treated as an interrupt

acknowledge cycle. An encoded byte is driven onto the data bus, representing the

highest priority level requesting service.

1:0

affect the register read selection. When bit 1=1, bit 0 selects the register status

returned following an OCW3 read. If bit 0=0, the IRR will be read. If bit 0=1, the ISR

will be read. Following ICW initialization, the default OCW3 port address read will be

“read IRR”. To retain the current selection (r ead ISR or read IRR), always write a 0 to

bit 1 when programming this register. The selected register can be read repeatedly

without reprogramming OCW3. To select a new status register, OCW3 must be

reprogrammed prior to attempting the read.

00 = No Action

01 = No Action

10 = Read IRQ Register

11 = Read IS Register

LPC Interface Bridge Registers (D31 :F 0)

472 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.4.10 ELCR1—Master Controller Edge/Level Triggered Register

(LPC I/F—D31:F0)

Offset Address: 4D0h Attribute: R/W

Default Value: 00h Size: 8 bits

In edge mode, (bit[x] = 0), the interrupt is recognized by a low to high transition. In

level mode (bit[x] = 1), the interrupt is recognized by a high level. The cascade

channel, IRQ2, the heart beat timer (IRQ0), and the keyboard controller (IRQ1),

cannot be put into level mode.

Bit Description

7IRQ7 ECL — R/W.

0 = Edge.

1 = Level.

6IRQ6 ECL — R/W.

0 = Edge.

1 = Level.

5IRQ5 ECL — R/W.

0 = Edge.

1 = Level.

4IRQ4 ECL — R/W.

0 = Edge.

1 = Level.

3IRQ3 ECL — R/W.

0 = Edge.

1 = Level.

2:0 Reserved. Must be 0.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 473

LPC Interface Bridge Registers (D31:F0)

13.4.11 ELCR2—Slave Controller Edge/Level Triggered Register

(LPC I/F—D31:F0)

Offset Address: 4D1h Attribute: R/W

Default Value: 00h Size: 8 bits

In edge mode, (bit[x] = 0), the interrupt is recognized by a low to high transition. In

level mode (bit[x] = 1), the interrupt is recognized by a high level. The real time clock,

IRQ8#, and the floating point error interrupt, IRQ13, cannot be programmed for level

mode.

Bit Description

7IRQ15 ECL — R/W.

0 = Edge

1 = Level

6IRQ14 ECL — R/W.

0 = Edge

1 = Level

5 Reserved. Must be 0.

4IRQ12 ECL — R/W.

0 = Edge

1 = Level

3IRQ11 ECL — R/W.

0 = Edge

1 = Level

2IRQ10 ECL — R/W.

0 = Edge

1 = Level

1IRQ9 ECL — R/W.

0 = Edge

1 = Level

0 Reserved. Must be 0.

LPC Interface Bridge Registers (D31 :F 0)

474 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.5 Advanced Programmable Interrupt Controller

(APIC)(D31:F0)

13.5.1 APIC Register Map (LPC I/F—D31:F0)

The APIC is accessed via an indirect addressing scheme. Two registers are visible by

software for manipulation of most of the APIC registers. These registers are mapped

into memory space. The address bits 15:12 of the address range are programmable

through bit 7:4 of OIC register (Chipset Configuration Register, offset 31FFh.) The

registers are shown in Table 13-4.

Table 13-5 lists the registers which can be accessed within the APIC via the Index

For example, software should never access byte 2 from the Data register before

accessing bytes 0 and 1. The hardware will not attempt to recover from a bad

programming model in this case.

13.5.2 IND—Index Register (LPC I/F—D31:F0)

Memory Address FEC0_0000h Attribute: R/W

Default Value: 00h Size: 8 bits

The Index Register will select which APIC indirect register to be manipulated by

software. The selector values for the indirect registers are listed in Table 13-5. Software

will program this register to select the desired APIC internal register

Table 13-4. APIC Direct Registers (LPC I/F—D31:F0)

Address Mnemonic Register Name Size Type

FEC0_0000h IND Index 8 bits R/W

FEC0_0010h DAT Data 32 bits R/W

FECO_0040h EOIR EOI 32 bits WO

Table 13-5. APIC Indirect Registers (LPC I/F—D31:F0)

Index Mnemonic Register Name Size Type

00 ID Identification 32 bits R/W

01 VER Version 32 bits RO

02–0F — Reserved — RO

10–11 REDIR_TBL0 Redirection Table 0 64 bits R/W, RO

12–13 REDIR_TBL1 Redirection Table 1 64 bits R/W, RO

... ... ... ... ...

3E–3F REDIR_TBL23 Redirection Table 23 64 bits R/W, RO

40–FF — Reserved — RO

Bit Description

7:0 APIC Index — R/W. This is an 8-bit pointer into the I/O APIC register table.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 475

LPC Interface Bridge Registers (D31:F0)

13.5.3 DAT—Data Register (LPC I/F—D31:F0)

Memory Address FEC0_0010h Attribute: R/W

Default Value: 00000000h S ize: 32 bits

This is a 32-bit register specifying the data to be read or written to the register pointed

to by the Index register. This register can only be accessed in dword quantities.

13.5.4 EOIR—EOI Register (LPC I/F—D31:F0)

Memory Address FEC0h_0040h Attribute: WO

Default Value: N/A Size: 32 bits

The EOI register is present to provide a mechanism to maintain the level triggered

semantics for level-triggered interrupts issued on the parallel bus.

When a write is issued to this register, the I/O APIC will check the lower 8 bits written

to this register, and compare it with the vector field for each entry in the I/O

Redirection Table. When a match is found, the Remote_IRR bit (Index Offset 10h, bit

14) for that I/O Redirection Entry will be cleared.

Note: If multiple I/O Redirection entries, for any reason, assign the same vector for more

than one interrupt input, each of those entries will have the Remote_IRR bit reset to 0.

The interrupt which was prematurely reset will not be lost because if its input remained

active when the Remote_IRR bit is cleared, the interrupt will be reissued and serviced

at a later time. Note: Only bits 7:0 are actually used. Bits 31:8 are ignored by the

ICH9.

Note: To provide for future expansion, the processor should always write a value of 0 to Bits

31:8.

Bit Description

7:0 APIC Data — R/W. This is a 32-bit register for the data to be read or written to the

APIC indirect register (Figure 13-5) pointed to by the Index register (Memory Address

FEC0_0000h).

Bit Description

31:8 R eserved. To provide for future expansion, the processor should alwa ys write a value of

0 to Bits 31:8.

7:0

Redirection Entry Clear — WO. When a write is issued to this register, the I/O APIC

will check this field, and compare it with the vector field for each entry in the I/O

Redirection Table. When a match is found, the Remote_IRR bit for that I/O Redirection

Entry will be cleared.

LPC Interface Bridge Registers (D31 :F 0)

476 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.5.5 ID—Identification Register (LPC I/F—D31:F0)

Index Offset: 00h Attribute: R/W

Default Value: 00000000h Size: 32 bits

The APIC ID serves as a physical name of the APIC. The APIC bus arbitration ID for the

APIC is derived from its I/O APIC ID. This register is reset to 0 on power-up reset.

13.5.6 VER—Version Register (LPC I/F—D31:F0)

Index Offset: 01h Attribute: RO, RWO

Default Value: 00170020h Size: 32 bits

Each I/O APIC contains a hardwired Version Register that identifies different

implementation of APIC and their ve rsions. The maximum redirection entry information

also is in this register, to let software know how many interrupt are supported by this

APIC.

Bit Description

31:28 Reserved

27:24 APIC ID — R/W. Software must program this value before using the APIC.

23:16 Reserved

15 Scratchpad Bit.

14:0 Reserved

Bit Description

31:24 Reserved

23:16

Maximum Redirection Entries (MRE) — RWO . This is the entry number (0 being the

lowest entry) of the highest entry in the redirection table. It is equal to the number of

interrupt input pins minus one and is in the range 0 through 239. In the ICH9 this field

is hardwired to 17h to indicate 24 interrupts.

BIOS must write to this field after PLTRST# to lockdown the value. this allows BIOS to

utilize some of the entries for its own purpose and thus advertising fewer IOxAPIC

Redirection Entries to the OS.

15 Pin Assertion Register Supported (PRQ) — RO. Indicate that the IOxAPIC does not

implement the Pin Assertion Register.

14:8 Reserved

7:0 Version (VS) — RO. This is a version number that identifies the implementation

version.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 477

LPC Interface Bridge Registers (D31:F0)

13.5.7 REDIR_TBL—Redirection Table (LPC I/F—D31:F0)

Index Offset: 10h–11h (vector 0) through Attribute:R/W, RO

3E–3Fh (vector 23)

Default Value: Bit 16 = 1. All other bits undefined Size: 64 bits each, (accessed

as two 32 bit quantities)

The Redirection Table has a dedicated entry for each interrupt input pin. The

information in the Redirection Table is used to translate the interrupt manifestation on

the corresponding interrupt pin into an APIC message.

The APIC will respond to an edge triggered interrupt as long as the interrupt is held

until after the acknowledge cycle has begun. Once the interrupt is detected, a delivery

status bit internally to the I/O APIC is set. The state machine will step ahead and wait

for an acknowledgment from the APIC unit that the interrupt message was sent. Only

then will the I/O APIC be able to recognize a new edge on that interrupt pin. That new

edge will only result in a new invocation of the handler if its acceptance by the

destination APIC causes the Interrupt Request Register bit to go from 0 to 1.

(In other words, if the interrupt was not already pending at the destination.)

Bit Description

63:56

Destination — R/W. If bit 11 of this entry is 0 (Physical), then bits 59:56 specifies an

APIC ID. In this case, bits 63:59 should be programmed by software to 0.

If bit 11 of this entry is 1 (Logical), then bits 63:56 specify the logical destination

address of a set of processors.

55:48 Extended Destination ID (EDID) — RO. These bits are sent to a local APIC only

when in Processor System Bus mode. They become bits 11:4 of the address.

47:17 Reserved

Mask — R/W.

0 = Not masked: An edge or level on this interrupt pin results in the delivery of the

interrupt to the destination.

1 = Masked: Interrupts are not delivered nor held pending. Setting this bit after the

interrupt is accepted by a local APIC has no effect on that interrupt. This behavior

is identical to the device withdrawing the interrupt before it is posted to the

processor. It is software's responsibility to deal with the case where the mask bit is

set after the interrupt message has been accepted by a local APIC unit but before

the interrupt is dispensed to the processor.

Trigger Mode — R/W. This field indicates the type of signal on the interrupt pin that

triggers an interrupt.

0 = Edge triggered.

1 = Level triggered.

Remote IRR — R/W. This bit is used for level triggered interrupts; its meaning is

undefined for edge triggered interrupts.

0 = Reset when an EOI message is received from a local APIC.

1 = Set when Local APIC/s accept the level interrupt sent by the I/O APIC.

Interrupt Input Pin Polarity — R/W. This bit specifie s the polarity of each interrup t

signal connected to the interrupt pins.

0 = Active high.

1 = Active low.

Delivery Status — RO. This field contains the current status of the delivery of this

interrupt. Writes to this bit have no effect.

0 = Idle. No activity for this interrupt.

1 = Pending. Interrupt has been injected, but delivery is not complete.

LPC Interface Bridge Registers (D31 :F 0)

478 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE: Delivery Mode encoding:

000 = Fixed. Deliv er the signal on the INTR signal of all processor cores list ed in the destination.

Trigger Mode can be edge or level.

001 = Lowest Priority. Deliver the signal on the INTR signal of the processor core that is

executing at the lowest priority among all the processors listed in the specified

destination. Trigger Mode can be edge or level.

010 = SMI (System Management Interrupt). Requires the interrupt to be programmed as edge

triggered. The vector information is ignored but must be programmed to all 0s for future

compatibility: not supported

011 = Reserved

100 = NMI. Deliver the signal on the NMI signal of all processor cores listed in the destination.

Vector information is ignored. NMI is treated as an edge triggered interrupt even if it is

programmed as level triggered. For proper operation this redirection table entry must be

programmed to edge triggered. The NMI delivery mode does not set the RIRR bit. If the

redirection table is incorrectly set to level, the loop count will continue countin g through

the redirection table addresses. Once the count for the NMI pin is reached again, the

interrupt will be sent again: not supported

101 = INIT. Deliver the signal to all processor cores listed in the destination by asserting the

INIT signal. All addressed loc al AP ICs wi ll assume their INIT state. INIT is always treated

as an edge triggered interrupt even if programmed as level triggered. For proper

operation this redirection table entry must be programmed to edge triggered. The INIT

delivery mode does not set the RIRR bit. If the redirection table is incorrectly set to level,

the loop count will continue counting through the redirection table addresses. Once the

count for the INIT pin is reached again, the interrupt will be sent again: not supported

110 = Reserved

111 = ExtINT. Deliver the signal to the INTR signal of all processor cores listed in the destination

as an interrupt that originated in an externally connected 8259A compatible interrupt

controller. The INTA cycle that corresponds to this ExtINT delivery will be routed to the

external controller that is expected to supply the vector. Requires the interrupt to be

programmed as edge triggered.

Destination Mode — R/W. This field determines the interpretation of the Destination

field.

0 = Physical. Destination APIC ID is identified by bits 59:56.

1 = Logical. Destinations are identified by matching bit 63:56 with the Logical

Destination in the Destination Format Register and Logical Destination Register in

each Local APIC.

10:8

Delivery Mode — R/W. This field specifies how the APICs listed in the destination field

should act upon reception of this signal. Certain Delivery Mode s will only operate as

intended when used in c on j unction with a specific trigger mode. These encodings are

listed in the no te below:

7:0 Vector — R/W. This field contains the interrupt vector for this interrupt. Values range

between 10h and FEh.

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 479

LPC Interface Bridge Registers (D31:F0)

13.6 Real Time Clock Registers

13.6.1 I/O Register Address Map

The RTC internal registers and RAM are organized as two banks of 128 bytes each,

called the standard and extended banks. The first 14 bytes of the standard bank

contain the R TC time and date information along with four registers, A –D, that are used

for configuration of the RTC. The extended bank contains a full 128 bytes of battery

backed SRAM, and will be accessible even when the RTC module is disabled (via the

RTC configuration register). Registers A–D do not physically exist in the RAM.

All data movement between the host processor and the real-time clock is done through

registers mapped to the standard I/O space. Th e register map appears in Table 13-6.

NOTES:

1. I/O locations 70h and 71h are the standard legacy location for the real-time clock.

The map for this bank is shown in Table 13-7. Locations 72h and 73h are for

accessing the extended RAM. The extended RAM bank is also accessed using an

indexed scheme. I/O address 72h is used as the address pointer and I/O address

73h is used as the data register. Index addresses above 127h are not valid. If the

extended RAM is not needed, it may be disabled.

2. Software must preserve the value of bit 7 at I/O addresses 70h and 74h. When

writing to this address, software must first read the v alue, and then write the same

value for bit 7 during the sequential address write. Note that port 70h is not

directly readable. The only way to read this register is through Alt Access mode.

Although R TC Index bits 6:0 are readable fr om port 74h, bit 7 will alwa ys return 0.

If the NMI# enable is not changed during normal operation, software can

alternatively read this bit once and then retain the value for all subsequent writes

to port 70h.

Table 13-6. RTC I/O Registers

I/O

Locations If U128E bit = 0 Function

70h and 74h Also alias to 72h and 76h Real-Time Clock (Standard RAM) Index Register

71h and 75h Also alias to 73h and 77h Real-Time Clock (Standard RAM) Target Register

72h and 76h Extended RAM Index Register (if enabled)

73h and 77h Extended RAM Target Register (if enabled)

LPC Interface Bridge Registers (D31 :F 0)

480 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.6.2 Indexed Regist ers

The RTC contains two sets of indexed registers that are accessed using the two

separate Index and Target registers (70/71h or 72/73h), as shown in Table 13-7.

Table 13-7. RTC (Standard) RAM Bank

Index Name

00h Seconds

01h Seconds Alarm

02h Minutes

03h Minutes Alarm

04h Hours

05h Hours Alarm

06h Day of Week

07h Day of Month

08h Month

09h Year

0Ah Register A

0Bh Register B

0Ch Register C

0Dh Register D

0Eh–7Fh 114 Bytes of User RAM

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 481

LPC Interface Bridge Registers (D31:F0)

13.6.2.1 RTC_REGA—Register A

RTC Index: 0A Attribute: R/W

Default Value: Undefined Size: 8-bit

Lockable: No Power Well: RTC

This register is used for general configuration of the RTC functions. None of the bits

are affected by RSMRST# or any other ICH9 reset signal.

Bit Description

Update In Progress (UIP) — R/W. This bit may be monitored as a status flag.

0 = The update cycle will not start for at least 488 µs. The time, calendar, and alarm

information in RAM is always available when the UIP bit is 0.

1 = The update is soon to occur or is in progress.

6:4

Division Chain Sele ct (DV[2:0]) — R/W. These three bits control the divider chain

for the oscillator, and are not affected by RSMRST# or any other reset signal.

DV2 corresponds to bit 6.

010 = Normal Operation

11X = Divider Reset

101 = Bypass 15 stages (test mode only)

100 = Bypass 10 stages (test mode only)

011 = Bypass 5 stages (test mode only)

001 = Invalid

000 = Invalid

3:0

Rate Select (RS[3:0]) — R/W. Selects one of 13 taps of the 15 stage divider chain.

The selected tap can generate a periodic interrupt if the PIE bit is set in Register B.

Otherwise this tap will set the PF flag of Register C. If the periodic interrupt is not to be

used, these bits should all be set to 0. RS3 corresponds to bit 3.

0000 = Interrupt never toggles

0001 = 3.90625 ms

0010 = 7.8125 ms

0011 = 122.070 µs

0100 = 244.141 µs

0101 = 488.281 µs

0110 = 976.5625 µs

0111 = 1.953125 ms

1000 = 3.90625 ms

1001 = 7.8125 ms

1010 = 15.625 ms

1011 = 31.25 ms

1100 = 62.5 ms

1101 = 125 ms

1110 = 250 ms

1111= 500 ms

LPC Interface Bridge Registers (D31 :F 0)

482 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.6.2.2 RTC_REGB—Register B (General Configuration)

RTC Index: 0Bh Attribute: R/W

Default Value: U0U00UUU (U: Undefined) Size: 8-bit

Lockable: No Power Well: RTC

Bit Description

Update Cycle Inhibit (SET) — R/W. Enables/Inhibits the update cycles. This bit is not

affected by RSMRST# nor any other reset signal.

0 = Update cycle occurs normally once each second.

1 = A current update cycle will abort and subsequent update cycles will not occur until

SET is returned to 0. When set is one, the BIOS may initialize time and calendar

bytes safely.

NOTE: This bit should be set then cleared early in BIOS POST after each powerup

directly after coin-cell battery insertion.

Periodic Interrupt Enable (P IE) — R/W. This bit is cleared by RSMRST#, but not on

any other reset.

0 = Disable.

1 = Enable. Allows an inte rrupt to occur with a time base set with the RS bits of register

Alarm Interrupt Enable (AIE) — R/W . This bit is cleared by R TCRST#, but not on any

other reset.

0 = Disable.

1 = Enable. Allows an interrupt to occur when the AF is set by an alarm match from the

update cycle. An alarm can occur once a se cond, one an hour, once a day, or one a

month.

Update-Ended Interrupt Enable (UIE) — R/W. This bit is cleared by RSMRST#, but

not on any other reset.

0 = Disable.

1 = Enable. Allows an interrupt to occur when the update cycle ends.

3Square Wave Enable (SQWE) — R/W. This bit serves no function in the ICH9. It is

left in this register bank to provide compatibility with the Motorola 146818B. The ICH9

has no SQW pin. This bit is cleared by RSMRST#, but not on any other reset.

Data Mode (DM) — R/W. This bit specifies either binary or BCD data representation.

This bit is not affected by RSMRST# nor any other reset signal.

0 = BCD

1 = Binary

Hour Format (HOURFORM) — R/W. This bit in dicates the hour byte format. This bit is

not affected by RSMRST# nor any other reset signal.

0 = Twelve-hour mode. In twelve-hour mode, the seventh bit represents AM as 0 and

PM as one.

1 = Twenty-four hour mode.

Daylight Savi n g s Legacy Softwa re Su pport (DSLSWS ) — R/W. Daylight savings

functionality is no longer supported. This bit is used to maintain legacy software

support and has no associated functionality. If BUC.DSO bit is set, the DSLSWS bit

continues to be R/W.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 483

LPC Interface Bridge Registers (D31:F0)

13.6.2.3 RTC_REGC—Register C (Flag Register)

RTC Index: 0Ch Attribute: RO

Default Value: 00U00000 (U: Undefined) Size : 8-bit

Lockable: No Power Well: RTC

Writes to Register C have no effect.

13.6.2.4 RTC_REGD—Register D (Flag Register)

RTC Index: 0Dh Attribute: R/W

Default Value: 10UUUUUU (U: Undefined) Size: 8-bit

Lockable: No Power Well: RTC

Bit Description

7Interrupt Request Flag (IRQF) — RO. IRQF = (PF * PIE) + (AF * AIE) + (UF *UFE).

This bit also cau ses the R T C Interrupt to be asserted. This bit is cleared upon RSMRST#

or a read of Register C.

Periodic Interrupt Flag (PF) — RO. This bit is cleared upon RSMRST# or a read of

0 = If no taps are specified via the RS bits in Register A, this flag will not be set.

1 = Periodic interrupt Flag will be 1 when the tap specified by the RS bits of register A is

5Alarm Flag (AF) — RO.

0 = This bit is cleared upon RTCRST# or a read of Register C.

1 = Alarm Flag will be set after all Alarm values match the current time .

4Update-Ended Flag (UF) — RO.

0 = The bit is cleared upon RSMRST# or a read of Register C.

1 = Set immediately following an update cycle for each second.

3:0 Reserved. Will always report 0.

Bit Description

Valid RAM and Time Bit (VRT) — R/W.

0 = This bit should always be written as a 0 for write cycle, howev er it will return a 1 for

read cycles.

1 = This bit is hardwired to 1 in the RTC power well.

6 Reserved. This bit always returns a 0 and should be set to 0 for write cycles.

5:0

Date Alarm — R/W. These bits store the date of month alarm value. If set to 000000b,

then a don’ t care state is assumed. The host must configure the date alarm for these

bits to do anything, yet they can be written at any time. If the date alarm is not

enabled, these bits will return 0s to mimic the functionality of the Motorola 146818B.

These bits are not affected by any reset assertion.

LPC Interface Bridge Registers (D31 :F 0)

484 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.7 Processor Interface Registers (LPC I/F—D31:F0)

Table 13-8 is the register address map for the processor interface registers.

13.7.1 NMI_SC—NMI Status and Control Register

(LPC I/F—D31:F0)

I/O Address: 61h Attribute: R/W, RO

Default Value: 00h Size: 8-bit

Lockable: No Power Well: Core

Table 13-8. Processor Interface PCI Register Address Map (LPC I/F—D31:F0)

Offset Mnemonic Register Name Default Type

61h NMI_SC NMI Status and Control 00h R/W, RO

70h NMI_EN NMI Enable 80h R/W (special)

92h PORT92 Fast A20 and Init 00h R/W

F0h COPROC_ERR Coprocessor Error 00h WO

CF9h RST_CNT Reset Control 00h R/W

Bit Description

SERR# NMI Source Status (SERR#_NMI_STS) — RO.

1 = Bit is set if a PCI agent detected a system error and pulses the PCI SERR# line and

if bit 2 (PCI_SERR_EN) is cleared. This interrupt source is enabled by setting bit 2

to 0. To reset the interrupt, set bit 2 to 1 and then set it to 0. When writing to port

61h, this bit must be 0.

NOTE: This bit is set by any of the ICH9 internal sources of SERR; this includes SERR

assertions forwarded from the secondary PCI bus, errors on a PCI Express*

port, or other internal functions that generate SERR#.

IOCHK# NMI Source Status (IOCHK_NMI_STS) — RO.

1 = Bit is set if an LPC agent (via SERIRQ) asserted IOCHK# and if bit 3

(IOCHK_NMI_EN) is cleared. This interrupt source is enabled by setting bit 3 to 0.

To reset the interrupt, set bit 3 to 1 and then set it to 0. When writing to port 61h,

this bit must be a 0.

Timer Counter 2 OUT Status (TMR2_OUT_STS) — RO. This bit reflects the current

state of the 8254 co unter 2 output. Counter 2 must be programmed following any PCI

reset for this bit to have a determinate value. When writing to port 61h, this bit must

be a 0.

4Refresh Cycle Togg le (REF_TOGGLE) — RO. This signal toggles from either 0 to 1 or

1 to 0 at a rate that is equivalent to when refresh cycles would occur. When writing to

port 61h, this bit must be a 0.

3IOCHK# NMI Enable (IOCHK_NMI_EN) — R/W.

0 = Enabled.

1 = Disabled and cleared.

2PCI SERR# Enable (PCI_SERR_EN) — R/W.

0 = SERR# NMIs are enabled.

1 = SERR# NMIs are disabled and cleared.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 485

LPC Interface Bridge Registers (D31:F0)

13.7.2 NMI_EN—NMI Enable (and Real Time Clock Index)

I/O Address: 70h Attribute: R/W (special)

Default Value: 80h Size: 8-bit

Lockable: No Power Well: Core

Note: The R TC Index field is write-only for normal operation. This field can only be read in Alt -

Access Mode. Note, however, that this register is aliased to Port 74h (documented in),

and all bits are readable at that address.

13.7.3 PORT92—Fast A20 and Init Register (LPC I/F—D31:F0)

I/O Address: 92h Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Power Well: Core

1Speaker Data Enab le (SPKR_DAT_EN) — R/W.

0 = S PKR output is a 0.

1 = SPKR output is equivalent to the Counter 2 OUT signal value.

0Timer Counter 2 Enable (TIM_CNT2_EN) — R/W.

0 = Disable

1 = Enable

Bit Description

Bits Description

7NMI Enable (NMI_EN) — R/W (special).

0 = Enable NMI sources.

1 = Disable All NMI sources.

6:0 Real Time Clock Index Address (RTC_INDX) — R/W (special). This data goes to

the RTC to select which register or CMOS RAM address is being accessed.

Bit Description

7:2 Reserved

Alternate A20 Gate (ALT_A20_GATE) — R/W. This bit is Or’d with the A20G ATE

input signal to generate A20M# to the processor.

0 = A20M# signal can potentially go active.

1 = This bit is set when INIT# goes active.

0INIT_NOW — R/W. When this bit tr ansit ions from a 0 t o a 1, the ICH9 will force INIT#

active for 16 PCI clocks.

LPC Interface Bridge Registers (D31 :F 0)

486 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.7.4 COPROC_ERR—Coprocessor Error Register

(LPC I/F—D31:F0)

I/O Address: F0h Attribute: WO

Default Value: 00h Size: 8-bits

Lockable: No Power Well: Core

13.7.5 RST_CNT—Reset Control Register (LPC I/F—D31:F0)

I/O Address: CF9h Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Power Well: Core

Bits Description

7:0

Coprocessor Error (COPR OC_ERR) — WO. Any value written to this register will

cause IGNNE# to go active, if FERR# had generated an internal IRQ13. For FERR# to

generate an internal IRQ13, the COPROC_ERR_EN bit (Chipset Configuration Register,

Offset 31FFh, bit 1) must be 1.

Bit Description

7:4 Reserved

Full Reset (FULL_RST) — R/W. This bit is used to determine the states of SLP_S3#,

SLP_S4#, and SLP_S5# after a CF9 hard reset (SYS_RST =1 and RST_CPU is set to 1),

after PWROK going low (with RSMRST# high), or after two TCO timeouts.

0 = ICH9 will keep SLP_S3#, SLP_S4# and SLP_S5# high.

1 = ICH9 will drive SLP_S3#, SLP_S4# and SLP_S5# low for 3 – 5 seconds.

NOTE: When this bit is set, it also causes the full power cycle (SLP_S3/4/5# assertion)

in response to SYSRESET#, PWROK#, and Watchdog timer reset sources.

2Reset CPU (RST_CPU) — R/W. When this bit transitions from a 0 to a 1, it initiates a

hard or soft reset, as determined by the SYS_RST bit (bit 1 of this register).

System Reset (SYS_RST) — R/W. This bit is used to determine a hard or soft reset to

the processor.

0 = When RST_CPU bit goes from 0 to 1, the ICH9 performs a soft reset by activating

INIT# for 16 PCI clocks.

1 = When RST_CPU bit goes from 0 to 1, the ICH9 performs a hard reset by activating

PLTRST# and SUS_STAT# active for about 5-6 milliseconds. In this case,

SLP_S3#, SLP_S4# and SLP_S5# state (assertion or de-assertion) depends on

FULL_RST bit sett ing. The ICH9 main power well is reset when this bit is 1. It also

resets the resume well bits (except for those noted throughout the EDS).

0 Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 487

LPC Interface Bridge Registers (D31:F0)

13.8 Power Management Registers (PM—D31:F0)

The power management registers are distributed within the PCI Device 31: Function 0

space, as well as a separate I/O range. Each register is described below. Unless

otherwise indicate, bits are in the main (core) power well.

Bits not explicitly defined in each register are assumed to be reserved. When writin g to

a reserved bit, the value should always be 0. Software should not attempt to use the

value read from a reserved bit, as it may not be consistently 1 or 0.

13.8.1 Power Management PCI Configuration Registers

(PM—D31:F0)

Table 13-9 shows a small part of the configuration space for PCI Device 31: Function 0.

It includes only those registers dedicated for power management. Some of the

registers are only used for Legacy Power management schemes.

Table 13-9. Power Management PCI Register Address Map (PM—D31:F0)

Offset Mnemonic Register Name Default Type

A0h GEN_PMCON_1 General Power Management

Configuration 1 0000h R/W,, R/WO,

A2h GEN_PMCON_2 General Power Management

Configuration 2 00h R/W, R/WC

A4h GEN_PMCON_3 General Power Management

Configuration 3 00h R/W, R/WC

A6h GEN_PMCON_LO

CK General Power Management

Configuration Lock 00h RO, R/WLO

A8h C5_EXIT_TIMING

_CNT C5 Exit Timing Register (Mobil e

Only) 13h R/W

A9h Cx-STATE_CNF Cx State Configuration (Mobile

Only) 00h R/W

AAh C4-TIMING_CNT C4 Timing Control (Mobile Only) 00h R/W

ABh BM_BREAK_EN BM_BREAK_EN 00h R/W

ACh PMIR Power Management Initialization 00000000h R/W, R/WL

B8–BBh GPI_ROUT GPI Route Control 00000000h R/W

LPC Interface Bridge Registers (D31 :F 0)

488 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.1.1 GEN_PMCON_1—General PM Configuration 1 Register

(PM—D31:F0)

Offset Address: A0h Attribute: R/W, RO, R/WO

Default Value: 0000h Size: 16-bit

Lockable: No Usage: ACPI, Legacy

Power Well: Core

Bit Description

15:13 Reserved

(Mobile

Only)

C4 Disable — R/W. This bit disables the C4 feature.

0 = Enables C4

1 = Disables C4.

When C4 Disable is 1:

• I/O reads to the LVL4 register will be retried normally, but with no other action

• All C4 transition attempts are disabled, overriding C4onC3 and Pop-Down transition.

(Mobile

Only)

C5_Enable — R/W. This bit enables the C5 and C6 features. When this bit is 0, the

platform does not enable the C5 and C6 features. When this bit is 1, the platform

enables C5/C6 features.

This bit also, along wit h GPIO_USE_SEL [0] bit, enables selection of PMSYNC#

function on ICH pin as shown below:

When C5_Enable and GPIO_USE_SEL[0] are both 0:

• The R/W bits of the C5 Exit Timing Register become scratchpad bits with no effect on

hardware functions

• I/O Reads to the LVL5 and LVL6 registers will be retired normally, but with no other action

• All attempts to enter deeper C-States that require a transition through the C5 timing logic

will be ignored

12:11

(Desktop

Only) Reserved

BIOS_PCI_EXP_EN — R/W. This bit acts as a global enable for the SCI associated

with the PCI Express* po rts.

0 = The various PCI Express ports and (G)M CH cannot cause the PC I_EXP_STS bit to

go active.

1 = The various PCI Express ports and (G)MCH can cause the PCI_EXP_STS bit to go

active.

9PWRBTN_LVL — RO. This bit indicates the current state of the PWRBTN# signal.

0 = Low.

1 = High.

8Reserved

(Desktop

Only) Reserved

(Mobile

Only)

Enter C4 When C3 Invoked (C4onC3_EN) — R/W. If this bit is set, then when

software does a LVL3 read, the ICH9 transitions to the C4 state.

GPIO_USE_SEL[0] C5_Enable Result

1XGPIO

00See Below

01PMSYNC#

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 489

LPC Interface Bridge Registers (D31:F0)

6i64_EN. Software sets this bit to indicate that the processor is an IA_64 processor,

not an IA_32 processor. This may be used in various st ate machines where there are

behavioral differences.

CPU SLP# Enable (CPUSLP_EN) — R/W.

0 = Disable.

1 = Enables th e CPUSLP# signal to go active in the S1 state. This reduces the

processor power.

NOTE: CPUS LP# will go active during Intel SpeedStep® technology transitions and

on entry to C3 and C4 states even if this bit is not set. (Mobile Only)

SMI_LOCK — R/WO . When this bit is set, writ es to the GLB_SMI_EN bit (PM BASE +

30h, bit 0) will have no effect. Once the SMI_LOCK bit is set, writes of 0 to

SMI_LOCK bit will have no effect (i.e., once set, this bit can only be cleared by

PLTRST#).

3:2

(Desktop

Only) Reserved

(Mobile

Only)

Intel SpeedStep Enable (SS_EN) — R/W.

0 = Intel SpeedStep technology logic is disabled and the SS_CNT register will not be

visible (reads to SS_CNT will return 00h and writes will have no effect).

1 = Intel SpeedStep technology logic is enabled.

(Mobile

Only)

PCI CLKRUN# En able (CLKRUN_EN) — R/W.

0 = D isable. ICH9 drives the CLKRUN# signal l ow.

1 = Enable CLKRUN# logic to control the system PCI cl ock via the CLKRUN# and

STP_PCI# signals.

NOTE: When the SLP_EN# bit is set, the ICH9 drives the CLKRUN# signal low

regardless of the state of the CLKRUN_EN bit. This ensures that the PCI and

LPC clocks continue running during a transition to a sleep state.

1:0

Periodic SMI# Rate Select (PER_SMI_SEL) — R/W. Set by software to control

the rate at which periodic SMI# is generated.

00 = 64 seconds

01 = 32 seconds

10 = 16 seconds

11 = 8 second s

Bit Description

LPC Interface Bridge Registers (D31 :F 0)

490 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.1.2 GEN_PMCON_2—General PM Configuration 2 Register

(PM—D31:F0)

Offset Address: A2h Attribute: R/W, R/WC

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI, Legacy

Power Well: Resume

Bit Description

DRAM Initialization Bit — R/W. This bit does not effect hardware functionality in any

way. BIOS is expect ed to set this bit prior to starting the DRAM initialization sequence

and to clear this bit after completing the DRAM initialization sequence. BIOS can detect

that a DRAM initialization sequence was interrupted by a reset by reading this bit during

the boot sequence.

• If the bit is 1, then the DRAM initialization was interrupted.

• This bit is reset by the assertion of the RSMRST# pin.

6:5

CPU PLL Lock Time (CPLT) — R/W. This field indicates the amount of time that the

processor needs to lock its PLLs. This is used wherever timing t270 (Chapter 8) applies.

00 = min 30.7 µs (Default)

01 = min 61.4 µs

10 = min 122.8 µs

11 = min 245.6 µs

It is the responsibili ty of the BIOS to program the co rrect value in this field prio r to the

first transition to C3 or C4 states (or performing Intel SpeedStep® technology

transitions). (Mobile Only)

NOTE: The DPSLP-TO-MCH Message bits (D31:F0:AAh, bits 1:0) act as an override to

these bits.

NOTE: These bits are not cleared by any type of reset except RSMRST# or a CF9h

write.

System Reset Status (SRS) — R/WC. Software clears this bit by writing a 1 to it.

0 = SYS_RESET# button Not pressed.

1 = ICH9 sets this bit when the SYS_RESET# button is pressed. BIOS is expected to

read this bit and clear it, if it is set.

NOTE: This bit is also reset by RSMRST# and CF9h resets.

CPU Thermal Trip Status (CTS) — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = This bit is set when PLTRST# is inactive and THRMTRIP# goes active while the

system is in an S0 or S1 state.

NOTES:

1. This bit is also reset by RSMRST#, and CF9h resets. It is not reset by the

shutdown and reboot associated with the CPUTHRMTRIP# event.

2. The CF9h reset in the description refers to CF9h type core well reset which

includes SYS_RST#, PWROK/VRMPWRGD low, SMBus hard reset, TCO Timeout.

This type of reset will clear CTS bit.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 491

LPC Interface Bridge Registers (D31:F0)

Minimum SLP_S4# Assertion Width Violation Status — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = Hardware sets this bit when the SLP_S4# assertion width is less than the time

programmed in the SLP_S4# Minimum Assertion Width field (D31:F0:Offset

A4h:bits 5:4). The ICH9 begins the timer when SLP_S4# is asserted during S4/S5

entry, or when the RSMRST# input is deasserted during G3 exit. Note that this bit

is functional regardless of the value in the SLP_S4# Assertion Stretch Enable

(D31:F0:Offset A4h:bit 3).

NOTE: This bit is reset by the assertion of the RSMRST# pin, but can be set in some

cases before the default value is readable.

CPU Power Failure (C PUPWR_FLR) — R/W.

0 = Software (typically BIOS) clears this bit by writing a 0 to it.

1 = Indicates that the VRMPWRGD signal from the processor’s VRM went low while the

system was in an S0 or S1 state.

NOTE: VRMPWRGD is sampl ed using the RTC clock. Therefore, low times that are less

than one RTC clock period may not be detected by the Intel ICH9.

PWROK Failure (PWROK_FLR) — R/WC.

0 = Software clears this bit by writ ing a 1 to it, or when the system goes into a G3

state.

1 = This bit will be set any time PWROK goes low, when the system was in S0, or S1

state. The bit will be cleared only by software by writing a 1 to this bit or when the

system goes to a G3 state.

NOTE: See Chapter 5.13.7.3 for more details about the PWROK pin functionality.

NOTE: In the case of true PWROK failure, PWROK will go low first before the

VRMPWRGD.

Bit Description

LPC Interface Bridge Registers (D31 :F 0)

492 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.1.3 GEN_PMCON_3—General PM Configuration 3 Register

(PM—D31:F0)

Offset Address: A4h Attribute: R/W, R/WC

Default Value: 00h Size: 16-bit

Lockable: No Usage: ACPI, Legacy

Power Well: RTC, SUS

Bit Description

15:10 Reserved

General Reset Status (GEN_RST_STS) — R/WC. This bit is set by hardware whenever

PLTRST# asserts for any reason other than going into a software-entered sleep state

(via PM1CNT.SLP_EN write) or a suspend well power failure (RSMRST# pin assertion).

BIOS is expected to consult and then write a ‘1’ to clear this bit during the boot flow

before determining what action to take based on PM1_STS.WAK_STS = 1. If

GEN_RST_STS = ‘1’, the cold reset boot path should be followed rather than the

resume path, regardless of the setting of WAK_STS.

This bit is cleared by the RSMRST# pin.

S4_STATE# Pin Disable — R/W.

0 = The traditional SLP_S4# signal (without Management Engine Overrides) is driven

on the S4_STATE# Pin. GPIO26 defaults to its native functionality, S4_STATE#.

1 = The S4_STATE# pin functionality is disabled. The pin is configured as GPIO26,

default as an output.

NOTE: This bit is cleared by RTCRST#. This bit acts as an override for

GPIO_USE_SEL[26].

7:6

SWSMI_RATE_SEL — R/W. This field indicates when the SWSMI timer will time out.

Valid values are:

00 = 1.5 ms ± 0.6 ms

01 = 16 ms ± 4 ms

10 = 32 ms ± 4 ms

11 = 64 ms ± 4 ms

These bits are not cleared by any type of reset except RTCRST#.

5:4

SLP_S4# Minimum Assertion Width — R/W. This field indicates the minimum

assertion width of the SLP_S4# signal to ensure that the DRAMs have been safely

power-cycled.

Valid values are:

11 = 1 to 2 seconds

10 = 2 to 3 seconds

01 = 3 to 4 seconds

00 = 4 to 5 seconds

This value is used in two ways:

1. If the SLP_S4# assertion width is ever shorter than this time, a status bit is set

for BIOS to read when S0 is entered.

2. If enabled by bit 3 in this register, the hardware wi ll prevent the SLP_S4# signal

from deasserting within this minimum time period after asserting.

RTCRST# forces this field to the conservative default state (00b).

NOTE: This field is RO when the SLP_S4# Stretching Policy Lock-Down bit is set.

SLP_S4# Assertion Stretch Enable — R/W.

0 = The SLP_S4# minimum assertion time is 1 to 2 RTCCLK.

1 = The SLP_S4# signal minimally assert for the time specified in bits 5:4 of this

This bit is cleared by RTCRST#.

NOTE: This bit is RO when the SLP_S4# Stretching Policy Lock-Down bit is set.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 493

LPC Interface Bridge Registers (D31:F0)

NOTE: RSMRST# is sampled using the RT C clock. Therefore, low times that are less than one RTC

clock period may not be detected by the ICH9.

2RTC Power Status (RTC_PWR_STS) — R/W. This bit is set when RT CRST# indicates

a weak or missing battery. The bit is not cleared by any type of reset. The bit will

remain set until the software clears it by writing a 0 back to this bit position.

Power Failure (PWR_FLR) — R/WC. This bit is in t he RTC well, and is not cleared by

any type of reset except RTCRST#.

0 = Indicates that the trickle current has not failed since the last time the bit was

cleared. Software clears this bit by writing a 1 to it.

1 = Indicates that the trickle current (from the main battery or trickle supply) was

removed or failed.

NOTE: Clearing CMOS in an ICH-based platform can be done by using a jumper on

RTCRST# or GPI, or using SAFEMODE strap. Implementations should not

attempt to clear CMOS by using a jumper to pull VccRTC low.

AFTERG3_EN — R/W. This bit determines what stat e to go to when power is re-applied

after a power failure (G3 state). This bit is in the RT C well and is only cleared by writes

of 06h or 0Eh to CF9h (when the CF9h global reset bit is clear), receiving hard reset

command with or without power cycle from SMBus or RTCRST#.

0 = System will return to S0 state (boot) after power is re-applied.

1 = System will return t o the S5 state ( except if it was i n S4, in which case it will ret urn

to S4). In the S5 state, the only enabled wake event is the Power Button or any

enabled wake event that was preserved through the power failure.

NOTE: This bit is set an y time a Power Button Ov erride occurs (i.e. , the power button is

pressed for at least 4 consecutive seconds), due to the corresponding bit in the

SMBus unconditional power down message, due to an internal thermal sensor

catastrophic condition and the assertion of THRMTRIP#.

Bit Description

LPC Interface Bridge Registers (D31 :F 0)

494 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.1.4 GEN_PMCON_LOCK- Ge neral Power Management Configuration Lock

Offset Address: A6h Attribute: RO, R/WLO

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI

Power Well: Core

Bit Description

(Desktop

Only) Reserved

(Mobile

Only)

Unlocked C-State Transition — RO. This bit is set by hardware when a processor

power state (C-State) transition deeper than C2 occurs and the C-

STATE_CONFIG_LOCK bit is not set. This bit is cleared by PLTRST# and is not

writable by software.

6:3 Reserved

SLP_S4# St retching Po licy Lock-D own — R/WLO. When set to 1, this bit locks

down the SLP_S4# Minimum Assertion Width and SLP_S4# Assertion Stretch

Enable bits in the GEN_PMCON_3 register, making them read-only.

This bit becomes locked when a value of 1b is written to it. Writes of 0 to this bit

are always ignored. This bit is cleared by platform reset.

ACPI_BASE_LOCK — R/WLO. When set to 1, this bit locks down the ACPI Base

Address Register (ABASE) at offset 40h. The Base Address Field becomes read-

only.

This bit becomes locked when a value of 1b is written to it. Writes of 0 to this bit

are always ignored. Once locked by writing 1, the only way to clear this bi t is to

perform a platform reset.

(Mobile

Only)

C-STATE_CONFIG_LOCK — R/WLO. When set to 1, this bit locks do wn the C-

State configuration parameters. The following configuration bits become read-only

when this bit is set:

• GEYSERVILLE_EN (GEN_PMCON_1, bit 3)

• IA64_EN (GEN_PMCON_1, bit 6)

• C4_DISABLE (GEN_PMCON_1, bit 12)

• CPU_PLL_LOCK_TIME (GEN_PMCON_2, bits 6:5)

• The entire C4 Timing Control Register (C4_TIMING_CNT)

• The entire C5 Exit Timing Register (C5_EXIT_TIMING_CNT)

This bit becomes locked when a value of 1b is written to it. Writes of 0 to this bit

are always ignored. Once locked by writing 1, the only way to clear this bi t is to

perform a platform reset.

(Desktop

Only) Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 495

LPC Interface Bridge Registers (D31:F0)

13.8.1.5 C5_EXIT_TIMING_CNT- C5 Ex it Timing Register (Mobile Only)

Offset Address: A8h Attribute: R/W

Default Value: 13h Size: 8-bit

Lockable: Yes Usage: ACPI, Legacy

Power Well: Core

This register is used to control the C5 and C6 Exit transitions.

Bit Description

7Reserved.

6SLow-C5 Exit Enable: When 1, this bit enables the Slow-C5/C6 Exit functionality.

5:3

PMSYNC# to STPCLK# ( t275): This fi eld selects th e amount of time th at the ICH

waits from the deassertion to PMSYNC# to the deassertion of STPCLK # during C5

and C6 exit process. This timing is referred to as t275 in timing diagrams.

000 = 16-17 PCI CLKs

001 = 80-86 us

010 = 99-105 us (Default)

011 = 118-124 us

100 = 18-24 us

101 = 38-44 us

110 = 56-62 us

111 = 199-205 us

2:0

DPRSTP# to STP_CPU# (t266b): This field selects the amount of time that the

ICH waits from the deassertion of DPRSTP# to the deassertion of STP_CPU# during

C5 and C6 exit process. This timing is referred to as t266b in timing diagrams.

000 = 22-28 us

001 = 34-40 us

010 = 56-62 us

011 = 95-102 us (Default)

101 = 138-144 us

110 = 72-78 us

111 = 199-205 us

LPC Interface Bridge Registers (D31 :F 0)

496 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.1.6 Cx-STATE_CNF—Cx State Configuration Register

(PM—D31:F0) (Mobile Only, Except Bit 2)

Offset Address: A9h Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI, Legacy

Power Well: Core

This register is used to enable new C-state related modes.

Bit Description

7SCRATCHPAD (S P) — R/W.

6:5 Reserved

Popdown Mode Enable (PDME) — R/W. This bit is used in conjunction with the

PUME bit (D31:F0:A9h, bit 3). If PUME is 0, then this bit must also be 0.

0 = The ICH9 will not attem pt to automatically re turn to a previous C3 or C4 s tate.

1 = When this bit is a 1 and Intel® ICH9 observes that there are no bus master

requests, it can return to a previous C3 or C4 state.

NOTE: This bit is separate from the PUME bit to cover cases where latency issues

permit POPUP but not POPDOWN.

Popup Mode Enable (PUME) — R/W. When this bit is a 0, the ICH9 behaves like

ICH5, in that bus m aster traffic is a br eak ev en t, and it wil l ret urn fr om C3/C4 to C0

based on a break event. See Chapter 5.13.5 for additional details on this mode.

0 = The ICH9 will treat Bu s mast er traffic a break event, and wil l return from C3/C4

to C0 based on a break event.

1 = When this bit is a 1 and ICH9 observes a bus master request, it will take the

system from a C3 or C4 state to a C2 state and auto enable bus masters. This

will let snoops and memory access occur.

(Desktop

and

Mobile)

Report Zero for BM_STS (BM_STS_ZERO_EN) — R/W.

0 = The ICH9 sets BM_STS (PMBASE + 00h, bit 4) if there is bus master activity

from PCI, PCI Express* and internal bus masters.

1 = When this bit is a 1, ICH9 will not set the BM_STS if there is bus master activity

from PCI, PCI Express and in ternal bus masters.

NOTES:

1. If the BM_STS bit is already set when the BM_STS_ZERO_EN bit is set, the

BM_STS bit will remain set. Software will still need to clear the BM_STS bit.

2. It is expected that if the PUME bit (this register, bit 3) is set, the

BM_STS_ZERO_EN bit should also be set. Setting one without the other

would mainly be for debug or errata workaround.

3. BM_STS will be set by LPC DMA or LPC masters , even if BM_ST S_ZERO_EN is

set.

1:0 Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 497

LPC Interface Bridge Registers (D31:F0)

13.8.1.7 C4-TIMING_CNT—C4 Timing Control Register

(PM—D31:F0) (Mobile Only)

Offset Address: AAh Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI, Legacy

Power Well: Core

This register is used to enable C-state related modes.

Bit Description

7Force Slow-C4 Exit — RW.

When set to 1, this bit forces the slow-C4 exit functionality to occur, rega rdless of the

trigger event or the setting of the Slow-C4 Exit Enable bit (Bit 6).

6Slow-C4 Exit Enable —When 1, this bit enables the Slow-C4 Exit functionality.

5:4 Reserved.

3:2

DPRSLPVR to STPCPU — R/W. This f ield selects the amount of time that the ICH9

waits for from the deassertion of DPRSLPVR to the deassertion of STP_CPU#. This

provides a programmable time for the processor’s voltage to stabilize when exiting

from a C4 state. This thus changes the value for t266a.

1:0

DPSLP-TO-MCH Message— R/W. This field selects the DPSLP# deassertion to MCH

message time (t270). Normally this value is determined by the CPU_PLL_LOCK_TIME

field in the GEN_PMCON_2 register. When this field is non-zero, then the values in this

consistent manner.

Bits t266amin t266amax Comment

00b 95 µs 101 µs Default

01b 22 µs 28 µs Value used for “Fast” VRMs

10b Reserved

11b Reserved

Bits t270

00b Use value is CPU_PLL_LOCK_TIME field (default is 30 µs)

01b 20 µs

10b 15 µs

11b 10 µs

LPC Interface Bridge Registers (D31 :F 0)

498 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.1.8 BM_BREAK_EN Register (PM—D31:F0) (Mobile Only)

Offset Address: ABh Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI, Legacy

Power Well: Core

Bit Description

STORAGE_BREAK_EN — R/W.

0 = Serial ATA traffic will not act as a break event.

1 = Serial ATA traffic acts as a break event, even if the BM_STS-ZERO_EN and

POPUP_EN bits are set. Parallel IDE or Serial A T A master activity will cause BM_STS

to be set and will cause a break from C3/C4.

PCIE_BREAK_EN — R/W.

0 = PCI Express* traffic will not act as a break event.

1 = PCI Express traffic acts as a break event, even if the BM_STS-ZERO_EN and

POPUP_EN bits are set. PCI Express master activity will ca use BM_STS to be set

and will cause a break from C3/C4.

PCI_BREAK_EN — R/W.

0 = PCI traffic will not act as a break event.

1 = PCI traffic acts as a break ev ent, even if the BM_STS- ZERO_EN an d POPUP_EN bits

are set. PCI master activity will cause BM_STS to be set and will cause a break

from C3/C4.

4:3 Reserved

EHCI_BREAK_EN — R/W.

0 = EHCI traffic will not act as a break event.

1 = EHCI traffic acts as a break eve nt, even if the BM_STS-ZERO_EN and POPUP_EN

bits are set. EHCI master activity will cause BM_STS to be set and will cause a

break from C3/C4.

UHCI_BREAK_EN — R/W.

0 = UHCI traffic will not act as a break event.

1 = USB traffic from any of the internal UHCIs acts as a break event, even if the

BM_STS-ZERO_EN and POPUP_EN bits are set. UHCI master activity will cause

BM_STS to be set and will cause a break from C3/C4.

HDA_BREAK_EN — R/W.

0 = Intel® High Definition Audio traffic will not act as a break event.

1 = Intel High Definition Audio traffic acts as a break event, even if the BM_STS-

ZERO_EN and POPUP_EN bits are set.

Intel High Definition Audio master activity will cause BM_STS to be set and will

cause a break from C3/C4.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 499

LPC Interface Bridge Registers (D31:F0)

13.8.1.9 PMIR—Power Manag ement Initialization Register (PM—D31:F0)

Offset Address: ACh Attribute: R/W

Default Value: 00000000h Size: 32-bit

13.8.1.10 GPIO_ROUT—GPIO Routing Control Register

(PM—D31:F0)

Offset Address: B8h – BBh Attribute: R/W

Default Value: 00000000h Size: 32-bit

Lockable: No Power Well: Resume

Note: GPIOs that are not implemented will not have the corresponding bits implemented in

this register.

Bit Description

31 CF9h Lock Down (CF9Lock)— RW.

When set to 1, this bit locks itself and bit 20 (CF9GR) in this register.

This bit is reset by a CF9h reset.

30 PMIR Field 2 — R/W. BIOS must program this bit to 1b.

29:21 Reserved.

CF9h Global Reset (CF9GR)— R/W.

When set, a CF9h write of 6h or Eh will cause a Global reset of both the Host and ME

partitions. If this bit is cleared, a CF9h write of 6h or Eh will only reset the host

partition. This bit field is not reset by a CF9h reset.

19:10 Reserved

9:8 PMIR Field 0 — R/W. BIOS must program these bits to 11b.

7:0 Reserved

Bit Description

31:30 GPIO15 Route — R/W. See bits 1:0 for description.

Same pattern for GPIO14 through GPIO3

5:4 GPIO2 Route — R/W. See bits 1:0 for description.

3:2 GPIO1 Route — R/W. See bits 1:0 for description.

1:0

GPIO0 Route — R/W. GPIO[15:0] can be routed to cause an SMI or SCI when the

GPIO[n]_STS bit i s set. If the GPIO0 is no t set to an input, this field has no effect.

If the system is in an S1–S5 state and if the G PE0_EN bit is also set, th en the GPIO can

cause a Wake event, even if the GPIO is NOT routed to cause an SMI# or SCI.

00 = No effect.

01 = SMI# (if corresponding ALT_GPI_SMI_EN bit is also set)

10 = SCI (if corresponding GPE0_EN bit is also set)

11 = Reserved

LPC Interface Bridge Registers (D31 :F 0)

500 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.2 APM I/O Decode

Table 13-10 shows the I/O registers associated with APM support. This register space is

enabled in the PCI Device 31: Function 0 space (APMDEC_EN), and cannot be moved

(fixed I/O location).

13.8.2.1 APM_CNT—Advanced Power Management Control Port Register

I/O Address: B2h Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Usage: Legacy Only

Power Well: Core

13.8.2.2 APM_STS—Advanced Power Management Status Port Register

I/O Address: B3h Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Usage: Legacy Only

Power Well: Core

Table 13-10. APM Register Map

Address Mnemonic Register Name Default Type

B2h APM_CNT Advanced Power Management Control Port 00h R/W

B3h APM_STS Advanced Power Management Status Port 00h R/W

Bit Description

7:0 Used to pass an APM command be tween the OS and the SMI handler. Writes to this

port not only store data in the APMC register, but also generates an SMI# when the

APMC_EN bit is set.

Bit Description

7:0 Used to pass data between t he OS and the SMI handler. Basically, this is a scratchpad

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 501

LPC Interface Bridge Registers (D31:F0)

13.8.3 Power Management I/O Registers

Table 13-11 shows the registers associated with ACPI and Legacy power management

support. These registers are enabled in the PCI Device 31: Function 0 space

(PM_IO_EN), and can be moved to any I/O location (128-byte aligned). The registers

are defined to support the ACPI 3.0a specification, and use the same bit names.

Note: All reserved bits and registers will always return 0 when read, and will have no effect

when written.

Table 13-11. ACPI and Legacy I/O Register Map (Sheet 1 of 2)

PMBASE

+ Offset Mnemonic Register Name ACPI Pointer Default Type

00h–01h PM1_STS PM1 Status PM1a_EVT_BLK 0000h R/WC

02h–03h PM1_EN PM1 Enable PM1a_EVT_BLK+

20000h R/W

04h–07h PM1_CNT PM1 Control PM1a_CNT_BLK 00000000h R/W, WO

08h–0Bh PM1_TMR PM1 Timer PMTMR_BLK xx000000h RO

0Ch–0Fh — Reserved — — —

10h–13h PROC_CNT Processor Control P_BLK 00000000h R/W, RO,

14h LV2 Level 2 P_BLK+4 00h RO

15h–18h — Reserved (Desktop Only) — — —

15h LV3 Level 3 (Mobile Only) P_BLK+5 00h RO

16h LV4 Level 4 (Mobile Only) P_BLK+6 00h RO

17h LV5 Level 5 (Mobile Only) P_BLK+7 00h RO

18h LV6 Level 6 (Mobile Only) P_BLK+8 00h RO

19h–1Fh — Reserved — — —

20-27h GPE0_STS General Purpose Event 0

Status GPE0_BLK 00000000h R/WC

28-2Fh GPE0_EN General Purpose Event 0

Enables GPE0_BLK+8 00000000h R/W

30h–33h SMI_EN SMI# Control and Enable 00000000h R/W, WO,

R/WO

34h–37h SMI_STS SMI Status 00000000h R/WC, RO

38h–39h ALT_GP_SMI_EN Alternate GPI SMI Enable 0000h R/W

3Ah–3Bh ALT_GP_SMI_STS Alternate GPI SMI Status 0000h R/WC

3Ch UPRWC USB Per- Port Re gisters

Write Control 0000h R/WC, RO ,

R/WO

3Dh–41h — Reserved — — —

42h GPE_CNTL General Purpose Event

Control 00h RO, R/W

43h — Reserved — — —

44h–45h DEVACT_STS Device Activity Status 0000h R/WC

46h–4Fh — Reserved — — —

LPC Interface Bridge Registers (D31 :F 0)

502 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

50h — Reserved (Desktop Only) — — —

50h PM2_CNT PM2 Control (Mobile Only) PM2a_CNT_BLK 00h R/W

51h–5Fh — Reserved — — —

54h–57h C3_RES C3-Residency Register

(Mobile On ly) — 00000000h RO

58h–5Bh C5_RES C5-Residency Register

(Mobile On ly) 00000000h RO

60h–7Fh — Reserved for TCO — — —

Table 13-11. ACPI and Legacy I/O Register Map (Sheet 2 of 2)

PMBASE

+ Offset Mnemonic Register Name ACPI Pointer Default Type

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 503

LPC Interface Bridge Registers (D31:F0)

13.8.3.1 PM1_STS—Power Managem ent 1 Status Register

I/O Address: PMBASE + 00h

(ACPI PM1a_EVT_BLK) Attribute: R/WC

Default Value: 0000h Size: 16-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Bits 0–7: Core,

Bits 8–15: Resume,

except Bit 11 in RTC

If bit 10 or 8 in this register is set, and the corresponding _EN bit is set in the PM1_EN

already in an S0 state when the event occurs), the ICH9 will also generate an SCI if the

SCI_EN bit is set, or an SMI# if the SCI_EN bit is not set.

Note: Bit 5 does not cause an SMI# or a wake event. Bit 0 does not cause a wake event but

can cause an SMI# or SCI.

Bit Description

Wake Status (WAK_STS) — R/WC. This bit is not affected by hard resets caused

by a CF9 write, but is reset by RSMRST#.

0 = Software clears this bit by writing a 1 to it.

1 = Set by hardware when the system is in one of the sleep states (via the SLP_EN

bit) and an enabled wake event occurs. Upon setting this bit, the ICH9 will

transition the system to the ON state.

If the AFTERG3_EN bit is not set and a power failure (such as removed batteries)

occurs without the SLP_EN bit set, the system will return to an S0 state when powe r

returns, and the WAK_STS bit will not be set.

If the AFTERG3_EN bit is set and a power failure occurs without the SLP_EN bit

having been set, the system will go into an S5 state when power returns, and a

subsequent wake event will cause the WAK_STS bit to be set. Note that any

subsequent wake event would have to be caused by either a Power Button press, or

an enabled wake event that was preserved through the power failure (enable bit in

the RTC well).

PCI Express Wake Status (PCIEXPWAK_STS) — R/WC.

0 = Software clears this bit by writing a 1 to it. If the WAKE# pin is still active during

the write or the PME mes sage received indicat ion has not been cleared in the

root port, then the bit will remain active (i.e. all inputs to this bit are level-

sensitive).

1 = This bit is set by hardware to indicate that the system woke due to a PCI

Express wakeup event. This wakeup event can be caused by the PCI Express

WAKE# pin being activ e or receipt of a PCI Express PME message at a root port.

This bit is set only when one of these events causes the system to transition

from a non-S0 system power state to the S0 system power state. This bit is set

independent of the s tate of the PCIEXP_WAKE_DIS bit.

Note: This bit does not itself cause a wake event or prevent entry to a sleeping

state. Th us i f the bit i s 1 an d the sy st em is put in to a sl eepin g s tate, the s ystem wil l

not automati cally wake.

13:12 Reserved

LPC Interface Bridge Registers (D31 :F 0)

504 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Power Button Override Status (PWRBTNOR_STS) — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = This bit is set any time a P ower Button Ov erride occurs (i.e. , the power button is

pressed for at least 4 consecutive seconds), due to the corresponding bit in the

SMBus slave message, ME Initiated Power Button Override, ME Initiated Host

Reset with Power down or due to an internal thermal sensor catastrophic

condition. The power button override causes an unconditional transition to the

S5 state, as well as sets the AFTERG3_EN bit. The BIOS or SCI handler clears

this bit by writing a 1 to it. This bit is not affected by hard resets via CF9h

writes, and is not reset by RSMRST#. Thus, this bit is preserved through power

failures. N ote that if thi s bit is still asserted when the global SCI_EN is s et then

an SCI will be generated.

RTC Status (RTC_STS) — R/WC. This bit is not affected by hard resets caused by a

CF9 write, but is reset by RSMRST#.

0 = Software clears this bit by writing a 1 to it.

1 = Set by hardware when the RTC generates an alarm (assertion of the IRQ8#

signal). Additio nally if the R T C_EN bit (PM BASE + 02h, bit 10 ) is set, the s etting

of the RTC_STS bit will generate a wake event.

ME_STS — R/WC. This bit is set when the Management Engine generates a Non-

Maskable wake event, and is not affected by any other enable bit. When this bit is

set, the Host Power Management logic wakes to S0.

This bit is only set by hardware and can only be reset by writing a one to this bit

position. This bit is not affected by hard resets caused by a CF9 write, but is reset by

RSMRST#.

Power Button Status (PWRBTN__STS) — R/WC. This bit is not affected by hard

resets caused by a CF9 write.

0 = If the PWRBTN# signal is held low for more than 4 seconds, the hardware clears

the PWRBTN_STS bit, sets the PWRBTNOR_STS bit, and the system transitions

to the S5 state with only PWRBTN# enabled as a wake event.

This bit can be cleared by software by writing a one to the bit position.

1 = This bit is set by hardware when the PWRBTN# signal is asserted Low,

independent of any other enable bit.

In the S0 state, whil e PWRBTN_EN and PWRBTN_STS are both set, an SCI (or

SMI# if SCI_EN is not set) will be generated.

In any sleeping state S1–S5, while PWRBTN_EN (PMBASE + 02h, bit 8) and

PWRBTN_STS are both set, a wake event is generated.

NOTE: If the PWRBTN_STS bit is cleared by software while the PWRBTN# signal is

sell asserted, this will not cause the PWRBN_STS bit to be s et. The PWRBTN #

signal must go inactive and active again to set the PWRBTN_STS bit.

7:6 Reserved

Global Status (GBL _STS) — R/WC.

0 = The SC I handler should then clear this bit by writing a 1 to the bit location.

1 = Set when an SCI is generated due to BIOS wanting the attention of the SCI

handler. BIOS has a corresponding bit, BIOS_RLS, which will cause an SCI and

set this bit.

(Desktop

Only) Reserved

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 505

LPC Interface Bridge Registers (D31:F0)

(Mobile

Only)

Bus Master Status (BM_STS) — R/WC. This bit will not cause a wake event, SCI

or SMI#.

0 = Software clears this bit by writing a 1 to it.

1 = Set by the ICH9 when a bus master requests access to main memory. Bus

master activit y is detected by any of th e PCI R equests being active, any internal

bus master request being active, or REQ-C2 message received while in C3 or C4

state.

NOTES:

1. If the BM_STS_ZERO_EN bit is set, then this bit will generally report as a 0.

LPC DMA and bus master activity will always set the BM_STS bit, even if the

BM_STS_ZERO_EN bit is set.

3:1 Reserved

Timer Overflow Status (TMROF_STS) — R/WC.

0 = The SCI or SMI# handler clears this bit by writing a 1 to the bit location.

1 = Thi s bit gets set any time bit 22 of the 24-bi t timer goes high (bits are

numbered from 0 to 23). This will occur every 2.3435 seconds. When the

TMROF_EN bit (PMBA SE + 02h, bit 0) i s set, then the setting of th e TMROF_STS

bit will additionally generate an SCI or SMI# (depending on the SCI_EN).

Bit Description

LPC Interface Bridge Registers (D31 :F 0)

506 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.3.2 PM1_EN—Power Management 1 Enable Register

I/O Address: PMBASE + 02h

(ACPI PM1a_EVT_BLK + 2) Attribute: R/W

Default Value: 0000h Size: 16-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Bits 0–7: Core,

Bits 8–9, 11–15: Resume,

Bit 10: RTC

Bit Description

15 Reserved

PCI Express* Wake Disable(PCIEXPWAK_DIS) — R/W. Modification of this bit has

no impact on the value of the PCIEXP_WAKE_STS bit.

0 = Inputs to the PCIEXP_WAKE_STS bit in the PM1 Status register enabled to wake

the system.

1 = Inputs to the PCIEXP_WAKE_STS bit in the PM1 Status register disabled from

waking the syste m.

13:11 Reserved

RTC Event Enable (RTC_EN) — R/W. This bit is in the RTC well to allow an R T C event

to wake after a power failure. This bit is not cleared by any reset other than RTCRST#

or a Power Button Override event.

0 = No SCI (or SMI#) or wake event is generated then RTC_STS (PMBASE + 00h, bit

10) goes active.

1 = An SCI (or SMI#) or wake event will occur when this bit is set and the RTC_ST S bit

goes active.

9 Reserved.

Power Button Enable (PWR BTN_EN) — R/W. This bit is used to enable the setting

of the PWRBTN_STS bit to generate a power management event (SMI#, SCI).

PWRBTN_EN has no effect on the PWRBTN_STS bit (PMBASE + 00h, bit 8) being set by

the assertion of the power button. The Power Button is always enable d a s a Wake

event.

0 = Disable.

1 = Enable.

7:6 Reserved.

Global Enable (GBL_EN) — R/W. When both the GBL_EN and the GBL_STS bit

(PMBASE + 00h, bit 5) are set, an SCI is raised.

0 = Disable.

1 = Enable SC I on GBL_STS going active.

4:1 Reserved.

Timer Overflow Interrupt Enable (TMROF_EN) — R/W. Works in conjunction with

the SCI_EN bit (PMBASE + 04h, bit 0) as described below:

TMROF_EN SCI_EN Ef fect when TMROF_STS is set

0 X No SMI# or SCI

10 SMI#

11 SCI

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 507

LPC Interface Bridge Registers (D31:F0)

13.8.3.3 PM1_CNT—Power Managem ent 1 Control

I/O Address: PMBASE + 04h

(ACPI PM1a_CNT_BLK) Attribute: R/W, WO

Default Value: 00000000h Size: 32-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Bits 0–7: Core,

Bits 8–12: RTC,

Bits 13–15: Resume

Bit Description

31:14 Reserved.

13 Sleep Enable (SLP_EN) — WO. Setting this bit causes th e system to sequen ce into

the Sleep state defined by the SLP_TYP field.

12:10

Sleep Type (SLP_TYP) — R/W. This 3-bit field defines the ty pe of Sleep the

system should e nter when the SLP_EN bi t is set to 1. These bits are only reset by

RTCRST#.

9:3 Reserved.

Global Release (GBL_RLS) — WO.

0 = This bit always reads as 0.

1 = ACPI software writes a 1 to this bit to raise an event to the BIOS. BIOS software

has a corresponding enable and status bits to control its ability to receive ACPI

events.

(Desktop

Only) Reserved

(Mobile

Only)

Bus Master Reload (BM_RLD) — R/W. This bit is treated as a sc r at chpad bit. This

bit is reset to 0 by PLTRST#

0 = Bus master requests will not cause a break from the C3 state.

1 = Enables Bus Master requests (in ternal or external) to caus e a break from the C3

state.

If software fails to set this bit before going to C3 state, ICH9 will still return to a

snoopable state from C3 or C4 states due to bus master activity.

Code Master Interrupt

000b ON: Typically maps to S0 state.

001b Asserts STPCLK#. Puts processor in Stop-Grant state. Optional to

assert CPUSLP# to put processor in sleep state: Typically maps to S1

state.

010b Reserved

011b Reserved

100b Reserved

101b Suspe nd-To-RAM. Assert SLP_S3#: Typically maps to S3 state.

110b Suspend-To-Disk. Assert SLP_S3#, and SLP_S4#: Typically maps to

S4 state.

111b Soft Off . Assert SLP_S3#, SLP_S4#, and SLP_S5#: Typically maps to

S5 state.

LPC Interface Bridge Registers (D31 :F 0)

508 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.3.4 PM1_TMR—Power Management 1 Timer Register

I/O Address: PMBASE + 08h

(ACPI PMTMR_BLK)Attribute: RO

Default Value: xx000000h Size: 32-bit

Lockable: No Usage: ACPI

Power Well: Core

13.8.3.5 PROC_CNT—Processor Co ntrol Register

I/O Address: PMBASE + 10h

(ACPI P_BLK) Attribute: R/W, RO, WO

Default Value: 00000000h Size: 32-bit

Lockable: No (bits 7:5 are write once)Usage: ACPI or Legacy

Power Well: Core

SCI Enable (SCI_EN) — R/W. Selects the SCI interrupt or the SMI# interrupt for

various events including the bits in the PM1_STS register (bit 10, 8, 0), and bits in

GPE0_STS.

0 = These events will generate an SMI#.

1 = These events will generate an SCI.

Bit Description

31:24 Reserved

23:0

Timer Value (TMR_VA L ) — RO. Returns the running count of the PM timer. This

counter runs off a 3.579545 MHz clock (14.31818 MHz divided by 4). It is reset to 0

during a PCI reset, and then co ntinues counting as long as the system is in the S0

state. After an S1 state, the counter will not be reset (it wi ll continue counting from the

last value in S0 state.

Anytime bit 22 of the timer goes HIGH to LOW (bits referenced from 0 to 23), the

TMROF_STS bit (PMBASE + 00h, bit 0) is set. The High-to-Low transition will occur

every 2.3435 seconds. If the TMROF_EN bit (PMBASE + 02h, bit 0) is set, an SCI

interrupt is also generated.

Bit Description

31:18 Reserved

Throttle Status (THTL_STS) — RO.

0 = No clock throttling is occurring (maximum processor performance).

1 = Indicates that the clock state machine is thr ottling the processor per formance. This

could be due to the THT_EN bit or the FORCE_THTL bit being set.

16:9 Reserved

Force Thermal Throttling (FORCE_THTL) — R/W. Software can set this bit to force

the thermal throttling function.

0 = No forced throttling.

1 = Th r ottling at the duty cycle speci f ied in THRM_DTY starts immediately, and no

SMI# is generated.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 509

LPC Interface Bridge Registers (D31:F0)

7:5

THRM_DTY — WO. This write-once field determines the duty cycle of the throttling

when the FORCE_THTL bit is set. The duty cycle indicates the approximate percentage

of time the STPCLK# signal is asserted while in the throttle mo de. The STPCLK#

throttle period is 1024 PCICLKs. Note that the throttling only occurs if the system is in

the C0 state. If in the C2, C3, or C4 state, no throttling occurs.

Once the THRM_DTY field is written, any subsequent writes will have no effect until

PLTRST# goes active.

THTL_EN — R/W. When set and the system is in a C0 state, it enables a processor-

controlled STPCLK# throttling. The duty cycle is selected in the THTL_DTY field.

0 = Disable

1 = Enable

3:1

THTL_DTY — R/W. This field determines the duty cycle of the throttling when the

THTL_EN bit is set. The duty cycle indicates the approximate percentage of time the

STPCLK# signal is asserted (low) while in the throttle mode. The STPCLK# throttle

period is 1024 PCICLKs.

0 Reserved

Bit Description

THRM_DTY Throttle Mode PCI Clocks

000b 50% (Default) 512

001b 87.5% 896

010b 75.0% 768

011b 62.5% 640

100b 50% 512

101b 37.5% 384

110b 25% 256

111b 12.5% 128

THTL_DTY Throttle Mode PCI Clocks

000b 50% (Default) 512

001b 87.5% 896

010b 75.0% 768

011b 62.5% 640

100b 50% 512

101b 37.5% 384

110b 25% 256

111b 12.5% 128

LPC Interface Bridge Registers (D31 :F 0)

510 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.3.6 LV2 — Level 2 Register

I/O Address: PMBASE + 14h

(ACPI P_BLK+4) Attribute: RO

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Core

NOTE: This register should not be used by IA-64 processors or systems with more than 1 logical

processor, unless appropriate semaphoring software has been put in place to ensure that

all threads/processors are ready for the C2 state when the read to this register occurs.

13.8.3.7 LV3—Level 3 Register (Mobile Only)

I/O Address: PMBASE + 15h (ACPI P_BLK + 5)

Attribute: RO

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Core

NOTE: If the C4onC3_EN bit is set, reads this register will initiate a LVL4 transition rather than a

LVL3 transition. In the event that software attempts to simultaneously read the LVL2 and

L VL3 registers (which is invalid), the ICH9 will ignore the L VL3 read, and only perform a C2

transition.

NOTE: This register should not be used by IA-64 processors or systems with more than 1 logical

processor, unless appropriate semaphoring software has been put in place to ensure that

all threads/processors are ready for the C3 state when the read to this register occurs.

13.8.3.8 LV4—Level 4 Register (Mobile Only)

I/O Address: PMBASE + 16h (ACPI P_BLK + 6)

Attribute: RO

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Core

NOTE: This register should not be used by IA-64 processors or systems with more than 1 logical

processor, unless appropriate semaphoring software has been put in place to ensure that

all threads/processors are ready for the C4 state when the read to this register occurs.

Bit Description

7:0

Reads to this register return all 0s, writes to this register have no effect. Reads to this

cause the STPCLK# signal to go active, and stay active until a break event occurs.

Throttling (due either to THTL_EN or FORCE_THTL) will be ignored.

Bit Description

7:0 Reads to this register return all 0s, writes to this register have no effect. Reads to this

persists until a break event occurs.

Bit Description

7:0 Reads to this register return all 0s, writes to this register have no effect. Reads to this

persists until a break event occurs.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 511

LPC Interface Bridge Registers (D31:F0)

13.8.3.9 LV5—Level 5 Register (Mobile Only)

I/O Address: PMBASE + 17h (ACPI P_BLK + 7)

Attribute: RO

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Core

NOTE: This register should not be used by IA-64 processors or systems with more than 1 logical

processor, unless appropriate semaphoring software has been put in place to ensure that

all threads/processors are ready for the C5 state when the read to this register occurs.

13.8.3.10 LV6—Level 6 Register (Mobile Only)

I/O Address: PMBASE + 18h (ACPI P_BLK + 8)

Attribute: RO

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Core

NOTE: This register should not be used by IA-64 processors or systems with more than 1 logical

processor, unless appropriate semaphoring software has been put in place to ensure that

all threads/processors are ready for the C6 state when the read to this register occurs.

Bit Description

7:0 Reads to this register return all 0s, writes to this register have no effect. Reads to this

persists until a break event occu rs.

Bit Description

7:0 Reads to this register return all 0s, writes to this register have no effect. Reads to this

persists until a break event occu rs.

LPC Interface Bridge Registers (D31 :F 0)

512 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.3.11 GPE0_STS—General Purpose Event 0 Status Register

I/O Address: PMBASE + 20h

(ACPI GPE0_BLK) Attribute: Bits 0:32 R/WC

Bits 33:63 RO

Default Value: 0000000000000000h Size: 64-bit

Lockable: No Usage: ACPI

Power Well: Resume

This register is symmetrical to the General Purpose Ev ent 0 Enab l e Register. Unless

indicated otherwise below, if the corresponding _EN bit is set, then when the _STS bit

get set, the ICH9 will generate a W ak e Event. Once back in an S0 state (or if already in

an S0 state when the event occurs), the ICH9 will also generate an SCI if the SCI_EN

bit is set, or an SMI# if the SCI_EN bit (PMBASE + 04h, bit 0) is not set. Bits 31:16 are

reset by a CF9h write; bits 63:32 and 15:0 are not. All are reset by RSMRST#.

Bit Description

63:33 Reserved.

USB6_STS — R/WC.

0 = Disable.

1 = Set by hardware and can be reset by writing a one to this bit position or a

resume well rese t. Th is bi t i s se t when USB UHCI con tr oll er #6 needs to cause a

wake. Additi onall y if the USB6 _EN bit is se t, the s etti ng of the USB6_ST S bit wi ll

generate a wake event.

31:16

GPIOn_STS — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = These bits are set any time the corresponding GPIO is set up as an input and the

corresponding GPIO signal is high (or low if the correspondin g GP_INV bit is s et).

If the corresponding enable bit is set in the GPE0_EN register, then when the

GPIO[n]_STS bit is set:

• If the system is in an S1–S5 state, the event will also wake the system.

• If the system is in an S0 state (or upon waking back to an S0 state), a SCI will be caused

depending on the GPIO_ROUT bits (D31:F0:B8h, bits 31:30) for the corresponding GPI.

NOTE: Mapping is as follows: bit 31 corresponds to GPIO[15]... and bit 16

corresponds to GPIO[0].

15 Reserved

USB4_STS — R/WC.

0 = Disable.

1 = Set by hardware and can be reset by writing a one to this bit position or a

resume well rese t. Th is bi t i s se t when USB UHCI con tr oll er #4 needs to cause a

wake. Additi onall y if the USB4 _EN bit is se t, the s etti ng of the USB4_ST S bit wi ll

generate a wake event.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 513

LPC Interface Bridge Registers (D31:F0)

PME_B0_STS — R/WC. This bit will be set to 1 by the ICH9 when any internal device

with PCI Power Management capabilities on bus 0 asserts the equivalent of the PME#

signal. Additionally, if the PME_B0_EN bit is set, and the system is in an S0 state,

then the setting of the PME_B0_STS bit will generate an SCI (or SMI# if SCI_EN is

not set). If the PM E_B0_STS bit is set, and the system is in an S1–S4 state (or S5

state due to SLP_TYP and SLP_EN), then the setting of the PME_B0_STS bit will

generate a wake event, and an SCI (or SMI# if SCI_EN is n ot se t) will be generated.

If the system is in an S5 state due to power button override, then the PME_B0_STS

bit will not cause a wake event or SCI.

The default for this bit is 0. Writing a 1 to this bit position clears this bit.

Note: HD audio wake events are reported in this bit.

Management Engine “maskable” wake events are also reported in this bit.

USB3_STS — R/WC.

0 = Disable.

1 = Set by hardware and can be reset by writing a one to this bit position or a

resume well reset. This bit is set when USB UHCI controller #3 needs to cause a

wake. Additional ly if th e USB3_ EN bi t is s et, the settin g of the USB3_STS bi t will

generate a wake event.

PME_STS — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = Set by hardware when the PME# signal goes active. Additionally, if the PME_EN

bit is set, and the system is in an S0 state, then the setting of the PME_STS bit

will generate an SCI or SMI# (if SCI_EN is not set). If the PME_EN bit is set, and

the system is in an S1–S4 state (or S5 state due to setting SLP_TYP and

SLP_EN), then the setting of the PME_STS bit wi ll gener ate a wak e event, and an

SCI will be generated. If the system is in an S5 state due to power button

override or a power failure, then PME_STS will not cause a wake event or SCI.

(Desktop

Only) Reserved

(Mobile

Only)

BATLOW_STS — R/WC. (Mobile Only) Software clears this bit by writing a 1 to it.

0 = BATLOW# Not asserted

1 = Set by hardware when the BATLOW# signal is asserted.

PCI_EXP_STS — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = Set by hardware to indicate that:

• The PME event message was received on one or more of the PCI Express* ports

• An Assert PMEGPE message received from the (G)MCH via DMI

NOTES:

1. The PCI WAKE# pin has no impact on this bit.

2. If the PCI_EXP_STS bit went active due to an Assert PMEGPE message, then a

Deassert PMEGPE message must be received prior to the software write in

order for the bit to be cleared.

3. If the bit is not cleared and the corresponding PCI_EXP_EN bit is set, the

level-triggered SCI will remain active.

4. A race condition exists where the PCI Express device sends another PME

message because the PCI Express device was not serviced within the time

when it must resend the message. This may result in a spurious interrupt,

and this is comprehended and approved by the PCI Express* Specification,

Revision 1.0a. The window for this race condition is approximately 95-105

milliseconds.

Bit Description

LPC Interface Bridge Registers (D31 :F 0)

514 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

8RI_STS — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = Set by hardware when the RI# input signal goes active.

SMBus Wake Status (SMB_WAK_STS) — R/WC. The SMBus con troll er can

independently cause an SMI# or SCI, so this bit does not need to do so (unlike the

other bits in this register). Software clears this bit by writing a 1 to it.

0 = Wake event Not caused by the ICH9’s SMBus logic.

1 = Set by hardware to indicate that the wake event was caused by the ICH9’s

SMBus logic.This bit will be set by the WAKE/SMI# command type, even if the

system is already awake. The SMI handler should then c lear this bit.

NOTES:

1. This bit is set by the SMBus slave command 01h (W ake/SMI#) even when the

system is in the S0 state. Therefore, to avoid an instant wake on subsequent

transitions to sleep states, software must clear this bit after each reception of

the Wake/SMI# command or just prior to entering the sleep state.

2. If SMB_WAK_STS is set due to SMBus slave receiving a message, it will be

cleared by internal logic when a THRMTRIP# event happens or a Power

Button Ove rride event. Ho wever, THRMTRIP# or Power Bu tton Override event

will not clear SMB_WAK_STS if it is set due to SMBALERT# signal going

active.

3. The SMBAL E RT_STS bit (D31:F3:I/ O Offset 00h:Bit 5) should be cleared by

software before the SMB_WAK_STS bit is cleared.

6TCOSCI_STS — R/WC. Software clears this bit by writing a 1 to it.

0 = TOC logic or thermal se nsor logic did Not cause SCI.

1 = Set by hardware when the TCO logic or thermal sensor logic causes an SCI.

USB5_STS— R/WC. Software clears this bit by writing a 1 to it.

0 = USB UHCI controller 5 does NOT need to cause a wake.

1 = Set by hardware when USB UHCI controller 5 needs to cause a wake. Wake event

will be generated if the corresponding USB2_EN bit is set.

USB2_STS — R/WC. Software clears this bit by writing a 1 to it.

0 = USB UHCI controller 2 does Not need to cause a wake.

1 = Set by hardware when USB UHCI controller 2 needs to c ause a wak e. W ake ev ent

will be generated if the corresponding USB2_EN bit is set.

USB1_STS — R/WC. Software clears this bit by writing a 1 to it.

0 = USB UHCI controller 1 does Not need to cause a wake.

1 = Set by hardware when USB UHCI controller 1 needs to c ause a wak e. W ake ev ent

will be generated if the corresponding USB1_EN bit is set.

2SWGPE_STS — R/WC.

The SWGPE_CTRL bit (bit 1 of GPE_CTRL reg) acts as a level input to this bit.

HOT_PLUG_STS — R/WC .

0 = Thi s bit is cleared by writing a 1 to this bit position.

1 = When a PCI Express* Hot-Plug event occurs. This will cause an SCI if the

HOT_PLUG_EN bit is set in the GEP0_EN register.

Thermal Interrupt Status (THRM_STS) — R/WC. Software clears this bit by

writing a 1 to it.

0 = THRM# signal Not driven active as defined by the THRM_POL bit

1 = Set by hardware anytime the THRM# signal is driven active as defined by the

THRM_POL bit. Additionally, if the THRM_EN bit is set, then the setting of the

THRM_STS bit will also generate a power management event (SCI or SMI#).

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 515

LPC Interface Bridge Registers (D31:F0)

13.8.3.12 G PE0_EN—General Purpose Event 0 Enables Register

I/O Address: PMBASE + 28h

(ACPI GPE0_BLK + 8) Attribute: Bits 0:32 R/W

Bits 33:63 RO

Default Value: 0000000000000000h Size : 64-bit

Lockable: No Usage: ACPI

Power Well: Bits 0–7, 9, 12, 14–63 Resume,

Bits 8, 10–11, 13 RTC

This register is symmetrical to the General Purpose Event 0 Status R egister. All the bits

in this register should be cleared to 0 based on a Power Button Override or processor

Thermal Trip event. The resume well bits are all cleared by RSMRST#. The RT C well bits

are cleared by RTCRST#.

Bit Description

63:33 Reserved.

USB6_EN — R/W.

0 = Disable.

1 = Enable the setting of the USB4_STS bit to generate a wake event. The

USB6_STS bit is set anytime USB UHCI controller #6 signals a wake event.

Break events are handled via the USB interrupt.

31:16

GPIn_EN — R/W. These bit s enable the corres ponding GPI[n]_STS bits being set to

cause a SCI, and/or wake even t. These bits are cleared by RSMRST#.

NOTE: Mapping is as follows: bit 31 corresponds to GPIO15... and bit 16

corresponds to GPIO0.

15 Reserved

USB4_EN — R/W.

0 = Disable.

1 = Enable the setting of the USB4_STS bit to generate a wake event. The

USB4_STS bit is set anytime USB UHCI controller #4 signals a wake event.

Break events are handled via the USB interrupt.

PME_B0_EN — R/W.

0 = Disable

1 = Enables the setting of the PME_B0_STS bit to generate a w ake event and/or an

SCI or SMI#. PME_B0_STS can be a wake event from the S1–S4 states, or from

S5 (if entered via SLP_TYP and SLP_EN) or power failure, but not Power Button

Override. This bit defaults to 0.

NOTE: It is only cleared by Software or RTCRST#. It is not cleared by CF9h writes.

USB3_EN — R/W.

0 = Disable.

1 = Enable the setting of the USB3_STS bit to generate a wake event. The

USB3_STS bit is set anytime USB UHCI controller #3 signals a wake event.

Break events are handled via the USB interrupt.

PME_EN — R/W.

0 = Disable.

1 = Enables the setting of the PME_STS to generate a wake event and/or an SCI.

PME# can be a wake event from the S1 – S4 state or from S5 (if entered via

SLP_EN, but not power button override).

(Desktop

Only) Reserved

LPC Interface Bridge Registers (D31 :F 0)

516 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

(Mobile

Only)

BATLOW_EN — R/W. (Mobile Only)

0 = Disable.

1 = Enables the BATLOW# signal to cause an SMI# or SCI (depending on the

SCI_EN bit) when it goes low. This bit does not prevent the BATLOW# signal

from inhibiting the wake event.

PCI_EXP_EN — R/W.

0 = Disable SCI generation upon PCI_EXP_STS bit being set.

1 = Enables ICH9 to cause an SCI when PCI_EXP_STS bit is set. This is used to

allow the PCI Express* ports, including the link to the (G)M CH, to cause an SCI

due to wake/PME events.

RI_EN — R/W. The value of this bit will be maintained through a G3 state and is not

affected by a hard reset caused by a CF9h write.

0 = Disable.

1 = Ena bles the setting of the R I_STS to generate a wake event.

7 Reserved

6TCOSCI_EN — R/W.

0 = Disable.

1 = Enables the setting of the TCOSCI_STS to generate an SCI.

5USB5_EN — R/W.

0 = Disable.

1 = Enables the setting of the USB5_STS to generate a wake event.

4USB2_EN — R/W.

0 = Disable.

1 = Enables the setting of the USB2_STS to generate a wake event.

3USB1_EN — R/W.

0 = Disable.

1 = Enables the setting of the USB1_STS to generate a wake event.

SWGPE_EN— R/W. This bit allows software to control the assertion of SWGPE_STS

bit. This bit This bit, when set to 1, enables the SW GPE function. If SWGPE_CTRL is

written to a 1, hardware will set SWGPE_STS (acts as a level input)

If SWGPE_STS, SWGPE_EN, and SCI_EN are all 1's, an SCI will be generated

If SWGPE_STS = 1, SWGPE_EN = 1, SCI_EN = 0, and GBL_SMI_EN = 1 then an

SMI# will be generated

HOT_PLUG_EN — R/W.

0 = Disables SCI generation upon the HOT_PLUG_STS bit being set.

1 = Enables the ICH9 to cause an SCI when the HOT_PLUG_STS bit is set. This is

used to allow the PCI Express ports to cause an SCI due to hot-plug events.

THRM_EN — R/W.

0 = Disable.

1 = Active assertion of the THRM# signal (as defined by the THRM_POL bit) will

generate a power management event (SCI or SMI) if the THRM_STS bit is also

set.

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 517

LPC Interface Bridge Registers (D31:F0)

13.8.3.13 SMI_EN—SMI Control and Enable Register

I/O Address: PMBASE + 30h Attribute: R/W, R/WO, WO

Default Value: 00000000h Size: 32 bit

Lockable: No Usage: ACPI or Legacy

Power Well: Core

Note: This register is symmetrical to the SMI status register.

Bit Description

31:28 Reserved

GPIO_UNLOCK_SMI_EN— R/WO. Setting this bit will cause the Intel ICH9 to

generate an SMI# when the GPIO_UNLOCK_SMI_STS bit is set in the SMI_STS

Once written to ‘1’, this bit can only be cleared by PLTRST#.

26:19 Reserved

18 INTEL_USB2_EN — R/W.

0 = Disable

1 = Enables Intel -Specific USB2 SMI logic to cause SMI#.

17 LEGACY_USB2_EN — R/W.

0 = Disable

1 = Enables legacy U S B2 logic to cause SMI#.

16:15 Reserved

PERIODIC_EN — R/W.

0 = Disable.

1 = Enables the ICH9 to generate an SMI# when the PERIODIC_STS bit (PMBASE +

34h, bit 14) is set in the SMI_STS register (PMBASE + 34h).

TCO_EN — R/W.

0 = Disables TCO logic generating an SMI#. Note that if the NMI2SMI_EN bit is set,

SMIs that are caused by re-routed NMIs will not be gated by the TCO_EN bit. Even

if the TCO_EN bit is 0, NMIs will still be routed to cause SMIs.

1 = Enables the TCO logic to generate SMI#.

NOTE: This bit cannot be written once the TCO_LOCK bit is se t.

12 Reserved

MCSMI_ENMi cr ocontroller SM I Ena b le (MCSMI_EN) — R/W.

0 = Disable.

1 = Enables ICH9 to trap accesses to the microcontroller range (62h or 66h) and

generate an SMI#. Note that “trapped’ cycles will be claimed by the ICH9 on PCI,

but not forwarded to LPC.

10:8 Reserved

BIOS Release (BIOS_RLS) — WO.

0 = This bit will always return 0 on reads. Writes of 0 to this bit have no effect.

1 = Enables the generation of an SCI interrupt for ACPI software when a one is written

to this bit position by BIOS software.

NOTE: GBL_STS being set will cause an SCI, even if the SCI_EN bit is not set.

Software must take great care not to set the BIOS_RLS bit (which causes

GBL_STS to be set) if the SCI handler is not in place.

LPC Interface Bridge Registers (D31 :F 0)

518 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Software SMI# Timer Enable (SWSMI_TMR_EN) — R/W.

0 = Disable. Clearing the SWSMI_TMR_EN bit before the timer expires will reset the

timer and the SMI# will not be generated.

1 = Starts Software SMI# Timer. When the SWSMI timer expires (the timeout period

depends upon the SWSMI_RATE_SEL bit setting), SWSMI_TMR_STS is set and an

SMI# is generated. SWSMI_TMR_EN stays set until cleared by software.

5APMC_EN — R/W.

0 = Disable. Writes to the APM_CNT register will not cause an SMI#.

1 = Enables writes to the APM_CNT register to cause an SMI#.

SLP_SMI_EN — R/W.

0 = Disables the generation of SMI# on SLP_EN. Note that this bit must be 0 before

the software attempts to transition the system into a sleep state by writin g a 1 to

the SLP_EN bit.

1 = A write of 1 to the SLP_EN bit (bit 13 in PM1_CNT register) will generate an SMI#,

and the system will not transition to the sleep stat e based on that write to the

SLP_EN bit.

3LEGACY_USB_EN — R/W.

0 = Disable.

1 = Enables legacy USB circuit to cause SM I#.

BIOS_EN — R/W.

0 = Disable.

1 = Enables the generation of SMI# when ACPI software writes a 1 to the GBL_RLS bit

(D31:F0:PMBase + 04h:bit 2). Note that if the BIOS_STS bit (D31:F0:PMBase +

34h:bit 2), which ge ts set when softw are writes 1 to GBL_RLS bit, is already a 1 at

the time that BIOS_EN beco mes 1, an SMI# will be generated when BIOS_EN gets

set.

End of SMI (EOS) — R/W (special). This bit controls the arbitration of the SMI signal

to the processor. This bit must be set for the ICH9 to assert SMI# low to the processor

after SMI# has been asserted previously.

0 = Once the ICH9 asserts SMI# low, the EOS bit is automatically cleared.

1 = When this bit is set to 1, SMI# signal wi ll be deasserted fo r 4 PCI clocks before its

assertion. In the SMI handler, the processor should clear all pending SMIs (by

servicing them and then clearing their respectiv e status bits), se t the EOS bi t, and

exit SMM. This will allow the SMI arbiter to re- assert SMI upon detection of an SMI

event and the setting of a SMI status bit.

NOTE: ICH9 is able to generate 1s t SMI after reset even though EOS bit is n ot set.

Subsequent SMI require EOS bit is set.

GBL_SMI_EN — R/W.

0 = No SMI# will be generated by ICH9. This bit is reset by a PCI reset event.

1 = Enabl es the generation of SMI# in the system upon any enabled SMI event.

NOTE: When the SMI_LOCK bit is set, this bit cannot be changed.

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 519

LPC Interface Bridge Registers (D31:F0)

13.8.3.14 SMI_STS—SMI Status Register

I/O Address: PMBASE + 34h A ttribute: RO, R/WC

Default Value: 00000000h Size: 32-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Core

Note: If the corresponding _EN bit is set when the _STS bit is set, the ICH9 will cause an

SMI# (except bits 8–10 and 12, which do not need enable bits since they are logic ORs

of other registers that have enable bits). The ICH9 uses the same GPE0_EN register (I/

O address: PMBase+2Ch) to enable/disable both SMI and ACPI SCI ge neral purpose

input events. ACPI OS assumes that it owns the entire GPE0_EN register per ACPI spec.

Problems arise when some of the general-purpose inputs are enabled as SMI by BIOS,

and some of the general purpose inputs are enabled for SCI. In this case ACPI OS turns

off the enabled bit for any GPIx inpu t sign als that are not indicated as SCI general-

purpose events at boot, and exit from sleeping states. BIOS should define a dummy

control method which prevents the ACPI OS from clearing the SMI GPE0_EN bits.

Bit Description

31:28 Reserved

27 GPIO_UNLOCK_SMI_STS — R/WC. This bit will be set if the GPIO registers lockdown

logic is requesting an SMI#. Writing a ‘1’ to this bit position clears this bit to ‘0’.

26 SPI_STS — RO. This bit will be set if the SPI logic is generating an SMI#. This bit is

read only because the sticky status and enable bits associated with this function are

located in the SPI registers.

25:22 Reserved

MONITOR_STS — RO. This bit will be set if the Trap/SMI logic has caused the SMI.

This will occur when the processor or a bus master accesses an assigned register (or a

sequence of accesses). See Section 10.1.43 through Section 10.1.49 for details on the

specific cause of the SMI.

20 PCI_EXP_SMI_STS — RO. PCI Express* SMI event occurred. This could be due to a

PCI Express PME event or Hot-Plug event.

19 Reserved

INTEL_USB2_STS — RO. This non-stic ky read-only bit is a logical OR of each of the

SMI status bits in the Intel-Specific USB2 SMI Status Register ANDed with the

corresponding enable bits. Additionally, the Port Disable W rite Enable SMI is reported in

this bit; the specific status bit for this event is contained in the USB Per-Port Registers

Write Control Register in this I/O space. This bit will not be active if the enable bits are

not set. Writes to this bit will have no effect.

All integrated USB2 Host Controllers are represented with this bit.

LEGACY_USB2_STS — RO. Thi s non- stic ky read- only bi t is a logi cal O R of e ach of the

SMI status bits in the USB2 Legacy Support Register ANDed with the corresponding

enable bits. This bit will not be active if the enable bits are not set. Writes to this bit will

have no effect.

All integrated USB2 Host Controllers are represented with this bit.

LPC Interface Bridge Registers (D31 :F 0)

520 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

SMBus SMI Status (SMBUS_SMI_S T S ) — R/WC. Software clears this bit by writing

a 1 to it.

0 = Thi s bit is set from the 64 kHz clock domain used by the SMBus. Software must

wait at least 15.63 μs after the initial assertion of this bit before clearing it.

1 = Indicates that the SM I# was caused by:

1. The SMBus Slave receiving a message that an SMI# should be caused, or

2. The SMBALERT# signal goes active and the SMB_SMI_EN bit is set and the

SMBALERT_DIS bit is cleared, or

3. The SMBus Slave recei ving a Host Notify mes sage and the

HOST_NOTIFY_INTREN and

the SMB_SMI_EN bits are set, or

4. The ICH9 detecting the SMLINK_SLAVE_SMI command while in the S0 state.

SERIRQ_SMI_STS — RO.

0 = SMI# was not caused by the SERIRQ decoder.

1 = Indicates that the SMI# was caused by the SERIRQ decoder.

NOTE: This is not a sticky bit

PERIODIC_STS — R/WC. Software clears this bit by writing a 1 to it.

0 = Software clears this bit by writing a 1 to it.

1 = This bit is set at the rate determined by the P E R_SMI_SEL bits. If the

PERIODIC_EN bit (PMBASE + 30h, bit 14) is also set, the ICH9 generates an SMI#.

TCO_STS — R/WC. Software clears this bit by writing a 1 to it.

0 = S MI# not caused by TCO logic.

1 = Indi cates the SMI# was caused by the TCO logic. Note that this is not a wake

event.

Device Monitor Status (DEVMON_STS) — RO.

0 = SMI# not caused by Device Monitor.

1 = Set if bit 0 of the DE VACT_STS regis ter (PMBASE + 44h) is se t. The bit is not stick y ,

so writes to this bit will have no effect.

Microcontroller SMI# Status (MCSMI_STS) — R/WC. Software clears this bit by

writing a 1 to it.

0 = Indicates that there has been no access to the power management microcontroller

range (62h or 66h).

1 = Set if there has been an access to the power management microcontroller range

(62h or 66h) and the Microcontroller Decode Enable #1 bit in the LPC Bridge I/O

Enables configuration register is 1 (D31:F0:Offset 82h:bit 11). Note that this

implementation assumes that the Microcontroller is on LPC. If this bit is set, and

the MCSMI_EN bit is also set, the ICH9 will generate an SMI#.

GPE0_STS — RO. This bit is a logical OR of the bits in the ALT_GP_SMI_STS register

that are also set up to cause an SMI# (as indicated by the GPI_ROUT registers) and

have the corresponding bit set in the ALT_GP_SMI_EN register. Bits that are not

routed to cause an SMI# will have no effect on this bit.

0 = SMI# was not generated by a GPI assertion.

1 = SMI# was generated by a GPI assertion.

GPE0_STS — RO. This bit is a logical OR of the bits 47:32, 14:10, 8, 6:2 and 0 in the

GPE0_STS register (PMBASE + 28h) that also have the corresponding bit set in the

GPE0_EN register (PMBASE + 2Ch).

0 = SMI# was not generated by a GPE0 event.

1 = SMI# was generated by a GPE0 event.

PM1_STS_REG — RO. This is an ORs of the bits in the ACPI PM1 Status Register

(offset PMBASE+00h) that can cause an SMI#.

0 = SMI# was not generated by a PM1_STS event.

1 = SMI# was generated by a PM1_STS event.

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 521

LPC Interface Bridge Registers (D31:F0)

13.8.3.15 ALT_GP_SMI_EN—Alternate GPI SMI Enable Register

I/O Address: PMBASE +38h Attribute: R/W

Default Value: 0000h Size: 16-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Resume

7 Reserved

6SWSMI_TMR_STS — R/WC. Software clears this bit by writing a 1 to it.

0 = Software SMI# Timer has Not expired.

1 = Set by the hardware when the Software SMI# Timer expires.

APM_STS — R/WC. Software clears this bit by writing a 1 to it.

0 = No SMI# generated by write access to APM Control register with APMCH_EN bit set.

1 = SMI # was gen erated by a write ac cess to the APM Control regist er with the

APMC_EN bit set.

SLP_SMI_STS — R/WC. Software clears this bit by writing a 1 to the bit location.

0 = No SMI# caused by write of 1 to SLP_EN bit when SLP_SMI_EN bit is also set.

1 = Indicates an SMI# was caused by a write of 1 to SLP_EN bit when SLP_SMI_EN bit

is also set.

LEGACY_USB_STS — RO. This bit is a logical OR of each of the SMI status bits in the

USB Legacy Keyboard/Mouse Control Registers ANDed with the corresponding enable

bits. This bit will not be active if the enable bits are not set.

0 = SMI# was not generated by USB Legacy event.

1 = SMI# was generated by USB Legacy event.

BIOS_STS — R/WC.

0 = No SMI# generated due to ACPI software requesting attention.

1 = This bit gets set by hardware when a 1 is written by software to the GBL_RLS bit

(D31:F0:PMBase + 04h:bit 2). When both the BIOS_EN bit (D31:F0:PMBase +

30h:bit 2) and the BIOS_STS bit are set, an SMI# will be generated. The

BIOS_STS bit is cleared when software writes a 1 to its bit position.

1:0 Reserved

Bit Description

15:0

Alternate GPI SMI Enable — R/W. These bits are used to enable the c orresponding

GPIO to cause an SMI#. For these bits to have any effect, the following must be true.

• The corresponding bit in the ALT_GP_SMI_EN register is set.

• The corresponding GPI must be routed in the GPI_ROUT register to cause an SMI.

• The corresponding GPIO must be implemented.

NOTE: Mapping is as follows: bit 15 corresponds to GPIO15... bit 0 corresponds to

GPIO0.

LPC Interface Bridge Registers (D31 :F 0)

522 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.3.16 ALT_GP_SMI_STS—Alternate GPI SMI Status Register

I/O Address: PMBASE +3Ah Attribute: R/WC

Default Value: 0000h Size: 16-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Resume

13.8.3.17 UPRWC—USB Per-Port Registers Write Control

I/O Address: PMBASE +3Ch Attribute: R/WC, R/W, R/WO

Default Value: 0000h Size: 16-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Resume

Bit Description

15:0

Alternate GPI SMI Status — R/WC. These bits report the status of the corres ponding

GPIOs.

0 = Inactive. Software clears this bit by writing a 1 to it.

1 = Active

These bits are sticky. If the foll owing conditions are true, then an SMI# will be

generated and the GPE0_STS bit set:

• The corresponding bit in the ALT_GPI_SMI_EN regis t er (PMBASE + 38h) is set

• The corresponding GPIO must be routed in the GPI_ROUT register to cause an SMI.

• The corresponding GPIO must be implemented.

All bits are in the resume well. Default for these bits is dependent on the state of the

GPIO pins.

Bit Description

15:9 Reserved

Write Enable Status — R/WC

0 = This bit gets set by hardware when the “Per-Port Registers Write Enable” bit is

written from 0 to 1

1 = This bit is cleared by software writing a 1b to this bit location

The setting condition takes precedence over t he clearing conditio n in the event that

both occur at once.

When this bit is 1b and bit 0 is 1b, the INTEL_USB2 _STS bit is set in th e SMI_STS

7:2 Reserved.

1 Reserved

Write Enable SMI Enable— R/WO

0 = Disable

1 = enables the generation of SMI when the Per-Port Registers Write Enable (bit 1) is

written from 0 to 1. Once written to 1b, this bit can not be cleared by software.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 523

LPC Interface Bridge Registers (D31:F0)

13.8.3.18 GPE_CNTL— General Purpose Control Register

I/O Address: PMBASE +42h Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI or Legacy

Power Well: Resume

13.8.3.19 DEVACT_STS — Device Activity Status Register

I/O Address: PMBASE +44h Attribute: R/WC

Default Value: 0000h Size: 16-bit

Lockable: No Usage: Legacy Only

Power Well: Core

Each bit indicates if an access has occurred to the corresponding device’ s trap range, or

for bits 6:9 if the corresponding PCI interrupt is active. This register is used in

conjunction with the P eriodic SMI# timer to detect any system activity for legacy power

management. The periodic SMI# timer indicates if it is the right time to read the

DEVACT_STS register (PMBASE + 44h).

Note: Software clears bits that are set in this register by writing a 1 to the bit position.

Bit Description

8:2 Reserved

SWGPE_CTRL— R/W. This bit allows software to control the assertion of SWGPE_STS

bit. This bit is used by hardw a re as th e le v e l i nput si gn al for the SWG PE_STS bit in the

GPE0_STS register. When SWGPE_CTRL is 1, SWGPE_STS will be set to 1, and writes to

SWGPE_STS with a value of 1 to

clear SWGPE_STS will result in SWGPE_STS being set back to 1 by hardware. When

SWGPE_CTRL is 0, writes to SWGPE_STS with a value of 1 will clear SWGPE_STS to 0.

THRM#_POL — R/W. This bit controls the polari ty of the THRM# pin nee ded to set the

THRM_STS bit.

0 = Low value on the THRM# signal will set the THRM_STS bit.

1 = HIGH value on the THRM# signal will set the THRM_STS bit.

Bit Description

15:13 Reserved

KBC_ACT_STS — R/WC. KBC (60/64h).

0 = Indicates that there has been no access to this device’s I/O range.

1 = This device’s I/O range has been accessed. Clear this bit by writing a 1 to the bit

location.

11:10 Reserved

PIRQDH_ACT_STS — R/WC. PIRQ[D or H].

0 = The corresponding PCI interrupts have not been active.

1 = At least one of the corresponding PCI interrupts has been active. Clear this bit by

writing a 1 to the bit loc a tion.

PIRQCG_ACT_STS — R/WC. PIRQ[C or G].

0 = The corresponding PCI interrupts have not been active.

1 = At least one of the corresponding PCI interrupts has been active. Clear this bit by

writing a 1 to the bit loc a tion.

LPC Interface Bridge Registers (D31 :F 0)

524 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.8.3.20 PM2_CNT—Power Management 2 Control (Mobile Only)

I/O Address: PMBASE + 50h

(ACPI PM2_CNT_BLK) Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Usage: ACPI

Power Well: Core

13.8.3.21 C3_RES— C3 Residency Register (Mobile Only)

I/O Address: PMBASE +54h Attribute: RO

Default Value 00000000h Size: 32-bit

Lockable: No Usage: ACPI/Legacy

Power Well: Core

Software may only write this register during system initialization to set the state of the

C3_RESIDENCY_MODE bit. It must not be written while the timer is in use.

PIRQBF_ACT_STS — R/WC. PIRQ[B or F].

0 = The corresponding PCI interrupts have not been active.

1 = At least o ne of the corresponding PCI interrupts has been active. Clear this bit by

writing a 1 to the bit location.

PIRQAE_ACT_STS — R/WC. PIRQ[A or E].

0 = The corresponding PCI interrupts have not been active.

1 = At least o ne of the corresponding PCI interrupts has been active. Clear this bit by

writing a 1 to the bit location.

5:0 Reserved

Bit Description

7:1 Reserved

Arbiter Disable (ARB_DIS) — R/W This bit is essentially just a scratchpad bit for

legacy software compatibility. Software typically sets this bit to 1 prior to entering a C3

or C4 state. When a transition to a C3 or C4 state occurs, ICH9 will automatically

prevent any internal or external non-Isoch bus masters from initiating any cycles up to

the (G)MCH. This blocking starts immediately upon the ICH9 sending the Go-C3

message to the (G)MCH. The blocking stops when the Ack-C2 message is received.

Note that this is not really blocking, in that messages (such as from PCI Express*) are

just queued and held pending.

Bit Description

31:24 Reserved

23:0

C3_RESIDENCY — RO. The value in this field increments at the same rate as the

Power Management Timer. This field increments whil e STP_CPU# is acti ve (i.e., the

processor is in a C3 or C4 state). This field will roll over in the same way as the PM

Timer, however the most significant bit is NOT sticky.

Software is responsible for reading this field before performing the Lvl3/4 transition.

Software must also check for rollover if the maximum time in C3/C4 could be

exceeded.

NOTE: Hardware reset is the only reset of this counter field.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 525

LPC Interface Bridge Registers (D31:F0)

13.8.3.22 C5_RES— C5 Residency Register (Mobile Only)

I/O Address: PMBASE +58h Attribute: RO

Default Value 00000000h Size: 32-bit

Lockable: No Usage: ACPI/Legacy

Power Well: Core

Bit Description

31:24 Reserved

23:0

C5_RESIDENCY — RO. The value in this field increments at the same rate as the

Power Management Timer. This field will roll over in the same way as the PM Timer,

however the most significant bit is NOT sticky.

Software is responsible for reading this field before performing the Lvl5 transition.

Software must also check for rollover if the maximum time in C5 could be exceeded.

NOTE: Hardware reset is the only reset of this counter field.

LPC Interface Bridge Registers (D31 :F 0)

526 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.9 System Management TCO Registers (D31:F0)

The TCO logic is accessed via registers mapped to the PCI configuration space (Device

31:Function 0) and the system I/O space. F or TCO PCI Configur ation registers, see LPC

Device 31:Function 0 PCI Configuration registers.

TCO Register I/O Map

The TCO I/O registers reside in a 32-byte range pointed to by a TCOBASE value, which

is, PMBASE + 60h in the PCI config space. The following table shows the mapping of

the registers within that 32-byte range. Each register is described in the following

sections.

13.9.1 TCO_RLD—TCO Timer Reload and Current Value Register

I/O Address: TCOBASE +00h Attribute: R/W

Default Value: 0000h Size: 16-bit

Lockable: No Power Well: Core

Table 13-12. TCO I/O Register Address Map

TCOBASE

+ Offset Mnemonic Register Name Default Type

00h–01h TCO_RLD TCO Timer Reload and Current

Value 0000h R/W

02h TCO_DAT_IN TCO Data In 00h R/W

03h TCO_DAT_OUT TCO Data Out 00h R/W

04h–05h TCO1_STS TCO1 Status 0000h R/WC, RO

06h–07h TCO2_STS TCO2 Status 0000h R/WC

08h–09h TCO1_CNT TCO1 Control 0000h R/W,

R/WLO, R/WC

0Ah–0Bh TCO2_CNT TCO2 Control 0008h R/W

0Ch–0Dh TCO_MESSAGE1,

TCO_MESSAGE2 TCO Message 1 and 2 00h R/W

0Eh TCO_WDCNT Watchdog Control 00h R/W

0Fh — Reserved — —

10h SW_IRQ_GEN Software IRQ Generation 03h R/W

11h — Reserved — —

12h–13h TCO_TMR TCO Timer Initial Value 0004h R/W

14h–1Fh — Reserved — —

Bit Description

15:10 Reserved

9:0 TCO Timer Value — R/W. Reading this register will return the current count of the TCO

timer. Writing any value to this register will reload the timer to prevent the timeout.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 527

LPC Interface Bridge Registers (D31:F0)

13.9.2 TCO_DAT_IN—TCO Data In Register

I/O Address: TCOBASE +02h Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Power Well: Core

13.9.3 TCO_DAT_OUT—TCO Data Out Register

I/O Address: TCOBASE +03h Attribute: R/W

Default Value: 00h Size: 8-bit

Lockable: No Power Well: Core

13.9.4 TCO1_STS—TCO1 Status Register

I/O Address: TCOBASE +04h Attribute: R/WC, RO

Default Value: 0000h Size: 16-bit

Lockable: No Power Well: Core

(Except bit 7, in RTC)

Bit Description

7:0 TCO Data In Value — R/W. This data register field is used for passing commands from

the OS to the SMI handler. Writes to this register will cause an SMI and set the

SW_TCO_SMI bit in the TCO1_STS register (D31:F0:04h).

Bit Description

7:0

TCO Data Out Value — R/W. This data register field is used for passing commands

from the SMI handl er to the OS. W rites to this regis ter will set the T C O_INT_STS bit in

the TCO_STS register. It will also cause an interrupt, as selected by the TCO_INT_SEL

bits.

Bit Description

15:13 Reserved

DMISERR_STS — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = ICH9 received a DMI special cycle message via DMI indicating that it wants to

cause an SERR#. The software must read the (G)MCH to determine the reason for

the SERR#.

11 Reserved

DMISMI_STS — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = ICH9 received a DMI special cycle message via DMI indicating that it wants to

cause an SMI. The software must read the (G)MCH to determine the reason for the

SMI.

DMISCI_STS — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = ICH9 received a DMI special cycle message via DMI indicating that it wants to

cause an SCI. The software must read the (G)MCH to determine the reason for the

SCI.

LPC Interface Bridge Registers (D31 :F 0)

528 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

BIOSWR_STS — R/WC.

0 = Software clears this bit by writin g a 1 to it.

1 = ICH9 sets this bit and generates and SMI# t o indicate an inv alid attempt to write to

the BIOS. This occurs when either:

a) The BIOSWP bit is changed from 0 to 1 and the BLD bit is also set, or

b) any write is attempted to the BIOS and the BIOSWP bit is also set.

NOTE: On write cycles att empted to the 4 MB lower alias to the BIOS space, the

BIOSWR_STS will not be set.

NEWCENTURY_STS — R/WC. This bit is in the RTC well.

0 = Cleared by writing a 1 to the bit position or by RTCRST# going active.

1 = This bit is set when the Year byte (RT C I/O s pace, index offset 09h ) roll s o v er from

99 to 00. Setting this bit will cause an SMI# (but not a wake event).

NOTE: The NEWCENTURY_STS bit is not valid when the R TC battery is first installed (or

when RTC power has not been maintained). Software can determine if RTC

power has not been maintained by checking the RTC_PWR_STS bit

(D31:F0:A4h, bit 2), or by other means (such as a checksum on RTC RAM). If

RTC power is determined to have not been maintained, BIOS should set the

time to a valid value and then clear the NEWCENTURY_STS bit.

The NEWCENTURY_STS bit may tak e up to 3 RT C clocks for the bit to be cleared after a

1 is written to the bit to clear i t. After writing a 1 to this bit, softw are should not exit the

SMI handler until verifying that the bit has actually been cleared. This will ensure that

the SMI is not re-entered.

6:4 Reserved

3TIMEOUT — R/WC.

0 = Software clears this bit by writin g a 1 to it.

1 = Set by ICH9 to indicate that the SMI was caused by the TCO timer reaching 0.

TCO_INT_STS — R/WC.

0 = Software clears this bit by writin g a 1 to it.

1 = SMI handler caused the interrupt by writing to the TCO_DAT_OUT register

(TCOBASE + 03h).

SW_TCO_SMI — R/WC.

0 = Software clears this bit by writin g a 1 to it.

1 = Software caused an SMI# by writing to the TCO_DAT_IN register (TCOBASE +

02h).

NMI2SMI_STS — RO.

0 = Cleared by clearing the associated NMI status bit.

1 = Set by the ICH9 when an SMI# occurs because an event occurred that would

otherwise have caused an NMI (because NMI2SMI_EN is set).

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 529

LPC Interface Bridge Registers (D31:F0)

13.9.5 TCO2_STS—TCO2 Status Register

I/O Address: TCOBASE +06h Attribute: R/WC

Default Value: 0000h Size: 16-bit

Lockable: No Power Well: Resume

(Except Bit 0, in RTC)

Bit Description

15:8 Reserved

7ME Host Reset Warm Status (ME_ HRST_WARM_STS) — R/WC. This bit is set

when the Management Engine generates a Host reset without powe r cycling. Software

clears this bit by writing a 1 to this bit position.

6ME Host Reset Cold Stat u s (ME_ HRST_COLD_STS) — R/WC. This bit is set when

the Management Engine generates a Host reset with power cycling. Software clears this

bit by writing a 1 to this bit position.

ME WAKE STATUS (ME_WAKE_STS) — R/WC. This bit is set when the Management

Engine generates a Non-Maskable wake ev ent, and is not affected by any other enable

bit. When this bit is set, the Host Power Management logic wakes to S0.

This bit is only set by hardware and can only be reset by writing a one to this bit

position. This bit is not affected by hard resets caused by a CF9h write, but is reset by

RSMRST.

SMLink Slave SMI Status (SMLINK_SLV_SMI_STS) — R/WC. Allow the software to

go directly into pre-determined sleep state. This av oids r ace conditions. Softw are clears

this bit by writing a 1 to it.

0 = The bit is reset by RSMRST#, but not due to the PCI Reset associated with exit

from S3–S5 states.

1 = ICH9 sets this bit to 1 when it receives the SMI message on the SMLink's Slave

Interface.

3 Reserved.

BOOT_STS — R/WC.

0 = Cleared by ICH9 based on RSMRST# or by software writing a 1 to this bit. Note

that software should first clear the SECOND_T O_ST S bit before writing a 1 to clear

the BOOT_STS bit.

1 = Set to 1 when the SECOND_TO_STS bit go es from 0 to 1 and the processor has not

fetched the first instruction.

If rebooting due to a second TCO timer timeout, and if the BOOT_STS bit is set, the

ICH9 will reboot using t he ‘safe’ multiplier (1111). This allows the system to recover

from a processor frequency multiplier that is too high, and allows the BIOS to check the

BOOT_STS bit at boot. If the bit is set and the frequency multiplier is 1111, then the

BIOS knows that th e pro cessor has been programmed to an invalid multiplier.

SECOND_TO_STS — R/WC.

0 = Software clears this bit by writing a 1 to it, or by a RSMRST#.

1 = ICH9 sets this bit to 1 to indicate that the TIMEOUT bit had been (or is currently)

set and a second timeout occurred before the TCO_RLD regi ster was written. If this

bit is set and the NO_REBOOT config bit is 0, then the ICH9 will reboot the system

after the second timeout. The reboot is done by asserting PLTRST#.

LPC Interface Bridge Registers (D31 :F 0)

530 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Intruder Detect (INTRD_DET) — R/WC.

0 = Software clears this bit by writing a 1 to it, or by RTCRST# assertion.

1 = Set by ICH9 to indicate that an intrusion was detected. This bit is set even if the

system is in G3 state.

NOTES:

1. This bit has a recovery time. After writing a 1 to this bit position (to clear it), the bit

may be read back as a 1 for up 65 microseconds before it is read as a 0. Software

must be aware of this recovery time when reading this bit after clearing it.

2. If the INTRUDER# signal is active when the software attempts to clear the

INTRD_DET bit, the bit will remain as a 1, and the SMI# will be generated again

immediately. The SMI ha ndler can clear the INTRD_SEL bits (TCOBASE + 0Ah, bits

2:1), to avoid further SMIs. However, if the INTRUDER# signals goes inactive and

then active again, there will not be further SMI’s (because the INTRD_SEL bits

would select that no SMI# be generated).

3. If the INTRUDER# signal goes inactive some point after the INTRD_DET bit is

written as a 1, then the INTRD_DET signal will go to a 0 when INTRUDER# input

signal goes inactive. Note that this is slightly different than a classic sticky bit, since

most sticky bits would remain active indefinitely when the signal goes active and

would immediately go inactive when a 1 is written to the bit

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 531

LPC Interface Bridge Registers (D31:F0)

13.9.6 TCO1_CNT—TCO1 Control Register

I/O Address: TCOBASE +08h Attribute: R/W, R/WL O, R/WC

Default Value: 0000h Size: 16-bit

Lockable: No Power Well: Core

Bit Description

15:13 Reserved

TCO_LOCK — R/WLO. When set to 1, this bit prevents writes from changing the

TCO_EN bit (in offset 30h of Power Management I/O space). Once this bit is set to 1, it

can not be cleared by software writing a 0 to this bit location. A core-well reset is

required to change this bit from 1 to 0. This bit defaults to 0.

TCO Timer Halt (TCO_TMR_HLT) — R/W.

0 = The TCO Timer is enabled to count.

1 = The TCO Timer will halt. It will not count, and thus cannot reach a value that will

cause an SMI# or set the SECOND_TO_STS bit. When set, this bit will prevent

rebooting and prevent Alert On LAN event messages from being transmitted on the

SMLINK (but not Alert On LAN* heartbeat me ssages).

10 Reserved

NMI2SMI_EN — R/W.

0 = Normal NMI functionality.

1 = Forces all NMIs to instead cause SMIs. The functionality of this bit is dependent

upon the se ttings of the NMI_EN bit and the GBL_ SMI_EN bit as detailed in the

following table:

NMI_NOW — R/WC.

0 = Software clears this bit by writing a 1 to it. The NMI handler is expected to clear

this bit. Another NMI will not be generated until the bit is cleared.

1 = W riting a 1 to thi s bit c auses an N MI. This al lows the B IOS or SMI handler t o force

an entry to the NMI handler.

7:0 Reserved

NMI_EN GBL_SMI_EN Description

0b 0b No SMI# at all because GBL_SMI_EN = 0

0b 1b SMI# will be caused due to NMI events

1b 0b No SMI# at all because GBL_SMI_EN = 0

1b 1b No SMI# due to NMI because NMI_EN = 1

LPC Interface Bridge Registers (D31 :F 0)

532 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.9.7 TCO2_CNT—TCO2 Control Register

I/O Address: TCOBASE +0Ah Attribute: R/W

Default Value: 0008h Size: 16-bit

Lockable: No Power Well: Resume

13.9.8 TCO_MESSAGE1 and TCO_MESSAGE2 Registers

I/O Address: TCOBASE +0Ch (Message 1)Attribute: R/W

TCOBASE +0Dh (Message 2)

Default Value: 00h Size: 8-bit

Lockable: No Power Well: Resume

Bit Description

15:6 Reserved

5:4

OS_POLICY — R/W. OS-based software writes to these bits to select the policy that

the BIOS will use after the platform resets due the WDT. The following convention is

recommended for the BIOS and OS:

00 = Boot normally

01 = Shut down

10 = Don’t load OS. Hold in pre-boot state and use LAN to determine next step

11 = Reserved

NOTE: These are just scratchpad bits. They should not be reset when the TCO logic

resets the platform due to Watchdog Timer.

GPIO11_ALERT_DISABLE — R/W. At reset (via RSMRST# asserted) this bit is set

and GPIO[11] alerts are disabled.

0 = Enable.

1 = Disable GPIO11/SMBALERT# as an alert source for the heartbeats and the SMBus

slave.

2:1

INTRD_SEL — R/W. This field selects the action to take if the INTRUDER# signal goes

active.

00 = No interrupt or SMI#

01 = Interrupt (as selected by TCO_INT_SEL).

10 = SMI

11 = Reserved

0Reserved

Bit Description

7:0 TCO_MESSAGE[n] — R/W. BIOS can write into these registers to indicate its boot

progress. The external microc ontroller can read these registers to monitor the boot

progress

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 533

LPC Interface Bridge Registers (D31:F0)

13.9.9 TCO_WDCNT—TCO Watchdog Control Register

Offset Address: TCOBASE + 0Eh Attribute: R/W

Default Value: 00h Size: 8 bits

Power Well: Resume

13.9.10 SW_IRQ_GEN—Software IRQ Generation Register

Offset Address: TCOBASE + 10h Attribute: R/W

Default Value: 03h Size: 8 bits

Power Well: Core

13.9.11 TCO_TMR—TCO Timer Initial Value Register

I/O Address: TCOBASE +12h Attribute: R/W

Default Value: 0004h Size: 16-bit

Lockable: No Power Well: Core

Bit Description

7:0

The BIOS or system management software can write into this register to indicate more

details on the boot progress. The register will reset to 00h based on a RSMRST# (but

not PLTRST #). The external microco ntroller can read this register to monitor boot

progress.

Bit Description

7:2 Reserved

1IRQ12_CAUSE — R/W. When software sets this bit to 1, IRQ12 will be asserted. When

software sets this bit to 0, IRQ12 will be deasserted.

0IRQ1_CAUSE — R/W. When software sets this bit to 1, IRQ1 will be asserted. When

software sets this bit to 0, IRQ1 will be deasserted.

Bit Description

15:10 Reserved

9:0

TCO Timer Initial Value — R/W. Value that is loaded into the timer each time the

TCO_RLD register is written. Values of 0000h or 0001h will be ignored and should not

be attempted. The timer is clocked at approximately 0.6 seconds, and thus allows

timeouts ranging from 1.2 second to 613.8 seconds. Note: The timer has an error of

±1 tick (0.6s).

The TCO Timer will only count down in the S0 state.

LPC Interface Bridge Registers (D31 :F 0)

534 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.10 General Purpose I/O Registers (D31:F0)

The control for the general purpose I/O signals is handled through a separate 64-byte

I/O space. The base offset for this space is selected by the GPIOBASE register.

Table 13-13. Registers to Control GPIO Address Map

GPIOBASE

+ Offset Mnemonic Register Name Default Access

00h–03h GPIO_USE_SEL GPIO Use Select

197F75FFh

(Desktop) /

187E75FFh

(Mobile)

R/W

04h–07h GP_IO_SEL GPIO Input/Output Select

E0EA6FFFh

(desktop) /

E1EA6FFFh

(mobile)

R/W

08h–0Bh — Reserved — —

0Ch–0Fh GP_LVL GPIO Level for Input or

Output

E2FEEFFFh

(Desktop) /

E3DEEFFFh

(Mobile)

R/W

10h–13h — Reserved — —

14h–17h — Reserved — —

18h–1Bh GPO_BLINK GPIO Blink Enable 00040000h R/W

1Ch–1Fh GP_SER_BLINK[31:0] GP Serial Blink [31:0] 00000000h R/W

20–23h GP_SB_CMDSTS[31:0] GP Serial Blink Command

Status [31:0] 00080000h R/W

24–27h GP_SB_DATA[31:0] GP Serial Blink Data [31:0] 00000000h R/W

28–2Bh Reserved

2C–2Fh GPI_INV GPIO Signal Invert 00000000h R/W

30h–33h GPIO_USE_SEL2 GPIO Use Select 2 [60:32]

070300FFh

(Desktop) /

070300FEh

(Mobile)

R/W

34h–37h GP_IO_SEL2 GPIO Input/Output Se lect 2

[60:32] 1B55FFF0h R/W

38h–3Bh GP_LVL2 GPIO Level for Input or

Output 2 [60:32]

1FFEFFF3h

(Desktop) /

0EFFFFF3h

(Mobile)

R/W

3Ch–3Fh — Reserved — —

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 535

LPC Interface Bridge Registers (D31:F0)

13.10.1 GPIO_USE_SEL—GPIO Use Select Register [31:0]

Offset Address: GPIOBASE + 00h Attribute: R/W

Default Value: 197F75FFh (Desktop) Size: 32-bit

187E75FFh (Mobile)

Lockable: Yes Power Well: Core for 0:7 , 16:2 3,

Resume for 8:15, 24:31

13.10.2 GP_IO_SEL—GPIO Input/Output Select Register [31:0]

Offset Address: GPIOBASE +04h Attribute: R/W

Default Value: E0EA6FFFh (Desktop) S ize: 32-bit

E1EA6FFFh (Mobile)

Lockable: Yes Power Well: Core for 0:7 , 16:2 3,

Resume for 8:15, 24:31

Bit Description

31:0

GPIO_USE_SEL[31:0] — R/W. Each bit in this register enables the corresponding

GPIO (if it exists) to be used as a GPIO, rather than for the native func tion.

0 = Signal used as native func tion.

1 = Signal used as a GPIO.

NOTES:

1. The following bits are always 1 because they are always unMultiplexed: 8, 12,

13, 17, 18, 20, 27 and 28. The following bit s are always 1 in mobile : 1, 6, 7, 17.

2. If GPIO[n] do es not exist, then, the n-bit in this register will always read as 0

and writes will hav e no effec t. The fol lowing bits are alw ays 0 in mobile: 1 5 and

25.

3. After a full reset (RSMRST#) all multiplexed signals in the resume and core

wells are configured as th eir default function. After only a PLTRST#, the GPIOs

in the core well are configured as their default function.

4. When configured to GPIO mode, the muxing logic will present the inactive state

to native logic that uses the pin as an input.

5. All GPIOs are reset to the default state by CF9h rese t except GPIO24.

6. Bit 26 may be overridden by bit 8 in the GEN_PMCON_3 Register.

7. If the GPIO use is configured by an SPI soft strap the corresponding bit in this

Bit Description

31:0

GP_IO_SEL[31:0] — R/W.

When configured in native mode (GPIO_USE_SEL[n] is 0), writes to these bits have

no effect. The value reported in this register is undefined when programmed as

native mode.

0 = Output. The corresponding GPIO signal is an output.

1 = Input. The corresponding GPIO signal is an input.

LPC Interface Bridge Registers (D31 :F 0)

536 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.10.3 GP_LVL—GPIO Level for Input or Output Register [31:0]

Offset Address: GPIOBASE +0Ch Attribute: R/W

Default Value: E2FEEFFFh (Desktop) Size: 32-bit

E3DEEFFFh (Mobile)

Lockable: Yes Power Well: Core for 0:7, 16:23,

Resume for 8:15, 24:31

13.10.4 GPO_BLINK—GPO Blink Enable Register [31:0]

Offset Address: GPIOBASE +18h Attribute: R/W

Default Value: 00040000h Size: 32-bit

Lockable: No Power Well: Core for 0:7, 16:23,

Resume for 8:15, 24:31

NOTE: GPIO18 will blink by default immediately after reset. This signal could be connected to an

LED to indicate a failed boot (by programming BIOS to clear GP_BLINK18 after successful

POST).

Bit Description

31:0

GP_LVL[31:0]— R/W.

If GPIO[n] is programmed to be an output (via the corresponding bit in the

GP_IO_SEL regist er), then the corresponding GP_LVL[n] bit can be updated by

software to drive a high or low value on the output pin. 1 = high, 0 = low.

If GPIO[n] is progr ammed as an input, then the corresp onding GP_L VL bit reflects the

state of the input signal (1 = high, 0 = low.) and writes will have no effect.

When configured in native mode (GPIO_USE_SEL[n] is 0), writes to these bits have

no effect. The value reported in this register is undefined when programmed as

native mode.

Bit Description

31:0

GP_BLINK[31:0] — R/W. The setting of this bit has no effect i f the corresponding

GPIO signal is programmed as an input.

0 = The corresponding GPIO will function normally.

1 = If the corresponding GPIO is programmed as an output, the output signal will

blink at a rate of approximately once per second. The high and low times have

approximately 0.5 seconds each. The GP_LVL bit is not altered when this bit is

set.

The value of the corresponding GP_LVL bit remains unchanged during the blink

process, and does not effect the blink in any way. The GP_LVL bit is not altered

when programmed to blink. It will remain at its previous value.

These bits correspond to GPIO in th e Resume well. These bits revert to the default

value based on RSMRST# or a write to the CF9h register (but not just on

PLTRST#).

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 537

LPC Interface Bridge Registers (D31:F0)

13.10.5 GP_SER_BLINK[31:0]—GP Serial Blink [31:0]

Offset Address: GPIOBASE +1Ch Attribute: R/W

Default Value: 00000000h Size: 32-bit

Lockable: No Power Well: Core for 0:7, 16:23,

Resume for 8:15, 24:31

Bit Description

31:0

GP_SER_BLINK[31:0] — R/W. The setting of this bit has no effect if the

corresponding GPIO is programmed as an input or if the corresponding GPIO has

the GPO_BLINK bit set.

When set to a ‘0’, the corresponding GPIO will function normally.

When using serial blink, this bit should be set to a 1 while the corresponding

GP_IO_SEL bit is set to 1. Setting the GP_IO_SEL bit to 0 after the GP_SER_BLINK

bit ensures ICH will not drive a 1 on the pin as an output. When this corresponding

bit is set to a 1 and the pin is configured to output mode, the serial blink capability

is enabled. The ICH wi ll serialize messages through an open-drain buffer

configuration.

The value of the corresponding GP_L VL bit remains unchanged and does not impact

the serial blink capability in any way.

Writes to this register have no effect when the corresponding pin is configured in

native mode and the read value returned is undefined.

LPC Interface Bridge Registers (D31 :F 0)

538 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.10.6 GP_SB_CMDSTS[31:0]—GP Serial Blink Command Status

[31:0]

Offset Address: GPIOBASE +20h Attribute: R/W, RO

Default Value: 00080000h Size: 32-bit

Lockable: No Power Well: Core

13.10.7 GP_SB_DATA[31:0]—GP Serial Blink Data [31:0]

Offset Address: GPIOBASE +24h Attribute: R/W

Default Value: 00000000h Size: 32-bit

Lockable: No Power Well: Core

Bit Description

31:24 Reserved

23:22

Data Length Select (DLS) — R/W. This field determines the number of bytes to

serialize on GPIO

00 = Serialize bits 7:0 of GP_SB_DATA (1 byte)

01 = Serialize bits 15:0 of GP_SB_DATA (2 bytes)

10 = Undefined - Software must not write this value

11 = Serialize bits 31:0 of GP_SB_DATA (4 bytes)

Software should not modify the value in this register unless the Busy bit is clear.

Writes to this register have no effect when the corresponding pin is configured in

native mode and the read value returned is undefined.

21:16

Data Rate Select (DRS) — R/W. This field selects the number of 120ns time

intervals to count between Manchester data transitions. The default of 8h results in

a 960ns minimum time between transitions. A value of 0h in this register produces

undefined behavior.

Software should not modify the value in this register unless the Busy bit is clear.

15:9 Reserved

8Busy — RO. This read-only status bit is the hardware indication that a serialization

is in progress. Hardware sets this bit to 1 based on the Go bit being set. Hardware

clears this bit when the Go bit is cleared by the hardware.

7:1 Reserved

Go — R/W. This bit is s e t to 1 by s oftware to start the serialization process.

Hardware clears the bit after the serialized data is sent. Writes of 0 to this regis ter

have no effect. Software should not write this bit to 1 unless the Busy status bit is

cleared.

Bit Description

31:0 GP_SB_DATA[31:0] — R/W. This register contains the data serialized out. The

number of bits shifted out are selected through the DLS field in the GP_SB_CMDSTS

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 539

LPC Interface Bridge Registers (D31:F0)

13.10.8 GPI_INV—GPIO Signal Invert Register [31:0]

Offset Address: GPIOBASE +2Ch Attribute: R/W

Default Value: 00000000h Size: 32-bit

Lockable: No Power Well: CPU I/O for 17, Core for

16, 7:0

13.10.9 GPIO_USE_SEL2—GPIO Use Select 2 Register [60:32]

Offset Address: GPIOBASE +30h Attribute: R/W

Default Value: 070300FFh (Desktop) Size: 32-bit

070300FEh (Mobile)

Lockable: Yes Power Well: Core for 0:7 , 16:2 3,

Resume for 8:15, 24:31

Bit Description

31:0

Input Inversion (GP_INV[n]) — R/W. This bit only has effect if the corresponding

GPIO is used as an input and used by the GPE logic, where the polarity matters. When

set to ‘1’, then the GPI is inverted as it is sent to the GPE logic that is using it. This bit

has no effect on the value that is reported in the GP_LVL register.

These bits are used to allow both active-low and active-high inputs to cause SMI# or

SCI. Note that in the S0 or S1 state, the input signal must be active for at least two PCI

clocks to ensure detection by the ICH9. In the S3, S4 or S5 states the input signal must

be active for at least 2 RTC clocks to ensure detection. The setting of these bits has no

effect if the corresponding GPIO is pro grammed as an output. These bits correspond to

GPI that are in the resume well, an d will be reset to their default v alues by RSMRST# or

by a write to the CF9h register.

0 = The corresponding GPI_STS bit is se t when the ICH9 dete cts the state of the in put

pin to be high.

1 = The corresponding GPI_STS bit is se t when the ICH9 dete cts the state of the in put

pin to be low.

Bit Description

31:29 Always 0. No corresponding GPIO.

28:0

GPIO_USE_SEL2[60:32]— R/W. Each bit in this register enables the corresponding

GPIO (if it exists) to be used as a GPIO, rather than for the native function.

0 = Signal used as native function.

1 = Signal used as a GPIO.

NOTES:

1. The following bit is always 1 because it is always unMultiplexed: 17. The

following bits are unMultiplexed in desktop and are also 1: 0, 1, 2, 24 and 26.

2. If GPIO[n] does not exist, then, the (n-32) bit in this register wil l always read as

0 and writes will hav e no effect. The foll owing bits are alw ays 0: 29, 30 and 31.

The following bit is also not used in mobile and is always 0: 0.

3. After a full reset RSMRST# all multiplexed signals in the resume and core wells

are config ured as the ir defa ult function. After only a PLTRST#, the GPIOs in the

core well are configured as their default function.

4. When configured to GPIO mode, the muxing logic will present th e inactiv e state

to native logic that uses the pin as an input.

5. Bit 26 is ignored, functionality is configured by bits 9:8 of FLMAP0 register.

This register corresponds to GPIO[60:32]. Bit 0 corresponds to GPIO32 and bit 28

corresponds to GPIO60.

LPC Interface Bridge Registers (D31 :F 0)

540 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

13.10.10 GP_IO_SEL2—GPIO Input/Output Select 2 Register

[60:32]

Offset Address: GPIOBASE +34h Attribute: R/W

Default Value: 1B55FFF0h Size: 32-bit

Lockable: Yes Power Well: Core for 0:7, 16:23,

Resume for 8:15, 24:31

13.10.11 GP_LVL2—GPIO Level for Input or Output 2 Register

[63:32]

Offset Address: GPIOBASE +38h Attribute: R/W

Default Value: 1FFEFFF3h (Desktop) Size: 32-bit

0EFFFFF3h (Mobile)

Lockable: Yes Power Well: Core for 0:7, 16:23,

Resume for 8:15, 24:31

§ §

Bit Description

31:29 Always 0. No corresponding GPIO.

28:0

GP_IO_SEL2[60:32] — R/W.

0 = GPIO signal is programmed as an output.

1 = Corresponding GPIO signal (if enabled in the GPIO_USE_SEL2 register) is

programmed as an input.

This register corresponds to GPIO[60:32]. Bit 0 corresponds to GPIO32.

Bit Description

31:29 Reserved. Read-only 0

28:0

GP_LVL[60:32] — R/W.

If GPIO[n] is programmed to be an output (via the corresponding bit in the GP_IO_SEL

high or low value on the output pin. 1 = high, 0 = low.

If GPIO[n] is programmed as an input, then the corresponding GP_LVL bit reflects the

state of the input signal (1 = high, 0 = low.) and writes will have no effect.

When configured in native mode (GPIO_USE_SEL[n] is 0), writes to these bits have no

effect. The value reported in this register is undefined when programmed as native

mode.

This register corresponds to GPIO[60:32]. Bit 0 corresponds to GPIO32.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 541

SATA Controller Registers (D31:F2)

14 SATA Controller Registers

(D31:F2)

14.1 PCI Configuration Registers (SATA–D31:F2)

Note: Address locations that are not shown should be treated as Reserved.

All of the SATA registers are in the core well. None of the registers can be locked.

Table 14-1. SATA Controller PCI Register Address Map (S ATA–D31:F2) (Sheet 1 of 2)

Offset Mnemonic Register Name Default Type

00h–01h VID Vendor Identific ati on 8086h RO

02h–03h DID Device Identification See register

description RO

04h–05h PCICMD PCI Command 0000h R/W, RO

06h–07h PCISTS PCI Status 02B0h R/WC, RO

08h RID Revision Identification See register

description RO

09h PI Programming Interface See re gister

description

See

description

0Ah SCC Sub Class Code See register

description

See

description

0Bh BCC Base Class Code 01h RO

0Dh PMLT Primary Master Latency Timer 00h RO

0Eh HTYPE Header Type 00h RO

10h–13h PCMD_BAR Primary Command Block Base Address 00000001h R/W, RO

14h–17h PCNL_BAR Primary Control Block Base Address 00000001h R/W, RO

18h–1Bh SCMD_BAR Secondary Command Block Base

Address 00000001h R/W, RO

1Ch–1Fh SCNL_BAR Secondary Control Block Base Address 00000001h R/W, RO

20h–23h BAR Legacy Bus Master Base Address 00000001h R/W, RO

24h–27h ABAR /

SIDPBA AHCI Base Address / SATA Index Data

Pair Base Address See register

description

See

description

2Ch–2Dh SVID Subsystem Vendor Identification 0000h R/WO

2Eh–2Fh SID Subsystem Identification 0000h R/WO

34h CAP Capabilities Pointer 80h RO

3Ch INT_LN Interrupt Line 00h R/W

3Dh INT_PN Interrupt Pin See register

description RO

40h-41h IDE_TIM Primary IDE Timing Register 0000h R/W

42h-43h IDE_TIM Secondary IDE Timing Register 0000h R/W

SATA Controller Registers (D31:F2)

542 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE: The ICH9 SATA controller is not arbitrated as a PCI device, therefore it does not nee d a

master latency timer.

14.1.1 VID—Vendor Identification Register (SATA—D31:F2)

Offset Address: 00h–01h Attribute: RO

Default Value: 8086h Size: 16 bit

Lockable: No Power Well: Core

70h–71h PID PCI Power Management Capability ID See regist er

description RO

72h–73h PC PCI Power Management Capabilities See register

description RO

74h–75h PMCS PCI Power Management Control and

Status See register

description R/W, RO,

R/WC

80h–81h MSICI Message Signaled Interrupt Capability

ID 7005h RO

82h–83h MSIMC Message Signaled Interrupt Message

Control 0000h RO, R/W

84h–87h MSIMA Message Signaled Interrupt Message

Address 00000000h RO, R/W

88h–89h MSIMD Message Signaled Interrupt Message

Data 0000h R/W

90h MAP Address Map 0000h R/W

92h–93h PCS Port Control and Status 0000h R/W, RO

94h-97h SCGC SATA Clock Gating Control 00000000h R/W

9Ch-9Fh SCLKGC SATA Clock General Configuration 00000000h R/W, R/WO

A8h-ABh SCAP0 SATA Capability Register 0 0010B012h RO, R/WO

ACh-AFh SCAP1 SATA Capability Register 1 00000048h RO

B0h-B1h FLRCID FLR Capability ID 0009h RO

B2h-B3h FLRCLV FLR Capability Length and Version See register

description R/WO, RO

B4h-B5h FLRCTRL FLR Control 0000h RO, R/W

C0h ATC APM Trapping Control 00h R/W

C4h ATS ATM Trapping Status 00h R/WC

D0h–D3h SP Scratch Pad 00000000h R/W

E0h–E3h BFCS BIST FIS Control/Status 00000000h R/W, R/WC

E4h–E7h BFTD1 BIST FIS Transmit Data, DW1 00000000h R/W

E8h–EBh BFTD2 BIST FIS Transmit Data, DW2 00000000h R/W

Table 14-1. SATA Controller PCI Register Address Map (SATA–D31:F2) (Sheet 2 of 2)

Offset Mnemonic Register Name Default Type

Bit Description

15:0 Vendor ID — RO. This is a 16-bit value assigned to Intel. Intel VID = 8086h

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 543

SATA Controller Registers (D31:F2)

14.1.2 DID—Device Identification Register (SATA—D31:F2)

Offset Address: 02h–03h Attribute: RO

Default Value: See Bit Description Size: 16 bit

Lockable: No Power Well: Core

14.1.3 PCICMD—PCI Command Register (SATA–D31:F2)

Address Offset: 04h–05h Attribute: RO, R/W

Default Value: 0000h Size: 16 bits

Bit Description

15:0 Device ID — RO. This is a 16-bit value assigned to the Intel® ICH9 SATA controller.

NOTE: The value of this fiel d will change dependent u p on the value of the MAP

Bit Description

15:11 Reserved

Interrupt Disable — R/W. This disables pin-based INTx# interrupts. This bit has no

effect on MSI operation.

0 = Int ernal INTx# messages are generated if there is an interrupt and MSI is not

enabled.

1 = Int ernal INTx# messages will not be generated.

9 Fast Back to Back Enable (FBE) — RO. Reserved as 0.

8 SERR# Enable (SERR_EN) — RO. Reserved as 0.

7 Wait Cycle Control (WCC) — RO. Reserved as 0.

Parity Error Response (PER) — R/W.

0 = Disabled. SATA controller will not generate PERR# when a data parity error is

detected.

1 = Enabled. SATA controller will generate PERR# when a data parity error is detected.

5 VGA Palette Snoop (VPS) — RO. Reserved as 0.

4 Postable Memory Write Enable (PMWE) — RO. Reserved as 0.

3 Special Cycle Enable (SCE) — RO. Reserved as 0.

2Bus Master Enable (BME) — R/W. This bit controls the ICH9’s ability to act as a PCI

master for IDE Bus Master transfers. This bit does not impact the generation of

completions for split transaction commands.

1Memory Space Enable (MSE) — R/W / RO. Controls access to the SATA controller’s

target memory space (for AHCI). This bit is RO ‘0’ when not in AHCI/RAID modes.

I/O Space Enable (IOSE) — R/W. This bit controls access to the I/O space registers.

0 = Disables access to the Legacy or Native IDE ports (both Primary and Secondary) as

well as the Bus Master I/O registers.

1 = Enable. Note that the Base Address register for the Bus Master registers should be

programmed before this bit is set.

SATA Controller Registers (D31:F2)

544 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.4 PCISTS — PCI Status Register (SATA–D31:F2)

Address Offset: 06h–07h Attribute: R/WC, RO

Default Value: 02B0h Size: 16 bits

Note: For the writable bits, software must write a 1 to clear bits that are set. Writing a 0 to

the bit has no effect.

Bit Description

15 Detected Parity Error (DPE) — R/WC.

0 = No parity error detected by SATA controller.

1 = SATA controller detects a parity error on its interface.

14 Signaled System Error (SSE) — RO. Reserved as 0.

13 Received Master Abort (RMA) — R/WC.

0 = Master abort Not generated.

1 = SATA controller, as a master, generated a master abort.

12 Reserved as 0 — RO.

11 Signaled Target Abort (STA) — RO. Reserved as 0.

10:9 DEVSEL# Timing Status (DEV_STS) — RO.

01 = Hardwired; Controls the device select time for the SAT A controller’s PCI interface.

Data Parity Error Detected (DPED) — R/WC. For ICH9, this bit can only be set on

read completions received from the bus when there is a parity error.

1 = SATA controller, as a master, either detects a parity error or sees the parity error

line asserted, and the parity error response bit (bit 6 of the command register) is

set.

7 Fast Back to Back Capable (FB2BC) — RO. Reserved as 1.

6 User Definable Features (UDF) — RO. Reserved as 0.

5 66MHz Capable (66MHZ_CAP) — RO. Reserved as 1.

4Capabilities List (CAP_LIST) — RO. This bit indicates the presen ce of a capabilities

list. The m inimum requirement for the capabilit ies list must be PCI power management

for the SATA controller.

Interrupt Status (INTS) — RO. Reflects the state of INTx# messages, IRQ14 or

IRQ15.

0 = Interrupt is cleared (independent of the state of Interrupt Disable bit in the

command register [offset 04h]).

1 = Interrupt is to be asserted

2:0 Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 545

SATA Controller Registers (D31:F2)

14.1.5 RID—Revision Identification Register (SATA—D31:F2)

Offset Address: 08h Attribute: RO

14.1.6 PI—Programming Interface Register (SATA–D31:F2)

14.1.6.1 When Sub Class Code Register (D31:F2:Offset 0Ah) = 01h

Address Offset: 09h Attribute: R/W, RO

Default Value: See bit description Size: 8 bits

Bit Description

7:0 Revision ID — RO. Refer to the Intel® I/O Controller Hub (ICH9) Specification Updat e

for the value of the Revision ID Register

Bit Description

7 This read-only bit is a 1 to indicate that the ICH9 supports bus master operation

6:4 Reserved. Will always return 0.

Secondary Mode Native Capable (SNC) — RO.

0 = Secondary controller only supports legacy mode.

1 = Secondary controller supports both legacy and native modes.

When MAP.MV (D31:F2:Offset 90:bits 1:0) is an y v alue other than 00b, this bit reports

as a 0. When MAP.MV is 00b, this bit reports as a 1.

Secondary Mode Native Enable (SNE) — R/W.

Determines the mode that the secondary channel is operating in.

0 = Secondary controller operating in legacy (compatibility) mode

1 = Secondary controller operating in native PCI mode.

When MAP.MV (D31:F2:Offset 90:bits 1:0) is an y v al ue other th an 00b, this bit is read-

only (RO). When MAP.MV is 00b, this bit is read/write (R/W).

If this bit is set by softw are, then the PN E bit (bit 0 of this regist er) must also be set by

software. While in theory these bits can be programmed separately, such a

configuration is not supported by hardware.

Primary Mode Native Capable (PNC) — RO.

0 = Primary controller only supports legacy mode.

1 = Primary controller supports both legacy and native modes.

When MAP.MV (D31:F2:Offset 90:bits 1:0) is an y v alue other than 00b, this bit reports

as a 0. When MAP.MV is 00b, this bit reports as a 1

Primary Mode Native Enable (PNE) — R/W.

Determines the mode that the primary channel is operating in.

0 = Primary controller operating in legacy (compatibility) mode.

1 = Primary controller operating in native PCI mode.

If this bit is set by software, then the SNE bit (bit 2 of this register) must also be set by

software simultaneously.

SATA Controller Registers (D31:F2)

546 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.6.2 When Sub Class Code Register (D31:F2:Offset 0Ah) = 04h

Address Offset: 09h Attribute: RO

Default Value: 00h Size: 8 bits

14.1.6.3 When Sub Class Code Register (D31:F2:Offset 0Ah) = 06h

Address Offset: 09h Attribute: RO

Default Value: 01h Size: 8 bits

14.1.7 SCC—Sub Class Code Register (SATA–D31:F2)

Address Offset: 0Ah Attribute: RO

Default Value: See bit description Size: 8 bits

Bit Description

7:0 Interface (IF) — RO.

When configured as RAID, this register becomes read only 0.

Bit Description

7:0 Interface (IF) — RO.

Indicates the SATA Controller supports AHCI, rev 1.2.

Bit Description

7:0

Sub Class Code (SCC)

This field spe cifies the sub-class code of the controller, per the table below:

Intel® ICH9 Only:

ICH9M Only:

Intel® Matrix Storage Techn o logy Enabled ICH9 components Only:

SCC Register Attribute SCC Register Value

RO 01h (IDE Controller)

MAP.SMS (D31:F2:Offset

90h:bit 7:6) SCC Register Value

00b 01h (IDE Controller)

01b 06h (AHCI Controller)

MAP.SMS (D31:F2:Offset

90h:bit 7:6) SCC Default Registe r

Value

00b 01h (IDE Controller)

01b 06h (AHCI Controller)

10b 04h (RAID Controller)

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 547

SATA Controller Registers (D31:F2)

14.1.8 BCC—Base Class Code Register

(SATA–D31:F2SATA–D31:F2)

Address Offset: 0Bh Attribute: RO

Default Value: 01h Size: 8 bits

14.1.9 PMLT—Primary Master Latency Timer Register

(SATA–D31:F2)

Address Offset: 0Dh Attribute: RO

Default Value: 00h Size: 8 bits

14.1.10 HTYPE—Header Type

(SATA–D31:F2)

Address Offset: 0Eh Attribute: RO

Default Value: 00h Size: 8 bits

14.1.11 PCMD_BAR—Primary Command Block Base Address

Address Offset: 10h–13h Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

NOTE: This 8-byte I/O space is used in native mode for the Primary Controller’s Command Block.

Bit Description

7:0 Base Class Code (BCC) — RO.

01h = Mass storage device

Bit Description

7:0 Master Latency Timer Count (MLTC) — RO.

00h = Hardwired. The SATA controller is implemented internally, and is not arbitrated

as a PCI device, so it does not need a Master Latency Timer.

Bit Description

7Multi-function Device (MFD) — RO.

Indicates this SATA controller is not part of a multifunction device.

6:0 Header Layout (HL) — RO.

Indicates that the SATA controller uses a target device layout.

Bit Description

31:16 Reserved

15:3 Base Address — R/W. This field provides the base address of the I/O space (8

consecutive I/O locations).

2:1 Reserved

0Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

SATA Controller Registers (D31:F2)

548 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.12 PCNL_BAR—Primary Control Block Base Address Register

(SATA–D31:F2)

Address Offset: 14h–17h Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

NOTE: This 4-byte I/O space is used in native mode for the Primary Controller’s Command Block.

14.1.13 SCMD_BAR—Secondary Command Block Base Address

Address Offset: 18h–1Bh Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

NOTE: This 4-byte I/O space is used in native mode for the Secondary Controller’s Command

Block.

14.1.14 SCNL_BAR—Secondary Control Block Base Address

Address Offset: 1Ch–1Fh Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

NOTE: This 4-byte I/O space is used in native mode for the Secondary Controller’s Command

Block.

Bit Description

31:16 Reserved

15:2 Base Address — R/W. This field provides the base address of the I/O space (4

consecutive I/O locations).

1 Reserved

0 Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

Bit Description

31:16 Reserved

15:3 Base Address — R/W. This field provides the base address of the I/O space (8

consecutive I/O locations).

2:1 Reserved

0Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

Bit Description

31:16 Reserved

15:2 Base Address — R/W. This field provides the base address of the I/O space (4

consecutive I/O locations).

1Reserved

0Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 549

SATA Controller Registers (D31:F2)

14.1.15 BAR — Legacy Bus Master Base Address Register

(SATA–D31:F2)

Address Offset: 20h–23h Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

The Bus Master IDE interface function uses Base Address register 5 to request a 16-

byte IO space to provide a software interface to the Bus Master functions. Only 12

bytes are actually used (6 bytes for primary, 6 bytes for secondary). Only bits [15:4]

are used to decode the address.

14.1.16 ABAR/SIDPBA1 — AHCI Base Address Register/Serial ATA

Index Data Pair Base Address (SATA–D31:F2)

When the programming interface is not IDE (i.e. SCC is not 01h), this register is named

ABAR. When the programming interface is IDE, this register becomes SIDPBA.

Note that hardware does not clear those BA bits when switching from IDE component

to non-IDE component or vice versa. BIOS is responsible for clearing those bits to 0

since the number of writable bits changes after component switching (as indicated by a

change in SCC). In the case, this register will then have to be re-programmed to a

proper value.

14.1.16.1 When SCC is not 01h

When the programming interface is not IDE, the register represents a memory BAR

allocating space for the AHCI memory registers defined in Section 15.3

Address Offset: 24-27h Attribute: R/W, RO

Default Value: 00000000h Size: 32 bits

NOTE:

1. The ABAR register must be set to a value of 0001_0000h or greater.

Bit Description

31:16 Reserved

15:5 Base Address — R/W. This field provides the base address of the I/O space (16

consecutive I/O locations).

4Base— R/W / RO. When SCC is 01h, this bit will be R/W resulting in requesting 16B of

I/O space. When SCC is not 01h, this bit will be Read Only 0, resulting in requesting

32B of I/O space.

3:1 Reserved

0Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

Bit Description

31:11 Base Address (BA) — R/W. Base address of register memory space (aligned to 1 KB)

10:4 Reserved

3Prefetchable (PF) — RO. Indicates that this range is not pre-fetchable

2:1 Type (TP) — RO. Indi cates that th is r ange can be mapped anywhere in 32-bit address

space.

0Resource Type Indicator (RTE) — RO. Hardwired to 0 to indicate a request for

SATA Controller Registers (D31:F2)

550 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.16.2 When SCC is 01h

When the programming interface is IDE, the register becomes an I/O BAR allocating 16

bytes of I/O space for the I/O-mapped registers defined in Section 27.2.4. Note that

although 16 bytes of locations are allocated, only 8 bytes are used to as SINDX and

SDATA registers; with the remaining 8 bytes preserved for future enhancement.

Address Offset: 24h–27h Attribute: R/WO

Default Value: 00000001h Size: 32 bits

14.1.17 SVID—Subsystem Vendor Identification Register

(SATA–D31:F2)

Address Offset: 2Ch–2Dh Attribute: R/WO

Default Value: 0000h Size: 16 bits

Lockable: No Power Well: Core

Function Level Reset: No

14.1.18 SID—Subsystem Identification Register (SATA–D31:F2)

Address Offset: 2Eh–2Fh Attribute: R/WO

Default Value: 0000h Size: 16 bits

Lockable: No Power Well: Core

Function Level Reset: No

14.1.19 CAP—Capabilities Pointer Register (SATA–D31:F2)

Address Offset: 34h Attribute: RO

Default Value: 80h Size: 8 bits

Bit Description

31:16 Reserved

15:4 Base Address (BA) — R/W. Base address of the I/O space.

3:1 Reserved

0Resource Type Indicator (RTE) — RO. Indicates a request for I/O space.

Bit Description

15:0 Subsystem Vendor ID (SVID) — R/WO. Value is written by BIO S. No hardware

action taken on this value.

Bit Description

15:0 Subsystem ID (SID) — R/WO. Value is written by BIOS. No hardw are action taken on

this value.

Bit Description

7:0 Capabilities Pointer (CAP_PTR) — RO. Indicates that the first capability pointer

offset is 80h. This value changes to 70h if the Sub Class Code (SCC) (Dev 31:F2:0Ah) is

configure as IDE mode (value of 01).

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 551

SATA Controller Registers (D31:F2)

14.1.20 INT_LN—Interrupt Line Register (SATA–D31:F2)

Address Offset: 3Ch Attribute: R/W

Default Value: 00h Size: 8 bits

Function Level Reset:No

14.1.21 INT_PN—Interrupt Pin Register (SATA–D31:F2)

Address Offset: 3Dh Attribute: RO

Default Value: See Register Description Size: 8 bits

14.1.22 IDE_TIM — IDE Timing Register (SATA–D31:F2)

Address Offset: Primary: 40h–41h Attribute: R/W

Secondary: 42h–43h

Default Value: 0000h Size: 16 bits

14.1.23 PID—PCI Power Management Capability Identification

Address Offset: 70h–71h Attribute: RO

Default Value: XX01h Size: 16 bits

Bit Description

7:0 Interrupt Line — R/W. This f ield is used to co mmunicate to softw are the interrupt li ne

that the interrupt pin is connected to.

Bit Description

7:0 Interrupt Pin — RO. This reflects the value of D31IP.SIP (Chipset Config

Registers:Offset 3100h:bits 11:8).

Bit Description

IDE Decode Enable (IDE) — R/W. Individually enable/disable the Primary or Secondary decode.

0 = Disable.

1 = Enables the Intel® ICH9 to decode the associated Command Blocks (1F0–1F7h for primary,

170–177h for secondary) and Control Block (3F6h for primary and 376h for secondary).

This bit effects the IDE decode ranges for both legacy and native-Mode decoding.

NOTE: This bit affects SATA operation in both combined and non-combined ATA modes. See

Section 5.16 for more on ATA modes of operation.

14:0 Reserved

Bits Description

15:8 Next Capability (NEXT) — RO.

B0h — if SCC = 01h (IDE mode) indicating next item is FLR capability pointer.

A8h — for all other values of SCC to point to the next capability structure.

7:0 Capability ID (CID) — RO. Indicates that this pointer is a PCI power management.

SATA Controller Registers (D31:F2)

552 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.24 PC—PCI Power Management Capabilities Register

(SATA–D31:F2)

Address Offset: 72h–73h Attribute: RO

Default Value: x003h Size: 16 bits

14.1.25 PMCS—PCI Power Management Control and Status

Address Offset: 74h–75h Attribute: R/W, R/WC

Default Value: xx08h Size: 16 bits

Function Level Reset: No (Bits 8 and 15)

Bits Description

15:11

PME Support (PME_SUP) — RO.

00000 = If SCC = 01h, indicates no PME support in IDE mode.

01000 = If SCC is not 01h, in a non-IDE mode, indicates PME# can be generated from

the D3HOT state in the SATA host controller.

10 D2 Supp ort (D2_SUP) — RO. Hardwired to 0. The D2 state is not supported

9 D1 Support (D1_SUP) — RO. Hardwired to 0. The D1 state is not supported

8:6 Auxiliary Current (AUX_CUR) — RO. PME# from D3COLD state is not supported,

therefore this field is 00 0b.

5Device Specifi c Initializat ion (DSI) — RO. Hardwired to 0 to indicate that no device-

specific initialization is required.

4 Reserved

3PME Clock (PME_CLK) — RO. Hardwired to 0 to indicate that PCI clock is not requ ired to

generate PME#.

2:0 Version (VER) — RO. Hardwired to 011 to indicates support for R evision 1.2 of the PCI

Power Management Specification.

Bits Description

PME Status (PMES) — R/WC. Bit is set when a PME event is to be requested, and if

this bit and PMEE is set, a PME# will be generated from the SATA controller

Note: Whenev er SCC = 01h, hardware wi ll automatic ally change th e attribu te of this bit

to RO ‘0’. Software is advised to clear PMEE and PMES together prior to changing SCC

thru MAP.SMS.

This bit is not rese t by Function Level Reset.

14:9 Reserved

PME Enable (PMEE) — R/W. When set, the SATA controller generates PME# form

D3HOT on a wa ke event .

Note: Whenever SCCSCC = 01h, hardware wi ll automatically change the attribute of

this bit to RO ‘0’ . Software is advised to clear PMEE and PMES together prior to changing

SCC thru MAP.SMS.

This bit is not rese t by Function Level Reset.

7:4 Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 553

SATA Controller Registers (D31:F2)

14.1.26 MSICI—Message Signaled Interrupt Capability

Identification (SATA–D31:F2)

Address Offset: 80h–81h Attribute: RO

Default Value: 7005h Size: 16 bits

Note: There is no support for MSI when the software is oper ating in legacy (IDE) mode when

AHCI is not enabled. Prior to switching from AHCI to IDE mode, software must make

sure that MSI is disabled.

No Soft Reset (NSFRST) — RO. These bits are used to indicate whether devices

transitioning from D3HOT state to D0 state will perform an internal reset.

0 = Device transitioning from D3HOT state to D0 state perform an internal reset.

1 = Device transitioning from D3HOT state to D0 state do not perform an internal reset.

Configuration content is preserved. Upon transition from the D3HOT state to D0 state

initialized state, no additional operating system intervention is required to preserve

configuration contex t beyond writin g to the PowerState bits.

Regardle ss of this bit, the controll er transition from D3HOT state to D0 state by a system

or bus segment reset will return to the state D0 uninitialized with only PME context

preserved if PME is supported and enabled.

2Reserved

1:0

Power State (PS) — R/W. These bits are used both to determine the current power

state of the

SATA controller and to set a new power state.

00 = D0 state

11 = D3HOT state

When in the D3HOT state, the controller’s configuration space is available, but the I/O

and memory spaces are not. Additionally, interrupts are blocked.

Bits Description

15:8 Next Pointer (NEXT) — RO. Indicates the next item in the list is the PCI power

management pointer.

7:0 Capability ID (CID) — RO. Capabilities ID indicates MSI.

SATA Controller Registers (D31:F2)

554 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.27 MSIMC—Message Signaled Interrupt Message Control

(SATA–D31:F2)

Address Offset: 82h–83h Attribute: R/W, RO

Default Value: 0000h Size: 16 bits

Note: There is no support for MSI when the software is operating in legacy (IDE) mode when

AHCI is not enabled. Prior to switching from AHCI to IDE mode, software must make

sure that MSI is disabled.

Bits Description

15:8 Reserved

764 Bit Address Capable (C64) — RO. Capable of generating a 32-bit message only.

6:4

Multiple Message Enable (MME) — R/W.

= 000 (and MSIE is set), a si ngle MSI message will be gener ated for all SA TA ports, and

bits [15:0] of the message vector will be driven from MD[15:0].

Values ‘011b’ to ‘111b’ are reserved. If this field is set to one of these reserved values,

the results are undefined.

NOTE: Note: The CCC interrupt is generated on unimplemented port (AHCI PI register

bit equal to 0). If CCC interrupt is disabled, no MSI shall be generated for the

port dedicated to the CCC interrupt. When CCC interrupt occurs, MD[2:0] is

dependant on CCC_CTL.INT (in addition to MME).

For 6 port components:

MME Value Driven on

MSI Memory Write

Bits[15:3] Bit[2] Bit[1] Bit[0]

000,

001, 010 MD[15:3] MD[2] MD[1] MD[0]

100 MD[15:3]

Port 0: 0

Port 1: 0

Port 2: 0

Port 3: 0

Port 4: 1

Port 5: 1

Port 0: 0

Port 1: 0

Port 2: 1

Port 3: 1

Port 4: 0

Port 5: 0

Port 0: 0

Port 1: 1

Port 2: 0

Port 3: 1

Port 4: 0

Port 5: 1

For 4 port components:

MME Value Dr iven on

MSI Memory Write

Bits[15:3] Bit[2] Bit[1] Bit[0]

000,

001, 010 MD[15:3] MD[2] MD[1] MD[0]

100 MD[15:3]

Port 0: 0

Port 1: 0

Port 4: 1

Port 5: 1

Port 0: 0

Port 1: 0

Port 2: 0

Port 3: 0

Port 0: 0

Port 1: 1

Port 2: 0

Port 3: 1

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 555

SATA Controller Registers (D31:F2)

14.1.28 MSIMA— Message Signaled Interrupt Message Address

(SATA–D31:F2)

Address Offset: 84h–87h Attribute: R/W

Default Value: 00000000h Size: 32 bits

Note: There is no support for MSI when the software is oper ating in legacy (IDE) mode when

AHCI is not enabled. Prior to switching from AHCI to IDE mode, software must make

sure that MSI is disabled.

14.1.29 MSIMD—Message Signaled Interrupt Message Data

(SATA–D31:F2)

Address Offset: 88h-89h Attribute: R/W

Default Value: 0000h Size: 16 bits

Note: There is no support for MSI when the software is oper ating in legacy (IDE) mode when

AHCI is not enabled. Prior to switching from AHCI to IDE mode, software must make

sure that MSI is disabled.

3:1

Multiple Message Capable (MMC) — RO. Indicates the number of interrupt messages

supported by the ICH9 SATA controller.

000 =1 MSI Capable (When SCC bit is set to 01h. MSI is not supported in IDE mode)

100 = 8 MSI Capable

MSI Enable (MSIE) — R/W /RO. If set, MSI is enabled and traditional interru pt pins

are not used to generate interrupts. This bit is RW when SC.SCC is not 01h and is read-

only 0 when SCC is 01h. Note that CMD.ID bit has no effect on MSI.

NOTE: Software must clear this bit to ‘0’ to disable MSI first before changing the

number of messages allocated in the MMC field. Software must also make sure

this bit is cleared to ‘0’ when operating in legacy mode (when GHC.AE = 0).

Bits Description

31:2 Address (ADDR) — R/W. Lower 32 bits of the system specified message address,

always DWORD aligned.

1:0 Reserved

Bits Description

15:0

Data (DATA) — R/W. This 16-bit field is programmed by system software if MSI is

enabled. Its content is driven onto the lower word of the data bus of the MSI memory

write transaction. Note that when the MME field is set to ‘001’ or ‘010’, bit [0] and bits

[1:0] respectively of the MSI memory write transaction will be driven based on the

source of the interrupt rather than from MD[2:0]. See the description of the MME field.

SATA Controller Registers (D31:F2)

556 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.30 MAP—Address Map Register (SATA–D31:F2)

Address Offset: 90h Attribute: R/W, R/WO

Default Value: 0000h Size: 16 bits

Function Level Reset: No (Bits 7:5 and 13:8 only)

14.1.31 PCS—Port Control and Status Register (SATA–D31:F2)

Address Offset: 92h–93h Attribute: R/W, RO

Default Value: 0000h Size: 16 bits

Function Level Reset: No

By default, the SAT A ports are set to the disabled state (bits [5:0] = ‘0’). When enabled

by software, the ports can transition between the on, partial, and slumber states and

can detect devices. When disabled, the port is in the “off” state and cannot detect any

devices.

If an AHCI-aw are or RAID enabled operating system is being booted, then system BIOS

shall insure that all supported SATA ports are enabled prior to passing control to the

OS. Once the AHCI aware OS is booted it becomes the enablin g/di sabling po licy owner

for the individual SA TA ports. This is accomplished by m anipulating a port’ s PxSCTL and

Bits Description

15:14 Reserved

13:8 Reserved

7:6

SATA Mode Select (SMS) — R/W. SW programs these bits to control the mode in

which the SATA Controller should operate:

00b = IDE mode

01b = AHCI mode

10b = RAID mode

11b = Reserved

NOTES:

1. The SATA Function Device ID will change based on the value of this register.

2. When switching from AHCI or RAID mode to IDE mode, a 2 port SATA controller

(Device 31, Function 5) will be enabled.

3. AHCI mode may only be selected when MV = 00

4. RAID mode may only be selected when MV = 00

5. Programming these bits with values that are invalid (e.g. selecting RAID when in

combined mode) will result in indeterministic behavior by the HW

6. SW shall not manipulate SMS during runtime operation; i.e. the OS will not do

this. The BIOS may choose to switch from one mode to another during POST.

These bits are not re set by Function Level Reset.

SATA Port-to-Controller Configuration (SC) — R/W. This bit changes the number of

SATA ports available within each SATA Controller.

0 = Up to 4 SATA ports are available for Controller 1 (Device 31 Function 2) with ports

[3:0] and up to 2 SATA ports are available for Controller 2 (Device 31 Function 5)

with ports [5:4].

1 = Up to 6 SATA ports are available for Controller 1 (Device 31 Function 2) with ports

[5:0] and no SATA ports are available for Controller 2 (Device 31 Function 5).

NOTE: This bit should be set to 1 only in AHCI mode. This bit is not reset by Function

Level Reset.

4:2 Reserved.

1:0 Map Value (MV) — RO. Reserved

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 557

SATA Controller Registers (D31:F2)

PxCMD fields. Because an AHCI or RAID aware OS will typically not have knowledge of

the PxE bits and because the PxE bits act as master on/off switches for the ports, pre-

boot software must insure that these bits are set to ‘1’ prior to booting the OS,

regardless as to whether or not a device is currently on the port.

Bits Description

OOB Retry Mode (ORM) — RW.

0 = The SATA controller will not retry after an OOB failure

1 = The SATA controller will continue to retry after an OOB failure until successful

(infinite r etry)

14 Reserved.

Port 5 Present (P5P) — RO. The status of this bit may change at any time. This bit

is cleared when the port is disabled via P5E. This bit is not cleared upon surprise

removal of a device.

0 = No device detected.

1 = The presence of a device on Port 5 has been detected.

Port 4 Present (P4P) — RO. The status of this bit may change at any time. This bit

is cleared when the port is disabled via P4E. This bit is not cleared upon surprise

removal of a device.

0 = No device detected.

1 = The presence of a device on Port 4 has been detected.

(Desktop

Only)

Port 3 Present (P3P) — RO. The status of this bit may change at any time. This bit

is cleared when the port is disabled via P3E. This bit is not cleared upon surprise

removal of a device.

0 = No device detected.

1 = The presence of a device on Port 3 has been detected.

(Desktop

Only)

Port 2 Present (P2P) — RO. The status of this bit may change at any time. This bit

is cleared when the port is disabled via P2E. This bit is not cleared upon surprise

removal of a device.

0 = No device detected.

1 = The presence of a device on Port 2 has been detected.

11:10

(Mobile

Only) Reserved.

Port 1 Present (P1P) — RO. The status of this bit may change at any time. This bit

is cleared when the port is disabled via P1E. This bit is not cleared upon surprise

removal of a device.

0 = No device detected.

1 = The presence of a device on Port 1 has been detected.

Port 0 Present (P0P) — RO. The status of this bit may change at any time. This bit

is cleared when the port is disabled via P0E. This bit is not cleared upon surprise

removal of a device.

0 = No device detected.

1 = The presence of a device on Port 0 has been detected.

7:6 Reserved

Port 5 Enabled (P5E) — R/W.

0 = Disabled. The port is in the ‘off’ state and cannot detect any devices.

1 = Enabled. The port can transition between the on, partial, and slumber states and

can detect devices.

NOTE: This bit takes preceden ce over P5CMD.SUD (offset ABAR+298h:bit 1)

If MAP.SC is ‘0’, if SCC is ‘01h’ this bit will be read only ‘0’ or if MAP.SPD[5] is ‘1’.

SATA Controller Registers (D31:F2)

558 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Port 4 Enabled (P4E) — R/W.

0 = Disabled. The port is in the ‘off’ state and cannot detect any devices.

1 = Enabled. The port can transition between the on, partial, and slumber states and

can detect devices.

NOTE: This bit takes precedence over P4CMD.SUD (offset ABAR+298h:bit 1)

If MAP.SC is ‘0’, if SCC is ‘01h’ this bit will be read only ‘0’ or if MAP.SPD[4] is ‘1’.

(Desktop

Only)

Port 3 Enabled (P3E) — R/W.

0 = Disabled. The port is in the ‘off’ state and cannot detect any devices.

1 = Enabled. The port can transition between the on, partial, and slumber states and

can detect devices.

NOTE: This bit takes precedence over P3CMD.SUD (offset ABAR+298h:bit 1). When

MAP.SPD[3] is ‘1’ this is reserved and is read-only 0.

(Desktop

Only)

Port 2 Enabled (P2E) — R/W.

0 = Disabled. The port is in the ‘off’ state and cannot detect any devices.

1 = Enabled. The port can transition between the on, partial, and slumber states and

can detect devices.

NOTE: This bit takes precedence over P2CMD.SUD (offset ABAR+218h:bit 1). When

MAP.SPD[2] is ‘1’ this is reserved and is read-only 0.

3:2

(Mobile

Only) Reserved

Port 1 Enabled (P1E) — R/W.

0 = Disabled. The port is in the ‘off’ state and cannot detect any devices.

1 = Enabled. The port can transition between the on, partial, and slumber states and

can detect devices.

NOTE: This bit takes precedence over P1CMD.SUD (offset ABAR+198h:bit 1). When

MAP.SPD[1] is ‘1’ this is reserved and is read-only 0.

Port 0 Enabled (P0E) — R/W.

0 = Disabled. The port is in the ‘off’ state and cannot detect any devices.

1 = Enabled. The port can transition between the on, partial, and slumber states and

can detect devices.

NOTE: This bit takes precedence over P0CMD.SUD (offset ABAR+118h:bit 1). When

MAP.SPD[0] is ‘1’ this is reserved and is read-only 0.

Bits Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 559

SATA Controller Registers (D31:F2)

14.1.32 SCLKCG - SATA Clock Gating Control Register

Address Offset: 94h-97h Attribute: R/W

Default Value: 00000000h Size: 32 bits

Bit Description

31 Reserved.

SATA Clock Request Enabled (SCRE) — RW

0 = SATA Clock Request Protocol is disabled. SATACLKREQ# pin, when in native

function, will always output ‘0’ to keep the SATA clock running.

1 = SATA Clock Request Protocol is enabled. SATACLKREQ# pin, when in native

function, will behave as the SATA clock request to the system clock chip.

29:24

Port Clock Disable (P CD ) —

0 = All clocks to the associated port logic will operate normally.

1 = The backbone clock driven to the associated port logic is gated and will not

toggle.

Bit 29: Port 5

Bit 28: Port 4

Bit 27: Port 3

BIt 26: Port 2

Bit 25: Port 1

Bit 24: Port 0

If a port is not available, software shall set the corresponding bit to 1. Software can

also set the corresponding bits to 1 on ports that are disabled.

23:9 Reserved.

8:0 SCLKCG Field 1 — R/W. BIOS must program these bits to 193h.

SATA Controller Registers (D31:F2)

560 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.33 SCLKGC - SATA Clock General Configuration Register

Address Offset: 9Ch-9Fh Attribute: R/W, R/WO

Default Value: 00000000h Size: 32 bits

Function Level Reset: No

Bit Description

31:8 Reserved

7 (ICH9

Base Only) Reserved

(ICH9R,

ICH9DH,

ICH9DO,

and

ICH9M-E

Only)

Alternate ID Enable (AIE) — R/WO.

0 = When in RAID mode the SATA Controller located at Device 31: Function 2 will

report the following Device ID 2822h for Desktop or 282Ah for Mobile and the

Microsoft Windows Vista* in-bo x version of the Intel ® Matrix Storage Manager

will load on the platform.

1 = When in RAID mode the SATA Controller located at Device 31: Function 2 will

report the following Device ID 2925h for Desktop or 292Ch for Mobile to

prevent the Microsoft Windows Vista* in-box version of the Intel® Matrix

Storage Manager from loading on the platform and will require the user to

perform an ‘F6’ installation of the appropriate Intel Matrix Storage Manager.

NOTE: This field is applicable when the AHCI is configured for RAID mode of

operation. It has no impact for AHCI and IDE modes of operation. BIOS is

recommended to program this bit prior to programming the MAP.SMS field

to reflect RAID. This field is reset by PLTRST#. BIOS is required to

reprogram the value of this bit after resuming from S3, S4 and S5.

6:2 Reserved

SATA2-port Configuration Indicator (SATA2PIND) — RO.

0 = Normal configuration.

1 = One IDE Controller is implemented supporting only two ports for a Primary

Master and a Secondary Master.

NOTE: When set, BIOS must ensure that bit 2 and bit 3 of the AHCI PI registers

are zeros. BIOS must also make sure that Port 2 and Port 3 are disabled

(via PCS configuration register) and the port clocks are gated (via SCLKCG

configuration register).

SATA4-port All Master Configuration Indicator (SATA4PMIND) — RO.

0 = Normal configuration.

1 = Two IDE Controllers are implemented, each supporting two ports for a Primary

Master and a Secondary Master.

NOTE: When set, BIOS must ensure that bit 2 and bit 3 of the AHCI PI registers

are zeros. BIOS must also make sure that Port 2 and Port 3 are disabled

(via PCS configuration register) and the port clocks are gated (via SCLKCG

configuration register).

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 561

SATA Controller Registers (D31:F2)

14.1.33.1 SATACR0—SATA Capability Register 0 (SATA–D31:F2)

Address Offset: A8h–ABh Attribute: RO, R/WO

Default Value: 0010B012h Size: 32 bits

Function Level Reset: No (Bits 15:8 only)

Note: This register shall be read-only 0 when SCC is 01h.

14.1.33.2 SATACR1—SATA Capability Register 1 (SATA–D31:F2)

Address Offset: ACh–AFh Attribute: RO

Default Value: 00000048h Size: 32 bits

Note: This register shall be read-only 0 when SCC is 01h.

Bit Description

31:24 Reserved

23:20 Major Revision (MAJREV) — RO: Major revision number of the SATA Capability

Pointer implemented.

19:16 Minor Revision (MINREV) — RO: Minor revision number of the SATA Capability

Pointer implemented.

15:8 Next Capability Pointer (NEXT) — R/WO: Points to the next capability structure.

These bits are not reset by Function Level Reset.

7:0 Capability ID (CAP)— RO: This value of 12h has been assigned by the PCI SIG to

designate the SATA Capability Structure.

Bit Description

31:16 Reserved

15:4

BAR Offset (BAROFST) — RO: Indicates the offset into the BAR where the Index/Data

pair are located (in Dword granularity). The Index and Data I/O registers are loca ted at

offset 10h within the I/O space defined by LBAR. A value of 004h indicates offset 10h.

000h = 0h offset

001h = 4h offset

002h = 8h offset

003h = Bh offset

004h = 10h offset

...

FFFh = 3FFFh offset (max 16KB)

3:0

BAR Location (BARLOC) — RO: Indicates the absolute PCI Configuration Register

address of the BAR containing the Index/Data pair (in Dword granularity). The Index

and Data I/O registers reside within the space defined by LBAR in the SA TA controller. A

value of 8h indicates offset 20h, which is LBAR.

0000 – 0011b = reserved

0100b = 10h => BAR0

0101b = 14h => BAR1

0110b = 18h => BAR2

0111b = 1Ch => BAR3

1000b = 20h => LBAR

1001b = 24h => BAR5

1010 – 1110b = reserved

1111b = Index/Data pair in PCI Configuration space. This isn’t supported in ICH9.

SATA Controller Registers (D31:F2)

562 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.34 FLRCID—FLR Capability ID (SATA–D31:F2)

Address Offset: B0-B1h Attribute: RO

Default Value: 0009h Size: 16 bits

14.1.35 FLRCLV—FLR Capability Length and Version (SATA–

D31:F2)

Address Offset: B2-B3h Attribute: RO, R/WO

Default Value: xx06h Size: 16 bits

Function Level Reset: No (Bit 9:8 Only when FLRCSSEL = ‘0’)

When FLRCSSEL = ‘0’, this register is defined as follows:

When FLRCSSEL = ‘1’, this register is defined as follows:

Bit Description

15:8 Next Capability Pointer — RO. 00h indicates the final item in the capability list.

7:0 Capability ID — RO. The value of this field depends on the FLRCSSEL bit.

13h = If PFLRCSSEL = 0

09h (Vendor Specific) = If PFLRCSSEL = 1

Bit Description

15:10 Reserved.

9FLR Capability — R/WO.

1 = Support for Function Level reset.

This bit is not reset by the Function Level Reset.

8TXP Capability — R/WO.

1 = Support for Transactions Pending (TXP) bit. TXP must be supported if FLR is

supported.

7:0 Vendor-Specific Capability ID — RO. This field indicates the # of bytes of this

Vendor Specific capability as required by the PCI specification. It has the value of 06h

for the FLR capability.

Bit Description

15:12 Vendor-Specific Capability ID — RO. A value of 2h identifies this capability as the

Function Level Reset (FLR).

11:8 Capability Version — RO. This field indicates the version of the FLR capability.

7:0 Vendor-Specific Capability ID — RO. This field indicates the # of bytes of this

Vendor Specific capability as required by the PCI specification. It has the value of 06h

for the FLR capability.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 563

SATA Controller Registers (D31:F2)

14.1.36 FLRC—FLR Cont rol (SATA–D31:F2)

Address Offset: B 4-B5h Attribute: RO, R/W

Default Value: 0000h Size: 16 bits

14.1.37 ATC—APM Trapping Control Register (SATA–D31:F2)

Address Offset: C0h Attribute: R/W

Default Value: 00h Size: 8 bits

Function Level Reset:No

Bit Description

15:9 Reserved.

8Transactions Pending (TXP) — RO.

0 = Controller has received all non-posted requests.

1 = Controller has issued non-posted requests which has not been completed.

7:1 Reserved.

0Initiate FLR — R/W. Used to initiate FLR transition. A write of ‘1’ indicates FLR

transi tion. Since hardw are must no t respond to an y cycles till FLR completion the v alue

read by software from this bit is ‘0’.

Bit Description

7:4 Reserved

3Secondary Slave Trap (SST) — R/W. Enables trapping and SMI# assertion on legacy

I/O accesses to 170h-177h and 376h. The active device on the secon d ary interface

must be device 1 for the trap and/or SMI# to occur.

2Secondary Master Trap (SPT) — R/W. Enables trapping and SMI# assertion on

legacy I/O accesses to 170h-177h and 376h. The active device on the secondary

interface must be device 0 for the trap and/or SMI# to occur.

1Primary Slave Trap (PST) — R/W. Enables trapping and SMI# assertion on legacy I/

O accesses to 1F0h-1F 7h and 3F6h. The active device on the primary interface must be

device 1 for the trap and/or SMI# to occur.

0Primary Master Trap (PMT) — R/W. Enables trapping and SMI# assertion on legacy

I/O accesses to 1F0h-1F7h and 3F6h. The active device on the primary interface must

be device 0 for the trap and/or SMI# to occur.

SATA Controller Registers (D31:F2)

564 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.1.38 ATS—APM Trapping Status Register (SATA–D31:F2)

Address Offset: C4h Attribute: R/WC

Default Value: 00h Size: 8 bits

Function Level Reset:No

14.1.39 SP Scratch Pad Register (SATA–D31:F2)

Address Offset: D0h Attribute: R/W

Default Value: 00000000h Size: 32 bits

Bit Description

7:4 Reserved

3Secondary Slave Trap (SST) — R/WC. Indicates that a trap occurred to the

secondary slave device.

2Secondary Master Trap (SPT) — R/WC. Indicates that a trap occurred to the

secondary master device.

1Primary Slave Trap (PST) — R/WC. Indicates that a trap occurred to the primary

slave device.

0Primary Master Trap (PMT) — R/WC. Indicates that a trap occurred to the primary

master device.

Bit Description

31:0 Data (DT) — R/W. This is a read/write register that is available for softw are to use. No

hardware action is taken on this register.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 565

SATA Controller Registers (D31:F2)

14.1.40 BFCS—BIST FIS Control/Status Register (SATA–D31:F2)

Address Offset: E0h–E3h Attribute: R/W, R/WC

Default Value: 00000000h Size: 32 bits

Bits Description

31:16 Reserved

Port 5 BIST FIS Initiate (P 5BFI) — R/W. When a rising e dge is detected on this bit

field, the ICH9 initiates a BIST FIS to the device on Port 5, using the parameters

specified in this register and the data specified in BFTD1 and BFTD2. The BIST FIS

will only be initiated if a device on Port 5 is present and ready (not partial/slumber

state). After a BIST FIS is successfully complete d, software must disable and re-

enable the port using the PxE bits at offset 92h prior to attempting additional BIST

FISs or to return the ICH9 to a normal operational mode. If the BIST FIS fails to

complete, as indicated by the BFF bit in the register, then software can clear then set

the P5BFI bit to initiate another BIST FIS. This can be retried until the BIST FIS

eventually completes successfully

Port 4 BIST FIS Initiate (P 4BFI) — R/W. When a rising e dge is detected on this bit

field, the ICH9 initiates a BIST FIS to the device on Port 4, using the parameters

specified in this register and the data specified in BFTD1 and BFTD2. The BIST FIS

will only be initiated if a device on Port 4 is present and ready (not partial/slumber

state). After a BIST FIS is successfully complete d, software must disable and re-

enable the port using the PxE bits at offset 92h prior to attempting additional BIST

FISs or to return the ICH9 to a normal operational mode. If the BIST FIS fails to

complete, as indicated by the BFF bit in the register, then software can clear then set

the P4BFI bit to initiate another BIST FIS. This can be retried until the BIST FIS

eventually completes successfully

(Desktop

Only)

Port 3 BIST FIS Initiate (P 3BFI) — R/W. When a rising e dge is detected on this bit

field, the ICH9 initiates a BIST FIS to the device on Port 3, using the parameters

specified in this register and the data specified in BFTD1 and BFTD2. The BIST FIS

will only be initiated if a device on Port 3 is present and ready (not partial/slumber

state). After a BIST FIS is successfully complete d, software must disable and re-

enable the port using the PxE bits at offset 92h prior to attempting additional BIST

FISs or to return the ICH9 to a normal operational mode. If the BIST FIS fails to

complete, as indicated by the BFF bit in the register, then software can clear then set

the P3BFI bit to initiate another BIST FIS. This can be retried until the BIST FIS

eventually completes successfully

(Desktop

Only)

Port 2 BIST FIS Initiate (P 2BFI) — R/W. When a rising e dge is detected on this bit

field, the ICH9 initiates a BIST FIS to the device on Port 2, using the parameters

specified in this register and the data specified in BFTD1 and BFTD2. The BIST FIS

will only be initiated if a device on Port 2 is present and ready (not partial/slumber

state). After a BIST FIS is successfully complete d, software must disable and re-

enable the port using the PxE bits at offset 92h prior to attempting additional BIST

FISes or to return the ICH9 to a normal operational mode. If the BIST FIS fails to

complete, as indicated by the BFF bit in the register, then software can clear then set

the P2BFI bit to initiate another BIST FIS. This can be retried until the BIST FIS

eventually completes successfully

13:12

(Mobile

Only) Reserved

SATA Controller Registers (D31:F2)

566 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

BIST FIS Successful (BFS ) — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = T his bit is set any time a BIST FIS transmitted by ICH9 receives an R_OK

completion status from the device.

NOTE: This bit must be cleared by software prior to initiating a BIST FIS.

BIST FIS Failed (BFF ) — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = T his bit is set any time a BIST FIS transmitted by ICH9 receives an R_ERR

completion status from the device.

NOTE: This bit must be cleared by software prior to initiating a BIST FIS.

Port 1 BIST FIS Initi ate (P1BFI) — R/W . When a rising edge is detected on this bit

field, the ICH9 initiates a BIST FIS to the device on Port 1, using the parameters

specified in this register and the data specified in BFTD1 and BFTD2. The BIST FIS

will only be initiated if a device on Port 1 is present and ready (not partial/slumber

state). After a BIST FIS is successfully completed, software must disable and re-

enable the port using the PxE bits at offset 92h prior to attempting additional BIST

FISes or to return the ICH9 to a normal operational mode. If the BIST FIS fails to

complete, as indicated by the BFF bit in the register, then softw are can clear then set

the P1BFI bit to initiate another BIST FIS. This can be retried until the BIST FIS

eventually completes successful ly

Port 0 BIST FIS Initiat e (P0BFI) — R/W. When a rising edge is detected on this bit

field, the ICH9 initiates a BIST FIS to the device on Port 0, using the parameters

specified in this register and the data specified in BFTD1 and BFTD2. The BIST FIS

will only be initiated if a device on Port 0 is present and ready (not partial/slumber

state). After a BIST FIS is successfully completed, software must disable and re-

enable the port using the PxE bits at offset 92h prior to attempting additional BIST

FISes or to return the ICH9 to a normal operational mode. If the BIST FIS fails to

complete, as indicated by the BFF bit in the register, then softw are can clear then set

the P0BFI bit to initiate another BIST FIS. This can be retried until the BIST FIS

eventually completes successful ly

7:2

BIST FIS Parameters (BFP) — R/W. These 6 bits form the contents of the upper 6

bits of the BIST FIS Pattern Definition in any BIST FIS transmitted by the ICH9. This

field is not port specific — its contents will be used for any BIST FIS initiated on port

0, port 1, port 2 or port 3. The specific bit definitions are:

Bit 7: T – Far End Transmit mode

Bit 6: A – Align Bypass mode

Bit 5: S – Bypass Scrambling

Bit 4: L – Far End Retimed Loopback

Bit 3: F – Far End Analog Loopback

Bit 2: P – Primitive bit for use with Transmit mode

1:0 Reserved

Bits Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 567

SATA Controller Registers (D31:F2)

14.1.41 BFTD1—BIST FIS Transmit Data1 Register (SATA–D31:F2)

Address Offset: E4h–E7h Attribute: R/W

Default Value: 00000000h Size: 32 bits

14.1.42 BFTD2—BIST FIS Transmit Data2 Register (SATA–D31:F2)

Address Offset: E8h–EBh Attribute: R/W

Default Value: 00000000h Size: 32 bits

Bits Description

31:0

BIST FIS Transmit Data 1 — R/W. The data programmed into this register will form

the contents of the second dword of any BIST FIS initiated b y the ICH9. This regis te r i s

not port specific — its contents will be used for BIST FIS initiated on any port. Although

the 2nd and 3rd DWs of the BIST FIS are only meaningful when the “T” bit of the BIST

FIS is set to indicate “Far-End Transmit mode”, this register’s contents will be

transmitted as the BIST FIS 2nd DW regardless of whether or not the “T” bit is indicated

in the BFCS register (D31:F2:E0h).

Bits Description

31:0

BIST FIS Transmit Data 2 — R/W. The data programmed into this register will form

the contents of the third dword of any BIST FIS initiated by the ICH9. This register is not

port specific — its contents will be used for BIST FIS initiated on any port. Although the

2nd and 3rd DWs of the BIST FIS are only meaningful when the “T” bit of the BIST FIS

is set to indicate “Far-End T ransmit mode” , this register’s contents will be transmitted as

the BIST FIS 3rd DW regardless of whether or not the “T” bit is indicated in the BFCS

SATA Controller Registers (D31:F2)

568 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.2 Bus Master IDE I/O Registers (D31:F2)

The bus master IDE function uses 16 by tes of I/O space, allocated via the BAR register,

located in Device 31:Function 2 Configur ation space, offset 20h. All bus master IDE I/O

space registers can be accessed as byte, word, or dword quantities. Reading reserved

bits returns an indeterminate, inconsistent value, and writes to reserved bits have no

affect (but should not be attempted). These registers are only used for legacy

operation. Software must not use these registers when running AHCI. All I/O registers

are reset by Function Level Reset. The description of the I/O registers is shown in

Table 14-2.

Table 14-2. Bus Master IDE I/O Register Address Map

BAR+

Offset Mnemonic Register Default Type

00 BMICP Command Register Primary 00h R/W

01 — Reserved — RO

02 BMISP Bus M aster IDE Status Register Primary 00h R/W, R/

WC, RO

03 — Reserved — RO

04–07 BMIDP Bus Master IDE Descriptor Table Pointer

Primary xxxxxxxxh R/W

08 BMICS Command Register Secondary 00h R/W

09 — Reserved — RO

0Ah BMISS Bus Master IDE Status Register Secondary 00h R/W, R/

WC, RO

0Bh — Reserved — RO

0Ch–

0Fh BMIDS Bus Master IDE Descriptor Table Pointer

Secondary xxxxxxxxh R/W

10h AIR AHCI Index Register 00000000h R/W, RO

14h AIDR AHCI Index Data Register xxxxxxxxh R/W

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 569

SATA Controller Registers (D31:F2)

14.2.1 BMIC[P,S]—Bus Master IDE Command Register (D31:F2)

Address Offset: Primary: BAR + 00h Attribute: R/W

Secondary: BAR + 08h

Default Value: 00h Size: 8 bits

Bit Description

7:4 Reserved. Returns 0.

Read / Write Control (R/WC) — R/W. This bit sets the direction of the bus master

transfer: This bit must NOT be changed when the bus master function is active.

0 = M emory reads

1 = Memory wr ites

2:1 Reserved. Returns 0.

Start/Stop Bus Master (START) — R/W.

0 = All state information is lost when this bit is cleared. Master mode operation cannot

be stopped and then resumed. If this bit is reset while bus master operation is still

active (i.e., the Bus Master IDE Active bit (D31:F2:BAR + 02h, bit 0) of the Bus

Master IDE Status register for that IDE channel is set) and th e drive has not yet

finished it s data trans fer (the Interru pt bit in the Bus Master IDE Status register for

that IDE channel is not set), the bus master command is said to be aborted and

data transferred from the drive may be discarded instead of being written to

system memory.

1 = Enables bus master operation of the controller. Bus master operation does not

actually start unless the Bus Master Enable bit (D31:F1:04h, bit 2) in PCI

configuration space is also set. Bu s master operation begins when this bit is

detected changing from 0 to 1. The controller will transfer data between the IDE

device and memory only when this bit is set. Master operation can be halted by

writing a 0 to thi s bit.

NOTE: This bit is intended to be cleared by software after the data transfer is

completed, as indicated by either the Bus Master IDE Active bit being cleared or

the Interrupt bit of the Bus Master IDE Status register for that IDE channel

being set, or both. Hardware does not clear this bit automatically. If this bit is

cleared to 0 prior to the DMA data transfer being initiated by the drive in a

SATA Controller Registers (D31:F2)

570 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.2.2 BMIS[P,S]—Bus Master IDE Status Register (D31:F2)

Address Offset: Primary: BAR + 02h Attribute: R/W, R/WC, RO

Secondary: BAR + 0Ah

Default Value: 00h Size: 8 bits

Bit Description

PRD Interrupt Status (PRDIS) — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = This bit is set when the host cont roll er execution of a PRD that has its PRD_INT bit

set.

Drive 1 DMA Capa ble — R/W.

0 = Not Capable.

1 = Capable. Set by device dependent code (BIOS or device driver) to indicate that

drive 1 for this channel is capable of DMA transfers, and that the controller has

been initialized for optimum performance. The Intel® ICH9 does not use this bit. It

is intended for systems that do not attach BMIDE to the PCI bus.

Drive 0 DMA Capa ble — R/W.

0 = Not Capable

1 = Capable. Set by device dependent code (BIOS or device driver) to indicate that

drive 0 for this channel is capable of DMA transfers, and that the controller has

been initialized for optimum performance. The ICH9 does not use this bit. It is

intended for systems that do not attach BMIDE to the PCI bus.

4:3 Reserved. Returns 0.

Interrupt — R/WC .

0 = Software clears this bit by writing a 1 to it.

1 = Set when a device FIS is re ceived with the ‘I’ bit s et, provided that softw are has not

disabled interrupts via the IEN bit of the Device Control Register (see chapter 5 of

the Serial ATA Specification, Revision 1.0a).

Error — R/WC.

0 = Software clears this bit by writing a 1 to it.

1 = Thi s bit is set when the controller encounters a target abort or master abort when

transferring data on PCI.

Bus Master IDE Active (ACT) — RO.

0 = Thi s bit is cleared by the ICH9 when the last transfer for a region is performed,

where EOT for that region is set in the region descriptor. It is also cleared by the

ICH9 when the Start Bus Master bit (D31:F2:BAR+ 00h, bit 0) is cleared in the

Command register. When this bit is read as a 0, all data transferred from the drive

during the previous bus master command is visible in system memory, unless the

bus master command was aborted.

1 = Set by the ICH9 when the Start bit is written to the Command register.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 571

SATA Controller Registers (D31:F2)

14.2.3 BMID[P,S]—Bus Master IDE Descriptor Table Pointer

Address Offset: Primary: BAR + 04h–07h Attribute: R/W

Secondary: BAR + 0Ch–0Fh

Default Value: All bits undefined Size: 32 bits

14.2.4 AIR—AHCI Index Register (D31:F2)

Address Offset: Primary: BAR + 10h Attribute: R/W

Default Value: 00000000h Size: 32 bits

This register is available only when SCC is not 01h.

14.2.5 AIDR—AHCI Index Data Register (D31:F2)

Address Offset: Primary: BAR + 14h Attribute: R/W

Default Value: All bits undefined Size: 32 bits

This register is available only when SCC is not 01h.

Bit Description

31:2

Address of Descriptor Table (ADDR) — R/W. The bits in th is field correspond to bits

[31:2] of the memory location of the Physical Region Descriptor (PRD). The Descriptor

Table must be Dword-aligned. The Descriptor Table must not cross a 64-K boundary in

memory.

1:0 Reserved

Bit Description

31:11 Reserved

10:2 Index (INDEX)— R/W: This Index register is used to select the Dword offset of the

Memory Mapped AHCI register to be accessed. A Dword, Word or Byte access is

specified by the active byte en ables of the I/O access to the Data register.

1:0 Reserved

Bit Description

31:0

Data (DATA)— R/W: This Data register is a “window” through which data is read or

written to the AHCI memory mapped registers. A read or write to this Data register

triggers a corresponding read or write to the memory mapped register pointed to by

the Index register. The Index register must be setup prior to the read or write to this

Data register.

Note that a physical register is not actually implemented as the data is actually stored

in the memory mapped registers.

Since this is not a physical register, the “default” value is the same as the default value

of the register po inte d to by Index.

SATA Controller Registers (D31:F2)

572 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.3 Serial ATA Index/Data Pair Superset Registers

All of these I/O registers are in the core well. They are exposed only when SCC is 01h

(i.e., IDE programming interface).

These are Index/Data Pair registers that are used to access the SerialATA superset

registers (SerialATA Status, SerialATA Control and SerialATA Error). The I/O space for

these registers is allocated through SIDPBA. Locations with offset from 08h to 0Fh are

reserved for future expansion. Software-write operations to the reserved locations will

have no effect while software-read operations to the reserved locations will return 0.

14.3.1 SINDX – Serial ATA Index (D31:F2)

Address Offset: SIDPBA + 00h Attribute: R/W

Default Value: 00000000h Size: 32 bits

Offset Mnemonic Register

00h–03h SINDEX Serial ATA Index

04h–07h SDATA Serial ATA Data

08h–0Ch — Reserved

0Ch–0Fh — Reserved

Bit Description

31:16 Reserved

15.8

Port Index (PIDX) - R/W: This Index field is used to specify the port of the SATA

controller at which the port-specific SSTS, SCTL, and SERR registers are located.

00h = Primary Master (Port 0)

01h = Primary Slave (Port 2)

02h = Secondary Master (Port 1)

03h = Secondary Slave (Port 3)

All other values are Reserved.

7:0

registers current ly being indexed into. These three registers are th e Serial A T A superset

SStatus, SControl and SError memory registers and are port specific, hence for this

SATA controller, the r e are four sets of these registers. Refer to Section 14.4.3.10,

Section 14.4.3.11, and Section 14.4.3.12 for definitions of the SStatus, SControl and

SError registers.

00h = SSTS

01h = SCTL

02h = SERR

All other values are Reserved.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 573

SATA Controller Registers (D31:F2)

14.3.2 SDATA – Serial ATA Data (D31:F2)

Address Offset: SIDPBA + 04h Attribute: R/W

Default Value: 00000000h Size: 32 bits

Bit Description

31:0

Data (DATA) - R/W: This Data register is a “window” through which data is read or

written to from the register pointed to by the Serial ATA Index (SINDX) register above.

Note that a physical register is not actually implemented as the data is actually stored

in the memory mapped registers.

Since this is not a physical register, the “default” value is the same as the default value

of the register po in te d to by SINDX.RIDX field.

SATA Controller Registers (D31:F2)

574 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.3.2.1 PxSSTS—Serial ATA Status Register (D31:F2)

Address Offset: Attribute: RO

Default Value: 00000000h Size: 32 bits

SDA T A when SINDX.RIDX is 00h. This is a 32-bit register that conveys the current state

of the interface and host. The ICH9 updates it continuously and asynchronously. When

the ICH9 transmits a COMRESET to the device, this register is updated to its reset

values.

Bit Description

31:12 Reserved

11:8

Interface Power Management (IPM) — RO. Indicates the current interface state:

All other values reserved.

7:4

Current Interface Speed (SPD) — RO. Indicates the negotiated interface

communication speed.

All other values reserved.

ICH9 Supports Generation 1 communication rates (1.5 Gb/s) and Gen 2 rates

(3.0 Gb/s).

3:0

Device Detection (DET) — RO. Indicates the interface device detection and Phy

state:

All other values reserved.

Value Description

0h Device not present or communication not established

1h Interface in active state

2h Interface in PARTIAL power management state

6h Interface in SLUMBER power management state

Value Description

0h Device not present or communication not established

1h Generation 1 communication rate negotiated

2h Generation 2 communication rate negotiated

Value Description

0h No device detected and Phy communication not established

1h Device presen ce detected but Phy communication not esta blished

3h Device presence detected an d Phy communication established

4h Phy in offline mode as a result of the interface being disabled or

running in a BI ST loopback mode

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 575

SATA Controller Registers (D31:F2)

14.3.2.2 PxSCTL — Serial ATA Control Register (D31:F2)

Address Offset: Attribute: R/W, RO

Default Value: 00000004h Size: 32 bits

SDATA when SINDX.RIDX is 01h. This is a 32-bit read-write register by which software

controls SATA capabilities. Writes to the SControl register result in an action being

taken by the ICH9 or the interface. R eads from the register return the last v alue written

to it.

Bit Description

31:20 Reserved

19:16 Port Multiplier Port (PMP) — RO. This field is not used by AHCI.

15:12 Select Power Management (SPM) — RO. This field is not used by AHCI.

11:8

Interface Power Management Transitions Allowed (IPM) — R/W. Indicates which

power states the ICH9 is allowed to transition to:

All other values reserved

7:4

Speed Allowed (SPD) — R/W. Indicates the highest allowable speed of the interface.

This speed is limited by the CAP.ISS (ABAR+00h:bit 23:20) field.

All other values reserved.

ICH9 Supports Generation 1 communication rates (1.5 Gb/s) and Gen 2 rates

(3.0 Gb/s).

3:0

Device Detection Initialization (DET) — R/W. Controls the ICH9’s device detection

and interface initialization.

All other values reserved.

When this field is written to a 1 h, the ICH9 initiates COMRESET and starts the

initialization process. When the initialization is complete, this field shall remain 1h until

set to another value by software.

This field may only be changed to 1h or 4h when PxCMD.ST is 0. Changing this field

while the ICH9 is running results in undefined behavior.

Value Description

0h No interface restrictions

1h Transitions to the PARTIAL state disabled

2h Transitions to the SLUMBER state disabled

3h Transitions to both PARTIAL and SLUMBER states disabled

Value Description

0h No speed negotiation restrictions

1h Limit speed negotiation to Generation 1 communication rate

2h Limit speed negotiation to Generation 2 communication rate

Value Description

0h No device detectio n or initializatio n action requested

Perform interface communication initialization sequence to establish

communication. This is functionally equivalent to a hard reset and

results in the interface being reset and communications re-

initialized

4h Disable the Serial ATA interface and put Phy in offline mode

SATA Controller Registers (D31:F2)

576 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.3.2.3 PxSERR—Serial ATA Error Register (D31:F2)

Address Offset: Attribute: R/WC

Default Value: 00000000h Size: 32 bits

SDATA when SINDx.RIDX is 02h.

Bits 26:16 of this register contains diagnostic error information for use by diagnostic

software in validating correct operation or isolating failure modes. Bits 11:0 contain

error information used by host softw are in determining the appropriate response to the

error condition. If one or more of bits 11:8 of this register are set, the controller will

stop the current transfer.

Bit Description

31:27 Reserved

26 Exchanged (X): When set to one this bit indicates that a change in device presence

has been dete cted since the last time this bit was cl eared. This bit shal l always be set to

1 anytime a COMINIT signal is received. This bit is reflected in the P0IS.PCS bit.

25 Unrecognized FIS Type (F): Indicates that one or more FISs were received by the

Transport layer with good CRC, but had a type field that was not recognized.

Transport state transition error (T): Indicates that an error has occurred in the

transition

from one state to another within the Transport layer since the last time this bi t was

cleared.

Transport state transition error (T): Indicates that an error has occurred in the

transition

from one state to another within the Transport layer since the last time this bi t was

cleared.

Handshake (H): Indicates that one or more R_ERR handshake response was received

in response to frame transmission. Such errors may be the result of a CRC error

detected by the recipient, a disparity or 8b/10b decoding error, or other error condition

leading to a negative handshake on a transmitted frame.

21 CRC Error (C): Indicates that one or more CRC errors occurred with the Link Layer.

20 Disparity Error (D): This field is not used by AHCI.

19 10b to 8b Decode Error (B): Indicates that one or more 10b to 8b decoding errors

occurred.

18 Comm Wake (W): Indicates that a Comm Wake signal was detected by the Phy.

17 Phy Internal Error (I): Indicates that the Phy detected some internal error.

PhyRdy Change (N): When set to 1 this bit indicates that the internal PhyRdy signal

changed state since the last time this bit was cleared. In the ICH9, this bit will be s et

when PhyRdy changes from a 0 -> 1 or a 1 -> 0. The state of this bit is then reflected

in the PxIS.PRCS interrupt status bit and an interrupt will be generated if enabled.

Software clears this bit by writing a 1 to it.

15:12 Reserved

11 Internal Error (E): The SATA controller failed due to a master or target abort when

attempting to access system memory.

10 Protocol Error (P): A violation of the Serial ATA protocol was detected.

Note: The ICH9 does not set this bit for all protocol violations that may occur on the

SATA link.

Persistent Communication or Data Integrity Erro r (C): A communication error

that was not recovered occurred that is expected to be persistent. Persistent

communications errors may arise from faulty interconnect with the device, from a

device that has been removed or has failed, or a number of other causes.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 577

SATA Controller Registers (D31:F2)

14.4 AHCI Registers (D31:F2)

Note: These registers are AHCI-specific and available when the ICH9 is properly configured.

The Serial ATA Status, Control, and Error registers are special exceptions and may be

accessed on all ICH9 components if properly configured; see Section 14.3 for details.

The memory mapped registers within the SATA controller exist in non-cacheable

memory space. Additionally, locked accesses are not supported. If software attempts to

perform locked transactions to the registers, indeterminate results may occur. Register

accesses shall have a maximum size of 64-bits; 64-bit access must not cross an 8-byte

alignment boundary. All memory registers are reset by Function Level Reset unless

specified otherwise.

The registers are broken into two sections – generic host control and port control. The

port control registers are the same for all ports, and there are as many registers banks

as there are ports.

8Transient Data Integrity Error (T): A data integrity error occurred that was not

recovered by the interface.

7:2 Reserved.

Recovered Communications Error (M ): Communications between the device and

host was temporarily lost but was re-established. This can arise from a device

temporarily being removed, from a temporary loss of Phy synchronization, or from

other causes and may be derived from the PhyNRdy signal between the Phy and Link

layers.

0Recovered Data Integrity Error (I): A data integrity error occurred that was

recovered by the interface through a retry operation or other recovery action.

Bit Description

Table 14-3. AHCI Register Address Map

ABAR +

Offset Mnemonic Register

00–1Fh GHC Generic Host Control

20h–FFh — Reserved

100h–17Fh P0PCR Port 0 port control registers

180h–1FFh P1PCR Port 1 port control registers

200h–27Fh P2PCR Port 2 port control registers (Desktop Only)

Registers are not available and software must not read or write

registers. (Mobile Onl y)

280h–2FFh P3PCR Port 3 port control registers (Desktop Only)

Registers are not available and software must not read or write

registers. (Mobile Onl y)

300h–37Fh P4PCR Port 4 port control registers

380h–3FFh P5PCR Port 5 port control registers

SATA Controller Registers (D31:F2)

578 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.4.1 AHCI Generic Host Control Registers (D31:F2)

14.4.1.1 CAP—Host Capabilities Register (D31:F2)

Address Offset: ABAR + 00h–03h Attribute: R/WO, RO

Default Value: FF22FFC2h (Desktop) Size: 32 bits

DE127F03h (Mobile)

Function Level Reset:No

All bits in this register that are R/WO are reset only by PLTRST#.

Table 14-4. Generic Host Controller Register Address Map

ABAR +

Offset Mnemonic Register Default Type

00–03 CAP Host Capabilities

FF22FFC2h

(desktop)

DE127F03h

(mobile)

R/WO, RO

04–07 GHC Global ICH9 Control 00000000h R/W, RO

08–0Bh IS Interrupt Status 00000000h R/WC

0Ch–0Fh PI Ports Implemented 00000000h R/WO, RO

10h-13h VS AHCI Version 00010200h RO

14h-17h CCC_CTL Command Completion Coalescing

Control 00010121h R/W, RO

18h-1Bh CCC_PORTS Command Completion Coalescing

Ports 00000000h R/W

1Ch-1Fh EM_LOC Enclosure Management Location 01000002h RO

20h-23h EM_CTRL Enclosure Management Control 07010000h R/W, R/WO,

A0h-A3h VSP Vendor Specific 00000000h RO, R/WO

Bit Description

31 Supports 64-bit Addressing (S64A) — RO. Indicates that the SATA controller can

access 64-bit data st ructures. The 32-bit upper bits of the port DMA Descriptor, the

PRD Base, and each PRD entry are read/write.

Supports Command Queue Accelerati on (S CQA) — RO. Hardwired to 1 to

indicate that the SATA controller supports SATA command queuing via the DMA

Setup FIS. The Intel® ICH9 handles DMA Setup FISes natively, and can handle auto-

activate optimization through that FIS.

29 Supports SNotification Register (SSNTF): — RO. The ICH9 SATA Controller does not

support the SNotification r egister.

Supports Interlock Swit ch (S IS) — R/WO. Indicates whether the SA TA controller

supports interlock switches on its ports for use in Hot Plug operations. This value is

loaded by platform BIOS prior to OS initialization.

If this bit is set, BIOS must also map the SATAGP pins to the SATA controller through

GPIO space.

Supports Staggered Spin-up (SSS) — R/WO. Indica tes whether the SATA

controller supports staggered spin-up on its ports, for use in balancing power spikes.

This value is loaded by platform BIOS prior to OS initialization.

0 = Staggered spin-up not supported.

1 = Staggered spin-up supported.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 579

SATA Controller Registers (D31:F2)

Supports Aggressive Link Power Management (SALP) — R/WO.

0 = Software shall treat the PxCMD.ALPE and PxCMD.ASP bits as reserved.

1 = The SATA controller supports auto-generating link requests to the partial or

slumber states when there are no commands to process.

25 Supports Activity LED (SAL) — RO. Indicates that the SATA controller supports a

single output pin (SATALED #) which indicates ac tivity.

Supports Command List Override (SCLO) — R/WO. When se t to '1', indicates

that the Controller supports the PxCMD.CLO bit and it's associated function. When

cleared to '0', The Controller is not capable of clearing the BSY and DRQ bits in the

Status register in order to issue a software reset if these bits are still set from a

previous operation.

23:20 Interface Speed Support (ISS) — R/WO. Indicat es the maximum spee d the SAT A

controller can support on its ports.

2h =3.0 Gb/s.

19 Supports Non-Zero DMA Offsets (SNZO) — RO. Reserved, as per the AHCI Revision

1.2 spec ification

Supports AHCI Mode Only (SAM) — RO. The SATA controller may optionally

support AHCI access mechanism only.

0 = SATA controller supports both IDE and AHCI Modes

1 = SATA controller supports AHCI Mode Only

17 Reserved

16 Supports Port Multiplier FIS Based Switching (PMFS) — RO. Reserved, as per

the AHCI Revision 1.0 specification.

NOTE: FIS Based Port Multiplier not supported by ICH9.

15 PIO Multiple DRQ Block (PMD) — RO. The SATA controller support s PIO Multiple

DRQ Command Block

14 Slumber State Ca pable (SSC) — R/WO. The SAT A controller supports the slumber

state.

13 Partial State Capable (PSC) — R/WO. The SATA controller supports the partial

state.

12:8 Number of Command Slots (NCS) — RO. Hardwired to 1Fh to indicate support for

32 slots.

7Command Completion Coalescing Supported (CCCS) — R/WO.

0 = Command Completion Coalescing Not Supported

1 = Command Completion Coalescing Supported

6Enclosure Management Supported (EMS) — R/WO.

0 = Enclosure Management Not Supported

1 = Enclosure Management Supporte d

Supports External SATA (SXS) — R/WO.

0 = External SATA is not supported on any ports

1 = External SATA is supported on one or more ports

When set, SW can examine each SATA port ’s Command Register (PxCMD) to

determine which port is routed externally.

4:0 Number of Ports (NPS) — RO. Hardwired to 5h to indicate support for 6 ports.

Note that the number of ports indicated in this field may be more than the number

of ports indicated in the PI (ABAR + 0Ch) register.

Bit Description

SATA Controller Registers (D31:F2)

580 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.4.1.2 GHC—Global ICH9 Control Register (D31:F2)

Address Offset: ABAR + 04h–07h Attribute: R/W, RO

Default Value: 00000000h Size: 32 bits

Bit Description

AHCI Enable (AE) — R/W. When set, indicates that an AHCI driver is loaded and the

controller will be talked to via AHCI mechanisms. This can be used by an ICH9 that

supports both legacy mechanisms (such as SFF-8038i) and AHCI to know when the

controller will not be talked to as legacy.

0 = Software will communicate with the ICH9 using legacy mechanisms.

1 = Software will communicate with the ICH9 using AHCI. The ICH9 will not have to

allow command processing via both AHCI and legacy mechanisms.

Software shall set this bit to 1 before accessing other AHCI registers.

30:3 Reserved

MSI Revert to Single Message (MRSM) — RO: When set to '1' by hardware,

indicates that the host controller requested more than one MSI vector but has reverted

to using the first vector only. When this bit is cleared to '0', the Controller has not

reverted to single MSI mode (i.e. hardw are is already in single MSI mode, softw are has

allocated the number of messages requested, or hardware is sharing interrupt vectors if

MC.MME < MC.MMC).

"MC.MSIE = '1' (MSI is enabled)

"MC.MMC > 0 (multiple messages requested)

"MC.MME > 0 (more than one message allocated)

"MC.MME!= MC.MMC (messa ges allocated not equal to numb er requested)

When this bit is set to '1', single MSI mode operation is in use and software is

responsible for clearing bits in the IS register to clear interrupts.

This bit shall be cleared to '0' by hardware when any of the four conditions stated is

false. This bit is also cleared to '0' when MC.MSIE = '1' and MC.MME = 0h. In this case,

the hardware has been programmed to use single MSI mode, and is not "reverting" to

that mode.

For ICH9, the Controller shall always revert to single MSI mode when the n umber of

vectors allocated by the host is less than the number requested. This bit is ignored

when GHC.HR = 1.

1Interrupt Enable (IE) — R/W. This global bit enables interrupts from the ICH9.

0 = All interrupt sources from all ports are disabled.

1 = Interrupts are allowed from the AHCI controller.

Controller Reset (HR) — R/W. Resets ICH9 AHCI controller.

0 = No effect

1 = When set by SW, this bit causes an internal reset of the ICH9 AHCI controller. All

state machines that relate to data tr ansfers and queuing return to an idle condition,

and all ports are re-initialized via COMRESET.

NOTE: For further details, consult section 12.3.3 of the Serial ATA Advanced Host

Controller Interface specification.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 581

SATA Controller Registers (D31:F2)

14.4.1.3 IS—Interrupt Status Register (D31:F2)

Address Offset: ABAR + 08h–0Bh Attribute: R/WC

Default Value: 00000000h Size: 32 bits

This register indicates which of the ports within the controller have an interrupt pending

and require service.

Bit Description

31:7 Reserved. Returns 0.

(Mobile

Only) Reserved. Returns 0 .

(Desktop

Only)

Coalescing Interrupt Pending Status (CIPS) — R/WC.

0 = No interrupt pending.

1 = A command completion coalescing interrupt has been generated.

Interrupt Pending Status Port[5] (IPS[5]) — R/WC.

0 = No interrupt pending.

1 = Port 5 has an interrupt pending. Software can use this information to determine

which ports require service after an interrupt.

Interrupt Pending Status Port[4] (IPS[4]) — R/WC.

0 = No interrupt pending.

1 = Port 4 has an interrupt pending. Software can use this information to determine

which ports require service after an interrupt.

(Desktop

Only)

Interrupt Pending Status Port[3] (IPS[3]) — R/WC.

0 = No interrupt pending.

1 = Port 3 has an interrupt pending. Software can use this information to determine

which ports require service after an interrupt.

(Desktop

Only)

Interrupt Pending Status Port[2] (IPS[2]) — R/WC

0 = No interrupt pending.

1 = Port 2 has an interrupt pending. Software can use this information to determine

which ports require service after an interrupt.

3:2

(Mobile

Only) Reser ved. Returns 0 .

Interrupt Pending Status Port[1] (IPS[1]) — R/WC.

0 = No interrupt pending.

1 = Port 1has an interrupt pending. Software can use this information to determine

which ports require service after an interrupt.

Interrupt Pending Status Port[0] (IPS[0]) — R/WC.

0 = No interrupt pending.

1 = Port 0 has an interrupt pending. Software can use this information to determine

which ports require service after an interrupt.

SATA Controller Registers (D31:F2)

582 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.4.1.4 PI—Ports Implemented Register (D31:F2)

Address Offset: ABAR + 0Ch–0Fh Attribute: R/WO, RO

Default Value: 00000000h Size: 32 bits

Function Level Reset:No

This register indicates which ports are exposed to the ICH9. It is loaded by platform

BIOS. It indicates which ports that the device supports are available for software to

use. For ports that are not available, software must not read or write to registers within

that port.

Bit Description

31:6 Reserved. Returns 0 .

Ports Implemented Port 5 (PI5) — R/WO.

0 = The port is not implemented.

1 = The port is implemented.

This bit is read-only ‘0’ if MAP.SC = ‘0’ or SCC = ‘01h’.

Ports Implemented Port 4 (PI4) — R/WO.

0 = The port is not implemented.

1 = The port is implemented.

This bit is read-only ‘0’ if MAP.SC = ‘0’ or SCC = ‘01h’.

(Mobile

Only)

Ports Implemented Port 3 (PI3) — RO.

0 = The port is not implemented.

(Desktop

Only)

Ports Implemented Port 3 (PI3) — R/WO.

0 = The port is not implemented.

1 = The port is implemented.

(Mobile

Only)

Ports Implemented Port 2 (PI2) — RO.

0 = The port is not implemented.

(Desktop

Only)

Ports Implemented Port 2 (PI2)— R/WO.

0 = The port is not implemented.

1 = The port is implemented.

1 Ports Implemented Port 1 (PI1) — R/WO.

0 = The port is not implemented.

1 = The port is implemented.

0Ports Implemented Port 0 (PI0) — R/WO.

0 = The port is not implemented.

1 = The port is implemented.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 583

SATA Controller Registers (D31:F2)

14.4.1.5 VS—AHCI Version (D31:F2)

Address Offset: ABAR + 10h–13h Attribute: RO

Default Value: 00010200h Size: 32 bits

This register indicates the major and minor ve rsion of the AHCI specification. It is BCD

encoded. The upper two bytes represent the major version number, and the lower two

bytes represent the minor version number. Example: Version 3.12 would be

represented as 00030102h. The current version of the specific ation is 1.20

(00010200h).

14.4.1.6 CCC_CTL—Command Completion Coalescing Control Register (D31:F2)

Address Offset: ABAR + 14h–17h Attribute: R/W, RO

Default Value: 00010131h Size: 32 bits

This register is used to configure the command coalescing feature. This register is

reserved if command coalescing is not supported (CAP_CCCS = ‘0’).

Bit Description

31:16 Major Version Number (MJR) — RO. Indicates the major version is 1

15:0 Minor Version Number (MNR) — RO. Indicates the minor version is 20.

Bit Description

31:16

Timeout Value (TV) — R/W. The timeout value is specified in 10 microsecond

intervals. hbaCCC_Timer is loaded with this timeout value. hbaCCC_Timer is only

decremented when commands are outstanding on the selected ports. The Controller

will signal a CCC interrupt when hbaCCC_Timer has decremented to ‘0’. The

hbaCCC_Timer is reset to the timeout value on the assertion of each CCC interrupt. A

timeout value of 0 is invalid.

15:8

Command Completions (CC) — R/W. Specifies the num b er of command

completions that are necessary to cause a CCC interrupt. The Controller has an

internal command completion counter, hbaCCC_CommandsComplete.

hbaCCC_CommandsComplete is incremented by one each time a selected port has a

command completion. When hbaCCC_CommandsComplete is equal to the command

completions value, a CCC interrupt is signaled. The internal command completion

counter is reset to ‘0’ on the assertion of each CCC interrupt.

7:3

Interrupt (INT) — RO. Specifies the interrupt used by the CCC feature. This

interrupt must be marked as unused in the AHCI Ports Implemented memory register

by the corresponding bit being set to ‘0’. Thus, the CCC_interrupt corresponds to the

interrupt for an unimplemented port on the controller. When a CCC in terrupt occurs,

the IS[INT] bit s hall be asserted to ‘1’ regardless of whether PIRQ interrupt or MSI is

used.

Note that in MSI, CC interrupt may share an interrupt vector with other ports. F or

example, if the number of message allocated is 4, then CCC interrupt share interrupt

vector 3 along with port 3, 4, and 5 but IS[6] shall get set.

2:1 Reserved

Enable (EN) — R/W.

0 = The command completion coalescing feature is disabled and no CCC interrupts are

generated

1 = The command completion coalescing feature is enabled and CCC interrupts may

be generated based on timeout or command completion conditions.

Software shall only change the contents of the TV and CC fields when EN is cleared to

'0'. On transi tion of thi s bit from '0 ' to '1 ', any updated v alues for the TV and CC fields

shall take effect.

SATA Controller Registers (D31:F2)

584 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.4.1.7 CCC_Ports—Command Completion Coalescing Ports Register (D31:F2)

Address Offset: ABAR + 18h–1Bh Attribute: R/W

Default Value: 00000000h Size: 32 bits

This register is used to specify the ports that are coalesced as part of the CCC feature

when CCC_CTL.EN = ‘1’. This register is reserved if command coalescing is not

supported (CAP_CCCS = ‘0’).

14.4.1.8 EM_LOC—Enclosure Management Location Register (D31:F2)

Address Offset: ABAR + 1Ch–1Fh Attribute: RO

Default Value: 01000002h Size: 32 bits

This register identifies the location and size of the enclosure management message

buffer. This register is reserved if enclosure management is not supported (i.e.

CAP.EMS = 0).

Bit Description

31:0

Ports (PRT) — R/W.

0 = The port is not part of the command completion c oalescing feature.

1 = The corresponding port is part of the command completion coalescing feature.

Bits set to ‘1’ in this regi ster must also ha ve t he corres ponding bit se t to ‘1’ in t he

Ports Implemented register.

Bits set to '1' in this register must also have the corresponding bit set to '1' in the

Ports Implemented register. An updated value for this field shall take effect within one

timer increment (1 millisecond).

Bit Description

31:16 Offset (OFST) — RO. The offset of the message buffer in Dwords from the beginning

of the ABAR.

15:0 Buffer Size (SZ) — RO. Specifies the size of the transmit message buffer area in

Dwords. The ICH9 SATA controller only supports transmit buffer.

A value of ‘0’ is invalid.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 585

SATA Controller Registers (D31:F2)

14.4.1.9 EM_CTRL—Enclosure Management Control Register (D31:F2)

Address Offset: ABAR + 20h–23h Attribute: R/W, R/WO, RO

Default Value: 07010000h Size: 32 bits

This register is used to control and obtain status for the enclosure management

interface. This register includes information on the attributes of the implementation,

enclosure management messages supported, the status of the interface, whether any

message are pending, and is used to initiate sending messages. This register is

reserved if enclosure management is not supported (CAP_EMS = ‘0’).

Bit Description

31:27 Reserved

Activity LED Hardware Dr iven (ATTR.ALHD) — R/WO.

1 = The SA TA controller drives the activity LED for the LED message type i n hardware

and does not utilize software for this LED.

The host controller does not begin transmitting the hardware based activity signal

until after software has written CTL.TM=1 after a reset condition.

Transmit Only (ATTR.XMT) — RO.

0 = Th e SATA controller supports transmitting and receiving messages.

1 = The SATA controller only supports transmitting messages and does not support

receiving messages.

Single Message Buffer (ATTR.SMB) — RO.

0 = There are separate receive and transmit buffers such that unsolicited messages

could be supported.

1 = The SATA controller has one message buffer that is shared for messages to

transmit and messages received. Unsolicited receive messages are not supported

and it is software’s responsibility to manage access to this buffer.

23:20 Reserved

19 SGPIO Enclosure Management Messages (SUPP.SGPIO): — RO.

1 = Th e SATA controller supports the SGPIO register interface message type.

18 SES-2 Enclosure Management Messages (SUPP.SES2): — RO.

1 = Th e SATA controller su pports the SES-2 mes sage type.

17 SAF-TE Enclosure Management Messages (SUPP.SAFTE): — RO.

1 = The SATA controller su pports the SAF-TE message type.

16 LED Message Types (SUPP.LED): — RO.

1 = Th e SATA controller supports the LED me ssage type.

15:10 Reserved

Reset (RST): — R/W.

0 = A write of ‘0’ to this bit by software will have no effect.

1 = When set by software, The SATA controller shall reset all enclosure management

message logic and take all appropriate reset actions to ensure message s can be

transmitted / received after the reset. After the SATA controller comple tes the

reset operation, the SATA controller shall set the value to ‘0’.

Transmit Message (CTL.TM): — R/W.

0 = A write of ‘0’ to this bit by software will have no effect.

1 = When set by software, The SATA controller shall transmit the message contained

in the message buffer. When the message is completely sent, the SATA controller

shall set the value to ‘0’.

Software shall not change the contents of the message buffer while CTL.TM is set to

'1'.

7:1 Reserved

0Message Received (STS.MR): — RO. Message Received is not supported i n ICH9.

SATA Controller Registers (D31:F2)

586 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.4.2 Vendor Specific Regi sters (D31:F2)

14.4.2.1 VSP—Vendor Specific (D31:F2)

Address Offset: ABAR + A0h–A3h Attribute: RO, RWO

Default Value: 00000000h Size: 32 bits

14.4.3 Port Registers (D31:F2)

Ports not available will result in the corresponding Port DMA register space being

reserved. The controller shall ignore writes to the reserved space on write cycles and

shall return ‘0’ on read cycle accesses to the reserved location.

Bit Description

31:1 Reserved

Supports Low Power Device Detection (SLPD)— RWO

Indicates whether SATA power management and device hot (un)pulg is supported.

0 = Not supported.

1 = Supported.

Table 14-5. Port [5:0] DMA Register Address Map (Sheet 1 of 4)

ABAR +

Offset Mnemonic Register

100h–103h P0CLB Port 0 Command List Base Address

104h–107h P0CLBU Port 0 Command List Base Address Upper 32-Bits

108h–10Bh P0FB Port 0 FIS Base Address

10Ch–10Fh P0FBU Port 0 FIS Base Address Upper 32-Bits

110h–113h P0IS Port 0 Interrupt Status

114h–117h P0IE Port 0 Interrupt Enable

118h–11Bh P0CMD Port 0 Command

11Ch–11Fh — Reserved

120h–123h P0TFD Port 0 Task File Data

124h–127h P0SIG Port 0 Signature

128h–12Bh P0SSTS Port 0 Serial ATA Status

12Ch–12Fh P0SCTL Port 0 Serial ATA Control

130h–133h P0SERR Port 0 Serial ATA Error

134h–137h P0SACT Port 0 Serial ATA Active

138h–13Bh P0CI Port 0 Command Issue

13Ch–17Fh — Reserved

180h–183h P1CLB Port 1 Command List Base Address

184h–187h P1CLBU Port 1 Command List Base Address Upper 32-Bits

188h–18Bh P1FB Port 1 FIS Base Address

18Ch–18Fh P1FBU Port 1 FIS Base Address Upper 32-Bits

190h–193h P1IS Port 1 Interrupt Status

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 587

SATA Controller Registers (D31:F2)

194h–197h P1IE Port 1 Interrupt Enable

198h–19Bh P1CMD Port 1 Command

19Ch–19Fh — Reserved

1A0h–1A3h P1TFD Port 1 Task File Data

1A4h–1A7h P1SIG Port 1 Signature

1A8h–1ABh P1SSTS Port 1 Serial ATA Status

1ACh–1AFh P1SCTL Port 1 Serial ATA Control

1B0h–1B3h P1SERR Port 1 Serial ATA Error

1B4h–1B7h P1SACT Port 1 Serial ATA Active

1B8h–1BBh P1CI Port 1 Command Issue

1BCh–1FFh — Reserved

200h–27Fh

(Mobile Only) —Reserved

Registers are not available and software must not read

from or write to registers.

200h–203h P2CLB Port 2 Command List Base Address

204h–207h P2CLBU Port 2 Command List Base Address Upper 32-Bits

208h–20Bh P2FB Port 2 FIS Base Address

20Ch–20Fh P2FBU Port 2 FIS Base Address Upper 32-Bits

210h–213h P2IS Port 2 Interrupt Status

214h–217h P2IE Port 2 Interrupt Enable

218h–21Bh P2CMD Port 2 Command

21Ch–21Fh — Reserved

220h–223h P2TFD Port 2 Task File Data

224h–227h P2SIG Port 2 Signature

228h–22Bh P 2SSTS Port 2 Serial ATA Status

22Ch–22Fh P2SCTL Port 2 Serial ATA Control

230h–233h P2SERR Port 2 Serial ATA Error

234h–237h P2SACT Port 2 Serial ATA Active

238h–23Bh P2CI Port 2 Command Issue

23Ch–27Fh — Reserved

280h–2FFh

(Mobile Only) —Reserved

Registers are not available and software must not read

from or write to registers.

280h–283h P3CLB Port 3 Command List Base Address

284h–287h P3CLBU Port 3 Command List Base Address Upper 32-Bits

288h–28Bh P3FB Port 3 FIS Base Address

28Ch–28Fh P3FBU Port 3 FIS Base Address Upper 32-Bits

290h–293h P3IS Port 3 Interrupt Status

Table 14-5. Port [5:0] DMA Register A ddress Map (Sheet 2 of 4)

ABAR +

Offset Mnemonic Register

SATA Controller Registers (D31:F2)

588 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

294h–297h P3IE Port 3 Interrupt Enable

298h–29Bh P3CMD Port 3 Command

29Ch–29Fh — Reserved

2A0h–2A3h P3TFD Port 3 Task File Data

2A4h–2A7h P3SIG Port 3 Signature

2A8h–2ABh P3SSTS Port 3 Serial ATA Status

2ACh–2AFh P 3SCTL Port 3 Serial ATA Control

2B0h–2B3h P3SERR Port 3 Serial ATA Error

2B4h–2B7h P3SACT Port 3 Serial ATA Active

2B8h–2BBh P3CI Port 3 Command Issue

2BCh–2FFh — Reserved

300h–303h P4CLB Port 4 Command List Base Address

304h–307h P4CLBU Port 4 Command List Base Address Upper 32-Bits

308h–30Bh P4FB Port 4 FIS Base Address

30Ch–30Fh P4FBU Port 4 FIS Base Address Upper 32-Bits

310h–313h P4IS Port 4 Interrupt Status

314h–317h P4IE Port 4 Interrupt Enable

318h–31Bh P4CMD Port 4 Command

31Ch–31Fh — Reserved

320h–323h P4TFD Port 4 Task File Data

324h–327h P4SIG Port 4 Signature

328h–32Bh P4SSTS Port 4 Serial ATA Status

32Ch–32Fh P4SCTL Port 4 Serial ATA Control

330h–333h P4SERR Port 4 Serial ATA Error

334h–337h P4SACT Port 4 Serial ATA Active

338h–33Bh P4CI Port 4 Command Issue

33Ch–37Fh — Reserved

380h–383h P5CLB Port 5 Command List Base Address

384h–387h P5CLBU Port 5 Command List Base Address Upper 32-Bits

388h–38Bh P5FB Port 5 FIS Base Address

38Ch–38Fh P5FBU Port 5 FIS Base Address Upper 32-Bits

390h–393h P5IS Port 5 Interrupt Status

394h–397h P5IE Port 5 Interrupt Enable

398h–39Bh P5CMD Port 5 Command

39Ch–39Fh — Reserved

3A0h–3A3h P5TFD Port 5 Task File Data

3A4h–3A7h P5SIG Port 5 Signature

Table 14-5. Port [5:0] DMA Register Address Map (Sheet 3 of 4)

ABAR +

Offset Mnemonic Register

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 589

SATA Controller Registers (D31:F2)

14.4.3.1 PxCLB—Port [5:0] C ommand List Base Address Register

(D31:F2)

Address Offset: Port 0: ABAR + 100h Attribute: R/W

Port 1: ABAR + 180h

Port 2: ABAR + 200h (Desktop Only)

Port 3: ABAR + 280h (Desktop Only)

Port 4: ABAR + 300h

Port 5: ABAR + 380h

Default Value: Undefined Size: 32 bits

14.4.3.2 PxCLBU—Port [5:0] Command List Base Address Upper

32-Bits Register (D31:F2)

Address Offset: Port 0: ABAR + 104h Attribute: R/W

Port 1: ABAR + 184h

Port 2: ABAR + 204h (Desktop Only)

Port 3: ABAR + 284h (Desktop Only)

Port 4: ABAR + 304h

Port 5: ABAR + 384h

Default Value: Undefined Size: 32 bits

3A8h–3ABh P5SSTS Port 5 Serial ATA Status

3ACh–3AFh P5SCTL Port 5 Serial ATA Control

3B0h–3B3h P5SERR Port 5 Serial ATA Error

3B4h–3B7h P5SACT Port 5 Serial ATA Active

3B8h–3BBh P5CI Port 5 Command Issue

3BCh–3FFh — Reserved

Table 14-5. Port [5:0] DMA Register A ddress Map (Sheet 4 of 4)

ABAR +

Offset Mnemonic Register

Bit Description

31:10

Command List Base Address (CLB) — R/W. Indicates the 32-bit bas e for the

command list for this port. This base is used when fetching commands to execute. The

structure pointed to by this address range is 1 KB in lengt h. This address must be 1-KB

aligned as indicated by bits 31:10 being read/write.

Note that these bits are not reset on a Controller reset.

9:0 Reserved

Bit Description

31:0

Command List Base Address Upper (CLBU) — R/W. Indicates the upper 32-bits for

the command list base address for this port. This base is used when fetching

commands to execute.

Note that these bits are not reset on a Controller reset.

SATA Controller Registers (D31:F2)

590 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.4.3.3 PxFB—Port [5:0] FIS Base Address Register (D31:F2)

Address Offset: Port 0: ABAR + 108h Attribute: R/W

Port 1: ABAR + 188h

Port 2: ABAR + 208h (Desktop Only)

Port 3: ABAR + 288h (Desktop Only)

Port 4: ABAR + 308h

Port 5: ABAR + 388h

Default Value: Undefined Size: 32 bits

14.4.3.4 PxFBU—Port [5:0] FIS Base Address Upper 32-Bits

Address Offset: Port 0: ABAR + 10Ch Attribute: R/W

Port 1: ABAR + 18Ch

Port 2: ABAR + 20Ch (Desktop Only)

Port 3: ABAR + 28Ch (Desktop Only)

Port 4: ABAR + 30Ch

Port 5: ABAR + 38Ch

Default Value: Undefined Size: 32 bits

Bit Description

31:8

FIS Base Address (FB) — R/W. Indicates th e 32-bit base for received FISes. The

structure pointed to by this address range is 256 bytes in length. This address must be

256-byte aligned, as indicated by bits 31:3 being read/write.

Note that these bits are not reset on a Controller reset.

7:0 Reserved

Bit Description

31:0 Command List Base Address Upper (CLBU) — R/W. Indicates the upper 3 2-bits for

the received FIS base for this port.

Note that these bits are not reset on a Controller reset.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 591

SATA Controller Registers (D31:F2)

14.4.3.5 PxIS—Port [5:0] Interrupt Status Register (D31:F2)

Address Offset: Port 0: ABAR + 110h Attribute: R/WC, RO

Port 1: ABAR + 190h

Port 2: ABAR + 210h (Desktop Only)

Port 3: ABAR + 290h (Desktop Only)

Port 4: ABAR + 310h

Port 5: ABAR + 390h

Default Value: 00000000h Size: 32 bits

Bit Description

31 Cold Port Detect Status (CPDS) — RO. Cold presence detect is not supported.

30 Task File Error Status (TFES) — R/WC. This bit i s set whe never t he status register is

updated by the device and the error bit (PxTFD.bit 0) is set.

29 Host Bus Fatal Error Status (HBFS) — R/WC. Indicates that the Intel® ICH9

encountered an error that it cannot recover from due to a bad software pointer. In PCI,

such an indication would be a target or master abort.

28 Host Bus Data Error Status (HBDS) — R/WC. Indicates that the ICH9 encountered a

data error (uncorrectable ECC / parity) when reading from or writing to system

memory.

27 Interface Fatal Error Status (IFS) — R/WC. Indicates that the ICH9 encountered an

error on the SATA interface which caused the transfer to stop.

26 Interface Non-fatal Error Status (INFS) — R/WC. Indicates that the ICH9

encountered an error on the SATA interface but was able to continue operation.

25 Reserved

24 Overflow Stat us (OFS) — R/WC. Indicates that the ICH9 received more bytes from a

device than was specified in the PRD table for the command.

23 Incorrect Port Multiplier Status (IPMS) — R/WC. Indicates that the ICH9 received

a FIS from a device whose Port Multiplier field did not match what was expected.

NOTE: Port Multiplier not supported by ICH9.

PhyRdy Change Status (PRCS) — RO. When set to one indicates the inte rnal PhyRdy

signal changed state. This bit reflects the state of PxSERR.DIAG.N. Unlike most of the

other bits in the register, this bit is RO and is only cleared when PxSERR.DIAG.N is

cleared.

Note that the internal PhyRdy signal also transitions when the port interface enters

partial or slumber power management states. Partial and slumber must be disabled

when Surprise Removal Notification is desired, otherwise the power management state

transitions will appear as false insertion and removal events.

21:8 Reserved

Device Interlock Status (DIS) — R/WC. When set, indicates th at a platform interlock

switch has been opened or closed, which may lead to a change in the connection state

of the device. This bit is only valid in systems that support an interlock switch (CAP.SIS

[ABAR+00:bit 28] set).

For systems that do not support an interlock switch, th is bit will always be 0.

Port Connect Change Status (PCS) — RO. This bit reflects the state of

PxSERR.DIAG.X. (ABAR+130h/1D0h/230h/2D0h, bit 26) Unlike other bits in this

0 = No change in Current Connect Status.

1 = Change in Current Connect Status.

5Descriptor Processed (DPS) — R/WC. A PRD with the I bit set h a s transferred al l it s

data.

SATA Controller Registers (D31:F2)

592 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.4.3.6 PxIE—Port [5:0] Interrupt Enable Register (D31:F2)

Address Offset: Port 0: ABAR + 114h Attribute: R/W, RO

Port 1: ABAR + 194h

Port 2: ABAR + 214h (Desktop Only)

Port 3: ABAR + 294h (Desktop Only)

Port 4: ABAR + 314h

Port 5: ABAR + 394h

Default Value: 00000000h Size: 32 bits

This register enables and disables the reporting of the corresponding interrupt to

system software. When a bit is set (‘1’) and the corresponding interrupt condition is

active, then an interrupt is generated. Interrupt sources that are disabled (‘0’) are still

reflected in the status registers.

Unknown FIS Interrupt (UFS) — RO. When set to ‘1’ in dicate s that an u nknown FIS

was received and has been copied into system memory. This bit is cleared to ‘0’ by

software clearing the PxSERR.DIAG.F bit to ‘0’. Note that this bit does not directly

reflect the PxSERR.DIAG.F bit. PxSERR.DIAG.F is set immediately when an unknown

FIS is detected, wh ereas this bit is set when the FIS is posted to memory. Software

should wait to act on an unknown FIS until this bit is set t o ‘1’ or the two bits may

become out of sync.

3Set Device Bits Interrupt (SDBS) — R/WC. A Set Device Bits FIS has been received

with the I bit set and has been copied into system memory.

2DMA Setup FIS Interrupt (DSS) — R/WC. A DMA Setup FIS has been received with

the I bit set and has been copied into system memory.

1PIO Setup FIS Interrupt (PSS) — R/WC. A PIO Setup FIS has been received with the

I bit set, it has been copied into system memory, and the data related to that FIS has

been transferred.

0Device to Host Register FIS Interrupt (DHRS) — R/WC. A D2H Register FIS has

been received with the I bit set, and has been copi ed into system memory.

Bit Description

31 Cold Presence Detect Enable (CPDE) — RO. Cold Presence Detect is not supporte d .

30 Task File Error Enable (TFEE) — R/W. When set, and GHC.IE and PxTFD.STS.ERR

(due to a reception of the error register from a received FIS) are set, the Intel® ICH9

will generate an interrupt.

29 Host Bus Fatal Error Enable (HBFE) — R/W. When set, and GHC.IE and PxS.HBFS

are set, the ICH9 will generate an interrupt.

28 Host Bus Data Error Enable (HBDE) — R/W. When set, and GHC.IE and PxS.HBDS

are set, the ICH9 will generate an interrupt.

27 Host Bus Data Error Enable (HBDE) — R/W. When set, GHC.IE is set, and

PxIS.HBDS is set, the ICH9 will generate an interrupt.

26 Interface Non-fatal Error Enable (INFE) — R/W. When set, GHC.IE is set, and

PxIS.INFS is set, the ICH9 will generate an interrupt.

25 Reserved

24 Overflow Error Enable (OFE) — R/W. When set, and GHC.IE and PxS.OFS are set,

the ICH9 will generate an interrupt.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 593

SATA Controller Registers (D31:F2)

23 Incorrect Port Multiplier Enable (IPME) — R/W. When set, and GHC.IE and

PxIS.IPMS are set, the ICH9 will generate an interrupt.

NOTE: Should be written as 0. Port Multiplier not supported by ICH9.

22 PhyRdy Change Interrupt Enable (PRCE) — R/W . When set, and GHC.IE is set, and

PxIS.PRCS is set, the ICH9 shall generate an interrupt.

21:8 Reserved

7Device Interlock Enable (DIE) — R/W. When set, and PxIS.DIS is set, the ICH9 will

generate an interrupt.

For systems that do not support an interlock switch, this bit shall be a read-only 0.

6Port Change Interrupt Enable (PCE) — R/W. When set, and GHC.IE and PxS.PCS

are set, the ICH9 will generate an interrupt.

5Descriptor Processed Interrupt Enable (DPE) — R/W . When set, and GHC.IE and

PxS.DPS are set, the ICH9 will generate an interrupt

4Unknown FIS Interrupt Enable (UFIE) — R/W. When set, and GHC.IE is set and an

unknown FI S is received, the ICH9 will generate thi s interrupt.

3Set Device Bits FIS Interrupt Enable (SDBE) — R/W. When set, and GHC.IE and

PxS.SDBS are set, the ICH9 will generate an interrupt.

2DMA Setup FIS Interrupt Enable (DSE) — R/ W. When set, and GHC.IE and PxS.DSS

are set, the ICH9 will generate an interrupt.

1PIO Setup FIS Interrupt Enable (PSE) — R/W. When set, and GHC.IE and PxS.PSS

are set, the ICH9 will generate an interrupt.

0Device to Host Register FIS Interrupt Enable (DHRE) — R/W. When set, and

GHC.IE and PxS.DHRS are set, the ICH9 will generate an interrupt.

Bit Description

SATA Controller Registers (D31:F2)

594 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.4.3.7 PxCMD—Port [5:0] Command Register (D31:F2)

Address Offset: Port 0: ABAR + 118h Attribute: R/W, RO, R/WO

Port 1: ABAR + 198h

Port 2: ABAR + 218h (Desktop Only)

Port 3: ABAR + 298h (Desktop Only)

Port 4: ABAR + 318h

Port 5: ABAR + 398h

Default Value: 0000w00wh Size: 32 bits

where w = 00?0b (for? , see bit description)

Function Level Reset:No (Bit 21, 19 and 18 only)

Bit Description

31:28

Interface Communication Co ntrol (ICC) — R/W. This is a four bit field which can

be used to control reset and power states of the interface. Writes to this field will

cause actions on the interface, either as primitives or an OOB sequence, and the

resulting status of the interface will be reported in the PxSSTS register (Address

offset Port 0:ABAR+124h, Port 1: ABAR+1A4h, Port 2: ABAR+224h, Port 3:

ABAR+2A4h, Port 4: ABAR+224h, Port 5: ABAR+2A4h).

When system software writes a non-reserved value other than No-Op (0h), the ICH9

will perform the action and update this field back to Idle (0h).

If software writes to this field to change the state to a state the link is already in (e.g.

interface is in the active state and a request is made to go to the active state), the

ICH9 will take no action and return this field to Idle.

NOTE: When the ALPE bit (bit 26) is set, then this register should not be set to 02h

or 06h.

Aggressive S lumber / Partial (ASP) — R/W . When set, and the ALPE bit (bit 26) is

set, the ICH9 sh all aggressively enter t he slumber state when it clears the PxCI

ICH9 will aggressively enter the partial state when it clears the PxCI register and the

PxSACT register is cleared. If CAP.SALP is cleared to '0', software shall treat this bit as

reserved.

26 Aggressive Link Power Management Enable (ALPE) — R/W. When set, the ICH9

will aggressively enter a lower link power state (partial or slumber) based upon the

setting of the ASP bit (bit 27).

Value Definition

Fh–7h Reserved

6h Slumber: This will cause the Intel® ICH9 to request a transition of the

interface to the slumber state. The SATA device may reject the request

and the interface will remain in its current state

5h–3h Reserved

2h Partial: This will cause the ICH9 to request a transition of the interface

to the partial st ate. The SATA device may reject the request and the

interface will remain in its current state.

1h Active: This will cause the ICH9 to request a transition of the interface

into the active

0h No-Op / Idle: When software reads this value, it indicates the ICH9 i s

not in the process of changing the interface state or sending a device

reset, and a new link command may be issued.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 595

SATA Controller Registers (D31:F2)

Drive LED on ATAPI Enable (DLAE) — R/W. When set, the ICH9 will drive the LED

pin active for ATAPI commands (PxCLB[CHz.A] set) in addition to ATA commands.

When cleared, the ICH9 will only drive the LED pin active for ATA commands. See

Section 5.16.9 for details on the activity LED.

24 Device is ATAPI (ATAPI) — R/W. When set, the connected device is an ATAPI

device. This bit is used by the ICH9 to control whe ther or not to gener ate the desktop

LED when commands are active. See Section 5.16.9 for details on the activity LED.

23:22 Reserved

External SATA Port (ESP) — R/WO.

0 = This port supports internal SATA devices only.

1 = This port will be used with an external SATA device. When set, CAP .SXS must also

be set.

This bit is not reset by Function Level Reset.

20 Reserved

Interlock Switch Attached to Port (ISP) — R/WO. When interlock switches are

supported in the platform (CAP.SIS [ABAR+00h:bit 28] set), this indicates whether

this particular port has an interlock switch attached. This bit can be used by system

software to enable su ch features as aggressive power management, as disconnects

can always be detected regardless of PHY state with an interlock switch. When this bit

is set, it is expected that HPCP (bit 18) in this register is also set.

The ICH9 takes no action on the state of this bit – it is for system software only. For

example, if this bit is cle ared, and an interlock switch toggles, the ICH9 still treats it

as a proper interlock switch event.

Note that these bits are not reset on a Controller reset.

This bit is not reset by Function Level Reset.

Hot Plug Capable Port (HPCP) — R/WO.

0 = Port is not capable of Hot-Plug.

1 = Port is Hot-Plug capable.

This indicates whether the platform exposes this port to a device which can be Hot-

Plugged. SATA b y definition is hot-pluggable, but not all platforms are constructed to

allow the device to be removed (it may be screwed into the chassis, for example).

This bit can be use d by system software to i ndicate a feature such as “eject device” to

the end-user. The ICH9 takes no action on the state of this bit - it is for system

software only. For example, if this bit is cleared, and a Hot-Plug event occurs, the

ICH9 still treats it as a proper Hot-Plug event.

Note that these bits are not reset on a Controller reset.

This bit is not reset by Function Level Reset.

17 Reserved

16 Port Multiplier FIS Based Switching Enable (PMFSE) — RO. The ICH9 does not support

FIS-based switch ing.

NOTE: FIS Port Multiplier not supported by ICH9.

15 Controller Running (CR) — RO. When this bit is set, the DMA engin es for a port are

running. See section 5.2.2 of the Serial ATA AHCI Specification for details on when

this bit is set and cleared by the ICH9.

14 FIS Receive Running (FR) — RO. When set, the F I S Receive DMA engine for the

port is running. See section 12.2.2 of the Serial ATA AHCI Specification for details on

when this bit is set and cleared by the ICH9.

Bit Description

SATA Controller Registers (D31:F2)

596 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Interlock Switch State (I S S) — RO. For systems that support interlock switches

(via CAP.SIS [ABAR+00h:bit 28]), if an interlock switc h e xists o n this port (via ISP in

this register), this bit indicates the current state of the interlock switch. A 0 indicates

the switch is closed, and a 1 indicates the switch is opened.

For systems that do not support interlock switches, or if an interlock switch is not

attached to this port, this bit reports 0.

12:8

Current Command Slot (CCS) — RO. Indi cates the current command slot the I CH9

is processing. This field is valid when the ST bit is set in this register, and is constantly

updated by the ICH9. This field can be updated as soon as the ICH9 recognizes an

active command slot, or at some point soon after when it begins processing the

command.

This field is used by software to dete rmine the curre nt command iss ue location of the

ICH9. In queued mode, software shall not use this field, as its value does not

represent the current command being executed. Software shall only use PxCI and

PxSACT when running queued commands.

7:5 Reserved

FIS Receive Enable (FRE) — R/W. When set, the ICH9 may post received FISes

into the FIS receive area pointed to by PxFB (ABAR+108h/188h/208h/288h) and

PxFBU (ABAR+10Ch/18Ch/20Ch/28Ch). When cleared, received FISes are not

accepted by the ICH9, ex ce pt for t he f irst D2H (devi ce- to-host) regist er FIS afte r th e

initialization sequence.

System software must not set this bit until PxFB (PxFBU) have been programmed

with a valid pointer to the FIS receiv e area, and if software wishes to move the base,

this bit must first be cleared, and software must wait for the FR bit (bit 14) in this

Command List Override (CLO) — R/W. Setting this bit to '1' causes

PxTFD.STS .BSY and PxTFD.STS .DRQ to be cleared to '0'. This allows a software reset

to be transmitted to the device regardless of whether the BSY and DRQ bits are still

set in the PxTFD.ST S regis te r. The Controller sets th is bit to '0' when PxTFD.STS.BSY

and PxTFD.STS.DRQ have been cleared to '0'. A write to this register with a value of

'0' shall have no effect.

This bit shall only be set to '1' immediately prior to setting the PxCMD.ST bit to '1'

from a previous value of '0'. Setting this bit to '1' at any other time is not supported

and will result in indeterminate behavi or. Softw are must wait for CLO to be cleared to

'0' before setting PxCMD.ST to '1'.

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 597

SATA Controller Registers (D31:F2)

14.4.3.8 PxTFD—Port [5:0] Task File Data Register (D31:F2)

Address Offset: Port 0: ABAR + 120h Attribute: RO

Port 1: ABAR + 1A0h

Port 2: ABAR + 220h (Desktop Only)

Port 3: ABAR + 2A0h (Desktop Only)

Port 4: ABAR + 320h

Port 5: ABAR + 3A0h

Default Value: 0000007Fh Size: 32 bits

This is a 32-bit register that copies specific fie lds of the task file when FISes are

received. The FISes that contain this information are:

D2H Register FIS

PIO Setup FIS

Set Device Bits FIS

2Power On Device (POD) — RO. Cold presence detect not supported. Defaults to 1.

Spin-Up Device (SUD) — R/W / RO

This bit is R/W and defaults to 0 for systems that support stagg ered spin-up (R/W

when CAP.SSS (ABAR+00h:bit 27) is 1). Bit is RO 1 for systems that do not support

staggered spin-up (when CAP.SSS is 0).

0 = No action.

1 = On an edge detect from 0 to 1, the ICH9 starts a COM RESET initialization

sequence to the device.

Clearing this bit to '0' does not cause any OOB signal to be sent on the inte rface.

When this bit is cleared to '0' and PxSCTL.DET=0h, the Controller will enter listen

mode.

Start (ST) — R/W. When set, the ICH9 may process the command list. When

cleared, the ICH9 may not process the command list. Whenever this bit is changed

from a 0 to a 1, the ICH9 st arts processing the com mand list at entry 0. Whenever

this bit is changed from a 1 to a 0, the PxCI register is cleared by the ICH9 upon the

ICH9 putting the controller into an idle state.

Refer t o s ection 12. 2. 1 of the Seri al ATA AHCI Specification for important restrictions

on when ST can be set t o 1.

Bit Description

31:16 Reserved

15:8 Error (ERR) — RO. Contains the latest copy of the task file error register.

7:0

Status (STS) — RO. Contains the latest copy of the task file status register. Fields of

note in this register that affect AHCI.

Bit Field Definition

7 BSY Indicates the i nterface is busy

6:4 N/A Not applicable

3 DRQ Indicates a data transfer is requested

2:1 N/A Not applicable

0 ERR Indicates an error during the transfer

SATA Controller Registers (D31:F2)

598 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.4.3.9 PxSIG—Port [5:0] Signature Register (D31:F2)

Address Offset: Port 0: ABAR + 124h Attribute: RO

Port 1: ABAR + 1A4h

Port 2: ABAR + 224h (Desktop Only)

Port 3: ABAR + 2A4h (Desktop Only)

Port 4: ABAR + 324h

Port 5: ABAR + 3A4h

Default Value: FFFFFFFFh Size: 32 bits

This is a 32-bit register which contains the initial signature of an attached device when

the first D2H Register FIS is received from that device. It is updated once after a reset

sequence.

Bit Description

31:0

Signature (S IG) — RO. Contains the signature received from a device on the first D2H

Bit Field

31:24 LBA High Register

23:16 LBA Mid Register

15:8 LB A Low Register

7:0 S ector Count Register

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 599

SATA Controller Registers (D31:F2)

14.4.3.10 PxSSTS—Port [5:0] Serial ATA Status Register (D31:F2)

Address Offset: Port 0: ABAR + 128h Attribute: RO

Port 1: ABAR + 1A8h

Port 2: ABAR + 228h (Desktop Only)

Port 3: ABAR + 2A8h (Desktop Only)

Port 4: ABAR + 328h

Port 5: ABAR + 3A8h

Default Value: 00000000h Size: 32 bits

This is a 32-bit register that conveys the current state of the interface and host. The

ICH9 updates it continuously and asynchronously. When the ICH9 transmits a

COMRESET to the device, this register is updated to its reset values.

Bit Description

31:12 Reserved

11:8

Interface Power Management (IPM) — RO. Indicates the current interface state:

All other values reserved.

7:4

Current Interface Speed (SPD) — RO. Indicates the negotiated interface

communication speed.

All other values reserved.

ICH9 Supports Generation 1 communication rates (1.5 Gb/s) and Gen 2 rates (3.0 Gb/

s).

3:0

Device Detection (DET) — RO. Indicates the in terface device detection and Phy

state:

All other values reserved.

Value Description

0h Device not present or communication not established

1h Interface in active state

2h Interface in PARTIAL power management state

6h Interface in SLUMBER power management state

Value Description

0h Device not present or communication not established

1h Generation 1 communication rate negotiated

2h Generation 2 communication rate negotiated

Value Description

0h No device detected and Phy communication not established

1h Device presen ce detected but Phy communication not esta blished

3h Device presence detected an d Phy communication established

4h Phy in offline mode as a result of the interface being disabled or

running in a BI ST loopback mode

SATA Controller Registers (D31:F2)

600 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

14.4.3.11 PxSCTL — Port [5:0] Serial ATA Contro l Register (D31:F2)

Address Offset: Port 0: ABAR + 12Ch Attribute: R/W, RO

Port 1: ABAR + 1ACh

Port 2: ABAR + 22Ch (Desktop Only)

Port 3: ABAR + 2ACh (Desktop Only)

Port 4: ABAR + 32Ch

Port 5: ABAR + 3ACh

Default Value: 00000004h Size: 32 bits

This is a 32-bit read-write register by which software controls SATA capabilities. Writes

to the SControl register result in an action being taken by the ICH9 or the interface.

Reads from the register return the last value written to it.

Bit Description

31:20 Reserved

19:16 Port Multiplier Port (PMP) — R/W. This field is not used by AHCI

15:12 Select Power Management (SPM) — R/W. This field is not used by AHCI

11:8

Interface Power Management Transitions Allowed (IPM) — R/W. Indicates which

power states the ICH9 is allowed to transition to:

All other values reserved

7:4

Speed Allowed (SPD) — R/W. Indicates the highest allowable speed of the interface.

This speed is limited by the CAP.ISS (ABAR+00h:bit 23:20) field.

ICH9 Supports Generation 1 communication rates (1.5 Gb/s) and Gen 2 rates

(3.0 Gb/s).

Value Description

0h No interface restrictions

1h Transitions to the PARTIAL state disabled

2h Transitions to the SLUMBER state disabled

3h Transitions to both PARTIAL and SLUMBER states disabled

Value Description

0h No speed negotiation restrictions

1h Limit speed negotiation to Generation 1 communication rate

2h Limit speed negotiation to Generation 2 communication rate

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 601

SATA Controller Registers (D31:F2)

14.4.3.12 PxSERR—Port [5:0] Serial ATA Error Register (D31:F2)

Address Offset: Port 0: ABAR + 130h Attribute: R/WC

Port 1: ABAR + 1B0h

Port 2: ABAR + 230h (Desktop Only)

Port 3: ABAR + 2B0h (Desktop Only)

Port 4: ABAR + 330h

Port 5: ABAR + 3B0h

Default Value: 00000000h Size: 32 bits

Bits 26:16 of this register contains diagnostic error information for use by diagnostic software in

validating correct oper ation or isolating fai lure modes. Bits 11:0 contain error info rmation used by

host software in determining the appropriate response to the error condition. If one or more of

bits 11:8 of this register are set, the controller will stop the current transfer.

3:0

Device Detection Initialization (DET) — R/W. Controls the ICH9’s device detection

and interface initialization.

All other values reserved.

When this field is written to a 1 h, the ICH9 initiates COMRESET and starts the

initialization process. When the initialization is complete, this field shall remain 1h until

set to another value by software.

This field may only be changed to 1h or 4h when PxCMD.ST is 0. Changing this field

while the ICH9 is running results in undefined behavior.

Note: It is permissible to implement any of the Serial ATA defined behaviors for

transmission of COMRESET when DET=1h.

Bit Description

Value Description

0h No device detectio n or initializatio n action requested

Perform interface communication initialization sequence to

establish com munication. This is functionally equivalent to a hard

reset and results in the interface being reset and communications

re-initialized

4h Disable the Serial ATA interface and put Phy in offline mode

Bit Description

31:27 Reserved

Exchanged (X) — R/WC. When set to one this bit indicates that a change in device

presence has been detected since the last time this bit was c leared. This bit shall

always be set to 1 anytime a COMINIT signal is received. This bit is reflected in the

P0IS.PCS bit.

25 Unrecognized FIS Type (F) — R/WC. Indicates that one or more FISs were received

by the Transport layer with good CRC, but had a type field that was not recognized.

24 Transport state transition error (T) — R/WC. Indicates that an error has occurred in

the transition from one state to another within the Transport layer since the last tim e

this bit was cleared.

23 Transport state transition error (T) — R/WC. Indicates that an error has occurred in

the transition from one state to another within the Transport layer since the last tim e

this bit was cleared.

SATA Controller Registers (D31:F2)

602 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Handshake (H) — R/WC. Indicates that one or more R_ERR handshake response was

received in response to frame transmission. Such errors may be the result of a CRC

error detected by the recipient, a disparity or 8b/10b decoding error, or other error

condition leading to a negative handshake on a transmitted frame.

21 CRC Error (C) — R/WC. Indicates that one or more CRC errors occurred with the Link

Layer.

20 Disparity Error (D) — R/WC . This field is not used by AHCI.

19 10b to 8b Decode Error (B) — R/WC. Indicates that one or more 10b to 8b decoding

errors occurred.

18 Comm Wake (W) — R/WC. Indicates that a Comm Wake signal was detected by the

Phy.

17 Phy Internal Error (I) — R/WC. Indicates that the Phy detected some internal error.

PhyRdy Change (N) — R/WC. When set to 1 this bit indicates that the internal PhyRdy

signal changed state since the last time this bit was cleared. In the ICH9, this bit will be

set when PhyRdy changes from a 0 -> 1 or a 1 -> 0. The state of this bit is then

reflected in the PxIS.PRCS interrupt status bit and an interrupt will be generated if

enabled. Software clears this bit by writing a 1 to it.

15:12 Reserved

11 Internal E rror (E) — R /WC. The SAT A controller fai led due to a master or target abort

when attempting to access system memory.

10 Protocol Error (P) — R/WC. A violation of the Serial ATA protocol was detected.

Note: The ICH9 does not set this bit for all protocol violations that may occur on the

SATA link.

Persistent Communication or Data Integrity Error (C) — R/WC. A communication

error that was not recovered occurred that is expected to be persistent. Persistent

communications errors may arise from faulty interconnect with the device, from a

device that has been removed or has failed, or a number of other causes.

8Transient Data I ntegrity Error (T ) — R/WC. A data integrity error o ccurred that was

not recovered by the interface.

7:2 Reserved.

Recovered Communications Error (M) — R/WC. Communications between the

device and host was temporarily lost but was re-established. This can arise from a

device temporarily being removed, from a temporary loss of Phy synchronization, or

from other causes and may be derived from the PhyNRdy signal between the Phy and

Link layers.

0Recovered Data Integrity Error (I) — R/WC. A data integrity error occurred that

was recovered by the interface through a retry operation or other recovery action.

Bit Description

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 603

SATA Controller Registers (D31:F2)

14.4.3.13 PxSACT—Port [5:0] Serial ATA Active (D31:F2)

Address Offset: Port 0: ABAR + 134h Attribute: R/W

Port 1: ABAR + 1B4h

Port 2: ABAR + 234h (Desktop Only)

Port 3: ABAR + 2B4h (Desktop Only)

Port 4: ABAR + 334h

Port 5: ABAR + 3B4h

Default Value: 00000000h Size: 32 bits

14.4.3.14 PxCI—Port [5:0] Command Issue Register (D31:F2)

Address Offset: Port 0: ABAR + 138h Attribute: R/W

Port 1: ABAR + 1B8h

Port 2: ABAR + 238h (Desktop Only)

Port 3: ABAR + 2B8h (Desktop Only)

Port 4: ABAR + 338h

Port 5: ABAR + 3B8h

Default Value: 00000000h Size: 32 bits

§ §

Bit Description

31:0

Device Status (DS) — R/W. System software sets this bit for SA T A queuing operations

prior to setting the PxCI.CI bit in the same command slot entry. This fiel d is clea red via

the Set Device Bits FIS.

This field is also cleared when PxCMD.ST (ABAR+118h/198h/218h/298h:bit 0) is

cleared by software, and as a result of a COMRESET or SRST.

Bit Description

31:0

Commands Issued (CI) — R/W. This field is set by software to indicate to the ICH9

that a command has been built-in system memory for a command slot and may be sent

to the device. Wh en th e ICH9 re ceiv es a FI S which clears the B SY and DRQ bits for the

command, it clears the corresponding bit in th is register for that command slot. Bits in

this field shall only be set to '1' by software when PxCMD.ST is set to '1'.

This field is also cleared when PxCMD.ST (ABAR+118h/198h/218h/298h:bit 0) is

cleared by software.

SATA Controller Registers (D31:F2)

604 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 605

SATA Controller Registers (D31:F5)

15 SATA Controller Registers

(D31:F5)

15.1 PCI Configuration Registers (SATA–D31:F5)

Note: Address locations that are not shown should be treated as Reserved.

All of the SATA registers are in the core well. None of the registers can be locked.

Table 15-1. SATA Controller PCI Register Address Map (S ATA–D31:F5) (Sheet 1 of 2)

Offset Mnemonic Register Name Default Type

00h–01h VID Vendor Identific ati on 8086h RO

02h–03h DID Device Identification See register

description RO

04h–05h PCICMD PCI Command 0000h R/W, RO

06h–07h PCISTS PCI Status 02B0h R/WC, RO

08h RID Revision Identification See register

description RO

09h PI Programming Interface See re gister

description

See

description

0Ah SCC Sub Class Code See register

description

See

description

0Bh BCC Base Class Code 01h RO

0Dh PMLT Primary Master Latency Timer 00h RO

10h–13h PCMD_BAR Primary Command Block Base Address 00000001h R/W, RO

14h–17h PCNL_BAR Primary Control Block Base Address 00000001h R/W, RO

18h–1Bh SCMD_BAR Secondary Command Block Base

Address 00000001h R/W, RO

1Ch–1Fh SCNL_BAR Secondary Control Block Base Address 00000001h R/W, RO

20h–23h BAR Legacy Bus Master Base Address 00000001h R/W, RO

24h–27h SIDPBA Serial ATA Index / Data Pair Base

Address 00000000h See

description

2Ch–2Dh SVID Subsystem Vendor Identification 0000h R/WO

2Eh–2Fh SID Subsystem Identification 0000h R/WO

34h CAP Capabilities Pointer 80h RO

3Ch INT_LN Interrupt Line 00h R/W

3Dh INT_PN Interrupt Pin See register

description RO

40h-41h IDE_TIM Primary IDE Timing Register 0000h R/W

42h-43h IDE_TIM Secondary IDE Timing Registers 0000h R/W

SATA Controller Registers (D31:F5)

606 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

NOTE: The ICH9 SATA controller is not arbitrated as a PCI device, therefore it does not nee d a

master latency timer.

15.1.1 VID—Vendor Identification Register (SATA—D31:F5)

Offset Address: 00h–01h Attribute: RO

Default Value: 8086h Size: 16 bit

Lockable: No Power Well: Core

70h–71h PID PCI Power Management Capability ID See regist er

description RO

72h–73h PC PCI Power Management Capabilities 4003h RO

74h–75h PMCS PCI Power Management Control and

Status 0008h R/W, RO,

R/WC

80h–81h MSICI Message Signaled Interrupt Capability

ID 7005h RO

82h–83h MSIMC Message Signaled Interrupt Message

Control 0000h RO, R/W

84h–87h MSIMA Message Signaled Interrupt Message

Address 00000000h RO, R/W

88h–89h MSIMD Message Signaled Interrupt Message

Data 0000h R/W

90h MAP Address Map 00h R/W

92h–93h PCS Port Control and Status 0000h R/W, RO,

R/WC

A8h–ABh SCAP0 SATA Capability Register 0 0010B012h RO

ACh–AFh SCAP1 SATA Capability Register 1 00000048h RO

B0h–B1h FLRCID FLR Capability ID 0009h RO

B2h–B3h FLRCLV FLR Capability Length and Value 2006h RO

B4h–B5h FLRCTRL FLR Control 0000h R/W, RO

C0h ATC APM Trapping Control 00h R/W

C4h ATS ATM Trapping Status 00h R/WC

Table 15-1. SATA Controller PCI Register Address Map (SATA–D31:F5) (Sheet 2 of 2)

Offset Mnemonic Register Name Default Type

Bit Description

15:0 Vendor ID — RO. This is a 16-bit value assigned to Intel. Intel VID = 8086h

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 607

SATA Controller Registers (D31:F5)

15.1.2 DID—Device Identification Register (SATA—D31:F5)

Offset Address: 02h–03h Attribute: RO

Default Value: See bit description Size: 16 bit

Lockable: No Power Well: Core

15.1.3 PCICMD—PCI Command Register (SATA–D31:F5)

Address Offset: 04h–05h Attribute: RO, R/W

Default Value: 0000h Size: 16 bits

Bit Description

15:0 Device ID — RO. This is a 16-bit value assigned to the Intel® ICH9 SATA controller.

NOTE: The value of this fiel d will change dependent u p on the value of the MAP

Bit Description

15:11 Reserved

Interrupt Disable — R/W. This disables pin-based INTx# interrupts. This bit has no

effect on MSI operation.

0 = Int ernal INTx# messages are generated if there is an interrupt and MSI is not

enabled.

1 = Int ernal INTx# messages will not be generated.

9 Fast Back to Back Enable (FBE) — RO. Reserved as 0.

8 SERR# Enable (SERR_EN) — RO. Reserved as 0.

7 Wait Cycle Control (WCC) — RO. Reserved as 0.

Parity Error Response (PER) — R/W.

0 = Disabled. SATA controller will not generate PERR# when a data parity error is

detected.

1 = Enabled. SATA controller will generate PERR# when a data parity error is detected.

5 VGA Palette Snoop (VPS) — RO. Reserved as 0.

4 Postable Memory Write Enable (PMWE) — RO. Reserved as 0.

3 Special Cycle Enable (SCE) — RO. Reserved as 0.

2Bus Master Enable (BME) — R/W. This bit controls the ICH9’s ability to act as a PCI

master for IDE Bus Master transfers. This bit does not impact the generation of

completions for split transaction commands.

1Memory Space Enable (MSE) — RO. This controller does not support AHCI, therefore

no memory space is required.

I/O Space Enable (IOSE) — R/W. This bit controls access to the I/O space registers.

0 = Disables access to the Legacy or Native IDE ports (both Primary and Secondary) as

well as the Bus Master I/O registers.

1 = Enable. Note that the Base Address register for the Bus Master registers should be

programmed before this bit is set.

SATA Controller Registers (D31:F5)

608 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

15.1.4 PCISTS — PCI Status Register (SATA–D31:F5)

Address Offset: 06h–07h Attribute: R/WC, RO

Default Value: 02B0h Size: 16 bits

Note: For the writable bits, software must write a 1 to clear bits that are set. Writing a 0 to

the bit has no effect.

15.1.5 RID—Revision Identificati on Register (SATA—D31:F5)

Offset Address: 08h Attribute: RO

Default Value: See bit description Size: 8 bits

Bit Description

15 Detected Parity Error (DPE) — R/WC.

0 = No parity error detected by SATA controller.

1 = SATA controller detects a parity error on its interface.

14 Signaled System Err or (S SE) — RO. Reserved as 0.

13 Received Master Abort (RMA) — R/WC.

0 = Master abort Not generated.

1 = SATA controller, as a master, generated a master abort.

12 Reserved

11 Signaled Target Abort (STA) — RO. Reserved as 0.

10:9 DEVSEL# Timing Status (DEV_STS) — RO.

01 = Hardwired; Controls the device select time for the SAT A controller’s PCI interface.

Data Parity Error Detected (DPED) — R/WC. For ICH9, this bit can only be set on

read completions received from SiBUS where there is a parity error.

1 = SATA controller, as a master, either detects a parity error or sees the parity error

line asserted, and the parity error response bit (bit 6 of the command register) is

set.

7Fast Back to Back Capable (FB2BC) — RO. Reserved as 1.

6User Definable Features (UDF ) — RO. Reserved as 0.

566MHz Capable (66MHZ_CAP) — RO. Reserved as 1.

4Capabilities List (CAP_LIST) — RO. This bit indicates the presen ce of a capabilities

list. The m inimum requirement for the capabilit ies list must be PCI power management

for the SATA controller.

Interrupt Status (INTS) — RO. Reflects the state of INTx# messages, IRQ14 or

IRQ15.

0 = Interrupt is cleared (independent of the state of Interrupt Disable bit in the

command register [offset 04h]).

1 = Interrupt is to be asserted

2:0 Reserved

Bit Description

7:0 Revision ID — RO. Refer to the Intel® I/O Controller Hub (ICH9) Family Specification

Update for the value of the Revision ID Register

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 609

SATA Controller Registers (D31:F5)

15.1.6 PI—Programming Interface Register (SATA–D31:F5)

Address Offset: 09h Attribute: RO

Default Value: 85h Size: 8 bits

When SCC = 01h

15.1.7 SCC—Sub Class Code Register (SATA–D31:F5)

Address Offset: 0Ah Attribute: RO

Default Value: 01h Size: 8 bits

15.1.8 BCC—Base Class Code Register (SATA–D31:F5)

Address Offset: 0Bh Attribute: RO

Default Value: 01h Size: 8 bits

Bit Description

7 This read-only bit is a 1 to indicate that the ICH9 supports bus master operation

6:4 Reserved.

Secondary Mode Native Capable (SNC) — RO. Indicates whether or not the

secondary channel has a fixed mode of operation.

0 = Indicates the mode is fixed and is determined by the (rea d-only) value of bit 2.

This bit will always return ‘0’.

Secondary Mode Native Enable (SNE) — RO.

Determines the mode that the secondary channel is operating in.

1 = Secondary controller operating in native PCI mode.

This bit will always return ‘1’.

Primary Mode Native Capable (PNC) — RO. Indicates whether or not the primary

channel has a fixed mode of operation.

0 = Indicates the mode is fixed and is determined by the (rea d-only) value of bit 0.

This bit will always return ‘0’.

Primary Mode Native Enable (PNE) — RO.

Determines the mode that the primary channel is operating in.

1 = Primary controller operating in native PCI mode.

This bit will always return ‘1’.

Bit Description

7:0 Sub Class Code (SCC ) — RO.

The value of this field determines whether the controller supports legacy IDE mode.

Bit Description

7:0 Base Class Code (BCC) — RO.

01h = Mass storage device

SATA Controller Registers (D31:F5)

610 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

15.1.9 PMLT—Primary Master Latency Timer Register

(SATA–D31:F5)

Address Offset: 0Dh Attribute: RO

Default Value: 00h Size: 8 bits

15.1.10 PCMD_BAR—Primary Command Blo ck Base Address

Address Offset: 10h–13h Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

NOTE: This 8-byte I/O space is used in native mode for the Primary Controller’s Command Block.

15.1.11 PCNL_BAR—Primary Control Block Base Address Register

(SATA–D31:F5)

Address Offset: 14h–17h Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

NOTE: This 4-byte I/O space is used in native mode for the Primary Controller’s Command Block.

Bit Description

7:0 Master Latency Timer Count (MLTC) — RO.

00h = Hardwired. The SATA controller is implemented internally, and is not arbitrated

as a PCI device, so it does not need a Master Latency Timer.

Bit Description

31:16 Reserved

15:3 Base Address — R/W. This field provides the base address of the I/O space (8

consecutive I/O locations).

2:1 Reserved

0Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

Bit Description

31:16 Reserved

15:2 Base Address — R/W. This field provides the base address of the I/O space (4

consecutive I/O locations).

1 Reserved

0 Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 611

SATA Controller Registers (D31:F5)

15.1.12 SCMD_BAR—Secondary Command Block Base Address

Address Offset: 18h–1Bh Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

NOTE: This 8-byte I/O spa ce is used in native mode for the Secondary Controller’s Command

Block.

15.1.13 SCNL_BAR—Secondary Co ntrol Block Base Address

Address Offset: 1Ch –1Fh Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

NOTE: This 4-byte I/O spa ce is used in native mode for the Secondary Controller’s Command

Block.

Bit Description

31:16 Reserved

15:3 Base Address — R/W. This field provides the base address of the I/O space (8

consecutive I/O locations).

2:1 Reserved

0Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

Bit Description

31:16 Reserved

15:2 Base Address — R/W. This field provides the base address of the I/O space (4

consecutive I/O locations).

1 Reserved

0Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

SATA Controller Registers (D31:F5)

612 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

15.1.14 BAR — Legacy Bus Master Base Address Register

(SATA–D31:F5)

Address Offset: 20h–23h Attribute: R/W, RO

Default Value: 00000001h Size: 32 bits

The Bus Master IDE interface function uses Base Address register 5 to request a 16-

byte IO space to provide a software interface to the Bus Master functions. Only 12

bytes are actually used (6 bytes for primary, 6 bytes for secondary). Only bits [15:4]

are used to decode the address.

15.1.15 SIDPBA — SATA Index/Data Pair Base Address Register

(SATA–D31:F5)

Address Offset: 24h–27h Attribute: R/W, RO

Default Value: 00000000h Size: 32 bits

When SCC is 01h

When the programming interface is IDE, the register represents an I/O BAR allocating

16B of I/O space for the I/O mapped registers defined in Section 15.4. Note that

although 16B of locations are allocated, some maybe reserved.

Bit Description

31:16 Reserved

15:5 Base Address — R/W. This field provides the base address of the I/O space (16

consecutive I/O locations).

4Base Address 4 (BA4)— R/W.

When SCC is 01h, this bit will be R/W resulting in requesting 16B of I/O space.

3:1 Reserved

0Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

Bit Description

31:16 Reserved

15:4 Base Address (BA) — R/W. Base addres s of register I/O space

3:1 Reserved

0Resource Type Indicator (RTE) — RO. Hardwired to 1 to indicate a request for I/O

space.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 613

SATA Controller Registers (D31:F5)

15.1.16 SVID—Subsystem Vendor Identification Register

(SATA–D31:F5)

Address Offset: 2Ch –2Dh Attribute: R/WO

Default Value: 0000h Size: 16 bits

Lockable: No Power Well: Core

Function Level Reset: No

15.1.17 SID—Subsystem Identification Register (SATA–D31:F5)

Address Offset: 2Eh–2Fh Attribute: R/WO

Default Value: 0000h Size: 16 bits

Lockable: No Power Well: Core

15.1.18 CAP—Capabilities Pointer Register (SATA–D31:F5)

Address Offset: 34h Attribute: RO

Default Value: 70h Size: 8 bits

15.1.19 INT_LN—Interrupt Line Register (SATA–D31:F5)

Address Offset: 3Ch Attribute: R/W

Default Value: 00h Size: 8 bits

Function Level Reset: No

15.1.20 INT_PN—Interrupt Pin Register (SATA–D31:F5)

Address Offset: 3Dh Attribute: RO

Default Value: See Register Description Size: 8 bits

Bit Description

15:0 Subsystem Vendor ID (SVID) — R/WO. Value is written by BIOS. No hardware

action taken on this value.

Bit Description

15:0 Subsystem ID (SID) — R/WO. Value is written b y BIOS. No hardw are action ta ken on

this value.

Bit Description

7:0 Capabilities Pointer (CAP_PTR) — RO. Indicates that the first capability pointer

offset is 70h if the Sub Class Code (SCC) (Dev 31:F2:0Ah) is configure as IDE mode

(value of 01).

Bit Description

7:0 Interrupt Line — R/W. This f ield is used to co mmunicate to softw are the interrupt li ne

that the interrupt pin is connected to. These bits are not reset by FLR.

Bit Description

7:0 Interrupt Pin — RO. This reflects the value of D31IP.SIP1 (Chipset Config

Registers:Offset 3100h:bits 11:8).

SATA Controller Registers (D31:F5)

614 Intel® I/O Controller Hub 9 (ICH9) Family Datasheet

15.1.21 IDE_TIM — IDE Timing Register (SATA–D31:F5)

Address Offset: Primary: 40h–41h Attribute: R/W

Secondary: 42h–43h

Default Value: 0000h Size: 16 bits

15.1.22 PID—PCI Power Management Capability Identification

Address Offset: 70h–71h Attribute: RO

Default Value: B001h Size: 16 bits

15.1.23 PC—PCI Power Management Capabilities Register

(SATA–D31:F5)

Address Offset: 72h–73h Attribute: RO

Default Value: 4003h Size: 16 bits

Bit Description

IDE Decode Enable (IDE) — R/W. Individually en able/disable the Primary or

Secondary decode.

0 = Disable.

1 = Enables the Intel® ICH9 to decode the associated Command Blocks (1F0–1F7h for

primary, 170–177h for secondary) and Control Block (3F6h for primary and 376h

for secondary).

This bit effects the IDE decode ranges for both legacy and native-Mode decoding.

NOTE: This bit affects SA T A oper ation in both combined and non-combined A TA modes.

See Section 5.16 for more on ATA modes of operation.

14:0 Reserved

Bits Description

15:8 Next Capability (NEXT) — RO. When SCC is 01h, this field will be B0h indicating the

next item is FLR Capability Pointer in the list.

7:0 Capability ID (CID) — RO. Indicates that this pointer is a PCI power management.

Bits Description

15:11 PME Support (PME_SUP) — RO. By default with SCC = 01h, the default value of

00000 indicates no PME support in IDE mode.

10 D2 Supp ort (D2_SUP) — RO. Hardwired to 0. The D2 state is not supported

9 D1 Support (D1_SUP) — RO. Hardwired to 0. The D1 state is not supported

8:6 Auxiliary Current (AUX_CUR) — RO. PME# from D3COLD state is not supported,

therefore this field is 00 0b.

5Device Specifi c Initialization (DSI) — RO. Hardwired to 0 to indicate that no device-

specific initialization is required.

4 Reserved

3PME Clock (PME_CLK) — RO. Hardwired to 0 to indicate that PCI clock is not requ ired to

generate PME#.

2:0 Version (VER) — RO. Hardwired to 011 to indica tes support for Revi sion 1.2 of the PCI

Power Management Specification.

Intel® I/O Controller Hub 9 (ICH9) Family Datasheet 615

SATA Controller Registers (D31:F5)

15.1.24 PMCS—PCI Power Management Control and Status

Address Offset: 74h–75h Attribute: RO, R/W, R/WC

Default Value: 0008h Size: 16 bits

Function Level Reset:No (Bits 8 and 15 only)

15.1.25 MID—Message Signal Interrupt Identifier (SATA–D31:F5)

Address Offset: 80h-81h Attribute: RO

Default Value: 7005h Size: 16 bits

Bits Description

PME Status (PMES) — R/WC. Bit is set when a PME event is to be requested, and if

this bit and PMEE is set, a PME# will be generated from the SATA controlle r.

Note: When SCC=01h this bit will be RO ‘0’. Software is advised to clear PMEE together

with PMES prior to changing SCC through MAP.SMS.

This bit is not reset by Function Level Reset.

14:9 Reserved

PME Enable (PMEE) — R/W. When SCC is not 01h, this bit R/W. When se t, the SATA

controller generates PME# form D3HOT on a wake event.