View NM10_3670567.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

document number: 322896-001 intel? NM10 family express chipset datasheet december 2009 www.datasheet.co.kr datasheet pdf - http://www..net/
2 datasheet information in this document is prov ided in connection with intel products . no license, express or implied, by estoppel or otherwise, to any intellectual proper ty rights is granted by this document. except as provided in intel's terms and condit ions of sale for such products, in tel assumes no liability whatsoever and intel disclaims any express or implied warranty, rela ting to sale and/or use of intel products including liability or warranties relating to fitness for a particul ar purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. unless otherwise agreed in writing by intel, the intel products are not designed nor intended for any application in which the failure of the intel product co uld create a situation where personal injury or death may occur. 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 instructions mark ed ?reserved? or ?undefined.? intel reserves these for future definition and shall have no responsibility wh atsoever for conflicts or incompatibilitie s arising from future changes to them. the information here is subject to change without notice. do not finalize a design with this information. the products described in this document 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. designers must not rely on the absence or characteristics of any features or instructions marked ?reserved? or ?undefined.? int el reserves these for future definition and shall have no responsib ility whatsoever for conflicts or incompatibilities arising fro m future changes to them. i 2 c is a two-wire communications bus/protocol de veloped by philips. smbus is a subset of the i 2 c bus/protocol and was developed by intel. implementations of the i 2 c bus/protocol may require licenses from various entities, including philips electronics n.v. and north american ph ilips corporation. intel, intel speedstep, and the in tel logo are trademarks or regi stered trademarks of intel corp oration or its subsidiaries in the united states and other countries. *other names and brands may be cl aimed as the property of others. copyright ? 2009, intel corporation www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 3 contents 1introduction ............................................................................................................ 30 1.1 intel NM10 family express chipset feature support ............................................... 31 1.2 content layout ................................................................................................. 34 1.3 functions and capabilities ......... ........... ............ ........... .......... ........... ........... ........ 36 2 signal description .................................................................................................... 43 2.1 direct media interface (dmi) to host controller ..................................................... 45 2.2 pci express* .................................................................................................... 45 2.3 platform lan connect interface........................................................................... 45 2.4 eeprom interface ............................................................................................. 46 2.5 firmware hub interface...................................................................................... 46 2.6 pci interface .................................................................................................... 47 2.7 serial ata interface........................................................................................... 49 2.8 lpc interface .................................................................................................... 50 2.9 interrupt interface ............................................................................................ 50 2.10 usb interface ................................................................................................... 51 2.11 power management interface.............................................................................. 52 2.12 processor interface............................................................................................ 54 2.13 smbus interface................................................................................................ 56 2.14 system management interface ............................................................................ 56 2.15 real time clock interface ................................................................................... 56 2.16 other clocks ..................................................................................................... 57 2.17 miscellaneous signals......................................................................................... 57 2.18 intel hd audio link............................................................................................ 58 2.19 serial peripheral interface (spi) ................. ......................................................... 59 2.20 general purpose i/o signals ............................................................................... 59 2.21 power and ground ............................................................................................. 60 2.22 pin straps ........................................................................................................ 61 2.22.1 functional straps ................................................................................... 61 2.22.2 external rtc circuitry ............................................................................. 63 2.23 device and revision id table .............................................................................. 64 3pin states ................................................................................................................ 65 3.1 integrated pull-ups and pull-downs ..................................................................... 65 3.2 output and i/o signals planes and states........ ..................................................... 66 3.3 power planes for input signals ............................................................................ 71 4 chipset and system clock domains ......................................................................... 74 5 functional description ............................................................................................. 76 5.1 pci-to-pci bridge (d30:f0) ................................................................................ 76 5.1.1 pci bus interface ................................................................................... 76 5.1.2 pci bridge as an initiator ........................................................................ 76 5.1.3 parity error detection and generation ....................................................... 78 5.1.4 pcirst# ............................................................................................... 79 5.1.5 peer cycles............................................................................................ 79 5.1.6 pci-to-pci bridge model .......................................................................... 80 5.1.7 idsel to device number mapping............................................................. 80 5.1.8 standard pci bus configuration mechanism ............................................... 80 www.datasheet.co.kr datasheet pdf - http://www..net/
4 datasheet 5.2 pci express* root ports (d28:f0,f1,f2,f3)...........................................................81 5.2.1 interrupt generation ...............................................................................81 5.2.2 power management.................................................................................82 5.2.3 serr# generation ..................................................................................83 5.2.4 hot-plug ................................................................................................84 5.3 lan controller (b1:d8:f0) ..................................................................................86 5.3.1 lan controller pci bus interface...............................................................86 5.3.2 serial eeprom interface ..........................................................................91 5.3.3 csma/cd unit ........................................................................................91 5.3.4 media management interface ...................................................................92 5.3.5 tco functionality ...................................................................................92 5.4 alert standard format (asf) ...............................................................................94 5.4.1 asf management solution features/capab ilities ............ .......... ........... ........95 5.4.2 asf hardware support ............................................................................96 5.4.3 asf software support .............................................................................97 5.5 lpc bridge (w/ system and management functi ons) (d31:f0) .................................98 5.5.1 lpc interface .........................................................................................98 5.5.2 serr# generation ................................................................................ 103 5.6 dma operation (d31:f0) .................................................................................. 104 5.6.1 channel priority.................................................................................... 105 5.6.2 address compatibility mode .... ............ ........... ........... ............ ........... ...... 105 5.6.3 summary of dma transfer sizes ............................................................. 106 5.6.4 autoinitialize ........................................................................................ 106 5.6.5 software commands ............................................................................. 107 5.7 lpc dma ........................................................................................................ 107 5.7.1 asserting dma requests ........................................................................ 107 5.7.2 abandoning dma requests..................................................................... 108 5.7.3 general flow of dma transfers ............................................................... 108 5.7.4 terminal count..................................................................................... 109 5.7.5 verify mode ......................................................................................... 109 5.7.6 dma request deassertion ...................................................................... 109 5.7.7 sync field / ldrq# rules ..................................................................... 110 5.8 8254 timers (d31:f0) ...................................................................................... 111 5.8.1 timer programming .............................................................................. 112 5.8.2 reading from the interval timer ............................................................. 113 5.9 8259 interrupt controllers (pic) (d31:f0)........................................................... 114 5.9.1 interrupt handling ................................................................................ 116 5.9.2 initialization command words (icwx) ..................................................... 117 5.9.3 operation command words (ocw) ......................................................... 118 5.9.4 modes of operation ............................................................................... 118 5.9.5 masking interrupts................................................................................ 121 5.9.6 steering pci interrupts.......................................................................... 121 5.10 advanced programmable interrupt controller (apic) (d31:f0)............................... 122 5.10.1 interrupt handling ................................................................................ 122 5.10.2 interrupt mapping................................................................................. 122 5.10.3 pci / pci express* message-based interrupts .......................................... 123 5.10.4 front side bus interrupt delivery ............................................................ 124 5.11 serial interrupt (d31:f0) .................................................................................. 126 5.11.1 start frame ......................................................................................... 126 5.11.2 data frames ........................................................................................ 126 5.11.3 stop frame.......................................................................................... 127 5.11.4 specific interrupts not supported via serirq........................................... 127 5.11.5 data frame format............................................................................... 127 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 5 5.12 real time clock (d31:f0)................................................................................. 129 5.12.1 update cycles ...................................................................................... 129 5.12.2 interrupts ........................................................................................... 130 5.12.3 lockable ram ranges ........................................................................... 130 5.12.4 century rollover .................................................................................. 130 5.12.5 clearing battery-backed rtc ram .......................................................... 131 5.13 processor interface (d31:f0) ............................................................................ 132 5.13.1 processor interface signals .................................................................... 133 5.13.2 dual-processor issues (nettop only) ....................................................... 135 5.14 power management (d31:f0)............................................................................ 136 5.14.1 features ............................................................................................. 136 5.14.2 chipset and system power states........................................................... 137 5.14.3 system power planes ............................................................................ 139 5.14.4 smi#/sci generation ........................................................................... 140 5.14.5 dynamic processor clock control ........... ................................................. 142 5.14.6 dynamic pci clock control (netbook only) .............................................. 145 5.14.7 sleep states ........................................................................................ 147 5.14.8 thermal management ........................................................................... 150 5.14.9 event input signals and their usage ....................................................... 152 5.14.10alt access mode .................................................................................. 155 5.14.11system power supplies, planes, and signals ............................................ 158 5.14.12clock generators.................................................................................. 161 5.14.13legacy power management theory of operation ....................................... 162 5.15 system management (d31:f0).......................................................................... 163 5.15.1 theory of operation.............................................................................. 163 5.15.2 heartbeat and event reporting via smbus ............................................... 164 5.16 sata host controller (d31:f2).......................................................................... 168 5.16.1 theory of operation.............................................................................. 170 5.16.2 sata swap bay support........................................................................ 171 5.16.3 power management operation................................................................ 171 5.16.4 sata led............................................................................................ 173 5.16.5 ahci operation .................................................................................... 173 5.17 high precision event timers .............................................................................. 174 5.17.1 timer accuracy .................................................................................... 174 5.17.2 interrupt mapping ................................................................................ 175 5.17.3 periodic vs. non-periodic modes ........... .................................................. 175 5.17.4 enabling the timers .............................................................................. 176 5.17.5 interrupt levels ................................................................................... 176 5.17.6 handling interrupts .............................................................................. 176 5.17.7 issues related to 64-bit timers with 32-bit processors .............................. 177 5.18 usb uhci host controllers (d29:f0, f1, f2, and f3)............................................ 177 5.18.1 data structures in main memory............................................................. 177 5.18.2 data transfers to/from main memory ...................................................... 178 5.18.3 data encoding and bit stuffing ............................................................... 178 5.18.4 bus protocol ........................................................................................ 178 5.18.5 packet formats .................................................................................... 179 5.18.6 usb interrupts..................................................................................... 179 5.18.7 usb power management ....................................................................... 182 5.18.8 usb legacy keyboard operation............................................................. 182 5.19 usb ehci host controller (d29:f7) ................................................................... 185 5.19.1 ehc initialization.................................................................................. 185 5.19.2 data structures in main memory............................................................. 186 5.19.3 usb 2.0 enhanced host controller dma ................................................... 186 www.datasheet.co.kr datasheet pdf - http://www..net/
6 datasheet 5.19.4 data encoding and bit stuffing ............................................................... 187 5.19.5 packet formats .................................................................................... 187 5.19.6 usb 2.0 interrupts and error conditions .................................................. 187 5.19.7 usb 2.0 power management .................................................................. 188 5.19.8 interaction with uhci host controllers..................................................... 190 5.19.9 usb 2.0 legacy keyboard operation ....................................................... 193 5.19.10usb 2.0 based debug port ..................................................................... 193 5.20 smbus controller (d31:f3) ............................................................................... 199 5.20.1 host controller ..................................................................................... 199 5.20.2 bus arbitration ..................................................................................... 204 5.20.3 bus timing .......................................................................................... 205 5.20.4 interrupts / smi# ................................................................................. 205 5.20.5 smbalert#......................................................................................... 207 5.20.6 smbus crc generation and checking ...................................................... 207 5.20.7 smbus slave interface........................................................................... 207 5.21 intel hd audio overview................................................................................... 213 5.22 serial peripheral interface (spi) ................. ....................................................... 214 5.22.1 flash device configurations ................................................................... 214 5.22.2 spi device compatibility requirements...... ............ ........... .......... ............. 214 5.22.3 chipset compatible command set .......................................................... 215 5.22.4 flash protection.................................................................................... 216 5.23 feature capability mechanism ...... ............ ........... ............ ........... .......... ............. 217 6 ballout definition ................................................................................................... 218 6.1 chipset ballout, signal, and mechanical document ............................................... 218 6.2 chipset ballout ................................................................................................ 218 7 chipset package information ................................................................................. 225 8 electrical characteristics ........................................................................................ 227 8.1 thermal specifications...................................................................................... 227 8.2 absolute maximum ratings ............................................................................... 227 8.3 dc characteristics ........................................................................................... 228 8.4 ac characteristics............................................................................................ 235 8.5 timing diagrams ............................................................................................. 244 9 register and memory mapping ............................................................................... 258 9.1 pci devices and functions ................................................................................ 258 9.2 pci configuration map ...................................................................................... 259 9.3 i/o map.......................................................................................................... 260 9.3.1 fixed i/o address ranges ...................................................................... 260 9.3.2 variable i/o decode ranges ................................................................... 262 9.4 memory map ................................................................................................... 264 9.4.1 boot-block update scheme .................................................................... 265 10 chipset configur ation registers ............................................................................. 267 10.1 chipset configuration registers (memory space) ................................................. 267 10.1.1 vch?virtual channel capability header re gister ........... .......... ........... ...... 269 10.1.2 vcap1?virtual channel capability #1 regist er .............. .......... ........... ...... 269 10.1.3 vcap2?virtual channel capability #2 regist er .............. .......... ........... ...... 270 10.1.4 pvc?port virtual channel control register............................................... 270 10.1.5 pvs?port virtual channel status register................................................ 270 10.1.6 v0cap?virtual channel 0 resource capab ility register.... ................ .......... 270 10.1.7 v0ctl?virtual channel 0 resource control register ................................. 271 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 7 10.1.8 v0sts?virtual channel 0 resource status register .................................. 271 10.1.9 v1cap?virtual channel 1 resource capa bility register ........ ............ ......... 272 10.1.10v1ctl?virtual channel 1 resource control register ................................. 272 10.1.11v1sts?virtual channel 1 resource status register .................................. 273 10.1.12rctcl?root complex topology capabilitie s list register ...... .................... 273 10.1.13esd?element self description register................................................... 273 10.1.14uld?upstream link descriptor register.................................................. 274 10.1.15ulba?upstream link base address register............................................ 274 10.1.16rp1d?root port 1 descriptor register .................................................... 274 10.1.17rp1ba?root port 1 base address register .............................................. 275 10.1.18rp2d?root port 2 descriptor register .................................................... 275 10.1.19rp2ba?root port 2 base address register .............................................. 275 10.1.20rp3d?root port 3 descriptor register .................................................... 276 10.1.21rp3ba?root port 3 base address register .............................................. 276 10.1.22rp4d?root port 4 descriptor register .................................................... 276 10.1.23rp4ba?root port 4 base address register .............................................. 277 10.1.24hdd?intel hd audio descriptor register................................................. 277 10.1.25hdba?intel hd audio base address register........................................... 277 10.1.26ilcl?internal link capabilities list regi ster ............ ......... ............ ........... 278 10.1.27lcap?link capabilities regi ster ............ ........... .......... ........... ........... ...... 278 10.1.28lctl?link control register ................................................................... 279 10.1.29lsts?link status register .................................................................... 279 10.1.30rpc?root port configuration register .................................................... 280 10.1.31rpfn?root port function number for pci express root ports .................... 281 10.1.32trsr?trap status register ................................................................... 282 10.1.33trcr?trapped cycle register ............................................................... 282 10.1.34twdr?trapped write data register ....................................................... 282 10.1.35iotrn ? i/o trap register (0-3) ............................................................ 283 10.1.36tctl?tco configuration register .......................................................... 284 10.1.37d31ip?device 31 interrupt pin register.................................................. 284 10.1.38d30ip?device 30 interrupt pin register.................................................. 285 10.1.39d29ip?device 29 interrupt pin register.................................................. 285 10.1.40d28ip?device 28 interrupt pin register.................................................. 286 10.1.41d27ip?device 27 interrupt pin register.................................................. 287 10.1.42d31ir?device 31 interrupt route register.............................................. 288 10.1.43d30ir?device 30 interrupt route register.............................................. 289 10.1.44d29ir?device 29 interrupt route register.............................................. 290 10.1.45d28ir?device 28 interrupt route register.............................................. 292 10.1.46d27ir?device 27 interrupt route register.............................................. 293 10.1.47oic?other interrupt control register ..................................................... 294 10.1.48rc?rtc configuration register.............................................................. 295 10.1.49hptc?high precision timer configuration register ................................... 295 10.1.50gcs?general control and status register ............................................... 296 10.1.51buc?backed up control register ........................................................... 298 10.1.52fd?function disable register .............. .................................................. 298 10.1.53cg?clock gating (netbook only)............................................................ 300 11 lan controller registers (b1:d8:f0) ..................................................................... 302 11.1 pci configuration registers (lan controller?b1:d8:f0) .............................................................................. 302 11.1.1 vid?vendor identification register (lan controller?b1:d8:f0) ................................................................... 303 www.datasheet.co.kr datasheet pdf - http://www..net/
8 datasheet 11.1.2 did?device identification register (lan controller?b1:d8:f0) ................................................................... 303 11.1.3 pcicmd?pci command register (lan controller?b1:d8:f0) ................................................................... 304 11.1.4 pcists?pci status register (lan controller?b1:d8:f0) ................................................................... 305 11.1.5 rid?revision identification register (lan controller?b1:d8:f0) ................................................................... 306 11.1.6 scc?sub class code register (lan controller?b1:d8:f0) ................................................................... 306 11.1.7 bcc?base-class code register (lan controller?b1:d8:f0) ................................................................... 306 11.1.8 cls?cache line size register (lan controller?b1:d8:f0) ................................................................... 307 11.1.9 pmlt?primary master latency timer register (lan controller?b1:d8:f0) ................................................................... 307 11.1.10headtyp?header type register (lan controller?b1:d8:f0) ................................................................... 307 11.1.11csr_mem_base ? csr memory-mapped base address register (lan controller?b1:d8:f0) ........................................... 308 11.1.12csr_io_base ? csr i/o-mapped base address register (lan controller?b1:d8:f0) ................................................................... 308 11.1.13svid ? subsystem vendor identification (lan controller?b1:d8:f0) ................................................................... 309 11.1.14sid ? subsystem identification (lan controller?b1:d8:f0) ................................................................... 309 11.1.15cap_ptr ? capabilities pointer (lan controller?b1:d8:f0) ................................................................... 309 11.1.16int_ln ? interrupt line register (lan controller?b1:d8:f0) ................................................................... 310 11.1.17int_pn ? interrupt pin register (lan controller?b1:d8:f0) ................................................................... 310 11.1.18min_gnt ? minimum grant register (lan controller?b1:d8:f0) ................................................................... 310 11.1.19max_lat ? maximum latency register (lan controller?b1:d8:f0) ................................................................... 310 11.1.20cap_id ? capability identification register (lan controller?b1:d8:f0) ................................................................... 311 11.1.21nxt_ptr ? next item pointer (lan controller?b1:d8:f0) ................................................................... 311 11.1.22pm_cap ? power management capabilities (lan controller?b1:d8:f0) ................................................................... 311 11.1.23pmcsr ? power management control/ status register (lan controller?b1:d8:f0) ............................................. 312 11.1.24pcidata ? pci power management data register (lan controller?b1:d8:f0) ................................................................... 313 11.2 lan control / status registers (csr) (lan controller?b1:d8:f0) .............................................................................. 313 11.2.1 scb_sta?system control block status word register (lan controller?b1:d8:f0) ................................................................... 314 11.2.2 scb_cmd?system control block command word register (lan controller?b1:d8:f0) ....................................................... 316 11.2.3 scb_genpnt?system control block general pointer register (lan controller?b1:d8:f0) ....................................................... 318 11.2.4 port?port interface register (lan controller?b1:d8:f0) ................................................................... 318 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 9 11.2.5 eeprom_cntl?eeprom control register (lan controller?b1:d8:f0) ................................................................... 320 11.2.6 mdi_cntl?management da ta interface (mdi) control register (lan controller?b1:d8:f0)....................................................... 320 11.2.7 rec_dma_bc?receive dma byte count register (lan controller?b1:d8:f0) ................................................................... 321 11.2.8 erec_intr?early receive interrupt register (lan controller?b1:d8:f0) ................................................................... 321 11.2.9 flow_cntl?flow control register (lan controller?b1:d8:f0) ................................................................... 322 11.2.10pmdr?power management driver register (lan controller?b1:d8:f0) ................................................................... 323 11.2.11gencntl?general control register (lan controller?b1:d8:f0) ................................................................... 324 11.2.12gensta?general status register (lan controller?b1:d8:f0) ................................................................... 324 11.2.13smb_pci?smb via pci register (lan controller?b1:d8:f0) ................................................................... 325 11.2.14statistical counters (lan controller?b1 :d8:f0) ....................................... 325 11.3 asf configuration registers (lan controller?b1:d8:f0) .............................................................................. 328 11.3.1 asf_rid?asf revision identification register (lan controller?b1:d8:f0) ................................................................... 329 11.3.2 smb_cntl?smbus control register (lan controller?b1:d8:f0) ................................................................... 329 11.3.3 asf_cntl?asf control register (lan controller?b1:d8:f0) ................................................................... 330 11.3.4 asf_cntl_en?asf control enable register (asf controller?b1:d8:f0) ................................................................... 331 11.3.5 enable?enable register (asf controller?b1:d8:f0) ................................................................... 331 11.3.6 apm?apm register (asf controller?b1:d8:f0) ................................................................... 332 11.3.7 wtim_conf?watchdog timer configuration register (asf controller?b1:d8:f0) ................................................................... 332 11.3.8 heart_tim?heartbeat timer register (asf controller?b1:d8:f0) ................................................................... 333 11.3.9 retran_int?retransmission interval register (asf controller?b1:d8:f0) ................................................................... 333 11.3.10retran_pcl?retransmission packet coun t limit..................................... 334 11.3.11asf_wtim1?asf watchdog timer 1 register (asf controller?b1:d8:f0) ................................................................... 334 11.3.12asf_wtim2?asf watchdog timer 2 register (asf controller?b1:d8:f0) ................................................................... 334 11.3.13pet_seq1?pet sequence 1 register (asf controller?b1:d8:f0) ................................................................... 334 11.3.14pet_seq2?pet sequence 2 register (asf controller?b1:d8:f0) ................................................................... 335 11.3.15sta?status register (asf controller?b1:d8:f0) ................................................................... 335 11.3.16for_act?forced actions register (asf controller?b1:d8:f0) ................................................................... 336 11.3.17rmcp_snum?rmcp sequence number register (asf controller?b1:d8:f0) ................................................................... 337 www.datasheet.co.kr datasheet pdf - http://www..net/
10 datasheet 11.3.18sp_mode?special modes register (asf controller?b1:d8:f0) ................................................................... 337 11.3.19inpoll_tconf?inter-poll timer configuration register (asf controller?b1:d8:f0) ................................................................... 337 11.3.20phist_clr?poll history clear register (asf controller?b1:d8:f0) ................................................................... 338 11.3.21pmsk1?polling mask 1 register (asf controller?b1:d8:f0) ................................................................... 339 11.3.22pmsk2?polling mask 2 register (asf controller?b1:d8:f0) ................................................................... 339 11.3.23pmsk3?polling mask 3 register (asf controller?b1:d8:f0) ................................................................... 339 11.3.24pmsk4?polling mask 4 register (asf controller?b1:d8:f0) ................................................................... 339 11.3.25pmsk5?polling mask 5 register (asf controller?b1:d8:f0) ................................................................... 340 11.3.26pmsk6?polling mask 6 register (asf controller?b1:d8:f0) ................................................................... 340 11.3.27pmsk7?polling mask 7 register (asf controller?b1:d8:f0) ................................................................... 340 11.3.28pmsk8?polling mask 8 register (asf controller?b1:d8:f0) ................................................................... 341 12 pci-to-pci bridge registers (d30:f0) .................................................................... 342 12.1 pci configuration registers (d30:f0) ................................................................. 342 12.1.1 vid? vendor identification register (pci-pci?d30:f0)............................. 343 12.1.2 did? device identification register (pci-pci?d30:f0) ............................. 343 12.1.3 pcicmd?pci command (pci-pci?d30:f0) ............................................. 343 12.1.4 psts?pci status register (pci-pci?d30:f0) .......................................... 344 12.1.5 rid?revision identification register (pci-pci?d30:f0) ............................ 346 12.1.6 cc?class code register (pci-pci?d30:f0)............................................. 346 12.1.7 pmlt?primary master latency timer register (pci-pci?d30:f0)................................................................................ 347 12.1.8 headtyp?header type register (pci-pci?d30:f0) ................................. 347 12.1.9 bnum?bus number register (pci-pci?d30:f0) ...................................... 347 12.1.10smlt?secondary master latency timer register (pci-pci?d30:f0)................................................................................ 348 12.1.11iobase_limit?i/o base and limit register (pci-pci?d30:f0)................................................................................ 348 12.1.12secsts?secondary status register (pci-pci?d30:f0) ............................ 348 12.1.13membase_limit?memory base and limit register (pci-pci?d30:f0)................................................................................ 349 12.1.14pref_mem_base_limit?prefetchable memory base and limit register (pci-pci?d30:f0) ..................................................... 350 12.1.15pmbu32?prefetchable memory base upper 32 bits register (pci-pci?d30:f0) ................................................................... 350 12.1.16pmlu32?prefetchable memory limit upper 32 bits register (pci-pci?d30:f0) ................................................................... 350 12.1.17capp?capability list pointer register (p ci-pci?d30:f0) ........ ............ ...... 351 12.1.18intr?interrupt information register (p ci-pci?d30:f0) ........................... 351 12.1.19bctrl?bridge control register (pci-pci?d30:f0) ................................... 351 12.1.20spdh?secondary pci device hiding register (pci-pci?d30:f0)................................................................................ 353 12.1.21dtc?delayed transaction control register (pci-pci?d30:f0)................................................................................ 354 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 11 12.1.22bps?bridge proprietary status register (pci-pci?d30:f0) ............................................................................... 355 12.1.23bpc?bridge policy configuration register (pci-pci?d30:f0) ............................................................................... 356 12.1.24svcap?subsystem vendor capability register (pci-pci?d30:f0) ............................................................................... 357 12.1.25svid?subsystem vendor ids register (pci-pci?d30:f0)......................... 357 13 lpc interface bridge registers (d31:f0) ............................................................... 358 13.1 pci configuration registers (lpc i/f?d31:f0) .................................................... 358 13.1.1 vid?vendor identification register (lpc i/f?d31:f0) .............................. 359 13.1.2 did?device identification register (l pc i/f?d31:f0) .............................. 359 13.1.3 pcicmd?pci command register (lpc i/f?d31:f0) ................................ 360 13.1.4 pcists?pci status register (lpc i/f?d31:f0) ....................................... 360 13.1.5 rid?revision identification register (lpc i/f?d31:f0) ............................ 361 13.1.6 pi?programming interface register (lpc i/f?d31:f0) ............................. 361 13.1.7 scc?sub class code register (lpc i/f?d31:f0) ..................................... 361 13.1.8 bcc?base class code register (lpc i/f?d31:f0).................................... 362 13.1.9 plt?primary latency timer register (lpc i/f?d31:f0) ............................ 362 13.1.10headtyp?header type register (lpc i/f?d31:f0).................................. 362 13.1.11ss?sub system identifiers register (lpc i/f?d31:f0)............................. 362 13.1.12capp?capability list pointer (lpc i/f? d31:f0) ......... ........... .......... ......... 363 13.1.13pmbase?acpi base address register (lpc i/f?d31:f0) .......................... 363 13.1.14acpi_cntl?acpi control register (lpc i/f ? d31:f0) ............................. 363 13.1.15gpiobase?gpio base address register (lpc i/f ? d31:f0) ..................... 364 13.1.16gc?gpio control register (lpc i/f ? d31:f0) ........................................ 364 13.1.17pirq[n]_rout?pirq[a,b,c,d] routing control register (lpc i/f?d31:f0) ................................................................................ 365 13.1.18sirq_cntl?serial irq control register (lpc i/f?d31:f0) ................................................................................ 365 13.1.19pirq[n]_rout?pirq[e,f,g,h] routing control register (lpc i/f?d31:f0) ................................................................................ 366 13.1.20lpc_i/o_dec?i/o decode ranges register (lpc i/f?d31:f0) ................................................................................ 367 13.1.21lpc_en?lpc i/f enables register (lpc i/f?d31:f0)................................ 368 13.1.22gen1_dec?lpc i/f generic decode range 1 register (lpc i/f?d31:f0) ................................................................................ 369 13.1.23gen2_dec?lpc i/f generic decode range 2register (lpc i/f?d31:f0) ................................................................................ 369 13.1.24gen3_dec?lpc i/f generic decode range 3register (lpc i/f?d31:f0) ................................................................................ 370 13.1.25gen4_dec?lpc i/f generic decode range 4register (lpc i/f?d31:f0) ................................................................................ 370 13.1.26fwh_sel1?firmware hub select 1 register (lpc i/f?d31:f0) ................................................................................ 371 13.1.27fwh_sel2?firmware hub select 2 register (lpc i/f?d31:f0) ................................................................................ 372 13.1.28fwh_dec_en1?firmware hub decode enable register (lpc i/f?d31:f0) ................................................................................ 372 13.1.29bios_cntl?bios control register (lpc i/f?d31:f0) ................................................................................ 374 13.1.30fdcap?feature detection capability id (lpc i/f?d31:f0) ................................................................................ 375 13.1.31fdlen?feature detection capability length (lpc i/f?d31:f0) ................................................................................ 375 www.datasheet.co.kr datasheet pdf - http://www..net/
12 datasheet 13.1.32fdver?feature detection version (lpc i/f?d31:f0) ................................................................................ 376 13.1.33fdvct?feature vector register (lpc i/f?d31:f0)................................... 376 13.1.34rcba?root complex base address register (lpc i/f?d31:f0) ................................................................................ 376 13.2 dma i/o registers (lpc i/f?d31:f0)................................................................. 377 13.2.1 dmabase_ca?dma base and current address registers (lpc i/f?d31:f0)................................................................... 378 13.2.2 dmabase_cc?dma base and current count registers (lpc i/f?d31:f0) ................................................................................ 378 13.2.3 dmamem_lp?dma memory low page registers (lpc i/f?d31:f0) ................................................................................ 379 13.2.4 dmacmd?dma command register (lpc i/f?d31:f0) .............................. 379 13.2.5 dmasta?dma status register (lpc i/f?d31:f0) .................................... 380 13.2.6 dma_wrsmsk?dma write single mask register (lpc i/f?d31:f0) ................................................................................ 380 13.2.7 dmach_mode?dma channel mode register (lpc i/f?d31:f0) ................................................................................ 381 13.2.8 dma clear byte pointer register (lpc i/f?d31:f0)................................... 382 13.2.9 dma master clear register (lpc i/f?d31:f0) .......................................... 382 13.2.10dma_clmsk?dma clear mask register (lpc i/f?d31:f0) ........................ 382 13.2.11dma_wrmsk?dma write all mask register (lpc i/f?d31:f0) ................................................................................ 383 13.3 timer i/o registers (lpc i/f?d31:f0) ............................................................... 383 13.3.1 tcw?timer control word register (lpc i/f?d31:f0) ............................... 384 13.3.2 rdbk_cmd?read back command (lpc i/f?d31:f0) ............................... 385 13.3.3 ltch_cmd?counter latch command (lpc i/f?d31:f0) ........................... 385 13.3.4 sbyte_fmt?interval timer status byte format register (lpc i/f?d31:f0) ................................................................................ 386 13.3.5 counter access ports register (lpc i/f?d31:f0) ...................................... 387 13.4 8259 interrupt controller (pic) registers (lpc i/f?d31:f0) ........................................................................................... 387 13.4.1 interrupt controller i/o map (lpc i/f?d31:f0) ........................................ 387 13.4.2 icw1?initialization command word 1 register (lpc i/f?d31:f0) ................................................................................ 388 13.4.3 icw2?initialization command word 2 register (lpc i/f?d31:f0) ................................................................................ 389 13.4.4 icw3?master controller initialization command word 3 register (lpc i/f?d31:f0) ......................................................... 390 13.4.5 icw3?slave controlle r initialization command word 3 register (lpc i/f?d31:f0) ......................................................... 390 13.4.6 icw4?initialization command word 4 register (lpc i/f?d31:f0) ................................................................................ 390 13.4.7 ocw1?operational control word 1 (interrupt mask) register (lpc i/f?d31:f0) .................................................................... 391 13.4.8 ocw2?operational control word 2 register (lpc i/f?d31:f0) ................................................................................ 391 13.4.9 ocw3?operational control word 3 register (lpc i/f?d31:f0) ................................................................................ 392 13.4.10elcr1?master controller edge/level triggered register (lpc i/f?d31:f0) ................................................................................ 393 13.4.11elcr2?slave controller edge/level triggered register (lpc i/f?d31:f0) ................................................................................ 393 13.5 advanced programmable interrupt controller (apic)(d31:f0)................................ 394 13.5.1 apic register map (lpc i/f?d31:f0)...................................................... 394 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 13 13.5.2 ind?index register (lpc i/f?d31:f0)................................................... 395 13.5.3 dat?data register (lpc i/f?d31:f0).................................................... 395 13.5.4 eoir?eoi register (lpc i/f?d31:f0) .................................................... 395 13.5.5 id?identification register (lpc i/f?d31: f0)........................................... 396 13.5.6 ver?version register (lpc i/f?d31:f0) ................................................ 396 13.5.7 redir_tbl?redirection table (lpc i/f?d31:f0)..................................... 397 13.6 real time clock registers (lpc i/f?d31:f0) ...................................................... 399 13.6.1 i/o register address map (lpc i/f?d31:f0)............................................ 399 13.6.2 indexed registers (lpc i/f?d31:f0) ...................................................... 399 13.7 processor interface registers (lpc i/f?d31:f0).................................................. 403 13.7.1 nmi_sc?nmi status and control register (lpc i/f?d31:f0) ................................................................................ 404 13.7.2 nmi_en?nmi enable (and real time clock index) register (lpc i/f?d31:f0).................................................................... 405 13.7.3 port92?fast a20 and init register (lpc i/f?d31:f0) ............................. 405 13.7.4 coproc_err?coprocessor error register (lpc i/f?d31:f0) ................................................................................ 405 13.7.5 rst_cnt?reset control register (lpc i/f?d31:f0) ................................ 406 13.8 power management registers (pm?d31:f0) ....................................................... 406 13.8.1 power management pci configuration registers (pm?d31:f0) ...................................................................................... 406 13.8.2 apm i/o decode ................................................................................... 415 13.8.3 power management i/o registers ........................................................... 415 13.9 system management tco registers (d31:f0) ..................................................... 438 13.9.1 tco_rld?tco timer reload and current value register .......................... 439 13.9.2 tco_dat_in?tco data in register ....................................................... 439 13.9.3 tco_dat_out?tco data out register .................................................. 440 13.9.4 tco1_sts?tco1 status register .......................................................... 440 13.9.5 tco2_sts?tco2 status register .......................................................... 442 13.9.6 tco1_cnt?tco1 control register ......................................................... 443 13.9.7 tco2_cnt?tco2 control register ......................................................... 443 13.9.8 tco_message1 and tco_message2 registers ....................................... 444 13.9.9 tco_wdcnt?tco watchdog control register ......................................... 444 13.9.10sw_irq_gen?software irq generation register .................................... 445 13.9.11tco_tmr?tco timer initial value register ............................................. 445 13.10 general purpose i/o registers (d31:f0) ............................................................. 445 13.10.1gpio_use_sel?gpio use select register .............................................. 446 13.10.2gp_io_sel?gpio input/output select register ....................................... 447 13.10.3gp_lvl?gpio level for input or output register ..................................... 447 13.10.4gpo_blink?gpo blink enable register .................................................. 447 13.10.5gpi_inv?gpio signal invert register..................................................... 448 13.10.6gpio_use_sel2?gpio use select 2 register[63:32] ............................... 448 13.10.7gp_io_sel2?gpio input/output select 2 register[63:32] ........................ 449 13.10.8gp_lvl2?gpio level for input or output 2 register[63:32] ...................... 449 14 uhci controlle rs registers .................................................................................... 450 14.1 pci configuration registers (usb?d29:f0/f1/f2/f3).................................................................................. 450 14.1.1 vid?vendor identification register (usb?d29:f0/f1/f2/f3) ...................................................................... 451 14.1.2 did?device identification register (usb?d29:f0/f1/f2/f3) ...................................................................... 451 14.1.3 pcicmd?pci command register (usb?d29:f0/f1/f2/f3)........................ 451 www.datasheet.co.kr datasheet pdf - http://www..net/
14 datasheet 14.1.4 pcists?pci status register (usb?d29:f0/f1/f2/f3) ....................................................................... 452 14.1.5 rid?revision identification register (usb?d29:f0/f1/f2/f3) ....................................................................... 453 14.1.6 pi?programming interface register (usb?d29:f0/f1/f2/f3) ....................................................................... 453 14.1.7 scc?sub class code register (usb?d29:f0/f1/f2/f3) ....................................................................... 453 14.1.8 bcc?base class code register (usb?d29:f0/f1/f2/f3) ....................................................................... 453 14.1.9 mlt?master latency timer register (usb?d29:f0/f1/f2/f3) ....................................................................... 454 14.1.10headtyp?header type register (usb?d29:f0/f1/f2/f3) ....................................................................... 454 14.1.11base?base address register (usb?d29:f0/f1/f2/f3) ....................................................................... 455 14.1.12svid ? subsystem vendor identification register (usb?d29:f0/f1/f2/f3) ....................................................................... 455 14.1.13sid ? subsystem identification register (usb?d29:f0/f1/f2/f3) ....................................................................... 455 14.1.14 int_ln?interrupt line register (usb?d29:f0/f1/f2/f3) ....................................................................... 456 14.1.15int_pn?interrupt pin register (usb?d29:f0/f1/f2/f3) ....................................................................... 456 14.1.16usb_relnum?serial bus release number register (usb?d29:f0/f1/f2/f3) ....................................................................... 456 14.1.17usb_legkey?usb legacy keyboard/mouse control register (usb?d29:f0/f1/f2/f3)........................................................... 457 14.1.18 usb_res?usb resume enable register (usb?d29:f0/f1/f2/f3) ....................................................................... 459 14.1.19cwp?core well policy register (usb?d29:f0/f1/f2/f3) ....................................................................... 459 14.2 usb i/o registers............................................................................................ 459 14.2.1 usbcmd?usb command register .......................................................... 460 14.2.2 usbsts?usb status register ................................................................ 463 14.2.3 usbintr?usb interrupt enable register................................................. 464 14.2.4 frnum?frame number register ............................................................ 465 14.2.5 frbaseadd?frame list base address register........................................ 465 14.2.6 sofmod?start of frame modify register ................................................ 466 14.2.7 portsc[0,1]?port status and control register ........................................ 467 15 sata controller registers (d31:f2) ....................................................................... 470 15.1 pci configuration registers (sata?d31:f2) ........................................................ 470 15.1.1 vid?vendor identification register (sata?d31:f2) ................................. 472 15.1.2 did?device identification register (sata?d31:f2) ................................. 472 15.1.3 pcicmd?pci command register (sata?d31:f2) ..................................... 472 15.1.4 pcists ? pci status register (sata?d31:f2) ......................................... 473 15.1.5 rid?revision identification register (sata?d31:f2) ............................... 474 15.1.6 pi?programming interface register (sata?d31:f2) ................................. 474 15.1.7 scc?sub class code register (sata?d31:f2) ......................................... 475 15.1.8 bcc?base class code register (sata?d31:f2sata?d31:f2)................................................................. 476 15.1.9 pmlt?primary master latency timer register (sata?d31:f2) .................................................................................... 476 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 15 15.1.10pcmd_bar?primary command block base address register (sata?d31:f2) ....................................................................... 476 15.1.11pcnl_bar?primary control block base address register (sata?d31:f2).................................................................................... 476 15.1.12scmd_bar?secondary command block base address register (ide d31:f1) .......................................................................... 477 15.1.13scnl_bar?secondary control block base address register (ide d31:f1) .......................................................................... 477 15.1.14bar ? legacy bus master base address register (sata?d31:f2).................................................................................... 477 15.1.15abar ? ahci base address register (sata?d31:f2).................................................................................... 478 15.1.16svid?subsystem vendor identification register (sata?d31:f2).................................................................................... 479 15.1.17sid?subsystem identification register (sata?d31:f2) ............................ 479 15.1.18cap?capabilities pointer register (sata? d31:f2)............... ............ ......... 479 15.1.19int_ln?interrupt line register (sata?d31:f2) ...................................... 479 15.1.20int_pn?interrupt pin register (sata?d31:f2)........................................ 480 15.1.21ide_timp ? primary ide timing register (sata?d31:f2) ......................... 480 15.1.22ide_tims ? slave ide timing register (sata?d31:f2) ............................ 481 15.1.23sdma_cnt?synchronous dma control register (sata?d31:f2).................................................................................... 482 15.1.24sdma_tim?synchronous dma timing register (sata?d31:f2).................................................................................... 483 15.1.25ide_config?ide i/o configuration register (sata?d31:f2).................................................................................... 485 15.1.26pid?pci power management capability identification register (sata?d31:f2) ....................................................................... 486 15.1.27pc?pci power management capabilities register (sata?d31:f2).................................................................................... 486 15.1.28pmcs?pci power management control and status register (sata?d31:f2) ....................................................................... 487 15.1.29msici?message signaled interrupt capability identification (sata?d31:f2) 487 15.1.30msimc?message signaled interrupt message control (sata?d31:f2)......... 488 15.1.31msima? message signaled interrupt message address (sata?d31:f2)....... 489 15.1.32msimd?message signaled interrupt message data (sata?d31:f2) ............ 489 15.1.33map?address map register (sata?d31:f2) ............................................ 489 15.1.34pcs?port control and status register (sata?d31:f2).............................. 490 15.1.35sir?sata initialization register ............................................................ 491 15.1.36siri?sata indexed registers index ...................................................... 492 15.1.37strd?sata indexed register data ........................................................ 492 15.1.38scap0?sata capability register 0 (sat a?d31:f2) ............. ............ ......... 493 15.1.39scap1?sata capability register 1 (sat a?d31:f2) ............. ............ ......... 494 15.1.40atc?apm trapping control register (sata?d31:f2) ................................ 495 15.1.41ats?apm trapping status register (sata?d31:f2) ................................. 495 15.1.42sp ? scratch pad register (sata?d31:f2) .............................................. 495 15.1.43bfcs?bist fis control/status register (sata?d31:f2) ........................... 496 15.1.44bftd1?bist fis transmit data1 register (sata?d31:f2) ........................ 497 15.1.45bftd2?bist fis transmit data2 register (sata?d31:f2) ........................ 497 15.2 bus master ide i/o registers (d31:f2) .............................................................. 497 15.2.1 bmic[p,s]?bus master ide command register (d31:f2) .......................... 498 15.2.2 bmis[p,s]?bus master ide status register (d31:f2) ............................... 499 15.2.3 bmid[p,s]?bus master ide descriptor table pointer register (d31:f2) ................................................................................ 500 www.datasheet.co.kr datasheet pdf - http://www..net/
16 datasheet 15.3 ahci registers (d31:f2) .................................................................................. 501 15.3.1 ahci generic host control registers (d31:f2).......................................... 501 15.3.2 port registers (d31:f2) ......................................................................... 505 16 ehci controller registers (d29:f7) ....................................................................... 519 16.1 usb ehci configuration registers (usb ehci?d29:f7)........................................................................................ 519 16.1.1 vid?vendor identification register (usb ehci?d29:f7)............................................................................. 520 16.1.2 did?device identification register (usb ehci?d29:f7)............................................................................. 520 16.1.3 pcicmd?pci command register (usb ehci?d29:f7)............................................................................. 521 16.1.4 pcists?pci status register (usb ehci?d29:f7)............................................................................. 522 16.1.5 rid?revision identification register (usb ehci?d29:f7)............................................................................. 523 16.1.6 pi?programming interface register (usb ehci?d29:f7)............................................................................. 523 16.1.7 scc?sub class code register (usb ehci?d29:f7)............................................................................. 523 16.1.8 bcc?base class code register (usb ehci?d29:f7)............................................................................. 523 16.1.9 pmlt?primary master latency timer register (usb ehci?d29:f7)............................................................................. 524 16.1.10mem_base?memory base address register (usb ehci?d29:f7)............................................................................. 524 16.1.11svid?usb ehci subsystem vendor id register (usb ehci?d29:f7)............................................................................. 524 16.1.12sid?usb ehci subsystem id register (usb ehci?d29:f7)............................................................................. 525 16.1.13cap_ptr?capabilit ies pointer register (usb ehci?d29:f7)............................................................................. 525 16.1.14 int_ln?interrupt line register (usb ehci?d29:f7)............................................................................. 525 16.1.15int_pn?interrupt pin register (usb ehci?d29:f7)............................................................................. 525 16.1.16pwr_capid?pci power management capability id register (usb ehci?d29:f7) ................................................................ 525 16.1.17nxt_ptr1?next item pointer #1 register (usb ehci?d29:f7)............................................................................. 526 16.1.18pwr_cap?power management capabilities register (usb ehci?d29:f7)............................................................................. 526 16.1.19pwr_cntl_sts?power management control/ status register (usb ehci?d29:f7)....................................................... 527 16.1.20debug_capid?debug port capability id register (usb ehci?d29:f7)............................................................................. 528 16.1.21nxt_ptr2?next item pointer #2 register (usb ehci?d29:f7)............................................................................. 528 16.1.22debug_base?debug port base offset register (usb ehci?d29:f7)............................................................................. 528 16.1.23usb_relnum?usb release number register (usb ehci?d29:f7)............................................................................. 528 16.1.24fl_adj?frame length adjustment register (usb ehci?d29:f7)............................................................................. 529 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 17 16.1.25pwake_cap?port wake capability register (usb ehci?d29:f7) ............................................................................ 530 16.1.26leg_ext_cap?usb ehci legacy support extended capability register (usb ehci?d29:f7)........ ............ ........... .......... ......... 530 16.1.27leg_ext_cs?usb ehci legacy support extended control / status register (usb ehci?d29:f7) ......................................... 531 16.1.28special_smi?intel specific usb 2.0 smi register (usb ehci?d29:f7) ............................................................................ 533 16.1.29access_cntl?access control register (usb ehci?d29:f7) ............................................................................ 534 16.2 memory-mapped i/o registers .......................................................................... 534 16.2.1 host controller capability registers ....... ........... .......... ........... ........... ...... 535 16.2.2 host controller operational registers ...................................................... 537 16.2.3 usb 2.0-based debug port register ........................................................ 551 17 smbus controller registers (d31:f3) ..................................................................... 555 17.1 pci configuration registers (smbus?d31:f3) .................................................... 555 17.1.1 vid?vendor identification register (smbus?d31:f3) .............................. 555 17.1.2 did?device identification register (smbus?d31:f3) .............................. 556 17.1.3 pcicmd?pci command register (smbus?d31:f3) ................................. 556 17.1.4 pcists?pci status register (smbus?d31:f3) ....................................... 557 17.1.5 rid?revision identification register (smbus?d31:f3) ............................ 557 17.1.6 pi?programming interface register (smbus?d31:f3) ............................. 558 17.1.7 scc?sub class code register (smbus?d31:f3) ..................................... 558 17.1.8 bcc?base class code register (smbus?d31:f3).................................... 558 17.1.9 smb_base?smbus base address register (smbus?d31:f3) ................................................................................ 558 17.1.10svid ? subsystem vendor identification register (smbus?d31:f2/f4) ........................................................................... 559 17.1.11sid ? subsystem identification register (smbus?d31:f2/f4) ........................................................................... 559 17.1.12int_ln?interrupt line register (smbus?d31:f3)................................... 559 17.1.13int_pn?interrupt pin register (smbus?d31:f3) .................................... 559 17.1.14hostc?host configuration register (smbus?d31:f3)............................. 560 17.2 smbus i/o registers ........................................................................................ 560 17.2.1 hst_sts?host status register (smbus?d31:f3) ................................... 561 17.2.2 hst_cnt?host control register (smbus?d31:f3).................................. 563 17.2.3 hst_cmd?host command register (smbus?d31:f3) ............................. 565 17.2.4 xmit_slva?transmit slave address register (smbus?d31:f3) ................................................................................ 565 17.2.5 hst_d0?host data 0 register (smbus?d31:f3) .................................... 565 17.2.6 hst_d1?host data 1 register (smbus?d31:f3) .................................... 565 17.2.7 host_block_db?host block data byte register (smbus?d31:f3) ................................................................................ 566 17.2.8 pec?packet error check (pec) register (smbus?d31:f3) ................................................................................ 566 17.2.9 rcv_slva?receive slave address register (smbus?d31:f3) ................................................................................ 567 17.2.10slv_data?receive slave data register (smbus?d31:f3) ....................... 567 17.2.11aux_sts?auxiliary status register (smbus?d31:f3) ............................. 567 17.2.12aux_ctl?auxiliary control register (smbus?d31:f3) ........... ........... ...... 568 17.2.13smlink_pin_ctl?smlink pin control register (smbus?d31:f3) ................................................................................ 568 www.datasheet.co.kr datasheet pdf - http://www..net/
18 datasheet 17.2.14smbus_pin_ctl?smbus pin control register (smbus?d31:f3) ................................................................................ 569 17.2.15slv_sts?slave status register (smbus ?d31:f3) .................................. 570 17.2.16 slv_cmd?slave command register (smbus?d31:f3) ............................ 570 17.2.17notify_daddr?notify device address register (smbus?d31:f3) ................................................................................ 571 17.2.18notify_dlow?notify data low byte register (smbus?d31:f3) ................................................................................ 571 17.2.19notify_dhigh?notify data high byte register (smbus?d31:f3) ................................................................................ 571 18 intel hd audio controller registers (d27:f0)................................................................ 573 18.1 intel hd audio pc i configuration space (intel hd audio? d27:f0) ................................................................................ 573 18.1.1 vid?vendor identification register (intel hd audio controller?d27:f0)........................................................ 575 18.1.2 did?device identification register (intel hd audio controller?d27:f0)........................................................ 575 18.1.3 pcicmd?pci command register (intel hd audio controller?d27:f0)........................................................ 575 18.1.4 pcists?pci status register (intel hd audio controller?d27:f0)........................................................ 576 18.1.5 rid?revision identification register (intel hd audio controller?d27:f0)........................................................ 577 18.1.6 pi?programming interface register (intel hd audio controller?d27:f0)........................................................ 577 18.1.7 scc?sub class code register (intel hd audio controller?d27:f0)........................................................ 577 18.1.8 bcc?base class code register (intel hd audio controller?d27:f0)........................................................ 577 18.1.9 cls?cache line size register (intel hd audio controller?d27:f0)........................................................ 577 18.1.10lt?latency timer register (intel hd audio controller?d27:f0)........................................................ 578 18.1.11headtyp?header type register (intel hd audio controller?d27:f0)........................................................ 578 18.1.12hdbarl?intel hd audio lower base address register (intel hd audio?d27:f0) ...................................................................... 578 18.1.13hdbaru?intel hd audio upper base address register (intel hd audio controller?d27:f0)........................................................ 578 18.1.14svid?subsystem vendor identification register (intel hd audio controller?d27:f0)........................................................ 579 18.1.15sid?subsystem identification register (intel hd audio controller?d27:f0)........................................................ 579 18.1.16capptr?capabilities pointer register (a udio?d30:f2) ..... .............. .......... 579 18.1.17intln?interrupt line register (intel hd audio controller?d27:f0)........................................................ 580 18.1.18intpn?interrupt pin register (intel hd audio controller?d27:f0)........................................................ 580 18.1.19hdctl?intel hd audio control register (intel hd audio controller?d27:f0)........................................................ 580 18.1.20tcsel?traffic class select register (intel hd audio controller?d27:f0)........................................................ 581 18.1.21pid?pci power management capability id register (intel hd audio controller?d27:f0)........................................................ 582 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 19 18.1.22pc?power management capabilities register (intel hd audio controller?d27:f0) ....................................................... 582 18.1.23pcs?power management control and status register (intel hd audio controller?d27:f0) ....................................................... 582 18.1.24mid?msi capability id register (intel hd audio controller?d27:f0) ....................................................... 583 18.1.25mmc?msi message control register (intel hd audio controller?d27:f0) ....................................................... 584 18.1.26mmla?msi message lower address register (intel hd audio controller?d27:f0) ....................................................... 584 18.1.27mmua?msi message upper address register (intel hd audio controller?d27:f0) ....................................................... 584 18.1.28mmd?msi message data register (intel hd audio controller?d27:f0) ....................................................... 584 18.1.29pxid?pci express* capability id register (intel hd audio controller?d27:f0) ....................................................... 585 18.1.30pxc?pci express* capabilities register (intel hd audio controller?d27:f0) ....................................................... 585 18.1.31devcap?device capabilities register (intel hd audio controller?d27:f0) ....................................................... 585 18.1.32devc?device control register (intel hd audio controller?d27:f0) ....................................................... 586 18.1.33devs?device status register (intel hd audio controller?d27:f0) ....................................................... 586 18.1.34vccap?virtual channe l enhanced capability header (intel hd audio controller?d27:f0) ....................................................... 587 18.1.35pvccap1?port vc capability register 1 (intel hd audio controller?d27:f0) ....................................................... 587 18.1.36pvccap2 ? port vc capability register 2 (intel hd audio controller?d27:f0) ....................................................... 587 18.1.37pvcctl ? port vc control register (intel hd audio controller?d27:f0) ....................................................... 588 18.1.38pvcsts?port vc status register (intel hd audio controller?d27:f0) ....................................................... 588 18.1.39vc0cap?vc0 resource capability register (intel hd audio controller?d27:f0) ....................................................... 588 18.1.40vc0ctl?vc0 resource control register (intel hd audio controller?d27:f0) ....................................................... 589 18.1.41vc0sts?vc0 resource status register (intel hd audio controller?d27:f0) ....................................................... 589 18.1.42vcicap?vci resource capability register (intel hd audio controller?d27:f0) ....................................................... 589 18.1.43vcictl?vci resource control register (intel hd audio controller?d27:f0) ....................................................... 590 18.1.44vcists?vci resource status register (intel hd audio controller?d27:f0) ....................................................... 590 18.1.45rccap?root complex link declaration enhanced capability header register (intel hd au dio controller?d27:f0).................. 591 18.1.46esd?element self description register (intel hd audio controller?d27:f0) ....................................................... 591 18.1.47l1desc?link 1 description register (intel hd audio controller?d27:f0) ....................................................... 591 18.1.48l1addl?link 1 lower address register (intel hd audio controller?d27:f0) ....................................................... 592 18.1.49l1addu?link 1 upper address register (intel hd audio controller?d27:f0) ....................................................... 592 www.datasheet.co.kr datasheet pdf - http://www..net/
20 datasheet 18.2 intel hd audio memory-mapped configuration registers (intel hd audio? d27:f0) ................................................................................ 592 18.2.1 gcap?global capabilities register (intel hd audio controller?d27:f0)........................................................ 596 18.2.2 vmin?minor version register (intel hd audio controller?d27:f0)........................................................ 597 18.2.3 vmaj?major version register (intel hd audio controller?d27:f0)........................................................ 597 18.2.4 outpay?output payload capability register (intel hd audio controller?d27:f0)........................................................ 597 18.2.5 inpay?input payload capability register (intel hd audio controller?d27:f0)........................................................ 598 18.2.6 gctl?global control register (intel hd audio controller?d27:f0)........................................................ 598 18.2.7 wakeen?wake enable register (intel hd audio controller?d27:f0)........................................................ 599 18.2.8 statests?state change status register (intel hd audio controller?d27:f0)........................................................ 600 18.2.9 gsts?global status register (intel hd audio controller?d27:f0)........................................................ 600 18.2.10outstrmpay?output stream payload capability (intel hd audio controller?d27:f0)........................................................ 600 18.2.11instrmpay?input stream payload capability (intel hd audio controller?d27:f0)........................................................ 601 18.2.12intctl?interrupt control register (intel hd audio controller?d27:f0)........................................................ 602 18.2.13intsts?interrupt status register (intel hd audio controller?d27:f0)........................................................ 603 18.2.14walclk?wall clock counter register (intel hd audio controller?d27:f0)........................................................ 604 18.2.15ssync?stream synchronization register (intel hd audio controller?d27:f0)........................................................ 604 18.2.16corblbase?corb lower base address register (intel hd audio controller?d27:f0)........................................................ 605 18.2.17corbubase?corb upper base address register (intel hd audio controller?d27:f0)........................................................ 605 18.2.18corbwp?corb write pointer register (intel hd audio controller?d27:f0)........................................................ 605 18.2.19corbrp?corb read pointer register (intel hd audio controller?d27:f0)........................................................ 606 18.2.20corbctl?corb control register (intel hd audio controller?d27:f0)........................................................ 606 18.2.21corbst?corb status register (intel hd audio controller?d27:f0)........................................................ 607 18.2.22corbsize?corb size register intel hd audio controller?d27:f0) ......................................................... 607 18.2.23rirblbase?rirb lower base address register (intel hd audio controller?d27:f0)........................................................ 607 18.2.24rirbubase?rirb upper base address register (intel hd audio controller?d27:f0)........................................................ 608 18.2.25rirbwp?rirb write pointer register (intel hd audio controller?d27:f0)........................................................ 608 18.2.26rintcnt?response interrupt count register (intel hd audio controller?d27:f0)........................................................ 608 18.2.27rirbctl?rirb control register (intel hd audio controller?d27:f0)........................................................ 609 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 21 18.2.28rirbsts?rirb status register (intel hd audio controller?d27:f0) ....................................................... 609 18.2.29rirbsize?rirb size register (intel hd audio controller?d27:f0) ....................................................... 610 18.2.30ic?immediate command register (intel hd audio controller?d27:f0) ....................................................... 610 18.2.31ir?immediate response register (intel hd audio controller?d27:f0) ....................................................... 611 18.2.32irs?immediate command status register (intel hd audio controller?d27:f0) ....................................................... 611 18.2.33dplbase?dma position lower base address register (intel hd audio controller?d27:f0) ....................................................... 612 18.2.34dpubase?dma position upper base address register (intel hd audio controller?d27:f0) ....................................................... 612 18.2.35sdctl?stream descriptor control register (intel hd audio controller?d27:f0) ....................................................... 612 18.2.36sdsts?stream descriptor status register (intel hd audio controller?d27:f0) ....................................................... 614 18.2.37sdlpib?stream descriptor link position in buffer register (intel hd audio controller?d27:f0 ) ........................................... 615 18.2.38sdcbl?stream descriptor cyclic buffer length register (intel hd audio controller?d27:f0) ....................................................... 615 18.2.39sdlvi?stream descriptor last valid index register (intel hd audio controller?d27:f0) ....................................................... 616 18.2.40sdfifow?stream descriptor fifo watermark register (intel hd audio controller?d27:f0) ....................................................... 616 18.2.41sdfifos?stream descriptor fifo size register (intel hd audio controller?d27:f0) ....................................................... 617 18.2.42sdfmt?stream descriptor format register (intel hd audio controller?d27:f0) ....................................................... 618 18.2.43sdbdpl?stream descriptor buffer de scriptor list pointer lower base address register (intel hd audio controller?d27:f0) ....................................................... 619 18.2.44sdbdpu?stream descriptor buffer descriptor list pointer upper base address register (intel hd audio controller?d27:f0) .............. 620 19 pci express* conf iguration registers .................................................................... 621 19.1 pci express* configuration registers (pci express?d28:f0/f1/f2/f3) ....................................................................... 621 19.1.1 vid?vendor identification register (pci express?d28:f0/f1/f2/f3) ............................................................ 623 19.1.2 did?device identification register (pci express?d28:f0/f1/f2/f3) ............................................................ 623 19.1.3 pcicmd?pci command register (pci express?d28:f0/f1/f2/f3) ............................................................ 623 19.1.4 pcists?pci status register (pci express?d28:f0/f1/f2/f3) ............................................................ 624 19.1.5 rid?revision identification register (pci express?d28:f0/f1/f2/f3) ............................................................ 625 19.1.6 pi?programming interface register (pci express?d28:f0/f1/f2/f3) ............................................................ 625 19.1.7 scc?sub class code register (pci express?d28:f0/f1/f2/f3) ............................................................ 626 19.1.8 bcc?base class code register (pci express?d28:f0/f1/f2/f3) ............................................................ 626 www.datasheet.co.kr datasheet pdf - http://www..net/
22 datasheet 19.1.9 cls?cache line size register (pci express?d28:f0/f1/f2/f3) ............................................................ 626 19.1.10plt?primary latency timer register (pci express?d28:f0/f1/f2/f3) ............................................................ 626 19.1.11headtyp?header type register (pci express?d28:f0/f1/f2/f3) ............................................................ 627 19.1.12bnum?bus number register (pci express?d28:f0/f1/f2/f3) ............................................................ 627 19.1.13iobl?i/o base and limit register (pci express?d28:f0/f1/f2/f3) ............................................................ 627 19.1.14ssts?secondary status register (pci express?d28:f0/f1/f2/f3) ............................................................ 628 19.1.15mbl?memory base and limit register (pci express?d28:f0/f1/f2/f3) ............................................................ 628 19.1.16pmbl?prefetchable memory base and limit register (pci express?d28:f0/f1/f2/f3) ............................................................ 629 19.1.17pmbu32?prefetchable memory base upper 32 bits register (pci express?d28:f0/f1/f2/f3) ................................................ 629 19.1.18pmlu32?prefetchable memory limit upper 32 bits register (pci express?d28:f0/f1/f2/f3) ................................................ 629 19.1.19capp?capabilities list pointer register (pci express?d28:f0/f1/f2/f3) ............................................................ 630 19.1.20intr?interrupt information register (pci express?d28:f0/f1/f2/f3) ............................................................ 630 19.1.21bctrl?bridge control register (pci express?d28:f0/f1/f2/f3) ............................................................ 630 19.1.22clist?capabilities list register (pci express?d28:f0/f1/f2/f3) ............................................................ 631 19.1.23xcap?pci express* capabilities register (pci express?d28:f0/f1/f2/f3) ............................................................ 632 19.1.24dcap?device capabilities register (pci express?d28:f0/f1/f2/f3) ............................................................ 632 19.1.25dctl?device control register (pci express?d28:f0/f1/f2/f3) ............................................................ 633 19.1.26dsts?device status register (pci express?d28:f0/f1/f2/f3) ............................................................ 633 19.1.27lcap?link capabilities register (pci express?d28:f0/f1/f2/f3) ............................................................ 634 19.1.28lctl?link control register (pci express?d28:f0/f1/f2/f3) ............................................................ 635 19.1.29lsts?link status register (pci express?d28:f0/f1/f2/f3) ............................................................ 636 19.1.30slcap?slot capabilities register (pci express?d28:f0/f1/f2/f3) ............................................................ 637 19.1.31slctl?slot control register (pci express?d28:f0/f1/f2/f3) ............................................................ 638 19.1.32slsts?slot status register (pci express?d28:f0/f1/f2/f3) ............................................................ 639 19.1.33rctl?root control register (pci express?d28:f0/f1/f2/f3) ............................................................ 640 19.1.34rsts?root status register (pci express?d28:f0/f1/f2/f3) ............................................................ 640 19.1.35mid?message signaled interrupt identifiers register (pci express?d28:f0/f1/f2/f3) ............................................................ 641 19.1.36mc?message signaled interrupt message control register (pci express?d28:f0/f1/f2/f3) ............................................................ 641 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 23 19.1.37ma?message signaled interrupt message address register (pci express?d28:f0/f1/f2/f3)................................................ 641 19.1.38md?message signaled interrupt message data register (pci express?d28:f0/f1/f2/f3) ............................................................ 642 19.1.39svcap?subsystem vendor capability register (pci express?d28:f0/f1/f2/f3) ............................................................ 642 19.1.40svid?subsystem vendor identification register (pci express?d28:f0/f1/f2/f3) ............................................................ 642 19.1.41pmcap?power management capability register (pci express?d28:f0/f1/f2/f3) ............................................................ 642 19.1.42pmc?pci power management capabilities register (pci express?d28:f0/f1/f2/f3) ............................................................ 643 19.1.43pmcs?pci power management control and status register (pci express?d28:f0/f1/f2/f3)................................................ 643 19.1.44mpc?miscellaneous port configuration register (pci express?d28:f0/f1/f2/f3) ............................................................ 644 19.1.45smscs?smi/sci status register (pci express?d28:f0/f1/f2/f3) ............................................................ 646 19.1.46 rpdcgen - root port dynamic clock gating enable (pci express-d28:f0 /f1/f2/f3) (netbook on ly) ............................................... 647 19.1.47ipws?intel ? pro/wireless 3945abg status (pci express?d28:f0/f1/f2/f3) (netbook only) ........................................ 647 19.1.48vch?virtual channel capability header register (pci express?d28:f0/f1/f2/f3) ............................................................ 647 19.1.49vcap2?virtual channel capability 2 register (pci express?d28:f0/f1/f2/f3) ............................................................ 648 19.1.50pvc?port virtual channel control register (pci express?d28:f0/f1/f2/f3) ............................................................ 648 19.1.51pvs ? port virtual channel status register (pci express?d28:f0/f1/f2/f3) ............................................................ 648 19.1.52v0cap ? virtual channel 0 resource capability register (pci express?d28:f0/f1/f2/f3) ............................................................ 649 19.1.53v0ctl ? virtual channel 0 resource control register (pci express?d28:f0/f1/f2/f3) ............................................................ 649 19.1.54v0sts ? virtual channel 0 resource status register (pci express?d28:f0/f1/f2/f3) ............................................................ 650 19.1.55ues ? uncorrectable error status register (pci express?d28:f0/f1/f2/f3 ............................................................. 650 19.1.56uem ? uncorrectable error mask (pci express?d28:f0/f1/f2/f3) ............................................................ 651 19.1.57uev ? uncorrectable error severity (pci express?d28:f0/f1/f2/f3) ............................................................ 652 19.1.58ces ? correctable error status register (pci express?d28:f0/f1/f2/f3) ............................................................ 653 19.1.59cem ? correctable error mask register (pci express?d28:f0/f1/f2/f3) ............................................................ 654 19.1.60aecc ? advanced error capabilities and control register (pci express?d28:f0/f1/f2/f3) ............................................................ 654 19.1.61res ? root error status register (pci express?d28:f0/f1/f2/f3) ............................................................ 655 19.1.62rctcl ? root complex topology capability list register (pci express?d28:f0/f1/f2/f3) ............................................................ 655 19.1.63esd ? element self description register (pci express?d28:f0/f1/f2/f3) ............................................................ 656 19.1.64uld ? upstream link description register (pci express?d28:f0/f1/f2/f3) ............................................................ 656 www.datasheet.co.kr datasheet pdf - http://www..net/
24 datasheet 19.1.65ulba ? upstream link base address register (pci express?d28:f0/f1/f2/f3) ............................................................ 657 19.1.66peetm ? pci express extended test mode register (pci express?d28:f0/f1/f2/f3) ............................................................ 657 20 high precision event timer registers ..................................................................... 658 20.1 memory mapped registers ................................................................................ 658 20.1.1 gcap_id?general capabilities and identifi cation register ...... ......... .......... 659 20.1.2 gen_conf?general configuration register ............................................. 660 20.1.3 gintr_sta?general interrupt status register......................................... 660 20.1.4 main_cnt?main counter value register ................................................. 661 20.1.5 timn_conf?timer n configuration and ca pabilities register .... ........... ...... 661 20.1.6 timn_comp?timer n comparator value register ..................................... 663 21 serial peripheral interface (spi)......................... ......................................................... 664 21.1 serial peripheral interface memory mapped co nfiguration registers........................ 664 21.1.1 spis?spi status register (spi memory mapped configuration registers).......................................... 665 21.1.2 spic?spi control register (spi memory mapped configuration registers).......................................... 666 21.1.3 spia?spi address register (spi memory mapped configuration registers).......................................... 667 21.1.4 spid[n] ?spi data n registe r (spi memory mapped configuration registers).......................................... 668 21.1.5 bbar?bios base address register (spi memory mapped configuration registers).......................................... 669 21.1.6 preop?prefix opcode configuration register (spi memory mapped configuration registers).......................................... 669 21.1.7 optype?opcode type configuration register (spi memory mapped configuration registers).......................................... 670 21.1.8 opmenu?opcode menu configuration register (spi memory mapped configuration registers).......................................... 670 21.1.9 pbr[n]?protected bios range [n] (spi memory mapped configuration registers).......................................... 671 figures figure 1-1 intel NM10 family express chipset features block diagram..........................31 figure 2-2 interface signals block diagram .......... .....................................................44 figure 2-3 example external rtc circuit ...................................................................63 figure 4-4 nettop only conceptual system clock diagram...........................................75 figure 4-5 netbook only conceptual clock diagram. ...................................................75 figure 5-6 generation of serr# to platform ..............................................................83 figure 5-7 64-word eeprom read instruction waveform ............................................91 figure 5-8 lpc interface diagram.............................................................................98 figure 5-9 lpc bridge serr# generation ................................................................ 104 figure 5-10 chipset dma controller.......................................................................... 104 figure 5-11 dma request assertion through ldrq# ................................................... 108 figure 5-12 coprocessor error timing diagram ....... ................................................... 134 figure 5-13 sata power states ............................................................................... 172 figure 5-14 usb legacy keyboard flow diagram ....................................................... 183 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 25 figure 5-15 chipset-usb port connections ............................................................... 191 figure 6-16 chipset ballout (topview?left side) ........................................................ 219 figure 6-17 chipset ballout (topview?right side) ...................................................... 220 figure 7-18 chipset package (top view) ................................................................... 225 figure 7-19 chipset package (bottom view) .............................................................. 226 figure 7-20 chipset package (side view) .................................................................. 226 figure 8-21 clock timing........................................................................................ 244 figure 8-22 valid delay from rising clock edge ......................................................... 244 figure 8-23 setup and hold times (tbd) .................................................................. 244 figure 8-24 float delay .......................................................................................... 244 figure 8-25 pulse width ......................................................................................... 245 figure 8-26 output enable delay ............................................................................. 245 figure 8-27 usb rise and fall times ........................................................................ 245 figure 8-28 usb jitter............................................................................................ 246 figure 8-29 usb eop width .................................................................................... 246 figure 8-30 smbus transaction ............................................................................... 246 figure 8-31 smbus timeout .................................................................................... 247 figure 8-32 power sequencing and reset signal timings (nettop only) ........................ 247 figure 8-33 power sequencing and reset signal timings (netbook only) ...................... 248 figure 8-34 g3 (mechanical off) to s0 timings (nettop only) ...................................... 249 figure 8-35 g3 (mechanical off) to s0 timings (netbook only).................................... 250 figure 8-36 s0 to s1 to s0 timing (nettop only) ....................................................... 251 figure 8-37 s0 to s5 to s0 timings, s3 cold (nettop only) .......................................... 251 figure 8-38 s0 to s5 to s0 timings, s3 hot (nettop only) ........................................... 252 figure 8-39 s0 to s5 to s0 timings, s3 cold (netbook only)........................................ 253 figure 8-40 s0 to s5 to s0 timings, s3 hot (netbook only) ......................................... 254 figure 8-41 c0 to c2 to c0 timings (netbook only) ................................................... 255 figure 8-42 c0 to c3 to c0 timings (nettop only) ..................................................... 255 figure 8-43 c0 to c4 to c0 timings (netbook only) ................................................... 256 figure 8-44 intel hd audio input and output timings................................................. 256 figure 8-45 spi timings ......................................................................................... 257 tables table 1-1 industry specifications ............................................................................ 30 table 1-2 pci devices and functions ....................................................................... 37 table 2-3 direct media interface signals .................................................................. 45 table 2-4 pci express* signals .............................................................................. 45 table 2-5 platform lan connect interface signals ..................................................... 45 table 2-6 eeprom interface signals........................................................................ 46 table 2-7 firmware hub interface signals............. ................................................... 46 table 2-8 pci interface signals .............................................................................. 47 table 2-9 serial ata interface signals ..................................................................... 49 table 2-10 lpc interface signals .............................................................................. 50 table 2-11 interrupt signals .................................................................................... 50 table 2-12 usb interface signals ............................................................................. 51 table 2-13 power management interface signals ........................................................ 52 table 2-14 processor interface signals ...................................................................... 54 table 2-15 sm bus interface signals ......................................................................... 56 table 2-16 system management interface signals ... ................................................... 56 table 2-17 real time clock interface ........................................................................ 56 www.datasheet.co.kr datasheet pdf - http://www..net/
26 datasheet table 2-18 other clocks ..........................................................................................57 table 2-19 miscellaneous signals ..............................................................................57 table 2-20 intel hd audio link signals ......................................................................58 table 2-21 serial peripheral interface (spi) signals .....................................................59 table 2-22 general purpose i/o signals.....................................................................59 table 2-23 power and ground signals .......................................................................60 table 2-24 functional strap definiti ons......................................................................61 table 3-25 integrated pull-up and pull-down resistors ................................................65 table 3-26 power plane and states for output and i/o signals .....................................67 table 3-27 power plane for input signals ...................................................................71 table 4-28 chipset and system clock domains...........................................................74 table 5-29 pci bridge initiator cycle types................................................................76 table 5-30 type 1 address format............................................................................79 table 5-31 msi vs. pci irq actions...........................................................................81 table 5-32 advanced tco functionality ................ .....................................................93 table 5-33 lpc cycle types supported ......................................................................99 table 5-34 start field bit definitions .........................................................................99 table 5-35 cycle type bit definitions ................. ..................................................... 100 table 5-36 transfer size bit definition..................................................................... 100 table 5-37 sync bit definition ............................................................................... 101 table 5-38 dma transfer size ................................................................................ 106 table 5-39 address shifting in 16-bit i/o dma transfers............................................ 106 table 5-40 counter operating modes ...................................................................... 112 table 5-41 interrupt controller core connections...... ................................................ 115 table 5-42 interrupt status registers...................................................................... 116 table 5-43 content of interrupt vector byte ............................................................. 116 table 5-44 apic interrupt mapping ......................................................................... 123 table 5-45 interrupt message address format.......................................................... 125 table 5-46 interrupt message data format .............................................................. 125 table 5-47 stop frame explanation......................................................................... 127 table 5-48 data frame format............................................................................... 128 table 5-49 configuration bits reset by rtcrst# a ssertion ........................................ 131 table 5-50 init# going active ............................................................................... 133 table 5-51 nmi sources ........................................................................................ 135 table 5-52 dp signal differences ............................................................................ 135 table 5-53 general power states for systems using chipset....................................... 137 table 5-54 state transition rules for chipset ........................................................... 138 table 5-55 system power plane.............................................................................. 139 table 5-56 causes of smi# and sci ........................................................................ 140 table 5-57 break events (netbook)......................................................................... 144 table 5-58 sleep types ......................................................................................... 148 table 5-59 causes of wake events.......................................................................... 148 table 5-60 gpi wake events .................................................................................. 149 table 5-61 transitions due to power failure .......... ................................................... 150 table 5-62 transitions due to power button .......... ................................................... 152 table 5-63 transitions due to ri# signal.............. ................................................... 153 table 5-64 write only registers with read paths in alt access mode .......................... 156 table 5-65 pic reserved bits return values ............................................................. 158 table 5-66 register write accesses in alt access mode ............................................. 158 table 5-67 chipset clock inputs ............................................................................. 161 table 5-68 heartbeat message data ........................................................................ 168 table 5-69 sata features support in chipset ........................................................... 169 table 5-70 sata feature description ...................................................................... 169 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 27 table 5-71 legacy replacement routing ................................................................. 175 table 5-72 bits maintained in low power states ....................................................... 182 table 5-73 usb legacy keyboard state transitions................................................... 184 table 5-74 uhci vs. ehci ..................................................................................... 185 table 5-75 debug port behavior ............................................................................. 194 table 5-76 i 2 c block read..................................................................................... 203 table 5-77 enable for smbalert# ......................................................................... 206 table 5-78 enables for smbus slave write and smbus host events ............................. 206 table 5-79 enables for the host notify command ..................................................... 206 table 5-80 slave write registers ............................................................................ 208 table 5-81 command types .................................................................................. 209 table 5-82 read cycle format ............................................................................... 210 table 5-83 data values for slave read registers ...................................................... 210 table 5-84 host notify format ............................................................................... 212 table 5-85 spi implementation options .................................................................. 214 table 5-86 required commands and opcodes .......................................................... 215 table 5-87 chipset standard spi commands ........................................................... 215 table 5-88 flash protection mechanism summary..... ................................................ 216 table 6-89 chipset ballout by signal name .............................................................. 221 table 8-90 chipset absolute maximum ratings........................................................ 227 table 8-91 dc current characteristics................ ..................................................... 228 table 8-92 dc characteristic input signal associat ion ............................................... 228 table 8-93 dc input characteristics........................................................................ 229 table 8-94 dc characteristic output signal associ ation ............................................. 231 table 8-95 dc output characteristics................. ..................................................... 232 table 8-96 other dc characteristics ....................................................................... 234 table 8-97 clock timings ...................................................................................... 235 table 8-98 sata interface timings ......................................................................... 236 table 8-99 smbus timing ...................................................................................... 236 table 8-100 intel hd audio timing ........................................................................... 237 table 8-101 lpc timing .......................................................................................... 237 table 8-102 miscellaneous timings........................................................................... 238 table 8-103 spi timings ......................................................................................... 238 table 8-104 (power sequencing and reset signal timings ........................................... 238 table 8-105 power management timings................................................................... 240 table 9-106 pci devices and functions ..................................................................... 259 table 9-107 fixed i/o ranges decoded by chipset ..................................................... 260 table 9-108 variable i/o decode ranges .................................................................. 263 table 9-109 memory decode ranges from processo r perspective.................................. 264 table 10-110 chipset configuration register me mory map (memory space)..................... 267 table 11-111 lan controller pci register address map (lan controller?b1:d8:f0) ......... 302 table 11-112 configuration of subsystem id and subsystem vendor id via eeprom ........ 309 table 11-113 data register structure.................. ....................................................... 313 table 11-114 chipset integrated lan controller csr space register address map ............ 313 table 11-115 self-test results format ....................................................................... 319 table 11-116 statistical counters........................ ....................................................... 326 table 11-117 asf register address map ..................................................................... 328 table 12-118 pci bridge register address map (pci-pci?d30:f0) ................................. 342 table 13-119 lpc interface pci register address map (lpc i/f?d31:f0) ........................ 358 table 13-120 dma registers ..................................................................................... 377 table 13-121 pic registers (lpc i/f?d31:f0)............................................................. 387 table 13-122 apic direct registers (lpc i/f?d31:f0) ................................................. 394 table 13-123 apic indirect registers (lpc i/f?d31:f0) ............................................... 394 www.datasheet.co.kr datasheet pdf - http://www..net/
28 datasheet table 13-124 rtc i/o registers (lpc i/f?d31:f0)....................................................... 399 table 13-125 rtc (standard) ram bank (lpc i/f?d31:f0) ........................................... 400 table 13-126 processor interface pci register a ddress map (lpc i/f?d31:f0) ................ 403 table 13-127 power management pci register address map (pm?d31:f0)...................... 407 table 13-128 apm register map ................................................................................. 415 table 13-129 acpi and legacy i/o register map .......................................................... 416 table 13-130 tco i/o register address map................................................................ 438 table 13-131 registers to control gpio address map.................................................... 445 table 14-132 uhci controller pci register addr ess map (usb?d29:f0/f1/f2/f3)............ 450 table 14-133 usb i/o registers................................................................................. 460 table 14-134 run/stop, debug bit interaction swdbg (bit 5), run/stop (bit 0) operation 462 table 15-135 sata controller pci register address map (sata?d31:f2)......................... 470 table 15-136 bus master ide i/o register address map ................................................ 497 table 15-137 ahci register address map .................................................................... 501 table 15-138 generic host controller register address map........................................... 501 table 15-139 port [1:0] dma register address map ...................................................... 505 table 16-140 usb ehci pci register address map (usb ehci?d29:f7).......................... 519 table 16-141 enhanced host controller capability re gisters ................... .......... ............. 535 table 16-142 enhanced host controller operational register address map ....................... 538 table 16-143 debug port register address map ........ ................................................... 551 table 17-144 smbus controller pci register address map (smbus?d31:f3) ................... 555 table 17-145 smbus i/o register address map ............................................................ 560 table 18-146 intel hd audio pci register address map (intel hd audio d27:f0) ........................................................................ 573 table 18-147 intel hd audio pci register address map (intel hd audio d27:f0) ........................................................................ 592 table 19-148 pci express* configuration registers address map (pci express?d28:f0/f1/f2/f3) ............................................................ 621 table 20-149 memory-mapped registers ..................................................................... 658 table 21-150 serial peripheral interface (spi) register address map (spi memory mapped configuration registers).......................................... 664 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 29 revision history revision desc ription date 001 ? initial release december 2009 www.datasheet.co.kr datasheet pdf - http://www..net/
introduction 30 datasheet 1 introduction this document provides specifications fo r the intel? NM10 family express chipset, which is designed for use in intel?s next generation nettop platform. note: in this document the intel NM10 family ex press chipset is referred to as the chipset. this document is intended for original equipment manufacturers and bios vendors. this manual assumes a working knowledge of the vocabulary and principles of pci express*, usb, ahci, sata, intel? high de finition audio (intel hd audio), smbus, pci, acpi and lpc. although some details of these features are described within this manual, refer to the individual in dustry specifications listed in ta b l e 1 - 1 for the complete details. table 1-1. industry specifications specification location pci express* base specification, revision 1.0a http://www.pcisig.com/specifications low pin count interface specification, revision 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/ pci local bus specification, 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, revision 1.1 http://www.pcisig.com/specifications universal serial bus specification (usb), revision 2.0 http://www.usb.org/developers/docs advanced configuration an d power interface, version 2.0 (acpi) http://www.acpi.info/spec.htm universal host controller in terface, revision 1.1 (uhci) http://developer.intel.com/design/ 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, revision 1.0 http://www.serialata.org/ specifications.asp alert standard format sp ecification, version 1.03 http://www.dmtf.org/standards/asf ieee 802.3 fast ethernet http://standards.ieee.org/ getieee802/ at attachment - 6 with pack et interface (ata/atapi - 6) http://t13.org (t13 1410d) ia-pc hpet (high precision event timers) specification, revision 1.0 http://www.intel.com/ hardwaredesign/hpetspec.htm www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 31 introduction figure 1-1 provides a block diagram of the intel NM10 series express chipset family in the nettop platform. 1.1 intel? NM10 family express chipset feature support ? direct media interface ? 10 gb/s each direction, full duplex ? transparent to software ? pci express* ? 4 pci express root ports ? supports pci express 1.0a ? 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 ? pci bus interface ? supports pci rev 2.3 specification at 33 mhz figure 1-1. intel NM10 family express chipset features block diagram www.datasheet.co.kr datasheet pdf - http://www..net/
introduction 32 datasheet ? 2 available pci req/gnt pairs support fo r 64-bit addressing on pci using dac protocol ? integrated serial ata host controller ?two ports ? data transfer rates up to 3.0 gb/s (300 mb/s) ? integrated ahci controller ? intel hd audio interface ? pci express endpoint ? independent bus master logic for eight general purpose streams: four input and four output ? support three external codecs ? supports variable length stream slots ? supports multichannel, 32-bit sample depth and 192 khz sample rate output ? provides mic array support ? allows for non-48 khz sampling output ? support for acpi device states ? smbus ? 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 internal or external microcontroller to access system resources ? compatible with most two-wire components that are also i 2 c 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 converter implementation ? system tco reduction circuits ? timers to generate smi# and reset upon detection of system hang ? timers to detect improper processor reset www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 33 introduction ? integrated processor frequency strap logic ? supports ability to disable external devices ? usb 2.0 ? includes four uhci host controllers, supporting eight external ports ? includes one ehci host controller that supports all eight ports ? includes one usb 2.0 high-speed debug port ? supports wake-up from sleeping states s1?s5 ? supports legacy keyboard/mouse software ? integrated lan controller ? integrated asf management controller ? supports ieee 802.3 ? lan connect interface (lci) ? 10/100 mb/s ethernet support ? power management logic ? supports acpi 3.0 ? acpi-defined power states (c1, s1, s3?s5 for nettop and c1?c4, s1, s3?s5 for netbook) ? acpi power management timer ? support for ?intel speedstep ? technology? processor power control and ?deeper sleep? power state ? pci clkrun# 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 nettop and netbook implementations ? external glue integration ? integrated pull-up, pull-down and series termination resistors on processor interface ? integrated pull-down and series resistors on usb ? enhanced dma controller ? two cascaded 8237 dma controllers ?supports lpc dma ? interrupt controller ? supports up to eight pci interrupt pins ? supports pci 2.3 message signaled interrupts ? two cascaded 82c59 with 15 interrupts www.datasheet.co.kr datasheet pdf - http://www..net/
introduction 34 datasheet ? integrated i/o apic capability with 24 interrupts ? supports processor system bus interrupt delivery ? 1.05 v operation with 1.5 v and 3.3 v i/o ? 5 v tolerant buffers on pci, usb and legacy signals ? 1.05 v core voltage ? integrated 1.05 v voltage regulator (intvr) for the suspend and lan wells firmware hub i/f supports bios memory size up to 8 mbytes ? serial peripheral interface (spi) for serial and shared flash ? 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 ? package 17 mm x17 mm 360 mmap 1.2 content layout chapter 1. introduction this chapter introduces intel NM10 expre ss chipset and provides information on manual organization and gives a general overview of chipset. chapter 2. signal description this chapter provides a block diagram of in tel NM10 express chipset interface signals and a detailed description of each signal. signals are arranged according to interface and details are provided as to the drive char acteristics (input/output, open drain, etc.) of all signals. chapter 3. intel NM10 ex press chipset pin states this chapter provides a complete list of signals, their associated power well, their logic level in each suspend state, and thei r logic level before and after reset. chapter 4. intel NM10 express ch ipset and system clock domains this chapter provides a list of each clock domain associated with intel NM10 express chipset in a chipset-based system. chapter 5. functional description this chapter provides a detailed description of the functions in the intel NM10 express chipset. all pci buses, devices and function s in this manual are abbreviated using the following nomenclature; bus:device:function. this manual abbreviates buses as b0 and b1, devices as d8, d27, d28, d29, d3 0 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 1 device 8 function 0 is abbreviated as b1:d 8:f0. generally, the bus number will not be www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 35 introduction used, and can be considered to be bus 0. note that intel NM10 express chipset?s external pci bus is typically bus 1, but may be assigned a different number depending upon system configuration. chapter 6. ballout definition this chapter provides a table of each sign al and its ball assignment in the 360-mmap package. chapter 7. package information this chapter provides drawings of the physical dimensions and characteristics of the 360-mmap package. chapter 8. electrical characteristics this chapter provides all ac and dc charac teristics including detailed timing diagrams. chapter 9. register and memory mappings this chapter provides an overview of the registers, fixed i/o ranges, variable i/o ranges and memory ranges decoded by intel NM10 express chipset. chapter 10. chipset configuration registers this chapter provides a detailed description of all registers and base functionality that is related to chipset configuration and not a sp ecific 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. lan controller registers this chapter provides a detailed description of all registers that reside in intel NM10 express chipset?s integrated lan controller. the integrated lan controller resides on chipset's external pci bus (typically bus 1) at device 8, function 0 (b1:d8:f0). chapter 12. pci-to-pci bridge registers this chapter provides a detailed description of all registers th at reside in the pci-to-pci bridge. this bridge resides at device 30, function 0 (d30:f0). chapter 13. lpc br idge registers this chapter 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 intel NM10 express chipset including dma, timers, interrupts, processor interfac e, gpio, power management, system management and rtc. chapter 14. sata controller registers this chapter provides a detailed description of all registers that reside in the sata controller. this controller resides at device 31, function 2 (d31:f2). www.datasheet.co.kr datasheet pdf - http://www..net/
introduction 36 datasheet chapter 15. uhci controller registers this chapter provides a detailed description of all registers that reside in the four uhci host controllers. these controllers reside at device 29, functions 0, 1, 2, and 3 (d29:f0/f1/f2/f3). chapter 16. ehci co ntroller registers this chapter provides a detailed description of all registers that reside in the ehci host controller. this controller resides at device 29, function 7 (d29:f7). chapter 17. smbus co ntroller registers this chapter provides a detailed description of all registers that reside in the smbus controller. this controller resides at device 31, function 3 (d31:f3). chapter 18. intel hd audio controller registers this chapter provides a detailed description of all registers that reside in the intel hd audio controller. this controller resides at device 27, function 0 (d27:f0). chapter 19. pci express* port controller registers this chapter provides a detailed description of all registers that reside in the pci express controller. this controller resides at device 28, functions 0 to 3(d30:f0-f3). chapter 20. high precision e vent timers registers this chapter provides a detailed description of all registers that reside in the multimedia timer memory mapped register space. chapter 21. serial periph eral interface registers this chapter provides a detailed description of all registers that reside in the spi memory mapped register space. 1.3 functions and capabilities this chipset provides extensive i/o su pport. functions and capabilities include: ? pci express* base specification, revision 1.0a support ? pci local bus specification , revision 2.3 support for 33 mhz pci operations ? acpi power management logic support ? enhanced dma controller, interrupt controller, and timer functions ? integrated serial ata host controller with independent dma operation on two ports and ahci support. ? usb host interface with support for eight usb ports; four uhci host controllers; one ehci high-speed usb 2.0 host controller ? integrated lan controller ? system management bus (smbus) specification , version 2.0 with additional support for i 2 c devices ? supports intel high definition audio ? supports intel ? matrix storage technology ? low pin count (lpc) interface www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 37 introduction ? firmware hub (fwh) interface support ? serial peripheral interface (spi) support this chipset incorporates a variety of pci functions that are divided into six logical devices (b0:d27, b0:d28, b0:d29, b0:d30, b0:d31 and b1:d8) as listed in ta b l e 1 - 2 . d30 is the dmi-to-pci bridge, d31 contains the pci-to-lpc bridge, sata controller, and smbus controller, d29 contains the four usb uhci controllers and one usb ehci controller, and d27 contains the pci express root ports. b1:d8 is the integrated lan controller. notes: 1 the pci-to-lpc bridge cont ains registers that control lpc, power management, system management, gpio, processor interface , rtc, interrupts, timers, and dma. the following sub-sections provide an ov erview of intel NM10 express chipset capabilities. direct media interface (dmi) direct media interface (dmi) is the chip-to-chip connection between the processor or mch and chipset. this high-speed interface integrates advanced priority-based servicing allowing for concurrent traffic and true isochronous transfer capabilities. base functionality is completely software-tra nsparent, permitting current and legacy software to operate normally. table 1-2. pci devices and functions bus:device:function function description bus 0:device 30:functi on 0 pci-to-pci bridge bus 0:device 31:function 0 lpc controller 1 bus 0:device 31:function 2 sata controller bus 0:device 31:functi on 3 smbus controller 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 #4 bus 0:device 29:function 7 usb 2.0 ehci controller 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 27:function 0 i ntel hd audio controller bus n:device 8:function 0 lan controller www.datasheet.co.kr datasheet pdf - http://www..net/
introduction 38 datasheet pci express* interface intel NM10 express chipset has four pci express root ports (ports 1-4), supporting the pci express base specification, revision 1.0a. pci express root ports 1?4 can be statically configured as four x1 ports or ganged together to form one x4 port. each root port supports 2.5 gb/s bandwidth in each direction (5 gb/s concurrent). serial ata (sata) controller intel NM10 express chipset has an integrated sata host controller that supports independent dma operation on two ports and supports data transfer rates of up to 3.0 gb/s (300 mb/s). the sata controller co ntains two modes of operation ? a legacy mode using i/o space, and an ahci mode using memory space. intel NM10 express chipset supports the serial ata specification , revision 1.0a.this chipset 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). ahci intel NM10 express chipset provides hardwa re 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. pci interface intel NM10 express chipset pci interface provides a 33 mhz, revision 2.3 implementation. this chipset integrates a pci arbiter that supports up to two external pci bus masters in addition to the inte rnal chipset requests. this allows for combinations of up to two pci down devices and pci slots. low pin count (lpc) interface intel NM10 express chipset implements an lpc interface as described in the lpc 1.1 specification . the low pin count (lpc) bridge functi on of this chipset resides in pci device 31:function 0. in addition to the lp c 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) intel NM10 express chipset 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 39 introduction compatibility modules (dma controller, timer/counters, inte rrupt 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 transfers. any two of the seven dma channels can be prog rammed to support fast type-f transfers. intel NM10 express chipset supports lpc dma, which is similar to isa dma, through chipset's dma controller. lpc dma is handle d 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. channels 0?3 are 8-bit channels. channels 5?7 are 16-bit channels . channel 4 is reserved as a generic bus master request. 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. intel NM10 express chipset provides an isa-compatible programmable interrupt controller (pic) that incorporates the functi onality of two, 82c59 interrupt controllers. the two interrupt controllers are cascaded so that 14 external and two internal interrupts are possible. in addition, this chipset supports a serial interrupt scheme. 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 in terrupt controller (apic) in addition to the standard isa compatib le programmable interrupt controller (pic) described in the previous section, th is chipset incorporates the advanced programmable interrupt controller (apic). universal serial bus (usb) controller intel NM10 express chipset contains an enhanced host controller interface (ehci) host controller that supports 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. this chipset also contains four universal host controller inte rface (uhci) controllers that support usb full-speed and low-speed signaling. intel NM10 express chipset supports eight usb 2.0 ports. all eight ports are high- speed, full-speed, and low-speed capable. this chipset's port-routing logic determines whether a usb port is controlled by one of the uhci controllers or by the ehci controller. see section 5.18 and section 5.19 for details. www.datasheet.co.kr datasheet pdf - http://www..net/
introduction 40 datasheet lan controller intel NM10 express chipset?s integrated lan controller includes a 32-bit pci controller that provides enhanced scatter-gather bus mastering capabilities and enables the lan controller to perform high speed data transfers over the pci bus. its bus master capabilities enable the component to pr ocess high-level commands and perform multiple operations; this lowers processor utilization by off-loading communication tasks from the processor. two large transmit and receive fifos of 3 kb each help prevent data underruns and overruns while waiting for bus accesses. this enables the integrated lan controller to transmit data with minimum interframe spacing (ifs). the lan controller can operate 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. alert standard format (asf) management controller intel NM10 express chipset integrates an al ert standard format controller in addition to the integrated lan controller, allowing interface system-monitoring devices to communicate through the integrated lan cont roller to the network. this makes remote manageability and system hardware monitoring possible using asf. the asf controller can collect and send various information from system components such as the processor, chipset, bios and sensors on the motherboard to a remote server running a management console. th e controller can also be programmed to accept commands back from the management console and execute those commands on the local system. rtc intel NM10 express chipset 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 rtc also supports two lockable memory ranges. 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 rtc also supports a date alarm that allows for scheduling a wake 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 intel NM10 express chipset configuration. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 41 introduction enhanced power management intel NM10 express chipset?s power manage ment functions include enhanced clock control and various low-power (suspend) states (e.g., suspend-to-ram and suspend- to-disk). a hardware-based thermal manageme nt circuit permits software-independent entrance to low-power states. this chipset contains full support for the advanced configuration and power interf ace (acpi) specification, revision 3.0. manageability intel NM10 express chipset integrates seve ral 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. chipset?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 from a software lock. the second expiration of the timer causes a system reset to recover from a hardware lock. ? processor present indicator. chipset looks for the processor to fetch the first instruction after reset. if the processor does not fetch the first instruction, chipset 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 chipset. the host controller can instruct chipset to generate either an sm i#, nmi, serr#, or tco interrupt. ? function disable. chipset provides the ability to disable the following integrated functions: lan, usb, lpc, intel hd audio, sata, 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 disable functions. ? intruder detect. chipset provides an input sign al (intruder#) that can be attached to a switch that is activated by the system case being opened. chipset can be programmed to generate an smi# or tc o interrupt due to an active intruder# signal. system management bus (smbus 2.0) this chipset contains an smbus host in terface that allows the processor to communicate with smbus slaves. this interface is compatible with most i 2 c devices. special i 2 c commands are implemented. this chipset's smbus host controller provides a mechanism for the processor to initiate communications with smbus peripherals (slaves). also, this chipset supports slave functionality, including the host notify pr otocol. hence, the host controller supports eight command protocols of the smbus interface (see system management bus (smbus) specification, version 2.0): quick command, send byte, receive byte, write byte/word, read byte/word, process ca ll, block read/write, and host notify. www.datasheet.co.kr datasheet pdf - http://www..net/
introduction 42 datasheet chipset?s smbus also implements hardware-based packet error checking for data robustness and the address resolution protoc ol (arp) to dynamically provide address to all smbus devices. intel? hd audio controller (intel? hd audio) the intel hd audio specification defines a digital interface that can be used to attach different types of codecs, such as audio an d modem codecs. in this chipset intel hd audio digital link shares pins with the ac-link. chipset?s intel hd audio controller supports up to three codecs. with the support of multi-channel audio stre am, 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 si de, chipset adds support for an arrays of microphones. the intel hd audio controller uses multi-pu rpose dma engines, to effectively manage the link bandwidth and support simultaneous independent streams on the link. the capability enables new exciting usage models with intel hd audio (e.g., listening to music while playing multi-player game on th e internet.) the intel hd audio controller also supports isochronous data transfers allowing glitch-free audio to the system. note: users interested in providing feedback on the intel high definition audio specification or planning to implement the intel high definition audio specification into a future product will need to execute the intel high definition audio specification developer?s agreement . for more information, contact nextgenaudio@intel.com. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 43 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. figure 2-2 and section 2.1 shows the interface signals for chipset. the ?#? symbol at the end of the signal na me 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 ?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# for signals in the rtc well, rsmrst# for signals in the suspend well, after pwrok for signals in the core well, and after lan_rst# for signals in the lan well. the following notations are used to describe the signal type: i input 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. oc open collector output pin. www.datasheet.co.kr datasheet pdf - http://www..net/
signal description 44 datasheet figure 2-2. interface signals block diagram www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 45 signal description 2.1 direct media interface (dmi) to host controller 2.2 pci express* 2.3 platform lan connect interface table 2-3. direct media interface signals name type description dmi[0:1]txp, dmi[0:1]txn dmi[2:3]txp, dmi[2:3]txn o direct media interface diffe rential transmit pair 0:3 dmi[0:1]rxp, dmi[0:1]rxn dmi[2:3]rxp, dmi[2:3]rxn i direct media interface diffe rential receive pair 0:3 dmi_zcomp i impedance compensation input: determines dmi input impedance. dmi_ircomp o impedance/current compensation output: determines dmi output impedance and bias current. table 2-4. pci express* signals name type description petp[1:4], petn[1:4] o pci express* differentia l transmit pair 1:4 perp[1:4], pern[1:4] i pci express differential receive pair 1:4 table 2-5. platform lan connect interface signals name type description lan_clk i lan i/f clock: this signal is driven by the platform lan connect component. the frequency range is 5 mhz to 50 mhz. lan_rxd[2:0] i received data: the platform lan connect component uses these signals to transfer data and contro l information to the integrated lan controller. these signals have in tegrated weak pu ll-up resistors. lan_txd[2:0] o transmit data : the integrated lan controller uses these signals to transfer data and control informat ion to the platform lan connect component. lan_rstsync o lan reset/sync: the platform lan connec t component?s reset and sync signals are multiplexed onto this pin. www.datasheet.co.kr datasheet pdf - http://www..net/
signal description 46 datasheet 2.4 eeprom interface 2.5 firmware hub interface table 2-6. eeprom interface signals name type description ee_shclk o eeprom shift clock : this signal is the serial shift clock output to the eeprom. ee_din i eeprom data in : this signal transfers data from the eeprom to chipset. this signal has an integrated pull -up resistor. ee_dout o eeprom data out : this signal transfers data from chipset to the eeprom. ee_cs o eeprom chip select : this is the chip select signal to the eeprom. table 2-7. firmware hub interface signals name type description fwh[3:0] / lad[3:0] i/o firmware hub signals: these sign als are multiplexed with the lpc address signals. fwh4 / lframe# o firmware hub signals: this signal is multiplexed with the lpc lframe# signal. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 47 signal description 2.6 pci interface table 2-8. 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 transact ion, ad[31:0] co ntain a physical address (32 bits). during subseque nt clocks, ad[31:0] contain data. chipset 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]b define the bus command. during the data phase, c/be[3:0]b defi ne the byte enables. all command encodings not shown are reserved. chipset does not decode reserved values, and therefor e will not respond if a pci master generates a cycle using one of the reserved values. devsel# i/o device select : chipset asserts devselb to claim a pci transaction. as an output, chipset asserts devsel# when a pci master peripheral attempts an access to an internal chipset address or an address destined dmi (main memory or gr aphics). as an input, devsel# indicates the response to an chipset-initiated transaction on the pci bus. devsel# is tri-stated from the leading edge of pltrst#. devsel# remains tri-stated by chipset 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 tran saction. while the initiator asserts frame#, data transfers continue. wh en the initiator negates frame#, the transaction is in the final data phase. frame# is an input to chipset when chipset is the target, and frame# is an output from chipset when chipset is the initiator. frame# re mains tri-stated by chipset until driven by an initiator. irdy# i/o initiator ready : irdy# indicates chipset's ability, as an initiator, to complete the current data phase of the transaction. it is used in conjunction with trdy#. a data phas e is completed on any clock both irdy# and trdy# are sampled asse rted. during a write, irdy# indicates chipset has valid data pres ent on ad[31:0]. during a read, it indicates chipset is prepared to latch data. irdy# is an input to chipset when chipset is the target and an output from chipset when chipset is an initiator. irdy# remains tri-stat ed by chipset 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 www.datasheet.co.kr datasheet pdf - http://www..net/
signal description 48 datasheet trdy# i/o target ready : trdy# indicates chipset's ability as a target to complete the current data phase of the transaction. trdy# is used in conjunction with irdy#. a data ph ase is completed when both trdy# and irdy# are sampled asserted. duri ng a read, trdyb indicates that chipset, as a target, has placed vali d data on ad[31:0]. during a write, trdy# indicates chipset, as a target is prepared to latch data. trdy# is an input to chipset when chipset is the initiator and an output from chipset when chipset is a target. t rdy# is tri-stated from the leading edge of pltrst#. trdy# remains tri-stated by chipset until driven by a target. stop# i/o stop : stop# indicates that chipset, as a target, is requesting the initiator to stop the cu rrent transaction. stop# causes chipset, as an initiator, to stop the current tran saction. stopb is an output when chipset is a target and an input when chipset 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]b. ?even? parity means that chipset counts the number of 1s within th e 36 bits plus par and the sum is always even. chipset calculates par on 36 bits regardless of the valid byte enables. chipset generates pa r for address and data phases and only ensures par to be valid one pci clock after the corresponding address or data phase. chipset drives and tri-states par identically to the ad[31:0] lines except that chipset delays par by exactly one pci clock. par is an output during the address phase (delayed one clock) for all chipset initiated transactions. par is an output during the data phase (delayed one clock) when chipset is the initiator of a pci write transaction, and when it is the targ et of a read transaction. chipset checks parity when it is the target of a pci write transaction. if a parity error is detected, chipse t will set the appropriat e internal status bits, and has the option to generate an nmib or smib. perr# i/o parity error : an external pci device driv es perrb when it receives data that has a parity error. chip set drives perrb when it detects a parity error. chipset can either generate an nmib or smib upon detecting a parity error (either detected internally or reported via the perr# signal). req[2:1] i pci requests: chipset supports up to 2 masters on the pci bus. gnt[2:1]# o pci grants: chipset supports up to 2 masters on the pci bus. pull-up resistors are not required on these signals. if pull-ups are used, they should be tied to the vcc3_3 power rail. pciclk i pci clock : this is a 33 mhz clock. pc iclk provides timing for all transactions on the pci bus. pcirst# o pci reset: this is the secondary pci bus reset signal. it is a logical or of the primary interface pltr st# signal and the state of the secondary bus reset bit of the bridge control register (d30:f0:3eh, bit 6). table 2-8. pci interface signals (sheet 2 of 3) name type description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 49 signal description 2.7 serial ata interface plock# i/o pci lock : this signal indicates an exclusive bus operation and may require multiple transactions to complete. chipset asserts plock# when it performs non-exclusive transactions on the pci bus. plock# is ignored when pci masters are granted the bus in nettop configurations. devices on the pci bus (other than chipset) are not permitted to assert th e plock# signal in netbook configurations. serr# i/od system error : serr# can be pulsed active by any pci device that detects a system error condition. upon sampling serr# active, chipset 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 chipset may drive pme# active due to an inte rnal wake event. chipset will not drive pme# high, but it will be pull ed up to vccsus3_3 by an internal pull-up resistor. table 2-9. serial ata interface signals name type description sata0txp sata0txn o serial ata 0 differential transmit pair: these are outbound high-speed differential signals to port 0. sata0rxp sata0rxn i serial ata 0 differential receive pair: these are inbound high- speed differential si gnals from port 0. sata1txp sata1txn o serial ata 1 differential transmit pair: these are outbound high-speed differential signals to port 1. sata1rxp sata1rxn i serial ata 1 differential receive pair: these are inbound high- speed differential si gnals from port 1. satarbias o serial ata resistor bias: these are analog connection points for an external resistor to ground. satarbias# i serial ata resistor bias complement: these are analog connection points for an ex ternal resistor to ground. sataled# oc serial ata led: this is an open-c ollector output pin driven during sata command activity. it is to be connected to external circuitry that can provide the current to dr ive a platform led. when active, the led is on. when tri-stated, the led is off. an external pull-up resistor to vcc 3_3 is required. note: an internal pull-up is en abled only during pltrst# assertion. table 2-8. pci interface signals (sheet 3 of 3) name type description www.datasheet.co.kr datasheet pdf - http://www..net/
signal description 50 datasheet 2.8 lpc interface 2.9 interrupt interface table 2-10.lpc interface signals 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 o lpc 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 master access. these signals are typically connected to external super i/o devi ce. an internal pull-up resistor is provided on these signals. ldrq1# may optionally be used as gpio. table 2-11.inter rupt signals name type description serirq i/o serial interrupt request: 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 the interrupt steering section. 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 the interrupt steering section. 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 interr upts, these signals can be used as gpio. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 51 signal description 2.10 usb interface table 2-12.usb interface signals name type description usbp0p, usbp0n, usbp1p, usbp1n i/o universal serial bus port [1:0] differential : these differential pairs are used to transmit data /address/command si gnals for ports 0 and 1. these ports can be routed to uhci controller #1 or the ehci controller. note: no external resistors are requ ired on these signals. the chipset 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 transmit data /address/command signals for ports 2 and 3. these ports can be routed to uhci controller #2 or the ehci controller. note: no external resistors are requir ed on these signals. chipset integrates 15 k pull-downs and provides an output driver impedance of 45 which requires no ex ternal series resistor usbp4p, usbp4n, usbp5p, usbp5n i/o universal serial bus port [5:4] differential : these differential pairs are used to transmit data /address/command si gnals for ports 4 and 5. these ports can be routed to uhci controller #3 or the ehci controller. note: no external resistors are requir ed on these signals. chipset integrates 15 k pull-downs and provides an output driver impedance of 45 which requires no ex ternal series resistor usbp6p, usbp6n, usbp7p, usbp7n i/o universal serial bus port [7:6] differential : these differential pairs are used to transmit data /address/command si gnals for ports 6 and 7. these ports can be routed to uhci controller #4 or the ehci controller. note: no external resistors are requ ired on these signals. the chipset integrates 15 k pull-downs and provides an output driver impedance of 45 which requires no external series resistor oc[4:0]# oc5# / gpio29 oc6# / gpio30 oc7# / gpio31 i overcurrent indicators: these signals set corresponding bits in the usb controllers to indicate th at an overcurrent condition has occurred. oc[7:5]# may optionally be used as gpios. note: oc[7:0]# are not 5 v tolerant. usbrbias o usb resistor bias: analog connection po int for an external resistor. used to set transmit cu rrents and internal load resistors. usbrbias# i usb resistor bias complement: analog connection point for an external resistor. used to set tr ansmit currents an d internal load resistors. www.datasheet.co.kr datasheet pdf - http://www..net/
signal description 52 datasheet 2.11 power management interface table 2-13.power management in terface signals (sheet 1 of 3) name type description pltrst# o platform reset: the chipset asserts pltrst# to reset devices on the platform (e.g., sio, fwh, lan, (g)mch, ide, tpm, etc.). the chipset asserts pltrst# during po wer-up and when s/w initiates a hard reset sequence through the rese t control register (i/o register cf9h). the chipset drives pltrst# inactive a minimum of 1 ms after both pwrok and vrmpwrgd are dr iven high. the chipset 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# i thermal alarm: thrm# is an active low signal generated by external hardware to generate an smi# or sci. thrmtrip# i thermal trip: when low, this signal in dicates that a thermal trip from the processor occurred, an d the chipset will immediately transition to a s5 state. the chip set will not wait for the processor stop grant cycle since the processor has overheated. slp_s3# o s3 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 off) state. note: this pin must be used to co ntrol the dram power to use chipset?s dram power-cycl ing feature. refer to chapter 5.14.11.2 for details. slp_s5# o s5 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. pwrok i power ok: when asserted, pwrok is an indication to the chipset that core power has been stable fo r 99 ms and that pciclk has been stable for 1 ms. an exception to this rule is if the system is in s3 hot , in which pwrok may or may not stay asserted even though pciclk may be inactive. pwrok can be driven asynchronously. when pwrok is negated, the chipset asserts pltrst#. note: pwrok must deassert for a minimum of three rtc clock periods for the chipset to full y reset the power and properly generate the pltrst# output. pwrbtn# i power button: the power button will cause smi# or sci to indicate a system request to go to a sleep st ate. 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 intern al 16 ms de-bounc e on the input. ri# i ring indicate: this signal is an input from a modem. it can be enabled as a wake event, and this is preserved across power failures. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 53 signal description sys_reset# i system reset: this pin forces an inte rnal reset after being debounced. the chipset 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 re set on the system. rsmrst# i resume well reset: this signal is used fo r resetting the resume power plane logic. lan_rst# i lan reset: when asserted, the internal lan controller will be put into reset. this signal must be as serted for at least 10 ms after the resume well power is valid. when deasserted, this signal is an indication that the resume well power is stable. note: lan_rst# should be tied to rsmrst#. wake# i pci express* wake event: sideband wake signal on pci express asserted by components requesting wake up. mch_sync# i mch sync: this input is internally anded with the pwrok input. connect to the ich_sync# output of (g)mch. this signal need to pull-up to vcc3_3 when the chipset is not pair with (g)mch. sus_stat# / lpcpd# o suspend status: this signal is asserted by the chipset 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 th ey should isolate their outputs that may be going to powered-off planes. this signal is called lpcpd# on the lpc interface. susclk o suspend clock: this clock is an output of the rtc generator circuit to use by other chips for refresh clock. vrmpwrgd i vrm power good: this should be connected to be the processor?s vrm power good signifying the vrm is stable. this signal is internally anded with the pwrok input. bm_busy#/ gpio0 i bus master busy: this signal supports the c3 state. it provides an indication that a bus master device is busy. when this signal is asserted, the bm_sts bit will be set. if this signal goes active in a c3 state, it is treated as a break event. note: this signal is internally sync hronized using the pciclk and a two-stage synchronizer. it does not need to meet any particular setup or hold time. clkrun# i/o pci clock run: this clock supports the pci clkrun protocol. it connects to peripherals that ne ed to request clock restart or prevention of clock stopping. stp_pci# 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. if this functional ity is not needed, this signal can be configured as a gpio. stp_cpu# o stop cpu clock: this signal is an outp ut to the external clock generator for it to turn off the proc essor clock. it is used to support the c3 state. if this functionality is not needed, this signal can be configured as a gpio. table 2-13.power management in terface signals (sheet 2 of 3) name type description www.datasheet.co.kr datasheet pdf - http://www..net/
signal description 54 datasheet 2.12 processor interface batlow# i battery low: this signal is an input fro m battery to indicate that there is insufficient power to boot the system. assertion will prevent wake from s3?s5 state. this signal can also be enabled to cause an smi# when asserted. dprslpvr o deeper sleep - voltage regulator: this signal is used to lower the voltage of vrm during the c4 state. when the signal is high, the voltage regulator outputs the lower ?deeper sleep? voltage. when low (default), the voltage regulator outputs the higher ?normal? voltage. dprstp# o deeper stop: this is a copy of the dprslpvr and it is active low. table 2-14.processor interfac e signals (sheet 1 of 2) name type description a20m# o mask a20: a20m# will go active based on either setting the appropriate bit in the port 92h register, or base d on the a20gate input being active. cpuslp# o cpu sleep: this signal puts the proce ssor into a state that saves substantial power compared to stop-g rant state. however, during that time, no snoops occur. the chipset can optionally assert the cpuslp# signal when going to the s1 state. ferr# i numeric coprocessor error: this signal is tied to the coprocessor error signal on the processor. ferr# is only used if the chipset co- processor error reporting function is enabled in the oic.cen register (chipset config register s:offset 31ffh: bit 1). if ferr# is asserted, the chipset 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 processo r unless ferr# is acti ve. ferr# requires an external weak pull -up to ensure a high level when the coprocessor error function is disabled. note: ferr# can be used in some st ates for notification by the processor of pending interrupt events. this functionality is independent of the oic register bit setting. ignne# o ignore numeric error: this signal is connected to the ignore error pin on the processor. ignne# is only us ed if the chipset co-processor error reporting function is enabled in the oic.cen register (chipset config registers:offset 31ffh: bit 1). if ferr# is active, indicating a coprocessor error, a write to the copr ocessor error register (i/o register f0h) causes the ignne# to be asserted. ignne# remains asserted until ferr# is negated. if ferr# is not asserted when the coprocessor error register is written, the ignn e# signal is not asserted. init# o initialization: init# is asserted by the ch ipset for 16 pci clocks to reset the processor. the chipset can be configured to support processor built in self test (bist). init3_3v# o initialization 3.3 v: this is the identical 3.3 v copy of init# intended for firmware hub. table 2-13.power management in terface signals (sheet 3 of 3) name type description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 55 signal description 2.13 smbus interface intr o cpu interrupt: intr is asserted by the ch ipset to signal 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 chipset 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 nm i source enable/disable bit in the nmi status and control register (i/o register 61h). smi# o system management interrupt: smi# is an active low output synchronous to pciclk. it is asserted by the chipset 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 chip set in response to one of many hardware or software events. wh en the processor samples stpclk# asserted, it responds by st opping its internal clock. rcin# i keyboard controller reset cpu: the keyboard controller can generate init# to the processor. this saves the external or gate with the chipset?s other sources of init#. when the chipset detects the assertion of this signal, init# is generated for 16 pci clocks. note: the chipset will ignore rcin# asse rtion during transitions to the s1, s3, s4, and s5 states. a20gate i a20 gate: a20gate is from the keyboard controller. the signal acts as an alternative method to force the a20m# signal acti ve. it saves the external or gate needed wi th various other chipsets. cpupwrgd / gpio49 o cpu power good: this signal should be connected to the processor?s pwrgood input to indicate when the cpu power is valid. this is an output signal that represents a lo gical and of the chipset?s pwrok and vrmpwrgd signals. this signal may op tionally be configured as a gpio. dpslp# o deeper sleep: dpslp# is asserted by th e chipset to the processor. when the signal is low, the processor enters the deep sleep state by gating off the processor core clock in side the processor. when the signal is high (default), the processor is not in the deep sleep state. table 2-15.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 re sistor is required. smbalert# / gpio11 i smbus alert: this signal is used to wa ke the system or generate smi#. if not used for smbalert#, it can be used as a gpio. table 2-14.processor interf ace signals (sheet 2 of 2) name type description www.datasheet.co.kr datasheet pdf - http://www..net/
signal description 56 datasheet 2.14 system management interface 2.15 real time clock interface 2.16 other clocks table 2-16.system management interface signals name type description intruder# i intruder detect: this signal can be set to disable the system if the chasis is detected open. this signal?s status is readab le, so it can be used like a gpio if the intruder detection is not needed. smlink[1:0] i/od system management link: these signals provide a smbus link to optional external system mana gement 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# i/od smlink alert: this signal is an output of the integrated lan and input to either the integrated asf or an external management controller in order for the lan?s smlink slave to be serviced. table 2-17.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, rt cx1 can be driven with the desired clock rate. rtcx2 special crystal input 2: this signal is connected to the 32.768 khz crystal. if no external crystal is used, rtcx2 should be left floating. table 2-18.other clocks name type description clk14 i oscillator clock: this clock signal is used for the 8254 timers. it runs at 14.31818 mhz. this clock is permitted to stop during s3 (or lower) states. clk48 i 48 mhz clock: this clock signal is used to run the usb controller. it runs at 48.000 mhz. this clock is perm itted to stop duri ng s3 (or lower) states. sata_clkp sata_clkn i 100 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 i 100 mhz differential clock: these signals are used to run the direct media interface. they run at 100 mhz. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 57 signal description 2.17 miscellaneous signals 2.18 intel hd audio link table 2-19.miscellaneous signals name type description intvrmen i internal voltage regulator enable: this signal must always connected to vccrtc to make su re the internal 1.05 v suspend regulator is been enabled. spkr o speaker: the spkr signal is the output of counter 2 and is internally ?anded? with port 61h bit 1 to pr ovide speaker data enable. this signal drives an external speaker driv er device, which in turn drives the system speaker. upon pltrst#, its output state is 0. note: spkr is sampled at the rising edge of pwrok as a functional strap. see section 2.22.1 for more details. there is a weak integrated pull-down resistor on spkr pin. rtcrst# i rtc reset: when asserted, this signal resets register bits in the rtc well. notes: 1. unless cmos is bein g cleared (only to be done in the g3 power state), the rtcrst# input must be high when all other rtc power planes are on. 2. in the case where the rtc batt ery is dead or missing on the platform, the rtcrst# pin must rise before the rsmrst# pin. strap0 o strapping 0: this pin have strapping function use as ?top-block swap override?. strap[1]#/ gpio48 o strapping 1: this pin have strapping function use as ?boot bios destination selection?. the strap[1]# pin can instead be used as a gpio. strap[2]#/ gpio17 o strapping 2: this pin have strapping function use as ?boot bios destination selection?. the strap[2]# pin can instead be used as a gpio. table 2-20.intel hd audio link signals (sheet 1 of 2) name 1,2 type description hda_rst# o intel hd audio reset: this signal is the ma ster hardware reset to external codec(s). hda_sync o intel high definition audio sync: this signal is a 48 khz fixed rate sample sync to the codec(s). it is also used to encode the stream number. hda_bit_clk o intel high definition audio bit clock output: this signal is a 24.000 mhz serial data clock generated by the intel high definition audio controller. this signal has an integrated pull-d own resistor so that hda_bit_clk doesn?t float when an intel high definition audio codec (or no codec) is connected. www.datasheet.co.kr datasheet pdf - http://www..net/
signal description 58 datasheet 2.19 serial peripheral interface (spi) 2.20 general purpose i/o signals hda_sdout o intel high definition audio serial data out: this signal is the serial tdm data output to the codec( s). this serial ou tput is double- pumped for a bit rate of 48 mb/s for intel high definition audio. note: hda_sdout is sampled at the rising edge of pwrok as a functional strap. see section 2.22.1 for more details. there is a weak integrated pull-down re sistor on the hda_sdout pin. hda_sdin[2:0] i intel high definition audio serial data in [2:0]: these signals are serial tdm data inputs from the three codecs. the serial input is single-pumped for a bit rate of 24 mb/s for intel hd audio. these signals have integrated pull-down resistors that ar e always enabled. 1. some signals have integrated pull-u ps or pull-downs. consult table in section 3.1 for details. 2. intel high definition audio have to configure th rough d30:f1:40h, bit 0: az#. this bit configure the intel high definition audio signals and bios need to set it to 1. table 2-21.serial peripheral interface (spi) signals name type description spi_cs# i/o spi chip select: this chip select signal is also used as the spi bus request signal. spi_miso i spi master in slave out : this signal is the data input pin for the chipset. spi_mosi o spi master out slave in : this signal is the data output pin for the chipset. spi_arb i spi arbitration : spi_arb is the spi arbi tration signal used to arbitrate the spi bus when sh ared flash is implemented. spi_clk o spi clock : this signal is the spi cloc k signal. during idle, the bus owner will drive the clock signal low. 17.86 mhz. table 2-22.general purpose i/o signals (sheet 1 of 2) name 1,2 type tolerance power well default description gpio49 i/o v_cpu_io v_cpu_io native multiplexed with cpupwrgd gpio48 i/o 3.3 v core native m ultiplexed with strap1# gpio[47:40] n/a n/a n/a n/a not implemented. gpio[39:38] i/o 3.3 v core gpi unmultiplexed. gpio37 n/a n/a n/a n/a not implemented. gpio36 i/o 3.3 v core gpi unmultiplexed. table 2-20.intel hd audio li nk signals (sheet 2 of 2) name 1,2 type description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 59 signal description gpio35 n/a n/a n/a n/a not implemented. gpio34 i/o 3.3 v core gpo unmultiplexed. gpio33 i/o 3.3 v core gpo unmultiplexed. gpio32 n/a n/a n/a n/a not implemented. gpio31 i/o 3.3 v resume native multiplexed with oc7# gpio30 i/o 3.3 v resume native multiplexed with oc6# gpio29 i/o 3.3 v resume native multiplexed with oc5# gpio28 i/o 3.3 v resume gpo unmultiplexed. gpio27 i/o 3.3 v resume gpo unmultiplexed. gpio26 i/o 3.3 v resume gpo unmultiplexed. gpio25 i/o 3.3 v resume gpo unmultiplexed. gpio24 i/o 3.3 v resume gpo unmultiplexed. not cleared by cf9h reset event. gpio23 i/o 3.3 v core native m ultiplexed with ldrq1# gpio22 i/o 3.3 v core gpi unmultiplexed. gpio[21:18] n/a n/a n/a n/a not implemented gpio17 i/o 3.3 v core gpo multiplexed with strap2#. gpio16 n/a n/a n/a n/a not implemented gpio[15:12] i/o 3.3 v resume gpi unmultiplexed. gpio11 i/o 3.3 v resume native multiplexed with smbalert# gpio[10:8] i/o 3.3 v resume gpi unmultiplexed. gpio[7:6] i/o 3.3 v core gpi unmultiplexed. gpio[5:2] i/od 5 v core gpi multiplexed with pirq[h:e]#. gpio1 i/o 5 v core gpi unmultiplexed. gpio0 i/o 3.3 v core gpi multiplexed with bm_busy#. 1. 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. 2. 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. some chipset 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 will result in the intel chipset driving a pin to a logic 1 to another devi ce that is powered down. table 2-22.general purpose i/o signals (sheet 2 of 2) name 1,2 type tolerance power well default description www.datasheet.co.kr datasheet pdf - http://www..net/
signal description 60 datasheet 2.21 power and ground table 2-23.power and ground signals name description vcc3_3 these pins provide the 3.3 v supply fo r core well i/o buffe rs (6pins). this power may be shut off in s3, s4, s5 or g3 states. vcc1_05 these pins provide the 1.05 v supply for core well logic (4 pins). this power may be shut off in s3, s4, s5 or g3 states. vcc1_5 these pins provide the 1.5 v supply fo r logic and i/o (4 pins). this power may be shut off in s3, s4, s5 or g3 states. v5ref these pins provide the re ference for 5 v tolerance on co re well inputs (1 pins). this power may be shut off in s3, s4, s5 or g3 states. vccsus3_3 these pins provide the 3.3 v supply fo r resume well i/o buffe rs (4 pins). this power is not expected to be shut off unless the system is unplugged in nettop configurations or the main battery is removed or completely drained and ac power is not available in netbook configurations. v5ref_sus this pin provides the reference for 5 v tole rance on resume well inputs (1 pin). this power is not expected to be shut off unless th e system is unplugged in nettop configurations or the main battery is removed or completely drained and ac power is not available in netbook configurations. vccrtc this pin provides the 3.3 v (can drop to 2.0 v min. in g3 state) supply for the rtc well (1 pin). this power is not ex pected to be shut off unless the rtc 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 a chipset-based platform can be done by using a jumper on rtcrst# or gpi. vccusbpll this pin provides the 1.5 v supply for co re well logic (1 pin). 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. vccdmipll this pin provides the 1.5 v supply for co re well logic (1 pin). this signal is used for the dmi pll. this powe r may be shut off in s3, s4, s5 or g3 states. vccsatapll this pin provides the 1.5 v supply for co re well logic (1 pin). 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 not used. v_cpu_io these pins are powered by the same supply as the processor i/o voltage (1 pins). this supply is used to drive the processor interface signals listed in ta b l e 2 - 1 4 . vss grounds (59 pins). www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 61 signal description 2.22 pin straps 2.22.1 functional straps the following signals are used for static configuration. they are sampled at the rising edge of pwrok to select configurations (excep t as noted), and then revert later to their normal usage. to invoke the associated mode, the signal should be driven at least four pci clocks prior to the time it is sampled. table 2-24.functional strap definitions (sheet 1 of 2) signal usage when sampled comment hda_sdout pci express* port config bit 1 rising edge of pwrok when tp3 not pulled low at rising edge of pwrok, sets bit 1 of rpc.pc (chipset configuration registers:offset 224h). see section 10.1.30 for details. this signal has a weak internal pull-down. hda_sync pci express port config bit 0 rising edge of pwrok this signal has a weak internal pull-down. sets bit 0 of rpc.pc (chipset configuration registers:offset 224h). see section 10.1.30 for details. ee_cs reserved this signal has a weak internal pull-down. note: this signal should not be pulled high. ee_dout reserved this signal has a we ak internal pull-up. note: this signal should not be pulled low. gnt2# reserved this signal has a we ak internal pull-up. note: this signal should not be pulled low. strap0# to p - b l o c k swap override rising edge of pwrok the signal has a weak in ternal pull-up. if the signal is sampled low, this indicates that the system is strapped to the ?top-block swap? mode (the chipset inverts a16 fo r all cycles targeting fwh bios space). the status of this strap is readable via the top swap bit (chipset configuration registers:offset 3414h:bit 0). note that software will not be able to clear the top-swap bit until the system is rebooted without strap0# being pulled down. strap2# / gpio17, strap1# / gpio48 boot bios destination selection rising edge of pwrok this field determines the destination of accesses to the bios memory range. signals have weak internal pull-ups. also co ntrollable via boot bios destination bit (chipset configuration registers:offset 3410h:bit 11:10) (strap2# is msb) 01 = spi 10 = pci 11 = lpc dprslpvr reserved this signal has a weak internal pull-down. note: this signal should not be pulled high. www.datasheet.co.kr datasheet pdf - http://www..net/
signal description 62 datasheet note: see section 3.1 for full details on pull-up/pull-down resistors. 2.22.2 external rtc circuitry to reduce rtc well power consumption, the chipset implements an internal oscillator circuit that is sensitive to step voltage changes in vccrtc. following figure shows an example schematic recommended to ensure correct operation of chipset rtc. gpio25 dmi ac/dc coupling selection rising edge of rsmrst# this signal has a weak internal pull-up. the internal pull-up is disabled within 100 ms after rsmrst# deasserts. if the signal is sampled high, the dmi interface is strapped to operate in dc coupled mode (no coupling capacitors are required on dmi differential pairs). if the signal is sampled low, the dmi interface is strapped to operate in ac coupled mode (coupling capacitors are required on dmi differential pairs). notes: 1. board designer must ensure that dmi implementation matches the strap selection. 2. the signal must be held low at least 2 us after rsmrst# deassertion to enable ac coupled mode. 3. when the chipset pairs with intel? atom? processor d400, d500 and n400 series, should enable ac couple mode for receive signal and dc couple mode for transmit signal. intvrmen enable integrated vccsus1_05 vrm always enables integrated vccsus1_05 vrm when sampled high. linkalert# reserved this signal requir es an external pull-up resistor. sataled# reserved this signal has a weak internal pull-up enabled only when pltrst# is asserted. note: this signal should not be pulled low. spkr no reboot rising edge of pwrok the signal has a weak inte rnal pull-down. if the signal is sampled high, this indicates that the system is strapped to the ?no reboot? mode (the chipset will disable the tco timer system reboot feature). the status of th is strap is readable via the no reboot bit (chipset config registers:offset 3410h:bit 5). table 2-24.functional strap definitions (sheet 2 of 2) signal usage when sampled comment www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 63 signal description note: c1 and c2 depend on crystal load. 2.23 device and revision id table notes: 1. intel NM10 contains a single sata device. th e sata device id is dependant upon which sata mode is selected by bios and capabilities exist in the sku. 2. loaded from eeprom. if eeprom contains eith er 0000h or ffffh in the device id location, then 27dch is used. refer to the ich7 eeprom map and programming guide for lan device ids. figure 2-3. example external rtc circuit 32.768 khz xtal 1 f (20% tolerance) c2 15 pf (5% tolerance) vccrtc rtcx2 rtcx1 vbatt 1 f (20% tolerance) 1 k vccsus3_3 c1 15 pf (5% tolerance) + r1 10 m ? rtcrst# 20 k schottky diodes device function description chipset dev id 1 chipset rev id comments d31, f0 lpc 27bch 00h d31, f2 sata 27c0h 00h non-ahci mode 1 27c1h 00h ahci mode 1 d31, f3 smbus 27dah 00h d30, f0 dmi to pci bridge 2448h e0h d29, f0 usb uhc #1 27c8h 00h d29, f1 usb uhc #2 27c9h 00h d29, f2 usb uhc #3 27cah 00h d29, f3 usb uhc #4 27cbh 00h d29, f7 usb ehci 27cch 00h d28:f0 pci express* port 1 27d0 00h d28:f1 pci express port 2 27d2 00h d28:f2 pci express port 3 27d4 00h d28:f3 pci express port 4 27d6 00h d27:f0 intel hd audio 27d8 00h d8: f0 lan see note 2 00h www.datasheet.co.kr datasheet pdf - http://www..net/
pin states 64 datasheet 3 pin states 3.1 integrated pull-ups and pull-downs notes: see next page table 3-25.integrated pull-u p and pull-down resistors signal resistor nominal notes hda_bit_clk, intel high definition audio pull-down 20 k 2, 6, 7 hda_rst#, intel high definition audio none n/a 2 hda_sdin[2:0], inte l high definition audio pull-down 20 k 2, 4 hda_sdout, intel high defi nition audio pull-down 20 k 1, 2 hda_sync, intel high defi nition audio pull-down 20 k 2, 4 dprslpvr pull-down 20 k 4, 9 ee_cs pull-down 20 k 10, 11 ee_din pull-up 20 k 10 ee_dout pull-up 20 k 10 gnt1# pull-up 20 k 10, 12 gnt2# pull-up 20 k 10, 19 strap0# strap1#/ gpio48 strap2#/ gpio17 pull-up 20 k 10, 19 gpio25 pull-up 20 k 10, 13 lad[3:0] / fhw[3:0]# pull-up 20 k 10 lan_clk pull-down 100 k 14 lan_rxd[2:0] ( pull-up 20 k 15 ldrq0# pull-up 20 k 10 ldrq1# / gpio23 pull-up 20 k 10 pme# pull-up 20 k 10 pwrbtn# pull-up 20 k 10 sataled# pull-up 15 k 16 spi_arb pull-down 20 k 10 spi_clk pull-down 20 k 10 spkr pull-down 20 k 4 usbp[7:0] [p,n] pull-down 15 k 18 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 65 pin states 1. the pull-down resistors on hda_bit_clk (ac ?97) and hda_rst# are enabled when either: - the lso bit (bit 3) in the ac?97 global co ntrol register (d30:f2:2c) is set to 1, or - both function 2 and function 3 of device 30 are disabled. - otherwise, the integrated pu ll-down resistor is disabled. 2. the intel high definition au dio link signals must be conf igured to be an intel high definition audio link. 3. simulation data shows that these resistor values can range from 10 k to 20 k . 4. simulation data shows that these resistor values can range from 9 k to 50 k . 5. simulation data shows that these resistor values can range from 10 k to 40 k . 6. the pull-down on this signal (in intel high definition audio mode) is only enabled when in s3 cold . 7. simulation data shows that these resistor values can range from 5.7 k to 28.3 k . 8. the pull-up or pull-down on this signal is only enabled at b oot/reset for strapping function. 9. simulation data shows that these resistor values can range from 15 k to 35 k . 10. the pull-down on this signal is on ly enabled when lan_rst# is asserted. 11. the internal pull-up is enabled only when the pcirst# pin is driven low and the pwrok indication is high. 12. internal pull-up is enabled during rsmrst# and is disabled within 100 ms after rsmrst# de-asserts. 13. simulation data shows that these resistor values can range from 45 k to 170 k . 14. simulation data shows that these resistor values can range from 15 k to 30 k . 15. simulation data shows that these resistor values can range from 10 k to 20 k . the internal pull-up is only enable d only during pltrst# assertion. 16. simulation data shows that these resistor values can range from 10 k to 30 k . 17. simulation data shows that these resistor values can range from 14.25 k to 24.8 k . 18. the internal pull-up is enabled only when pcirst# is low. 3.2 output and i/o signals planes and states ta b l e 3 - 2 6 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. the chipset not driving the signal high or low. ?high? the chipset is driving the signal to a logic 1 ?low? the chipset is driving the signal to a logic 0 ?defined? driven to a level that is defined by the function (will be high or low) ?undefined? the chipset 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, so the chipset is not driving note that the signal levels are the same in s4 and s5, except as noted. the chipset suspend well signal states are indeterminate and undefined and may glitch, including input signals acting as outputs, pr ior to rsmrstb deassertion. this does not apply to lan_rst#, slp_s3#, slp_s4#, an d slp_s5#. these signals are determinate and defined prior to rsmrst# deassertion. www.datasheet.co.kr datasheet pdf - http://www..net/
pin states 66 datasheet the chipset core well signal states are indeterminate and undefined and may glitch, including input signals acting as outputs, pr ior to pwrok assertion. this does not apply to ferr# and thrmtrip#. these signals ar e determinate and defined prior to pwrok assertion. table 3-26.power plane and states for ou tput and i/o signal s (sheet 1 of 4) signal name power plane during pltrst# 6 / rsmrst# 7 immediately after pltrst# 6 / rsmrst# 7 c3/c4 s1 s3 cold 13 s4/ s5 pci express* petp[4:1], petn[4:1] core high high 12 defined defined off off dmi dmi[3:0]txp, dmi[3:0]txn core high high 12 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 devsel# core high-z high-z high-z high-z off off frame# core high-z high-z high-z high-z off off gnt[2:1]# strap1#/gpio48 strap2#/gpio17 core high with internal pull- ups high high high off off irdy#, trdy# core high-z high-z high-z high-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# core high high high high off off lan connect and eeprom interface ee_cs lan low running defined defined note 4 note 4 ee_dout lan high high defined defined note 4 note 4 ee_shclk lan high-z running defined defined note 4 note 4 lan_rstsync lan high low defined defined note 4 note 4 lan_txd[2:0] lan low low defined defined note 4 note 4 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 67 pin states sata interface sata[0]txp, sata[0]txn sata[1]txp, sata[1]txn core high-z high-z defined defined off off sataled# core high-z high-z defined defined off off satarbias core high-z high-z defined defined off off interrupts pirq[a:d]#, pirq[h:e]# / gpio[5:2] core high-z high-z defined high-z off off serirq core high-z high-z running high-z off off usb interface usbp[7:0][p,n] suspend low low low low low low usbrbias suspend high-z high-z defined defined defined define d oc[7:5]#/ gp[31:29] suspend input input driven driven driven driven power management pltrst# suspend low high high high low low slp_s3# suspend low high high high low low slp_s4# suspend low high high high high low slp_s5# suspend low high high high high low 10 stp_pci# core high high defined high low low stp_cpu# core high high low high low low sus_stat# / lpcpd# suspend low high high high low low dprslpvr core low low low/ high 5 high off off dprstp# core high high low/ high 5 high off off susclk suspend low running table 3-26.power plane and states for output and i/o signals (sheet 2 of 4) signal name power plane during pltrst# 6 / rsmrst# 7 immediately after pltrst# 6 / rsmrst# 7 c3/c4 s1 s3 cold 13 s4/ s5 www.datasheet.co.kr datasheet pdf - http://www..net/
pin states 68 datasheet processor interface a20m# core dependant on a20gate signal see note 8 defined high off off cpupwrgd / gpio49 core see note 3 high high high off off ignne# core high see note 8 high high off off init# core high high high high off off init3_3v# core high high high high off off intr core see note 8 see note 8 defined low off off nmi core see note 8 see note 8 defined low off off smi# core high high defined high off off stpclk# core high high low low off off dpslp# core high high high/ low high off off smbus interface smbclk, smbdata suspend high-z high-z defined defined defined define d system management interface smlink[1:0] suspend high-z high-z defined defined defined define d linkalert# suspend high-z high-z defined defined defined define d miscellaneous signals spkr core high-z with internal pull- down low defined defined off off intel hd audio interface hda_rst# suspend low low 11 high tbd low low hda_sdout core high-z with internal pull- down running running low off off hda_sync core high-z with internal pull- down running running low off off hda_bit_clk core high-z with internal pull- down low 11 running low off off table 3-26.power plane and states for ou tput and i/o signal s (sheet 3 of 4) signal name power plane during pltrst# 6 / rsmrst# 7 immediately after pltrst# 6 / rsmrst# 7 c3/c4 s1 s3 cold 13 s4/ s5 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 69 pin states notes: 1. NM10 drives these signals high after the cpu reset. 2. gpio[18] will toggle at a frequ ency of approximately 1 hz when the NM10 comes out of reset 3. cpupwrgd is an output that represents a logica l and of the NM10?s vrmpwrgd and pwrok signals, and thus will be driven low by NM10 when either vrmpwr gd or pwrok are inactive. during boot, or during a hard reset with power cy cling, cpupwrgd will be expected to transi tion from low to high. 4. lan connect and eeprom sign als will either be ?defin ed? or ?off? in s3-s5 states depending upon whether or not the lan power planes are active. 5. the state of the dprslpvr and dprstp # signals in c4 are high if deeper sleep is enabled or low if it is disabled. 6. the states of vcc3_3 signals are taken at the times during pltrst# and immediately after pltrst#. 7. the states of vccsus3_3 signals are taken at the times during rsmrst# and immediately after rsmrst#. 8. NM10 drives these signals low before pw rok rising and low after the cpu reset. 9. gpio[25] transitions from pulled high internally to actively driven with in 100 ms of the deassertion of the rsmrst# pin. 10. 10.slp_s5# signals will be high in the s4 state. 11. low until intel high definition audio controller reset bi t set (d27:f0:offset hdbar+08h:bit 0), at which time acz_rst# will be high and acz_bit_clk will be running. 12. petp/n[6:1] high until port is enabled by software. 13. in s3hot, signal states are platform implementation specific, as some external components and interfaces may be powered when the nm 10 is in the s3hot state. un-multiplexed gpio signals gpio[7:6] core input input driven driven off off gpio[15:12,10:8] suspend input input driven driven driven driven gpio24 suspend no change no chan ge defined defined defined define d gpio25 suspend high high 7 defined defined defined define d gpio[28:26] suspend low low defined defined defined define d gpio33 suspend high high defined defined off off gpio34 core low low 11 defined defined off off gpio[39:38] core input input driven driven off off spi interface spi_cs# suspend high high high high high high spi_mosi suspend high high high high high high spi_arb suspend low low low low low low spi_clk suspend low low low low low low table 3-26.power plane and states for output and i/o signals (sheet 4 of 4) signal name power plane during pltrst# 6 / rsmrst# 7 immediately after pltrst# 6 / rsmrst# 7 c3/c4 s1 s3 cold 13 s4/ s5 www.datasheet.co.kr datasheet pdf - http://www..net/
pin states 70 datasheet 3.3 power planes for input signals ta b l e 3 - 2 7 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 the chipset 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# and slp_s5#. these signals are determinate and defined prior to rsmrst# deassertion. the chipset 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. table 3-27.power plane for input signals (sheet 1 of 2) signal name power well driver during reset c3/c4 s1 s3 cold 2 s4/s5 a20gate core external microcontroller static static low low hda_sdin[2:0 ] (intel hd audio mode) suspend intel hd audio codec driven low low low bm_busy# / gpio0 2 core graphics component [(g)mch] driven high low low batlow# suspend power supply high high high high clk14 core clock generator running running low low clk48 core clock generator running running low low dmi_clkp dmi_clkn core clock generator running running low low ee_din lan eeprom component driven driven note 1 note 1 ferr# core processor static static low low perp[4:1], pern[4:1] core pci express* device driven driven driven driven dmi[3:0]rxp, dmi[3:0]rxn core (g)mch driven driven low low intruder# rtc external switch driven driven driven driven intvrmen rtc external pull-up or pull-down driven driven driven driven www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 71 pin states notes: see next page lan_clk lan lan connect component driven driven note 1 note 1 lan_rst# suspend power supply high high static static lanrxd[2:0] lan lan connect component driven driven note 1 note 1 ldrq0# core lpc devices driven high low low ldrq1# / gpio23 3 core lpc devices driven high low low mch_sync# core (g)mch driven driven low low oc[7:0]# suspend external pull-ups driven driven driven driven pciclk core clock generator running running low low pme# suspend internal pull-up driven driven driven driven pwrbtn# suspend internal pull-up driven driven driven driven pwrok rtc system power supply driven driven low low rcin# core external microcontroller high high low low req[2:1]#, core pci master driven driven low low ri# suspend serial port buffer driven driven driven driven rsmrst# rtc external rc circuit high high high high rtcrst# rtc external rc circuit high high high high sata_clkp, sata_clkn core clock generator running running low low sata[1:0]rxp, sata[1:0]rxn core sata drive driven driven driven driven satarbias# core external pull-down driven driven driven driven serr# core pci bus peripherals driven high low low smbalert# / gpio11 3 suspend external pull-up driven driven driven driven sys_reset# suspend external circuit driven driven driven driven thrm# core thermal sensor driven driven low low thrmtrip# core thermal sensor driven driven low low usbrbias# suspend external pull-down driven driven driven driven vrmpwrgd core processor voltage regulator driven driven low low wake# suspend external pull-up driven driven driven driven spi_miso suspend external pull-up driven driven driven driven spi_arb suspend internal pull-down low low low low table 3-27.power plane for input signals (sheet 2 of 2) signal name power well driver during reset c3/c4 s1 s3 cold 2 s4/s5 www.datasheet.co.kr datasheet pdf - http://www..net/
pin states 72 datasheet 1. lan connect and eeprom sign als will either be ?driven? or ?low? in s3?s5 states depending upon whether or not th e lan power planes are active. 2. in s3hot, signal states are platform implementation specific , as some extern al components and interfaces may be po wered when the NM10 is in the s3hot state. 3. these signals can be configured as outputs in gpio mode. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 73 chipset and system clock domains 4 chipset and system clock domains ta b l e 4 - 2 8 shows the system clock domains. figure 4-4 and figure 4-5 show the assumed connection of the various system components, including the clock generator in nettop and netbook systems. for complete details of the system clocking solution, refer to the system?s clock generator component specification. table 4-28.chipset and system clock domains clock domain frequency source usage chipset sata_clkp, sata_clkn 100 mhz main clock generator differential clock pair used for sata. chipset dmi_clkp, dmi_clkn 100 mhz main clock generator differential clock pair used for dmi. chipset pciclk 33 mhz main clock generator free-running pci clock to chipset. this clock remains on during s0 and s1 (in nettop) state, and is expected to be shut off during s3 or below in nettop configurations or s1 or below in netbook configurations. system pci 33 mhz main clock generator pci bus, lpc i/f. these on ly go to external pci and lpc devices. will stop ba sed on clkrun# (and stp_pci#) in netbook configurations. chipset clk48 48.000 mhz main clock generator super i/o, usb controllers. expected to be shut off during s3 or below in nettop configurations or s1 or below in netbook configurations. chipset clk14 14.31818 mhz main clock generator used for acpi timer an d multimedia timers. expected to be shut off during s3 or below in nettop configurations or s1 or below in netbook configurations. lan_clk 5 to 50 mhz lan connect component generated by the lan connect component. expected to be shut off during s3 or below in nettop configurations or s1 or below in netbook configurations. spi_clk 17.86 mhz ich generated by the lan connect component. expected to be shut off during s3 or below in nettop configurations or s1 or below in netbook configurations. www.datasheet.co.kr datasheet pdf - http://www..net/
chipset and system clock domains 74 datasheet figure 4-4. nettop only conceptual system clock diagram figure 4-5. netbook only conceptual clock diagram intel NM10 express chipset 32 khz xtal susclk# (32 khz) 14.31818 mhz pci clocks (33 mhz) clock gen. 14.31818 mhz 48 mhz lan connect 100 mhz diff. pair 1 to 6 differential clock fan out device sata 100 mhz diff. pair dmi 100 mhz diff. pair pci express 100 mhz diff. pairs high definition audio codec(s) 24 mhz 50 mhz 48.000 mhz 33 mhz intel NM10 express chipset 32 khz xtal susclk# (32 khz) 14.31818 mhz stp_cpu# stp_pci# pci clocks (33 mhz) clock gen. 14.31818 mhz 48 mhz lan connect 100 mhz diff. pair 1 to 6 differential clock fan out device sata 100 mhz diff. pair dmi 100 mhz diff. pair pci express 100 mhz diff. pairs high definition audio codec(s) 24 mhz 50 mhz 48.000 mhz 33 mhz www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 75 functional description 5 functional description this chapter describes the functi ons and interfaces of chipset. 5.1 pci-to-pci bridge (d30:f0) the pci-to-pci bridge resides in pci device 30, function 0 on bus #0. this portion of chipset implements the buffering and cont rol 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 rang es for the dmi. all register contents are lost when core well power is removed. direct media interface (dmi) is the chip-t o-chip connection between the cpu and i/o controller hub. this high-speed interface integrates advanced priority-based servicing allowing for concurrent traffic and true isochronous transfer capabilities. base functionality is completely software i/o controller hub transparent permitting current and legacy software to operate normally. to provide for true isochronous transfers and configurable quality of service (qos) transactions, chipset supports two virtual ch annels on dmi: vc0 and vc1. these two channels provide a fixed arbitration scheme where vc1 is 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., chipset and cpu). configuration registers for dmi, virtual ch annel support, and dmi active state power management (aspm) are in the rcrb sp ace in the chipset config registers ( section 10 ). 5.1.1 pci bus interface chipset pci interface supports pci local bus specification, revision 2.3, at 33 mhz. chipset integrates a pci arbiter that suppor ts up to two external pci bus masters in addition to the internal chipset requests. 5.1.2 pci bridge as an initiator the bridge initiates cycles on the pci bus wh en granted by the pci arbiter. the bridge generates the following cycle types: table 5-29.pci bridge initiator cycle types command c/be# notes i/o read/write 2h/3h non-posted www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 76 datasheet 5.1.2.1 memory reads and writes the bridge bursts memory writes on pci that are received as a single packet from dmi. 5.1.2.2 i/o reads 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 corresp onding 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 configuration reads and writes the bridge generates single dw configuration read and write cycles. when the cycle completes on the pci bus, the bridge gene rates a corresponding completion. if the cycle is retried, the cycle is kept in th e 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 any agent except dmi while locked. if a locked read results in a target or mast er abort, the lock is not established (as per the pci local bus specification ). agents north of chipset must not forward a subsequent locked read to the bridge if th ey see the first one finish with a failed completion. 5.1.2.5 target / master aborts when a cycle initiated by the bridge is ma ster/target aborted, the bridge will not re- attempt the same cycle. for 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 was master or target aborted on pci. the bridge drops posted writes that abort. 5.1.2.6 secondary master latency timer the bridge implements a master latency timer via the slt register which, upon expiration, causes the de-assertion of frame# at the next legal clock edge when there is another active request to use the pci bus. memory read/write 6h /7h writes are posted configuration read/write ah/bh non-posted special cycles 1h posted table 5-29.pci bridge initiator cycle types command c/be# notes www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 77 functional description 5.1.2.7 dual address cycle (dac) the bridge will issue full 64-bit dual ad dress cycles for device memory-mapped registers above 4 gb. 5.1.2.8 memory and i/o decode to pci the pci bridge in chipset 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 memo ry 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) set ? if bctrl.ie (d30: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.vgae (d30:f0:offset 3eh:bi t 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 specificatio n, assuming the above rules are met. 5.1.3 parity error detection and generation pci parity errors can be detected and repo rted. the following behavioral rules apply: ? when a parity error is detected on pci, the bridge sets the secsts.dpe (d30:f0:offset 1eh:bit 15). ? if the bridge is a master and bctrl.pere (d30:f0:offset 3eh:bit 0) 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 the psts.sse (d30:f0:offset 06h:bit 14) and generate an internal serr#. ? if the psts.sse is set because of an ad dress parity error and the pcicmd.see is set, the bridge will generate an internal serr# ? when bad parity is detected from dmi, ba d parity will be driven on all data the bridge. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 78 datasheet ? when an address parity error is detected on pci, the pci bridge will not 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 se t. 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. 5.1.4 pcirst# the pcirst# pin is genera ted under two conditions: ? pltrst# active ? bctrl.sbr (d30:f0:offset 3eh:bit 6) set to 1 the pcirst# pin is in the resu me well. pcirst# should 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 cycles 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:offset 4ch:bit 2) ? memory 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 have 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 manage ability, bpc.cde can be set. wh en 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 cycle to allow addr essing of extended pci space. the format is as follows: table 5-30.type 1 address format bits definition 31:27 reserved (same as the pci local bus specification ) 26:24 extended configuration address ? al lows addressing of up to 4k. these bits are combined with bits 7:2 to get the full register. 23:16 bus number (same as the pci local bus specification ) 15:11 device number (same as the pci local bus specification ) 10:8 function number (same as the pci local bus specification ) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 79 functional description note: chipset usb controllers cannot perform peer-to-peer traffic. 5.1.6 pci-to-pci bridge model from a software perspective, chipset contains a pci-to-pci bridge. this bridge connects dmi to the pci bus. by using the pci-to-pci bridge software model, chipset can have its decode ranges programmed by existing pl ug-and-play software such that pci ranges do not conflict with graphics aperture ranges in the host controller. note: all downstream devices should be disabled before reconfiguring the pci bridge. failure to do so may cause undefined results. 5.1.7 idsel to device number mapping when addressing devices on the external pci bus (with the pci slots), chipset asserts one address signal as an idsel. when acce ssing device 0, chipset asserts ad16. when accessing device 1, chipset asserts ad17. this mapping continues all the way up to device 15 where chipset asserts ad31. note th at chipset internal functions (intel hd audio, usb, sata and pci bridge) are enumer ated like they are off of a separate pci bus (dmi) from the external pci bus. the integrated lan controller is device 8 on chipset?s pci bus, and hence it uses ad24 for idsel. 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 mechan ism implemented within chipset. the pci local bus specification, revision 2.3 defines two mechanisms to access configuration space, mechanism 1 and mechanism 2. chipset only supports mechanism 1. warning: configuration writes to internal devices, wh en the devices are disabled, are invalid and may cause undefined results. 7:2 register (same as the pci local bus specification ) 10 0 must be 1 to indicate a type 1 cy cle. type 0 cycles are not decoded. table 5-30.type 1 address format bits definition www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 80 datasheet 5.2 pci express* root ports (d28:f0,f1,f2,f3) there are four root ports available in chipset. these all reside in device 28, and take function 0 ? 3. port 1 is function 0, port 2 is function 1, port 3 is function 2, port 4 is function 3. optionally, pci express ports 1-4 can be configured as a single one x4 port identified as port 1. this is accomplished by placing ex ternal pull-up resistors on hda_sdout and hda_sync. when these signals are sampled high on pwrok assertion, this will be registered in the port configuration field of the root port configuration register and the corresponding ports will be configured as one x4 port. 5.2.1 interrupt generation the root port generates interrupts on behalf of hot-plug and power management events, when enabled. these interrupts can ei ther be pin based, or can be msis, when enabled. when an interrupt is generated via the lega cy pin, the pin is internally routed to chipset 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) registers. ta b l e 5 - 3 1 summarizes interrupt behavior for msi and wire-modes. in the table ?bits? refers to the hot-plug and pme interrupt bits. table 5-31.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 bi ts, and one or more bits are set on the same clock wire active send message www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 81 functional description 5.2.2 power management 5.2.2.1 s3/s4/s5 support software initiates the transition to s3/s4/s5 by performing an io write to the power management control register in chipset. 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 it's 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 chipset root ports links are in the l2/l3 ready state, chipset power management control logic will proceed with the entry into s3/s4/s5. prior to entering s3, software is re quired to put each device into d3 hot . when a device is put into d3 hot , 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 st ate 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 chipset can make no assumptions about the state of the link prior to receivin g a pme_turn_off message. 5.2.2.2 resuming from suspended state the root port contains enough circuitry in the resume well to detect a wake event thru the wake# signal and to wake the system. when wake# is detected asserted, an internal signal is sent to the power mana gement controller of chipset 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_p me 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:offset 60h:bit 16 is cleared), the root port will set rsts.ps, an d log the pme requester id into rsts.rid (d28:f0/f1/f2/f3:offset 60h:bits 15:0). if an interrupt is enabled via rctl.pie (d28:f0/f1/f2/f3:offset 5ch:bit 3), an interru pt will be generated. this interrupt can be either a pin or a msi if msi is enabled via mc.msie (d28:f0/f1/f2/f3:offset 82h:bit 0). see section 5.2.2.4 for smi/sci generation. if this is a subsequent message received (rst s.ps is already set), the root port will set rsts.pp (d28:f0/f1/f2/f3:offset 60h:bit 17) and log the pme requester id from the message in a hidden register. no other action will be taken. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 82 datasheet when the first pme event is cleared by softwa re clearing rsts.ps, the root port will set rsts.ps, clear rsts.pp, and move the requ ester id from the hidden register into rsts.rid. if rctl.pie is set, generate an interrupt. if rctl.pie is not set, send over 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 must be generated. this last condition handles the case where the message was received prior to the operating system re-enabling interru pts 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 operating systems, pm events can be routed to generate sci. to generate sci, mpc.pmce must be set. when set, a power management event will cause smscs.pmcs (d28:f0/f1/f2/ f3: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:offset d8h:bit 0). when this bit is set, power management events will set smscs.pmms (d28:f0/f1/f2/f3: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 concu rrently with an interrupt or sci. 5.2.3 serr# generation serr# may be generated via two paths ? thro ugh pci mechanisms involving bits in the pci header, or through pci express mechan isms involving bits in the pci express capability structure. figure 5-6. 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 83 functional description 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 mo dules (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:offset 5ah:bit 6) and slsts.pdc (d28:f0/f1/f2/f3:offset 6h:bit 3). if slctl.pde (d28:f0/ f1/f2/f3:offset 58h:bit 3) and slctl.hpe (d28:f0/f1/f2/f3: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/f3:offset 58h:bits 7:6) or slctl.pic (d28:f0/f1/f2/f3: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/f3:offset 58h:bit 4) to indicate the command has completed. if slctl.cce and slctl.hpe (d28:f0/f1/f2/f3: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 register would invariably end up writing to the indicators, power controller fields; hence, any write to the slot control register is considered a command and if enabled, www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 84 datasheet will result in a command complete interrupt. the only exception to this rule is a write to disable the command complete interrupt whic h 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. 5.2.4.3 attention button detection when an attached device is ejected, an a ttention button could be pressed by the user. this attention button press will result in a 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/f3:offset 5ah:bit 0). if slctl.abe (d28:f0/f1/f2/f3:offset 58h:bit 0) and slctl.hpe (d28:f0/f1/f2/ f3:offset 58h:bit 5) are set, the hot-plug controller will also generate an interrupt. the interrupt is generated on an edge-event. fo r 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 supp orted on legacy operating systems. to support hot-plug on non-pci express aware op erating systems, hot-plug events can be routed to generate sci. to generate sci, mpc.hpce (d28:f0/f1/f2/f3:offset d8h:bit 30) must be set. when set, enabled hot- plug events will cause smscs.hpcs (d28:f0/ f1/f2/f3:offset dch:bit 30) to be set. additionally, bios workarounds for hot-plug can be supported by setting mpc.hpme (d28:f0/f1/f2/f3:offset d8h:bit 1). when this bit is set, hot-plug events can cause smi status bits in smscs to be set. suppor ted hot-plug events and their corresponding smscs bit are: ? command completed - scscs.hpccm (d28:f0/f1/f2/f3:offset dch:bit 3) ? presence detect changed - smscs.hppdm (d28:f0/f1/f2/f3:offset dch:bit 1) ? attention button pressed - smscs.hpabm (d28:f0/f1/f2/f3:offset dch:bit 2) ? link active state changed - smscs.hplas (d28:f0/f1/f2/f3:offset dch:bit 4) 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 85 functional description 5.3 lan controller (b1:d8:f0) chipset?s integrated lan controller includ es a 32-bit pci controller that provides enhanced scatter-gather bus mastering capabilities and enables the lan controller to perform high-speed data transf ers over the pci bus. its bu s 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 transmit and receive fifos of 3 kb each, help prevent data underruns and overruns while waiting for bus accesses. this enables the integrated lan controller to transmit data with minimum interframe spacing (ifs). chipset integrated lan controller can operate 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. the integrated lan controller also includes an interface to a serial (4-pin) eeprom. the eeprom provides power-on initialization for hardware and software configuration parameters. from a software perspective, the integrated lan controller appears to reside on the secondary side of chipset?s virtual pci-to-pci bridge (see section 5.1.6 ). this is typically bus 1, but may be assigned a different number, depending upon system configuration. the following summarizes chipset lan controller features: ? compliance with advanced configuration and power interface and pci power management standards ? support for wake-up on interesting packets and link status change ? support for remote power-up using wake on lan* (wol) technology ? deep power-down mode support ? backward compatible software with 82550, 82557, 82558 and 82559 ? tcp/udp checksum off load capabilities ? support for intel?s adaptive technology 5.3.1 lan controller pci bus interface as a fast ethernet controller, the role of chipset integrated lan controller is to access transmitted data or deposit received data. the lan controller, as a bus master device, initiates memory cycles via the pci bus to fetch or deposit the required data. to perform these actions, the lan contro ller is controlled and examined by the processor via its control and status structures and registers. some of these control and status structures reside in the lan controll er and some reside in system memory. for access to the lan controller?s control/status registers (csr), the lan controller acts as a slave (in other words, a target device). the lan controller serves as a slave also while the processor accesses the eeprom. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 86 datasheet 5.3.1.1 bus slave operation chipset integrated lan controller serves as a target device in one of the following cases: ? processor accesses to the lan controller system control block (scb) control/ status registers (csr) ? processor accesses to the eeprom through its csr ? processor accesses to the lan controller port address via the csr ? processor accesses to the mdi control register in the csr the size of the csr memory space is 4 kbyt e in the memory space and 64 bytes in the i/o space. the lan controller treats accesses to these memory spaces differently. control/status regi ster (csr) accesses the integrated lan controller supports zero wait-state single cycle memory or i/o mapped accesses to its csr space. separate bars request 4 kb of memory space and 64 bytes of i/o space to accomplish this. base d on its needs, the software driver uses either memory or i/o mapping to access these registers. the lan controller provides four valid kb of csr space that include the following elements: ? system control block (scb) registers ? port register ? eeprom control register ? mdi control register ? flow control registers in the case of accessing the control/status registers, the processor is the initiator and the lan controller is the target. retry premature accesses the lan controller responds with a retry to any configuration cycle accessing the lan controller before the completion of the automatic read of the eeprom. the lan controller may continue to retry any configuration accesses until the eeprom read is complete. the lan controller does not enforce the rule that the retried master must attempt to access the same address again in order to complete any delayed transaction. any master access to the lan controller after the completion of the eeprom read is honored. error handling data parity errors: the lan controller checks for data parity errors while it is the target of the transaction. if an error was detected, the lan controller sets the detected parity error bit in the pci configuration status register, bit 15. the lan controller also www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 87 functional description asserts perr#, if the parity error response bit is set (pci configuration command register, bit 6). the lan controller does not attempt to terminate a cycle in which a parity error was detected. this gives the initiator the option of recovery. target-disconnect: the lan controller prematurely terminate a cycle in the following cases: ? after accesses to its csr ? after accesses to the configuration space system error: the lan controller reports parity error during the address phase using the serr# pin. if the serr# enable bit in the pci configuration command register or the parity error response bit are not set, the lan controller only sets the detected parity error bit (pci configuration status re gister, bit 15). if serr# enable and parity error response bits are both set, the lan co ntroller sets the signaled system error bit (pci configuration status register, bit 14) as well as the detected parity error bit and asserts serr# for one clock. the lan controller, when detecting system error, claims the cycle if it was the target of the transaction and continues the transaction as if the address was correct. note: the lan controller reports a system error for any error during an address phase, whether or not it is involved in the current transaction. 5.3.1.2 clkrun# signal (netbook only) chipset receives a free-running 33 mhz clock. it does not stop based on the clkrun# signal and protocol. when the lan controller runs cycles on the pci bus, chipset makes sure that the stp_pci# signal is high indica ting that the pci clock will be running. this is to make sure that any pci tracker does not get confused by transactions on the pci bus with its pci clock stopped. 5.3.1.3 pci power management enhanced support for the power management standard, pci local bus specification, revision 2.3, is provided in chipset in tegrated lan controller. the lan controller supports a large set of wake-up packets and the capability to wake the system from a low power state on a link status change. the lan controller enables the host system to be in a sleep state and remain virtually connected to the network. after a power management event or link stat us change is detected, the lan controller wakes the host system. the following sections describe these events, the lan controller power states, and estimated power consumption at each power state. the lan controller contains power management registers for pci, and implements four power states, d0 through d3, which vary from maximum power consumption at d0 to the minimum power consumption at d3. pci tr ansactions are only allowed in the d0 state, except for host accesses to the lan controller?s pci configuration registers. the d1 and d2 power management states enable intermediate power savings while www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 88 datasheet providing the system wake-up capabilities. in the d3 cold state, the lan controller can provide wake-up capabilities. wake-up indica tions from the lan controller are provided by the power management event (pme#) signal. 5.3.1.4 pci reset signal the pcirst# signal may be activate d in one of the following cases: ? during s3?s5 states ? due to a cf9h reset if pme is enabled (in the pci power management registers), pcirst# assertion does not affect any pme related circuits (in other words, pci power management registers and the wake-up packet would not be affected). while pcirst# is active, the lan controller ignores other pci signals. the co nfiguration of the lan controller registers associated with acpi wake events is not affected by pcirst#. the integrated lan controller uses the pcirst# or the pwrok signal as an indication to ignore the pci interface. following the deassertion of pcirst#, the lan controller pci configuration space, mac configuration, and memory structure are initialized while preserving the pme# signal and its context. 5.3.1.5 wake-up events there are two types of wake-up events: ?int eresting? packets and link status change. these two events are detailed below. note: if the wake on lan bit in th e eeprom is not set, wake-up events are supported only if the pme enable bit in the power management control/status register (pmcsr) is set. however, if the wake on lan bit in the eeprom is set, and wake on magic packet* or wake on link status change are enabled, the power management enable bit is ignored with respect to these events. in the latte r case, pme# would be asserted by these events. ?interesting? packet event in the power-down state, the lan controlle r is capable of recognizing ?interesting? packets. the lan controller supports predef ined and programmable packets that can be defined as any of the following: ? arp packets (with multiple ip addresses) ? direct packets (with or without type qualification) ? magic packet ? neighbor discovery multicast address packet (?arp? in ipv6 environment) ? netbios over tcp/ip (nbt) query packet (under ipv4) ? internetwork package exchange* (ipx) diagnostic packet this allows the lan controller to handle various packet types. in general, the lan controller supports programmable filterin g of any packet in the first 128 bytes. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 89 functional description when the lan controller is in one of the low power states, it searches for a predefined pattern in the first 128 bytes of the incoming packets. the only exception is the magic packet, which is scanned for the entire frame. the lan controller classifies the incoming packets as one of the following categories: ? no match: the lan controller discards the packet and continues to process the incoming packets. ? tco packet: the lan controller implements perfec t filtering of tco packets. after a tco packet is processed, the lan controller is ready for the next incoming packet. tco packets are treated as any other wake-up packet and may assert the pme# signal if configured to do so. ? wake-up packet: the lan controller is capable of recognizing and storing the first 128 bytes of a wake-up packet. if a wake-up packet is larger than 128 bytes, its tail is discarded by the lan controller. after the system is fully powered-up, software has the ability to determine the cause of the wake-up event via the pmdr and dump the stored data to the host memory. magic packets are an exception. the magic packets may cause a power management event and set an indication bit in the pmdr; however, it is not stored by the lan controller for use by the system when it is woken up. link status change event the lan controller link status indication circuit is capable of issuing a pme on a link status change from a valid link to an invalid link condition or vice versa. the lan controller reports a pme link status event in all power states. if the wake on lan bit in the eeprom is not set, the pme# signal is gated by the pme enable bit in the pmcsr and the csma configure command. 5.3.1.6 wake on lan* (preboot wake-up) the lan controller enters wake on lan mode after reset if the wake on lan bit in the eeprom is set. at this point, the lan co ntroller is in the d0u state. when the lan controller is in wake on lan mode: ? the lan controller scans incoming packets for a magic packet and asserts the pme# signal for 52 ms when a 1 is detected in wake on lan mode. ? the activity led changes its functionality to indicates that the received frame passed individual address (ia) filtering or broadcast filtering. ? the pci configuration registers are accessible to the host. the lan controller switches from wake on lan mode to the d0a power state following a setup of the memory or i/o base address registers in the pci configuration space. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 90 datasheet 5.3.2 serial eeprom interface the serial eeprom stores configuration data for chipset integrated lan controller and is a serial in/serial out device. the lan controller supports a 64-register or 256-register size eeprom and automatically detects the eeprom?s size. the eeprom should operate at a frequency of at least 1 mhz. all accesses, either read or write, are preceded by a command instruction to the device. the address field is six bits for a 64-register eeprom or eight bits for a 256- register eeprom. the end of the address fiel d is indicated by a dummy 0 bit from the eeprom that indicates the entire address fiel d has been transferred to the device. an eeprom read instruction waveform is shown in figure 5-7 . the lan controller performs an automatic read of seven words (0h, 1h, 2h, ah, bh, ch, and dh) of the eeprom after the deassertion of reset. 5.3.3 csma/cd unit chipset integrated lan controller csma/c d unit implements both the ieee 802.3 ethernet 10 mbps and ieee 802.3u fast ethernet 100 mbps standards. it performs all the csma/cd protocol functions (e.g., transm ission, reception, collision handling, etc.). the lan controller csma/cd unit interfaces to the 82562et/em/ez/ex 10/100 mbps ethernet through chipset?s lan connect interface signals. 5.3.3.1 full duplex when operating in full-duplex mode, the lan controller can transmit and receive frames simultaneously. transmission starts regardless of the state of the internal receive path. reception starts when the platform lan connect component detects a valid frame on its receive differential pair. chipset integrated lan controller also supports the ieee 802.3x flow contro l standard, when in full-duplex mode. figure 5-7. 64-word eeprom read instruction waveform a 1 a 0 ee_cs ee_shclkk ee_din ee_dout a 5 a 4 a 2 d 15 d 0 read op code a 3 a 1 a 0 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 91 functional description the lan controller operates in either half-duplex mode or full-duplex mode. for proper operation, both the lan controller csma /cd module and the discrete platform lan connect component must be set to the same duplex mode. the csma duplex mode is set by the lan controller configure command or forced by automatically tracking the mode in the platform lan connect component. following reset, the csma defaults to automatically track the platform lan connect component duplex mode. the selection of duplex operation (full or ha lf) and flow control is done in two levels: mac and lan connect. 5.3.3.2 flow control the lan controller supports ieee 802.3x fram e-based flow control frames only in both full duplex and half duplex switched envi ronments. the lan controller flow control feature is not intended to be used in shared media environments. flow control is optional in full-duplex mode and is selected through software configuration. there are three modes of flow control that can be selected: frame-based transmit flow control, frame-base d receive flow control, and none. 5.3.3.3 vlan support the lan controller supports the ieee 802.1 standard vlan. all vlan flows will be implemented by software. the lan controller supports the reception of long frames, specifically frames longer than 1518 bytes, including the crc, if software sets the long receive ok bit in the configuration command . otherwise, ?long? frames are discarded. 5.3.4 media manage ment interface the management interface allows the processor to control the platform lan connect component via a control register in chipset integrated lan controller. this allows the software driver to place the platform lan connect in specific modes (e.g., full duplex, loopback, power down, etc.) without the need for specific hardware pins to select the desired mode. this structure allows the lan controller to query the platform lan connect component for status of the link. this register is the mdi control register and resides at offset 10h in the lan controller csr. the mdi registers reside within the platform lan connect component, and are described in detail in the platform lan connect component?s datasheet. the processor writes commands to this register and the lan controller reads or writes the control/status parameters to the platform lan connect component through the mdi register. 5.3.5 tco functionality chipset integrated lan controller supports management communication to reduce total cost of ownership (tco). the smbus is used as an interface between the asf controller and the integrated tco host controller. there are two different types of tco operation that are supported (only one supported at a time), they are 1) integrated asf control or 2) external tco controller support. the smlink is a dedicated bus www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 92 datasheet between the lan controller and the integrated asf controller (if enabled) or an external management controller. an eeprom of 256 wo rds is required to support the heartbeat command. 5.3.5.1 advanced tco mode the advanced tco functionalities through the smlink are listed in ta b l e 5 - 3 2 . note: for a complete description on various commands, see the total cost of ownership (tco) system management bus interface application note (ap-430) . transmit command duri ng normal operation to serve a transmit request from the tco controller, chipset lan controller first completes the current transmit dma, sets th e tco request bit in the pmdr register (see section 11.2 ), and then responds to the tco controller?s transmit request. following the completion of the tco transmit dma, the lan controller increments the transmit tco statistic counter (described in section 11.2.14 ). following the completion of the transmit operation, chipset increments the nominal transmit statistic counters, clears the tco request bit in the pmdr register, and resumes its normal transmit flow. the receive flow is not affected duri ng this entire period of time. receive tco chipset lan controller supports receive flow towards the tco controller. chipset can transfer only tco packets, or all packets that passed mac address filtering according to its configuration and mode of operation as de tailed below. while configured to transfer only tco packets, it supports ethernet type ii packets with optional vlan tagging. force tco mode: while chipset is in the force tco mode, it may receive packets (tco or all) directly from the tco controller. receiving tco packets and filtering level is controlled by the set receive enable comm and from the tco controller. following a reception of a tco packet, chipset increments its nominal receive statistic counters as well as the receive tco counter. table 5-32.advanced tco functionality power state tco controller functionality d0 nominal transmit set receive tco packets receive tco packets read chipset status (pm & link state) force tco mode dx (x>0) d0 functionality plus: read phy registers force tco mode dx functionality plus: configuration commands read/write phy registers www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 93 functional description dx>0 power state: while chipset is in a powerdown state, it may receive tco packets or all directly to the tco controller. receiving tco packets is enabled by the set receive enable command from the tco controller. although tco packet might match one of the other wake up filters, once it is transferred to the tco controller, no further matching is searched for and pme is not issu ed. while receive to tco is not enabled, a tco packet may cause a pme if configured to do so (setting tco to 1 in the filter type). d0 power state: at d0 power state, chipset may transfer tco packets to the tco controller. at this state, tco packets are posted first to the host memory, then read by chipset, and then posted back to the tco cont roller. after the packet is posted to tco, the receive memory structure (that is occupied by the tco packet) is reclaimed. other than providing the necessary receive resource s, there is no required device driver intervention with this process. eventually, chipset increments the receive tco static counter, clears the tco request bit, and resumes normal control. read chipset status (pm and link state) the tco controller is capable of reading chipset power state and link status. following a status change, chipset asserts linkalert# and then the tco can read its new power state. set force tco mode the tco controller put chipset into the force tco mode. chipset is set back to the nominal operation following a pcirst#. following the transition from nominal mode to a tco mode, chipset aborts transmission and reception and loses its memory structures. the tco may configure chipset before it starts transmission and reception if required. warning: the force tco is a destructive command. it causes chipset to lose its memory structures, and during the force tco mode chipset ignores any pci accesses. therefore, it is highly recommended to use this command by the tco controller at system emergency only. 5.4 alert standard format (asf) the asf controller collects information fr om various components in the system (including the processor, chipset, bios, and sensors on the motherboard) and sends this information via the lan controller to a remote server running a management console. the controller also accepts commands back from the management console and drives the execution of those commands on the local system. the asf controller is responsible for monitoring sensor devices and sending packets through the lan controller smbus (system management bus) interface. these asf controller alerting capabilities include sy stem health information such as bios messages, post alerts, operating system failure notifications, and heartbeat signals to indicate the system is accessible to the server. also included are environmental notification (e.g., thermal, voltage and fan alerts) that send proactive warnings that something is wrong with the hardware. the pa ckets are used as alert (s.o.s.) packets www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 94 datasheet or as ?heartbeat? status packets. in addition, asset security is provided by messages (e.g., ?cover tamper? and ?cpu missing?) that notify of potential system break-ins and processor or memory theft. the asf controller is also responsible for receiving and responding to rmcp (remote management and control protocol) packets. rmcp packets are used to perform various system apm commands (e.g., reset, power-up, power-cycle, and power-down). rmcp can also be used to ping the system to ensure that it is on the network and running correctly and for capability reporting. a majo r advantage of asf is that it provides these services during the time that software is unable to do so (e.g., during a low- power state, during boot-up, or during an operating system hang) but are not precluded from running in the working state. the asf controller communicates to the system and the lan controller logic through the smbus connections. the first smbus connect s to the host smbus controller (within chipset) and any smbus platform sensors. the smbus host is accessible by the system software, including software running on the operating system and the bios. note that the host side bus may require isolation if there are non-auxiliary devices that can pull down the bus when un-powered. the second smbus connects to the lan controller. this second smbus is used to provid e a transmit/receive network interface. the stimulus for causing the asf controller to send packets can be either internal or external to the asf controller. external stimuli are link status changes or polling data from smbus sensor devices; internal events come from, among others, a set of timers or an event caused by software. the asf controller provides three local configuration protocols via the host smbus. the first one is the smbus arp interface that is used to identify the smbus device and allow dynamic smbus address assignment. the second protocol is the asf controller command set that allows software to manage an asf controller compliant interface for retrieving info, sending alerts, and controlling timers. chipset provides an input and an output ee prom interface. the eeprom contains the lan controller configuration and the asf cont roller configuration/packet information. 5.4.1 asf management solution features/capabilities ? alerting ? transmit sos packets from s0?s5 states ? system health heartbeats ? sos hardware events - system boot failure (watchdog expires on boot) - lan link loss - entity presence (on asf power-up) - smbus hung - maximum of eight legacy sensors - maximum of 128 asf sensor events ? watchdog timer for operating system lockup/system hang/failure to boot www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 95 functional description ? general push support for bios (post messages) ? remote control ? presence ping response ? configurable boot options ? capabilities reporting ? auto-arp support ? system remote control - power-down - power-up - power cycle - system reset ? state-based security ? conditio nal action on watchdog expire ? asf compliance ? compliant with the alert standard format (asf) specification, version 1.03 - pet compliant packets - rmcp - legacy sensor polling - asf sensor polling - remote control sensor support ? advanced features / miscellaneous ? smbus 2.0 compliant ? optional reset extension logic (for use with a power-on reset) 5.4.2 asf hardware support asf requires additional hardware to make a complete solution. note: if an asf compatible device is external ly connected and properly configured, the internal chipset asf controller will be di sabled. the external asf device will have access to the smbus controller. 5.4.2.1 intel ? 82562em/ex the 82562em/ex ethernet lan controller is necessary. this lan controller provides the means of transmitting and receiving data on the network, as well as adding the ethernet crc to the data from the asf. 5.4.2.2 eeprom (256x16, 1 mhz) to support chipset asf solution, a larger, 256x16 1 mhz, eeprom is necessary to configure defaults on reset and on hard power losses (software un-initiated). the asf controller shares this eeprom with the lan controller and provides a pass through interface to achieve this. the asf controller expects to have exclusive access to words www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 96 datasheet 40h through f7h. the lan controller can use the other eeprom words. the asf controller will default to safe defaults if th e eeprom is not present or not configured properly (both cause an invalid crc). 5.4.2.3 legacy sensor smbus devices the asf controller is capable of monitoring up to eight sensor devices on the main smbus. these sensors are expected to be compliant with the legacy sensor characteristics defined in the alert standard format (asf) specification, version 1.03 . 5.4.2.4 remote control smbus devices the asf controller is capable of causing remote control actions to remote control devices via smbus. these remote control actions include power-up, power-down, power-cycle, and reset. the asf controller supports devices that conform to the alert standard format (asf) specification, version 1.03, remote control devices. 5.4.2.5 asf sensor smbus devices the asf controller is capable of monitoring up to 128 asf sensor devices on the main smbus. however, asf is restricted by the number of total events which may reduce the number of smbus devices supported. the ma ximum number of events supported by asf is 128. the asf sensors are expected to operate as defined in the alert standard format (asf) specification, version 1.03. 5.4.3 asf software support asf requires software support to make a complete solution. the following software is used as part of the complete solution. ? asf configuration driver / application ? network driver ? bios support for smbios, smbus arp, acpi ? sensor configuration driver / application note: contact your intel field representative fo r the client asf software development kit (sdk) that includes additional documentatio n and a copy of the client asf software drivers. intel also provides an asf console sdk to add asf support to a management console. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 97 functional description 5.5 lpc bridge (w/ system and management functions) (d31:f0) the lpc bridge function of chipset 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 mana gement, system management, gpio, and rtc. in this chapter, registers and functions associated with other functional units (power management, gpio, usb, ide, etc.) ar e described in their respective sections. 5.5.1 lpc interface chipset implements an lpc in terface as described in the low pin count interface specification, revision 1.1. the lpc interface to chipset is shown in figure 5-8 . note that chipset implements all of the signals that are shown as optional, but peripherals are not required to do so. 5.5.1.1 lpc cycle types chipset implements the following cycle types as described in ta b l e 5 - 3 3 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 tr ansfer must be word-ali gned (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) figure 5-8. lpc interface diagram table 5-33.lpc cycle types supported cycle type comment i/o read 1 byte only. chipset breaks up 16- and 32-bit processor cycles into multiple 8-bit transfers. i/o write 1 byte only. chipset 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) www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 98 datasheet 5.5.1.2 start field definition note: all other encodings are reserved. 5.5.1.3 cycle type / di rection (cyctype + dir) chipset drives bit 0 of this field to 0. peripherals running bus master cycles must also drive bit 0 to 0. ta b l e 5 - 3 5 shows the valid bit encodings. note: all other encodings are reserved. 5.5.1.4 size bits[3:2] are reserved. chipset drives them to 00. peripherals running bus master cycles are also supposed to drive 00 for bits 3:2; however, chipset ignores those bits. bits[1:0] are encoded as listed in ta b l e 5 - 3 6 . table 5-34.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. table 5-35.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 bu s master cycle generates this value, chipset aborts the cycle. table 5-36.transfer size bit definition bits[1:0] size 00 8-bit transfer (1 byte) 01 16-bit transfer (2 bytes) 10 reserved . chipset does not drive this combination. if a peripheral running a bus master cycle drives this combination, chipset may abort the transfer. 11 32-bit transfer (4 bytes) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 99 functional description 5.5.1.5 sync valid values for the sync field are shown in ta b l e 5 - 3 7 . notes: 1. all other combinations are reserved. 2. if the lpc controller receives any sync retu rned 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 allo wed to assert an error sync. 5.5.1.6 sync time-out there are several error cases that can occur on the lpc interface. chipset 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 chipset. 5.5.1.7 sync error indication chipset 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, chipset treats this as an serr by reporting this into the device 31 error reporting logic. 5.5.1.8 lframe# usage chipset follows the usage of lframe# as defined in the low pin count interface specification, revision 1.1. chipset performs an abort for the following cases (possible failure cases): table 5-37.sync bit definition bits[3:0] 1,2 indication 0000 ready: sync achieved with no error. for dma transfers, this also indicates dma request deassertion and no more tr ansfers desired for that channel. 0101 short wait: part indicating wait-states. for bus master cycles, chipset does not use this encoding. instead, chipset uses the long wait encoding (see next encoding below). 0110 long wait: part indicating wait-states, and ma ny wait-states will be added. this encoding driven by chipset 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 allowed for any other type of cycle. 1010 error: sync achieved with error. this is ge nerally used to re place the serr# or iochk# signal on the pci/isa bus. it indica tes that the data is to be transferred, but there is a serious error in this tran sfer. for dma transfers, this not only indicates an error, but also indicate s dma request deasse rtion and no more transfers desired for that channel. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 100 datasheet ? chipset starts a memory, i/o, or dma cycle, but no device drives a valid sync after four consecutive clocks. ? chipset starts a memory, i/o, or dma cycle, and the peripheral drives an invalid sync pattern. ? a peripheral drives an invalid address when performing bus master cycles. ? a peripheral drives an invalid value. 5.5.1.9 i/o cycles for i/o cycles targeting registers specified in chipset?s decode ranges, chipset 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, chipset 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), chipset 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.5.1.10 bus master cycles chipset supports bus master cycles and requ ests (using ldrq#) as defined in the low pin count interface specification, revision 1.1. chipset has two ldrq# inputs, and thus supports two separate bus master devices. it uses the associated start fields for bus master 0 (0010b) or bus master 1 (0011b). note: chipset does not support lpc bus masters performing i/o cycles. lpc bus masters should only perform memory read or memory write cycles. 5.5.1.11 lpc power management clkrun# protocol (netbook) the clkrun# protocol is same as in 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. chipset shuts of f the ldrq# input buff ers. after driving sus_stat# active, chipset 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 asynchrono us reset events. chipset asserts both sus_stat# (connects to lpcpd#) and pltrst# (connects to lrst#) at the same time www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 101 functional description when the core logic is reset (via cf9h, pw rok, or sys_reset#, etc.). this is not inconsistent with the lpc lpcpd# protocol. 5.5.1.12 configuration and chipset implications lpc interface decoders to allow the i/o cycles and memory mapped cycles to go to the lpc interface, chipset includes several decoders. during configurat ion, chipset must be programmed with the same decode ranges as the peripheral. th e decoders are programmed via the device 31:function 0 configuration space. note: chipset 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 chipset 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.2 serr# generation several internal and external sources of th e lpc bridge can cause serr#, as described below. the first class of errors is parity errors related to the backbone. the lpc bridge captures generic data parity errors (errors it finds on the backbone) as well as errors returned on the backbone cycles where th e bridge was the master and parity error response is enabled. if either of these tw o conditions is met, and with serr# enable (pcicmd.serr_en) set, serr# will be captured. additionally, if the lpc bridge receives an error sync on lpc bus, an serr# will also be generated. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 102 datasheet 5.6 dma operation (d31:f0) chipset supports lpc dma using chipset?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 co nfiguration space. these 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-10 ). dma controller 1 (dma-1) corresponds to dma channels 0?3 and dm a 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 acce pting 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 co mpatible 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. chipset 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. the dma controller also features refresh address generation, and autoinitialization following a dma termination. figure 5-9. lpc bridge serr# generation serr# pcicmd.serr_en (d31:f0:04h, bit 8) pcists.dpe (d31:f0:06h, bit15) pcists.dped (d31:f0:06h, bit 8) pcists.sse (d31:f0:06h, bit 14) lpc error sync received figure 5-10. chipset dma controller channel 0 channel 1 channel 2 channel 3 channel 4 channel 5 channel 6 channel 7 dma-1 dma-2 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 103 functional description 5.6.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.6.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 over channels 5, 6, and 7. 5.6.1.2 rotating priority rotation 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 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.6.2 address compatibility mode when the dma is operating, the addresses do not increment or decrement through the high and low page 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 www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 104 datasheet 5.6.3 summary of dma transfer sizes ta b l e 5 - 3 8 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/decrem ent? 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 cu rrent address register will be incremented or decremented. 5.6.3.1 address shifting when programmed for 16-b it i/o count by words chipset maintains compatibility with the implem entation of the dma in the pc at that used the 82c37. the dma shifts the addre sses for transfers to/from a 16-bit device count-by-words. note: the least significant bit of the low page re gister is dropped in 16-bit shifted mode. when programming the current address regi ster (when the dma channel is in this mode), the current address must be progra mmed to an even address with the address value shifted right by one bit. the address shifting is shown in ta b l e 5 - 3 9 . note: the least significant bit of the page regi ster is dropped in 16-bit shifted mode. 5.6.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 ba se page, address, and byte/word count registers of that channel following tc. the base registers are loaded simultaneously with the current registers by the mi croprocessor when the dma channel is table 5-38.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-39.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) a0 a[16:1] a[23:17] a0 a[16:1] a[23:17] 0 a[15:0] a[23:17] www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 105 functional description programmed and remain unchanged throughout the dma service. the mask bit is not set when the channel is in autoinitialize. follo wing autoinitialize, the channel is ready to perform another dma service, without processo r intervention, as soon as a valid dreq is detected. 5.6.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.7 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 ho st. 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.7.1 asserting dma requests 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). chipset 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-11 , 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 enco ded 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 ld rq# signal must go high for at least 1 clock. after that one clock, ldrq# signal can be brought low to the next encoding sequence. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 106 datasheet if another dma channel also needs to reques t 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 channe l 2 is run on the interface, the peripheral can send the encoded request for channel 3. th is 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. 5.7.2 abandoning dma requests dma requests can be deasserted in two fash ions: 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 so ftware 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 chipset, there is no assurance th at 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 comple te the cycle normally with any random data. this method of dma deassertion should be prevented whenever possible, to limit boundary conditions both on chipset and the peripheral. 5.7.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 lpc i/f and begins the dma transfer. the general flow for a basic dma transfer is as follows: 1. chipset starts transfer by asserting 0000b on lad[3:0] with lframe# asserted. 2. chipset asserts ?cycle type? of dma, di rection based on dma transfer direction. 3. chipset asserts channel number an d, if applicable, terminal count. 4. chipset indicates the size of the transfer: 8 or 16 bits. 5. if a dma read - figure 5-11. dma request assertion through ldrq# start msb lsb act start lclk ldrq# www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 107 functional description ? chipset drives the first 8 bits of data and turns the bus around. ? the peripheral 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 write - ? chipset turns the bus around and waits for data. ? the peripheral indicates data ready th rough sync and transfers the first byte. ? if a 16-bit transfer, the peripheral indi cates data ready and transfers the next byte. 7. the peripheral turns around the bus. 5.7.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 th e channel field. terminal count indicates the last byte of transfer, based upon the size of the transfer. for example, on an 8-bit transfer size (size fiel d is 00b), if the tc bit is set, then this is the last byte. on a 16-bit transfer (size fiel d is 01b), if the tc bit is set, then the second byte is the last byte. the peripheral, therefore, must internalize the tc bit when the channel field is communicated, and only signal tc when the last byte of that transfer size has been transferred. 5.7.5 verify mode verify mode is supported on the lpc interfac e. 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 ho st will not transfer this data into main memory. 5.7.6 dma request deassertion an end of transfer is communicated to chipset through a special sync field transmitted by the peripheral. an lpc device must not a ttempt to signal the end of a transfer by deasserting ldreq#. if a dma transfer is seve ral bytes (e.g., a transfer from a demand mode device) chipset 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 chipset whether this is the last byte of transfer or if more bytes are requested. to indicate the last byte of tr ansfer, the peripheral uses a sync value of 0000b (ready with no error), or 1010b (ready with error). these encodings tell chipset that this is the last piece of data transferred on a dma read (chips et to peripheral), or the byte that follows is the last piece of data transferred on a dma write (peripheral to chipset). www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 108 datasheet when chipset sees one of these two encodings, it ends the dma transfer after this byte and deasserts the dma request to the 8237. therefore, if chipset indicated a 16-bit transfer, the peripheral can end the transfer after one byte by indicating a sync value of 0000b or 1010b. chipset does not attempt to transfer the second byte, and deasserts the dma request internally. if the peripheral indicates a 0000b or 1010 b sync pattern on the last byte of the indicated size, then chipset 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 chipset keep s the dma request active to the 8237. therefore, on an 8-bit transfer si ze, if the peripheral indicates a sync value of 1001b to chipset, the data will be transf erred and the dma request will remain active to the 8237. at a later time, chipset will then come back with another start ? cyctype ? channel ? size etc. combination to initiate another transfer to the peripheral. the peripheral must not assume that the next start indication from chipset 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 afte r every transfer. only demand mode dma devices can be ensured that they will receiv e the next start indication from chipset. note: indicating a 0000b or 1010b encoding on th e 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 (peripheral to memory), and indicates to the 8237 that the dma transfer occurred, incrementing the 8 237?s address and decrementing its byte count. 5.7.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 dm a 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 host and peripheral through system bios is performed is beyond the scope of th is specification. since the lpc host and lpc peripheral are motherboard devices, no ?plug-n-play? registry is required. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 109 functional description the peripheral must not assume that the host is able to perform transfer sizes that are larger than the size allowed for the dma cha nnel, 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. 5.8 8254 timers (d31:f0) chipset 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 tw o 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 request signal this counter provides the refresh request si gnal 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 afte r being written to the counter i/o address. the ref_toggle bit will have a square wave 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 initia l count value. the speaker must be enabled by a write to port 061h (see nmi status and control ports). www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 110 datasheet 5.8.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 byte s (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 mode. counting is affect ed as described in the mode definitions. the new count must follow the programmed count format. if a counter is programmed to read/write two-byte counts, the following precaution applies: a program must not transfer contro l 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. ta b l e 5 - 4 0 lists the six operating modes for the interval counters. table 5-40.counter operating modes mode function description 0 out 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. 2 rate generator (divide by n counter) output is 1. output goes to 0 for one clock time, then back to 1 and counter is reloaded. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 111 functional description 5.8.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 co mmand methods, the count must be read according to the programmed format; specifica lly, if the counter is programmed for two byte counts, two bytes must be read. the tw o bytes do not have to be read one right after the other. read, write, or programmi ng operations for other counters may be inserted between them. 5.8.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. however, in the case of counter 2, the count can be stopped by writing to the gate bit in port 61h. 5.8.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 re ad 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 co unter latch commands may be used to latch more than one counter. counter latch comma nds 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. 3 square wave output output is 1. ou tput 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. table 5-40.counter operating modes www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 112 datasheet 5.8.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 equiva lent to several counter latch commands, one for each counter latched. each counter's la tched count is held until it is read or reprogrammed. once read, a counter is unlat ched. 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 stat us latch operations are performed 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 whether the co unter is programmed for one or two type counts, returns the latched count. subsequent reads return unlatched count. 5.9 8259 interrupt controllers (pic) (d31:f0) chipset 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, pa rallel ports, floppy disk, ide, 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. ta b l e 5 - 4 1 shows how the cores are connected. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 113 functional description . chipset cascades the slave controller onto the master controller through master controller interrupt input 2. this means ther e are only 15 possible interrupts for chipset 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 chipset. in the following descriptions of the 8259s, the interru pt levels are in reference to the signals at the internal interface of the 8259s, afte r the required inversions have occurred. therefore, the term ?high? indicates ?act ive,? which means ?low? on an originating pirq#. table 5-41.interrupt controller core connections 8259 8259 input typical interrupt source connected pin / function master 0 internal internal timer / counter 0 output / 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 serirq, 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 0 internal 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# 3 generic irq11 via serirq, sci, tco, or pirq# 4 ps/2 mouse irq12 via serirq, sci, tco, or pirq# 5 internal state machine output based on processor ferr# assertion. may optionally be used for sci or tco interrupt if ferr# not needed. 6 sata sata primary (legacy mode), or via serirq or pirq# 7 sata sata secondary (legacy mode) or via serirq or pirq# www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 114 datasheet 5.9.1 interrupt handling 5.9.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 de termine the interrupt vector returned, and status of any other pending interrupts. ta b l e 5 - 4 2 defines the irr, isr, and imr. 5.9.1.2 acknowledging interrupts the processor generates an interrupt acknowle dge cycle that is translated by the host bridge into a pci interrupt acknowledge cy cle to chipset. the pic translates this command into two internal inta# pulses expe cted by the 8259 cores. the pic uses the first internal inta# pulse to freeze 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 wi th three bits representing the interrupt within that controller. 5.9.1.3 hardware/software 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. table 5-42.interrupt status registers bit description irr interrupt request register. this bit is set on a low to high transition of the interrupt 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 ma sked interrupt will not generate intr. isr interrupt service register. this bit is set, and the co rresponding irr bit cleared, when an interrupt acknowledge cycle is seen, and the vect or returned is for that interrupt. imr interrupt mask register. this bit determines whethe r an interrupt is masked. masked interrupts will not generate intr. table 5-43.content of interrupt vector byte master, slave interrupt bits [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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 115 functional description 3. the processor acknowledges the intr and responds with an interrupt acknowledge cycle. the cycle is translated into a pc i interrupt acknowledge cycle by the host bridge. this command is broadcast over pci by chipset. 4. upon observing its own interrupt acknowledg e cycle on pci, chipset converts it into the two cycles that the internal 8259 pair can respond to. each cycle appears as an interrupt acknowledge pulse on the intern al inta# pin of the cascaded interrupt controllers. 5. upon receiving the first internally genera ted 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 ge nerated 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.9.2 initialization command words (icwx) before operation can begin, each 8259 must be initialized. in chipset, 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.9.2.1 icw1 an i/o write to the master or slave controller base address with data bit 4 equal to 1 is interpreted as a write to icw1. upon sens ing this write, chipset 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 initializati on 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. the interrupt mask register is cleared. 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. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 116 datasheet 5.9.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.9.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 chipset, 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.9.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.9.3 operation command words (ocw) these command words reprogram the interru pt controller to operate in various interrupt modes. ? ocw1 masks and unmasks interrupt lines. ? ocw2 controls the rotation of interrupt pr iorities when in rotating priority mode, and controls the eoi function. ? ocw3 is sets up isr/irr reads, enables/disables the special mask mode (smm), and enables/disables polled interrupt mode. 5.9.4 modes of operation 5.9.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 acknow ledged, 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 117 functional description the second inta#. while the isr bit is set, all further interrupts of the same or lower priority are inhibited, while higher levels ge nerate another interrupt. interrupt priorities can be changed in the rotating priority mode. 5.9.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 th at 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.9.4.3 automatic 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.9.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.9.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 inte rrupt service routine do not need separate vectors if the service routine uses the poll command. poll mode can also be used to www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 118 datasheet expand the number of interrupts. the pollin g interrupt service routine can call the appropriate service routine, instead of prov iding 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, disablin g 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. 5.9.4.6 cascade mode the pic in chipset has one master 8259 and one slave 8259 cascaded onto the master through irq2. this configuration can handle up to 15 separate priority levels. the master controls the slaves through a three bit internal bus. in chipset, 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.9.4.7 edge and level triggered mode in isa systems this mode is programmed using bit 3 in icw1, which sets level or edge for the entire controller. in chipset, this bi t is disabled and a new register for edge and level triggered mode selection, per interrupt input, is included. th is is the edge/level control registers elcr1 and elcr2. if an elcr bit is 0, an interrupt request w ill be recognized by a low-to-high transition on the corresponding irq input. the irq in put can remain high without generating another interrupt. if an elcr bit is 1, an in terrupt request will be recognized by a high level on the corresponding irq input and ther e 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 in ta#. if the irq input goes inactive before this time, a default irq7 vector is returned. 5.9.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, th e eoi command; or automatically when aeoi bit in icw4 is set to 1. 5.9.4.9 normal end of interrupt in normal eoi, software writes an eoi co mmand before leaving the interrupt service routine to mark the interrupt as complete d. there are two forms of eoi commands: specific and www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 119 functional description non-specific. when a non-specific eoi comm and is issued, the pic clears the highest isr bit of those that are set to 1. non-specif ic eoi is the normal mode of operation of the pic within chipset, as the interrupt bein g 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 dete rmine which isr bit to clear by issuing a specific eoi. an isr bit that is masked is no t 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.9.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 acknowle dge 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. 5.9.5 masking interrupts 5.9.5.1 masking on an indi vidual interr upt 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.9.5.2 special mask mode some applications may require an interrupt service routine to dynamically alter the system priority structure during its execution under software control. for example, the 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 register. normally, when an interrupt servic e routine acknowledges an interrupt without 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.9.6 steering pci interrupts chipset can be programmed to allow pirqa# -pirqh# to be internally routed to interrupts 3?7, 9?12, 14 or 15. the assignme nt is programmable through the 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. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 120 datasheet 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 routed to specified irq line, software must change the irq's corresponding elcr bit to level sensitive mode. chipset internally inverts the pirqx# line to send an active 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 external pirq to be asserted. chipset receives the pirq input, like all of the other external sources, and routes it accordingly. 5.10 advanced programmable interrupt controller (apic) (d31:f0) in addition to the standard isa-compatible pic described in the previous chapter, chipset incorporates the apic. while the stan dard 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.10.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 th e 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 chipset suppor ts 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.10.2 interrupt mapping the i/o apic within chipset 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 . www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 121 functional description 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 inte rnal interrupt sources. 2. if irq 11 is used for hpet #2, software should ensure irq 11 is not shared with any other devices to ensure the proper operation of hpet #2. chipset hardware does not prevent sharing of irq 11. 5.10.3 pci/pci express* message-based interrupts when external devices through pci / pci expr ess wish to generate an interrupt, they will send the message defined in the pci express* base specification, revision 1.0a for generating inta# ? intd#. these will be tran slated internal assertions/de-assertions of inta# ? intd#. table 5-44.apic interrupt mapping irq # 1 via serirq direct from pin via pci message internal modules 0 no no no cascade 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 2 12 yes no yes 13 no no no ferr# logic 14 yes yes 3 yes sata primary (legacy mode) 15 yes yes yes sata secondary (legacy mode) 16 pirqa# pirqa# yes internal devices are routable; see section 10.1.37 though section 10.1.46 . 17 pirqb# pirqb# 18 pirqc# pirqc# 19 pirqd# pirqd# 20 n/a pirqe# yes option for sci, tco, hpet #0,1,2. other internal devices are routable; see section 10.1.37 though section 10.1.46 . 21 n/a pirqf# 22 n/a pirqg# 23 n/a pirqh# www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 122 datasheet 5.10.4 front side bu s interrupt delivery for processors that support front side bus (fsb) interrupt delivery, chipset requires that the i/o apic deliver interrupt messages to the processor in a parallel manner, rather than using the i/o apic serial scheme. this is done by chipset 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 chipset detects an interrupt event (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, chipset 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. chipset then delivers the message by perf orming a write cycle to the appropriate address with the appropriate data. the address and data formats are described below in section 5.10.4.4 . note: fsb interrupt delivery compatibility with processor clock control depends on the processor, not chipset. 5.10.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.10.4.2 level-trig gered operation 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.10.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.10.4.4 interrupt message format chipset writes the message to pci (and to the host controller) as a 32-bit memory write cycle. it uses the formats shown in ta b l e 5 - 4 5 and ta b l e 5 - 4 6 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 chipset has any way to have a smi www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 123 functional description source from chipset power management logic cause the i/o apic to send an smi message (there is no way to do this). chipset?s i/o apic can only send interrupts due to interrupts which do not include smi, nmi or init. this means that in ia32/ia64 based platforms, front side bus interrupt message format delivery modes 010 (smi/pmi), 100 (nmi), and 101 (init) as indi cated in this section, must not be used and is not supported. only the hardware pin connection is supported by chipset. : table 5-45.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. 3 redirection hint: this bit is used by the processor host bridge to allow the interrupt message to be redirected. 0 = the message will be de livered 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 2 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 to those processors that are part of the logical group as based on the logical id. 1:0 will always be 00. table 5-46.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 correspondi ng bit in the i/o redirection table for that interrupt. 10:8 delivery mode: this is the same as the correspo nding 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 th e corresponding bits in the i/o redirection table for that interrupt. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 124 datasheet 5.11 serial interrupt (d31:f0) chipset supports a serial irq scheme. this allo ws a single signal to be used to report interrupt requests. the signal used to transmit this information is shared between the host, chipset, and all peripherals that su pport 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 re lease 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 chipset supports a message for 21 serial interrupts. these represent the 15 isa interrupts (irq0?1, 2?15), the four pci inte rrupts, and the control signals smi# and iochk#. the serial irq protocol does not support the additional apic interrupts (20?23). 5.11.1 start frame the serial irq protocol has two modes of operation which affect the start frame. these two modes are: continuous, where chipset 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, chipset asserts the start frame. this start frame 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 configuratio n 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. chipset senses the line low and continues to drive it low for the remainder of the start fr ame. since the first pci clock of the start frame was driven by the peripheral in this mode, chipset drives the serirq line low for 1 pci clock less than in continuous mode. this mode of operation allows for a quiet, and therefore lower power, operation. 5.11.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/data frames 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 125 functional description 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.11.3 stop frame after all data frames, a stop frame is driven by chipset. the serirq signal is driven low by chipset 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.11.4 specific interrupts not supported via serirq there are three interrupts seen through the serial stream that are not supported by chipset. these interrupts are generated inte rnally, and are not sharable with other devices within the system. these interrupts are: ? irq0. heartbeat interrupt generated 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#. chipset 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. 5.11.5 data frame format ta b l e 5 - 4 8 shows the format of the data frames. for the pci interrupts (a ? d), the output from chipset is anded with the pci in put 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-47.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 may initiate a start frame www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 126 datasheet 5.12 real time clock (d31:f0) the real time clock (rtc) module provides a battery backed-up date 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 available. the hour is represented in twelve or twenty-fou r hour format, and data can be represented in bcd or binary format. the design is f unctionally 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 ar e for time and date information. the next four (0ah to 0dh) are registers, which configure and report rtc functions. table 5-48.data frame format data frame # interrupt clocks past start frame comment 1 irq0 2 ignored. irq0 can only be generated vi a 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 irq14 44 not attached to sata logic 16 irq15 47 not 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 pirqc# 21 pci intd# 62 drive pirqd# www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 127 functional description the time and calendar data should match the data mode (bcd or binary) and hour mode (12 or 24 hour) as selected in regist er 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 co uld 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 royal observatory greenwich, years that are divisible by 100 are typically not leap year s. 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. chipset does not implement month/year alarms. 5.12.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 ma tching 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 upda ted-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 and daylight savings 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 se t at least two seconds before one of these conditions (leap year, daylight savings time adjustments) occurs. 5.12.2 interrupts the real-time clock interrupt is internally routed within chipset both to the i/o apic and the 8259. it is mapped to interrupt vector 8. this interrupt does not leave chipset, 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. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 128 datasheet 5.12.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 range 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.12.4 century rollover chipset detects a rollover when the year by te (rtc i/o space, index offset 09h) transitions form 99 to 00. upon dete cting the rollover, chipset 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, chipset 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.12.5 clearing battery-backed rtc ram clearing cmos ram in an chipset-based plat form 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 rtc cmos array once the system is booted. the normal position would cause rtcrst# to be pulled up through a weak pull-up resistor. ta b l e 5 - 4 9 shows which bits are set to their default state when rtcrst# 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 129 functional description table 5-49.configuration bits reset by rtcrst# assertion (sheet 1 of 2) bit name register location bit(s) default state alarm interrupt enable (aie) register b (general configuration) (rtc_regb) i/o space (rtc index + 0bh) 5x alarm flag (af) register c (flag register) (rtc_regc) i/o space (rtc index + 0ch) 5x swsmi_rate_sel general pm configuration 3 register gen_pmcon_3 d31:f0:a4h 7:6 0 slp_s4# minimum assertion width general pm configuration 3 register gen_pmcon_3 d31:f0:a4h 5:4 0 slp_s4# assertion stretch enable general pm configuration 3 register gen_pmcon_3 d31:f0:a4h 3 0 rtc power status (rtc_pwr_sts) general pm configuration 3 register gen_pmcon_3 d31:f0:a4h 2 0 power failure (pwr_flr) general pm configuration 3 register (gen_pmcon_3) d31:f0:a4h 1 0 afterg3_en general pm configuration 3 register gen_pmcon_3 d31:f0:a4h 0 0 power button override status (prbtnor_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 register (gpe0_en) pmbase + 2ch 11 0 batlow_en (netbook only) general purpose event 0 enables register (gpe0_en) pmbase + 2ch 10 0 www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 130 datasheet 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 array. note: the gpi strap technique to clear cmos requ ires multiple steps to implement. the system is booted with the jumper in ne w 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.13 processor interface (d31:f0) chipset interfaces to the processor with a variety of signals ? standard outputs to processor: a20m#, smi#, nmi, init#, intr, stpclk#, ignne#, cpuslp# (supported only on nettop platforms), cpupwrgd ? standard input from processor: ferr# ? intel speedstep ? technology output to processor: cpupwrgood (in netbook configurations) most chipset outputs to the processor use standard buffers. chipset 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.13.1 processor interface signals this section describes each of the signals that interface between chipset 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.13.1.1 a20m# (mask a20) the a20m# signal is active (low) when bo th of the following conditions are true: ri_en general purpose event 0 enables register (gpe0_en) pmbase + 2ch 8 0 newcentury_sts tco1 status register (tco1_sts) tcobase + 04h 7 0 intruder detect (intrd_det) tco2 status register (tco2_sts) tcobase + 06h 0 0 top swap (ts) backed up control register (buc) chipset config registers:offset 3414h 0x table 5-49.configuration bits reset by rtcrst# assertio n (sheet 2 of 2) bit name register location bit(s) default state www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 131 functional description ? 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). 5.13.1.2 init# (initialization) the init# signal is active (driven low) based on any one of several events described in ta b l e 5 - 5 0 . 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 inactive. this section refers to init#, but applies to two signals: init# and init3_3v#, as init3_3v# is functionally identical to init#, but signaling at 3.3 v. 5.13.1.3 ferr#/ignne# (numeric coproc essor error/ ignore numeric error) chipset 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 co processor 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), chipset negates the internal irq13 and drives ignne# active. ig nne# remains active until ferr# is driven inactive. ignne# is not driven active unless ferr# is active. table 5-50.init# going active cause of init# going active comment shutdown special cycle from processor. port92 write, where init_now (bit 0) transitions from a 0 to a 1. portcf9 write, where sys_rst (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 chipset will arm init# to be generated again. note: rcin# signal is expe cted to be high during s3 hot and low during s3 cold , 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, so ftware sets cpu_bist_en bit and then does a full processor reset using the cf9 register. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 132 datasheet if coproc_err_en is not set, the assertion of ferr# will have not generate an internal irq13, nor will the write to f0h generate ignne#. 5.13.1.4 nmi (non-maskable interrupt) non-maskable interrupts (nmis) can be generated by several sources, as described in ta b l e 5 - 5 1 . 5.13.1.5 stop clock request and cpu sleep (stpclk# and cpuslp#) chipset power management logic controls these active-low signals. refer to section 5.14 for more information on the functionality of these signals. note: cpu sleep (cpuslp#) is supported only on nettop platforms. 5.13.1.6 cpu power good (cpupwrgood) this signal is connected to the processor?s pwrgood input. this signal represents a logical and of chipset?s pwrok and vrmpwrgd signals. 5.13.1.7 deeper sleep (dpslp#) this active-low signal controls the internal gating of the processor?s core clock. this signal asserts before and deasserts after th e 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-12. coprocessor error timing diagram ferr# internal irq13 i/o write to f0h ignne# table 5-51.nmi sources cause of nmi comment serr# goes active (either internally, externally via serr # signal, or via message from cpu) 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). www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 133 functional description 5.13.2 dual-processor issues (nettop only) 5.13.2.1 signal differences in dual-processor designs, some of the processor signals are unused or used differently than for uniprocessor designs. 5.13.2.2 power management for dual-processor configurations in which more than one stop grant cycle may be generated, the cpu is expected to count st op grant cycles and only pass the last one through to chipset. this prevents chipset fr om getting out of 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 chipset only supports the c1 state for dual-processor designs. in going to the s1 state for nettop, multiple stop-grant cycles will be generated by the processors. chipset also has the option to assert the processor?s slp# signal (cpuslp#). 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. 5.14 power management (d31:f0) 5.14.1 features ? support for advanced configuration and powe r interface, version 2.0 (acpi) providing power and thermal management ? acpi 24-bit timer ? software initiated throttling of processor performance for thermal and power reduction table 5-52.dp signal differences signal difference a20m# / a20gate generally not used , but still supported by chipset. stpclk# used for s1 state as well as preparation for entry to s3?s5 also allows for therm# based throttli ng (not via acpi control methods). should be connected to both processors. ferr# / ignne# generally not used, but still supported by chipset. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 134 datasheet ? hardware override to throttle processor performance if system too hot ?sci and smi# generation ? pci pme# signal for wake up from low-power states ? system clock control ? (netbook only) acpi c2 state: stop grant (using stpclk# signal) halts processor?s instruction stream ? (netbook only) acpi c3 state: ability to halt processor clock (but not memory clock) ? (netbook only) acpi c4 state: ability to lower processor voltage. ? (netbook only) clkrun# protocol for pci clock starting/stopping ? system sleep state control ? acpi s1 state: stop grant (using stpclk# signal) halts processor?s instruction stream (only stpclk# active, and cpuslp# optional) ? 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 ? streamlined legacy power management for apm-based systems 5.14.2 chipset and system power states ta b l e 5 - 5 3 shows the power states defined for c hipset -based platforms. the state names generally match the corresponding acpi states. table 5-53.general power states for systems using chipse t (sheet 1 of 2) state/ substates legacy name / description g0/s0/c0 full on: processor operating. individual de vices may be shut down to save power. the different processor operating levels are defined by cx states, as shown in ta b l e 5 - 5 4 . within the c0 state, chipset can throttle the processor using the stpclk# signal to reduce power co nsumption. the throttling 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 (netbook only) stop-grant: the stpclk# signal goes active to the processor. the processor performs a stop-grant cycle, halts its in struction stream, an d 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 (netbook only) stop-clock: the stpclk# signal goes active to the processor. the processor performs a stop-grant cycle, halts its instruction stream. chipset then asserts dpslp# followed by stp_cpu#, which fo rces the clock generator to stop the processor clock. this is al so used for intel speedstep ? technology support. accesses to memory (by graphics, pci, or internal units) is not permitted while in a c3 state. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 135 functional description ta b l e 5 - 5 4 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. g0/s0/c4 (netbook only) stop-clock with lower processor voltage: this closely resembles the g0/ s0/c3 state. however, after chipset 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, chipset increases the voltage to the processor. g1/s1 stop-grant: similar to g0/s0/c2 state. chipset also has the option to assert the cpuslp# signal to furthe r reduce processor power consumption (nettop only). note: the behavior for this state is sl ightly different wh en supporting ia64 processors. g1/s3 suspend-to-ram (str): the system context is maintained in system dram, but power is shut off to non-critical ci rcuits. memory is re tained, and refreshes continue. all clocks stop except rtc clock. g1/s4 suspend-to-disk (std): 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 requ ired when waking. g3 mechanical off (moff): system context not maintained. all power is shut off except for the rtc. no ?wake? events are possible, because the system does not have any power. this state occurs if th e user removes the batteries, turns off a mechanical switch, or if the system power supply is at a level that is insufficient to power the ?waking? logic. when system power returns, tran sition will depends on the state just prior to the entry to g3 and the afterg3 bit in the gen_pmcon3 register (d31:f0 , offset a4). refer to ta b l e 5 - 6 1 for more details. table 5-53.general power states for systems using chipset (sheet 2 of 2) state/ substates legacy name / description table 5-54.state transition rule s for chipset (sheet 1 of 2) present state transition trigger next state g0/s0/c0 ? processor halt instruction ? level 2 read ? level 3 read (netbook only) ? level 4 read (netbook 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) (netbook 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 www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 136 datasheet notes: 1. some wake events can be pr eserved through power failure. 2. transitions from the s1?s5 or g3 states to the s0 state are deferr ed until batlow# is inactive in netbook configurations. 5.14.3 system power planes the system has several independent power planes, as described in ta b l e 5 - 5 5 . note that when a particular power plane is shut off, it should go to a 0 v level. g0/s0/c2 (netbook only) ? any enabled break event ? power button override ?power failure ? previously in c3/c4 and bus masters idle ?g0/s0/c0 ?g2/s5 ?g3 ? c3 or c4 - depending on pdme bit (d31:f0: offset a9h: bit 4) g0/s0/c3 (netbook 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 (netbook 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 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) table 5-54.state transition rules for chipset (sheet 2 of 2) present state transition trigger next state www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 137 functional description s 5.14.4 smi#/sci generation on any smi# event taking place, chipset 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 pciclk. if another smi event occurs, smi# is driven active again. the sci is a level-mode interrupt that is ty pically handled by an acpi-aware operating system. in non-apic systems (which is the de fault), the sci irq is routed to one of the 8259 interrupts (irq 9, 10, or 11). the 825 9 interrupt controller must be programmed to level mode for that interrupt. in systems using the apic, the sci can be rout ed 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.14 ). the interrupt remains asserted until all sci sources are removed. table 5-55.system power plane plane controlled by description cpu slp_s3# signal the slp_s3# signal can be used to cut th e power to the processor completely. for netbook systems, the dprslpvr support al lows lowering the processor?s voltage during the c4 state. s3 hot : the new s3 hot state keeps more of the plat form logic, including chipset core well, powered to reduce the cost of external powe r plane logic. slp_s3# is only used to remove powe r to the processor and to shut system clocks. this impacts the board design, but there is no specific chipset bit or strap needed to indicate which option is selected. main slp_s3# signal (s3 cold ) or slp_s4# signal (s3 hot ) s3 cold : when slp_s3# goes active, power ca n 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 mu st be retained to the main memory. the processor, devices on the pci bus, lpc i/f, and graphi cs will typically be shut off when the main power plane is shut, although there may be small subsections powered. s3 hot : slp_s4# is used to cut the main po wer well, rather than using slp_s3#. this impacts the board design , but there is no specific chipset bit or strap needed to indicate which option is selected. 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 sh ut 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 powe r to the memory can also be shut. device[n] gpio individual subsystems may have their own power plan e. for example, gpio signals may be used to control the power to disk drives, audio amplifiers, or the display screen. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 138 datasheet ta b l e 5 - 5 6 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 wi th an acpi-based system. each smi# or sci source has a corresponding enable and status bit. table 5-56.causes of smi# and sci (sheet 1 of 2) cause 1-5 sci smi additional en ables where reported pme# yes yes pme_en=1 pme_sts pme_b0 (internal ehci controller) 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_sts power button override 6 ) yes no none prbtnor_sts rtc alarm 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 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 7 yes 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 tcosci_sts tco sci message from cpu yes no none mchsci_sts tco smi logic no yes tco_en=1 tco_sts tco smi ? year 2000 rollover no yes 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 cpu 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 139 functional description 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. chipset must have smi# fully enabled when chipset is also enabled to trap cycles. if smi# is not enabled in conjunction with the trap en abling, then hardware behavior is undefined. 6. when a power button override first occurs, th e system will transition immediately to s5. the sci will only occur after the next wake to s0 if the residual status bit (prbtnor_sts) is not cleared prior to setting sci_en. 7. only gpi[15:0] may generate an smi# or sci. tco smi ? change of the bioswp bit from 0 to 1 no yes bld=1 bioswr_sts tco smi ? write attempted to bios no yes bioswp=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 no 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 controller 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_intren smbus_smi_sts host_notify_sts (netbook) 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 table 5-56.causes of smi# and sci (sheet 2 of 2) cause 1-5 sci smi additional enables where reported www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 140 datasheet 5.14.4.1 pci express* sci pci express ports and the cpu (via dmi) have the ability to cause pme using messages. when a pme message is received, chipse t will set the pci_exp_sts bit. if the pci_exp_en bit is also set, chipset can cause an sci via the gpe1_sts register. 5.14.4.2 pci express* hot-plug pci express has a hot-plug mechanism and is capable of generating a sci via the gpe1 register. it is also capable of generating an smi. however, it is not capable of generating a wake event. 5.14.5 dynamic proces sor clock control chipset has extensive control for dynamically starting and stopping system clocks. the clock control is used for transitions among the various 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. chipset supports the acpi c0 and c1 states (in nettop) or c0, c1, c2, c3 and c4 (in netbook) states. the dynamic processor clock control is handled using the following signals: ? stpclk#: used to halt processor instruction stream. ? (netbook) stp_cpu#: used to stop processor?s clock ? (netbook) dpslp#: used to force deeper sleep for processor. ? (netbook) dprslpvr: used to lower voltage of vrm during c4 state. ? (netbook) dprstp#: used to lower voltage of vrm during c4 state the c1 state is entered based on the processor performing an auto halt instruction. (netbook) the c2 state is entered based on the processor reading the level 2 register in chipset. it 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. (netbook) the c3 state is entered based on the processor reading the level 3 register in chipset and when the c4 on c3_en bit is clear (d31:f0:offset a0:bit 7). this state can also be entered after a temporary retu rn to c2 from a prior c3 or c4 state. (netbook) the c4 state is entered based on the processor reading the level 4 register in chipset, or by reading the level 3 register when the c4onc3_en bit is set. this state can also be entered after a temporary return to c2 from a prior c4 state. a c1 state in nettop only or a c1, c2, c3, or c4 state in netbook only ends due to a break event. based on the break event, chipset returns the system to c0 state. (netbook) ta b l e 5 - 5 7 lists the possible break events from c2, c3, or c4. the break events from c1 are indicated in the processor?s datasheet. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 141 functional description 5.14.5.1 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). ? (netbook) 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. ? (netbook) 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). ? 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 chipset observing the stop-grant cycle. this ensures that the stpclk# signals stays active for a sufficient period after the proce ssor observes the response phase. table 5-57.break events (netbook) event breaks from comment any unmasked interrupt goes active c2, c3, c4 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 many possible sources any internal event that cause init# to go active c2, c3, c4 could be indicated by the keyboard controller via the rcin input signal. any bus master request (internal, external or dma, or bm_busy#) 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) www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 142 datasheet ? (netbook) if in the c1 state and the stpc lk# signal goes active, the processor will generate 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.14.5.2 deferred c3/c4 (netbook only) due to the new dmi protocol, if there is any bus master activity (other than true isoch), then the c0-to-c3 transition will pause at th e c2 state. chipset will keep the processor in a c2 state until: ? chipset does not detect bus master activity. ? a break event occurs. in this case, chipset 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 chipset will treat bus master activity as a break event. when reaching the c2 state, if there is any bus master activity, chipset will return the processor to a c0 state. 5.14.5.3 popup (auto c3/c4 to c2) (netbook only) when the pume bit (d31:f0: offset a9h: bit 3) is set, chipset enables a mode of operation where standard (non-isoch) bus mast er 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 cpu, even if the arb_dis bit is set. 5.14.5.4 popdown (auto c2 to c3/c4) (netbook 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 simila r 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 that bus master traffic is not a break event in this case. 5.14.6 dynamic pci cloc k control (netbook 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 143 functional description 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 chipset is ?free-runnin g? and is not affected by the stp_pci# signal. 5.14.6.1 conditions for checking the pci clock when there is a lack of pci activity chipset 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, chipset deasserts (drive high) clkrun# for 1 clock and then tri-states the signal. 5.14.6.2 conditions for ma intaining the pci clock pci masters or lpc devices that wish to main tain the pci clock running will observe the clkrun# signal deasserted, and then must re-assert if (drive it low) within 3 clocks. ? when chipset has tri-stated the clkrun# si gnal after deasserting it, chipset then checks to see if the signal has been re-asserted (externally). ? after observing the clkrun# signal assert ed for 1 clock, chipset again starts asserting the signal. ? if an internal device needs the pci bu s, chipset asserts the clkrun# signal. 5.14.6.3 conditions for stopping the pci clock ? if no device re-asserts clkrun# once it has been deasserted for at least 6 clocks, chipset stops the pci clock by assertin g the stp_pci# signal to the clock synthesizer. 5.14.6.4 conditions for re -starting the pci clock ? a peripheral asserts clkrun# to indicate that it needs the pci clock re-started. ? when chipset observes the clkrun# signal asserted for 1 (free running) clock, chipset deasserts the stp_pci# signal to the clock synthesizer within 4 (free running) clocks. ? observing the clkrun# signal asserted ex ternally for 1 (free running) clock, chipset again starts driving clkrun# asserted. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 144 datasheet if an internal source requests the clock to be re-started, chipset re-asserts clkrun#, and simultaneously deasserts the stp_pci# signal. 5.14.6.5 lpc devices and clkrun# (netbook only) if an lpc device (of any type) needs the 33 mhz pci clock, such as for lpc dma (netbook only) 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 chipset asserts it on their behalf. the ldrq# inputs are ignored by chipset wh en the pci clock is stopped to the lpc devices in order to avoid misinterpreting the request. chipset 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#, chipset assume s that the lpc device receives its first clock rising edge corresponding to chipset? s second pci clock rising edge after the deassertion. 5.14.7 sleep states 5.14.7.1 sleep state overview chipset directly supports different sleep stat es (s1?s5) that are entered by setting the slp_en bit, or due to a power button press. the entry to the sleep states are 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 has higher priority than throttling. ? prior to setting the slp_en bit, the software turns off processor-controlled throttling. note that thermal throttling ca nnot be disabled, but setting the slp_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.14.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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 145 functional description 5.14.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 en abled via a gpio pin before it can be used. upon exit from chipset-controlled sleep st ates, the wak_sts bit is set. the possible causes of wake events (and their restrictions) are shown in ta b l e 5 - 5 9 . note: (netbook only) if the batlow# signal is asserted, chipset does not attempt to wake from an s1?s5 state, even if the power butt on is pressed. this prevents the system from waking when the battery power is insu fficient to wake the system. wake events that occur while batlow# is asserted are latched by chipset, and the system wakes after batlow# is de-asserted. table 5-58.sleep types sleep type comment s1 chipset asserts the stpclk# signal. it also has the option to assert cpuslp# signal (only suppo rted on nettop plat forms). this lowers the processor?s power consumption. no snooping is possible in this state. s3 chipset asserts slp_s3#. the slp_s3# sign al controls the powe r to non-critical circuits. power is only retained to devices needed to wake from this sleeping state, as well as to the memory. s4 chipset asserts slp_s3# and slp_s4#. th e 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. chipset as serts slp_s3#, slp_s4# and slp_s5#. table 5-59.causes of wake events cause states can wake from 1 how enabled rtc alarm s1 ? s5 2 set rtc_en bit in pm1_en register power button s1 ? s5 always enabled as wake event gpi[0:15] s1 ? s5 2 gpe0_en register note: gpis that are in the core well are not capable of waking the system from sleep states where the core well is not powered. classic usb s1 ? s5 set usb1_en, usb 2_en, usb 3_en, and usb4_en bits in gpe0_en register lan s1 ? s5 will use pme#. wake enable set with lan logic. ri# s1 ? s5 2 set ri_en bit in gpe0_en register intel hd audio s1 ? s5 2 set ac97_en bit in gpe0_en register primary pme# s1 ? s5 pme_b0_en bit in gpe0_en register secondary pme# s1 ? s5 set pme_en bit in gpe0_en register. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 146 datasheet notes: 1. if in the s5 state due to a powerbutton ove rride or thrmtrip#, the possible wake events are due to power button, hard reset without cycling (see command type 3 in ta b l e 5 - 81 ), and hard reset system (see command type 4 in ta b l e 5 - 8 1 ). 2. 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. 3. when the wake# pin is active and the pci ex press device is enable d to wake the system, chipset will wake the platform. it is important to understand that the variou s gpis have 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. ta b l e 5 - 6 0 summarizes the use of gpis as wake events. the latency to exit the various sleep states varies greatly and is heavily dependent on power supply design, so much so that the exit latencies due to chipset are insignificant. 5.14.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 cpu (via dmi) have the ability to cause pme using messages. when a pme message is received, chipset will set the pci_exp_sts bit. pci_exp_wake# s1?s5 pci_exp_wake bit 3 pci_exp pme message s1 must use the pci express* wake# pin rather than messages for wake from s3,s4, or s5. smbalert# s1 ? s5 always enabled as wake event smbus slave message 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. smbus host notify message received s1 ? s5 host_notify_wken bit smbu s slave command register. reported in the smb_wak_sts bit in the gpeo_sts register. table 5-59.causes of wake events cause states can wake from 1 how enabled table 5-60.gpi wake events gpi power well wake from notes gpi[12, 7:0] core s1 acpi compliant gpi[15:13,11:8] resume s1?s5 acpi compliant www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 147 functional description 5.14.7.5 sx-g3-sx, ha ndling 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 previo usly 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 chipset exits g3 after power returns (rsmrst# goes high), the pwrbtn # signal is already high (because v cc - 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 returns the ri_sts bit is set and the system interprets that as a wake event. 3. rtc alarm: the rtc_en bit is in the rtc well and is preserved after a power loss. like pwrbtn_sts the rtc_sts bit is cleared when rsmrst# goes low. chipset 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#. 5.14.8 thermal management chipset has mechanisms to assist with managing thermal problems in the system. 5.14.8.1 thrm# signal the thrm# signal is used as a status inpu t for a thermal sensor. based on the thrm# signal going active, chipset generates an smi# or sci (depending on sci_en). table 5-61.transitions due to power failure state at power failure afterg3_en bit transition when power returns s0, s1, s3 1 0 s5 s0 s4 1 0 s4 s0 s5 1 0 s5 s0 www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 148 datasheet 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 go es 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 includ e shutting off unwanted subsystems, or halting the processor. by setting the thrm_pol bit to high, anothe r smi# or sci can optionally be generated 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.14.8.2 processor init iated passive cooling this mode is initiated by software setting the thtl_en (pmbase+10h:bit 4) or force_thtl (pmbase+10h:bit 8) bits. software sets the thtl_dty (pmbase+10h:b its 3:1) or thrm_dty (pmbase+10h:bits 7:5) bits to select throttle ratio and th tl_en or force_thtl bits to enable the throttling. throttling results in stpclk# active for a minimum time of 12.5% and a maximum 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, chipset waits for the stop- grant cycle before starting the count of the time the stpclk# signal is active. 5.14.8.3 thrm# override software bit the force_thtl bit allows the bios to forc e passive cooling, independent of the acpi software (which uses the thtl_en and thtl_dty bits). if this bit is set, chipset starts throttling using the ratio in the thrm_dty field. when this bit is cleared chipset 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 ar e set, then chipset should use the duty cycle defined by the thrm_dty field, not the thtl_dty field. 5.14.8.4 active cooling active cooling involves fans. the gpio signals from chipset can be used to turn on/off a fan. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 149 functional description 5.14.9 event input signals and their usage chipset has various input signals that trigger specific events. this section describes those signals and how they should be used. 5.14.9.1 pwrbtn# (power button) chipset 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 input. the state transition descriptions are included in ta b l e 5 - 6 2 . 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. power button override function if pwrbtn# is observed active for at least four consecutive seconds, the state machine should unconditionally transition to the g2/s5 state, regardless of present state (s0? s4), even if pwrok is not active. in this ca se, the transition to the g2/s5 state should 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 afte r the de-bounce, and is readable via the pwrbtn_lvl bit. note: the 4-second pwrbtn# assertion should on ly be used if a system lock-up has occurred. the 4-second timer starts counting when chipset 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. table 5-62.transitions due to power button present state event transition/action comment s0/cx pwrbtn# goes low smi# or sci generated (depending on sci_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 unconditional transition to s5 state no dependence on processor (e.g., stop-grant cycles) or any other subsystem www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 150 datasheet 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 power button waiting for the system to awake. since a 4-second press of the power button 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 power button can wake the system, but the sleep button cannot. although chipset 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.14.9.2 ri# (ring indicator) the ring indicator can cause a wake event (if enabled) from the s1?s5 states. ta b l e 5 - 63 shows when the wake event is generated or ignored in different states. if in the g0/ s0/cx states, chipset generate s 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 c hipset . it can be in modem or external. 5.14.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 generate 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. table 5-63.transitions due to ri# signal present state event ri_en event s0 ri# active x ignored s1?s5 ri# active 0 1 ignored wake event www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 151 functional description 5.14.9.4 sys_reset# signal when the sys_reset# pin is detected as active after the 16 ms debounce logic, chipset 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 ev en though activity is still occurring. once the reset is asserted, it remains assert ed for 5 to 6 ms regardless of whether the sys_reset# 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.14.9.5 thrmtrip# signal if thrmtrip# goes active, the processor is indicating an overheat condition, and chipset immediately transitions to an s5 state. however, since the processor has overheated, it does not respond to chipset?s stpclk# pin with a stop grant special cycle. therefore, chipset does not wait for one. immediately upon seeing thrmtrip# low, chipset initiates a transition to the s5 state, drive slp_s3#, slp_s4#, slp_s5# low, and set the cts bit. the transition looks like a power button override. it is extremely important that when a th rmtrip# event occurs, chipset power down immediately without following the normal s0 -> s5 path. this path may be taken in parallel, but chipset must immediately enter a power down state. it does this by driving slp_s3#, slp_s4#, and slp_s5# immediately 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 chipset, are no longer executing cycles properly. therefore, if thrmtrip# goes acti ve, and chipset 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. chipset follows this flow for thrmtrip#. 1. at boot (pltrst# low), thrmtrip# ignored. 2. after power-up (pltrst# high), if thrmtrip# sampled active, slp_s3#, slp_s4#, and slp_s5# assert, and normal sequence of sleep machine starts. 3. until sleep machine enters the s5 state, slp_s3#, slp_s4#, and slp_s5# stay active, even if thrmtrip# is now inactive. this is the equivalent of ?latching? the thermal trip event. 4. if s5 state reached, go to step #1, othe rwise stay here. if chipset does not reach s5, chipset does not reboot until power is cycled. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 152 datasheet 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 5.14.9.6 bm_busy# (netbook only) the bm_busy# signal is an input from a graphics component to indicate if it is busy. if prior to going to the c3 stat e, the bm_busy# signal is ac tive, then the bm_sts bit will be set. if after going to the c3 state, th e bm_busy# signal goes back active, chipset will treat this as if one of the pci req# sign als went active. this is treated as a break event. 5.14.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 in to read-only registers, chipset implements an alt access mode. if the alt access mode is entered and exit ed after reading the registers of chipset timer (8254), the timer starts counting fa ster (13.5 ms). the following steps listed below can cause problems: 1. bios enters alt access mode for reading chipset 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 oper ating system does not reprogram the system timer again, the timer ticks may be happeni ng faster than expected. for example dos and its associated software assume that the system timer 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 window s* 98, windows* 2000, and windows nt*) reprogram the system timer and therefore do not encounter this problem. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 153 functional description 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 op erating 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 access mode. 5.14.10.1 write only registers with read paths in alt access mode the registers described in ta b l e 5 - 6 4 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-64.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 1 dma chan 0 base address low byte 40h 7 1 timer counter 0 status, bits [5:0] 2 dma chan 0 base address high byte 2 timer counter 0 base count low byte 01h 2 1 dma chan 0 base count low byte 3 timer counter 0 base count high byte 2 dma chan 0 base count high byte 4 timer counter 1 base count low byte 02h 2 1 dma chan 1 base address low byte 5 timer counter 1 base count high byte 2 dma chan 1 base address high byte 6 timer counter 2 base count low byte 03h 2 1 dma chan 1 base count low byte 7 timer counter 2 base count high byte 2 dma chan 1 base count high byte 41h 1 timer counter 1 status, bits [5:0] 04h 2 1 dma chan 2 base address low byte 42h 1 timer counter 2 status, bits [5:0] 2 dma chan 2 base address high byte 70h 1 bit 7 = nmi enable, bits [6:0] = rtc address 05h 2 1 dma chan 2 base count low byte c4h 2 1 dma chan 5 base address low byte 2 dma chan 2 base count high byte 2 dma chan 5 base address high byte 06h 2 1 dma chan 3 base address low byte c6h 2 1 dma chan 5 base count low byte 2 dma chan 3 base address high byte 2 dma chan 5 base count high byte www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 154 datasheet notes: 1. bits 5, 3, 1, and 0 return 0. 2. the ocw1 register must be read before entering alt access mode. 07h 2 1 dma chan 3 base count low byte c8h 2 1 dma chan 6 base address low byte 2 dma chan 3 base count high byte 2 dma chan 6 base address high byte 08h 6 1 dma chan 0?3 command 2 cah 2 1 dma chan 6 base count low byte 2 dma chan 0?3 request 2 dma chan 6 base count high byte 3 dma chan 0 mode: bits(1:0) = 00 cch 2 1 dma chan 7 base address low byte 4 dma chan 1 mode: bits(1:0) = 01 2 dma chan 7 base address high byte 5 dma chan 2 mode: bits(1:0) = 10 ceh 2 1 dma chan 7 base count low byte 6 dma chan 3 mode: bits(1:0) = 11. 2 dma chan 7 base count high byte 20h 12 1 pic icw2 of master controller d0h 6 1 dma chan 4?7 command 1 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 4 pic ocw1 of master controller 2 4 dma chan 5 mode: bits(1:0) = 01 5 pic ocw2 of master controller 5 dma chan 6 mode: bits(1:0) = 10 6 pic ocw3 of master controller 6 dma 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 controller 1 11 pic ocw2 of slave controller 12 pic ocw3 of slave controller table 5-64.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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 155 functional description 5.14.10.2 pic reserved bits many bits within the pic are reserved, and must have 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 ta b l e 5 - 6 5 . 5.14.10.3 read only registers with write paths in alt access mode the registers described in ta b l e 5 - 6 6 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 softwa re. 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. 5.14.11 system power supplies, planes, and signals 5.14.11.1 power plane control with slp_s3#, slp_s4# and slp_s5# the usage of slp_s3# and slp_s4# depends on whether the platform is configured for s3 hot and s3 cold . s3 hot the slp_s3# output signal is used to cut power only to the processor and associated subsystems and to optionally stop system clocks. table 5-65.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-66.register write accesses in alt access mode i/o address register write value 08h dma status register for channels 0?3. d0h dma status register for channels 4?7. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 156 datasheet s3 cold the slp_s3# output signal can be used to cut power to the system core supply, since it only goes active for the str state (typical ly mapped to acpi s3). power must be maintained to chipset resume well, and to any other circuits that need to generate wake signals from the str state. cutting power to the core may be done via the power supply, or by external fets to 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 memo ry may be done via the power supply, or by external fets to the motherboard. the slp_s4# output signal is used to remove 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 to the motherboard. 5.14.11.2 slp_s4# and su spend-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_s4# logic in chipse t 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 fe ature that is enabled by the slp_s4# assertion stretch enable bit (d31:f0:a4h bi t 3), the dram power must be controlled by the slp_s4# signal. 5.14.11.3 pwrok signal the pwrok input should go active based on the core supply voltages becoming valid. pwrok should go active no sooner than 100 ms after vcc3_3 and vcc1_5 have reached their nominal values. note: 1. sys_reset# is recommended for implem enting 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 sm bus and processor resets, and avoids improperly reporting power failures. 2. if the pwrok input is used to implement the system reset button, chipset does not provide any mechanism to limit the amount of time that the processor is held in reset. the platform must externally ensure that maximum reset assertion specifications are met. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 157 functional description 3. if a design has an active-low reset button electrically and?d with the pwrok signal from the power supply and the processo r?s voltage regulator module chipset pwrok_flr bit will be set. chipset treats th is internally as if the rsmrst# signal had gone active. however, it is not treated as a full power failure. if pwrok goes inactive and then active (but rsmrst# stays high), then chipset reboots (regardless of the state of the afterg3 bi t). if the rsmrst# signal also goes low before pwrok goes high, then this is a full power failure, and the reboot policy is controlled by the afterg3 bit. 4. 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 chipset. 5. in the case of true pwrok failure, pw rok goes low first before the vrmpwrgd. 5.14.11.4 cpupwrgd 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.14.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. vr mpwrgd may go active before or after the pwrok from the main power supply. chipset has no dependency on the order in which these two signals go active or inactive. 5.14.11.6 batlow# (battery low) (netbook 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. 5.14.11.7 controlling leakag e and power consumption during low-power states to control leakage in the system, various signals tri-state or go low during some low- power states. general principles: ? all signals going to powered down planes (e ither internally or externally) must be either tri-stated or driven low. ? signals with pull-up resistors should not be low during low-power states. this is to avoid the power consumed in the pull-up resistor. ? buses should be halted (and held) in a known state to avoid a floating input (perhaps to some other device). floating inputs can cause extra power consumption. based on the above principles, the following measures are taken: ? during s3 (str), all signals attached to powered down planes are tri-stated or driven low. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 158 datasheet 5.14.12 clock generators the clock generator is expected to provide the frequencies shown in ta b l e 5 - 6 7 . 5.14.12.1 clock control sign als from chipset to clock synthesizer (netbook only) the clock generator is assumed to have a direct connection from the following chipset signals: ? stp_cpu#: stops processor clocks in c3 and c4 states ? stp_pci#: stops system pci clocks (not chipset free-running 33 mhz clock) due to clkrun# protocol ? slp_s3#: expected to drive clock chip pwrdown (through inverter), to stop clocks in s3 hot and on the way to s3 cold to s5. table 5-67.chipset clock inputs clock domain frequency source usage sata_clk 100 mhz differential main clock generator used by sata controller. stopped in s3 ~ s5 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 nettop only: free-running pci clock to chipset. stopped in s3 ~ s5 based on slp_s3# assertion. netbook only: free-running (not affected by stp_pci# pci clock to chipset. this is not the system 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 controller s and intel hd 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. lan_clk 0.8 to 50 mhz lan connect lan connect interface. contro l policy is determined by the clock source. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 159 functional description 5.14.13 legacy power management theory of operation instead of relying on acpi software, legacy power management uses bios and various hardware mechanisms. the scheme relies on th e 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. chipset does not support burst modes. 5.14.13.1 apm power management (nettop only) chipset has a timer that, when enabled by the 1min_en bit in the smi control and enable register, generates an smi# once per minute. the smi handler can check for system activity by reading the devact_sts regi ster. 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 deva ct_sts register will be set. software clears the bits by writing a 1 to the bit position. the devact_sts register allows for monitori ng various internal devices, or super i/o devices (sp, pp, fdc) on lpc or pci, keyb oard controller accesses, or audio functions on lpc or pci. other pci activity can be monitored by checking the pci interrupts. 5.14.13.2 mobile apm power ma nagement (netbook only) in netbook systems, there are additional re quirements associated with device power management. to handle this, chipset has spec ific smi# traps available. the following algorithm is used: 1. the periodic smi# timer checks if a device is idle for the required 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 smi# handler 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. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 160 datasheet 5.15 system management (d31:f0) chipset provides various functions to make a system easier to manage and to lower the total cost of ownership (tco) of the system . in addition, chipset provides integrated asf management support. features and functions can be augmented via external a/d converters and gpio, as well as an external microcontroller. the following features and func tions are supported by chipset: ? 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 firmware hub programming ? detects if data on first read is ffh (indicates unprogrammed firmware hub) ? 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.52 ) ? integrated asf management support note: voltage id from the processor can be read via gpi signals. 5.15.1 theory 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 be provided without the aid of an external microcontroller. 5.15.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 rese t, the tco timer times out twice and chipset asserts pltrst#. 5.15.1.2 handling an intruder chipset 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 rtc 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 chipset to cause an smi# or interrupt. the bios or in terrupt handler can then cause a transition to the s5 state by writing to the slp_en bit. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 161 functional description the software can also directly read the status of the intruder# signal (high or low) by clearing and then reading the intrd_det bit. th is allows the signal to be used as a gpi if the intruder function is not required. 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 chipset?s rtc well, and is set and cleared synchronously with the rtc clock. thus, when software a ttempts 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 ge nerated again immediately. the smi handler can clear the intrd_sel bits to avoid furthe r smis. however, 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.15.1.3 detecting improper firmware hub programming chipset can detect the case where the firmware hub is not programmed. this results in the first instruction fetched to have a value of ffh. if this occurs, chipset sets the bad_bios bit, which can then be reported via the heartbeat and event reporting using an external, alert on lan* enabled lan controller (see section 5.15.2 ). 5.15.2 heartbeat and event reporting via smbus chipset integrated lan controller supports asf heartbeat and event reporting functionality when used with the 825 62em or 82562ex platform lan connect component. this allows the integrated lan controller to report messages to a network management console without the aid of the sy stem processor. this is crucial in cases where the processor is malfunctioning or cannot function due to being in a low-power state. all heartbeat and event messages are sent on the smbus interface. this allows an external lan controller to act upon these me ssages if the internal lan controller is not used. the basic scheme is for chipset integrated la n controller to send a prepared ethernet message to a network management console. the prepared message is stored in the non-volatile eeprom that is connected to chipset. messages are sent by the lan controller either because a specific event has occurred, or they are sent periodically (also know n as a heartbeat). the event and heartbeat messages have the exact same format. the event messages are sent based on events www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 162 datasheet occurring. the heartbeat messages are sent every 30 to 32 seconds. when an event occurs, chipset sends a new message and increments the seq[3:0] field. for heartbeat messages, the sequence number does not increment. the following rules/steps apply if the system is in a g0 state and the policy is for chipset to reboot the system after a hardware lockup: 1. on detecting the lockup, the second_to_st s bit is set. chipset may send up to 1 event message to the lan controller. chipset then attempts to reboot the processor. 2. if the reboot at step 1 is successful then the bios should clear the second_to_sts bit. this prevents any fu rther heartbeats from being sent. the bios may then perform addition recovery/boot steps. (see note 2, below.) 3. if the reboot attempt in step 1 is not su ccessful, the timer will timeout a third time. at this point the system has locked up and was unsuccessful in rebooting. chipset does not attempt to automatically reboot again. chipset starts sending a message every heartbeat period (30?32 seconds). the heartbeats continue until some external intervention occurs (reset, power failure, etc.). 4. after step 3 (unsuccessful reboot after third timeout), if the user does a power button override, the system goes to an s5 state. chipset continues sending the messages every heartbeat period. 5. after step 4 (power button override afte r unsuccessful reboot) if the user presses the power button again, the system should wake to an s0 state and the processor should start executing the bios. 6. if step 5 (power button press) is successful in waking the system, chipset continues sending messages every heartb eat period until the bios clears the second_to_sts bit. (see note 2) 7. if step 5 (power button press) is un successful in waking the system, chipset continues sending a message every heartbeat period. chipset does not attempt to automatically reboot again. chipset st arts sending a message every heartbeat period (30?32 seconds). the heartbeats continue until some external intervention occurs (reset, power failure, etc.). (see note 3) 8. after step 3 (unsuccessful reboot after thir d timeout), if a reset is attempted (using a button that pulses pwrok low or via the message on the smbus slave i/f), chipset attempts to reset the system. 9. after step 8 (reset attempt) if the rese t is successful, the bios is run. chipset continues sending a message every heartbeat period until the bios clears the second_to_sts bit. (see note 2) 10. after step 8 (reset attempt), if the reset is unsuccessful, chipset continues sending a message every heartbeat period. chipset does not attempt to reboot the system again without external intervention. (see note 3) the following rules/steps apply if the system is in a g0 state and the policy is for chipset to not reboot the system after a hardware lockup. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 163 functional description 1. on detecting the lockup the second_to_ sts bit is set. chipset sends a message with the watchdog (wd) event status bit set (and any other bits that must also be set). this message is sent as soon as the lockup is detected, and is sent with the next (incremented) sequence number. 2. after step 1, chipset sends a message every heartbeat period until some external intervention occurs. 3. rules/steps 4?10 apply if no user intervention (resets, power button presses, smbus reset messages) occur after a third timeout of the watchdog timer. if the intervention occurs before the third timeout, then jump to rule/step 11. 4. after step 3 (third timeout), if the user does a power button override, the system goes to an s5 state. chipset continues sending heartbeats at this point. 5. after step 4 (power button override), if the user presses the power button again, the system should wake to an s0 state and the processor should start executing the bios. 6. if step 5 (power button press) is su ccessful in waking the system, chipset continues sending heartbeats until the bi os clears the second_to_sts bit. (see note 2) 7. if step 5 (power button press) is unsuccessful in waking the system, chipset continues sending heartbeats. chipset does not attempt to reboot the system again until some external intervention occurs (reset, power failure, etc.). (see note 3) 8. after step 3 (third timeout), if a reset is attempted (using a button that pulses pwrok low or via the message on the smbus slave i/f), chipset attempts to reset the system. 9. if step 8 (reset attempt) is successful, the bios is run. chipset continues sending heartbeats until the bios clears th e second_to_sts bit. (see note 2) 10. if step 8 (reset attempt), is unsuccessful, chipset continues sending heartbeats. chipset does not attempt to reboot the sy stem again without external intervention. note: a system that has locked up and can not be restarted with power button press is probably broken (bad power su pply, short circuit on some bus, etc.) 11. this and the following rules/steps apply if the user intervention (power button press, reset, smbus message, etc.) occur pr ior to the third timeout of the watchdog timer. 12. after step 1 (second timeout), if the us er does a power button override, the system goes to an s5 state. chipset continues sending heartbeats at this point. 13. after step 12 (power button override), if the user presses the power button again, the system should wake to an s0 state and the processor should start executing the bios. 14. if step 13 (power button press) is successful in waking the system, chipset continues sending heartbeats until the bi os clears the second_to_sts bit. (see note 2) 15. if step 13 (power button press) is uns uccessful in waking the system, chipset continues sending heartbeats. chipset does not attempt to reboot the system again until some external intervention occurs (reset, power failure, etc.). (see note 3) www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 164 datasheet 16. after step 1 (second timeout), if a reset is attempted (using a button that pulses pwrok low or via the message on the smbus slave i/f), chipset attempts to reset the system. 17. if step 16 (reset attempt) is successful, the bios is run. chipset continues sending heartbeats until the bios clears th e second_to_sts bit. (see note 2) 18. if step 16 (reset attempt), is unsuccessful, chipset continues sending heartbeats. chipset does not attempt to reboot the sy stem again without external intervention. (see note 3) if the system is in a g1 (s1?s4) state, chipset sends a heartbeat message every 30? 32 seconds. if an event occurs prior to the system being shutdown, chipset immediately sends an event message with the next incremented sequence number. after the event message, chipset resumes sending heartbeat messages. note: notes for previous two numbered lists. 1. normally, chipset does not send heartbea t messages while in the g0 state (except in the case of a lockup). however, if a hardware event (or heartbeat) occurs just as the system is transitioning into a g0 state, the hardware continues to send the message even though the system is in a g0 state (and the status bits may indicate this). these messages are sent via the smbus. chipset abides by the smbus rules associated with collision detection. it delays starting a message until the bus is idle, and detects collisions. if a collision is detected chipset waits until the bus is idle, and tries again. 2. warning: it is important the bios clears the second_to_sts bit, as the alerts interfere with the lan device driver from working properly. the alerts reset part of the lan controller and would prevent an operating system?s device driver from sending or receiving some messages. 3. a system that has locked up and can not be restarted with power button press is assumed to have broken hardware (bad power supply, short circuit on some bus, etc.), and is beyond chipset?s recovery mechanisms. 4. a spurious alert could occur in the following sequence: ? the processor has initiated an alert using the send_now bit ? during the alert, the thrm#, intruder# or gpio11 changes state ? the system then goes to a non-s0 state. once the system transitions to the non-s0 state, it may send a single alert with an incremental sequence number. 5. an inaccurate alert message can be generated in the following scenario ? the system successfully boots after a second watchdog timeout occurs. ? pwrok goes low (typically due to a reset button press) or a power button override occurs (before the second_to_sts bit is cleared). www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 165 functional description ? an alert message indicating that the processor is missing or locked up is generated with a new sequence number. ta b l e 5 - 6 8 shows the data included in the alert on lan messages. 5.16 sata host controller (d31:f2) the sata function in chipset has dual modes of operation to support different operating system conditions. in the case of native ide enabled operating systems, chipset unitize single controllers to enable two ports of the bus. the map register, section 15.1.33 , provides the ability to share pci functions. when sharing is enabled, all decode of i/o is do ne through the sata registers. device 31, function 1 (ide controller) is hidden by software writing to the function disable register (d31, f0, offset f2h, bit 1), and its configuration registers are not used. chipset sata controller features two 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. chipset sata controller interacts with an attached mass storage device through a register interface that is equivalent to that presented by a traditional ide host adapter. the host software follows existing standards and conventions when accessing the register interface and follows standard command protocol conventions. table 5-68.heartbeat message data field comment cover tamper status 1 = this bit is set if th e intruder detect bit is set (intrd_det). temp event status 1 = this bit is set if chipset therm# input signal is asserted. processor missing event status 1 = this bit is set if the processor failed to fetch it s first instruction. tco timer event status 1 = this bit is set when the tco timer expires. software event status 1 = this bit is set when software writes a 1 to the send_now bit. unprogrammed firmware hub event status 1 = first bios fetch returned a va lue of ffh, indicating that the firmware hub has not yet been programmed (still erased). gpio status 1 = this bit is set when gpio11 signal is high. 0 = this bit is cleared when gpio11 signal is low. an event message is triggered on an transition of gpio11. seq[3:0] this is a sequence number. it initially is 0, and increments each time chipset sends a new message. upon reaching 1111, the sequence number rolls over to 0000. msb (seq3) sent first. system power state 00 = g0, 01 = g1, 10 = g2, 11 = pre-boot. msb sent first message1 will be the same as the message1 register. msb sent first. message2 will be the same as the message2 register. msb sent first. wdstatus will be the same as the wdstatus register. msb sent first. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 166 datasheet ta b l e 5 - 6 9 lists chipset sata feature support information. ta b l e 5 - 7 0 contains descriptions for the sata features listed in ta b l e 5 - 6 9 . note: sata interface transfer rates are independen t of udma mode settings. sata interface transfer rates will operate at the bus?s ma ximum speed, regardless of the udma mode reported by the sata device or the system bios. table 5-69.sata features support in chipset feature chipset (ahci disabled) chipset (ahci 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 initiated power management n/a supported (netbook only) staggered spin-up supported supported command completion coalescing n/a n/a port multiplier n/a n/a external sata n/a n/a table 5-70.sata feature description feature description native command queuing (ncq) allows the device to reorde r commands for more efficient data transfers auto activate for dma collapses a dma se tup then dma activate sequence into a dma setup only hot plug support allows for device dete ction 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 after 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 re quires attention host initiated power management capability for the host contro ller to request partial and slumber interface power states www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 167 functional description 5.16.1 theory of operation 5.16.1.1 standard ata emulation chipset contains a set of registers that shadow the contents of the legacy ide registers. the behavior of the command and contro l block registers, pio, and dma data transfers, resets, and interrupts are all emulated. note: chipset 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 comple tes 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.1.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 readin g 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 so ftware sets bit 7 of the control register before performing a read, the first item written will be returned from the fifo. staggered spin-up enables the host the ability to spin up hard drives sequentially to prevent power load problems on boot command completion coalescing reduces interrupt and completi on overhead by allowing a specified number of commands to complete and then generating an interrupt to process the commands port multiplier a mechanism for one active host connection to communicate with multiple devices external sata technology that allows for an outside the box connection of up to 2 meters (when using the cable defined in sata-io) table 5-70.sata feature description www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 168 datasheet 5.16.2 sata swap bay support dynamic hot-plug (e.g., surprise removal) is not supported by the sata host controller without special support from ahci and the proper board hardware. however, chipset does provide 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 bo ard hardware (implementation specific), bios, and operating system support. 5.16.3 power management operation power management of chipset sata controller and ports will cover operations of the host controller and the sata wire. 5.16.3.1 power state mappings the d0 pci power management state for device is supported by chipset 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 standby immediate 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, sata defines three phy layer power states, which have 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 169 functional description 5.16.3.2 power state transitions 5.16.3.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 on line. similarly, the sata device must perform the same action. 5.16.3.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.3.2.3 host controller d3 hot state after the interface and device have been pu t 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 management. 1. when the power state is d3, only accesses to configuration space are allowed. any attempt to access the memory or i/o spaces will result in master abort. figure 5-13. sata power states intel ? ich sata controller = d0 device = d3 power res ume 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) www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 170 datasheet 2. when the power state is d3, no interrupt s 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 a ssumed that software has properly shut down the device and disabled the ports. therefore, there is no need to sustain any values 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.3.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). 5.16.3.3 smi trapping (apm) device 31:function2:offset c0h (see section 15.1.40 ) 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). 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 sata co ntroller, and for an smi# to be generated. 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 15.1.41 ) are updated indicating that a trap occurred. 5.16.4 sata led the sataled# output is driven whenever the bsy bit is set in any sata port. the sataled# is an active-low open-collector output. when sataled# is low, the led should be active. when sataled# is high, the led should be inactive. 5.16.5 ahci operation chipset provides hardware support for adva nced host controller interface (ahci), a programming interface for sata host controlle rs developed thru a joint industry effort. ahci defines transactions between the sata controller and software and enables advanced performance and usability with sa ta. 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 171 functional description chipset supports all of the mandatory features of the serial ata advanced host controller interface specification , revision 1.0 and many optional features, such as hardware assisted native command queuing, aggressive power management, led indicator support, and hot-plug thru the us e of interlock switch support (additional platform hardware and software may be re quired depending upon the implementation). note: for reliable device removal notification wh ile in ahci operation without the use of interlock switches (surprise removal), interf ace power management should be disabled for the associated port. see section 7.3.1 of the ahci specification for more information. note: when there are more than two prd entries for a pio data transfer that spans multiple data fises, chipset does not support interm ediate prd entries that are less than 144 words in size when chipset is oper ating in ahci mode at 1.5 gb/s. 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. chipset provides three timers. the three ti mers are implemented as a single counter each with its own comparator and value 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 implemen ted 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 over any 1 ms peri od to within 0.05% of the time specified in the timer resolution fields. 2. within any 100 microsecond 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). www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 172 datasheet the main counter is clocked by the 14.31818 mhz clock, synchronized into the 66.666 mhz domain. this results in a non-uniform du ty cycle on the synchronized clock, but does have the correct average period. the accuracy of the main counter is as accurate as the 14.3818 mhz clock. 5.17.2 interrupt mapping mapping option #1 (legacy replacement option) in this case, the legacy replacement rout bit (leg_rt_cnf) is set. this forces the mapping found in ta b l e 5 - 7 1 . 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 supported interru pt values are irq 20, 21, 22, and 23. 5.17.3 periodic vs. no n-periodic modes non-periodic mode timer 0 is configurable to 32 (default) or 64-bit mode, whereas timers 1 and 2 only support 32-bit mode (see section 20.1.5 ). all three 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. table 5-71.legacy replacement routing timer 8259 mapping apic mapping comment 0 irq0 irq2 in this case, the 8254 timer will not cause any interrupts 1 irq8 irq8 in this case, the rtc will not cause any interrupts. 2 per irq routing field. per irq routing field www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 173 functional description 4. software writes the new value in the timer0_comparator_val register 5. software sets the enable_cnf bit to enable interrupts. 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. 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 shou ld 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.10 for information regarding the polarity programmin g of the i/o apic for detecting internal interrupts. if the interrupts are mapped to the i/o apic and set for level-triggered mode, they can be shared with pci interrupts. this 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-triggered 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. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 174 datasheet if a timer has been configured to level-tr iggered 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. 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 proc essor reads the 64-bit register using two separate 32-bit reads. the danger is that ju st 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 time r to behave as a 32-bit timer. the upper 32-bits are always 0. 5.18 usb uhci host controllers (d29:f0, f1, f2, and f3) chipset contains four usb 2.0 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 eight usb ports. ? overcurrent detection on all eight usb ports is supported. the overcurrent inputs are not 5 v tolerant, and can be used as gpis if not needed. ? chipset?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. 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 commu nicate control, status, and data between software and chipset. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 175 functional description 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 chipset communicate via the schedule data structures. 5.18.3 data encoding and bit stuffing chipset 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 densit y. 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 synchroniz ation mechanism and is not shown in the following packet diagrams. the last two bits in the sync field are a marker that is used to identify the first bit of the pid. all subs equent bits in the packet must be indexed from this point. 5.18.4.3 packet field formats all packets have distinct start and end of pa cket delimiters. full details are given in the universal serial bus specif ication, revision 2.0, in section 8.3.1. 5.18.4.4 address fields function endpoints are addressed using th e 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 frame basis. the frame number field rolls over upon reaching its maximum value of 7ffh, and is sent only for sof tokens at the start of each frame. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 176 datasheet 5.18.4.6 data field the data field may range from 0 to 1023 by tes 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. 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 re sulting from an chipset operation error. all transaction-based sources can be masked by software through chipset?s interrupt enable register. additionally, individual tran sfer descriptors can be marked to generate an interrupt on completion. when chipset drives an interrupt for usb, 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 transactio n-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 in dex -1) when it is servicing an interrupt. crc error / time-out a crc/time-out error occurs when a packet transmitted from chipset to a usb device or a packet transmitted from a usb device to chipset generates a crc error. chipset is informed of this event by a time-out from the usb device or by chipset?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 field decrements to 0, the following occurs: ? the active bit in the td is cleared www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 177 functional description ? 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 interru pt 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 sign aled 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 transactio n 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 re gister (bit 2 of i/o offset 04h) is set, a hardware interrupt is signaled to the syst em. the usb interrupt bit in the hc status register is set either when the td complete s successfully or because of errors. if the completion is because of errors, the usb error bit in the hc status register is also set. 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. reception 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 regi ster at the end of the frame in which this event occurs. this feature streamlines the proc essing 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 syst em at the end of the frame where the event occurred. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 178 datasheet 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 se t to 1 at the end of the frame. a hardware interrupt is signaled to the system. if an eof babble was caused by chipset (due to incorrect schedule for instance), chipset forces a bit stuff error followed by an eop and the start of the next frame. stalled this event indicates that a device/endpo int 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 generally be caused by chipset not being able to access required data buffers in me mory 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 re gister 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 erro r interrupt bit in the hc status register is set to 1 at the end of the frame and a hard ware interrupt is signaled to the system. 5.18.6.2 non-transaction based interrupts if an chipset process error or system error occur, chipset halts and immediately issues a hardware interrupt to the system. resume received this event indicates that chipset received a resume 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 179 functional description chipset 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 th rough the interrupt enable register. host system error chipset sets this bit to 1 when a parity error, master abort, or target abort occur. when this error occurs, chipset 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 susp ended state and its power can be removed. this requires that certain bits of informatio n are retained in the resume power plane of chipset 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 chipset enters the s3, s4, or s5 states. when chipset detects a resume event on any of its ports, it sets the corresponding usb_sts bit in acpi space. if usb is en abled as a wake/break event, the system wakes up and an sci generated. 5.18.8 usb legacy keyboard operation when a usb keyboard is plugged into the sy stem, and a standard ke yboard is not, the system may not boot, and ms-dos legacy so ftware will not run, because the keyboard will not be identified. chipset 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. table 5-72.bits maintain ed in low power states register offset bit description 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 www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 180 datasheet 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-14 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 sm i. 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. this method is used on mpiix and has been validated. the logic also needs to block the accesses to the 8042. if there is an external 8042, then this is simply accomplished by not activating the 8042 cs. this is simply 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 a dditional term is required for the ?pass- through? case. the state table for the diagram is shown in ta b l e 5 - 7 3 . figure 5-14. usb legacy keyboard flow diagram kbc accesses pci config read, write 60 read clear smi_60_r en_smi_on_60r comb. decoder and same for 60w, 64r, 64w smi or to individual "caused by" "bits" to pirqd# to "caused by" bit and and en_pirqd# usb_irq clear usb_irq en_smi_on_irq s d r s d r www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 181 functional description table 5-73.usb legacy keyboard state transitions (sheet 1 of 2) 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 co nfig register dete rmines if cycle passed through to 8042 and if smi# generated. idle 64h / read n/a idle bit 2 in conf ig register dete rmines if cycle passed through to 8042 and if smi# generated. idle 60h / write don't care idle bit 1 in config register de termines if cycle passed through to 8042 and if smi# generated. idle 60h / read n/a idle bit 0 in conf ig register dete rmines 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 register. no smi# generated. pstate rema ins 1. if data value is not dfh or ddh then the 8042 may 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. pstate 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 / read n/a idle this is an invalid sequence. bit 0 in config register determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in config regist er is set, then smi# should be generated. gatestate1 64h / read n/a gatestate1 just stay in same state. generate an smi# if enabled in bit 2 of config register. pstate 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 imprope r end of sequence. bit 3 in config register determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in config regist er is set, then smi# should be generated. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 182 datasheet 5.19 usb ehci host controller (d29:f7) chipset contains an enhanced host controller interface (ehci) host controller which supports up to eight usb 2.0 high-speed root ports. usb 2.0 allows data transfers up to 480 mb/s using the same pins as the eight usb full-speed/low-speed ports. chipset contains port-routing logic that determines whether a usb port is controlled by one of the uhci controllers or by the ehci controller. usb 2.0 based debug port is also implemented in chipset. a summary of the key architectural differen ces between the usb uhci host controllers and the ehci host controller are shown in ta b l e 5 - 7 4 . 5.19.1 ehc initialization the following descriptions step through the expected chipset enhanced host controller (ehc) initialization sequence in chronologica l order, beginning with a complete power cycle in which the suspend well and core well have been off. gatestate2 64h / read n/a gates tate2 just stay in same state. generate an smi# if enabled in bit 2 of config register. pstate remains 1. gatestate2 60h / write xxh idle improper end of sequence. bit 1 in config register 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. gatestate2 60h / read n/a idle improper end of sequence. bit 0 in config register 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. table 5-73.usb legacy keyboard state transitions (sheet 2 of 2) current state action data value next state comment table 5-74.uhci vs. ehci parameter usb uhci usb ehci accessible by i/o space memory space memory data structure single linked list se parated in to periodic and asynchronous lists differential signaling voltage 3.3 v 400 mv ports per controller 2 8 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 183 functional description 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 repr esentative for additional chipset 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. 5.19.1.3 ehc resets in addition to the standard chipset hardware resets, portions of the ehc are reset by the hcreset bit and the transition from the 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 structur es 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 chipset 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 5.19.10 ), 2. the periodic dma engine, and 3. the asynchronous dma engine. chipset always performs any currently-pending debug port transaction at the beginning of a microframe, followed by any pending 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 d3 hot (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. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 184 datasheet 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 (port #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. 5.19.5 packet formats see chapter 8 of the universal serial bus specification, revision 2.0 . chipset ehci allows entrance to usb te st modes, as defined in the usb 2.0 specification, including test j, test packet, etc. however, note that chipset test packet test mode interpacket gap timing ma y 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 interru pts and the error conditions that cause them. all error conditions that the eh c detects can be reported through the ehci interrupt status bits. only chipset-specific interrupt and error-reporting behavior is documented in this section. the ehci interru pts section must be read first, followed by this section of the datasheet to fully comp rehend the ehc interrupt and error-reporting functionality. ? based on the ehc?s buffer sizes and buffe r management policies, the data buffer error can not occur on chipset. ? master abort and target abort responses fr om hub interface on ehc-initiated read packets will be treated as fatal host errors. the ehc halts when these conditions are encountered. ? chipset 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 writ e 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 chipset supports the 1024-element frame list size, the frame list rollover interrupt occurs every 1024 milliseconds. ? chipset delivers interrupts using pirqh#. ? chipset 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 peri odic list, the ?missed microframe? bit does not get set on a control-structure-fetch that fails the late-start test. if subsequent www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 185 functional description 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, th e 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 en able), 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. 5.19.7 usb 2.0 power management 5.19.7.1 pause feature this feature allows platforms (especially netbook 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 chipset netbook only. the policies for ente ring these states typically are based on the recent history of system bus activi ty to incrementally enter deeper power management 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 stat e 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. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 186 datasheet 5.19.7.3 acpi device states the usb 2.0 function only supports the d0 and d3 pci power management states. notes regarding chipset implemen tation 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 me mory-mapped i/o range 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 not assert for any reason. the internal pme# signal is used to signal wake events, etc. 5. when the device power state field is wri tten to d0 from d3, an internal reset is generated. see section ehc resets for gene ral rules on the effects of this reset. 6. attempts to write any other 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. 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 system 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 hot state (48 mhz clock stops), or the s3 cold /s4/s5 states (core power turns off). ? all core well logic is reset in the s3/s4/s5 states. 5.19.7.5 netbook only considerations chipset usb 2.0 implementation does no t behave differently in the netbook configurations versus the nettop configurations. however, some features may be especially useful for the netbook configurations. ? if a system (e.g., netbook) does not im plement all eight usb 2.0 ports, chipset provides mechanisms for changing the structural parameters of the ehc and hiding unused uhci controllers. see chipset bios specification for information on how bios should configure chipset. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 187 functional description ? netbook systems may want to minimize the conditions that will wake the system. chipset implements the ?wake enable? bits in the port status and control registers, as specified in the ehci spec, for this purpose. ? netbook systems may want to cut suspend well power to some or all usb ports when in a low-power state. chipset implements the optional port wake capability register 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 controller shares the eight usb ports with four uhci host controllers in chipset. 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; and the uhc at d29:f3 shares ports 6 and 7 with the ehc. there is very little interaction between the enhanced and the uhci controllers other than the muxing control which is provided as part of the ehc. figure 5-15 shows the usb port connections at a conceptual level. 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 . chipset 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 the ehci software drivers are not present 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. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 188 datasheet note that the port-routing logic is the only block of logic within chipset 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/demultiplexed between the uhci and ehci host controllers. the other usb functional signals are handled as follows: ? the overcurrent inputs (oc[7:0]#) are di rectly routed to both controllers. an overcurrent event is recorded in both controllers? status registers. 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. chipset also allows the usb debug port traffic to be routed in and out of port #0. when in this mode, the enhanced host controller is the owner of port #0. 5.19.8.2 device connects the enhanced host controller interface spec ification 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 figure 5-15. chipset-usb port connections uhci #3 (d29:f3) uchi #0 (d29:f0) uhci #1 (d29:f1) uhci #2 (d29:f2) enhanced host controller logic debug port port 7 port 3 port 4 port 5 port 6 port 2 port 1 port 0 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 189 functional description ? in this case, the uhc is the owner of th e port both before and after the connect occurs. the ehc (except for the port-routing logic) does not see 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 th e port both before and after the connect occurs. the ehc (except for the port-routing logic) not see the connect occur. the uhci driver handles the connection an d initialization process. since the uhc does not perform the high-speed chirp handshake, 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 pe rforms the port reset. after the 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 uh c to see a connect event and the ehc to see an ?electrical? disconnect event. th e 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 hardware has set the port enable bit in the ehc?s portsc register. the port is functional at this point. the uhc continues to see an unconnected port. 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) not see 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 does not see a device attached. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 190 datasheet 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 chipset 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. 5.19.10 usb 2.0 based debug port chipset 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 on chipset systems (e.g., the dpd cannot be connected to port #0 thru 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: reset event effect on configur e 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) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 191 functional description ? 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 disa bled state from the viewpoint of a standard host controller driver. in mode 1, the debug port 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. ta b l e 5 - 7 5 shows the debug port behavior relate d to the state of bits in the debug registers as well as bits in the associated port status and control register. table 5-75.debug port behavior (sheet 1 of 2) owner_cnt enabled_ct port enable run / stop suspend debug port behavior 0 x x x x debug port is not being used. normal operation. 1 0 x x x debug port is not being used. normal operation. 1 1 0 0 x debug port in mode 1. sync keepalives sent plus debug traffic www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 192 datasheet 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. software sets the appropriate values in the following 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) 2. the debug port controller sends a token packet consisting of: ?sync ? token_pid_cnt field 1 1 0 1 x 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. 1 1 1 0 0 invalid. host controller driver should not put the controller into this state (enabled, not running and not suspended). 1 1 1 0 1 port is suspended. no debug traffic sent. 1 1 1 1 0 debug port in mode 2. debug traffic is interspersed with normal traffic. 1 1 1 1 1 port is suspended. no debug traffic sent. table 5-75.debug port behavior (sheet 2 of 2) owner_cnt enabled_ct port enable run / stop suspend debug port behavior www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 193 functional description ? 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 receiv ed, 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) www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 194 datasheet ? go_cnt (note: this will always be 1 to initiate the transaction) 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 waits for a response from the debug device. if a response is received: ? the received pid is placed in to 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 valid packet was received from the devi ce 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 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 195 functional description debug software can determine the current ?ini tialized? 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. ot herwise the ehci should not be considered initialized. debug software will initialize th e debug port registers depending on the state 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 us b root port has been designated as the debug port by examining bits 20:23 of the ehci host controller structural parameters register. this 4-bit field represents the numeric value assigned to the debug port (i.e., 0001=port 0). 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 ap propriate (see determining the debug port) portsc register is set. if the current co nnect 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 register. to ensure a successful reset, debug software should wait at least 50 ms before clearing the port reset bit. due to possible delays, this bit may not change to 0 immediately; reset is complete when this bi t reads as 0. software must not continue until this bit reads 0. if a high-speed device is attached, the eh ci 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/disabl ed bit in the portsc 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 www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 196 datasheet 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.20 smbus controller (d31:f3) chipset 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 processor to initiate communications with smbus peripherals (slaves). chipset is also capable of operating in a mode in which it can communicate with i 2 c compatible devices. chipset can perform smbus messages with eith er packet error checking (pec) enabled or disabled. the actual pec calculation and checking is performed in hardware by chipset. the slave interface allows an external master to read from or write to chipset. write 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. chipset?s internal host controller cannot access chipset?s internal slave interface. chipset 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. chipset 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, ex cept for the new host notify command (which is actually a received message). the programming model of the host controlle r is combined into two portions: a pci configuration portion, and a system i/o mappe d 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. chipset 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. 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 197 functional description the host controller supports 8 command protocols of the smbus interface (see system management bus (smbus) specification, version 2.0 ): quick command, send byte, receive byte, write 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 so ftware sets the start bit, the smbus host controller performs the requested transa ction, 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 re gisters? (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 (i ndicating 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 contro ller updates all registers while completing the new command. using the smb host controller to send commands to chipset?s smb slave port is supported. chipset 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 sh ould not be tied together externally. 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. wh ile the command is in operation, the host_busy bit is set. if th e 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. quick command when programmed for a quick command, the transmit slave address register is sent. the pec byte is not 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. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 198 datasheet 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. so ftware 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 write word command. software must force the i2c_en bit to 0 when running this comm and. 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 th an writing data. first chipset 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 registers are sent. data is received into the data0 on the read byte, and the dat0 and data1 registers on th e 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 write word followed by a read word, but without a second command or stop condition. when programmed for the process call comma nd, chipset transmits the transmit slave address, host command, data0 and data1 regist ers. 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 register (smb i/o register, offset 04h) needs to be 0. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 199 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/write chipset 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 chipset, the interrupt is generated only after a transmission or recept ion of 32 bytes, or when the entire byte count has been transmitted/received. the byte count field is transmitted but ignored by chipset 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 addre ss and a write condition. after the command code chipset issues a byte count describin g how many more bytes will follow in the message. if a slave had 20 bytes to send, th e 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 value stored in the data0 register. 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, version 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. chipset will still send the number of bytes (on writes) or receive the number of bytes (on reads) indicated in the data0 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). i 2 c read this command allows chipset to perform block reads to certain i 2 c devices, such as serial e 2 proms. the smbus block read supports the 7-bit addressing mode only. however, this does not allow access to devices using the i 2 c ?combined format? that has data bytes after the address. typically these data bytes correspond to an offset (address) within the serial memory chips. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 200 datasheet note: this command is supported independent of the setting of the i2c_en bit. the i 2 c 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 i 2 c read command, the value written into bit 0 of the transmit slave address register (smb i/o register, offset 04h) needs to be 0. the format that is used for the command is shown in ta b l e 5 - 7 6 . chipset 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 re ad 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. table 5-76.i 2 c 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 201 functional description the combined data payload must not exceed 32 bytes. the byte leng th 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 pe c byte. the pec is computed on the total message beginning with the first slav e address and using the normal pec computational rules. it is highly recommende d that a pec byte be used with the block write-block read process call. software mu st do a read to the command register (offset 2h) to reset the 32 byte buffer pointe r prior to reading the block data register. 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 condit ion. chipset continuously monitors the smbdata line. when chipset is attempting to drive the bus to a 1 by letting go of the smbdata line, and it samples smbdata low, th en some other master is driving the bus and chipset will stop transferring data. if chipset sees that it has lost arbitration, the condition is called a collision. chipset will set the bus_err bit in the host status regist er, and if enabled, generate an interrupt or smi#. the processor is responsible for restarting the transaction. when chipset is a smbus master, it drives the clock. when chipset 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. chipset will also provide minimum time between smbus transactions as a master. note: chipset supports the same arbitration protocol for both the smbus and the system management (smlink) interfaces. www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 202 datasheet 5.20.3 bus timing 5.20.3.1 clock stretching some devices may not be able to handle thei r clock toggling at the rate that chipset as an smbus master would like. they have the ca pability of stretching the low time of the clock. when chipset attempts to release the clock (allowing the clock to go high), the clock will remain low for an extended period of time. chipset 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. simila rly, 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 (chipset 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. chipset will discard the cycl e and set the dev_err bit. the time out minimum is 25 ms (800 rtc clocks). the time-out counter inside chipset will start after the last bit of data is transferred by chipset and it is waiting for a response. the 25 ms timeout counter will not co unt 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). 5.20.4 interrupts / smi# chipset smbus controller uses pirqb# as it s 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). ta b l e 5 - 7 8 and ta b l e 5 - 7 9 specify how the various enable bits in the smbus function control the generation of the interrupt, host and slave 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 203 functional description table 5-77.enable for smbalert# event intren (host control i/o register, offset 02h, bit 0) smb_smi_en (host configuration register, 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 register, bit 5) xx xwake generated x1 0slave smi# generated (smbus_smi_sts) 1 0 0 interrupt generated table 5-78.enables for smbus slave write and smbus host events event intren (host control i/o register, offset 02h, bit 0) smb_smi_en (host configuration register, d31:f3:offset 40h, bit1) event slave write to wake/smi# command x x wake generated when asleep. slave smi# generated when awake (smbus_smi_sts). slave write to smlink_slave_s mi command x x slave smi# generated when in the s0 state (smbus_smi_sts) any combination of host status register [4:1] asserted 0xnone 1 0 interrupt generated 11host smi# generated table 5-79.enables for the host notify command host_notify_intre n (slave control i/o register, offset 11h, bit 0) smb_smi_en (host config register, d31:f3:off40h, bit 1) host_notify_wken (slave control i/o register, offset 11h, bit 1) result 0x0none xx1wake generated 1 0 x interrupt generated 11xslave smi# generated (smbus_smi_sts) www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 204 datasheet 5.20.5 smbalert# smbalert# is multiplexed with gpio11. wh en enable and the signal is asserted, chipset can generate an interrupt, an smi#, or a wake event from s1 ? s5. note: any event on smbalert# (regardless whether it is programmed as a gpi or not), causes the event message to be sent in heartbeat mode. 5.20.6 smbus crc gene ration and checking if the aac bit is set in the auxiliary contro l register, chipset automatically calculates and drives crc at the end of the transmitte d packet 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 re gister 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 chipset?s smbus slave interface is accessed via the smbus. the sm bus slave logic will not generate or handle receiving the pec by te and will only act as a legacy alerting protocol device. the slave interface allows chipset to decode cycles, and allows an external microcontroller to perform specif ic 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 th e address that chipset 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 microcontrolle r can read to get the state of chipset. ? status bits to indicate that the smbus sl ave 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.13 ) for all others www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 205 functional description note: the external microcontroller should not attempt to access chipset?s smbus slave logic until either: ? 800 milliseconds after both: rtest# is high and rsmrst# is high, or ? the pltrst# de-asserts the 800 ms case is based on the scenario where the rtc battery is dead or missing such that the rtc power well comes up simult aneously with suspend well. in this case, the rtc clock may take a while to stabilize. chipset uses the rtc clock to extend the internal rsmrst# by ~100 ms. therefore, if th e clock is slow to toggle, this time could be extended. 800 ms is assumed to be sufficient guardband for this. 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, chipset 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 a ccommodate the least significant bit used for read/write control. for example, if chipset slave address (rcv_slva) is left at 44h (default), the external micro controller woul d use an address of 88h/89h (write/read). 5.20.7.1 format of slave write cycle the external master performs byte write commands to chipset 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. note: if chipset is sent a ?hard reset without cy cling? command on smbus while the system is in s4 or s5, the reset command will no t be executed until the next wake event. smbus write commands sent after the hard reset without cycling command and before the wake event will be naked by chip set. this also applies to any smbus wake commands sent after a hard reset without cycling command, such that the smbus wake command will not cause the system to wa ke. any smbus read that is accepted by chipset will complete normally. ta b l e 5 - 8 0 has the values associated with the registers. table 5-80.slave write registers register function 0command register. see ta b l e 5 - 8 1 below for legal values written to this register. 1?3 reserved 4 data message byte 0 5 data message byte 1 6?7 reserved 8 reserved 9?ffh reserved www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 206 datasheet note: the external microcontroller is responsible to make sure that it does not update the contents of the data byte regi sters until they have been read by the system processor. chipset overwrites the old value with any new value received. a race condition is possible where the new value is being written to the re gister just at the ti me it is being read. chipset will not attempt to cover this race condition (i.e., unpredictable results in this case). table 5-81.command types command type description 0 reserved 1 wake/smi#. this command wakes the system if it is not already awake. if system is already awake, an smi# is generated. note: the smb_wak_sts bit will be set by this command, even if the system is already awake. the smi handler should then clear this bit. 2 unconditional powerdown. this command sets the pwrbtnor_sts bit, and has the same effect as the po werbutton override occurring. 3 hard 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. 4 hard reset system. this command causes a hard reset of the system (including cycling of the power supply). th is is equivalent to a write to the cf9h register with bits 3:1 set to 1. 5 disable the tco messages. this command will disa ble chipset from sending heartbeat and event mess ages (as described in section 5.15.2 ). once this command has been executed, heartbeat an d event message reporting can only be re-enabled by assertion and deas sertion of the rsmrst# signal. 6 wd reload: reload watchdog timer. 7 reserved 8 smlink_slv_smi. when chipset detects this co mmand type while in the s0 state, it sets the smli nk_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, chipset acknowledge s 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 smlink_slv_smi command is received. in this case, the smlink_slv_smi_sts bit may get set but no t serviced before th e system goes to sleep. once the system returns to s0, the smi associated with this bit would then be generated. software must be able to handle this scenario. 9?ffh reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 207 functional description 5.20.7.2 format of read command the external master performs byte read commands to chipset smbus slave i/f. 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 ta b l e 5 - 8 2 shows the read cycle format. ta b l e 5 - 8 3 shows the register mapping for the data byte. table 5-82.read cycle format bit description driven by comment 1 start external microcontroller 8:2 slave address - 7 bits external microcontroller must match value in receive slave address register 9 write external microcontroller always 0 10 ack chipset 18:11 command code - 8 bits external microcontroller indicat es which register is being accessed see ta b l e 5 - 8 3 19 ack chipset 20 repeated start exter nal microcontroller 27:21 slave address - 7 bits external microcontroller must match value in receive slave address register 28 read external microcontroller always 1 29 ack chipset 37:30 data byte chipset value depends on register being accessed. see ta b l e 5 - 8 3 38 not ack external microcontroller 39 stop external microcontroller table 5-83.data values fo r slave read registers register bits description 07:0 reserved 1 2:0 system power state 000 = s0 001 = s1 010 = reserved 011 = s3 100 = s4 101 = s5 110 = reserved 111 = reserved 17:3 reserved 2 3:0 frequency strap register 27:4 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 208 datasheet 3 5:0 watchdog timer current value 37:6 reserved 4 0 1 = the intruder detect (intrd_det) bit is set. this indicates that the system cover has probably been opened. 4 1 1 = bti temperature event occurred. this bit will be set if chipset?s thrm# input signal is active. need to take after polarity control. 4 2 boot-status. this bit will be 1 when the processor does not fetch the first instruction. 4 3 this bit will be set after the tco timer times out a second time (both timeout and second_to_sts bits set). 46:4 reserved 4 7 the bit will reflect the state of the gpi11/smbalert# signal, and will depend on the gp_inv11 bit. it does not matter if the pin is configured as gpi11 or smbalert#. ? if the gp_inv11 bit is 1, the va lue of register 4 bit 7 will equal the level of the gpi11/smbalert# pin (high = 1, low = 0). ? if the gp_inv11 bit is 0, the va lue of register 4 bit 7 will equal the inverse of the level of the gpi11/smbalert# pin (high = 1, low = 0). 5 0 unprogrammed flash bios bit. this bit will be 1 to indicate that the first bios fetch returned ffh, that indicates that the flash bios is probably blank. 5 1 battery low status (netbook only). 1 if batlow# is ?0? 5 2 processor power failure status. 1 if the cpupwr_flr bit in the gen_pmcon_2 register is set. 5 3 init# due to receiving shutdown message. this event is visible from the reception of the shutdown message until a platform reset is done. events on signal will not create an event message. 5 4 lt range: lt reset indication. even ts on signal will not create an event message. 5 5 power_ok_bad: indicates the failure core power well ramp during boot/resume. this bit will be active if the slp_s3# pin is de- asserted and pwrok pi n is not asserted. 5 6 thermal trip: this bit will shadow the state of cpu thermal trip status bit (cts). events on signal will not create an event message. 57 reserved 6 7:0 contents of the message 1 register. 7 7:0 contents of the message 2 register. 8 7:0 contents of the wdstatus register. table 5-83.data values fo r slave read registers register bits description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 209 functional description 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 chipset 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 ? read occurs (which is invalid for smbus read or write protocol), and the address matches chipset? s slave address, chipset 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 chipset?s receive slave address, it will assume that th e protocol is followed, ignore bit 28, and proceed with the slave read cycle. note: an external microcontroller must not attempt to access chipset?s smbus slave logic until at least 1 second after both rtcrst# and rsmrst# are deasserted (high). 5.20.7.3 format of host notify command chipset 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 chipset 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. ta b l e 5 - 8 4 shows the host notify format. table 5-84.host notify format (sheet 1 of 2) 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) chipset chipset 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 device address register 18 unused ? always 0 external master 7-bit-only address; this bit is inserted to complete the byte www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 210 datasheet 5.21 intel hd audio overview chipset?s 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 enco ded data between system memory and an external codec(s). chipset implements four output dma engines and 4 input dma engines. the output dma engines move digi tal data from system memory to a d-a converter in a codec. chipset implements a single serial data output signal (hda_sdout) that is connected to all exte rnal codecs. the input dma engines move digital data from the a-d converter in the codec to system memory. chipset implements three serial digital input sign als (hda_sdi[2:0]) supporting up to three 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 ou tput dma engines is then combined and serially sent to the external codecs over th e intel high definition audio link. the input dma engines receive data from the codecs over 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 tran sported to and from the codecs via dma engines. 19 ack chipset 27:20 data byte low ? 8 bits external master loaded into the notify data low byte register 28 ack chipset 36:29 data byte high ? 8 bits external master loaded into the notify data high byte register 37 ack chipset 38 stop external master table 5-84.host notify format (sheet 2 of 2) bit description driven by comment www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 211 functional description 5.22 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 (c lk), master data out (master out slave in (mosi)), master data in (master in slave out (miso)) and an active low chip select (cs#). communication on the spi bus is done with a master ? slave protocol. the typical bus topology consists of a single spi master wi th a single spi slave (flash device). the slave is connected to chipset and is implemented as a tri-state bus. note: when spi is selected by the boot bios dest ination strap and a spi device is detected by chipset, lpc based bios flash is disabled. 5.22.1 flash device configurations chipset spi flash may be used in two configurations. ta b l e 5 - 8 5 focuses on these various configurations involving chipset. note: chipset spi interface supports a single chip select pin for a single spi device. 5.22.2 spi device compatibility requirements a variety of spi flash devices exist in the market. in order for a spi device to be compatible with chipset it must meet the minimum requirements detailed in the following sections. 5.22.2.1 chipset spi based bios on ly configuration requirements a spi flash device must meet the following minimum requirements to be compatible with chipset in a non-shared flash configuration: ? erase size capability of at least one of the following: 64 kb, 32 kb, 4 kb, 2 kb, 512 bytes, or 256 bytes. ? required command set and associated opcodes (refer to section 5.22.3.1 ). ? device identification command (refer to section 5.22.3.2 ). ? device must support multiple writes to a page without requiring a preceding erase cycle (refer to section 5.22.4 ) table 5-85.spi implementation options configuration system bios location system bios and intel amt shared flash fwh present number of spi device(s) 1fwhnoyes0 2 spi no no 1 www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 212 datasheet ? serial flash device must ignore the upper address bits such that an address of ffffffh simply 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, the device must complete the cycle gracefully without any impact on the flash content. ? an erase command (page, sector, block, chip, or etc.) must set to 1 (ffh) all bits inside the designated area (page, sector, block, chip, or etc.). ? minimum density of 4 mb (platform dependent based on size of bios). note: chipset only supports mode 0 on spi flash devices 5.22.3 chipset compat ible command set 5.22.3.1 required command set for inter operability ta b l e 5 - 8 6 contains a list of commands and the associated opcodes that a spi based serial flash device must support in order to be interoperable with the serial flash interface. 5.22.3.2 recommended standard commands the following table contains a list of standard commands that a spi device should support to be compatible with chipset. th is list only contains standard commands and is not meant to be an all inclusive list of commands that spi devices can support. table 5-86.required commands and opcodes commands opcode program data 02h read data 03h read status 05h table 5-87.chipset standard spi commands commands opcode notes write status 01h if command is supported by a device, 01h must be supported. write disable 04h write enable 06h if command is supported by a device, 06h must be supported. fast read 0bh chipset does not support this command. jedec id 9fh either jedec id (9fh) or an identify device with abh is required, not both. identify device abh either jedec id (9fh) or an identify device with abh is required, not both www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 213 functional description 5.22.4 flash protection there are three types of flash protection mechanisms: 1. bios range write protection 2. smi#-based global write protection the three mechanisms are conceptually or ?d together such that if any of the mechanisms indicate that the access should be blocked, then it is blocked. ta b l e 5 - 8 8 provides a summary of the three mechanisms. a blocked command will appear to software to finish, except that the blocked access status bit is set in this case. 5.22.4.1 bios range write protection chipset 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 th e 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. 5.22.4.2 smi# based global write protection chipset provides a method for blocking writes to the spi flash when the write protect 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 inte ract in the same manner for spi bios as they do for the fwh bios. table 5-88.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 ich components for fwh bios bar reads and writes yes reset override not applicable- specific to flash sharing www.datasheet.co.kr datasheet pdf - http://www..net/
functional description 214 datasheet 5.23 feature capability mechanism a new set of registers have been added into chipset lpc interface (device 31, function 0, offset e0h - ebh) that allows the system software or bios to easily determine the features supported by chipset. these re gisters 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) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 215 ballout definition 6 ballout definition 6.1 chipset ballout, signal, and mechanical document an electronic version of the ballout is available. please look for chipset ballout, signal, and mechanical document on ibl with doc id: 405447 6.2 chipset ballout this section contains chipset ballout information. the ballout is preliminary and subject to change. the figures below are the ballout map of the 360 bga package. figure 6-16 is a ballout list, sorted alphabetically by signal name. www.datasheet.co.kr datasheet pdf - http://www..net/
ballout definition 216 datasheet figure 6-16. chipset ballout (topview?left side) 12345678910111213 avss strap2 # / ad22 --- pa r a d2 4 --- pl ock# --- trdy # --- --- ad10 b a d31 pirqa # pirqc# --- ad23 vss irdy# ad21 ad18 vss serr# --- ad19 c ad30 oc6# / gpio30 oc7# / gpio31 --- oc1# --- ad29 ad27 gpio1 --- ad16 --- c/be2# d--- oc3# oc2# oc0# --- pirqf# / gpio3 pirqb# --- a d2 8 perr# strap0 # --- e --- --- --- --- oc4# oc 5 # / gpio29 --- pirqe# / gpio2 --- ad15 --- ad17 --- f vccsus 3_3 vss --- clk48 v5ref_ sus vccus bpll --- pirqh# / gpio5 --- vcc3_3 --- v5ref --- g--- usbrb i as usbrb i as# vss --- --- --- vss --- vcc3_4 --- ad25 --- hvss usbp1p usbp1n vss vss usbp0p usbp0n pirqg# / gpio4 --- pirqd# --- ad26 --- j--- usbp2n usbp2p --- --- --- --- --- --- vcc1_0 5 --- pcicl k --- k usbp4n usbp4p --- vss usbp3p usbp3n v cc s us 3_3 vss rsvd --- vss --- --- l---usbp5n usbp5p v ss --- --- --- --- --- --- --- ad20 --- m --- --- --- --- usbp6p usbp6n v ss spi_cs# vcc1_5 --- vss --- rsvd n usbp7n usbp7p v ss v cc s us 3_3 --- --- --- --- --- --- --- vss vss p --- --- --- --- gpio14 hda _ bi t_clk lan _ rs tsy nc hda _ sd in2 spi_clk --- vss --- vss r--- spi_mis o gpio24 spi_ar b --- --- --- --- --- vcc3_3 --- rsv d --- t spi_m o si vss --- lan_cl k rtcrst # ee_ dou t lan_tx d1 intrude r# vcc3_3 --- --- --- --- u--- hda _ rs t# ee_ cs lan_t x d2 --- --- --- --- --- pwrok --- rsv d --- vvss hda _ sd in1 ee_shc lk --- rtcx2 lad0 / fwh0 vss vss --- v cc 1 _ 0 5--- rsv d --- w--- hda _ sd in0 lan_t x d0 rtcx1 --- --- --- lad3 / fwh3 - -- rsv d --- vss --- y hda _ s ync vss --- fwh4 /lfram lad2 / fwh2 vccapl l --- ldrq0# --- rsv d --- rsv d --- aa hda _ sd out lan_r x d0 clk14 --- ldrq1# / gpio23 lad1 / fwh1 - - - v cc1_5 - - - rsv d --- rsv d --- ab --- --- --- vss --- vss vss vss --- rsv d rsv d --- rsv d ac gpio34 lan_r x d2 rsmrst # sata _ c lkp --- --- sata0 t xn vss sata1 t xp --- sata r bias --- rsvd ad lan_r x d1 vss intv rm en sata_ c lkn --- sata0 r xp sata0t xp sata1r xp sata1 t xn vss sata r bias# --- vcc3_3 ae vss ee_ din v ccrtc --- --- sata0r xn --- sata1r xn --- vss --- --- vss 12345678910111213 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 217 ballout definition figure 6-17.chipset ballout (topview?right side) 10 13 14 15 16 17 18 19 20 21 22 23 24 25 trdy # a d10 --- --- fra me # --- gnt1# --- req2# --- --- pcirst # gpio12 vss a vss ad19 --- dev se l# vss ad4 ad6 ad7 vss --- ad0 lan_ r st# vss batlo w# b --- c/be2# --- gpio22 --- ad2 ad3 ad5 --- --- pme# gpio13 gpio25 wake # c perr# --- ad9 ad8 --- a d1 gpio26 gpio27 --- suscl k --- --- --- d ad15 --- ad11 --- gnt2# --- vss --- s mba l ert# / pwrbt n# --- smbd ata gpio15 slp_s 4# e vcc3 _ 3 --- stop# --- vss --- vccsu s3_3 --- tp3 slp_s 5# gpio28 --- s mlin k1 smlin k0 f vcc3 _ 4 --- s tra p 1# / --- req1# --- s y s _ r eset# --- --- --- s u s _ s tat# / pl tr s t# vss --- g pirqd# --- ad12 --- c/ be0# --- smbcl k gpio9 slp_s 3# linkal ert# --- ri# dmi_z comp vcc3_ 3 h vcc1 _ 05 --- ad14 --- spkr --- --- --- --- --- dmi_i r comp petn 1 petp 1 - - - j --- --- --- --- --- vcc1 _ 05 gpio8 v ss v ss pern 1 perp 1 --- pern 2 perp 2 k --- --- ad13 --- c/be3# --- --- --- --- --- petn3 pern3 perp4 --- l --- rsvd --- c/be1# --- gpio10 pern2 perp2 vcc1 _ 5 petp3 --- --- --- --- m --- vss vss --- --- --- --- --- --- --- vcc1_ 5 v ss petp 4 petn 4 n --- vss --- v cc 1 _ 05 --- pern4 perp4 vss dmi0tx p dmi0t x n --- --- --- --- p vcc3 _ 3 --- vss --- --- --- --- --- --- --- vss dmi0 r xn dmi0 r xp --- r --- --- --- bmbu s y# / --- nmi dmi2 r xp dmi2 r xn dmi1 r xp dmi1 r xn vss --- dmi1tx n dmi1t x p t pwr o k --- gpio33 --- a20ga te --- --- --- --- --- --- dmi2tx n dmi2tx p --- u vcc1 _ 05 --- rsv d --- vrmp wrgd --- s tp c l k# vss dmi3 r xp dmi3 r xn vss dmi3tx p dmi3tx n vss v rsv d --- gpio7 --- gpio6 --- v_ c p u _io --- --- --- vss dmi_ c l kn dmi_ c l kp --- w rsv d --- rsv d --- s tp_p ci# --- ignne# --- a20m# c pu s l p# ferr# --- vss vccdm ipll y rsv d --- rsv d --- seri r q --- dpslp # --- thrmt rip# smi# --- --- --- --- aa rsvd rsvd --- rsv d rsv d thrm# --- stp _ c pu# dprsl pvr / --- cpupw rgd / dprst p# intr --- ab --- rsvd --- rsv d --- rsv d mch _ s ync# clkru n# --- rcin# --- gpio38 gpio39 init# ac vss vcc3_ 3 --- rsvd rsvd rsvd rsv d rsv d vss init3_3 v# --- gpio36 vss satal ed# ad vss vss --- --- rsvd --- rsv d --- rsv d rsv d --- rsv d rsv d vss ae 10 13 14 15 16 17 18 19 20 21 22 23 24 25 www.datasheet.co.kr datasheet pdf - http://www..net/
ballout definition 218 datasheet table 6-89.chipset ballout by signal name (sheet 1 of 4) signal name ball # signal name ball # signal name ball # a20gate u16 ad27 c8 rsvd ad15 a20m# y20 ad28 d9 rsvd ac17 hda_bit_clk p6 ad29 c7 rsvd ab13 hda_rst# u2 ad30 c1 devsel# b15 hda_sdin0 w2 ad31 b1 tp3 f20 hda_sdin1 v2 lan_rst# b23 rsvd ac13 hda_sdin2 p8 batlow# b25 rsvd ab15 hda_sdout aa1 clk14 aa3 dmi_clkn w23 hda_sync y1 clk48 f4 dmi_clkp w24 ad0 b22 clkrun# ac19 dmi_zcomp h24 ad1 d18 cpupwrgd / gpio49 ab22 dmi_ircomp j22 ad2 c17 cpuslp# y21 dmi0rxn r23 ad3 c18 c/be0# h16 dmi0rxp r24 ad4 b17 c/be1# m15 dmi0txn p21 ad5 c19 c/be2# c13 dmi0txp p20 ad6 b18 c/be3# l16 dmi1rxn t21 ad7 b19 rsvd ab16 dmi1rxp t20 ad8 d16 rsvd ae24 dmi1txn t24 ad9 d15 rsvd ae23 dmi1txp t25 ad10 a13 rsvd aa14 dmi2rxn t19 ad11 e14 rsvd v14 dmi2rxp t18 ad12 h14 rsvd r12 dmi2txn u23 ad13 l14 rsvd ae20 dmi2txp u24 ad14 j14 rsvd w10 dmi3rxn v21 ad15 e10 rsvd v12 dmi3rxp v20 ad16 c11 rsvd ae21 dmi3txn v24 ad17 e12 rsvd ae18 dmi3txp v23 ad18 b9 rsvd ad19 dprslpvr ab20 ad19 b13 rsvd u12 dprstp# ab23 ad20 l12 rsvd ad17 dpslp# aa18 ad21 b8 rsvd ac15 ee_cs u3 ad22 a3 rsvd ad18 ee_din ae2 ad23 b5 rsvd y12 ee_dout t6 ad24 a6 rsvd aa10 ee_shclk v3 ad25 g12 rsvd aa12 ferr# y22 ad26 h12 rsvd y10 frame# a16 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 219 ballout definition gnt1# a18 intvrmen ad3 pern2 m18 gnt2# e16 rsvd y14 perp2 m19 strap0# d11 irdy# b7 petn2 k24 gpio48 / strap1# g14 lad0 / fwh0 v6 petp2 k25 bmbusy# / gpio0 t15 lad1 / fwh1 aa6 pern3 l23 gpio1 c9 lad2 / fwh2 y5 perp3 l24 gpio10 m17 lad3 / fwh3 w8 petn3 l22 gpio12 a24 lan_clk t4 petp3 m21 gpio13 c23 lan_rstsync p7 pern4 p17 gpio14 p5 lan_rxd0 aa2 perp4 p18 gpio15 e24 lan_rxd1 ad1 petn4 n25 strap2# / gpio17 a2 lan_rxd2 ac2 petp4 n24 pirqe# / gpio2 e8 lan_txd0 w3 perr# d10 gpio24 r3 lan_txd1 t7 pirqa# b2 gpio25 c24 lan_txd2 u4 pirqb# d7 gpio26 d19 ldrq0# y8 pirqc# b3 gpio27 d20 ldrq1# / gpio23 aa5 pirqd# h10 gpio28 f22 fwh4/lframe# y4 plock# a8 pirqf# / gpio3 d6 mch_sync# ac18 pltrst# g23 gpio33 u14 rsvd ae16 pme# c22 gpio34 ac1 nmi t17 pwrbtn# e21 gpio36 ad23 oc0# d4 pwrok u10 gpio38 ac23 oc1# c5 rcin# ac21 gpio39 ac24 oc2# d3 rsvd k9 pirqg# / gpio4 h8 oc3# d2 req1# g16 pirqh# / gpio5 f8 oc4# e5 req2# a20 gpio6 w16 oc[5]# / gpio29 e6 rsvd m13 gpio7 w14 oc[6]# / gpio30 c2 gpio22 c15 gpio8 k18 oc[7]# / gpio31 c3 ri# h23 gpio9 h19 par a5 rsmrst# ac3 rsvd ad16 pciclk j12 rtcrst# t5 ignne# y18 pcirst# a23 rtcx1 w4 init# ac25 pern1 k21 rtcx2 v5 init3_3v# ad21 perp1 k22 rsvd ab10 intr ab24 petn1 j23 sata_clkn ad4 intruder# t8 petp1 j24 sata_clkp ac4 table 6-89.chipset ballout by signal name (sheet 2 of 4) signal name ball # signal name ball # signal name ball # www.datasheet.co.kr datasheet pdf - http://www..net/
ballout definition 220 datasheet sata0rxn ae6 susclk d22 v_cpu_io w18 sata0rxp ad6 sys_reset# g18 vcc3_3 t9 sata0txn ac7 thrmtrip# aa20 vcc3_3 r10 sata0txp ad7 thrm# ab17 vcc3_3 g10 sata1rxn ae8 trdy# a10 vcc3_3 f10 sata1rxp ad8 usbp0n h7 vccrtc ae3 sata1txn ad9 usbp0p h6 vccsus3_3 n4 sata1txp ac9 usbp1n h3 vccsus3_3 f18 rsvd ab11 usbp1p h2 vccsus3_3 k7 sataled# ad25 usbp2n j2 vcc1_5 aa8 satarbias# ad11 usbp2p j3 vcc1_5 m9 satarbias ac11 usbp3n k6 vrmpwrgd v16 serirq aa16 usbp3p k5 vss ad2 serr# b11 usbp4n k1 vss ae1 slp_s3# h20 usbp4p k2 vss y2 slp_s4# e25 usbp5n l2 vss t2 slp_s5# f21 usbp5p l3 vss v1 smbalert# / gpio11 e20 usbp6n m6 vss h1 smbclk h18 usbp6p m5 vss a1 smbdata e23 usbp7n n1 vss ab4 smi# aa21 usbp7p n2 vss ab6 smlink0 f25 usbrbias# g3 vss ab7 smlink1 f24 usbrbias g2 vss l4 linkalert# h21 vcc1_05 v10 vss n3 spi_arb r4 vcc1_05 j10 vss h4 spi_clk p9 vcc1_05 p15 vss h5 spi_cs# m8 vcc1_05 k17 vss k4 spi_miso r2 v5ref f12 vss g4 spi_mosi t1 v5ref_sus f5 vss b6 spkr j16 vcc3_3 h25 vss ad10 stop# f14 vcc1_5 m20 vss ae10 stpclk# v18 vcc1_5 n22 vss ab8 stp_cpu# ab19 vccdmipll y25 vss ac8 stp_pci# y16 vccsatapll y6 vss v7 sus_stat# / lpcpd# g22 vcc3_3 ad13 vss v8 vxxusbpll f6 vccsus3_3 f1 vss m7 table 6-89.chipset ballout by signal name (sheet 3 of 4) signal name ball # signal name ball # signal name ball # www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 221 ballout definition vss m11 vss p11 vss g8 vss k8 vss k11 vss b10 vss r14 vss w12 vss n12 vss n13 vss n14 vss p13 vss v19 vss p19 vss k19 vss e18 vss f16 vss b16 vss ad20 vss w22 vss t22 vss v22 vss r22 vss k20 vss b20 vss ad24 vss ae25 vss y24 vss v25 vss n23 vss a25 vss b24 vss g24 vss ae13 vss f2 wake# c25 table 6-89.chipset ballout by signal name (sheet 4 of 4) signal name ball # signal name ball # signal name ball # www.datasheet.co.kr datasheet pdf - http://www..net/
chipset package information 222 datasheet 7 chipset package information the chipset package information is shown in figure 7-18 , figure 7-19 , and figure 7-20 . note: all dimensions unless otherwise specified are in millimeters. figure 7-18. chipset package (top view) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 223 chipset package information figure 7-19. chipset package (bottom view) figure 7-20. chipset package (side view) www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 224 datasheet 8 electrical characteristics this chapter contains the dc and ac charac teristics for chipset. ac timing diagrams are included. 8.1 thermal specifications chipset?s thermal design power (tdp) for nettop platform is 2.1 w and netbook is 1.5 w. refer to chipset thermal design guidelines (doc id: 417912) for detail chipset thermal information. 8.2 absolute maximum ratings table 8-90. chipset 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.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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 225 electrical ch aracteristics 8.3 dc characteristics notes: 1. intel high definition audio codec only supported at 3.3v. 2. vccsus3_3 assumes that the 8 high-speed usb 2.0 devices are connected to chipset?s root ports. 3. icc (rtc) data is estimated with vccrtc at 3.0 v while the system is in a mechanical off (g3) state at room temperature. only the g3 state of this rail is shown to provide an estimate of battery life. table 8-91.dc current characteristics power plane maximum current consumption symbol s0 s3 cold s4/s5 g3 vcc1_05 0.955a 0.000a 0.000a 0.000a vcc1_5 1.422a 0.000a 0.000a 0.000a vcc3_3 1 0.216a 0.000a 0.000a 0.000a vccsus3_3 2 0.092a 27ma 27ma 0.000a vccrtc 3 na na na 6ua v5ref 6ma 0.000a 0.000a 0.000a v5ref_sus 10ma 10ma 10ma 0.000a v_cpu_io 14ma 0.000a 0.000a 0.000a vccusbpll 10ma 0.000a 0.000a 0.000a vccdmipll 24ma 0.000a 0.000a 0.000a vccsatapll 45ma 0.000a 0.000a 0.000a table 8-92.dc characteristic input signal association (sheet 1 of 2) symbol associated signals v ih1 /v il1 (5v tolerant) pci signals: ad[31:0], c/be[3:0]# , devsel#, frame#, irdy#, par, perr#, plock#, req[2:1]#, gpio22, gpio1, serr#, stop#, trdy# interrupt signals: pirq[d:a]#, pirq[h:e]#/gpio[5:2] vih2/vil2 clock signals: clk14, clk48 power management signals: mch_sync#, thrm#, vrmpwrgd gpio signals: gpio[39:37,33,7, 6] strap signals: spkr, sataled# (strap purposes only) www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 226 datasheet v ih3 /v il3 clock signals: pciclk lpc/firmware hub signal s: lad[3:0]/fwh[3:0], ldrq0#, ldrq1#/gpio23 power management signals: lan_rst#, bm_busy#/gpio0, clkrun#, lan_rst# pci signals: pme# interrupt signals: serirq cpu signals: a20gate, rcin# usb signals: oc[4:0]#, oc[7:5]#/gpio[31:29] gpio signals: strap1#/gpio 48, strap2#/gpio17, gpio0 spi signals: spi_cs#, spi_miso, spi_arb v ih4 /v il4 smbus signals: smbclk, smbdata system management signals: smbalert#/gpio11, smlink[1:0] v ih5 /v il5 lan signals: lan_clk, lan_rxd[2:0] eeprom signals: ee_din strap signals: ee_cs, ee_do ut (strap purposes only) v ih6 /v il6 processor signals: ferr#, thrmtrip# gpio signals : gpio49/cpupwrgd v imin7 /v imax7 pci express* data rx signals: per[p,n][4:1] v ih8 /v il8 real time clock signals: rtcx1 v imin9 /v imax9 sata signals: sata[1:0]rx[p,n] v ih10 /v il10 strap signals: hda_sd out, hda_sync (strap purposes only) gpio signals : gpio34 see v il_hda /v ih_hda for high definition audio low voltage mode (netbook only) v ih11 /v il11 / v cross(abs) clock signals: dmi_clkn, dmi_clkp, sata_clkn, sata_clkp v ih12 /v il12 power management signals: : batlow#, pwrbtn#, ri#, sys_reset#, wake# system management signal: linkalert# gpio signals: gpio[28:26, 25:24, 15:12, 10:8] v ih13 /v il13 power management signals: pwrok, rsmrst#, rtcrst# system management signals: intruder# v ih14 /v il14 other signals: intvrmen v di / v cm / v se (5v tolerant) usb signals: usbp[7:0][p,n] (low-speed and full-speed) v hssq / v hsdsc / v hscm (5v tolerant) usb signals: usbp[7:0][p,n] (in high-speed mode) table 8-92.dc characteristic input signal association (sheet 2 of 2) symbol associated signals www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 227 electrical ch aracteristics table 8-93.dc input charac teristics (she et 1 of 2) symbol parameter min max unit notes v il1 input low voltage ?0.5 0.3(vcc3_3) v v ih1 input high voltage 0.5(vcc3_3) v5ref + 0.5 v v il2 input low voltage ?0.5 0.8 v v ih2 input high voltage 2.0 vcc3_3 + 0.5 v v il3 input low voltage ?0.5 0.3(vcc3_3) v v ih3 input high voltage 0.5(vcc3_3) vcc3_3 + 0.5 v v il4 input low voltage ?0.5 0.8 v v ih4 input high voltage 2.1 vccsus3_3 + 0.5 v v il5 input low voltage -0.5 0.3(vcc3_3) v v ih5 input high voltage 0.6(vcc3_3) vcc3_3 + 0.5 v v il6 input low voltage ? 0.5 0.58(v_cpu_io) v v ih6 input high voltage 0.73(v_cpu_io) v_cpu_io + 0.5 v v imin7 minimum input voltage 175 mvdiffp-p 1 v imax7 maximum input voltage 1200 mvdiffp-p 1 v il8 input low voltage ? 0.5 0.10 v v ih8 input high voltage 0.40 1.2 v v imin9 minimum input voltage 325 mvdiffp-p 2 v imax9 maximum input voltage 600 mvdiffp-p 2 v imin9 minimum input voltage 275 mvdiffp-p 3 v imax9 maximum input voltage 750 mvdiffp-p 3 v il10 input low voltage ? 0.5 0.35(vcc3_3) v v ih10 input high voltage 0.65(vcc3_3) vcc3_3 + 0.5 v v il11 input low voltage -0.150 0.150 v v ih11 input high voltage 0.660 0.850 v v il12 input low voltage ? 0.5 0.8 v v ih12 input high voltage 2.0 vccsus3_3 + 0.5 v v il13 input low voltage ? 0.5 0.78 v v ih13 input high voltage 2.0 vccrtc + 0.5 v 4 v il14 input low voltage ? 0.5 0.65 v v ih14 input high voltage 2.0 vccrtc + 0.5 v 4 v cross(abs) absolute crossing point 0.250 0.550 v v di differential input sensitivity 0.2 v 5, 6 www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 228 datasheet notes: 1. pci express mvdiff p-p = |petp[x] ? petn[x]| 2. applicable only when sata po rt signaling rate is 1.5 gb/s: sata vdiff, tx (v imax/min10 ) is measured at the sata connector on the tr ansmit side (generally, the motherboard connector), where sata mvdiff p-p = |sata[x] txp/rxp ? sata[x]txn/rxn| 3. applicable only when sata port signal ing rate is 3 gb/s: sata vdiff, tx (v imax/min10 ) is measured at the sata connector on the transmit side (generally, the motherboard connector), where sata mvdiff p-p = |sata[x]txp/rxp ? sata[x]txn/rxn| 4. vccrtc is the voltage applied to the vccrtc we ll of chipset. when th e system is in a g3 state, this is generally supplie d by the coin cell battery, but for s5 and greater, this is generally vccsus3_3. 5. v di = | usbpx[p] ? usbpx[n] 6. applies to high-speed usb 2.0 7. includes v di range v cm differential common mode range 0.8 2.5 v 6, 7 v se single-ended receiver threshold 0.8 2.0 v 6 v hssq hs squelch detection threshold 100 150 mv v hsdsc hs disconnect detection threshold 525 625 mv v hscm hs data signaling common mode voltage range ? 50 500 mv v hssq hs squelch detection threshold 100 150 mv v hsdsc hs disconnect detection threshold 525 625 mv v hscm hs data signaling common mode voltage range ? 50 500 mv table 8-93.dc input characteristics (sheet 2 of 2) symbol parameter min max unit notes www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 229 electrical ch aracteristics notes: 1. these signals are open drain table 8-94.dc characteristic output signal association symbol associated signals v oh1 /v ol1 processor signals: a20m#, dpslp# , dprstp#, ignne#, init#, intr, nmi, smi#, stpclk#, cpupwrgd/gpio49 v oh2 /v ol2 pci signals: ad[31:0], c/be[3:0]# , devsel#, frame#, irdy#, par, perr#, plock#, serr#, stop#, trdy# intel hd audio sign als: hda_rst#, hda_sdout, acz_sync, hda_bit_clk note: see v oh_hda /v ol_hda for high definition audio low voltage mode v oh3 /v ol3 smbus signals: smbclk 1 , smbdata 1 system management signals: smlink[1:0] 1 gpio signals: gpio11/smbalert 1 v oh4 /v ol4 power management signals: dprslp vr, pltrst#, slp_s3#, slp_s4#, slp_s5#, stp_cpu#, stp_pci#, susclk, sus_stat gpio signals:gpio[39, 38, 33, 20, 18, 16, 7, 6] other signals: spkr sata signal: sataled# eeprom signals: ee_cs, ee_dout, ee_shclk v oh5 /v ol5 usb signal s: usbp[7:0][p,n] in low-speed and full-speed modes v omin6 /v omax6 pci express* data tx signals: pet[p,n][4:1] on chipset. v omin7 /v omax7 sata signals: sata[1:0]tx[p,n] v oh8 /v ol8 lpc/firmware hub signals: lad[3:0]/fwh[3:0], lframe#/fwh[4] pci signals: pcirst#, gnt[2:1]#,st rap0#, strap1#/gpio48, strap0#/gpio17 gpio signals: : gpio23/ldrq1#, gpio22, gpio[5 :2]/pirq[h:e]#, gpio1, gpio0/ bm_busy#, gpio34 interrupt signals: serirq spi signals: spi_cs#, spi_mosi, spi_clk processor interface signal: init3_3v# lan signals: lan_rstsync, lan_txd[2:0] v oh9 /v ol9 gpio signals: gpio[28:26, 25:24, 15:12, 10:8], gpio[31:29]/oc[7:5]# v hsoi v hsoh v hsol v chirpj v chirpk usb signals: usbp[7:0][p: n] in high-speed mode v oh_hda /v ol_hda intel hd audio signals: hd a_rst#, hda_sdout, hda_sync www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 230 datasheet notes: 1. maximum i ol for cpupwrgd is 12 ma for short du rations (<500 ms per 1.5 s) and 9 ma for long durations. table 8-95.dc output characteristics symbol parameter min max unit i ol / i oh notes v ol1 output low voltage 0.255 v 3 ma 1 v oh1 output high voltage v_cpu_io ? 0.3 v -3 ma v ol2 output low voltage 0.1(vcc3_3) v 1.5 ma v oh2 output high voltage 0.9(vcc3_3) v -0.5 ma 2 v ol3 output low voltage 0.4 v 4 ma v oh3 output high voltage vccsus3_3 ? 0.5 v-2 ma 2 v ol4 output low voltage 0.4 v 6 ma v oh4 output high voltage vcc3_3 ? 0.5 v -2 ma v ol5 output low voltage 0.4 v 5 ma v oh5 output high voltage vcc3_3 ? 0.5 v -2 ma v omin6 minimum output voltage 800 mvdif fp-p 3 v omax6 maximum output voltage 1200 mvdif fp-p 3 v omin7 minimum output voltage 400 mvdif fp-p 4 v omax7 maximum output voltage 600 mvdif fp-p 4 v omin7 minimum output voltage 400 mvdif fp-p 5 v omax7 maximum output voltage 700 mvdif fp-p 5 v ol8 output low voltage 0.1(vcc3_3) v 1.5 ma v oh8 output high voltage 0.9(vcc3_3) v -0.5 ma 2 v ol9 output low voltage 0.4 v 6 ma v oh9 output high voltage vccsus3_3 ? 0.5 v-0.5 ma v hsoi hs idle level ? 10.0 10.0 mv v hsoh hs data signaling high 360 440 mv v hsol hs data signaling low ? 10.0 10.0 mv v chirpj chirp j level 700 1100 mv v chirpk chirp k level ? 900 ? 500 mv v ol_hda output low voltage 0.1(vcchda) v 1.5 ma v oh_hda output high voltage 0.9(vcc_hda) v -0.5 ma www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 231 electrical ch aracteristics 2. the serr#, pirq[h:a], gpio11, smbdat a, smbclk, linkalert#, and smlink[1:0] signal has an open drain driver and satale d# has an open collector driver, and the v oh spec does not apply. this signal must have an ex ternal pull-up resistor. 3. pci express mvdiff p- p = |petp[x] ? petn[x]| 4. applicable only when sat a port signaling rate is 1.5 gb/s: sata vdiff, tx (v omax/min8 ) is measured at the sata connector on the transmit side closest to chipset (generally, the motherboard connector), where sata mv diff p-p = |sataxtxp ? sataxtxn|. 5. applicable only when sat a port signaling rate is 3 gb/s: sata vdiff, tx ( vomax/min8 ) is measured at the sata connector on the transmit side closest to chipset (generally, the motherboard connector), where sata mv diff p-p = |sataxtxp ? sataxtxn|. table 8-96.other dc characteristics symbol parameter min max unit notes v5ref chipset core well reference voltage 4.75 5.25 v 1 vcc3_3 i/o buffer voltage 3.135 3.465 v 1 vcc1_5, vccusbpll, vccsatapll, vccdmipll internal logic and i/o buffer voltage 1.425 1.575 v 1 v_cpu_io processor interface 0.945 1.25 v 1, 2 v5ref_sus suspend well reference voltage 4.75 5.25 v 1 vccsus3_3 suspend well i/o buffer voltage 3.135 3.465 v 1 vcc1_05 internal logic voltage 0.998 1.102 v 1 vccrtc battery voltage 2.0 3.6 v 1 v di differential input sensitivity 0.2 v |(usbpx+,usbpx - )| v cm differential common mode range 0.8 2.5 v includes v di v crs output signal crossover voltage 1.3 2.0 v v se single ended rcvr threshold 0.8 2.0 v i li1 ata input leakage current ? 200 200 a (0 v < v in < 5 v) i li2 pci_3v hi-z state data line leakage ? 10 10 a (0 v < v in < 3.3 v) i li3 pci_5v hi-z state data line leakage ? 70 70 a max v in = 2.7 v min v in = 0.5 v i li4 input leakage current ? clock signals ? 100 +100 a 1 c in input capacitance ? all other 12 pf f c = 1 mhz c out output capacitance 12 pf f c = 1 mhz c i/o i/o capacitance 12 pf f c = 1 mhz www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 232 datasheet notes: 1. for all noise components 20 mhz, the sum of the dc voltage and the ac noise component must be within the specified dc min/max operating range on the chipset supply voltages. 2. the tolerances shown in table 8-96 are inclusive of all noise from dc up to 20 mhz. in testing, the voltage rails should be measured with a bandwidth limi ted oscilloscope that has a roll off of 3 db/decade above 20 mhz. 3. includes clk14, clk48, lan_clk, and pciclk. 8.4 ac characteristics 1 typi cal va lue c l xtal1 6 pf c l xtal2 6 pf table 8-96.other dc characteristics symbol parameter min max unit notes table 8-97.clock timings (sheet 1 of 2) sym parameter min max unit notes figure pci clock (pciclk) t1 period 30 33.3 ns 8-21 t2 high time 11 ns t3 low time 11 ns t4 rise time 1 4 v/ns t5 fall time 1 4 v/ns 14 mhz clock (clk14) t6 period 67 70 ns 8-21 t7 high time 20 ns t8 low time 20 ns t41 rising edge rate 1.0 4.0 v/ns 1 t42 falling edge rate 1.0 4.0 v/ns 48 mhz clock (clk48) f clk48 operating frequency 48.00 0 mhz 2 t9 frequency tolerance 100 ppm t10 high time 7 ns 8-21 t11 low time 7 ns t12 rise time 1.2 ns t13 fall time 1.2 ns www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 233 electrical ch aracteristics notes: 1. clk14 edge rates in a system as measured from 0.8 v to 2.0 v. 2. the clk48 expects a 40/60% duty cycle. 3. the maximum high time (t18 max) provides a simple method for device s to detect bus idle conditions. 4. susclk duty cycle can range from 30% minimum to 70% maximum. smbus clock (smbclk) f smb operating frequency 10 16 khz t18 high time 4.0 50 us 3 8-30 t19 low time 4.7 us t20 rise time 1000 ns t21 fall time 300 ns hda_bit_clk (intel ? high definition audio mode) fhda operating frequency 24.0 mhz frequency tolerance ? 100 ppm t26a input jitter (ref er to clock chip specification) ? 300 ppm t27a high time (measured at 0.75vcc) 18.75 22.91 ns 8-21 t28a low time (measured at 0.35vcc) 18.75 22.91 ns sata clock (sata_clkp, sata_clkn) / dmi clock (dmi_clkp, dmi_clkn) t36 period 9.997 10.0533 ns t37 rise time 175 700 ps t38 fall time 175 700 ps suspend clock (susclk) fsusclk operating frequency 32 khz 4 t39 high time 10 ? us t39a low time 10 ? us table 8-97.clock timings (sheet 2 of 2) sym parameter min max unit notes figure table 8-98.sata interface timings sym parameter min max units notes figure ui gen i operating data period 666.43 670.12 ps ui-2 gen ii operating data period (3gb/s) 333.21 335.06 ps t120 rise time 0.2 0.41 ui 1 t121 fall time 0.2 0.41 ui 2 t122 tx differential skew ? 20 ps www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 234 datasheet notes: 1. 20% ? 80% at transmitter 2. 80% ? 20% at transmitter 3. as measured from 100 mv differential cros spoints of last and first edges of burst. 4. operating data period during out-of-band burst transmissions. notes: 1. t134 has a minimum timing for i 2 c of 0 ns, while the minimum timing for smbus is 300 ns. 2. a device will timeout when any clock low exceeds this value. 3. t137 is the cumulative time a slave device is allowed to extend the clock cycles in one message from the initial start to stop. if a slave device exceeds this time, it is expected to release both its clock and da ta lines and reset itself. 4. 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. 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 table 8-98.sata interface timings sym parameter min max units notes figure table 8-99.smbus timing sym parameter min max units notes figure t130 bus tree time between stop and start condition 4.7 ? s 8-30 t131 hold time after (repeated) start condition. after this period, the first clock is generated. 4.0 ? s t132 repeated start condition setup time 4.7 ? s t133 stop condition setup time 4.0 ? s t134 data hold time 0 ? ns 1 t135 data setup time 250 ? ns t136 device time out 25 35 ms 2 t137 cumulative clock low extend time (slave device) ?25ms 3 8-31 t138 cumulative clock low extend time (master device) ?10ms 4 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 235 electrical ch aracteristics notes: 1. audio link operating in inte l high definiti on audio mode. 1 table 8-100.intel hd audio timing sym parameter min max units notes figures t143 time duration for which hda_sdout is valid before hda_bit_clk edge. 7?ns 1 8-44 t144 time duration for which hda_sdout is valid after hda_bit_clk edge. 7?ns 1 t145 setup time for hda_sdin [2:0] at rising edge of hda_bit_clk 15 ? ns 1 t146 hold time for hda_sdin [2:0] at rising edge of hda_bit_clk 0?ns 1 table 8-101.lpc timing sym parameter min max units notes figures t150 lad[3:0] valid delay from pciclk rising 2 11 ns 8-22 t151 lad[3:0] output enable delay from pciclk rising 2? ns 8-26 t152 lad[3:0] float delay from pciclk rising ? 28 ns 8-24 t153 lad[3:0] setup time to pciclk rising 7 ? ns 8-23 t154 lad[3:0] hold time from pciclk rising 0 ? ns t155 ldrq[1:0]# setup time to pciclk rising 12 ? ns t156 ldrq[1:0]# hold time from pciclk rising 0 ? ns t157 lframe# valid delay from pciclk rising 2 12 ns 8-22 table 8-102.miscellaneous timings sym parameter min max units notes figures t160 serirq setup time to pciclk rising 7 ? ns 8-23 t161 serirq hold time from pciclk rising 0 ? ns 8-23 t162 ri#, extsmi#, gpio, usb resume pulse width 2 ? rtcclk 8-25 t163 spkr valid delay from osc rising ? 200 ns 8-22 t164 serr# active to nmi active ? 200 ns t165 ignne# inactive from ferr# inactive ? 230 ns www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 236 datasheet notes: 1. the typical clock frequency dr iven by chipset is 17.9 mhz. table 8-103.spi timings sym parameter min max units notes figures t180 serial clock frequency 17.3 18.4 mhz 1 t182 duty cycle at the host 40 60 % 8-45 t183 tco of spi_mosi with respect to serial clock falling edge at the host -5 13 ns t184 setup of spi_miso with respect to serial clock falling edge at the host 16 ? ns t185 hold of spi_miso with respect to serial clock falling edge at the host 0?ns t186 setup of spi_cs# assertion with respect to serial clock rising at the host. 30 ? ns t187 hold of spi_cs# de assertion with respect to serial clock falling at the host. 30 ? ns table 8-104.(power sequencing and re set signal timings (sheet 1 of 2) sym parameter min max units notes fig t200 vccrtc active to rtcrst# inactive 18 ? ms 8-32 8-33 t201 v5ref_sus active to vccsus3_3 active 0 ? ms 1 t202 vccsus3_3 active to vccsus1_05 active ? ? ? 2 t203 vccrtc supply active to vccsus supplies active 0?ms3 t204 vccsus supplies active to lan_rst# inactive, rsmrst# inactive (nettop only) 10 ? ms 8-32 8-34 t205 vccsus supplies active to rsmrst# inactive (netbook only) 5 ? ms 8-33 8-35 t208 vccsus supplies active to lan_rst# inactive (netbook only) 10 ? ms 8-33 t209 v5ref active to vcc3_3 active 0 ? ms 1 8-32 8-33 t211 vcc1_5 active to v_cpu_io active ? ? ? 1 t212 vccsus supplies active to vcc supplies active (netbook only) 0?ms5 8-33 t213 vccsus supplies active to vcc supplies active (nettop only) 0?ms3 8-32 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 237 electrical ch aracteristics notes: 1. 5ref must be powered up before vcc3_3, or after vcc3_3 within 0.7 v. also, v5ref must power down after vcc3_3, or be fore 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?. if the integrated vccsus1_05 voltage regulator is not used: a) vccsus3_3 must power up before vccsus1_05 or after vccsus1_05 within 0.7 v, b) vccsus1_05 must power down before vccsus3_3 or after vccsus3_3 within 0.7 v. 3. the vccsus supplies must not 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. vcc supplies refer to all ?core well? supplies: vcc3_3, vcc1_05, vcc1_5, v5ref, vccusbpll, vccdmipll, vccsatapll, v_cpu_io and vcchda (netbook only). it implies that all ?suspend wells? and vccrtc are stable too. 6. init# value determined by value of the cp u bist enable bit (chipset configuration register offset 3414h: bit 2). 7. these transitions are clocked off the intern al rtc. 1 rtc clock is approximately from 28.992 s to 32.044 s. t214 vcc supplies active to pwrok note: pwrok assertion indicates that pciclk has been stable for at least 1 ms. 99 ? ms 5 8-32 8-33 8-34 8-35 8-37 8-38 8-39 8-40 t215 v_cpu_io active to stpclk# and cpuslp# inactive (nettop only) ?50ns 8-34 8-37 8-38 t216 vcc active to dprslpvr inactive and stpclk#, stp_cpu#, stp_pci#, dpslp#, dprstp# inactive (netbook only) ?50ns 8-35 8-39 8-40 t217 pwrok active and sys_reset# inactive to sus_stat# inactive and processor i/f signals latched to strap value 32 38 rtcclk 6, 7 8-34 8-35 8-37 8-38 8-39 8-40 t218 sus_stat# inactive to pltrst# inactive 2 3 rtcclk 7 8-34 8-35 8-37 8-38 8-39 8-40 t228 hda_rst# active low pulse width 1 ? us t229 hda_rst# inactive to hda_bit_clk startup delay 162.8 ? ns table 8-104.(power sequencing and re set signal timings (sheet 2 of 2) sym parameter min max units notes fig www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 238 datasheet table 8-105.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-34 8-35 t231 t232 rsmrst# inactive to susclk running, slp_s5# inactive 110 ms 1, 2 8-34 8-35 t233 slp_s5# inactive to slp_s4# inactive see note below 3 8-34 8-35 t234 slp_s4# inactive to slp_s3# inactive 1 2 rtcclk 4 8-34 8-35 t250 processor i/f sign als latched prior to stpclk# active (netbook only) 0 5 8-41 8-43 t253 dpslp# active to stp_cpu# active (netbook only) 11pciclk 6 8-42 8-43 t254 stp_cpu# active to processor clock stopped (netbook only) 0?pciclk 6, 7 8-43 t255 stp_cpu# active to dprstp#, dprslpvr active (netbook only) 0 8-43 t265 break event to dprstp#, dprslpvr inactive (c4 exit) (netbook only) 1.5 1.8 s 8 8-43 t266 dprslpvr, dprstp# inactive to stp_cpu# inactive and cpu vcc ramped (netbook only) programable. see d31:f0:aa, bits 3:2 s 8-43 t267 break event to stp_cpu# inactive (c3 exit) (netbook only) 6 note 14 pciclk 6, 9, 10 8-42 t268 stp_cpu# inactive to processor clock running (netbook only) 03pciclk 6, 7 8-43 t269 stp_cpu# inactive to dpslp# inactive (netbook only) 11pciclk 6, 11 8-42 8-43 t271 s1 wake event to cpuslp# inactive (nettop only) 1 25 pciclk 6 8-36 t273 break event to stpclk# inactive (c2 exit) (netbook only) 0ns 8-41 t274 stpclk# inactive to processor i/f signals unlatched (netbook only) 89pciclk 5, 6 8-41 8-43 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 239 electrical ch aracteristics t280 stpclk# active to dmi message 0 pciclk 12 8-36 8-37 8-38 8-39 8-40 t281 dmi message to cpuslp# active (nettop only) 60 63 pciclk 6 8-36 t283 dmi message to sus_stat# active 2 rtcclk 4 8-37 8-38 8-39 8-40 t284 sus_stat# active to pltrst#, pcirst# active (nettop only) 7 17 rtcclk 4 8-37 8-38 t285 sus_stat# active to stp_pci# active (netbook only) 2 10 rtcclk 4 8-39 8-40 t286 stp_pci# active to pltrst# and pcirst# active (netbook only) 5 7 rtcclk 4 8-39 8-40 t287 pltrst#, pcirst# active to slp_s3# active 1 2 rtcclk 4 8-37 8-38 8-39 8-40 t288 (s3 cold configuration only) slp_s3# active to pwrok, vrmpwrgd inactive (netbook only) 0ms 13 8-39 t289 slp_s3# active to pwrok, vrmpwrgd inactive (nettop only) 0ms 13 8-37 t290 (s3 cold configuration only) pwrok, vrmpwrgd inactive to vcc supplies inactive (netbook only) 20 ns 14, 15 8-39 t291 slp_s3# active to slp_s4# active 1 2 rtcclk 4 8-37 8-38 8-39 8-40 t292 (s3 hot configuration only) slp_s4# active to vrmpwrgd and pwrok inactive 0ms 13 8-38 8-40 t293 (s3 hot configuration only) pwrok, vrmpwrgd inactive to vcc supplies inactive 20 ns 14, 15 8-38 8-40 t294 pwrok, vrmpwrgd in active to vcc supplies inactive (nettop only) 20 ns 14, 15 8-37 table 8-105.power management timings (sheet 2 of 3) sym parameter min max units notes fig www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 240 datasheet notes: 1. 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. 2. if the afterg3_en bit (gen_p mcon_3 configuration register bit 1) is set to a 1, slp_s5# will not be de-asserted until a wake event is detected. if the afterg3_en bit is set to 0, slp_s5# will deassert within the specification listed in the table. 3. the min/max times depend on the progra mming of the ?slp_s4# minimum assertion width? and the ?slp_s4# assertion stretch enable bits (d31:f0:a4h bits 5:3). 4. these transitions are clocked off the internal rtc. 1 rtc clock is approximately 28.992 s to 32.044 s. t295 slp_s4# active to slp_s5# active 1 2 rtcclk 4, 16 8-37 8-38 8-39 8-40 t296 wake event to slp_s5# inactive 1 10 rtcclk 4 8-37 8-38 8-39 8-40 t297 slp_s5# inactive to slp_s4# inactive see note below 3 8-37 8-38 8-39 8-40 t298 slp_s4# inactive to slp_s3# inactive 1 2 rtcclk 4 8-37 8-38 8-39 8-40 t299 s4 wake event to slp_s4# inactive (s4 wake) see note below 3 8-37 8-38 8-39 8-40 t300 s3 wake event to slp_s3# inactive (s3 wake) 0 small as possi ble rtcclk 4 8-37 8-38 8-39 8-40 t301 cpuslp# inactive to stpclk# inactive (nettop only) 8 pciclk 8-36 t302 slp_s3# inactive to chipset check for pwrok active 45msec 8-37 8-38 8-39 8-40 t303 slp_s3# active to vcc supplies inactive 5 us 15, 17 other timings t310 thrmtrip# active to slp_s3#, slp_s4#, slp_s5# active 3 pci clk t311 rsmrst# rising edge transition from 20% to 80% 50 us t312 rsmrst# falling edge transition 18 table 8-105.power management timings (sheet 3 of 3) sym parameter min max units notes fig www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 241 electrical ch aracteristics 5. note that this does not apply for synchronous smis. 6. these transitions are clocked off the 33 mhz pciclk. 1 pciclk is approximately 30 ns. 7. this is a clock generator specification. 8. this is non-zero to enforce the minimum asse rt time for dprslpvr. if the minimum assert time for dprslpvr has been met, then this is pe rmitted to be 0. 9. 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. 10. this value should be at most a few clocks greater than the minimum. 11. this value is programmable in multiples of 1024 pci clks. maximum is 8192 pci clks (245.6 s). 12. chipset stpclk# assertion will trigger the processor to send a stop grant acknowledge cycle. the timing for this cycle getting to chipset is dependant on the processor and the memory controller. 13. chipset has no maximum timing requirement fo r 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. 14. t290, t293, and t294 apply during s0 to g3 transitions only. in addition, the timings are not applied to v5ref. v5ref timings are bonded by power sequencing. 15. a vcc supply is inactive when the voltage is below the min value specified in table 8-96 . 16. f 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). 17. t303 applies during s0 to s3-s5 transitions. 18. rsmrst# falling edge must transition to 0. 8 v or less before vccsus3_3 drops to 2.1 v. 8.5 timing diagrams figure 8-21. clock timing figure 8-22. valid delay from rising clock edge clock 1.5v valid delay vt output www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 242 datasheet figure 8-23. setup and hold times figure 8-24. float delay figure 8-25. pulse width figure 8-26. output enable delay clock vt input hold time setup time vt 1.5v input vt output float delay vt pulse width vt clock output output enable delay vt 1.5v www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 243 electrical ch aracteristics figure 8-27. usb rise and fall times figure 8-28. usb jitter figure 8-29. usb eop width differential data lines 90% 10% 10% 90% t r t f rise time fall time c l c l low-speed: 75 ns at c l = 50 pf, 300 ns at c l = 350 pf full-speed: 4 to 20 ns at c l = 50 pf high-speed: 0.8 to 1.2 ns at c l = 10 pf paired transitions consecutive transitions crossover points t period differential data lines jitter differential data lines eop width data crossover level tperiod www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 244 datasheet figure 8-30. smbus transaction figure 8-31. smbus timeout t130 smbclk smbdata t131 t19 t134 t20 t21 t135 t132 t18 t133 start stop t137 clk ack clk ack t138 t138 smbclk smbdata www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 245 electrical ch aracteristics notes: 1. other power includes vccusbpll, vccdmipll, and vccsat apll. 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 si gnals, including vcc1_05, to vcc3_3 and vcc1_5. however, if vcc3_3 (core well buffer) is powered before vcc1_05 (core well logic), core well signal states are indeterminate, undefined, an d may glitch prior to pwrok assertion. refer to section 3.2 and section 3.3 for a list of signals th at will be determinate before pwrok. 2. prwok must not glitch, even if rsmrst# is low. 3. this power is supply by chipset internal vr. figure 8-32. power sequencing and reset signal timings (nettop only) vccrtc v_cpu_io vccsus3_3 rtcrst# lan_rst#, rsmrst# t200 t201 ich 7 ps dkt d v5ref_sus v5ref pwrok vcc3_3 vccsus1_05 3 t203 t204 t209 t211 t214 t202 t213 vcc1_5, vcc1_05 and other power 1 www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 246 datasheet notes: 1. other power includes vccusbpl l, 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 si gnals, including vcc1_05, to vcc3_3 and vcc1_5. however, if vcc3_3 (core well buffer) is powered before vcc 1_05 (core well logic), core well signal states are indeterminate, undefined, and may glitch prior to pwrok assertion. refer to section 3.2 and section 3.3 for a list of signals that will be determinate before pwrok. 2. this power is supply by chipset internal vr. figure 8-33. power sequencing and re set signal timings (netbook only) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 247 electrical ch aracteristics notes: 1. vcc includes vcc1_5, vcc3_3, vcc1_05, vc cusbpll, vccdmipll, vccsatapll, and v5ref. figure 8-34. g3 (mechanical off) to s0 timings (nettop only) www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 248 datasheet notes: 1. vcc includes vcc1_5,vcc3_3, vcc1_05, vccu sbpll, vccdmipll, vccsatapll, and v5ref. figure 8-35. g3 (mechanical off) to s0 timings (netbook only) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 249 electrical ch aracteristics notes: 1. vcc includes vcc1_5, vcc3_3, vcc1_05, vc cusbpll, vccdmipll, vccsatapll, and v5ref. 2. t294 is applicable when the syst em transitions from s0 to g3 only. figure 8-36. s0 to s1 to s0 timing (nettop only) figure 8-37. s0 to s5 to s0 timings, s3 cold (nettop only) t280 t281 t271 t301 s0 s0 s1 s1 s1 s0 s0 state stpclk# dmi message cpuslp# wake event stpclk# dmi message sus_stat# pl trst# slp_s3# (s3 cold conf ig) slp_s5# wake event pw rok vcc 1 s0 s0 s3 s3 s5 s0 t283 t284 t287 t289 t294 t214 t217 t218 t215 (from v _cpu_io) t280 ich7_s0_s5_s0_dt_s3cold.vsd slp_s4# t291 t295 t297 t298 s4 s4 s3 s3/s4/s5 s0 t296 t300 t299 vrmpwrgd www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 250 datasheet notes: 1. vcc includes vcc1_5, vcc3_3, vcc1_05, vccu sbpll, vccdmipll, vc csatapll, and v5ref. 2. t293 is applicable when the system transitions from s0 to g3 only. figure 8-38. s0 to s5 to s0 timings, s3 hot (nettop only) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 251 electrical ch aracteristics notes: 1. t290 is applicable when the syst em transitions from s0 to g3 only. 2. vcc includes vcc1_5, vcc1_5_b, vcc3_3, v cc1_05, vccusbpll, vccdmipll, vccsatapll, and v5ref. figure 8-39. s0 to s5 to s0 timings, s3 cold (netbook only) stp_cpu#, dpslp#, dprstp# pltrst# pcirst# slp_s3# (s3 cold board config) slp_s5# wake event pwrok vcc s0 s0 s3 s3 s5 s3/s4/s5 s0 s0 t295 t288 t290 t296 t214 t217 t218 stp_pci# stpclk# dmi message dprslpvr t280 t283 t285 t287 t286 sus_stat# s4 slp_s4# t291 t297 t300 t298 t216 t299 t302 www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 252 datasheet notes: 1. t293 is applicable when the system transitions from s0 to g3 only. 2. vcc includes vcc1_5, vcc1_5_b, vcc3_3, vc c1_05, vccusbpll, vc cdmipll, vccsatapll, and v5ref. figure 8-40. s0 to s5 to s0 timings, s3 hot (netbook only) stp_cpu#, dpslp#, dprstp# pltrst# pcirst# slp_s3# (s3 hot board config) slp_s5# wake event vrmpwrgd vcc s0 s0 s3 s3 s5 s3/s4/s5 s0 s0 t295 t292 t293 t296 t217 t218 stp_pci# stpclk# dmi message dprslpvr t280 t283 t285 t287 t286 sus_stat# s4 slp_s4# t291 t297 t300 t298 t216 t299 t302 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 253 electrical ch aracteristics figure 8-41. c0 to c2 to c0 timings (netbook only) figure 8-42. c0 to c3 to c0 timings (nettop only) unlatched latched unlatched cpu i/f signals stpclk# break event t250 t273 t274 unlatched latched cpu i/f signals stpclk# c0_c3_timing break event bus master stp_cpu# t250 t253 t268 t269 t274 active idle dpslp# unlatched cpu clocks running running stopped t267 t254 www.datasheet.co.kr datasheet pdf - http://www..net/
electrical ch aracteristics 254 datasheet figure 8-43. c0 to c4 to c0 timings (n etbook only) figure 8-44. intel hd audio input and output timings unlatched cpu i/f signals stpclk# c0_c4_timing break event bus master stp_cpu# t250 t253 t266 t269 t274 dprstp# dpslp# active idle dprslpvr unlatched cpu clocks running running t254 t255 cpu vcc t265 stopped t268 latched www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 255 electrical ch aracteristics figure 8-45. spi timings t182 t182 spi_clk spi_mosi spi_miso t184 t183 t185 spi_cs# t186 t187 www.datasheet.co.kr datasheet pdf - http://www..net/
register and memory mapping 256 datasheet 9 register and memory mapping the chipset contains registers that are located in the processor?s i/o space and memory space and sets of pci configurat ion registers that are located in pci configuration space. this chapter describes the chipset i/o and memory maps at the register-set level. register access is also described. register-level address maps and individual register bit descriptions are provid ed in the following chapters. the following notations and definitions are used in the register/instruction description chapters. all bit(s) or bit-fields must be correctly deal t with by software. on reads, software must use appropriate masks to extract the defined bits and not rely on reserved bits being any particular value. on writes, software must ensure that the values of reserved bit locations are preserved. any chipset configuration register or i/o or memory mapped location not explicitly indicated in this document must be considered reserved. 9.1 pci devices and functions the chipset incorporates a variety of pci functions as shown in table 9-106 . these functions are divided into six logical devices (b0:d30, b0:d31, b0:d29, b0:d28, b0:d27 and b1:d8). d30 contains the dmi interface-to-pci bridge and the ac?97 audio and modem controller. d31 contains the pci-to-lpc bridge, sata controller, and the ro read only. in some cases, if a register is read only, writes to this register location have no effect. however, in other cases, two separate registers are located at the same location where a read accesses one of the registers and a write accesses the other register. see the i/o and memory map tables for details. wo write only. in some cases, if a register is write only, reads to this register location have no effect. however, in other cases, two separate registers are located at the same location where a read accesses one of the registers and a write accesses the other register. see the i/o and memory map tables for details. r/w read/write. a register with this attribute can be read and written. r/wc read/write clear. a register bit with th is 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 read/write, 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 value has been written, th e bit becomes read only. default when chipset is reset, it sets its regi sters to predetermine d default states. the default state represents the minimum f unctionality feature set required to successfully bring up the system. hence, it does not represent the optimal system configuration. it is the responsibility of the system initialization software to determine configuration, operating paramete rs, and optional syst em features that are applicable, and to program th e chipset registers accordingly. bold register bits that are highlighted in bold text indicate that the bit is implemented in the chipset. regist er bits that are not implemente d or are hardwired will remain in plain text. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 257 register and memory mapping smbus controller. d29 contains the four usb uhci controllers and one usb ehci controller. d27 contains the intel high definition audio controller. b1:d8 is the integrated lan controller. note: from a software perspective, the integrated lan controller resides on the chipset's external pci bus. this is typically bus 1, but may be assigned a different number depending on system configuration. 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 lan controller will be disabled if no platform lan connect component is detected (see chapter 5.3 - volume 1). when a function is disabled, it does not appear at all to the software. a disabled function will not respond to any register reads or writes, insuring that these devices appear hidden to software. b notes: 1. the lpc controller contains registers th at control lpc, power management, system management, gpio, processor interfa ce, rtc, interrupt s, timers, dma. 9.2 pci configuration map each pci function on the chipset 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 cycles on the pci bus by the host bridge using configuration mechanism #1 detailed in the pci local bus specification, revision 2.3 . table 9-106.pci devices and functions bus:device:function 1 function description bus 0:device 30:functi on 0 pci-to-pci bridge bus 0:device 31:function 0 lpc controller 1 bus 0:device 31:function 2 sata controller bus 0:device 31:functi on 3 smbus controller 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 #4 bus 0:device 29:function 7 usb 2.0 ehci controller 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 27:function 0 i ntel hd audio controller bus n:device 8:functi on 0 lan controller www.datasheet.co.kr datasheet pdf - http://www..net/
register and memory mapping 258 datasheet 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 extract the defined bits and not rely on reserved bits being any particular value. on writes, software must ensure that the values of reserved bit positions are preserved. that is, the values of reserved bit positions must fi rst 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 within a regist er, the configuration space contains reserved locations. software should not write to re served 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-107 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 ta rget ranges that are marked as ?reserved? will not be decoded by the ch ipset, and will be passed to pci unless the subtractive decode policy 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 positive ly decoded by the chipset in medium speed. address ranges that are not listed or marked ?reserved? are not decoded by the chipset (unless assigned to one of the variable ranges). table 9-107.fixed i/o ranges decoded by chipset (sheet 1 of 3) 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 in terrupt controller interrupt 24h?25h interrupt controller in terrupt controller interrupt 28h?29h interrupt controller in terrupt controller interrupt 2ch?2dh interrupt controller interrupt controller interrupt 2e?2f lpc sio lpc sio forwarded to lpc www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 259 register and memory mapping 30h?31h interrupt controller in terrupt controller interrupt 34h?35h interrupt controller in terrupt controller interrupt 38h?39h interrupt controller in terrupt 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 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 dma 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 table 9-107.fixed i/o ranges decoded by chipset (sheet 2 of 3) i/o address read target write target internal unit www.datasheet.co.kr datasheet pdf - http://www..net/
register and memory mapping 260 datasheet notes: 1. a read to this address will subtractivel y go to pci, where it will master abort. 9.3.2 variable i/o decode ranges table 9-108 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 soft ware allows conflicts to occur. the chipset does not perform any checks for conflicts. 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 ferr#/ignne# / interrupt controller ferr#/ignne# / interrupt controller processor i/f 170h?177h ide controller, sata controller, or pci sata controller, or pci forwarded to ide or sata 1f0h?1f7h ide controller, sata controller, or pci 1 sata controller, or pci forwarded to ide or sata 376h ide controller, sata controller, or pci sata controller, or pci forwarded to ide or sata 3f6h ide controller, sata controller, or pci 1 sata controller, or pci forwarded ide or sata 4d0h?4d1h interrupt controller interrupt controller interrupt cf9h reset generator reset generator processor i/f table 9-107.fixed i/o ranges decoded by chipset (sheet 3 of 3) i/o address read target write target internal unit www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 261 register and memory mapping note: 1. decode range size determin ed by d31:f0:adh:bits 5:4 9.4 memory map table 9-109 shows (from the processor perspective) the memory ranges that the chipset 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). the chipset may then claim the cycle for the internal lan controller. 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 range, it will be forwarded up to dmi. software must not attempt locks to the chipset'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-108.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 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 64 lan unit lpc generic 1 anywhere in 64 kb i/o space 4 to 256 lpc peripheral lpc generic 2 1 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 www.datasheet.co.kr datasheet pdf - http://www..net/
register and memory mapping 262 datasheet table 9-109.memory decode ranges from processor perspective (sheet 1 of 2) memory range target d ependency/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 0000h?fec0 0100h i/o apic inside chipset fed4 0000h?fed4 0fffh tpm on lpc ffc0 0000h?ffc7 ffffh ff80 0000h?ff87 ffffh firmware hub (or pci) 1 bit 8 in firmware hub decode enable register is set ffc8 0000h?ffcf ffffh ff88 0000h?ff8f ffffh firmware hub (or pci) 1 bit 9 in firmware hub decode enable register is set ffd0 0000h?ffd7 ffffh ff90 0000h?ff97 ffffh firmware hub (or pci) 1 bit 10 in firmware hub decode enable register is set ffd8 0000h?ffdf ffffh ff98 0000h?ff9f ffffh firmware hub (or pci) 1 bit 11 in firmware hub decode enable register is set ffe0 000h?ffe7 ffffh ffa0 0000h?ffa7 ffffh firmware hub (or pci) 1 bit 12 in firmware hub decode enable register is set ffe8 0000h?ffef ffffh ffa8 0000h?ffaf ffffh firmware hub (or pci) 1 bit 13 in firmware hub decode enable register is set fff0 0000h?fff7 ffffh ffb0 0000h?ffb7 ffffh firmware hub (or pci) 1 bit 14 in firmware hub decode enable register is set fff8 0000h?ffff ffffh ffb8 0000h?ffbf ffffh firmware hub (or pci) 1 always enabled. the top two, 64 kb blocks of this range can be swapped, as described in section 7.4.1 . ff70 0000h?ff7f ffffh ff30 0000h?ff3f ffffh firmware hub (or pci) 1 bit 3 in firmware hub decode enable register is set ff60 0000h?ff6f ffffh ff20 0000h?ff2f ffffh firmware hub (or pci) 1 bit 2 in firmware hub decode enable register is set ff50 0000h?ff5f ffffh ff10 0000h?ff1f ffffh firmware hub (or pci) 1 bit 1 in firmware hub decode enable register is set ff40 0000h?ff4f ffffh ff00 0000h?ff0f ffffh firmware hub (or pci) 1 bit 0 in firmware hub decode enable register is set 4 kb anywhere in 4-gb range integrated lan controller 2 enable via bar in device 29:function 0 (integrated lan controller) 1 kb anywhere in 4-gb range usb ehci controller 2 enable via standa rd pci mechanism (device 29, function 7) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 263 register and memory mapping notes: 1. pci is the target when the boot bios destination selection bit is low (chipset config registers:offset 3401:bit 3). when pci select ed, the firmware hub decode enable bits have no effect. 2. only lan cycles can be seen on pci. 3. 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. 9.4.1 boot-block update scheme the chipset supports a ?top-block swap? mode that has the chipset 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 chipset will invert a16 for cycles ta rgeting firmware hub space. when this bit is 0, the chipset will not invert a16. this bi t 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. 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 firmware 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 512 b anywhere in 64-bit addressing space intel hd audio host controller enable via standard pci mechanism (device 30, function 1) fed0 x000h?fed0 x3ffh high precision event timers 3 bios determines the ?fixed? location which 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-109.memory decode ranges from processor perspective (sheet 2 of 2) memory range target dependency/comments www.datasheet.co.kr datasheet pdf - http://www..net/
register and memory mapping 264 datasheet if a power failure occurs at any point after st ep 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.22.1 - volume 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 strap removed 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 265 chipset configuration registers 10 chipset configuration registers this chapter describes all registers and base functionality that is related to chipset configuration and not a specific interface (e.g., lpc, pci, or pci express*). it contains the root complex register block that describes the behavior of the upstream internal link. this block is mapped into memory space, using register rcba of the pci-to-lpc bridge. accesses in this space must be limited to 32-(dword) bit quantities. burst accesses are not allowed. 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-110.chipset configur ation register memory map (memory space) (sheet 1 of 3) offset mnemonic register name default type 0000?0003h vch virtual channel capability header 10010002h ro 0004?0007h vcap1 virtual channel capability #1 00000801h ro 0008?000bh vcap2 virtual channel capability #2 00000001h ro 000c?000dh pvc port virtual channel control 0000h r/w, ro 000e?000fh pvs port virtual channel status 0000h ro 0010?0013h v0cap virtual channel 0 resource capability 00000001h ro 0014?0017h v0ctl virtual channel 0 resource control 800000ffh r/w, ro 001a?001bh v0sts virtual channel 0 resource status 0000h ro 001c?001fh v1cap virtual channel 1 resource capability 30008010h r/wo, ro 0020?0023h v1ctl virtual channel 1 resource control 00000000h r/w, ro 0026?0027h v1sts virtual channel 1 resource status 0000h ro 0100?0103h rctcl root complex topology capability list 1a010005h ro 0104?0107h esd element self description 00000602h 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 www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 266 datasheet 0130?0133h rp2d root port 2 descriptor 02xx0002h r/wo, ro 0138?013fh rp2ba root port 2 base address 00000000000e1000h ro 0140?0143h rp3d root port 3 descriptor 03xx0002h r/wo, ro 0148?014fh rp3ba root port 3 base address 00000000000e2000h ro 0150?0153h rp4d root port 4 descriptor 04xx0002h r/wo, ro 0158?015fh rp4ba root port 4 base address 00000000000e3000h ro 0160?0163h hdd intel hd audio descriptor 05xx0002h r/wo, ro 0168?016fh hdba intel hd audio base address 00000000000d8000h ro 01a0?01a3h ilcl internal link capability list 00010006h ro 01a4?01a7h lcap link capabilities 00012441h ro, r/wo 01a8?01a9h lctl link control 0000h r/w 01aa?01abh lsts link status 0041h ro 0224?0227h rpc root port configuration 0000000xh r/w, ro 0238?023bh rpfn root port function number for pci express root ports 00543210h r/wo, ro 1e00?1e03h trsr trap status register 00h 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, ro 1e88-1e8fh iotr1 i/o trap register 1 0000000000000000h r/w, ro 1e90-1e97h iotr2 i/o trap register 2 0000000000000000h r/w, ro 1e98-1e9fh iotr3 i/o trap register 3 0000000000000000h r/w, ro 3000?3001h tctl tco control 00h r/w 3100?3103h d31ip device 31 interrupt pin 00042210h r/w, ro 3104?3107h d30ip device 30 interrupt pin 00002100h r/w, ro 3108?310bh d29ip device 29 interrupt pin 10004321h r/w 310c?310fh d28ip device 28 interrupt pin 00004321h r/w 3110?3113h d27ip device 27 interrupt pin 00000001h r/w 3140?3141h d31ir device 31 interrupt route 3210h r/w 3142?3143h d30ir device 30 interrupt route 3210h r/w 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 31ff?31ffh oic other interrupt control 00h 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 0000000xh r/w, r/wlo table 10-110.chipset configuration register memory map (memory space) (sheet 2 of 3) offset mnemonic register name default type www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 267 chipset configuration registers 10.1.1 vch?virtual channel capability head er register offset address: 0000?0003h attribute: ro default value: 10010002h size: 32-bit 10.1.2 vcap1?virtual channe l capability #1 register offset address: 0004?0007h attribute: ro default value: 00000801h size: 32-bit 3414?3414h buc backed up control 0000001xb r/w 3418?341bh fd function disable see bit description r/w, ro 341c?341fh cg clock gating (netbook only) 00000000h r/w, ro table 10-110.chipset configur ation register memory map (memory space) (sheet 3 of 3) offset mnemonic register name default type bit description 31:20 next capability offset (nco) ? ro.this field indicates the next item in the list. 19:16 capability version (cv) ? ro. this field indicates suppo rt as a version 1 capability structure. 15:0 capability id (cid) ? ro. this field indicates this is the virtual channel capability item. bit description 31:12 reserved 11:10 port arbitration table entry size (pats) ? ro. this field indicates the size of the port arbitration table is 4 bi ts (to allow up to 8 ports). 9:8 reference clock (rc) ? ro. fixed at 100 ns. 7 reserved 6:4 low priority extended vc count (lpevc) ? ro. this field indicates that there are no additional vcs of low priority with extended capabilities. 3 reserved 2:0 extended vc count (evc) ? ro. this field indicates that there is one additional vc (vc1) that exists with extended capabilities. www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 268 datasheet 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 ch annel control register offset address: 000c?000dh attribute: r/w, ro default value: 0000h size: 16-bit 10.1.5 pvs?port virtual channel status register offset address: 000e?000fh attribute: ro default value: 0000h size: 16-bit 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 vc arbitration table offset (ato) ? ro. this field indicates that no table is present for vc arbitration since it is fixed. 23:8 reserved 7:0 vc arbitration capability (ac) ? ro. this field indicates that the vc arbitration is fixed in the root complex. vc1 is highest priority and vc0 is lowest priority. bit description 15:04 reserved 3:1 vc arbitration select (as) ? ro. this field indica tes 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. 0 load vc arbitration table (lat) ? ro. this bit 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:01 reserved 0 vc arbitration ta ble status (vas) ? ro. this bit indicates the coherency status of the vc arbitration table when it is being updated. this fi eld is always 0 in the root complex since there is no vc arbitration table. 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 269 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 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. this field indicates that this vc uses fixed port arbitration. bit description 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. this field indicate s the id to use for this virtual channel. 23:20 reserved 19:17 port arbitration select (pas) ? r/w. this field indicate s which port ta ble is being programmed. the root complex takes 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 implement an arbitration table fo r this virtual channel. 15:8 reserved 7:1 transaction class / virtual channel map (tvm) ? r/w. this field 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 bit description 15:02 reserved 1 vc negotiation pending (np) ? ro. when set, this bit indicates the virtual channel is still being nego tiated with ingress ports. 0 port arbitration tables status (ats) ? ro. there is no port arbitration table for this vc, so this bit is reserved at 0. www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 270 datasheet 10.1.9 v1cap?virtual channel 1 resource capability register offset address: 001c?001fh attribute: r/wo, ro default value: 30008010h size: 32-bit 10.1.10 v1ctl?virtual channel 1 resource control register offset address: 0020?0023h attribute: r/w, ro default value: 00000000h size: 32-bit bit description 31:24 port arbitration table offset (at) ? ro. this field indicates the location of the port arbitration table in the ro ot complex. a value of 3h indicates the 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 determin ation 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. this field indica tes the port arbitration capability is time-based wrr of 128 phases. bit description 31 virtual channel enable (en) ? r/w. 0 = disables the vc. 1 = enables the vc. 30:27 reserved 26:24 virtual channel identifier (id) ? r/w. this field indicates the id to use for this virtual channel. 23:20 reserved 19:17 port arbitration select (pas) ? r/w. this field indicate s 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) ? ro/w. when set, the port arbitration table loaded is 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. this field 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 271 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 rctcl?root comp lex topology capabili ties list register offset address: 0100?0103h attribute: ro default value: 1a010005h size: 32-bit 10.1.13 esd?element self description register offset address: 0104?0107h attribute: r/wo, ro default value: 00000602h size: 32-bit bit description 15:02 reserved 1 vc negotiation pending (np) ? ro. 0 = virtual channel is not being negotiated with ingress ports. 1 = the virtual channel is still being negotiated with ingress ports. 0 port arbitration tables status (ats) ? ro. this field indicates the coherency status of the port arbitratio n table. this bit is set when lat (offset 000ch:bit 0) is written with value 1 and pas (offset 0014h:bits19:17) has value of 4h. this bit is cleared after the table has been updated. bit description 31:20 next capability (next) ? ro. this field indicates the next item in the list. 19:16 capability version (cv) ? ro. this field indicates th e version of the capability structure. 15:0 capability id (cid) ? ro. this field indicates this is a pci express* link capability section of an rcrb. bit description 31:24 port number (pn) ? ro. a value of 0 to indicate the egress port for the chipset. 23:16 component id (cid) ? r/wo . this field indicates the component id assigned to this element by software. this is written on ce by platform bios and is locked until a platform reset. 15:8 number of link entries (nle) ? ro. this field indica tes that one link entry (corresponding to dmi), 6 root port entrie s (for the downstream ports), and the intel hd audio device are de scribed by this rcrb. 7:4 reserved 3:0 element type (et) ? ro. this field indicates that the element type is a root complex internal link. www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 272 datasheet 10.1.14 uld?upstream link descriptor register offset address: 0110?0113h attribute: r/wo, ro default value: 00000001h size: 32-bit 10.1.15 ulba?upstream link base address register offset address: 0118?011fh attribute: r/wo default value: 0000000000000000h size: 64-bit 10.1.16 rp1d?root port 1 descriptor register offset address: 0120?0123h attribute: r/wo, ro default value: 01xx0002h size: 32-bit bit description 31:24 target port number (pn) ? r/wo. this field is prog rammed by platform bios to match the port number of the (g)mch/cpu rcrb that is attached to this rcrb. 23:16 target component id (tcid) ? r/wo. this field is prog rammed by platform bios to match the component id of the (g)mch/cpu rcrb that is attached to this rcrb. 15:2 reserved 1 link type (lt) ? ro. this bit indicates that the link points to the (g)mch/cpu rcrb. 0 link valid (lv) ? ro. this bit indicates that the link entry is valid. bit description 63:32 base address upper (bau) ? r/wo. this field is progra mmed by platform bios to match the upper 32-bits of base address of the (g)mch/cpu rcrb that is attached to this rcrb. 31:0 base address lower (bal) ? r/wo. this field is progra mmed by platform bios to match the lower 32-bits of base address of the (g)mch/cpu rcrb that is attached to this rcrb. bit description 31:24 target port number (pn) ? ro. this field indicates that the target port number is 1h (root port #1). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, since the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. this bit indicates that the link points to a root port. 0 link valid (lv) ? ro. when fd.pe1d (offs et 3418h, bit 16) is set, this link is not valid (returns 0). when fd.pe1d is clea red, this link is valid (returns 1). www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 273 chipset configuration registers 10.1.17 rp1ba?root port 1 base address register offset address: 0128?012fh attribute: ro default value: 00000000000e0000h size: 64-bit 10.1.18 rp2d?root port 2 descriptor register offset address: 0130?0133h attribute: r/wo, ro default value: 02xx0002h size: 32-bit 10.1.19 rp2ba?root port 2 base address register offset address: 0138?013fh attribute: ro default value: 00000000000e1000h size: 64-bit bit description 63:32 reserved 31:28 reserved 27:20 bus number (bn) ? ro. this field indicates th e root port is on bus #0. 19:15 device number (dn) ? ro. this field indicates the root port is on device #28. 14:12 function number (fn) ? ro. this field indicates the root port is on function #0. 11:0 reserved bit description 31:24 target port number (pn) ? ro. this field indicates th e target port number is 2h (root port #2). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, sinc e the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. this bit indicates that the link points to a root port. 0 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 not valid (return 0). when rpc.pc is ?00? and fd.pe2d is cleared, the link for this root port is valid (return 1). bit description 63:32 reserved 31:28 reserved 27:20 bus number (bn) ? ro. this field indicates th e root port is on bus #0. 19:15 device number (dn) ? ro. this field indicates the root port is on device #28. 14:12 function number (fn) ? ro. this field indicates the root port is on function #1. 11:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 274 datasheet 10.1.20 rp3d?root port 3 descriptor register offset address: 0140?0143h attribute: r/wo, ro default value: 03xx0002h size: 32-bit 10.1.21 rp3ba?root port 3 base address register offset address: 0148?014fh attribute: ro default value: 00000000000e2000h size: 64-bit 10.1.22 rp4d?root port 4 descriptor register offset address: 0150?0153h attribute: r/wo, ro default value: 04xx0002h size: 32-bit bit description 31:24 target port number (pn) ? ro. this field indicates th e target port number is 3h (root port #3). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, since the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. this bit indicates that the link points to a root port. 0 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 th is root port is not valid (return 0). when rpc.pc is ?00?, ?01?, or ?10?, and fd.pe3d is cl eared, the link for this root port is valid (return 1). bit description 63:32 reserved 31:28 reserved 27:20 bus number (bn) ? ro. this field indicates th e root port is on bus #0. 19:15 device number (dn) ? ro. this field indicates the root port is on device #28. 14:12 function number (fn) ? ro. this field indi cates the root port is on function #2. 11:0 reserved bit description 31:24 target port number (pn) ? ro. this field indicates th e target port number is 4h (root port #4). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, since the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. this bit indicates that the link points to a root port. 0 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 not valid (return 0). when rpc.pc is ?00? or ?01? and fd.pe4d is cl eared, the link for this root port is valid (return 1). www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 275 chipset configuration registers 10.1.23 rp4ba?root port 4 base address register offset address: 0158?015fh attribute: ro default value: 00000000000e3000h size: 64-bit 10.1.24 hdd?intel hd audi o descriptor register offset address: 0160?0163h attribute: r/wo, ro default value: 15xx0002h size: 32-bit 10.1.25 hdba?intel hd audi o base address register offset address: 0168?016fh attribute: ro default value: 00000000000d8000h size: 64-bit bit description 63:32 reserved 31:28 reserved 27:20 bus number (bn) ? ro. this field indicates th e root port is on bus #0. 19:15 device number (dn) ? ro. this field indicates the root port is on device #28. 14:12 function number (fn) ? ro. this field indicates the root port is on function #3. 11:0 reserved bit description 31:24 t arget port number (pn) ? ro. this field indicates th e target port number is 15h (intel hd audio). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, sinc e the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. this bit indicates that the link points to a root port. 0 link valid (lv) ? ro. when 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). bit description 63:32 reserved 31:28 reserved 27:20 bus number (bn) ? ro. this field indicates th e root port is on bus #0. 19:15 device number (dn) ? ro. this field indicates the root port is on device #27. 14:12 function number (fn) ? ro. this field indicates the root port is on function #0. 11:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 276 datasheet 10.1.26 ilcl?internal link ca pabilities li st register offset address: 01a0?01a3h attribute: ro default value: 00010006h size: 32-bit 10.1.27 lcap?link capa bilities register offset address: 01a4?01a7h attribute: ro/ r/wo default value: 00012441h size: 32-bit bit description 31:20 next capability offset (next) ? ro. indicates this is the last item in the list. 19:16 capability version (cv) ? ro. this field indicates th e version of the capability structure. 15:0 capability id (cid) ? ro. this field indicates this is capability for dmi. bit description 31:18 reserved 17:15 nettop only l1 exit latency (el1) ? l1 not supported on dmi. 17:15 netbook only l1 exit latency (el1) ? ro. this field is set to 010b to indicate an exit latency of 2us to 4 us. 14:12 l0s exit latency (el0) ? r/wo. this field indicates that exit latency is 128 ns to less than 256 ns. 11:10 nettop only active state link pm support (aspm) ? r/wo. this field indicates that l0s is supported on dmi. 11:10 netbook only active state link pm support (aspm) ? r/wo. this field in dicates the level of active state power management on dmi. 00 = neither l0s nor l1s are supported 01 = l0s entry supported on dmi 10 = l1 entry supported on dmi 11 = both l0s and l1 supported on dmi 9:4 maximum link width (mlw) ? indicates the maximum link width is 4 ports. 3:0 maximum link speed (mls) ? indicates the link speed is 2.5 gb/s. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 277 chipset configuration registers 10.1.28 lctl?link control register offset address: 01a8?01a9h attribute: r/w default value: 0000h size: 16-bit 10.1.29 lsts?link status register offset address: 01aa?01abh attribute: ro default value: 0041h size: 16-bit bit description 15:8 reserved 7 extended synch (es) ? r/w. when set, this bit fo rces extended transmission of fts ordered sets when exitin g l0s prior to entering l0 and extra sequences (netbook only) at exit from l1 prior to entering l0. 6:2 reserved 1:0 nettop only active state link pm control (apmc) ? r/w. this field indicates whether dmi should enter l0s. 00 = disabled 01 = l0s entry enabled 10 = reserved 11 = reserved 1:0 netbook only active state link pm control (apmc) ? r/w. this field indicates whether dmi should enter l0s or l1 or both. 00 = disabled 01 = l0s entry enabled 10 = l1 entry enabled 11 = l0s and l1 entry enabled bit description 15:10 reserved 9:4 negotiated link width (nlw) ? ro. negotiated link width is x4 (000100b). netbook only: the chipset may also indi cate x2 (000010b), depending on cpu configuration. 3:0 link speed (ls) ? ro. link is 2.5 gb/s. www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 278 datasheet 10.1.30 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 7 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 priority port (hpp) ? r/w. this field controls wh ich port is enabled for high priority when the hpe bit in this register is set. 111 = reserved 110 = reserved 101 = reserved 100 = reserved 100 = port 4 010 = port 3 001 = port 2 000 = port 1 3:2 reserved 1:0 port configuration (pc) ? ro. this field controls how the pci bridges are organized in various modes of operation. fo r 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 acz_sdout (bit 1) and acz_sync (bit 0) when tp3 is not pulled low at the rising edge of pwrok. 11 = 1 x4, port 1 (x4) 10 = reserved 01 = reserved 00 = 4 x1s, port 1 (x1), port 2 (x1), port 3 (x1), port 4 (x1) these bits live in the resume we ll and are only reset by rsmrst#. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 279 chipset configuration registers 10.1.31 rpfn?root port function number for pci express root ports offset address:0238?023bhattribute: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 have 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 no t affected by the logical function number assignment and is associated with physical ports. bit description 31:15 reserved 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 r oot port function numbers. 11 reserved 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 r oot port function numbers. 7 reserved 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 r oot port function numbers. 3 reserved 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 r oot port function numbers. www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 280 datasheet 10.1.32 trsr?trap status register offset address: 1e00?1e03h attribute: r/wc, ro default value: 00000000h size: 32-bit 10.1.33 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 trapped and generated the smi# for software to read. 10.1.34 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 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 enable d 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 th e corresponding bit location in this register. 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 location 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 da ta. this field is undefined after trapping a read cycle. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 281 chipset configuration registers 10.1.35 iotrn ? i/o trap register (0-3) offset address: 1e80?1e87h register 0 attribute: r/w, ro 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 match the type specified in bit 48. 1 = trapping logic will operate on both read and write cycles. 48 read/write# (rwio) ? r/w. 0 = write 1 = read note: the value in this field does not matter 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 en ables 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 value in the corresponding address bit in a receiv ed cycle will be treated as a match. the corresponding bit in the addres s field, below, is ignored. the mask is only provided for the lower 6 bits of the dword address, al lowing 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 0 trap and smi# enable (trse) ? r/w. 0 = trapping and smi# logic disabled. 1 = the trapping logic specified in this register is enabled. www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 282 datasheet 10.1.36 tctl?tco configuration register offset address: 3000?3000h attribute: r/w default value: 00h size: 8-bit 10.1.37 d31ip?device 31 in terrupt pin register offset address: 3100?3103h attribute: r/w, ro default value: 00042210h size: 32-bit bit description 7 tco irq enable (ie) ? r/w. 0 = tco irq is disabled. 1 = tco irq is enabled, as sele cted by the tco_irq_sel field. 6:3 reserved 2:0 tco irq select (is) ? r/w. specifies on which irq the tco will internally 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 shar eable 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) note: when setting the these bits, the ie bit should be cleared to prevent glitching. note: when the interrupt is mapped to apic interrupts 9, 10 or 11, the apic should be programmed for active-h igh reception. when the interrupt is mapped to apic interrupts 20 through 23, the apic should be programmed for active- low reception. bit description 31:16 reserved 15:12 sm bus pin (smip) ? r/w. this field 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 283 chipset configuration registers 10.1.38 d30ip?device 30 in terrupt pi n register offset address: 3104?3107h attribute: r/w, ro default value: 00002100h size: 32-bit 10.1.39 d29ip?device 29 in terrupt pi n register offset address: 3108?310bh attribute: r/w default value: 10004321h size: 32-bit 11:8 sata pin (sip) ? r/w. this field 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 pci bridge pin (pcip) ? ro. currently, the pci br idge does not generate an interrupt, so this field is read-only and 0. bit description bit description 31:4 reserved 3:0 lpc bridge pin (lip) ? ro. currently, the lpc bri dge does not generate an interrupt, so this field is read-only and 0. bit description 31:28 ehci pin (eip) ? r/w. this field indicates which pin the ehci contro ller drives as its interrupt. 0h = no interrupt 1h = inta# (default) 2h = intb# 3h = intc# 4h = intd# 5h?fh = reserved 27:16 reserved 15:12 uhci #3 pin (u3p) ? r/w. this field indicates wh ich pin the uhci controller #3 (ports 6 and 7) drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# 3h = intc# 4h = intd# (default) 5h?fh = reserved www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 284 datasheet 10.1.40 d28ip?device 28 in terrupt pin register offset address: 310c?310fh attribute: r/w default value: 00214321h size: 32-bit 11:8 uhci #2 pin (u2p) ? r/w. this field indicates wh ich pin the uhci controller #2 (ports 4 and 5) drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# 3h = intc# (default) 4h = intd# 5h?fh = reserved 7:4 uhci #1 pin (u1p) ? r/w. this field indicates wh ich pin the uhci controller #1 (ports 2 and 3) drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# (default) 3h = intc# 4h = intd# 5h?fh = reserved 3:0 uhci #0 pin (u0p) ? r/w. this field indicates wh ich pin the uhci controller #0 (ports 0 and 1) drives as its interrupt. 0h = no interrupt 1h = inta# (default) 2h = intb# 3h = intc# 4h = intd# 5h?fh = reserved bit description bit description 31:16 reserved 15:12 pci express #4 pin (p4ip) ? r/w. this field indicate s which pin the pci express* port #4 drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# 3h = intc# 4h = intd# (default) 5h?fh = reserved 11:8 pci express #3 pin (p3ip) ? r/w. this field 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?fh = reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 285 chipset configuration registers 10.1.41 d27ip?device 27 in terrupt pi n register offset address: 3110?3113h attribute: r/w default value: 00000001h size: 32-bit 7:4 pci express #2 pin (p2ip) ? r/w. this field indicate s which pin the pci express port #2 drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# (default) 3h = intc# 4h = intd# 5h?fh = reserved 3:0 pci express #1 pin (p1ip) ? r/w.this field indicate s which pin the pci express port #1 drives as its interrupt. 0h = no interrupt 1h = inta# (default) 2h = intb# 3h = intc# 4h = intd# 5h?fh = reserved bit description bit description 31:4 reserved 3:0 intel hd audio pin (zip) ? r/w. this field indicate s 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 www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 286 datasheet 10.1.42 d31ir?device 31 in terrupt route register offset address: 3140?3141h attribute: r/w default value: 3210h size: 16-bit bit description 15 reserved 14:12 interrupt d pin route (idr) ? r/w. this field indicate s which physical pin on the chipset is connected to the intd# pi n 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. this field indicate s which physical pin on the chipset is connected to the intc# pi n reported for device 31 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. this field indicate s which physical pin on the chipset is connected to the intb# pi n reported for device 31 functions. 0h = pirqa# 1h = pirqb# (default) 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 3 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 287 chipset configuration registers 10.1.43 d30ir?device 30 in terrupt route register offset address: 3142?3143h attribute: r/w default value: 3210h size: 16-bit 2:0 interrupt a pin route (iar) ? r/w. this field indicates which physical pin on the chipset is connected to the inta# pi n reported for device 31 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# bit description bit description 15 reserved 14:12 interrupt d pin route (idr) ? r/w. this field indicate s which physical pin on the chipset is connected to the intd# pi n reported for device 30 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. this field indicate s which physical pin on the chipset is connected to the intc# pi n reported for device 30 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# (default) 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 7 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 288 datasheet 10.1.44 d29ir?device 29 in terrupt route register offset address: 3144?3145h attribute: r/w default value: 3210h size: 16-bit 6:4 interrupt b pin route (ibr) ? r/w. this field indicate s which physical pin on the chipset is connected to the intb# pi n reported for device 30 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. this field indicates which physical pin on the chipset is connected to the inta# pi n reported for device 30 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# bit description bit description 15 reserved 14:12 interrupt d pin route (idr) ? r/w. this field indicate s which physical pin on the chipset is connected to the intd# pi n reported for device 29 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# 3h = pirqd# (default) 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 11 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 289 chipset configuration registers 10:8 interrupt c pin route (icr) ? r/w. this field indicate s which physical pin on the chipset is connected to the intc# pi n 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. this field indicate s which physical pin on the chipset is connected to the intb# pi n 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. this field indicate s which physical pin on the chipset is connected to the inta# pi n reported for device 29 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# bit description www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 290 datasheet 10.1.45 d28ir?device 28 in terrupt route register 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. this field indicate s which physical pin on the chipset is connected to the intd# pi n 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. this field indicate s which physical pin on the chipset is connected to the intc# pi n 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. this field indicate s which physical pin on the chipset is connected to the intb# pi n 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. this field indicate s which physical pin on the chipset is connected to the inta# pi n reported for device 28 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 291 chipset configuration registers 10.1.46 d27ir?device 27 in terrupt 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. this field indicate s which physical pin on the chipset is connected to the intd# pi n 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. this field indicate s which physical pin on the chipset is connected to the intc# pi n 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. this field indicate s which physical pin on the chipset is connected to the intb# pi n 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. this field indicate s which physical pin on the chipset is connected to the inta# pi n reported for device 27 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 292 datasheet 10.1.47 oic?other interrupt control register offset address: 31ff?31ffh attribute: r/w default value: 00h size: 8-bit 10.1.48 rc?rtc configuration register offset address: 3400?3403h attribute: r/w, r/wlo default value: 00000000h size: 32-bit bit description 7:2 reserved 1 coprocessor error enable (cen) ? r/w. 0 = ferr# will not generate irq13 nor ignne#. 1 = if ferr# is low, the chipset generates irq13 internally and holds it until an i/o port f0h write. it will also drive ignne# active. 0 apic enable (aen) ? r/w. 0 = the internal ioxapic is disabled. 1 = enables the internal ioxa pic and its address decode. bit description 31:5 reserved 4 upper 128 byte lock (ul) ? r/wlo. 0 = bytes not locked. 1 = bytes 38h?3fh in the upper 128-byte bank of rtc ram are locked and cannot be accessed. writes will be dr opped and reads will not retu rn valid data. this bit is reset on system reset. 3 lower 128 byte lock (ll) ? r/wlo. 0 = bytes not locked. 1 = bytes 38h?3fh in the lower 128-byte bank of rtc ram are locked and cannot be accessed. writes will be dropped and reads will not return valid data. bit reset on system reset. 2 upper 128 byte enable (ue) ? r/w. 0 = bytes locked. 1 = the upper 128-byte bank of rtc ram can be accessed. 1:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 293 chipset configuration registers 10.1.49 hptc?high precision ti mer configuration register offset address: 3404?3407h attribute: r/w default value: 00000000h size: 32-bit 10.1.50 gcs?general contro l and status register offset address: 3410?3413h attribute:r/w, r/wlo default value: 00000yy0h (yy = xx0000x0b)size: 32-bit bit description 31:8 reserved 7 address enable (ae) ? r/w. 0 = address disabled. 1 = the chipset will decode th e high precision timer memory address range selected by bits 1:0 below. 6:2 reserved 1:0 address select (as) ? r/w. this field selects 1 of 4 possible memory address ranges for the high precision time r functionality. the encodings are: 00 = fed0_0000h ? fed0_03ffh 01 = fed0_1000h ? fed0_13ffh 10 = fed0_2000h ? fed0_23ffh 11 = fed0_3000h ? fed0_33ffh bit description 31:12 reserved 11:10 boot bios straps (bbs) : this field determines the destinatio n of accesses to the bios memory range. the default values for these bits represent the strap values of gnt5#/gpio17 (bit 11) and gnt4#/gpio48 (bit 10) (active-high logic levels) at the rising edge of pwrok. when pci is selected, the top 16 mb of memory below 4 gb (ff00_0000h to ffff_ffffh) is accepted by the primary side of the pci-to-pci bridge and forwarde d to the pci bus. this allows systems with corrupted or unprog rammed 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) for these cycles to go to pci. note that bios decode range bits and the other bi os protection bits have no effect when pci is selected. when spi or lpc is selected, the range that is de coded 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. bits 11:10 description 00b reserved 01b spi (supports shared flash with lan) 10b pci 11b lpc www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 294 datasheet 9 server error reporting mode (serm) ? r/w. 0 = the chipset is the final target of all errors . the (g)mch/cpu sends a messages to the chipset for the purpose of generating nmi. 1 = the (g)mch/cpu is the final targ et of all errors from pci express* and dmi. in this mode, if the chipset detects a fatal, non-fatal, or correctable error on dmi or its downstream ports, it sends a message to the (g)mch/cpu. if the chip set receives an e rr_* message from the downstream port, it sends that message to the (g)mch/cpu. 8:7 reserved 6 (netbook only) ferr# mux enable (fme) ? r/w. this bit enables ferr# to be a processor break event indication. 0 = disabled. 1 = the chipset examines ferr# during a c2, c3, or c4 state as a break event. see chapter 5.14.5 - volume 1 for a functional description. 6 (nettop only) reserved 5 no reboot (nr) ? r/w. this bit is set when the ?no reboot? strap (spkr pin on chipset) is sampled high on pwrok. this bit may be set or cl eared 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# on the first timeou t, but will not reboot on the second timeout. 4 alternate access mode enable (ame) ? r/w. 0 = disabled. 1 = alternate access read only registers can be writ ten, and write only regist ers can be read. before entering a low power state, several registers fro m 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, an d to restore data into read-only re gisters, the chipset implements an alternate access mode. for a list of these registers see section 5.14.10. 3 reserved . 2 reserved page route (rpr) ? r/w. this bit 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 with in the chipset, and read s will be returned from the internal shadow 1 = writes will be forwarded to pci, shadowed with in the chipset, and reads will be returned from the internal shadow. note: if some writes are completed to lpc/pci to th ese i/o ranges, and then this bit is flipped such that writes will now go to the other interface, the reads will not return what was last written. shadowing is perfo rmed 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 0 bios interface lock-down (bild) ? r/wlo. 0 = disabled. 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 295 chipset configuration registers 10.1.51 buc?backed up control register offset address: 3414?3414h attribute:r/w default value: 0000001xb all bits in this register are in the rtc well and only cleared by rtcrst#. 10.1.52 fd?function disable register offset address: 3418?341bh attribute: r/w, ro default value: see bit description size: 32-bit the uhci functions must be disabled from highest function number to lowest. for example, if only three uhcis are wanted, software must disable uhci #4 (ud4 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 config uration 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 di sabled prior to disabling 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 7:3 reserved 2 cpu bist enable (cbe) ? r/w. this bit is in the resume we ll 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 i/f signals (h old time after cpurst# inactive). 1 reserved 0 top swap (ts) ? r/w. 0 = chipset will not invert a16. 1 = chipset will invert a16 for cycles going to th e bios space (but not the feature space) in the fwh. if the chipset is strapped for top-swap (strap0# 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. bit description 31:20 reserved 19 pci express 4 disable (pe4d) ? r/w. when disabled, the link for this port is put into the ?link down? state. 0 = pci express* port #4 is enabled. (default) 1 = pci express port #4 is disabled. 18 pci express 3 disable (pe3d) ? r/w. when disabled, the link for this port is put into the link down state. 0 = pci express port #3 is enabled. (default) 1 = pci express port #3 is disabled. www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 296 datasheet 17 pci express 2 disable (pe2d) ? r/w. when disabled, the link for this port is put into the link down state. 0 = pci express port #2 is enabled. (default) 1 = pci express port #2 is disabled 16 pci express 1 disable (pe1d) ? r/w. when disabled, the link for this port is put into the link down state. 0 = pci express port #1 is enabled. (default) 1 = pci express port #1 is disabled. 15 ehci disable (ehcid) ? r/w. 0 = the ehci is enabled. (default) 1 = the ehci is disabled. 14 lpc bridge disable (lbd) ? r/w. 0 = the lpc bridge is enabled. (default) 1 = the lpc bridge is disabled. unlike the ot her 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 deco ded when this bit is set, but the aliases at the top of 1 mb (the e and f segment) no longer will be decoded. 13:12 reserved 11 uhci #4 disable (u4d) ? r/w. 0 = the 4th uhci (ports 6 an d 7) is enabled. (default) 1 = the 4th uhci (ports 6 and 7) is disabled. 10 uhci #3 disable (u3d) ? r/w. 0 = the 3rd uhci (ports 4 an d 5) is enabled. (default) 1 = the 3rd uhci (ports 4 and 5) is disabled. 9 uhci #2 disable (u2d) ? r/w. 0 = the 2nd uhci (ports 2 and 3) is enabled. (default) 1 = the 2nd uhci (ports 2 and 3) is disabled. 8 uhci #1 disable (u1d) ? r/w. 0 = the 1st uhci (ports 0 an d 1) is enabled. (default) 1 = the 1st uhci (ports 0 and 1) is disabled. 7 hide internal lan (hil) ? r/w. 0 = the lan controller is enabled. (default) 1 = the lan controller is disabled and will not decode configuration cycles off of p 6:5 reserved 4 intel hd audio disable (zd) ? r/w. 0 = the intel high definition audio controller is enabled. (default) 1 = the intel high definition audio controll er is disabled and its pci configuration space is not accessible. 3 sm bus disable (sd) ? r/w. 0 = the sm bus controller is enabled. (default) 1 = the sm bus controller is disabled. in ch ipset and previous, this also disabled the i/o space. in the chipset, it only disables the configuration space. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 297 chipset configuration registers 10.1.53 cg?clock gati ng (netbook only) offset address: 341c?341fh attribute: r/w, ro default value: 00000000h size: 32-bit 2 serial ata disable (sad) ? r/w. default is 0. 0 = the sata controller is enabled. 1 = the sata controller is disabled. 1:0 reserved bit description bit description 31 legacy (lpc) dynamic clock gate enable ? 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 uhci dynamic clock gating is disabled 1 = usb uhci dynamic cl ock gating is enabled 0 = reserved 1 = reserved 27:26 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 23 reserved 22 high definition audio dynamic clock gate enable ? r/w. 0 = high definition audio dynamic clock gating is disabled 1 = high definition audio dynamic clock gating is enabled 21 high definition audio static clock gate enable ? r/w. 0 = high definition audio static clock gating is disabled 1 = high definition audio static clock gating is enabled 20 usb ehci static clock gate enable ? r/w. 0 = usb ehci static cl ock 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:17 reserved 16 pci dynamic gate enable ? r/w. functionality reserved . bios must ensure bit is 0. 15:4 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
chipset configuration registers 298 datasheet 3 dmi 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 2 pci express tx dynamic clock gate enable ? r/w. 0 = pci express root port tx dy namic clock gating is disabled 1 = pci express root port tx dy namic clock gating is enabled 1 dmi tx dynamic clock gate enable ? r/w. 0 = dmi tx dynamic clock gating is disabled 1 = dmi tx dynamic clock gating is enabled 0 pci express root port static clock gate enable ? r/w. 0 = pci express root port stat ic clock gating is disabled 1 = pci express root port stat ic clock gating is enabled bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 299 lan controller registers (b1:d8:f0) 11 lan controller registers (b1:d8:f0) the chipset integrated lan controller appears to reside at pci device 8, function 0 on the secondary side of the chipset's virtual pci-to-pci bridge. this is typically bus 1, but may be assigned a different number depend ing upon system configuration. the lan controller acts as both a master and a slave on the pci bus. as a master, the lan controller interacts with the system main memory to access data for transmission or deposit received data. as a slave, some of the lan controller?s control structures are accessed by the host processor to read or write information to the on-chip registers. the processor also provides the lan controller with the necessary commands and pointers that allow it to process receive and transmit data. 11.1 pci configuration registers (lan controller?b1:d8:f0) note: address locations that are not shown should be treated as reserved (see section 9.2 for details). . table 11-111.lan controller pci register address map (lan controller?b1:d8: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 ro, r/w 06h?07h pcists pci status 0290h ro, r/wc 08h rid revision identification see register description. ro 0ah scc sub class code 00h ro 0bh bcc base class code 02 ro 0ch cls cache line size 00h r/w 0dh pmlt primary master latency timer 00h r/w 0eh headtyp header type 00h ro 10h?13h csr_mem_base csr memory?mapped base address 00000008h r/w, ro 14h?17h csr_io_base csr i/o?mapped base address 00000001h r/w, ro 2ch?2dh svid subsystem vendor identification 0000h ro 2eh?2fh sid subsystem identification 0000h ro 34h cap_ptr capabilities pointer dch ro 3ch int_ln interrupt line 00h r/w 3dh int_pn interrupt pin 01h ro www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 300 datasheet 11.1.1 vid?vendor identi fication register (lan controller?b1:d8:f0) offset address: 00h ? 01h attribute: ro default value: 8086h size: 16 bits 11.1.2 did?device identi fication register (lan controller?b1:d8:f0) offset address: 02h ? 03h attribute: ro default value: see bit description size: 16 bits 3eh min_gnt minimum grant 08h ro 3fh max_lat maximum latency 38h ro dch cap_id capability id 01h ro ddh nxt_ptr next item pointer 00h ro deh?dfh pm_cap power manage ment capabili ties fe21h ro e0h?e1h pmcsr power management control/ status 0000h r/w, ro, r/wc e3 pcidata pci power management data 00h ro table 11-111.lan controller pci register address map (lan controller?b1:d8: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. bit description 15:0 device id ? ro. this is a 16-bit value assigned to the chipset integrated lan controller. notes: 1. if the eeprom is not present (or not prop erly programmed), reads to the device id return the defa ult value referred to in the intel ? i/o controller hub 7 family specification update. 2. if the eeprom is present (and properly programmed) and if the value of word 23h is not 0000h or ffffh, the device id is loaded from the eeprom, word 23h after the hardware reset. (see section 11.1.4 - sid, subsystem id of lan controller for detail) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 301 lan controller registers (b1:d8:f0) 11.1.3 pcicmd?pci co mmand register (lan controller?b1:d8:f0) offset address: 04h ? 05h attribute: ro, r/w default value: 0000h size: 16 bits bit description 15:11 reserved 10 interrupt disable ? r/w. 0 = enable. 1 = disables lan controller to assert its inta signal. 9 fast back to back enable (fbe) ? ro. hardwired to 0. the integrated lan controller will not run fast back-to-back pci cycles. 8 serr# enable (serr_en) ? r/w. 0 = disable. 1 = enable. allow serr# to be asserted. 7 wait cycle control (wcc) ? ro. ha rdwired to 0. not implemented. 6 parity error response (per) ? r/w. 0 = the lan controller will ignore pci parity errors. 1 = the integrated lan controller will take normal action when a pci parity error is detected and will enable generation of parity on dmi. 5 vga palette snoop (vps) ? ro. hardwired to 0. not implemented. 4 memory write and invalidate enable (mwie) ? r/w. 0 = disable. the lan controller will not use the memory write and invalidate command. 1 = enable. 3 special cycle enable (sce) ? ro. hardwired to 0. the lan controller ignores special cycles. 2 bus master enable (bme) ? r/w. 0 = disable. 1 = enable. the chipset's integrated lan cont roller may function as a pci bus master. 1 memory space enable (mse) ? r/w. 0 = disable. 1 = enable. the chipset's integrated lan cont roller will respond to the memory space accesses. 0 i/o space enable (iose) ? r/w. 0 = disable. 1 = enable. the chipset's integrated lan co ntroller will respond to the i/o space accesses. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 302 datasheet 11.1.4 pcists?pci status register (lan controller?b1:d8:f0) offset address: 06h ? 07h attribute: ro, r/wc default value: 0290h 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 = parity error not detected. 1 = the chipset's integrated lan controller has detected a parity error on the pci bus (will be set even if parity error response is disabled in the pci command register). 14 signaled system error (sse) ? r/wc. 0 = integrated lan controller has not asserted serr# 1 = the chipset?s integrated lan controller has asserted serr#. serr# can be routed to cause nmi, smi#, or interrupt. 13 master abort status ( rma) ? r/wc. 0 = master abort not generated 1 = the chipset?s integrated lan controller (as a pci master) has generated a master abort. 12 received target abort (rta) ? r/wc. 0 = target abort not received. 1 = the chipset?s integrated lan controller (as a pci master) has received a target abort. 11 signaled target abort (sta) ? ro. hardwired to 0. the device will not signal target abort. 10:9 devsel# timing status (dev_sts) ? ro. 01h = medium timing. 8 data parity error detected (dped) ? r/wc. 0 = parity error not detected (condition s below are not met). 1 = all of the following thre e conditions have been met: 1. the lan controller is acting as bus master 2. the lan controller has asserted perr# (f or reads) or detected perr# asserted (for writes) 3. the parity error response bit in the la n controller?s pci command register is set. 7 fast back to back capable (fb2bc) ? ro. hardwired to 1. the device can accept fast back-to-back transactions. 6 user definable features (udf) ? ro . hardwired to 0. not implemented. 5 66 mhz capable (66mhz_cap) ? ro . hardwired to 0. the de vice does not support 66 mhz pci. 4 capabilities list (cap_list) ? ro. 0 = the eeprom indicates that the integrat ed lan controller does not support pci power management. 1 = the eeprom indicates that the integr ated lan controller supports pci power management. 3 interrupt status (ints) ? ro. this bit indicates that an interrupt is pe nding. it is independent from the state of the interru pt enable bit in th e command register. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 303 lan controller registers (b1:d8:f0) 11.1.5 rid?revision identification register (lan controller?b1:d8:f0) offset address: 08h attribute: ro default value: see bit description size: 8 bits 11.1.6 scc?sub class code register (lan controller?b1:d8:f0) offset address: 0ah attribute: ro default value: 00h size: 8 bits 11.1.7 bcc?base-class code register (lan controller?b1:d8:f0) offset address: 0bh attribute: ro default value: 02h size: 8 bits 2:0 reserved bit description bit description 7:0 revision id (rid) ? ro. this field is an 8-bit va lue that indicates the revision number for the integrated lan controller. the three least significant bits in this register may be overridden by the id and rev id fields in the ee prom. refer to the intel ? i/o controller hub 7 family specification update for the value of the revision id register. bit description 7:0 sub class code (scc) ? ro . this 8-bit value specifies the sub-class of the device as an ethernet controller. bit description 7:0 base class code (bcc) ? ro . this 8-bit value specifies the base class of the device as a network controller. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 304 datasheet 11.1.8 cls?cache line size register (lan controller?b1:d8:f0) offset address: 0ch attribute: r/w default value: 00h size: 8 bits 11.1.9 pmlt?primary master latency timer register (lan controller?b1:d8:f0) offset address: 0dh attribute: r/w default value: 00h size: 8 bits 11.1.10 headtyp?header type register (lan controller?b1:d8:f0) offset address: 0eh attribute: ro default value: 00h size: 8 bits bit description 7:5 reserved 4:3 cache line size (cls) ? r/w. 00 = memory write and invalidate (mwi) comm and will not be used by the integrated lan controller. 01 = mwi command will be used with cache line size set to 8 dwords (only set if a value of 08h is written to this register). 10 = mwi command will be used with cache line size set to 16 dwords (only set if a value of 10h is written to this register). 11 = invalid. mwi comman d will not be used. 2:0 reserved bit description 7:3 master latency timer count (mltc) ? r/w. this field defines the number of pci clock cycles that the integrated lan controller may own the bus while acting as bus master. 2:0 reserved bit description 7 multi-function device (mfd) ? ro . hardwired to 0 to indicate a single function device. 6:0 header type (htype) ? ro . this 7-bit field identifies the header layout of the configuration space as an ethernet controller. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 305 lan controller registers (b1:d8:f0) 11.1.11 csr_mem_base ? cs r memory-mapped base address register (lan controller?b1:d8:f0) offset address: 10h ? 13h attribute: r/w, ro default value: 00000008h size: 32 bits note: the chipset?s integrated lan controller requires one bar for memory mapping. software determines which bar (memory or i/o) is used to access the lan controller?s csr registers. 11.1.12 csr_io_base ? csr i/o- mapped base address register (lan controller?b1:d8:f0) offset address: 14h ? 17h attribute: r/w, ro default value: 00000001h size: 32 bits note: the chipset?s integrated lan controller requires one bar for memory mapping. software determines which bar (memory or i/o) is used to access the lan controller?s csr registers. bit description 31:12 base address (mem_addr) ? r/w. this field contains the u pper 20 bits of the base address provides 4 kb of memory-mapped spac e for the lan controller?s control/status registers. 11:4 reserved 3 prefetchable (mem_pf) ? ro . hardwired to 0 to indicate that this is not a pre- fetchable memory-mapped address range. 2:1 type (mem_type) ? ro . hardwired to 00b to indica te the memory-mapped address range may be located anywhere in 32-bit address space. 0 memory-space indicator (mem_space) ? ro . hardwired to 0 to indicate that this base address maps to memory space. bit description 31:16 reserved 15:6 base address (io_addr) ? r/w. this field provides 64 by tes of i/o-ma pped address space for the lan controller?s control/status registers. 5:1 reserved 0 i/o space indicator (io_space) ? ro . hardwired to 1 to indicate that this base address maps to i/o space. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 306 datasheet 11.1.13 svid ? subsystem vendor identification (lan controller?b1:d8:f0) offset address: 2ch ? 2d attribute: ro default value: 0000h size: 16 bits 11.1.14 sid ? subsystem identification (lan controller?b1:d8:f0) offset address: 2eh ? 2fh attribute: ro default value: 0000h size: 16 bits note: the chipset?s integrated lan controller provid es support for configurable subsystem id and subsystem vendor id fields. after rese t, the lan controller automatically reads addresses ah through ch, and 23h of the eeprom. the lan controller checks bits 15:13 in the eeprom word ah, and functions according to table 11-112 . notes: 1. the device id is loaded from word 23h only if the value of word 23h is not 0000h or ffffh 2. the revision id is subject to chan ge according to th e silicon stepping. 11.1.15cap_ptr ? capabilities pointer (lan controller?b1:d8:f0) offset address:34hattribute: ro default value: dch size: 8 bits bit description 15:0 subsystem vendor id (svid) ? ro . see section 11.1.14 for details. bit description 15:0 subsystem id (sid) ? ro . table 11-112.configuration of subsystem id and subsys tem vendor id via eeprom bits 15:14 bit 13 device id 1 vendor id revision id 2 subsystem id subsystem vendor id 11b, 10b, 00b x 1051h 8086h 00h 0000h 0000h 01b 0b word 23h 8086h 00h word bh word ch 01b 1b word 23h word ch 80h + word ah, bits 10:8 word bh word ch bit description 7:0 capabilities pointer (cap_ptr) ? ro . hardwired to dch to indicate the offset within configuration space for the locati on of the power ma nagement registers. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 307 lan controller registers (b1:d8:f0) 11.1.16 int_ln ? interr upt line register (lan controller?b1:d8:f0) offset address: 3ch attribute: r/w default value: 00h size: 8 bits 11.1.17 int_pn ? interrupt pin register (lan controller?b1:d8:f0) offset address: 3dh attribute: ro default value: 01h size: 8 bits 11.1.18 min_gnt ? mini mum grant register (lan controller?b1:d8:f0) offset address: 3eh attribute: ro default value: 08h size: 8 bits 11.1.19 max_lat ? maximu m latency register (lan controller?b1:d8:f0) offset address: 3fh attribute: ro default value: 38h size: 8 bits bit description 7:0 interrupt line (int_ln) ? r/w. this field identifies the system interrupt line to which the lan controller?s pci interrupt re quest pin (as defined in the interrupt pin register) is routed. bit description 7:0 interrupt pin (int_pn) ? ro . hardwired to 01h to indicate that the lan controller?s interrupt request is connected to pirqa#. however, in the chipset implementation, when the lan controller interru pt is generated pirqe# will go active, not pirqa#. note that if the pirqe# signal is used as a gpi, the external visibility will be lost (though pirqe# will still go active internally). bit description 7:0 minimum grant (min_gnt) ? ro . this field indicates the amount of time (in increments of 0.25 s) that the lan controller needs to retain ownership of the pci bus when it initiates a transaction. bit description 7:0 maximum latency (max_lat) ? ro . this field defines how often (in increments of 0.25 s) the lan controller needs to access the pci bus. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 308 datasheet 11.1.20 cap_id ? capability identification register (lan controller?b1:d8:f0) offset address: dch attribute: ro default value: 01h size: 8 bits 11.1.21 nxt_ptr ? ne xt item pointer (lan controller?b1:d8:f0) offset address: ddh attribute: ro default value: 00h size: 8 bits 11.1.22 pm_cap ? power ma nagement capabilities (lan controller?b1:d8:f0) offset address: deh ? dfh attribute: ro default value: 7e21h size: 16 bits bit description 7:0 capability id (cap_id) ? ro . hardwired to 01h to indicate that the chipset?s integrated lan controller su pports pci power management. bit description 7:0 next item pointer (nxt_ptr) ? ro . hardwired to 00b to indicate that power management is the last item in the capabilities list. bit description 15:11 pme support (pme_sup) ? ro . hardwired to 11111b. this 5-bit field indicates the power states in which the lan controller may assert pme#. the lan controller supports wake-up in all power states. 10 d2 support (d2_sup) ? ro . hardwired to 1 to indicate that the lan controller supports the d2 power state. 9 d1 support (d1_sup) ? ro . hardwired to 1 to indicate that the lan controller supports the d1 power state. 8:6 auxiliary current (aux_cur) ? ro . hardwired to 000b to indicate that the lan controller implements the data registers. the auxiliary power consumption is the same as the current consumption reported in the d3 stat e in the data register. 5 device specific initialization (dsi) ? ro . hardwired to 1 to indicate that special initialization of this function is required (beyond the standard pci configuration header) before the generic class device driver is able to use it. dsi is required for the lan controller after d3-to-d0 reset. 4 reserved 3 pme clock (pme_clk) ? ro . hardwired to 0 to indicate that the lan controller does not require a clock to genera te a power management event. 2:0 version (ver) ? ro . hardwired to 010b to indicate that the lan controller complies with of the pci power management specification, revision 1.1. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 309 lan controller registers (b1:d8:f0) 11.1.23 pmcsr ? power management control/ status register (lan controller?b1:d8:f0) offset address: e0h ? e1h attribute: ro, r/w, r/wc default value: 0000h size: 16 bits bit description 15 pme status (pme_stat) ? r/wc. 0 = software clears this bit by writing a 1 to it. this also deasserts the pme# signal and clears the pme status bit in the power management driver register. when the pme# signal is enabled, th e pme# signal reflects the state of the pme status bit. 1 = set upon occurrence of a wake-up event, independent of the state of the pme enable bit. 14:13 data scale (dscale) ? ro. this field indicates the data register scaling factor. it equals 10b for registers 0 through 8 and 00 b for registers nine through fifteen, as selected by the ?data select? field. 12:9 data select (dsel) ? r/w. this field is used to select which data is reported through the data register and data scale field. 8 pme enable (pme_en) ? r/w. this bit enables the chipset?s integrated lan controller to assert pme#. 0 = the device will not assert pme#. 1 = enable pme# assertion when pme status is set. 7:5 reserved 4 dynamic data (dyn_dat) ? ro . hardwired to 0 to indicate that the device does not support the ability to monitor the power consumption dynamically. 3:2 reserved 1:0 power state (pwr_st) ? r/w. this 2-bit field is used to determine the current power state of the integrated lan controller, and to put it into a new power state. the definition of the field values is as follows: 00 = d0 01 = d1 10 = d2 11 = d3 www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 310 datasheet 11.1.24 pcidata ? pci power ma nagement data register (lan controller?b1:d8:f0) offset address: e3h attribute: ro default value: 00h size: 8 bits the data register is an 8-bit read only register that provides a mechanism for the chipset?s integrated lan controller to report state dependent maximum power consumption and heat dissipation. the value reported in this register depends on the value written to the data select field in the pmcsr register. the power measurements defined in this register have a dynamic rang e of 0 w to 2.55 w with 0.01 w resolution, scaled according to the data scale field in the pmcsr. the structure of the data register is given in table 11-113 . 11.2 lan control / status registers (csr) (lan controller?b1:d8:f0) bit description 7:0 power management data (pwr_mgt) ? ro . state dependent power consumption and heat dissipation data. table 11-113.data register structure data select data scale data reported 0 2 d0 power consumption 1 2 d1 power consumption 2 2 d2 power consumption 3 2 d3 power consumption 4 2 d0 power dissipated 5 2 d1 power dissipated 6 2 d2 power dissipated 7 2 d3 power dissipated 8 2 common function power dissipated 9?15 0 reserved table 11-114.chipset integrated lan co ntroller csr space register address map offset mnemonic register name default type 00h?01h scb_sta system control block status word 0000h r/wc, ro 02h?03h scb_cmd system control block command word 0000h r/w, wo 04h?07h scb_genpnt system control block general pointer 0000 0000h r/w www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 311 lan controller registers (b1:d8:f0) 11.2.1 scb_sta?system control block status word register (lan controller?b1:d8:f0) offset address: 00h ? 01h attribute: r/wc, ro default value: 0000h size: 16 bits the chipset?s integrated lan controller places the status of its command unit (cu) and receive unit (rc) and interrupt indications in this register for the processor to read. 08h?0bh port port interface 0000 0000h r/w (special) 0ch? 0dh ? reserved ?? 0eh eeprom_cntl eeprom control 00 r/w, ro, wo 0fh ? reserved ?? 10h?13h mdi_cntl managem ent data interface control 0000 0000h r/w (special) 14h?17h rec_dma_bc receive dma byte count 0000 0000h ro 18h erec_intr early receive interrupt 00h r/w 19?1ah flow_cntl flow control 0000h ro, r/w (special) 1bh pmdr power management driver 00h r/wc 1ch gencntl general control 00h r/w 1dh gensta general status 00h ro 1eh ? reserved ?? 1fh smb_pci smb via pci 27h r/w 20h?3ch ? reserved ?? table 11-114.chipset integrated lan cont roller csr space register address map offset mnemonic register name default type bit description 15 command unit (cu) executed (cx) ? r/wc. 0 = software acknowledges the in terrupt and clears this bit by writing a 1 to the bit position. 1 = interrupt signaled because the cu ha s completed executing a command with its interrupt bit set. 14 frame received (fr) ? r/wc. 0 = software acknowledges the in terrupt and clears this bit by writing a 1 to the bit position. 1 = interrupt signaled because the receive unit (ru) has finished receiving a frame. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 312 datasheet 13 cu not active (cna) ? r/wc. 0 = software acknowledges the interrupt and cl ears this bit by writing a 1 to the bit position. 1 = the command unit left the active state or entered the idle state. there are 2 distinct states of the cu. when configured to generate cna interrupt, the interrupt will be activated when the cu leaves the active state and enters either the idle or the suspended state. when configured to ge nerate ci interrupt, an interrupt will be generated only when the cu enters the idle state. 12 receive not ready (rnr) ? r/wc. 0 = software acknowledges the interrupt and cl ears this bit by writing a 1 to the bit position. 1 = interrupt signaled because the receive unit left the ready state. this may be caused by an ru abort command, a no resources situation, or set suspend bit due to a filled receive frame descriptor. 11 management data interrupt (mdi) ? r/wc. 0 = software acknowledges the interrupt and cl ears this bit by writing a 1 to the bit position. 1 = set when a management data interface read or write cycle has completed. the management data interrupt is enabled through the interru pt enable bit (bit 29 in the management data interface control register in the csr). 10 software interrupt (swi) ? r/wc. 0 = software acknowledges the interrupt and cl ears this bit by writing a 1 to the bit position. 1 = set when software generates an interrupt. 9 early receive (er) ? r/wc. 0 = software acknowledges the interrupt and cl ears this bit by writing a 1 to the bit position. 1 = indicates the occurrence of an early receive interrupt. 8 flow control pause (fcp) ? r/wc. 0 = software acknowledges the interrupt and cl ears this bit by writing a 1 to the bit position. 1 = indicates flow co ntrol pause interrupt. 7:6 command unit status (cus) ? ro. 00 = idle 01 = suspended 10 = lpq (low priority queue) active 11 = hpq (high priority queue) active 5:2 receive unit status (rus) ? ro. bit description value status value status 0000b idle 1000b reserved 0001b suspended 1001b suspended with no more rbds 0010b no resources 1010b no resources due to no more rbds 0011b reserved 1011b reserved 0100b ready 1100b ready with no rbds present 0101b reserved 1101b reserved 0110b reserved 1110b reserved 0111b reserved 1111b reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 313 lan controller registers (b1:d8:f0) 11.2.2 scb_cmd?system control block command word register (lan controller?b1:d8:f0) offset address: 02h ? 03h attribute: r/w, wo default value: 0000h size: 16 bits the processor places commands for the command and receive units in this register. interrupts are also acknowledged in this register. 1:0 reserved bit description bit description 15 cx mask (cx_msk) ? r/w. 0 = interrupt not masked. 1 = disable the generati on of a cx interrupt. 14 fr mask (fr_msk) ? r/w. 0 = interrupt not masked. 1 = disable the generation of an fr interrupt. 13 cna mask (cna_msk) ? r/w. 0 = interrupt not masked. 1 = disable the generation of a cna interrupt. 12 rnr mask (rnr_msk) ? r/w. 0 = interrupt not masked. 1 = disable the generation of an rnr interrupt. 11 er mask (er_msk) ? r/w. 0 = interrupt not masked. 1 = disable the generation of an er interrupt. 10 fcp mask (fcp_msk) ? r/w. 0 = interrupt not masked. 1 = disable the generation of an fcp interrupt. 9 software generated interrupt (si) ? wo. 0 = no effect. 1 = setting this bit causes the lan co ntroller to generate an interrupt. 8 interrupt mask (im) ? r/w. this bit enables or di sables the lan controller?s assertion of the inta# signal. this bit has higher precedence that the specific interrupt mask bits and the si bit. 0 = enable the assertion of inta#. 1 = disable the assertion of inta#. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 314 datasheet 7:4 command unit command (cuc) ? r/w. valid values are listed below. all other values are reserved . 0000 = nop: does not affect the cu rrent state of the unit. 0001 = cu start : start execution of the first command on the cbl. a pointer to the first cb of the cbl should be placed in the scb general pointer before issuing this command. the cu start command should only be issued when the cu is in the idle or suspended states (not when th e cu is in the active state), and all of the previously issued command blocks have been processed and completed by the cu. sometimes it is only possible to determine that all command blocks are completed by checking that the complete bit is set in all previously issued command blocks. 0010 = cu resume: resume operation of the command unit by executing the next command. this command will be ignored if the cu is idle. 0011 = cu hpq start: start execution of the first comm and on the high priority cbl. a pointer to the first cb of the hpq cb l should be placed in the scb general pointer before issuing this command. 0100 = load dump counters address: indicates to the device where to write dump data when using the dump statistical counters or dump and reset statistical counters commands. this command must be executed at least once before any usage of the dump statistical counters or dump and reset statistical counters commands. the address of the dump area must be placed in the general pointer register. 0101 = dump statistical counters: tells the device to dump its statistical counters to the area designated by the lo ad dump counters address command. 0110 = load cu base: the device?s internal cu base register is loaded with the value in the csb general pointer. 0111 = dump and reset statistical counters: indicates to the de vice to dump its statistical counters to the area designated by the load dump counters address command, and then to clear these counters. 1010 = cu static resume: resume operation of the command unit by executing the next command. this comman d will be ignored if the cu is idle. this command should be used only when the cu is in the suspended state and has no pending cu resume commands. 1011 = cu hpq resume: resume execution of the firs t command on the hpq cbl. this command will be ignore d if the hpq was not started. 3 reserved bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 315 lan controller registers (b1:d8:f0) 11.2.3 scb_genpnt?system cont rol block general pointer register (lan controller?b1:d8:f0) offset address: 04h ? 07h attribute: r/w default value: 0000 0000h size: 32 bits 11.2.4 port?port interface register (lan controller?b1:d8:f0) offset address: 08h ? 0bh attribute: r/w (special) default value: 0000 0000h size: 32 bits the port interface allows the processor to re set the chipset?s internal lan controller, or perform an internal self test. the port dw ord may be written as a 32-bit entity, two 16-bit entities, or four 8-bit entities. the lan controller will only accept the command after the high byte (offset 0bh) is written; therefore, the high byte must be written last. 2:0 receive unit command ( ruc) ? r/w. valid values are: 000 = nop: does not affect the curre nt state of the unit. 001 = ru start: enables the receive unit. the pointer to the rfa must be placed in the scb general pointer before using this command. the device pre-fetches the first rfd and the first rbd (if in flexible mode) in preparation to receive incoming frames that pass its address filtering. 010 = ru resume: resume frame reception (only when in suspended state). 011 = rcv dma redirect: resume the rcv dma when configured to ?direct dma mode.? the buffers are indicated by an rbd chain which is pointed to by an offset stored in the general pointer register (this offset will be added to the ru base). 100 = ru abort: abort ru receive operation immediately. 101 = load header data size (hds): this value defines the size of the header portion of the rfds or receive buffers. the hds value is defined by the lower 14 bits of the scb general pointer, so bits 31:15 should always be set to 0?s when using this command. once a load hds command is issued, the device expects only to find header rfds, or be used in ?rcv direct dma mode? until it is reset. note that the value of hd s should be an even, non-zero number. 110 = load ru base: the device?s internal ru base re gister is loaded with the value in the scb general pointer. 111 = rbd resume: resume frame reception into the rfa. this command should only be used when the ru is already in the ?no resources due to no rbds? state or the ?suspended wi th no more rbds? state. bit description bit description 15:0 scb general pointer ? r/w. the scb general pointer register is programmed by software to point to various data structures in main memo ry depending on the current scb command word. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 316 datasheet bit description 31:4 pointer field (port_ptr) ? r/w (special). a 16-byte aligned address must be written to this field when issuing a self-test command to the port interface.the results of the self test will be written to the address specified by this field. 3:0 port function selection (port_func) ? r/w (special). valid values are listed below. all other values are reserved . 0000 = port software reset: completely resets the lan controller (all csr and pci registers). this command should not be used when the device is active. if a port software reset is desired, so ftware should do a selective reset (described below), wait for the port regi ster to be cleared (completion of the selective reset), and then issue the po rt software reset command. software should wait approximately 10 s after issuing this comm and before attempting to access the lan controller?s registers again. 0001 = self test: the self-test begins by issuing an internal selective reset followed by a general internal self-test of the la n controller. the results of the self-test are written to memory at the address sp ecified in the pointer field of this register. the format of the se lf-test result is shown in table 11-115 . after completing the self-test and writing the results to memory, the lan controller will execute a full internal reset and will re-initialize to the default configuration. self-test does not generate an interru pt of similar indicator to the host processor upon completion. 0010 = selective reset: sets the cu and ru to the idle state, but otherwise maintains the current configuration parameters (ru and cu base, hdssize, error counters, configure information an d individual/multica st addresses are preserved). software shou ld wait approximately 10 s after issuing this command before attempting to access the lan controller?s registers again. table 11-115.self-te st results format bit description 31:13 reserved 12 general self-test result (self_tst) ? r/w (special). 0 = pass 1 = fail 11:6 reserved 5 diagnose result (diag_rslt) ? r/w (special). this bit pr ovides the result of an internal diagnostic test of the serial subsystem. 0 = pass 1 = fail 4 reserved 3 register result (reg_rslt) ? r/w (special). this bit provides the result of a test of the internal parallel subsystem registers. 0 = pass 1 = fail 2 rom content result (rom_rslt) ? r/w (special). this bit provides the result of a test of the internal microcode rom. 0 = pass 1 = fail 1:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 317 lan controller registers (b1:d8:f0) 11.2.5 eeprom_cntl?eepro m control register (lan controller?b1:d8:f0) offset address: 0eh attribute: ro, r/w, wo default value: 00h size: 8 bits the eeprom control register is a 16-bit field that enables a read from and a write to the external eeprom. 11.2.6 mdi_cntl?management da ta interface (mdi) control register (lan controller?b1:d8:f0) offset address: 10h ? 13h attribute: r/w (special) default value: 0000 0000h size: 32 bits the management data interface (mdi) control register is a 32-bit field and is used to read and write bits from the lan connect comp onent. this register may be written as a 32-bit entity, two 16-bit entities, or four 8-bit entities. the lan controller will only accept the command after the high byte (offset 13h) is written; therefore, the high byte must be written last. bit description 7:4 reserved 3 eeprom serial data out (eedo) ? ro. note that this bit represents ?data out? from the perspective of the eeprom device. this bit cont ains the value read from the eeprom when performing read operations. 2 eeprom serial data in (eedi) ? wo. note that this bit represents ?data in? from the perspective of the eeprom device. the value of this bit is written to the eeprom when performing write operations. 1 eeprom chip select (eecs) ? r/w. 0 = drives the chipset?s ee_cs signal low to di sable the eeprom. this bit must be set to 0 for a minimum of 1 s between consecutive instruction cycles. 1 = drives the chipset?s ee_cs sign al high, to enable the eeprom. 0 eeprom serial clock (eesk) ? r/w. toggling this bit clocks data into or out of the eeprom. software must ensure that this bit is toggled at a rate that meets the eeprom component?s minimum clock frequency specification. 0 = drives the chipset?s ee_shclk signal low. 1 = drives the chipset?s ee_shclk signal high. bit description 31:30 these bits are reserved and should be set to 00b. 29 interrupt enable ? r/w (special). 0 = disable. 1 = enables the lan controller to assert an interrupt to indicate the end of an mdi cycle. 28 ready ? r/w (special). 0 = expected to be reset by software at the same time the command is written. 1 = set by the lan controller at the end of an mdi transaction. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 318 datasheet 11.2.7 rec_dma_bc?receive dm a byte count register (lan controller?b1:d8:f0) offset address: 14h ? 17h attribute: ro default value: 0000 0000h size: 32 bits 11.2.8 erec_intr?early rece ive interrupt register (lan controller?b1:d8:f0) offset address: 18h attribute: r/w default value: 00h size: 8 bits the early receive interrupt register allows the internal lan controller to generate an early interrupt depending on the length of the frame. the lan controller will generate an interrupt at the end of the frame regardless of whether or not early receive interrupts are enabled. note: it is recommended that software not use this register unless receive interrupt latency is a critical performance issue in that particular software environment. using this feature may reduce receive interrupt latency, but will also result in the generation of more interrupts, which can degrade system efficiency and performance in some environments. 27:26 opcode ? r/w (special). these bits define the opcode: 00 = reserved 01 = mdi write 10 = mdi read 11 = reserved 25:21 lan connect address ? r/w (special). this field of bits contains the lan connect address. 20:16 lan connect register address ? r/w (special). this field contains the lan connect register address. 15:0 data ? r/w (special). in a write command, software places the data bits in this field, and the lan controller transfers the data to the external lan connect component. during a read command, the lan controller reads these bits serially from the lan connect, and software reads the data from this location. bit description bit description 31:0 receive dma byte count ? ro. this field keeps track of how many bytes of receive data have been passed into host memory via dma. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 319 lan controller registers (b1:d8:f0) 11.2.9 flow_cntl?flow control register (lan controller?b1:d8:f0) offset address: 19h ? 1ah attribute: ro, r/w (special) default value: 0000h size: 16 bits bit description 7:0 early receive count ? r/w. when some non-zero value x is programmed into this register, the lan controller will set the er bit in the scb status word register and assert inta# when the byte count indicates that there are x qwords remaining to be received in the current frame (based on the type/len gth field of the received frame). no early receive interrupt will be generated if a valu e of 00h (the default value) is programmed into this register. bit description 15:13 reserved 12 fc paused low ? ro. 0 = cleared when the fc timer reache s 0, or a pause frame is received. 1 = set when the lan controller receives a pause low command with a value greater than 0. 11 fc paused ? ro. 0 = cleared when the fc timer reaches 0. 1 = set when the lan controller receives a pause command regardless of its cause (fifo reaching flow control threshold, fetching a receiv e frame descriptor with its flow control pause bit set, or soft ware writing a 1 to the xoff bit). 10 fc full ? ro. 0 = cleared when the fc timer reaches 0. 1 = set when the lan controller sends a pause command with a value greater than 0. 9 xoff ? r/w (special). this bit should only be us ed if the lan controller is configured to operate with ieee frame-based flow control. 0 = this bit can only be cleare d by writing a 1 to the xon bi t (bit 8 in this register). 1 = writing a 1 to this bit forces the xoff re quest to 1 and causes the lan controller to behave as if the fifo extender is full. this bit will also be set to 1 when an xoff request due to an ?rfd xoff? bit. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 320 datasheet 11.2.10 pmdr?power management driver register (lan controller?b1:d8:f0) offset address: 1bh attribute: r/wc default value: 00h size: 8 bits the chipset?s internal lan controller provides an indication in the pmdr that a wake-up event has occurred. 8 xon ? wo. this bit should only be used if th e lan controller is configured to operate with ieee frame-ba sed flow control. 0 = this bit always returns 0 on reads. 1 = writing a 1 to this bit resets the xoff requ est to the lan controller, clearing bit 9 in this register. 7:3 reserved 2:0 flow control threshold ? r/w. the lan controller can generate a flow control pause frame when its receive fifo is almost fu ll. the value programmed into this field determines the number of bytes still available in the receive fifo when the pause frame is generated. bit description bits 2:0 free bytes in rx fifo comment 000b 0.50 kb fast system (recommended default) 001b 1.00 kb 010b 1.25 kb 011b 1.50 kb 100b 1.75 kb 101b 2.00 kb 110b 2.25 kb 111b 2.50 kb slow system bit description 7 link status change indication ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = the link status change bit is set following a change in link status. 6 magic packet ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set when a magic packet is received regardless of the magic packet wake- up disable bit in the configuration command and the pme enable bit in the power management control/ status register. 5 interesting packet ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set when an ?interesting? pa cket is received. in teresting packets are defined by the lan controller packet filters. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 321 lan controller registers (b1:d8:f0) 11.2.11 gencntl?genera l control register (lan controller?b1:d8:f0) offset address: 1ch attribute: r/w default value: 00h size: 8 bits 11.2.12 gensta?general status register (lan controller?b1:d8:f0) offset address: 1dh attribute: ro default value: 00h size: 8 bits 4:3 reserved 2 asf enabled ? ro. this bit is set to 1 when th e lan controller is in asf mode. 1 tco request ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = this bit is set to 1b when the lan controller is busy with tco activity. 0 pme status ? r/wc. this bit is a reflection of th e pme status bit in the power management control/status register (pmcsr). 0 = software clears this bit by writing a 1 to it.this also clears the pme status bit in the pmcsr and deasserts the pme signal. 1 = set upon a wake-up event, independent of the pme enable bit. bit description bit description 7:4 reserved . these bits should be set to 0000b. 3 lan connect software reset ? r/w. 0 = cleared by software to begin normal lan connect operating mode. software must not attempt to access the lan connect interface for at least 1ms after clearing this bit. 1 = software can set this bit to force a reset condition on the lan connect interface. 2 reserved . this bit should be set to 0. 1 deep power-down on link down enable ? r/w. 0 = disable 1 = enable. the chipset?s internal lan cont roller may enter a d eep power-down state (sub-3 ma) in the d2 and d3 power states while the link is down. in this state, the lan controller does not keep link integrity. this state is not supported for point-to- point connection of two end stations. 0 reserved bit description 7:3 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 322 datasheet 11.2.13 smb_pci?smb via pci register (lan controller?b1:d8:f0) offset address: 1fh attribute: r/w, ro default value: 27h size: 8 bits software asserts sreq when it wants to isolate the pci-accessible smbus to the asf registers/commands. it waits for sgnt to be asserted. at this point scli, sdao, sclo, and sdai can be toggled/read to force asf controller smbus transactions without affecting the external smbus. after all operat ions are completed, the bus is returned to idle (sclo=1b,sdao=1b, scli=1b, sdai=1b), sreq is released (written 0b). then sgnt goes low to indicate released control of the bus. the logic in the asf controller only asserts or deasserts sgnt at times when it determines that it is safe to switch (all smbuses that are switched in/out are idle). when in isolation mode (sgnt=1), software can access the chipset smbus slaves that allow configuration without affecting the exte rnal smbus. this includes configuration register accesses and asf command accesses. however, this capability is not available to the external tco controller. when sgnt=0, the bit-banging and reads are reflected on the main smbus and the pcisml_s da0, pcisml_scl0 read only bits. 11.2.14 statistical counters (lan controller?b1:d8:f0) the chipset?s integrated lan controller prov ides information for network management statistics by providing on-chip statistical counters that count a variety of events associated with both transmit and receiv e. the counters are updated by the lan controller when it completes the processing of a frame (that is, when it has completed transmitting a frame on the link or when it has completed receiving a frame). the 2 duplex mode ? ro. this bit indicates th e wire duplex mode. 0 = half duplex 1 = full duplex 1 speed ? ro. this bit indicates the wire speed. 0 = 10 mb/s 1 = 100 mb/s 0 link status indication ? ro. this bit indicates the status of the link. 0 = invalid 1 = valid bit description 7:6 reserved 5 pcisml_sclo ? ro. smbus clock from the asf controller. 4 pcisml_sgnt ? ro. smbus isolation grant from the asf controller. 3 pcisml_sreq ? r/w. smbus isolation request to the asf controller. 2 pcisml_sdao ? ro. smbus data from the asf controller. 1 pcisml_sdai ? r/w. smbus data to the asf controller. 0 pcisml_scli ? r/w. smbus clock to the asf controller. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 323 lan controller registers (b1:d8:f0) statistical counters are reported to the software on demand by issuing the dump statistical counters command or dump and reset statistical counters command in the scb command unit co mmand (cuc) field. table 11-116.statistical counters (sheet 1 of 2) id counter description 0 transmit good frames this counter contains the nu mber of frames that were transmitted properly on the link . it is updated only after the actual transmission on the link is completed, not when the frame was read from memory as is do ne for the transmit command block status. 4 transmit maximum collisions (maxcol) errors this counter contains the numb er of frames that were not transmitted because they encountered the configured maximum number of collisions. 8transmit late collisions (latecol) errors this counter contains the numb er of frames that were not transmitted since they encountered a collision later than the configured slot time. 12 transmit underrun errors a transmit underrun occurs because the system bus cannot keep up with the transmission. this counter contains the number of frames that were either not tran smitted or retransmitted due to a transmit dma underrun. if the la n controller is configured to retransmit on underrun, this counter may be updated multiple times for a single frame. 16 transmit lost carrier sense (crs) this counter contains the nu mber of frames that were transmitted by the lan controller despite the fact that it detected the de-assertion of crs du ring the transmission. 20 transmit deferred this counter contains th e number of frames that were deferred before transmission due to activity on the link. 24 transmit single collisions this counter contains the number of transmitte d frames that encountered one collision. 28 transmit multiple collisions this counter contains the number of transmitte d frames that encountered more than one collision. 32 transmit total collisions this counter contains the total number of collisions that were encountered while attempting to transmit. this count includes late collisions and frames that encountered maxcol. 36 receive good frames this counter contains the number of frames that were received properly from the link. it is updated only after the actual reception from the link is comple ted and all the data bytes are stored in memory. 40 receive crc errors this counter contains the number of aligned frames discarded because of a crc error. this co unter is updated, if needed, regardless of the receive unit state. the receive crc errors counter is mutually exclusive of the receive alignment errors and receive short frame errors counters. 44 receive alignment errors this counter contains the numb er of frames that are both misaligned (for example, cr s de-asserts on a non-octal boundary) and contain a crc error. the counter is updated, if needed, regardless of the rece ive unit state. the receive alignment errors counter is mutu ally exclusive of the receive crc errors and receive shor t frame errors counters. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 324 datasheet the statistical counters are initially set to 0 by the chipset?s integrated lan controller after reset. they cannot be preset to anything other than 0. the lan controller increments the counters by internally re ading them, incrementing them and writing them back. this process is invisible to the processor and pci bus. in addition, the counters adhere to the following rules: ? the counters are wrap-around counters. after reaching ffffffffh the counters wrap around to 0. ? the lan controller updates the required counters for each frame. it is possible for more than one counter to be updated as mu ltiple errors can occur in a single frame. ? the counters are 32 bits wide and their beha vior is fully compatible with the ieee 802.1 standard. the lan controller supports all mandatory and recommend statistics functions through the status of the receive header and directly through these statistical counters. 48 receive resource errors this counter contains the number of good frames discarded due to unavailability of resources. frames intended for a host whose receive unit is in the no resources state fall into this category. if the lan controller is configured to save bad frames and the status of the received frame indica tes that it is a bad frame, the receive resource errors counter is not updated. 52 receive overrun errors this counter contains the number of frames known to be lost because the local system bus was not available. if the traffic problem persists for mo re than one frame, the frames that follow the first are also lost; however, because there is no lost frame indicator, they are not counted. 56 receive collision detect (cdt) this counter contains the number of frames that encountered collisions during frame reception. 60 receive short frame errors this counter contains the number of received frames that are shorter than the minimum frame length. the receive short frame errors counter is mutual ly exclusive to the receive alignment errors and receive crc errors counters. a short frame will always increment only the receive short frame errors counter. 64 flow control trans mi t pa use this counter contains the numb er of flow control frames transmitted by the lan controller. this count includes both the xoff frames transmitted and xon (pause(0)) frames transmitted. 68 flow control receive pause this counter contains the numb er of flow control frames received by the lan controller. th is count includes both the xoff frames received and xon (p ause(0)) fram es received. 72 flow control receive unsupported this counter contains the number of mac control frames received by the lan controller that are not flow control pause frames. these frames are valid ma c control frames that have the predefined mac control type value and a valid address but has an unsupported opcode. 76 receive tco frames this counter contains the number of tco packets received by the lan controller. 78 transmit tco frames this counter contains the number of tco packets transmitted. table 11-116.statistical counters (sheet 2 of 2) id counter description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 325 lan controller registers (b1:d8:f0) the processor can access the counters by issuing a dump statistical counters scb command. this provides a ?snapshot?, in main memory, of the internal lan controller statistical counters. the lan controller supports 21 counters. the dump could consist of the either 16, 19, or all 21 counters, depending on the status of the extended statistics counters and tco statistics configuration bits in the configuration command. 11.3 asf configuration registers (lan controller?b1:d8:f0) the asf registers in this table are accessible through the chipset smbus slave interface. table 11-117.asf register address map offset mnemonic register name default type e0h asf_rid asf revision identification ech ro e1h smb_cntl smbus control 40h r/w e2h asf_cntl asf control 00h r/w, ro e3h asf_cntl_en asf control enable 00h r/w e4h enable enable 00h r/w e5h apm apm 08h r/w e6h?e7h ? reserved ?? e8h wtim_conf watchdog timer configuration 00h r/w e9h heart_tim heartbeat timer 02h r/w eah retran_int retransmission interval 02h r/w ebh retran_pcl retransmission packet count limit 03h r/w ech asf_wtim1 asf watchdog timer 1 01h r/w edh asf_wtim2 asf watchdog timer 2 00h r/w f0h pet_seq1 pet sequence 1 00h r/w f1h pet_seq2 pet sequence 2 00h r/w f2h sta status 40h r/w f3h for_act forced actions 02h r/w f4h rmcp_snum rmcp sequence number 00h r/w f5h sp_mode special modes x0h r/wc, ro f6h inpoll_tconf inter-poll timer configuration 10h r/w f7h phist_clr poll history clear 00h r/wc f8h pmsk1 polling mask 1 xxh r/w f9h pmsk2 polling mask 2 xxh r/w fah pmsk3 polling mask 3 xxh r/w fbh pmsk4 polling mask 4 xxh r/w fch pmsk5 polling mask 5 xxh r/w www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 326 datasheet 11.3.1 asf_rid?asf revision identification register (lan controller?b1:d8:f0) offset address: e0h attribute: ro default value: ech size: 8 bits 11.3.2 smb_cntl?smbus control register (lan controller?b1:d8:f0) offset address: e1h attribute: r/w default value: 40h size: 8 bits this register is used to control configurations of the smbus ports. fdh pmsk6 polling mask 6 xxh r/w feh pmsk7 polling mask 7 xxh r/w ffh pmsk8 polling mask 8 xxh r/w table 11-117.asf re gister address map offset mnemonic register name default type bit description 7:3 asf id ? ro . hardwired to 11101 to identify the asf controller. 2:0 asf silicon revision ? ro . this field provides the silicon revision. bit description 7 smbus remote control asf enable (smb_rcasf) ? r/w . 0 = legacy descriptors an d operations are used. 1 = asf descriptors and operations are used. 6 smbus arp enable (smb_arpen) ? r/w . 0 = disable. 1 = asf enables the smbus arp protocol. 5:4 reserved 3 smbus drive low (smb_drvlo) ? r/w . 0 = asf will not drive the main sm bus signals low while pwr_good = 0. 1 = asf will drive the main smbus signals low while pwr_good = 0. 2:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 327 lan controller registers (b1:d8:f0) 11.3.3 asf_cntl?asf control register (lan controller?b1:d8:f0) offset address: e2h attribute: r/w, ro default value: 00h size: 8 bits this register contains enables for special modes and sos events. ctl_pwrls should be set if asf should be expecting a power loss due to software action. otherwise, an eeprom reload will happen when the power is lost. bit description 7 smbus hang sos enable (ctl_smbhg) ? r/w . 0 = disable 1 = enables smbus hang sos to be sent. 6 watchdog sos enable (ctl_wdg) ? r/w . 0 = disable. 1 = enables watchdog sos to be sent. 5 link loss sos enable (ctl_link) ? r/w. 0 = disable. 1 = enables link loss sos to be sent. 4 os hung status (ctl_oshung) ? ro. 1 = this bit will be set to 1 when asf has detected a watchdog expiration. note: this condition is only clearable by a pci rst# assertion (system reset). 3 power-up sos enable (ctl_pwrup) ? r/w . 0 = disable. 1 = enables power-up sos to be sent. 2 reserved 1 receive arp enable (ctl_rxarp) ? r/w . the lan controller interface provides a mode where all packet s can be requested. 0 = disable. 1 = enable. asf requests all pa ckets when doing a receive enable. this is necessary in lan controller to get arp packets. note: changes to this bit will no t take effect until the ne xt receive enable command to the lan. 0 power loss ok (ctl_pwrls) ? r/w. 0 = power loss will reload eeprom 1 = power loss will not reload eeprom www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 328 datasheet 11.3.4 asf_cntl_en?asf cont rol enable register (asf controller?b1:d8:f0) offset address: e3h attribute: r/w default value: 00h size: 8 bits this register is used to enable global pr ocessing as well as polling. global enable controls all of the smbus processing and packet creation. 11.3.5 enable?enable register (asf controller?b1:d8:f0) offset address: e4h attribute: r/w default value: 00h size: 8 bits this register provides the mechanism to enab le internal sos operations and to enable the remote control functions. bit description 7 global enable (cena_all) ? r/w . 0 = disable 1 = all control and polling enabled 6 receive enable (cena_rx) ? r/w . 0 = disable 1 = tco receives enabled. 5 transmit enable (cena_tx) ? r/w . 0 = disable 1 = sos and rmcp transmits enabled 4 asf polling enable (cena_apol) ? r/w . 0 = disable 1 = enable asf sensor polling. 3 legacy polling enable (cena_lpol) ? r/w . 0 = disable 1 = enable legacy sensor polling. 2:0 number of legacy poll devices (cena_nlpo l) ? r/w. this 3-bit value indicates how many of the eight possible po lling descriptors are active. 000 = first polling de scriptor is active. 001 = first two polling descriptors are active. ... 111 = enables all eight descriptors. bit description 7 enable oshung arps (ena_osharp) ? r/w . 0 = disable 1 = asf will request all packets when in a oshung state. this allows asf to receive arp frames and resp ond as appropriate. 6 state-based security destination port select (ena_sb0298) ? r/w . 0 = state-based security will be honore d on packets received on port 026fh. 1 = packets received on po rt 0298h will be honored. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 329 lan controller registers (b1:d8:f0) 11.3.6 apm?apm register (asf controller?b1:d8:f0) offset address: e5h attribute: r/w default value: 08h size: 8 bits this register contains the configuration bit to disable state-based security. 11.3.7 wtim_conf?watchdog time r configuration register (asf controller?b1:d8:f0) offset address: e8h attribute: r/w default value: 00h size: 8 bits this register contains a single bit that enables the watchdog timer. this bit is not intended to be accessed by software, but sh ould be configured appropriately in the eeprom location for this register default. the bit provides real-time control for enabling/disabling the watchdog timer. wh en set the timer will count down. when cleared the counter will stop. timer start asf smbus messages will set this bit. timer stop asf smbus transactions will clear this bit. 5 pet vlan enable (ena_vlan) ? r/w. 0 = disable 1 = indicates a vlan header for pet note: if this bit is set, the pet packet in ee prom must have the vlan tag within the packet. 4 reserved 3 system power cycle enable (ena_cycle) ? r/w . 0 = disable 1 = enables rmcp power cycle action. 2 system power-down enable (ena_dwn) ? r/w . 0 = disable 1 = enables rmcp power-down action. 1 system power-up enable (ena_up) ? r/w . 0 = disable 1 = enables rmcp power-up action. 0 system reset enable (ena_rst) ? r/w . 0 = disable 1 = enables rmcp reset action bit description bit description 7:4 reserved 3 disable state-based secu rity (apm_dissb) ? r/w. 0 = state-based security on oshung is enabled. 1 = state-based security is disabled and actions are not gated by oshung. 2:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 330 datasheet 11.3.8 heart_tim?heartbe at timer register (asf controller?b1:d8:f0) offset address: e9h attribute: r/w default value: 02h size: 8 bits the heartbeat timer register implements the heartbeat timer. this defines the period of the heartbeats packets. it contains a down counting value when enabled and the time-out value when the counter is disabled. the timer can be configured and enabled in a single write. note: the heartbeat timer controls the heartbeat status packet frequency. the timer is free- running and the configured time is only valid from one heartbeat to the next. when enabled by software, the next heartbeat may occur in any amount of time less than the configured time. . 11.3.9 retran_int?retransmis sion interval register (asf controller?b1:d8:f0) offset address: eah attribute: r/w default value: 02h size: 8 bits this register implements the retransmission timer. this is the time between packet transmissions for multiple packets due to a sos. bit description 7:1 reserved 0 timer enable (wdg_ena) ? r/w. 0 = disable 1 = enable counter bit description 7:1 heartbeat timer value (hbt_val) ? r/w . heartbeat timer load value in 10.7-second resolution. this field can only be written wh ile the timer is disabled. (10.7 sec ? 23 min range). read as lo ad value when hbt_ena=0. read as decrementing value when hbt_ena=1. timer resolution is 10.7 seconds. a value of 00h is invalid. 0 timer enable (hbt_ena) ? r/w . 0 = disable 1 = enable / reset counter bit description 7:1 retransmit timer va lue (rtm_val) ? r/w. retransmit timer load value 2.7 second resolution. this field is always writable (2.7 sec ? 5.7 min range). timer is accurate to +0 seconds, ?0.336 seconds. reads always show the load value (decrement value not shown). a value of 00h is invalid. 0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 331 lan controller registers (b1:d8:f0) 11.3.10 retran_pcl?retransmi ssion packet count limit register (asf controller?b1:d8:f0) offset address: ebh attribute: r/w default value: 03h size: 8 bits this register defines the number of packets that are to be sent due to an sos. 11.3.11 asf_wtim1?asf watc hdog timer 1 register (asf controller?b1:d8:f0) offset address: ech attribute: r/w default value: 01h size: 8 bits this register is used to load the low byte of the timer. when read, it reports the decrementing value. this register is not inte nded to be written by software, but should be configured appropriately in the eeprom loca tion for this register default. timer start asf smbus transactions will load values into this register. once the timer has expired (0000h), the timer will be disabled (edg_ena =0b) and the value in this register will remain at 00h until otherwise changed. 11.3.12 asf_wtim2?asf watc hdog timer 2 register (asf controller?b1:d8:f0) offset address: edh attribute: r/w default value: 00h size: 8 bits this register is used to load the high byte of the timer. when read, it reports the decrementing value. this register is not inte nded to be written by software, but should be configured appropriately in the eeprom loca tion for this register default. timer start asf smbus transactions will load values into this register. once the timer has expired (0000h), the timer will be disabled (edg_ena =0b) and the value in this register will remain at 00h until otherwise changed. bit description 7:0 retransmission packet count lim it (rpc_val) ? r/w. this field provides the number of packets to be sent for all sos packets that require retransmissions. bit description 7:0 asf watchdog t imer 1 (awd1_val) ? r/w. this field provides the low byte of the asf 1-second resolution timer. the timer is accurate to +0 seconds, ?0.336 seconds. bit description 7:0 asf watchdog timer 2 (awd2_val) ? r/w. this field provides the high byte of the asf 1-second resolution timer. the timer is accurate to +0 seconds, ?0.336 seconds. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 332 datasheet 11.3.13 pet_seq1?pet se quence 1 register (asf controller?b1:d8:f0) offset address: f0h attribute: r/w default value: 00h size: 8 bits this register (low byte) holds the current va lue of the pet sequence number. this field is read/write-able through this register, an d is also automatically incremented by the hardware when new pet packets are generated. by policy, software should not write to this register unless transmission is disabled. 11.3.14 pet_seq2?pet se quence 2 register (asf controller?b1:d8:f0) offset address: f1h attribute: r/w default value: 00h size: 8 bits this register (high byte) holds the current va lue of the pet sequence number. this field is read/write-able through this register, an d is also automatically incremented by the hardware when new pet packets are generated. by policy, software should not write to this register unless transmission is disabled. 11.3.15 sta?status register (asf controller?b1:d8:f0) offset address: f2h attribute: r/w default value: 40h size: 8 bits this register gives status indication about several aspects of asf. bit description 7:0 pet sequence byte 1 (pseq1_val) ? r/w. this field provides the low byte. bit description 7:0 pet sequence byte 2 (pseq2_val) ? r/w. this fi eld provides th e high byte. bit description 7 eeprom loading (sta_load) ? r/w . eeprom defaults are in the process of being loaded when this bit is a 1. 6 eeprom invalid checksum indication (sta_icrc) ? r/w . this bit should be read only after the eec_load bit is a 0. 0 = valid 1 = invalid checksum detected for asf portion of the eeprom. 5:4 reserved 3 power cycle status (sta_cycle) ? r/w . 0 = software clears this bit by writing a 1. 1 = this bit is set when a power cycle operation has been issued. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 333 lan controller registers (b1:d8:f0) 11.3.16 for_act?forced actions register (asf controller?b1:d8:f0) offset address: f3h attribute: r/w default value: 02h size: 8 bits this register contains many different forcible actions including apm functions, flushing internal pending sos operations, software sos operations, software reset, and eeprom reload. writes to this register must only set one bit per-write. setting multiple bits in a single write can have indeterminate results. note: for bits in this register, writing a 1 invokes the operation. the bits self-clear immediately. 2 power down status (sta_down) ? r/w. 0 = software clears this bit by writing a 1 1 = this bit is set when a power down operation has been issued. 1 power up status (sta_up) ? r/w. 0 = software clears this bit by writing a 1 1 = this bit is set when a power up operation has been issued. 0 system reset status (sta_rst) ? r/w. 0 = software clears this bit by writing a 1 1 = this bit is set when a system reset operation has been issued. bit description 7 software reset (frc_rst) ? r/w . this bit is used to re set the asf controller. it performs the equivalent of a hardware reset and re-r ead the eeprom. this bit self- clears immediately. software should wait for the eec_load bit to clear. 6 force eeprom reload (frc_eeld) ? r/w . force reload of eeprom without affect current monitoring state of the asf controller. this bit self-clears immediately. note: software registers in eeprom are not lo aded by this action. software should disable the asf controller before issuin g this command and wait for sta_load to clear before enabling again. 5 flush sos (frc_flush) ? r/w . this bit is used to flush any pending soses or history internal to the asf controller. this is necessary because the status register only shows events that have happene d as opposed to sos events sent. also, the history bits in the asf controller are not softwa re visible. self-clears immediately. 4 reserved 3 force apm power cycle (frc_acyc) ? r/w . this mode forces the asf controller to initiate a power cycle to the system. the bit self-clears immediately. 2 force apm hard power down (frc_ahdn) ? r/w . this mode forces the asf controller to initiate a hard power down of the system immediately. the bit self-clears immediately. 1 clear asf polling histor y (frc_clrapol) ? r/w . writing a 1b to this bit position will clear the poll history associated with all asf polling. writing a 0b has no effect. this bit self-clears immediately. 0 force apm reset (frc_arst) ? r/w . this mode forces the asf controller to initiate a hard reset of the system immediately. the bit self-clears immediately. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 334 datasheet 11.3.17 rmcp_snum?rmcp sequ ence number register (asf controller?b1:d8:f0) offset address: f4h attribute: r/w default value: 00h size: 8 bits this register is a means for software to read the current sequence number that hardware is using in rmcp packets. softwa re can also change the value. software should only write to this register while the global enable is off. 11.3.18 sp_mode?special modes register (asf controller?b1:d8:f0) offset address: f5h attribute: r/wc, ro default value: x0h size: 8 bits the register contains miscellaneous functions. 11.3.19 inpoll_tconf?i nter-poll timer configuration register (asf controller?b1:d8:f0) offset address: f6h attribute: r/w default value: 10h size: 8 bits this register is used to load and hold the value (in increments of 5 ms) for the polling timer. this value determines how often the asf polling timer expires which determines the minimum idle time between sensor polls. bit description 7:0 rmcp sequence num ber (rseq_val) ? r/w. this is the current sequence number of the rmcp packet being sent or the sequence number of the next rmcp packet to be sent. this value can be set by software. at reset, it defaults to 00h. if the sequence number is not ffh, the asf controller will automatically increment this number by one (or rollover to 00h if incrementing fro m feh) after a successful rmcp packet transmission. bit description 7 smbus activity bit (spe_act) ? ro . 1 = asf controller is active with a smbus tran saction. this is an indicator to software that the asf controller is still processing commands on the smbus. 6 watchdog status (spe_wdg) ? r/wc . 0 = software clears this bit by writing a 1 to it. 1 = this bit is set when a watchdog expiration occurs. 5 link loss status (spe_lnk) ? r/wc . 0 = software clears this bit by writing a 1 to it. 1 = this bit is set when a link loss occurs (link is down for more than 5 seconds). 4:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 335 lan controller registers (b1:d8:f0) 11.3.20 phist_clr?poll hi story clear register (asf controller?b1:d8:f0) offset address: f7h attribute: r/wc default value: 00h size: 8 bits this register is used to clear the history of the legacy poll operations. asf maintains history of the last poll data for each legacy poll operation to compare against the current poll to detect changes. by setting the appropriate bit, the history for that legacy poll is cleared to 0s. bit description 7:0 inter-poll timer configuration (iptc_val) ? r/w . this field identifies the time, in 5.24 ms units that the asf controller will wait between the end of the one asf poll alert message to start on the next. the value 00h is invalid and unsupported. bit description 7 clear polling descriptor 8 history (phc_poll8) ? r/wc . writing a 1b to this bit position will clear the poll history associat ed with polling descri ptor #8. writing a 0b has no effect. 6 clear polling descriptor 7 history (phc_poll7) ? r/wc . writing a 1b to this bit position will clear the poll history associat ed with polling descri ptor #7. writing a 0b has no effect. 5 clear polling descriptor 6 history (phc_poll6) ? r/wc . writing a 1b to this bit position will clear the poll history associat ed with polling descri ptor #6. writing a 0b has no effect. 4 clear polling descriptor 5 history (phc_poll5) ? r/wc . writing a 1b to this bit position will clear the poll history associat ed with polling descri ptor #5. writing a 0b has no effect. 3 clear polling descriptor 4 history (phc_poll4) ? r/wc . writing a 1b to this bit position will clear the poll history associat ed with polling descri ptor #4. writing a 0b has no effect. 2 clear polling descriptor 3 history (phc_poll3) ? r/wc . writing a 1b to this bit position will clear the poll history associat ed with polling descri ptor #3. writing a 0b has no effect. 1 clear polling descriptor 2 history (phc_poll2) ? r/wc . writing a 1b to this bit position will clear the poll history associat ed with polling descri ptor #2. writing a 0b has no effect. 0 clear polling descriptor 1 history (phc_poll1) ? r/wc . writing a 1b to this bit position will clear the poll history associat ed with polling descri ptor #1. writing a 0b has no effect. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 336 datasheet 11.3.21 pmsk1?polling mask 1 register (asf controller?b1:d8:f0) offset address: f8h attribute: r/w default value: xxh size: 8 bits this register provides software an interface for the polling #1 data mask. 11.3.22 pmsk2?polling mask 2 register (asf controller?b1:d8:f0) offset address: f9h attribute: r/w default value: xxh size: 8 bits this register provides software an interface for the polling #2 data mask. 11.3.23 pmsk3?polling mask 3 register (asf controller?b1:d8:f0) offset address: fah attribute: r/w default value: xxh size: 8 bits this register provides software an interface for the polling #3 data mask. 11.3.24 pmsk4?polling mask 4 register (asf controller?b1:d8:f0) offset address: fbh attribute: r/w default value: xxh size: 8 bits this register provides software an interface for the polling #4 data mask. bit description 7:0 polling mask for polling descriptor #1 (pol1_msk) ? r/w . this field is used to read and write the data mask for polling de scriptor #1. software should only access this register when the asf co ntroller is global disabled. bit description 7:0 polling mask for polling descriptor #2 (pol2_msk) ? r/w. this field is used to read and write the data mask for polling de scriptor #2. software should only access this register when the asf co ntroller is global disabled. bit description 7:0 polling mask for polling descriptor #3 (pol3_msk) ? r/w . this register is used to read and write the data mask for polling descriptor #3. software should only access this register when the asf co ntroller is global disabled. bit description 7:0 polling mask for polling descriptor #4 (pol4_msk) ? r/w . this register is used to read and write the data mask for polling descriptor #4. software should only access this register when the asf co ntroller is global disabled. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 337 lan controller registers (b1:d8:f0) 11.3.25 pmsk5?polling mask 5 register (asf controller?b1:d8:f0) offset address: fch attribute: r/w default value: xxh size: 8 bits this register provides software an interface for the polling #5 data mask. 11.3.26 pmsk6?polling mask 6 register (asf controller?b1:d8:f0) offset address: fdh attribute: r/w default value: xxh size: 8 bits this register provides software an interface for the polling #6 data mask. 11.3.27 pmsk7?polling mask 7 register (asf controller?b1:d8:f0) offset address: feh attribute: r/w default value: xxh size: 8 bits this register provides software an interface for the polling #7 data mask. bit description 7:0 polling mask for polling desc riptor #5 (pol5_msk) ? r/w . this register is used to read and write the data mask for polling descriptor #5. software should only access this register when the asf co ntroller is global disabled. bit description 7:0 polling mask for polling desc riptor #6 (pol6_msk) ? r/w . this register is used to read and write the data mask for polling descriptor #6. software should only access this register when the asf co ntroller is global disabled. bit description 7:0 polling mask for polling descriptor #7 (pol7_msk) ? r/w . this register is used to read and write the data mask for polling descriptor #7. software should only access this register when the asf co ntroller is global disabled. www.datasheet.co.kr datasheet pdf - http://www..net/
lan controller registers (b1:d8:f0) 338 datasheet 11.3.28 pmsk8?polling mask 8 register (asf controller?b1:d8:f0) offset address: ffh attribute: r/w default value: xxh size: 8 bits this register provides software an interface for the polling #8 data mask. bit description 7:0 polling mask for polling descriptor #8 (pol8_msk) ? r/w. this register is used to read and write the data mask for polling descriptor #8. software should only access this register when the asf co ntroller is global disabled. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 339 pci-to-pci bridge registers (d30:f0) 12 pci-to-pci bridge registers (d30:f0) the chipset pci bridge resides in pci de vice 30, function 0 on bus #0. this implements the buffering and control lo gic between pci and the backbone. the arbitration for the pci bus is handled by this pci device. 12.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 12-118.pci bridge register addre ss 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 rid revision identification see register description ro 09h-0bh cc class code 00060401h ro 0dh pmlt primary master latency timer 00h ro 0eh headtyp header type 81h ro 18h-1ah bnum bus number 000000h r/w, ro 1bh smlt secondary master latency timer 00h r/w, ro 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 ba se and limit 00000000h r/w, ro 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 memory limit 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 40h?41h spdh secondary pci device hiding 00h r/w, ro 44h-47h dtc delayed transaction control 00000000h r/w, ro 48h-4bh bps bridge proprietary status 00000000h r/wc, ro www.datasheet.co.kr datasheet pdf - http://www..net/
pci-to-pci bridge registers (d30:f0) 340 datasheet 12.1.1 vid? vendor identificati on register (pci-pci?d30:f0) offset address: 00h?01h attribute: ro default value: 8086h size: 16 bits 12.1.2 did? device identificati on register (pci-pci?d30:f0) offset address: 02h?03h attribute: ro default value: see bit description size: 16 bits 12.1.3 pcicmd?pci command (pci-pci?d30:f0) offset address: 04h ? 05h attribute: r/w, ro default value: 0000h 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 12-118.pci bridge re gister address map (pci-pci ?d30: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 .this is a 16-bit value assigned to the pci bridge. refer to the intel ? i/o controller hub 7 family specification update for the value of the device id register. bit description 15:11 reserved 10 interrupt disable (id) ? ro . hardwired to 0. the pci bridge has no interrupts to disable 9 fast back to back enable (fbe ) ? ro. hardwired to 0, per the pci express* base specification, revision 1.0a . 8 serr# enable (serr_en) ? r/w . 0 = disable. 1 = enable the chipset to generate an nmi (o r smi# if nmi routed to smi#) when the d30:f0 sse bit (offset 06h, bit 14) is set. 7 wait cycle control (wcc) ? ro. hardwired to 0, per the pci express* base specification, revision 1.0a . 6 parity error response (per) ? r/w . 0 = the chipset ignores parity errors on the pci bridge. 1 = the chipset will set the sse bit (d30:f0, offset 06h, bit 14) when parity errors are detected on the pci bridge. 5 vga palette snoop (vps) ? ro . hardwired to 0, per the pci express* base specification, revision 1.0a . www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 341 pci-to-pci bridge registers (d30:f0) 12.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. 4 memory write and invalidate enable (mwe) ? ro . hardwired to 0, per the pci express* base specification, revision 1.0a 3 special cycle enable (sce) ? ro . hardwired to 0, per the pci express* base specification, revision 1.0a and the pci- to-pci bridge specification. 2 bus master enable (bme) ? r/w. 0 = disable 1 = enable. allows the pci-to-pci br idge to accept cycles from pci. 1 memory space enable (mse) ? r/w. controls the respon se as a target for memory cycles targeting pci. 0 = disable 1 = enable 0 i/o space enable (iose) ? r/w. controls the response as a target for i/o cycles targeting pci. 0 = disable 1 = enable bit description bit description 15 detected parity error (dpe) ? r/wc. 0 = parity error not detected. 1 = indicates that the chipset detected a pari ty error on the internal backbone. this bit gets set even if the parity error resp onse bit (d30:f0:04 bit 6) is not set. www.datasheet.co.kr datasheet pdf - http://www..net/
pci-to-pci bridge registers (d30:f0) 342 datasheet 14 signaled system error (sse) ? r/wc. several internal and external sources of the bridge can cause serr#. the first class of errors is parity e rrors related to the backbone. the pci bridge captures generic da ta parity errors (errors it finds on the backbone) as well as errors returned on backbone cycles wher e 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 e rrors. the pci bridge captures generic data parity erro rs (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 enab led 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 errors, each with a corresponding 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 = set when the bridge receives a ma ster abort status from the backbone. 12 received target abort (rta) ? r/wc. 0 = no target abort received. 1 = set when the bridge receives a ta rget abort status from the backbone. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 343 pci-to-pci bridge registers (d30:f0) 12.1.5 rid?revision identificati on register (pci-pci?d30:f0) offset address: 08h attribute: ro default value: see bit description size: 8 bits 12.1.6 cc?class code register (pci-pci?d30:f0) offset address: 09h-0bh attribute: ro default value: 060401h size: 24 bits 11 signaled target abort (sta) ? r/wc . 0 = no signaled target abort 1 = set when the bridge generates a completion packet with target abort status on the backbone. 10:9 reserved . 8 data parity error detected (dpd) ? r/wc . 0 = data parity error not detected. 1 = set when the bridge receives a comp letion packet from the backbone from a previous request, an d detects a parity error, and cm d.pere is set (d30:f0:04 bit 6). 7:5 reserved . 4 capabilities list (clist) ? ro. hardwired to 1. capability list exist on the pci bridge. 3 interrupt status (is) ? ro . hardwired to 0. the pci bridge does not generate interrupts. 2:0 reserved bit description bit description 7:0 revision id ? ro 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 th is device is a pci-to-pci bridge. 7:0 programming interface (pi) ? ro . hardwired to 01h. indi cates the bridge is subtractive decode www.datasheet.co.kr datasheet pdf - http://www..net/
pci-to-pci bridge registers (d30:f0) 344 datasheet 12.1.7 pmlt?primary master latency timer register (pci-pci?d30:f0) offset address: 0dh attribute: ro default value: 00h size: 8 bits 12.1.8 headtyp?header type register (pci-pci?d30:f0) offset address: 0eh attribute: ro default value: 81h size: 8 bits 12.1.9 bnum?bus number re gister (pci-pci?d30:f0) offset address: 18h-1ah attribute: r/w, ro 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 7 multi-function device (mfd) ? ro . the value reported he re depends upon the state of the ac ?97 function hide (fd) regist er (chipset config registers:offset 3418h), per the following table: 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. fd.aad fd.amd mfd 00 1 01 1 10 1 11 0 bit description 23:16 subordinate bus number (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) ? ro . hardwired to 00h for legacy software compatibility. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 345 pci-to-pci bridge registers (d30:f0) 12.1.10 smlt?secondary master latency timer register (pci-pci?d30:f0) offset address: 1bh attribute: r/w, ro default value: 00h size: 8 bits this timer controls the amount of time the chipset 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 ex piration of this counter will result in the de-assertion of frame#. if the grant has no t been removed, then the chipset pci-to- pci bridge may continue ownership of the bus. 12.1.11 iobase_limit?i/o ba se and limit register (pci-pci?d30:f0) offset address: 1ch-1dh attribute: r/w, ro default value: 0000h size: 16 bits 12.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 7:3 master latency timer count (mltc) ? r/w . this 5-bit field in dicates the number of pci clocks, in 8-clock increments, that the chipset 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. bi ts 11:0 are assumed to be padded to fffh. 11:8 ii/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 correspon ding 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. bit description 15 detected parity error (dpe) ? r/wc. 0 = parity error not detected. 1 = chipset pci bridge detected an addres s 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. www.datasheet.co.kr datasheet pdf - http://www..net/
pci-to-pci bridge registers (d30:f0) 346 datasheet 12.1.13 membase_limit?memory base and limit register (pci-pci?d30:f0) offset address: 20h?23h attribute: r/w, ro 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. 13 received master abort (rma) ? r/wc. 0 = no master abort. 1 = this bit is set whenever th e bridge is acting as an in itiator on the pci bus and the cycle is master-aborted. for (g)mch or cpu/chipset interface packets that have completion required, this must also cause a target abort to be returned and sets psts.sta. (d30:f0:06 bit 11) 12 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 or cpu/chipset 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). 11 signaled target abort (sta) ? r/wc. 0 = no target abort. 1 = this bit is set when the br idge is acting as a target on the pci bus and signals a target abort. 10:9 devsel# timing (devt) ? ro. 01h = medium decode timing. 8 data parity error detected (dpd) ? r/wc. 0 = conditions de scribed below not met. 1 = the chipset sets this bit when all of the following 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. 7 fast back to back capable (fbc) ? ro . hardwired to 1 to indicate that the pci to pci target logic is capable of re ceiving fast back-to-back cycles. 6 reserved 5 66 mhz capable (66mhz_cap) ? ro . hardwired to 0. this br idge is 33 mhz capable only. 4:0 reserved bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 347 pci-to-pci bridge registers (d30:f0) 12.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 th e 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. 12.1.15 pmbu32?prefetchable me mory base upper 32 bits register (pci-pci?d30:f0) offset address: 28h?2bh attribute: r/w default value: 00000000h size: 32 bits bit description 31-20 memory limit (ml) ? r/w . these bits are compared with bits 31:20 of the incoming address to determine the upper 1-mb alig ned 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 alig ned value (inclusive) of the range. the incoming address must be greate r than or equal to this value. 3:0 reserved bit description 31-20 prefetchable memory limit (pml) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine the u pper 1-mb aligned value (exclusive) of the range. the incoming address mu st be less than this value. 19-16 64-bit indicator (i64l) ? ro. indicates support for 64-bit addressing. 15:4 prefetchable memory base (pmb) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine the lo wer 1-mb aligned value (inclusive) of the range. the incoming address must be greater than or equal to this value. 3:0 64-bit indicator (i64b) ? ro. indicates support fo r 64-bit addressing. bit description 31:0 prefetchable memory base upper portion (pmbu) ? r/w. upper 32-bits of the prefetchable address base. www.datasheet.co.kr datasheet pdf - http://www..net/
pci-to-pci bridge registers (d30:f0) 348 datasheet 12.1.16 pmlu32?prefetchable memory limit upper 32 bits register (pci-pci?d30:f0) offset address: 2c?2fh attribute: r/w default value: 00000000h size: 32 bits 12.1.17 capp?capability list poin ter register (pci-pci?d30:f0) offset address: 34h attribute: ro default value: 50h size: 8 bits 12.1.18 intr?interrupt informat ion register (pci-pci?d30:f0) offset address: 3ch ? 3dh attribute: r/w, ro default value: 0000h size: 16 bits 12.1.19 bctrl?bridge control register (pci-pci?d30:f0) offset address: 3eh ? 3fh attribute: r/wc, ro default value: 0000h size: 16 bits 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 no t assert an interrupt. 7:0 interrupt line (iline) ? r/w. software written value to indicate which interrupt line (vector) the interrupt is conn ected to. no hardware action is taken on this register. since the bridge does not gene rate an interrupt, bios should program this value to ffh as per the pci bri dge specification. bit description 15:12 reserved 11 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) expi res for a delayed transaction in the hard state. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 349 pci-to-pci bridge registers (d30:f0) 9 secondary discard timer (sdt) ? r/w. this bit sets the maximum number of pci clock cycles that the chipset 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 chipset pci bridge. if the master has not repeated the transaction at least once before the counter expi res, the chipset pci bridge discards the transaction from its queue. 0 = the pci master timeout value is between 2 15 and 2 16 pci clocks 1 = the pci master timeout value is between 2 10 and 2 11 pci clocks 8 primary discard timer (pdt) ? r/w . this bit is r/w for software compatibility only. 7 fast back to back enable (fbe) ? ro. hardwi red to 0. the pci logi c will not generate fast back-to-back cycles on the pci bus. 6 secondary bus reset (sbr) ? r/w . this bit controls pcirst# assertion on pci. 0 = bridge de-asserts pcirst# 1 = bridge asserts pcirst#. when pcirst # is asserted, the delayed transaction buffers, posting buffers, and the pci bus ar e initialized back to reset conditions. the rest of the part and the config uration registers are not affected. 5 master abort mode (mam) ? r/w . this bit controls th e chipset pci bridge?s behavior when a master abort occurs: master abort on (g)mch or cpu/chipset interconnect (dmi): 0 = bridge asserts trdy# on pc i. it drives all 1?s 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 re turned on the (g)mch or cpu/chipset interconnect. 1 = target abort completion st atus will be returned on the (g)mch or cpu/chipset interconnect. note: all locked reads will return a completer abort completion status on the (g)mch or cpu/chipset interconnect. 4 vga 16-bit decode (v16d) ? r/w . this bit controls enable s the chipset pci bridge to provide 16-bits decoding of vga i/o a ddress precluding the decode of vga alias addresses every 1 kb. this bit requires the vgae bit in this register be set. 3 vga enable (vgae) ? r/w . when set to a 1, the chipset pci bridge forwards the following transactions to pci regardless of th e value of the i/o base and limit 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 secondary accesses to the primary interface in reverse. that is, when the bit is 0, memory and i/o a ddresses on the secondary interface between the above ranges will be claimed. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
pci-to-pci bridge registers (d30:f0) 350 datasheet 12.1.20 spdh?secondary pci device hiding register (pci-pci?d30:f0) offset address: 40h?41h attribute: r/w, ro default value: 00h size: 16 bits this register allows software to hide the pci devices, either plugged into slots or on the motherboard. 2 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 chipset pci bri dge 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). 1 serr# enable (see) ? r/w . this bit controls the forwarding of secondary interface serr# assertions on the prim ary interface. when set, th e 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. 0 parity error response enable (pere) ? r/w . 0 = disable 1 = the chipset pci bridge is enabled for pari ty error reporting based on parity errors on the pci bus. bit description bit description 15:8 reserved 7 hide device 7 (hd7) ? r/w, ro . same as bit 0 of this regi ster, except for device 7 (ad[23]) 6 hide device 6 (hd6) ? r/w, ro . same as bit 0 of this re gister, except for device 6 (ad[22]) 5 hide device 5 (hd5) ? r/w, ro . same as bit 0 of this re gister, except for device 5 (ad[21]) 4 hide device 4 (hd4) ? r/w, ro . same as bit 0 of this re gister, except for device 4 (ad[20]) 3 hide device 3 (hd3) ? r/w, ro . same as bit 0 of this re gister, except for device 3 (ad[19]) 2 hide device 2 (hd2) ? r/w, ro. same as bit 0 of this register, except for device 2 (ad[18]) 1 hide device 1 (hd1) ? r/w, ro . same as bit 0 of this regi ster, except for device 1 (ad[17]) 0 hide device 0 (hd0) ? r/w, ro . 0 = the pci configuration cycles for this slot are not affected. 1 = chipset hides device 0 on the pci bus. th is is done by masking the idsel (keeping it low) for configuration cycles to that device. since the device will not see its idsel go active, it will not respond to pci configuration cycles and the processor will think the device is not present. ad[16] is used as idsel for device 0. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 351 pci-to-pci bridge registers (d30:f0) 12.1.21 dtc?delayed transa ction control register (pci-pci?d30:f0) offset address: 44h ? 47h attribute: r/w, ro default value: 00000000h size: 32 bits bit description 31 discard delayed transactions (ddt) ? r/w. 0 = logged delayed transactions are kept. 1 = the chipset pci bridge will discard any delayed transactions it has logged. this includes transactions in th e pending queue, and any transactions in the active queue, whether in the hard or soft dt st ate. the prefetchers will be disabled and return to an idle state. note: if a transaction is running on pci at the time this bit is set, that transaction will continue until either the pci master di sconnects (by de-asserting frame#) or the pci bridge disconnects (by asserting stop#). this bit is cleared by the pci bridge when the delayed transaction queu es are empty and have returned to an idle state. software sets this bit and polls for its completion 30 block delayed transactions (bdt) ? r/w. 0 = delayed transactions accepted 1 = the chipset pci bridge will not accept in coming transactions which will result in delayed transactions. it will blindly retr y 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 . this field controls the maximum number of delayed transactions that the ch ipset 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 4 auto flush after disconne ct enable (afade) ? r/w. 0 = the pci bridge will retain any fetched da ta 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 (b y asserting stop#) disconnects the pci transfer. 3 never prefetch (np) ? r/w. 0 = prefetch enabled 1 = the chipset 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). www.datasheet.co.kr datasheet pdf - http://www..net/
pci-to-pci bridge registers (d30:f0) 352 datasheet 12.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 2 memory read multiple prefetch disable (mrmpd) ? r/w. 0 = mrm commands will fetch multiple ca che lines as defined by the prefetch algorithm. 1 = memory read multiple (mrm) commands wi ll fetch only up to a single, 64-byte aligned cache line. 1 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 fe tch only up to a single, 64-byte aligned cache line. 0 memory read prefetch disable (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 bit description 31:17 reserved 16 perr# assertion detected (pad) ? r/wc. this bit is set by hardware whenever 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 (in 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 de termine the source of a system problem. 15:7 reserved 6:4 number of pending transactions (npt) ? ro . this field indi cates to 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 transactions (nat) ? ro. this field indicate s to debug software how many transactions are in the ac tive queue. possible values are: 00 = no active transactions 01 = 1 active transaction 10 = 2 active transactions 11 = reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 353 pci-to-pci bridge registers (d30:f0) 12.1.23 bpc?bridge policy configuration register (pci-pci?d30:f0) offset address: 4ch ? 4fh attribute: r/w, ro 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 should insert wait states in order to optimize lead-off latency. when the master returns after this thre shold 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 re trying 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 re ad 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 po licy completely such that wait states will not be inserted on the read lead-off data phase. the default value (12h) specifies 18 pci clocks (540 ns) and is a pproximately 4 clocks less than the typical idle lead-off latency expected for nettop chipset systems. this value may need to be changed by bios, depending on the platform. 7 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 forwar d 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. 6 perr#-to-serr# enable (pse) ? r/w . when this bit is set, a 1 in the perr# assertion status bit (in the bri dge proprietary status register) will result in an internal serr# assertion on the primary side of th e bridge (if also enabled by the serr# enable bit in the primary command re gister). serr# is a source of nmi. 5 secondary discard timer testmode (sdtt) ? r/w . 0 = the secondary discard timer expiration will be defined in bctrl.sdt (d30:f0:3e, bit 9) 1 = the secondary discard timer wi ll expire after 128 pci clocks. 4:3 reserved 2 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 cycle from pci that falls outside of the memory and i/o window registers 1 reserved 0 received 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. www.datasheet.co.kr datasheet pdf - http://www..net/
pci-to-pci bridge registers (d30:f0) 354 datasheet 12.1.24 svcap?subsystem vend or capability register (pci-pci?d30:f0) offset address: 50h ? 51h attribute: ro default value: 000dh size: 16 bits 12.1.25 svid?subsystem vendor ids register (pci-pci?d30:f0) offset address: 54h ? 57h attribute: r/wo default value: 00000000h size: 32 bits 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 pci bridge subsystem vendor capability. bit description 31:16 subsystem identifier (sid) ? r/wo . this field indicate s the subsystem as identified by the vendor. this field is write once and is locked down until a bridge reset occurs (not the pci bus reset). 15:0 subsystem vendor identifier (svid) ? r/wo . this field indicates the manufacturer of the subsystem. this field is write once and is locked down until a bridge reset occurs (n ot the pci bus reset). www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 355 lpc interface bridge registers (d31:f0) 13 lpc interface bridge registers (d31:f0) the lpc bridge function of the chipset re sides in pci device 31:function 0. this function contains many other functional uni ts, such as dma and interrupt controllers, timers, power management, system management, gpio, rtc, and lpc configuration registers. registers and functions associated with othe r functional units (ehci, uhci, ide, 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-119.lpc interface pci register ad dress 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 0200h 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 ro 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 80h r/w 64h sirq_cntl serial irq control 10h r/w, ro 68h?6bh pirq[ n ]_rout pirq[e?h] routing control 80h r/w 80h lpc_i/o_dec i/o decode ranges 0000h r/w www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 356 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 82h?83h lpc_en lpc interface enables 0000h r/w 84h?87h gen1_dec lpc interface generic decode range 1 00000000h r/w 88h?8bh gen2_dec lpc interface generic decode range 2 00000000h r/w 8ch?8eh gen3_dec lpc interface generic decode range 3 00000000h r/w 90h?93h gen4_dec lpc interface 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 fwh_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 bios control 00h r/wlo, r/w e0h?e1h fdcap feature detect ion 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-119.lpc interface pc i 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 . this is a 16-bit value assign ed to the chip set lpc bridge. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 357 lpc interface bridge registers (d31:f0) 13.1.3 pcicmd?pci command re gister (lpc i/f?d31:f0) offset address: 04h ? 05h attribute: r/w, ro default value: 0007h size: 16-bit lockable: no power well: core 13.1.4 pcists?pci status re gister (lpc i/f?d31:f0) offset address: 06 ? 07h attribute: ro, r/wc default value: 0210h size: 16-bit lockable: noh 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 15:10 reserved 9 fast back to back enable (fbe) ? ro. hardwired to 0. 8 serr# enable (serr_en) ? r/w. the lpc bridge generate s serr# if this bit is set. 7 wait cycle control (wcc) ? ro. hardwired to 0. 6 parity error respon se enable (pere) ? r/w. 0 = no action is taken when detecting a parity error. 1 = enables the chipset lpc bridge to respon d to parity errors de tected 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 enable (iose) ? ro . i/o space cannot be disabled on lpc. bit description 15 detected parity error (dpe) ? r/wc. set when the lpc bri dge detects a parity error on the internal backbone. set even if the pcicmd.pere bit (d31:f0:04, bit 6) is 0. 0 = parity error not detected. 1 = parity error detected. 14 signaled system error (sse)? r/wc . set when the lpc bri dge signals a system error to the internal serr# logic. 13 master abort status (rma) ? r/wc . 0 = unsupported request status not received. 1 = the bridge received a completion wi th unsupported requ est status from the backbone. 12 received target abort (rta) ? r/wc . 0 = completion abort not received. 1 = completion with completion ab ort received from the backbone. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 358 datasheet 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 11 signaled target abort (sta) ? r/wc. 0 = target abort not generated on the backbone. 1 = lpc bridge generated a completion pa cket with target abort status on the backbone. 10:9 devsel# timing status (dev_sts) ? ro. 01 = medium timing. 8 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 co mpletion 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. 7 fast back to back capable (fbc) : reserved ? bit has no meaning on the internal backbone. 6 reserved . 5 66 mhz capable (66mhz_cap) ? reserved ? bit has no meaning on internal backbone. 4 capabilities list (clist) ? ro . capability list exis ts on the lpc bridge. 3 interrupt status (is) ? ro . the lpc bridge does not generate interrupts. 2:0 reserved . bit description bit description 7:0 revision id (rid) ? ro. bit description 7:0 programming interface ? ro. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 359 lpc interface bridge registers (d31:f0) 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 clas s code register (lpc i/f?d31:f0) offset address: 0bh attribute: ro default value: 06h size: 8 bits 13.1.9 plt?primary la tency timer register (lpc i/f?d31:f0) offset address: 0dh attribute: ro default value: 00h size: 8 bits 13.1.10 headtyp?header type register (lpc i/f?d31:f0) offset address: 0eh attribute: ro default value: 80h size: 8 bits 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 th e type of device for the lpc bridge. 06h = bridge device. bit description 7:3 master latency count (mlc) ? reserved . 2:0 reserved . bit description 7 multi-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. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 360 datasheet 13.1.11 ss?sub system identifier s 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 th e 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 power well: core 13.1.13 pmbase?acpi base addres s 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 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 offs et of the first item. bit description 31:16 reserved 15:7 base address ? r/w. this field provides 128 by tes of i/o space for acpi, gpio, and tco logic. this is placed on a 128-byte boundary. 6:1 reserved 0 resource type indicator (rte) ? ro. ha rdwired to 1 to indicate i/o space. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 361 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 13.1.15 gpiobase?gpio base ad dress register (lpc i/f ? d31:f0) offset address: 48h?4bh attribute: r/w, ro default value: 00000001h size: 32 bit bit description 7 acpi enable (acpi_en) ? r/w. 0 = disable. 1 = decode of the i/o range pointed to by th e acpi base register is enabled, and the acpi power management fu nction is enabled. no te that the apm power management ranges (b2/b3h) are always en abled and are not affected by this bit. 6:3 reserved 2:0 sci irq select (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 that interrupt is not sharable with the serirq stream, but is shareable with other pci interrupts. if using the apic, the sci can also be mapped to irq20?23, and can be shared with other interrupts. note: when the interrupt is mapped to apic inte rrupts 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 shou ld be programmed for active-low 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) 110b irq22 (only available if apic enabled) 111b irq23 (only available if apic enabled) bit description 31:16 reserved . always 0. 15:6 base address (ba) ? r/w. provides the 64 bytes of i/o space for gpio. 5:1 reserved . always 0. 0 ro. hardwired to 1 to indicate i/o space. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 362 datasheet 13.1.16 gc?gpio control register (lpc i/f ? d31:f0) offset address: 4ch attribute: r/w default value: 00h size: 8 bit 13.1.17 pirq[n]_rout?p irq[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 7:5 reserved . 4 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:0 reserved . bit description 7 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 363 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 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 7 serial 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 se rirq pin will be configured as serirq. 6 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: for systems using quiet mode, this bit should be set to 1 (continuous mode) for at least one frame after coming out of reset before switch ing back to quiet mode. failure to do so will result in the chipset 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 chipset will drive the start frame for the number of clocks specified. in quiet mode, the chipset will drive the start frame for the number of clocks specified minus one, as the first cl ock was driven by the peripheral. 00 = 4 clocks 01 = 6 clocks 10 = 8 clocks 11 = reserved bit description 7 interrupt routing enable (irqen) ? r/w. 0 = the corresponding pirq is routed to on e 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 su bsequently be changed by the os when setting up for i/o apic interrupt delivery mode. 6:4 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 364 datasheet 13.1.20 lpc_i/o_dec?i/o de code ranges register (lpc i/f?d31:f0) offset address: 80h attribute: r/w default value: 0000h size: 16 bit 3:0 irq routing ? r/w. (isa compatible.) bit description 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 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 determin es 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 7 reserved 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 365 lpc interface bridge registers (d31:f0) 13.1.21 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 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 bit description 15:14 reserved 13 cnf2_lpc_en ? r/w. microcontroller enable # 2. 0 = disable. 1 = enables the decoding of the i/o locati ons 4eh and 4fh to th e lpc interface. this range is used for a microcontroller. 12 cnf1_lpc_en ? r/w. super i/o enable. 0 = disable. 1 = enables the decoding of the i/o locati ons 2eh and 2fh to th e lpc interface. this range is used for super i/o devices. 11 mc_lpc_en ? r/w. microcontroller enable # 1. 0 = disable. 1 = enables the decoding of the i/o locati ons 62h and 66h to th e lpc interface. this range is used for a microcontroller. 10 kbc_lpc_en ? r/w. keyboard enable. 0 = disable. 1 = enables the decoding of the i/o locati ons 60h and 64h to th e lpc interface. this range is used for a microcontroller. 9 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. 8 gamel_lpc_en ? r/w. low gameport enable 0 = disable. 1 = enables the decoding of the i/o locations 200h to 207h to the lpc interface. this range is used for a gameport. 7:4 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 366 datasheet 13.1.22 gen1_dec?lpc i/f generi c 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 3 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). 2 lpt_lpc_en ? r/w. parallel port enable 0 = disable. 1 = enables the decoding of the lptrange to th e lpc interface. this range is selected in the lpc_fdd/lpt decode range register (d31:f0:80h, bit 9:8). 1 comb_lpc_en ? r/w. com port b enable 0 = disable. 1 = enables the decoding of the comb rang e to the lpc interface. this range is selected in the lpc_com decode rang e register (d31:f0:80h, bits 6:4). 0 coma_lpc_en ? r/w. com port a enable 0 = disable. 1 = enables the decoding of the coma ra nge to the lpc interface. this range is selected in the lpc_com decode rang e register (d31:f0:80h, bits 3:2). bit description bit description 31:24 reserved 23:18 generic i/o decode range address[7:2] mask : a ?1? in any bit position indicates that any value in the correspon ding 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 ad dress, 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, an d must have address lines 31:16 as 0. note: the chipset does not provide decode down to the word or byte level. 1 reserved 0 generic 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 367 lpc interface bridge registers (d31:f0) 13.1.23 gen2_dec?lpc i/f gene ric decode range 2register (lpc i/f?d31:f0) offset address: 88h ? 8bh attribute: r/w default value: 00000000h size: 32 bit power well: core 13.1.24 gen3_dec?lpc i/f gene ric decode range 3register (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 ra nge address[7:2] mask : a ?1? in any bit position indicates that any value in the corresponding address bi t in a received cycle will be treated as a match. the corresponding bit in the address fi eld, below, is ignored. the mask is only provided for the lower 6 bits of the dword a ddress, allowing for decoding blocks up to 256 bytes in size. 17:16 reserved 15:2 generic i/o decode range 2base address (gen1_base) ? r/w . note: the chipset does not provide decode down to the word or byte level. 1 reserved 0 generic decode range 2enable (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 rang e address[7:2] mask: a ?1? in any bit position indicates that any value in the corresponding address bi t in a received cycle will be treated as a match. the corresponding bit in the address fi eld, below, is ignored. the mask is only provided for the lower 6 bits of the dword a ddress, allowing for decoding blocks up to 256 bytes in size. 17:16 reserved 15:2 generic i/o decode range 3base address (gen3_base) ? r/w. note: the chipset does not provide decode down to the word or byte level. 1 reserved 0 generic decode range 3enable (gen3_en) ? r/w. 0 = disable. 1 = enable the gen3 i/o range to be forwarded to the lpc i/f www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 368 datasheet 13.1.25 gen4_dec?lpc i/f gene ric decode range 4register (lpc i/f?d31:f0) offset address: 90h ? 93h attribute: r/w default value: 00000000h size: 32 bit power well: core 13.1.26 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:24 reserved 23:18 generic i/o decode range address[7:2] mask : a ?1? in any bit position indicates that any value in the correspon ding 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 ad dress, allowing for decoding blocks up to 256 bytes in size. 17:16 reserved 15:2 generic i/o decode range 4base address (gen4_base) ? r/w. note: the chipset does not provide decode down to the word or byte level. 1 reserved 0 generic decode range 4enable (gen4_en) ? r/w. 0 = disable. 1 = enable the gen4 i/o range to be forwarded to the lpc i/f bit description 31:28 fwh_f8_idsel ? ro. idsel for two 512-kb firmware hub memory ranges and one 128-kb memory range. this field is fixed at 0000. the idsel programmed in this field addresses the following 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 addr esses 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 addr esses 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 addr esses the following memory ranges: ffe0 0000h ? ffe7 ffffh ffa0 0000h ? ffa7 ffffh www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 369 lpc interface bridge registers (d31:f0) 13.1.27 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 15:12 fwh_d8_idsel ? r/w. idsel for two 512-kb fi rmware hub memo ry ranges. the idsel programmed in this field addr esses the following memory ranges: ffd8 0000h ? ffdf ffffh ff98 0000h ? ff9f ffffh 11:8 fwh_d0_idsel ? r/w. idsel for two 512-kb fi rmware hub memo ry ranges. the idsel programmed in this field addr esses the following memory ranges: ffd0 0000h ? ffd7 ffffh ff90 0000h ? ff97 ffffh 7:4 fwh_c8_idsel ? r/w. idsel for two 512-kb fi rmware hub memo ry ranges. the idsel programmed in this field addr esses the following memory ranges: ffc8 0000h ? ffcf ffffh ff88 0000h ? ff8f ffffh 3:0 fwh_c0_idsel ? r/w. idsel for two 512-kb fi rmware hub memo ry ranges. the idsel programmed in this field addr esses the following memory ranges: ffc0 0000h ? ffc7 ffffh ff80 0000h ? ff87 ffffh bit description bit description 15:12 fwh_70_idsel ? r/w. idsel for two, 1-m firmware hub memory ranges. the idsel programmed in this field a ddresses 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 a ddresses 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 a ddresses 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 a ddresses the following memory ranges: ff40 0000h ? ff4f ffffh ff00 0000h ? ff0f ffffh www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 370 datasheet 13.1.28 fwh_dec_en1?firmware hu b 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 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 14 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 13 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 12 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 11 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 10 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 9 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 371 lpc interface bridge registers (d31:f0) 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 chipset simply decodes these ranges as memory accesses when enabled for the spi flash interface. 8 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 7 fwh_legacy_f_en ? r/w. this enables the decoding of the legacy 128-k range at f0000h ? fffffh. 0 = disable. 1 = enable the following legacy ranges for the firmware hub f0000h ? fffffh 6 fwh_legacy_e_en ? r/w. this enables the decoding of the legacy 128-k range at e0000h ? effffh. 0 = disable. 1 = enable the following legacy ranges for the firmware hub e0000h ? effffh 5:4 reserved 3 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 2 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 1 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 0 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 www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 372 datasheet 13.1.29 bios_cntl?bios control register (lpc i/f?d31:f0) offset address: dch attribute: r/wlo, r/w, ro default value: 00h size: 8 bit lockable: no power well: core bit description 7:5 reserved 4 top swap status (tss)? ro: this bit prov ides 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: 1 bios lock enable (ble) ? r/wlo. 0 = setting the bioswe will not cause smis. 1 = enables setting the bioswe bit to cause smis. once set, this bit can only be cleared by a pltrst# 0 bios write enable (bioswe) ? r/w. 0 = only read cycles permitted to firmware hub or spi flash. 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 en sures that only smi code can update bios. note: writes to the firmware hub?s feature space are not blocked when the bioswe is cleared in order to allow access to registers. the feature space is the second range that is located 4 mb below the bios range for each firmware hub. 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 the same line to complete quickly 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 373 lpc interface bridge registers (d31:f0) 13.1.30 fdcap?feature dete ction capability id (lpc i/f?d31:f0) offset address: e0h-e1h attribute: ro default value: 0009h size: 16 bit power well: core 13.1.31 fdlen?feature detect ion capability length (lpc i/f?d31:f0) offset address: e2h attribute: ro default value: 0ch size: 8 bit power well: core 13.1.32 fdver?feature detection version (lpc i/f?d31:f0) offset address: e3h attribute: ro default value: 10h size: 8 bit power well: core 13.1.33 fdvct?feature vector register (lpc i/f?d31:f0) offset address: e4h?ebh attribute: ro default value: see description size: 64 bit power well: core bit description 15:8 next item pointer (next) : configuration offset of the next capability item. 00h indicates the last item in the capability list. 7:0 capability id: indicates a vendor specific capability bit description 7:0 capability length: indicates the length of this vendor specific capability, as required by pci spec. bit description 7:4 vendor-specific capability id : a value of 1h in this 4- bit field identifies this capability as feature detectio n type. this field allows so ftware to differentiate the feature detection capability from other vendor-speci fic capabilities 3:0 capability version : this field indicates the version of the feature detection capability bit description 63:10 reserved 9 mobile features capability? ro : 0 = disabled 1 = capable www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 374 datasheet 13.1.34 rcba?root complex base address register (lpc i/f?d31:f0) offset address: f0h attribute: r/w default value: 00000000h size: 32 bit 13.2 dma i/o registers (lpc i/f?d31:f0) 8:4 reserved 3 sata ahci capability? ro : 0 = capable 1 = disabled 2:0 reserved bit description bit description 31:14 base address (ba) ? r/w. base address for the root complex register block decode range. this address is al igned on a 16-kb boundary. 13:1 reserved 0 enable (en) ? r/w. when set, this bit enables the range specified in ba to be claimed as the root complex register block. table 13-120.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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 375 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 = 02hattribute:r/w ch. #2 = 04h; ch. #3 = 06hsize:16 bit (per channel), ch. #5 = c4h ch. #6 = c8h but accessed in two 8-bit ch. #7 = cch; quantities default value: undef lockable: no power well:core 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 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 channel 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-120.dma regi sters (sheet 2 of 2) port alias register name default type www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 376 datasheet 13.2.2 dmabase_cc?dma base an d current count registers (lpc i/f?d31:f0) i/o address: ch. #0 = 01h; ch. #1 = 03hattribute:r/w ch. #2 = 05h; ch. #3 = 07hsize: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 bit description 15:0 base and current address ? r/w. this register determin es the address for the transfers to be performed. the address specif ied points to two sepa rate 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 increments/decrements in the current address register after each transfer, 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 po inted to by the current byte pointer flip/flop. before acce ssing an address regi ster, the byte pointer flip/flop should be cleared to ensure that th e low byte is accessed first. bit description 15:0 base and current count ? r/w. this register determines the number of transfers to be performed. the address spec ified points to two separate registers. on writes, the value is stored 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 transfer. when the value in the register rolls from 0 to ffffh, a terminal count is generated. if the channel is in auto- initialize mode, the current count register will be re loaded from the base count register after a termin al count is generated. for transfers to/from an 8-bit slave (channels 0?3), the count register indicates the number of bytes to be transferred. for tran sfers to/from a 16-bit slave (channels 5?7), the count register indicates the nu mber of words to be transferred. the register is accessed in 8 bit quantities. the byte is po inted to by the current byte pointer flip/flop. before acce ssing a count register, the byte pointer flip/flop should be cleared to ensure that the low byte is ac cessed first. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 377 lpc interface bridge registers (d31:f0) 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 13.2.4 dmacmd?dma command re gister (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 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. this register remains static throughout the dma transfer. 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. bit description 7:5 reserved . must be 0. 4 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 = fixed priority to the channel group 1 = rotating priority to the group. 3 reserved . must be 0. 2 dma channel group enable ? wo. both channel groups are enabled following part reset. 0 = enable the dma channel group. 1 = disable. disabling channel group 4?7 al so disables channel group 0?3, which is cascaded through channel 4. 1:0 reserved . must be 0. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 378 datasheet 13.2.5 dmasta?dma status re gister (lpc i/f?d31:f0) i/o address: ch. #0 ? 3 = 08h; ch. #4 ? 7 = d0h attribute: ro default value: undefined size: 8-bit lockable: no power well: core 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:4 channel request status ? ro. when a valid dma reques t 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 ch annel, so the request status of channel 4 is a logical or of the requ est status for chan nels 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 bi t response for channe l 4 is irrelevant: 0 = channel 0 1 = channel 1 (5) 2 = channel 2 (6) 3 = channel 3 (7) bit description 7:3 reserved . must be 0. 2 channel mask select ? wo. 0 = enable dreq for the selected channel. the channel is selected through bits [1:0]. therefore, only one ch annel 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) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 379 lpc interface bridge registers (d31:f0) 13.2.7 dmach_mode?dma ch annel 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 5 address increment/decrement select ? wo. this bit controls address increment/ decrement during dma transfers. 0 = address increment. (default af ter part reset or master clear) 1 = address decrement. 4 autoinitialize enable ? wo. 0 = autoinitialize feature is disabled and dma transfers te rminate on a terminal count. a part reset or master clear disables autoinitialization. 1 = dma restores the base address and co unt registers to th e current registers following a terminal count (tc). 3:2 dma transfer type ? wo. these bits represent the direction of the dma transfer. when the channel is programmed for cascade mode, (bits[7:6] = 11) the transfer 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 ch annel 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) www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 380 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 re gister (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. comm and enabled with a write to the i/o port address. writing to this register initializes the byte pointer flip/flop to a known state. it clears the internal latch used to address the uppe r 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. this command precedes the first access to a 16-bit dma controller register. the first ac cess 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 clear ? wo. no specific pattern. enabled with a write to the port. this has the same effect as the hardware reset. the co mmand, status, reques t, 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 enabled with a write to the port. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 381 lpc interface bridge registers (d31:f0) 13.2.11 dma_wrmsk?dma writ e 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 13.3 timer i/o registers (lpc i/f?d31:f0) bit description 7:4 reserved . must be 0. 3:0 channel mask bits ? r/w. this register permit s all four channels to be simultaneously enabled/disabled instead of enabling/disabling each channel individually, as is the case with the mask re gister ? write single mask bit. in addition, this register has a read path to allow the st atus 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 chan nel is in auto-initialization mode). setting the bit(s) to a 1 disables the corre sponding 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. port aliases register name default value type 40h 50h counter 0 interv al time status byte format 0xxxxxxxb ro counter 0 counter acce ss port undefined r/w 41h 51h counter 1 interval time status byte format 0xxxxxxxb ro counter 1 counter acce ss port undefined r/w 42h 52h counter 2 interval time status byte format 0xxxxxxxb ro counter 2 counter acce ss port undefined r/w 43h 53h timer control word undefined wo timer control word register xxxxxxx0b wo counter latch command x0h wo www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 382 datasheet 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 word s 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 register, the read back command and the counter latch command. when these 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 select 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/w rite control bits. the actual counter programming is done through the co unter port (40h for counter 0, 41h for counter 1, and 42h for counter 2). 00 = counter latch command 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. 0 binary/bcd countdown select ? wo. 0 = binary countdown is used. the largest possible binary count is 2 16 1 = binary coded decimal (bcd ) count is used. the largest possible bcd count is 10 4 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 mode 3 square wave output 100b mode 4 software triggered strobe 101b mode 5 hardware triggered strobe www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 383 lpc interface bridge registers (d31:f0) 13.3.2 rdbk_cmd?read back command (lpc i/f?d31:f0) the read back command is used to determine the count 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 op eration from that counter returns the latched status. the next one or two reads, depend ing on whether the counter is programmed for one or two byte counts, returns the latched count. subsequent reads return an unlatched count. 13.3.3 ltch_cmd?counter latch command (lpc i/f?d31:f0) the counter latch command latches the current count value. 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 byte s 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 latche d once and then latc hed 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 5 latch count of se lected counters . 0 = current count value of the sele cted counters will be latched 1 = current count will not be latched 4 latch status of selected counters . 0 = status of the selected counters will be latched 1 = status will not be latched 3 counter 2 select . 1 = counter 2 count and/or status will be latched 2 counter 1 select . 1 = counter 1 count and/or status will be latched 1 counter 0 select . 1 = counter 0 count and/or status will be latched. 0 reserved . must be 0. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 384 datasheet 13.3.4 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 read 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 th e status byte. the status byte returns the following: bit description 7:6 counter selection. these bits select the counter for la tching. 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. bit description 7 counter out pin state ? ro. 0 = out pin of the counter is also a 0 1 = out pin of the counter is also a 1 6 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 until the count is loaded into the counting element (ce), the count value will be incorrect. 0 = count has been transf erred from cr to ce and is available for reading. 1 = null count. count has not been transferre d from cr to ce and is not yet available for reading. 5:4 read/write selection status ? ro. these bits reflect the read/write selection made through bits[5:4] of the control register. th e binary codes returned during the status read match the codes used to progra m the counter read /write selection. 00 = counter latch command 01 = read/write least significant byte (lsb) 10 = read/write most significant byte (msb) 11 = read/write lsb then msb www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 385 lpc interface bridge registers (d31:f0) 13.3.5 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 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 locate d 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-121 shows the different register possibilities for each address. 3:1 mode selection status ? ro. these bits return the counter mode programming. the binary code returned matche s 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 0 countdown type status ? ro. this bit reflects the current countdown type. 0 = binary countdown 1 = binary coded decimal (bcd) countdown. bit description bit description 7:0 counter port ? r/w. each counter po rt address is used to program the 16-bit count register. the order of progra mming, either lsb only, msb only, or lsb then msb, is defined with the interval counte r control register at port 43 h. the counter port is also used to read the current co unt from the count register, an d return the status of the counter programming following a read back command. table 13-121.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 www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 386 datasheet note: refer to note addressing active-low interrupt sources in 8259 interrupt controllers section (chapter 5.9 - volume 1). 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. 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 word 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 word 2 undefined wo slave pic icw3 init. cmd word 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 table 13-121.pic regist ers (lpc i/f?d31:f0) port aliases register name default value type bit description 7:5 icw/ocw select ? wo. these bits are mcs-85 specific, and not needed. 000 = should be programmed to ?000? 4 icw/ocw select ? wo. 1 = this bit must be a 1 to select ic w1 and enable the icw2, icw3, and icw4 sequence. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 387 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 contro ller 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. 3 edge/level bank select (ltim) ? wo. disabled. replac ed by the edge/level triggered control registers (elc r, d31:f0:4d0h, d31:f0:4d1h). 2adi ? wo. 0 = ignored for the chipset. should be programmed to 0. 1 single or cascade (sngl) ? wo. 0 = must be programmed to a 0 to indicate two controllers operating in cascade mode. 0 icw4 write required (ic4) ? wo. 1 = this bit must be programmed to a 1 to indicate that icw4 needs to be programmed. bit description 7:3 interrupt vector base address ? wo. bits [7:3] define the base address in the interrupt vector table for the interrupt routines as sociated with each interrupt request level input. 2:0 interrupt request level ? wo. when writing icw2, these bits should all be 0. during an interrupt acknowle dge cycle, these bits are pr ogrammed 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 www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 388 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 controlle r initialization command word 3 register (lpc i/f?d31:f0) offset address: a1h attribute: wo default value: all bits undefined size: 8 bits 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 bit description 7:3 0 = these bits must be programmed to 0. 2 cascaded interrupt controller irq connection ? 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 controlle r?s priority solver. if it wins, the intr signal is asserted to the processor, and th e returning interrupt ac knowledge 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 identification code ? wo. these bits are compared against the slave identification code broadcast by the master co ntroller from the traili ng edge of the first internal inta# pulse to the trailing edge of the second internal inta# pulse. these bits must be programmed to 02h to match the code broadcast by th e master controller. when 02h is broadcast by the master contro ller during the inta# sequence, the slave controller assumes responsibility fo r broadcasting the interrupt vector. bit description 7:5 0 = these bits must be programmed to 0. 4 special fully nested mode (sfnm) ? wo. 0 = should normally be disabled by writing a 0 to this bit. 1 = special fully nested mode is programmed. 3 buffered mode (buf) ? wo. 0 = must be programmed to 0 for the chipset. this is non-buffered mode. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 389 lpc interface bridge registers (d31:f0) 13.4.7 ocw1?operational contro l word 1 (interrupt mask) register (lpc i/f?d31:f0) offset address: master controller ? 021h attribute: r/w slave controller ? 0a1h size: 8 bits default value: 00h 13.4.8 ocw2?operational co ntrol 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 rotati on is the default. both rotation mode and specific eoi mode are disabl ed following initialization. 2 master/slave in buffered mode ? wo. not used. 0 = should always be programmed to 0. 1 automatic 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. 0 microprocessor mode ? wo. 1 = must be programmed to 1 to indicate that the controller is operating in an intel architecture-based system. bit description 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 in terrupt requests will again be accepted by the controller. masking irq2 on the master controller will also mask the interrupt requests from the slave controller. 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 (clear) 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 command 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? www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 390 datasheet 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 2:0 interrupt level select (l2, l1, l0) ? wo. l2, l1, and l0 determine the interrupt level acted upon when the sl bit is active. a simple binary code, outlined below, selects the channel for the command to act upon. when the sl bit is inactive, these bits do not have a defined function; prog ramming l2, l1 and l0 to 0 is sufficient in this case. bit description 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 bit description 7 reserved . must be 0. 6 special mask mode (smm) ? wo. 1 = the special mask mode can be used by an interrupt service routine to dynamically alter the system priority structure while th e routine is executing, through selective enabling/disabling of the other channel's ma sk bits. bit 5, the esmm bit, must be set for this bit to have any meaning. 5 enable special mask mode (esmm) ? wo. 0 = disable. the smm bit becomes a ?don't care?. 1 = enable the smm bit to set or reset the special mask mode. 4:3 ocw3 select ? wo. when selecting ocw3, bits 4:3 = 01 2 poll mode command ? wo. 0 = disable. poll command is not issued. 1 = enable. the next i/o read to the interr upt controller is treated as an interrupt acknowledge cycle. an encode d byte is driven onto the data bus, repr esenting the highest priority level requesting service. 1:0 register read command ? wo. these bits provide control for reading the in-service register (isr) and the interrupt request register (irr). when bit 1=0, bit 0 will not affect the register read sele ction. 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, th e default ocw3 port address read will be ?read irr?. to retain the curre nt selection (read isr or read irr), always write a 0 to bit 1 when programming this register. the selected regist er can be read repeatedly without reprogramming ocw3. to select a new status regist er, ocw3 must be reprogrammed prior to attempting the read. 00 = no action 01 = no action 10 = read irq register 11 = read is register www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 391 lpc interface bridge registers (d31:f0) 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. 13.4.11 elcr2?slave controller e dge/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 recogn ized by a high level. the real time clock, irq8#, and the floating point error interru pt, irq13, cannot be programmed for level mode. bit description 7 irq7 ecl ? r/w. 0 = edge. 1 = level. 6 irq6 ecl ? r/w. 0 = edge. 1 = level. 5 irq5 ecl ? r/w. 0 = edge. 1 = level. 4 irq4 ecl ? r/w. 0 = edge. 1 = level. 3 irq3 ecl ? r/w. 0 = edge. 1 = level. 2:0 reserved . must be 0. bit description 7 irq15 ecl ? r/w. 0 = edge 1 = level 6 irq14 ecl ? r/w. 0 = edge 1 = level 5 reserved . must be 0. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 392 datasheet 13.5 advanced programmabl e interrupt controller (apic)(d31:f0) 13.5.1 apic register map (lpc i/f?d31:f0) the apic is accessed via an indirect addre ssing scheme. two registers are visible by software for manipulation of most of the apic registers. these registers are mapped into memory space. the registers are shown in table 13-122 . table 13-123 lists the registers which can be accessed within the apic via the index register. when accessing these registers, accesses must be done one dword at a time. for example, software should not access byte 2 from the data register before accessing bytes 0 and 1. the hardware will not atte mpt to recover from a bad programming model in this case. 4 irq12 ecl ? r/w. 0 = edge 1 = level 3 irq11 ecl ? r/w. 0 = edge 1 = level 2 irq10 ecl ? r/w. 0 = edge 1 = level 1 irq9 ecl ? r/w. 0 = edge 1 = level 0 reserved . must be 0. bit description table 13-122.apic direct registers (lpc i/f?d31:f0) address mnemoni c 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-123.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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 393 lpc interface bridge registers (d31:f0) 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-123 . software will program this register to select the desired apic internal register . 13.5.3 dat?data register (lpc i/f?d31:f0) memory address fec0_0010h attribute: r/w default value: 00000000h size: 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, th e 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 entr ies 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 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 table 13-123.apic indirect registers (lpc i/f?d31:f0) index mnemonic register name size type bit description 7:0 apic index ? r/w. this is an 8-bit pointer into the i/o apic register table. bit description 7:0 apic data ? r/w. this is a 32-bit register for the da ta to be read or written to the apic indirect register ( ta b l e 1 3 - 1 2 3 ) pointed to by the index register (memory address fec0_0000h). www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 394 datasheet at a later time. note: only bits 7:0 are actually used. bits 31:8 are ignored by the chipset. note: to provide for future expansion, the processor should always write a value of 0 to bits 31:8. 13.5.5 id?identification re gister (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 regist er (lpc i/f?d31:f0) index offset: 01h attribute: ro default value: 00170020h size: 32 bits each i/o apic contains a hardwired version register that identifies different implementation of apic and their versions . the maximum redirection entry information also is in this register, to let software kn ow how many interrupt are supported by this apic. bit description 31:8 reserved . to provide for future expansion, the processor should always 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. bit description 31:28 reserved 27:24 apic id ? r/w. software must program th is value before using the apic. 23:16 reserved 15 scratchpad bit. 14:0 reserved bit description 31:24 reserved 23:16 maximum redirection entries ? ro. this field 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 th e range 0 through 239. in the chipset this field is hardwired to 17h to indicate 24 interrupts. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 395 lpc interface bridge registers (d31:f0) 13.5.7 redir_tbl?redirection table (lpc i/f?d31:f0) index offset: 10h ? 11h (vector 0) throughattribute: 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 in terrupt 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 se t. the state machine will step ahead and wait for an acknowledgment from the apic unit th at 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.) 15 prq ? ro. this bit indicate that the ioxapic does not implement the pin assertion register. 14:8 reserved 7:0 version ? ro. this is a version number that iden tifies the implementation version. 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 shou ld 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. th ey become bits 11:4 of the address. 47:17 reserved 16 mask ? r/w. 0 = not masked: an edge or level on this in terrupt 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 inte rrupt. this behavior is identical to the device withdrawing th e 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 ac cepted by a local apic unit but before the interrupt is dispen sed to the processor. 15 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. 14 remote irr ? r/w. this bit is used for level triggered interrupts; its meaning is undefined for edge tr iggered 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. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 396 datasheet note: delivery mode encoding: 000 = fixed. deliver the signal on the intr signal of all processor cores listed 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 in terrupt). requires th e interrupt to be pr ogrammed as edge triggered. the vector information is ignored but must be programmed to all 0?s 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 op eration this redirectio n 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 counting through the redirection table addresses. once the co unt 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 local apics will assume thei r 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 redirect ion 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 exte rnally 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. 13 interrupt input pin polarity ? r/w. this bit specifies th e polarity of each interrupt signal connected to the interrupt pins. 0 = active high. 1 = active low. 12 delivery status ? ro. this field contains the current st atus 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 inject ed, but delivery is not complete. 11 destination mode ? r/w. this field dete rmines the interpretati on 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 regi ster 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 modes will only operate as intended when used in conjunction with a specific trigger mode. these encodings are listed in the note below: 7:0 vector ? r/w. this field contains the interrupt vector for this interrupt. values range between 10h and feh. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 397 lpc interface bridge registers (d31:f0) 13.6 real time clock regi sters (lpc i/f?d31:f0) 13.6.1 i/o register addres s map (lpc i/f?d31:f0) the rtc internal registers and ram are or ganized as two banks of 128 bytes each, called the standard and extended banks. the first 14 bytes of the standard bank contain the rtc 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. the register map appears in table 13-124 . 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-125 . 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 firs t read the value, 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 rtc index bits 6:0 are readable fr om port 74h, bit 7 will always 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. 13.6.2 indexed register s (lpc i/f?d31:f0) 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-125 . table 13-124.rtc i/o regi sters (lpc i/f?d31:f0) 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 targ et register (if enabled) www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 398 datasheet 13.6.2.1 rtc_rega?register a (lpc i/f?d31:f0) 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 chipset reset signal. table 13-125.rtc (standard) ram bank (lpc i/f?d31:f0) 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 bit description 7 update in progress (uip) ? r/w. this bit may be monito red 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 select (dv[2:0]) ? r/w. these three bits cont rol 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 399 lpc interface bridge registers (d31:f0) 13.6.2.2 rtc_regb?register b (general configuration) (lpc i/f?d31:f0) rtc index: 0bh attribute: r/w default value: u0u00uuu (u: undefined) size: 8-bit lockable: no power well: rtc 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 pi e 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 does not toggle 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 bit description bit description 7 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 subs equent 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 ea rly in bios post after each powerup directly after coin-cell battery insertion. 6 periodic interrupt enable (pie) ? r/w. this bit is cleare d by rsmrst#, but not on any other reset. 0 = disable. 1 = enable. allows an interrupt to occur with a time base set with the rs bits of register a. 5 alarm interrupt enable (aie) ? r/w. this bit is cleared by rtcrst#, 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 second, one an hour, once a day, or one a month. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 400 datasheet 13.6.2.3 rtc_regc?register c (flag register) (lpc i/f?d31:f0) 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. 4 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. 3 square wave enable (sqwe) ? r/w. this bit serves no function in the chipset. it is left in this register bank to provide compatibility with the motorola 146818b. the chipset has no sqw pin. this bit is cleare d by rsmrst#, but not on any other reset. 2 data mode (dm) ? r/w. this bit specifies either binary or bcd data representation. this bit is not affected by rs mrst# nor any other reset signal. 0 = bcd 1 = binary 1 hour format (hourform) ? r/w. this bit indicates the hour byte format. this bit is not affected by rsmrst# no r 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. 0 daylight savings enable (dse) ? r/w. this bit triggers two sp ecial hour updates per year. the days for the hour adjustment are those specified in united states federal law as of 1987, which is different than previous years. this bit is not affected by rsmrst# nor any other reset signal. 0 = daylight savings time updates do not occur. 1 = a) update on the fi rst sunday in april, where time increments from 1:59:59 am to 3:00:00 am. b) update on the last sunday in october when the time first reaches 1:59:59 am, it is changed to 1:00:00 am. the time must increment normally for at least two update cycles (seconds) previous to these conditions for the ti me change to occur properly. bit description bit description 7 interrupt request flag (irqf) ? ro. irqf = (pf * pie) + (af * aie) + (uf *ufe). this bit also causes the rtc interrupt to be asserted. this bit is cleared upon rsmrst# or a read of register c. 6 periodic interrupt flag (pf) ? ro. this bit is cleared upon rsmrst# or a read of register c. 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 ta p specified by the rs bits of register a is 1. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 401 lpc interface bridge registers (d31:f0) 13.6.2.4 rtc_regd?register d (flag register) (lpc i/f?d31:f0) rtc index: 0dh attribute: r/w default value: 10uuuuuu (u: undefined) size: 8-bit lockable: no power well: rtc 13.7 processor interface regi sters (lpc i/f?d31:f0) table 13-126 is the register address map for the processor interface registers. 5 alarm 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. 4 update-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 bit description 7 valid ram and time bit (vrt) ? r/w. 0 = this bit should always be written as a 0 fo r write cycle, however 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 sh ould 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 as sumed. 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 0?s to mimi c the functionality of the motorola 146818b. these bits are not affected by any reset assertion. table 13-126.processor interface pci re gister 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 r/w cf9h rst_cnt reset control 00h r/w www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 402 datasheet 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 bit description 7 serr# nmi source status (serr#_nmi_sts) ? ro. 1 = bit is set if a pci agent detected a syst em error and pulses th e pci serr# line and if bit 2 (pci_serr_en) is cleared. this in terrupt 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 chipset internal sources of serr; this includes serr assertions forwarded from the secondary pci bus, errors on a pci express* port, or other inte rnal functions that generate serr#. 6 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. th is 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. 5 timer counter 2 out status (tmr2_out_sts) ? ro. this bit reflects the current state of the 8254 counter 2 output. counter 2 must be programmed following any pci reset for this bit to have a de terminate value. when writing to port 61h, this bit must be a 0. 4 refresh cycle toggle (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. 3 iochk# nmi enable (iochk_nmi_en) ? r/w. 0 = enabled. 1 = disabled and cleared. 2 pci serr# enable (pci_serr_en) ? r/w. 0 = serr# nmis are enabled. 1 = serr# nmis are di sabled and cleared. 1 speaker data enable ( spkr_dat_en) ? r/w. 0 = spkr output is a 0. 1 = spkr output is equivalent to the counter 2 out signal value. 0 timer counter 2 enable (tim_cnt2_en) ? r/w. 0 = disable 1 = enable www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 403 lpc interface bridge registers (d31:f0) 13.7.2 nmi_en?nmi enable (and real time clock index) register (lpc i/f?d31:f0) i/o address: 70h attribute: r/w (special) default value: 80h size: 8-bit lockable: no power well: core note: the rtc index field is write-only for normal op eration. 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 13.7.4 coproc_err?coprocessor error register (lpc i/f?d31:f0) i/o address: f0h attribute: r/w default value: 00h size: 8-bits lockable: no power well: core bits description 7 nmi 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). th is data goes to the rtc to select which register or cmos ram address is being accessed. bit description 7:2 reserved 1 alternate a20 gate (alt_a20_gate) ? r/w. this bit is or?d with the a20gate input signal to generate a20m# to the processor. 0 = a20m# signal can po tentially go active. 1 = this bit is set when init# goes active. 0 init_now ? r/w. when this bit transitions fro m a 0 to a 1, the chipset will force init# active for 16 pci clocks. bits description 7:0 coprocessor error (coproc_err) ? r/w. any value written to this register will cause ignne# to go active, if ferr# had ge nerated an internal irq13. for ferr# to generate an internal irq13, the coproc_err_en bit (device 31:function 0, offset d0, bit 13) must be 1. reads to th is register always return 00h. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 404 datasheet 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 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 writing 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-127 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. bit description 7:4 reserved 3 full reset (full_rst) ? r/w. this bit is used to de termine the states of slp_s3#, slp_s4#, and slp_s5# after a cf9 hard rese t (sys_rst =1 and rst_cpu is set to 1), after pwrok going low (with rsmrst# high), or after two tco timeouts. 0 = chipset will keep slp_s3 #, slp_s4# and slp_s5# high. 1 = chipset 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 sys_reset#, pwrok# , and watchdog timer reset sources. 2 reset cpu (rst_cpu) ? r/w. when this bit transitions from a 0 to a 1, it initiates a hard or soft reset, as de termined by the sys_rst bit (bit 1 of this register). 1 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 chipset performs a soft reset by activating init# for 16 pci clocks. 1 = when rst_cpu bit goes from 0 to 1, the chipset performs a hard reset by activating pltrst# and sus_stat# active for about 5-6 milliseconds, however the slp_s3#, slp _ s4# and slp_s5# will not go ac tive. the chipset main power well is reset when this bit is 1. it also resets the resume well bits (except for those noted throughout the datasheet). 0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 405 lpc interface bridge registers (d31:f0) 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 table 13-127.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, ro, 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 a9h cx-state_cnf cx state config uration (netbook only). 00h r/w aah c4-timing_cnt c4 timing control (netbook only). 00h r/w abh bm_break_en bm_break_en 00h r/w adh msc_fun miscellaneous functionality 00h r/w b8?bbh gpi_rout gpi route control 0000000 0h r/w bit description 15:11 reserved 10 bios_pci_exp_en ? r/w. this bit acts as a glob al enable for th e sci associated with the pci express* ports. 0 = the various pci express ports and (g )mch/cpu cannot cause the pci_exp_sts bit to go active. 1 = the various pci express ports and (g)mch/cpu can cause the pci_exp_sts bit to go active. 9 pwrbtn_lvl ? ro. this bit indicates the curre nt state of the pwrbtn# signal. 0 = low. 1 = high. 8 reserved 7 (nettop only) reserved 7 (netbook only) enter c4 when c3 invoked (c4onc3_en) ? r/w. if this bit is set, then when software does a lvl3 read , the chipset-m/chipset-u transitions to the c4 state. 6 i64_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 state machines where there are behavioral differences. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 406 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 5 (nettop only) cpu slp# enable (cpuslp_en) ? r/w. 0 = disable. 1 = enables the cpuslp# signal to go acti ve in the s1 state. this reduces the processor power. 5 (netbook only) reserved 4 smi_lock ? r/wo. when this bit is set, writes to the glb_smi_en bit (pmbase + 30h, bit 0) will have no effect. once th e smi_lock bit is set, writes of 0 to smi_lock bit will have no effect (i.e., on ce set, this bit can only be cleared by pltrst#). 3:2 (nettop only) reserved 3 (netbook 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. 2 (netbook only) pci clkrun# enable (clkrun_en) ? r/w. 0 = disable. chipset-m/chipset-u drives the clkrun# signal low. 1 = enable clkrun# logic to control the system pci clock via the clkrun# and stp_pci# signals. note: when the slp_en# bit is set, the chipset 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 period ic smi# is generated. 00 = 1 minute 01 = 32 seconds 10 = 16 seconds 11 = 8 seconds bit description bit description 7 dram initialization bit ? r/w. this bit does not effect hardware functionality in any way. bios is expected 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 interru pted by a reset by re ading 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 407 lpc interface bridge registers (d31:f0) 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 20 ) 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 responsibility of the bios to program the correct value in this field prior to the first transition to c3 or c4 states (or performing intel speedstep ? technology transitions). note: the new dpslp-to-slp bits (d31:fo: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 cf9 write 4 system reset status (srs) ? r/wc. software clears this bit by writing a 1 to it. 0 = sys_reset# button not pressed. 1 = chipset 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. 3 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 inacti ve and thrmtrip# goes active while the system is in an s0 or s1 state. notes: 1. this bit is also reset by rsmrst#, an d cf9h resets. it is not reset by the shutdown and reboot associated with the cputhrmtrip# event. 2. the cf9h reset in the desc ription refers to cf9h ty pe core well reset which includes sys_rst#, pwrok/vrmpwrgd lo w, smbus hard reset, tco timeout. this type of reset will clear cts bit. 2 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 a ssertion width field (d31:f0:offset a4h:bits 5:4). the chipset be gins the timer when slp_s4 # is asserted during s4/ s5 entry, or when the rsmrst# input is de asserted during g3 ex it. 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 th e rsmrst# pin, but can be set in some cases before the default value is readable. 1 cpu power failure (cpupwr_flr) ? r/wc. 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 sampled using the rtc clock. therefore, low times that are less than one rtc clock period may no t be detected by the chipset. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 408 datasheet note: vrmpwrok is sampled using the rtc clock. th erefore, low times that are less than one rtc clock period may not be detected by the chipset. 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: 8-bit lockable: no usage: acpi, legacy power well: rtc 0 pwrok failure (pwrok_flr) ? r/wc. 0 = software clears this bit by writing a 1 to it, or when the system goes into a g3 state. 1 = this bit will be set any time pwrok goes low, wh en the system was in s0, or s1 state. the bit will be cleared only by software by writ ing a 1 to this bit or when the system goes to a g3 state. note: see chapter 5.14.11.3 - volume 1 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 bit description 7:6 swsmi_rate_sel ? r/w. this field indicates wh en 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 an y 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, th e hardware will prevent the slp_s4# signal from deasserting within this minimum time pe riod after asserting. rtcrst# forces this field to the conservative default state (00b) 3 slp_s4# assertion st retch 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 register. this bit is cleared by rtcrst# 2 rtc power status (rtc_pwr_sts) ? r/w. this bit is set when rtcrst# indicates a weak or missing battery. the bit is not cl eared by any type of reset. the bit will remain set until the software clears it by writing a 0 back to this bit position. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 409 lpc interface bridge registers (d31:f0) note: rsmrst# is sampled using the rtc clock. therefore, low times that are less than one rtc clock period may not be detected by the chipset. 13.8.1.4 cx-state_cnf?cx state configuration register (pm?d31:f0) (netbook only) 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. 1 power failure (pwr_flr) ? r/wc. this bit is in the rt c 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 trickl e 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. 0 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 rtc well and is not cleared by any type of reset except writes to cf9h or rtcrst#. 0 = system will return to s0 stat e (boot) after power is re-applied. 1 = system will return to the s5 state (except if it was in s4, in which case it will return 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: bit will be set when thrmtr ip#-based shutdown occurs. bit description bit description 7 scratchpad (sp) ? r/w. 6:5 reserved 4 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 chipset on netbook platform will not attempt to automatically return to a previous c3 or c4 state. 1 = when this bit is a 1 and chipset on netb ook platform 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. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 410 datasheet 13.8.1.5 c4-timing_cnt?c4 timing control register (pm?d31:f0) (netbook 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. 3 popup mode enable (pume) ? r/w. when this bit is a 0, the chipset on netbook platform behaves like chipset, in that bus ma ster traffic is a break event, and it will return from c3/c4 to c0 based on a break event. see chapter 5. 14.5 for additional details on this mode. 0 = the chipset will treat bus master traffi c a break event, and will return from c3/c4 to c0 based on a break event. 1 = when this bit is a 1 and chipset observes a bus master request, it will take the system from a c3 or c4 state to a c2 stat e and auto enable bus masters. this will let snoops and memory access occur. 2 report zero for bm_s ts (bm_sts_zero_en) ? r/w. 0 = the chipset 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, chipset will not set the bm_sts if there is bus master activity from pci, pci express an d internal 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 wi ll still need to clear the bm_sts bit. 2. it is expected that if the pume bi t (this register, bit 3) is set, the bm_sts_zero_en bit should also be se t. setting one without the other would mainly be for debug or errata workaround. 3. bm_sts will be set by lpc dma (net book only) or lpc masters, even if bm_sts_zero_en is set. 1:0 reserved bit description bit description 7:4 reserved 3:2 dprslpvr to stpcpu ? r/w. this field selects the amount of time that the chipset on netbook platform waits for from the deasse rtion 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 changes the value for t266. bits t266 min t266 max comment 00b 95 s 101 s default 01b 22 s 28 s value used for ?fast? vrms 10b 34 s 40 s recommended value 11b reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 411 lpc interface bridge registers (d31:f0) 13.8.1.6 bm_break_en register (pm?d31:f0) (netbook only) offset address: abh attribute: r/w default value: 00h size: 8-bit lockable: no usage: acpi, legacy power well: core 1:0 dpslp-to-slp ? r/w. this field selects the dpslp# deassertion to cpu_slp# deassertion time (t270). normally this value is determined by the cpu_pll_lock_time field in th e gen_pmcon_2 register. when this field is non-zero, then the values in this register have higher priority. it is software?s responsibility to program these fields in a consistent manner. bit description bits t270 00b use value in cpu_pll_lock_t ime field (default is 30 s) 01b 20 s 10b 15 s (recommended value) 11b 10 s bit description 7 ide_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. serial ata master activity will cause bm_sts to be set and will cause a break from c3/c4. 6 (netbook only) 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 cause bm_sts to be set and will cause a break from c3/c4. 5 pci_break_en ? r/w. 0 = pci traffic will not act as a break event. 1 = pci traffic acts as a break event, ev en if the bm_sts-zero_en and 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 2 ehci_break_en ? r/w. 0 = ehci traffic will not act as a break event. 1 = ehci traffic acts as a break event, 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. 1 uhci_break_en ? r/w. 0 = uhci traffic will not act as a break event. 1 = usb traffic from any of the internal uh cis 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. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 412 datasheet 13.8.1.7 msc_fun?miscellaneous functionality register (pm?d31:f0) offset address: adh attribute: r/w default value: 00h size: 8-bit power well: resume 13.8.1.8 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. 0acaz_break_en ? r/w. 0 = intel hd 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. bit description bit description 7:2 reserved 1:0 usb transient disconnect detect (tdd) ? r/w: this field prevents a short single- ended zero (se0) condition on the usb port s from being interpreted by the uhci host controller as a disconnect . bios should set to 11b. 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 is set. if the gpio0 is not set to an input, this field has no effect. if the system is in an s1?s5 state and if the gpe0_en bit is also set, then 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 413 lpc interface bridge registers (d31:f0) 13.8.2 apm i/o decode table 13-128 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 13.8.3 power management i/o registers table 13-129 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 lo cation (128-byte aligned). the registers are defined to support the acpi 2.0 specification, and use the same bit names. note: all reserved bits and registers will always re turn 0 when read, and will have no effect when written. table 13-128.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 between the os and the smi handler. writes to this port not only store data in the apmc regi ster, but also generates an smi# when the apmc_en bit is set. bit description 7:0 used to pass data between the os and the smi handler. basically, this is a scratchpad register and is not affected by any other register or functi on (other than a pci reset). www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 414 datasheet table 13-129.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+2 0000h 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, wo 14h?16h ? reserved (nettop only) ? ? ? 14h lv2 level 2 (netbook only) p_blk+4 00h ro 15h lv3 level 3 (netbook only) p_blk+5 00h ro 16h lv4 level 4 (netbook only) p_blk+6 00h ro 17h?1fh ? reserved ??? 20h ? reserved (nettop only) ? ? ? 20h pm2_cnt pm2 control (netbook only) pm2a_cnt_blk 00h r/w 28h?2bh gpe0_sts general purpose event 0 status gpe0_blk 00000000h r/wc 2ch?2fh gpe0_en general purpose event 0 enables gpe0_blk+4 00000000h r/w 30h?33h smi_en smi# control and enable 00000000h r/w, wo, r/w (special) 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_st s alternate gpi smi status 0000h r/wc 3ch?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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 415 lpc interface bridge registers (d31:f0) 13.8.3.1 pm1_sts?power management 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, an d the corresponding _en bit is set in the pm1_en register, then the chipset will generate a wake event. once back in an s0 state (or if already in an s0 state when the event occurs ), the chipset will also generate an sci if the sci_en bit is set, or an sm i# 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. 50h ? reserved (nettop only) 50h ss_cnt intel speedstep ? te c h n o l o g y control (netbook only) 01h r/w (special) 51h?5fh ? reserved ??? 54h?57h c3_res c3-residency register (netbook only) ? 00000000h ro, r/w 60h?7fh ? reserved for tco ? ? ? table 13-129.acpi and legacy i/o register map (sheet 2 of 2) pmbase + offset mnemonic register name acpi pointer default type bit description 15 wake status (wak_sts) ? r/wc. this bit is not affect ed by hard resets caused by a cf9 write, but is reset by rsmrst#. 0 = software clears this bi t 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 chipset will transition the system to the on state. if the afterg3_en bit is not set and a powe r failure (such as removed batteries on a netbook platform) occurs without the slp_en bit set, the system will return to an s0 state when power re turns, and the wak_sts bit will not be set. if the afterg3_en bit is set and a powe r 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). www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 416 datasheet 14 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 message receiv ed indication has not been cleared in the root port, then the bit wi ll remain active (i.e. all inputs to this bit are level- sensitive). 1 = this bit is set by hardware to indica te that the system woke due to a pci express wakeup event. this wakeup event can be caused by the pci express wake# pin being active or receipt of a pci express pm e 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 state of the pciexp_wake_dis bit. note: this bit does not itself cause a wake event or prevent entry to a sleeping state. thus, if the bit is 1 and the syst em is put into a sleeping state, the system will not automatically wake. 14 reserved 13:12 reserved 11 power button override status (prbtnor_sts) ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set any time a power button ov erride occurs (i.e., the power button is pressed for at least 4 consecutive second s), or due to the corresponding bit in the smbus slave message. the power butt on override causes an unconditional transition to the s5 state, as well as sets the afterg# 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. note that if this bit is still asserted when the global sci_en is set then an sci will be generated. 10 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 genera tes an alarm (assertion of the irq8# signal). additionally if the rtc_en bit (pmbase + 02h, bit 10) is set, the setting of the rtc_sts bit will generate a wake event. 9 reserved bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 417 lpc interface bridge registers (d31:f0) 8 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 mo re 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 hard ware when the pwrbtn# si gnal is asserted low, independent of any other enable bit. in the s0 state, while 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 set. the pwrbtn# signal must go inactive and active again to set the pwrbtn_sts bit. 7:6 reserved 5 global status (gbl _sts) ? r/wc. 0 = the sci 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. 4 (nettop only) reserved 4 (netbook only) bus master status (bm_sts) ? r/wc. this bit will not cause a wake event, sci or smi#. 0 = software clears this bi t by writing a 1 to it. 1 = set by the chipset on netbook platform when a bus master requests access to main memory. bus master activity is dete cted by any of the pci requests being active, any internal bus master reques t being active, the bm_busy# signal 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 (netbook only) and bus master activity will always set the bm_sts bit, even if the bm_sts_zero_en bit is set. 3:1 reserved 0 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 = this bit gets set any time bit 22 of the 24-bit timer goes high (bits are numbered from 0 to 23). this will oc cur every 2.3435 seconds. when the tmrof_en bit (pmbase + 02h, bit 0) is set, then the setting of the tmrof_sts bit will additionally gene rate an sci or smi# (depending on the sci_en). bit description www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 418 datasheet 13.8.3.2 pm1_en?power mana gement 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 14 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 th e 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 system. 14 reserved 13:11 reserved 10 rtc event enable (rtc_en) ? r/w. this bit is in the rtc well to allow an rtc 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 ge nerated 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_sts bit goes active. 9 reserved . 8 power button enable (pwrbtn_en) ? r/w. this bit is used to enable the setting of the pwrbtn_sts bit to gene rate a power management event (smi#, sci). pwrbtn_en has no effe ct on the pwrbtn_sts bit (pmbase + 00h, bit 8) being set by the assertion of the power bu tton. the power button is always enabled as a wake event. 0 = disable. 1 = enable. 7:6 reserved . 5 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 sci on gbl_sts going active. 4:1 reserved . 0 timer overflow interrupt enable (tmrof_en) ? r/w. works in conjunction with the sci_en bit (pmbase + 04 h, bit 0) as described below: tmrof_en sci_en effect when tmrof_sts is set 0 x no smi# or sci 10 smi# 11 sci www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 419 lpc interface bridge registers (d31:f0) 13.8.3.3 pm1_cnt?power management 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 the system to sequence into the sleep state defined by the slp_typ field. 12:10 sleep type (slp_typ) ? r/w. this 3-bit field defines the type of sleep the system should enter when the slp_en bit is set to 1. these bits are only reset by rtcrst#. 9:3 reserved . 2 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. 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 suspend-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. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 420 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 control 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 1 (nettop only) reserved 1 (netbook only) bus master reload (bm_rld) ? r/w. this bit is treated as a scratchpad bit. this bit is reset to 0 by pltrst# 0 = bus master requests will no t cause a break from the c3 state. 1 = enable bus master requests (internal, external or bm_busy#) to cause a break from the c3 state. if software fails to set this bit before going to c3 st ate, the chipset on netbook platform will still return to a snoopable stat e from c3 or c4 states due to bus master activity. 0 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 bit description 31:24 reserved 23:0 timer value (tmr_val) ? 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 continues counti ng 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 421 lpc interface bridge registers (d31:f0) 17 throttle status (thtl_sts) ? ro. 0 = no clock throttling is occurring (maximum processor performance). 1 = indicates that the clock state machine is throttling the processor performance. this could be due to the tht_en bit or the force_thtl bit being set. 16:9 reserved 8 force thermal throttling (force_thtl) ? r/w. software can se t this bit to force the thermal throttling function. 0 = no forced throttling. 1 = throttling at the duty cycle specified in thrm_dty starts immediately, and no smi# is generated. 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 a pproximate percentage of time the stpclk# signal is asserted while in the throttle mode. the stpclk# throttle period is 1024 pciclks. note that the throttling only occurs if the system is in the c0 state. for netbook only, if in the c2, c3, or c4 state, no throttling occurs. once the thrm_dty field is written, any subs equent writes will have no effect until pltrst# goes active. 4 thtl_en ? r/w. when set and the system is in a c0 state, it enables a processor- controlled stpclk# throttling. the duty cy cle is selected in the thtl_dty field. 0 = disable 1 = enable 3:1 thtl_dty ? r/w. this field determ ines the duty cycle of the throttling when the thtl_en bit is set. the duty cycle indicate s the approximate perc entage 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 www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 422 datasheet 13.8.3.6 lv2 ? level 2 register (netbook only) 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 intel ? ia64 processors or sy stems with mo re than 1 logical processor, unles s appropriate semaphoring software has been put in place to ensure that all threads/proce ssors are ready for the c2 state wh en the ?read to this register? instruction occurs. 13.8.3.7 lv3?level 3 register (netbook 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 notes: 1. if the c4onc3_en bit is set, reads this register will initiate a lvl4 transition rather than a lvl3 transition. in the event th at software attempts to simultaneously read the lvl2 and lvl3 registers (which is not permitted), the chipset on netb ook platform will ignore the lvl3 read, and only perform a c2 transition. 2. this register should not be used by ia64 pr ocessors or systems with more than 1 logical processor, unless appropriate semaphoring soft ware has been put in place to ensure that all threads/processors are ready for the c3 state when the ?read to this register? instruction occurs. bit description 7:0 reads to this register return all 0s, writes to this regi ster have no effect. reads to this register generate a ?enter a level 2 power state? (c2) to the clock control logic. this will cause the stpclk# signal to go active, an d 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 register generate a ?enter a c3 power state? to the clock control logic. the c3 state persists until a break event occurs. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 423 lpc interface bridge registers (d31:f0) 13.8.3.8 lv4?level 4 register (netbook 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 ia64 pr ocessors or systems with more than 1 logical processor, unless appropriate semaphoring software has been put in place to ensure that all threads/processors are re ady for the c4 stat e when the ?read to this register? instruction occurs. 13.8.3.9 pm2_cnt?power management 2 control register (netbook only) i/o address: pmbase + 20h ( acpi pm2_blk ) attribute: r/w default value: 00h size: 8-bit lockable: no usage: acpi power well: core 13.8.3.10 gpe0_sts?general purpose event 0 status register i/o address: pmbase + 28h ( acpi gpe0_blk ) attribute: r/wc default value: 00000000h size: 32-bit lockable: no usage: acpi power well: resume this register is symmetrical to the general purpose event 0 enable register. unless indicated otherwise below, if the corresponding _en bit is set, then when the _sts bit get set, the chipset will generate a wake event. once back in an s0 state (or if already in an s0 state when the event occurs), th e chipset 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 15:0 are not. all are reset by rsmrst#. bit description 7:0 reads to this register return all 0s, writes to th is register have no effect. reads to this register generate a ?enter a c4 power state? to the clock control logic. the c4 state persists until a break event occurs. bit description 7:1 reserved 0 arbiter disabl e (arb_dis) ? r/w. this bit is a scratchp ad bit for legacy software compatibility. software typicall y sets this bit to 1 prior to entering a c3 or c4 state. when a transition to a c3 or c4 state occurs, chipset on ne tbook platform will automatically prevent any internal or exte rnal non-isoch bus masters from initiating any cycles up to the (g)mch/cpu. this blocking starts immediately upon the chipset sending the go?c3 message to the (g)mch/cpu. the blocking stops when the ack-c2 message is received. note that this is not really blocking, in th at messages (such as from pci express*) are just queued and held pending. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 424 datasheet bit description 31:16 gpion_sts ? r/wc. 0 = software clears this bi t 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 corresponding gp_inv bit is set). 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 co rresponds to gpio15... and bit 16 corresponds to gpio0. 15 reserved 14 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 reset. this bit is set when usb uhci controller #4 needs to cause a wake. additionally if the usb4_en bit is set, the setting of the usb4_sts bit will generate a wake event. 13 pme_b0_sts ? r/wc. this bit will be set to 1 by the chipset when any internal device with pci power management capabili ties 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_s ts bit will generate an sci (or smi# if sci_en is not set). if the pme_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 not set) 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. 12 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. additionally if the usb3_en bit is set, the setting of the usb3_sts bit will generate a wake event. 11 pme_sts ? r/wc. 0 = software clears this bi t 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 will generate a wake event, and an sci will be generated. if the system is in an s5 state due to power button override or a power failur e, then pme_sts will not cause a wake event or sci. 10 (nettop only) reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 425 lpc interface bridge registers (d31:f0) 10 (netbook only) batlow_sts ? r/wc. (netbook 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. 9 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 me ssage received from the (g)mch/cpu 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 corre sponding 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. 8 ri_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. 7 smbus wake status (smb_wak_sts) ? r/wc. the smbus controller 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 chipset?s smbus logic. 1 = set by hardware to indicate that the wake event was caused by the chipset?s smbus logic.this bit will be set by the wake/smi# co mmand type, even if the system is already awake. the smi ha ndler should then clear this bit. notes: 1. this bit is set by the smbus slave command 01h (wake/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 sl ave receiving a mess age, it will be cleared by internal logic when a thrmtrip# event happens or a power button override event. however, thrmtrip# or power button override event will not clear smb_wak_sts if it is set due to smbalert# signal going active. 3. the smbalert_sts bit (d31:f3:i/o offs et 00h:bit 5) should be cleared by software before the smb_wak_sts bit is cleared. 6 tcosci_sts ? r/wc. software clears this bit by writing a 1 to it. 0 = toc logic did not cause sci. 1 = set by hardware when th e tco logic causes an sci. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 426 datasheet 13.8.3.11 gpe0_en?general purpose event 0 enables register i/o address: pmbase + 2ch ( acpi gpe0_blk + 4 ) attribute: r/w default value: 00000000h size: 32-bit lockable: no usage: acpi power well: bits 0?7, 9, 12, 14?31 resume, bits 8, 10?11, 13 rtc this register is symmetrical to the general purpose event 0 status register. 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 ar e all cleared by rsmrst#. the rtc sell bits are cleared by rtcrst#. 5 ac97_sts ? r/wc. this bit will be set to 1 when the codecs are attempting to wake the system and the pme events for the codecs are armed for wakeup. a pme is armed by programming the appropriate p mee bit in the power management control and status register at bit 8 of of fset 54h in each ac?97 function. 0 = software clears this bit by writing a 1 to it. 1 = set by hardware when the codecs ar e attempting to wake the system. the ac97_sts bit gets set only from the following case: 1.the pmee bit for the functi on is set, and the ac-link bit clock has been shut and the routed acz_sdin line is high (for audi o, if routing is disabled, no wake events are allowed. note: this bit is not affected by a hard reset caused by a cf9h write. 4 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 cause a wake. wake event will be generated if the corresponding usb 2_en bit is set. 3 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 cause a wake. wake event will be generated if the corresponding usb 1_en bit is set. 2 swgpe_sts ? r/wc. the swgpe_ctrl bit (bit 1 of gpe_ctrl re g) acts as a level input to this bit. 1 hot_plug_sts ? r/wc. 0 = this bit is cleared by writ ing a 1 to this bit position. 1 = when a pci express* hot-plug event oc curs. this will cause an sci if the hot_plug_en bit is set in the gep0_en register. 1 reserved 0 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# sign al 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 po wer management event (sci or smi#). bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 427 lpc interface bridge registers (d31:f0) bit description 31:16 gpin_en ? r/w. these bits enable the corresp onding gpi[n]_sts bits being set to cause a sci, and/or wake event. these bits are cleared by rsmrst#. note: mapping is as follows: bit 31 corresponds to gpi o 15... and bit 16 corresponds to gpi o 0. 15 reserved 14 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. 13 pme_b0_en ? r/w. 0 = disable 1 = enables the setting of the pme_b0_sts bit to generate a wake 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, bu t not power button override. this bit de faults to 0. note: it is only cleared by software or rtcr st#. it is not clea red by cf9h writes. 12 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. 11 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). 10 (nettop only) reserved 10 (netbook only) batlow_en ? r/w. (netbook only) 0 = disable. 1 = enables the batlow# signal to caus e 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. 9 pci_exp_en ? r/w. 0 = disable sci generation up on pci_exp_sts bit being set. 1 = enables chipset 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)mch/cpu, to cause an sci due to wake/pme events. 9 reserved . must be programmed to 0. 8 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 = enables the setting of the ri_sts to generate a wake event. 7 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 428 datasheet 13.8.3.12 smi_en?smi control and enable register i/o address: pmbase + 30h attribute: r/w, r/w (special), 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. 6 tcosci_en ? r/w. 0 = disable. 1 = enables the setting of the tc osci_sts to generate an sci. 5 ac97_en ? r/w. 0 = disable. 1 = enables the setting of the ac97_sts to generate a wake event. note: this bit is also used for intel hd audi o when the intel high definition audio host controller is enabled. 4 usb2_en ? r/w. 0 = disable. 1 = enables the setting of the usb2_sts to generate a wake event. 3 usb1_en ? r/w. 0 = disable. 1 = enables the setting of the usb1_sts to generate a wake event. 2 swgpe_en? r/w. this bit allows software to control the asse rtion 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 se t swgpe_sts (acts as a level input) if swgpe_sts, swgpe_en, and sci_en ar e all 1s, an sci wi ll be generated if swgpe_sts = 1, swgpe_en = 1, sci_en = 0, and gbl_smi_en = 1, then an smi# will be generated 1 hot_plug_en ? r/w. 0 = disables sci generation upon the hot_plug_sts bit being set. 1 = enables the chipset 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. 1 reserved 0 thrm_en ? r/w. 0 = disable. 1 = active assertion of the thrm# signal (a s defined by the thrm_pol bit) will set the thrm_sts bit and generate a powe r management event (sci or smi). bit description bit description 31:26 reserved 25 reserved 24:19 reserved 18 intel_usb2_en ? r/w. 0 = disable 1 = enables intel-specific usb2 smi logic to cause smi#. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 429 lpc interface bridge registers (d31:f0) 17 legacy_usb2_en ? r/w. 0 = disable 1 = enables legacy usb2 logic to cause smi#. 16:15 reserved 14 periodic_en ? r/w. 0 = disable. 1 = enables the chipset to generate an smi# when the periodic_sts bit (pmbase + 34h, bit 14) is set in the smi_sts register (pmbase + 34h). 13 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 set. 12 reserved 11 mcsmi_enmicrocontroller smi enable (mcsmi_en) ? r/w. 0 = disable. 1 = enables chipset to trap accesses to the microcontroller range (62h or 66h) and generate an smi#. note that ?tra pped? cycles will be claimed by the chipset on pci, but not forwarded to lpc. 10:8 reserved 7 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 inte rrupt 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. 6 software smi# timer enable (swsmi_tmr_en) ? r/w. 0 = disable. clearing the swsmi_tmr_en bi t 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 sett ing), swsmi_tmr_sts is set and an smi# is generated. swsm i_tmr_en stays set until cleared by software. 5 apmc_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#. 4 slp_smi_en ? r/w. 0 = disables the generation of smi# on slp_en. note that this bit must be 0 before the software attemp ts to transition the system into a sleep state by writing 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 state based on that write to the slp_en bit. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 430 datasheet 13.8.3.13 smi_sts?smi status register i/o address: pmbase + 34h attribute: 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 chipset 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 chipset uses the same gpe0_en register (i/o address: pmbase+2ch) to enable/disable both smi and acpi sci general purpose input events. acpi os assumes that it owns the entire gpe0_en register per acpi spec. problems arise when some of the general-pu rpose inputs are enabled as smi by bios, and some of the general purpose inputs are en abled for sci. in this case acpi os turns off the enabled bit for any gpix input 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. 3 legacy_usb_en ? r/w. 0 = disable. 1 = enables legacy usb circuit to cause smi#. 2 bios_en ? r/w. 0 = disable. 1 = enables the generation of smi# wh en 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 gets set when software writes 1 to gbl_rls bit, is already a 1 at the ti me that bios_en becomes 1, an smi# will be generated when bios_en gets set. 1 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 chipset to assert smi# low to the processor after smi# has been asserted previously. 0 = once the chipset asserts smi# low, the eos bit is automatically cleared. 1 = when this bit is set to 1, smi# sign al will be deassert ed for 4 pci clocks before its assertion. in the smi handler, the processor should clear all pending smis (by servicing them and th en clearing their respective status bits), set the eos bit, and exit smm. this will allow the smi arbiter to re- assert smi upon detection of an smi ev ent and the setting of a smi status bit. note: chipset is able to generate 1st smi after reset even though eos bit is not set. subsequent smi re quire eos bit is set. 0 gbl_smi_en ? r/w. 0 = no smi# will be generated by chipset. this bit is reset by a pci reset event. 1 = enables 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 bit description 31:27 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 431 lpc interface bridge registers (d31:f0) 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 bi ts associated with this function are located in the spi registers. 25 reserved 24:22 reserved 21 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 mast er accesses an assigned register (or a sequence of accesses). see section 10.1.32 through section 10.1.35 for details on the spec ific 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. 20:19 reserved 19 reserved 18 intel_usb2_sts ? ro. this non-sticky 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. this bit will not be active if the enable bits are not set. writes to this bit will have no effect. 17 legacy_usb2_sts ? ro. this non-sticky read-only bit is a logical or of each of the smi status bits in the usb2 le gacy support register anded with the corresponding enable bi ts. this bit will not be active if the enable bits are not set. writes to this bit wi ll have no effect. 16 smbus smi status (smbus_smi_sts) ? r/wc. software clears this bit by writing a 1 to it. 0 = this bit is set from the 64 khz clock domain used by the smbus. software must wait at least 15.63 us after the initial assertion of this bit before clearing it. 1 = indicates that the smi# 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 receiving a host notify message and the host_notify_intren and the sm b_smi_en bits are set, or 4. the chipset dete cting the smlink_slave_smi command while in the s0 state. 15 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 14 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 determ ined by the per_smi_sel bits. if the periodic_en bit (pmbase + 30h, bit 14) is also set, the chipset generates an smi#. 13 tco_sts ? r/wc. software clears this bit by writing a 1 to it. 0 = smi# not caused by tco logic. 1 = indicates the smi# was caused by the tco logic. note that this is not a wake event. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 432 datasheet 12 device monitor status (devmon_sts) ? ro. 0 = smi# not caused by device monitor. 1 = set if bit 0 of the devact_sts regist er (pmbase + 44h) is set. the bit is not sticky, so writes to this bit will have no effect. 11 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 rang e (62h or 66h). 1 = set if there has been an access to the power manageme nt microcontroller range (62h or 66h) and the microcontrol ler 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 th at the microcontroller is on lpc. if this bit is set, and the mc smi_en bit is also set, th e chipset will generate an smi#. 10 gpi_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 bi t 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. 9 gpe0_sts ? ro. this bit is a logical or of the bits 14:10, 8: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. 8 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. 7 reserved 6 swsmi_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 th e software smi# timer expires. 5 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 generated by a write access to the apm control register with the apmc_en bit set. 4 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 sl p_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. 3 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. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 433 lpc interface bridge registers (d31:f0) 13.8.3.14 alt_gp_smi_en?alterna te 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 13.8.3.15 alt_gp_smi_sts?altern ate 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 2 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 bi t is cleared when software writes a 1 to its bit position. 1:0 reserved bit description bit description 15:0 alternate gpi smi enable ? r/w. these bits are used to enable the corresponding gpio to cause an smi#. for th ese 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 correspon ds to gpio15... bit 0 corresponds to gpio0. bit description 15:0 alternate gpi smi status ? r/wc. these bits report th e status of the corresponding gpios. 0 = inactive. software clears th is bit by writing a 1 to it. 1 = active these bits are sticky. if the following conditions are true, then an smi# will be generated and the gpe0_sts bit set: ? the corresponding bit in the alt_gpi_sm i_en register (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. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 434 datasheet 13.8.3.16 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.17 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 interru pt is active. this register is used in conjunction with the periodic smi# timer to detect any system activity for legacy power management. the periodic smi# timer indicate s 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 7:2 reserved 1 swgpe_ctrl? r/w. this bit allows softwa re to control the assertion of swgpe_sts bit. this bit is used by hardware as the le vel input signal for the swgpe_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 swgp e_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. 0 thrm#_pol ? r/w. this bit controls the po larity of the thrm# pin needed 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 12 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 9 pirqdh_act_sts ? r/wc. pirq[d or h]. 0 = the corresponding pci inte rrupts have not been active. 1 = at least one of the corresponding pci inte rrupts has been active . clear this bit by writing a 1 to the bit location. 8 pirqcg_act_sts ? r/wc. pirq[c or g]. 0 = the corresponding pci inte rrupts have not been active. 1 = at least one of the corresponding pci inte rrupts has been active . clear this bit by writing a 1 to the bit location. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 435 lpc interface bridge registers (d31:f0) 13.8.3.18 ss_cnt? intel speedstep ? technology control register (netbook only) i/o address: pmbase +50h attribute: r/w (special) default value 01h size: 8-bit lockable: no usage: acpi/legacy power well: core note: writes to this register will initiate an intel speedstep technology transition that involves a temporary transition to a c3-lik e state in which the stpclk# signal will go active. an intel speedstep technology transition always occur on writes to the ss_cnt register, even if the value written to ss_state is the same as the previous value (after this ?transition? the system would still be in the same intel speedstep technology state). if the ss_en bit is 0, then writes to this register will have no effect and reads will return 0. 7 pirqbf_act_sts ? r/wc. pirq[b or f]. 0 = the corresponding pci interrupts have not been active. 1 = at least one of the corresponding pci inte rrupts has been active . clear this bit by writing a 1 to the bit location. 6 pirqae_act_sts ? r/wc. pirq[a or e]. 0 = the corresponding pci interrupts have not been active. 1 = at least one of the corresponding pci inte rrupts has been active . clear this bit by writing a 1 to the bit location. 5:1 reserved 0 ide_act_sts ? r/wc. ide primary drive 0 and drive 1. 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 . the enable bit is in the atc register (d31:f1:offset c0h). clear this bit by writing a 1 to the bit location. bit description bit description 7:1 reserved 0 ss_state (intel speedstep ? technology state) ? r/w (spe cial). when this bit is read, it returns the last value written to this register. by convention, this will be the current intel speedstep technology state. writes to this register causes a change to the intel speedstep technolo gy state indicated by the value wr itten to this bit. if the new value for ss_state is the same as the previous value, then transition will still occur. 0 = high power state. 1 = low power state note: this is only a convention because the tr ansition is the same regardless of the value written to this bit. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 436 datasheet 13.8.3.19 c3_res? c3 residency register (netbook only) i/o address: pmbase +54h attribute: r/w/ro default value 00000000h size: 32-bit lockable: no usage: acpi/legacy power well: core the value in this field increments at the same rate as the power management timer. this field increments while stp_cpu# is active (i.e. the cpu is in a c3 or c4 state). this field will roll over in the same way as the power management timer, however the most significant bit is not sticky. 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. for tco pci configuration 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 configuratio n space. the following table shows the mapping of the registers within that 32-byte range. each register is described in the following sections. 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. if the c3_resedency_mod e bit is clear, this field automatically resets to 0 at the point when the lvl3 or lvl4 read occurs. if the c3_residency_mode bit is set, the register does not reset when the lvl3 or lvl4 read occurs. in either mode, it increments while stp_cpu# is active (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 fi eld before performing th e 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. table 13-130.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/w, r/wc www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 437 lpc interface bridge registers (d31:f0) 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 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 08h?09h tco1_cnt tco1 control 0000h r/w, r/w (special), 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 11h r/w 11h ? reserved ?? 12h?13h tco_tmr tco timer initial value 0004h r/w 14h?1fh ? reserved ?? table 13-130.tco i/o register address map tcobase + offset mnemonic register name default type 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. 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). www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 438 datasheet 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 out value ? r/w. this data register fiel d is used for passing commands from the smi handler to the os. writes to this register will set the tco_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 12 dmiserr_sts ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = chipset received a dmi special cycle message via dmi indicating that it wants to cause an serr#. the software must re ad the (g)mch/cpu to determine the reason for the serr#. 11 reserved 10 dmismi_sts ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = chipset received a dmi special cycle message via dmi indicating that it wants to cause an smi. the software must read the (g)mch/cpu to determine the reason for the smi. 9 dmisci_sts ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = chipset received a dmi special cycle message via dmi indicating that it wants to cause an sci. the software must read the (g)mch/cpu to determine the reason for the sci. 8 bioswr_sts ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = chipset sets this bit and generates and smi# to indicate an invalid 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 attempted to the 4 mb lower alias to the bios space, the bioswr_sts will not be set. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 439 lpc interface bridge registers (d31:f0) 7 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 (rtc i/o space, index offset 09h) rolls over 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 rtc battery is first installed (or when rtc power has not been maintain ed). 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 legal value and then clear the newcentury_sts bit. the newcentury_sts bit may take up to 3 rtc clocks for the bit to be cleared after a 1 is written to the bit to clear it . after writing a 1 to this bit, software should not exit the smi handler until verifying that the bit has actually been cleared. this will ensure th at the smi is not re-entered. 6:4 reserved 3 timeout ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = set by chipset to indicate that the sm i was caused by the tco timer reaching 0. 2 tco_int_sts ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = smi handler caused the interrupt by writing to the tco_dat_out register (tcobase + 03h). 1 sw_tco_smi ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = software caused an smi# by writing to the tco_dat_in register (tcobase + 02h). 0 nmi2smi_sts ? ro. 0 = cleared by clearing the associated nmi status bit. 1 = set by the chipset when an smi# occurs because an event occurred that would otherwise have caused an nmi (because nmi2smi_en is set). bit description www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 440 datasheet 13.9.5 tco2_sts?tco2 status register i/o address: tcobase +06h attribute: r/w, r/wc default value: 0000h size: 16-bit lockable: no power well: resume (except bit 0, in rtc) bit description 15:5 reserved 4 smlink slave smi status (smlink_slv_smi_sts) ? r/wc. allow the software to go directly into pre-de termined sleep state. this avoids race conditions. software clears this bit by writing a 1 to it. 0 = the bit is reset by rsmrst#, but not du e to the pci reset associated with exit from s3?s5 states. 1 = chipset sets this bit to 1 when it receives the smi message on the smlink's slave interface. 3 reserved 2 boot_sts ? r/wc. 0 = cleared by chipset based on rsmrst# or by software writing a 1 to this bit. note that software should first clear the seco nd_to_sts bit before writing a 1 to clear the boot_sts bit. 1 = set to 1 when the second_to_sts bit goes 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 chipset will reboot using the ?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 the processor has been programmed to an invalid multiplier. 1 second_to_sts ? r/wc. 0 = software clears this bit by writing a 1 to it, or by a rsmrst#. 1 = chipset 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 register was written. if this bit is set and the no_reboot config bit is 0, then the chipset will reboot the system after the second timeout. the re boot is done by asserting pltrst#. 0 intruder detect (intrd_det) ? r/wc. 0 = software clears this bit by writin g a 1 to it, or by rtcrst# assertion. 1 = set by chipset to indicate that an intrusion was detected. this bit is set even if the system is in g3 state. note: 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 mi croseconds before it is read as a 0. software must be aware of this recove ry time when reading this bit after clearing it. note: 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 handler can clear the intrd_sel bits (tcobase + 0ah, bits 2:1), to avoid further smis. howe ver, 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 sm i# be generated). note: 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 sl ightly different than a classic sticky bit, since most sticky bits woul d remain active indefinite ly when the signal goes active and would immediat ely go inactive when a 1 is written to the bit. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 441 lpc interface bridge registers (d31:f0) 13.9.6 tco1_cnt?tco1 control register i/o address: tcobase +08h attrib ute:r/w, r/w (special), r/wc default value: 0000h size:16-bit lockable: no power well:core bit description 15:13 reserved 12 tco_lock ? r/w (special). 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. 11 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 coun t, and thus cannot re ach 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 messages). 10 send_now ? r/w (special). 0 = the chipset will clear this bit when it has completed sending the message. software must not set this bit to 1 again until the chipset has set it back to 0. 1 = chipset sends an alert on lan event message over the smlink interface, with the software event bit set. setting the send_now bit causes the chipset integrated lan controller to reset, which can have unpredictable side-effects. unless software protects against these side effects, software should not attempt to set this bit. 9 nmi2smi_en ? r/w. 0 = normal nmi functionality. 1 = forces all nmis to instead cause smis. th e functionality of th is bit is dependent upon the settings of the nmi_en bit and the gbl_smi_en bit as detailed in the following table: 8 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 = writing a 1 to this bit causes an nmi. this allows the bios or smi handler to force an entry to the nmi handler. 7:0 reserved nmi_en gbl_smi_en description 0b 0b no smi# at all be cause gbl_smi_en = 0 0b 1b smi# will be caused due to nmi events 1b 0b no smi# at all be cause gbl_smi_en = 0 1b 1b no smi# due to nmi because nmi_en = 1 www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 442 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 tc o_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 pl atform 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 sh ould not be reset when the tco logic resets the platform du e to watchdog timer. 3 gpio11_alert_disable ? r/w. at reset (via rsmrst# asserted) this bit is set and gpio11 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 0 reserved bit description 7:0 tco_message[ n ] ? r/w. the value written into this register will be sent out via the smlink interface in the message field of the alert on lan message. bios can write to this register to indicate its boot progress which ca n be monitored externally. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 443 lpc interface bridge registers (d31:f0) 13.9.9 tco_wdcnt?tco watc hdog 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: 11h 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 watchdog status (wdstatus) ? r/w. the value written to this register will be sent in the alert on lan message on the smlink interface. it can be used by the bios or system management software to indicate more details on the boot progress. this register will be reset to the default of 00h based on rsmrst# (but not pci reset). bit description 7:2 reserved 1 irq12_cause ? r/w. the state of this bit is logically anded with the irq12 signal as received by the chipset?s serirq logic. this bit must be a 1 (default) if the chipset is expected to receive irq12 asse rtions from a serirq device. 0 irq1_cause ? r/w. the state of this bit is logi cally anded with the irq1 signal as received by the chipset?s serirq logic. this bit must be a 1 (default) if the chipset is expected to receive irq1 asse rtions from a serirq device. 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 wr itten. values of 0000h or 0001h will be ignored and should not be attempted. the timer is clocked at approxim ately 0.6 seconds, and thus allows timeouts ranging from 1.2 second to 613.8 s econds. note: the timer has an error of 1 tick (0.6s). the tco timer will only count down in the s0 state. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 444 datasheet 13.10 general purpose i/ o registers (d31:f0) the control for the general purpose i/o sign als is handled through a separate 64-byte i/o space. the base offset for this spac e is selected by the gpiobase register. gpio register i/o address map table 13-131.registers to control gpio address map gpiobase + offset mnemonic register name default access general registers 00h?03h gpio_use_sel gpio use select 1f2af7ffh r/w 04h?07h gp_io_sel gpio input/output select e0e8ffffh r/w 08h?0bh ? reserved ?? 0ch?0fh gp_lvl gpio level for input or output 02fe0000h r/w 10h?13h reserved ?? output control registers 14h?17h ? reserved ?? 18h?1bh gpo_blink gpio blink enable 00040000h r/w 1ch?1fh ? reserved ?? input control registers 20?2bh ? reserved ?? 2c?2fh gpi_inv gpio signal invert 00000000h r/w 30h?33h gpio_use_sel2 gpio use select 2 [63:32] 000300feh r/w 34h?37h gp_io_sel2 gpio input/output select 2 [63:32] 000000f0h r/w 38h?3bh gp_lvl2 gpio level for input or output 2 [63:32] 00030003h r/w www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 445 lpc interface bridge registers (d31:f0) 13.10.1 gpio_use_sel?gpio use select register offset address: gpiobase + 00h attribute: r/w default value: 1f2af7ffh size: 32-bit lockable: no power well: core for 0:7, 16:23, resume for 8:15, 24:31 13.10.2 gp_io_sel?gpio input/ output select register offset address: gpiobase +04h attribute: r/w default value: e0e8ffffh size: 32-bit lockable: no power well: core for 0:7, 16:23, resume for 8:15, 24:31 bit description 31:0 gpio_use_sel[31:0] ? r/w. each bit in this regi ster enables the corresponding gpio (if it exists) to be used as a gp io, rather than for the native function. 0 = signal used as native function. 1 = signal used as a gpio. notes: 1. the following bits are always 1 because they are unmuxed: 6:10,12:15, 24:25 2. the following bits are not implemente d because they are determined by the configuration: 16, 18, 20, 32 3. if gpio[n] does not exist, then the bit in this register will always read as 0 and writes will have no effect. 4. after a full reset (rsmrst#) all multip lexed signals in the resume and core wells are configured as their default func tion. after just a pltrst#, the gpio in the core well are configured as their default function. 5. when configured to gpio mode, the mult iplexing logic will present the inactive state to native logic that uses the pin as an input. 6. all gpios are reset to the default state by cf9h re set except gpio24 bit description 31:0 gp_io_sel[31:0] ? r/w. when configured in na tive 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. www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 446 datasheet 13.10.3 gp_lvl?gpio level for input or output register offset address: gpiobase +0ch attribute: r/w default value: 02fe0000h size: 32-bit lockable: no power well: core for 0:7, 16:23, resume for 8:15, 24:31 13.10.4 gpo_blink?gpo blink enable register 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 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_i o_sel register), 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 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 re gister is undefined when programmed as native mode. bit description 31:0 gp_blink[31:0] ? r/w. the setting of this bit has no e ffect if 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 ou tput, the output signal wi ll blink at a rate of approximately once per second. the high and lo w times have approximately 0.5 seconds each. the gp_lvl bit is not alte red when this bit is set. the value of the corresponding gp_lvl bit remain s 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 the resume well. these bits revert to the default value based on rsmrst# or a write to the cf9h regi ster (but not just on pltrst#). www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 447 lpc interface bridge registers (d31:f0) 13.10.5 gpi_inv?gpio sign al invert register offset address: gpiobase +2ch 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 13.10.6 gpio_use_sel2?gpio use select 2 register[63:32] offset address: gpiobase +30h attribute:r/w default value: 000300feh size:32-bit lockable: no power well:cpu i/o for 17, core for 16, 7:0 bit description 31:0 gp_inv[n] ? r/w. input inversion: 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 se nt 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 in put signal must be acti ve for at least two pci clocks to ensure detection by the chipset. in the s3, s4 or s5 st ates 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 programmed as an output. these bits correspond to gpi that are in the resume well, and will be reset to their default values by rsmrst# or by a write to the cf9h register. 0 = the corresponding gpi_sts bit is set when the chipset detects the state of the input pin to be high. 1 = the corresponding gpi_sts bit is set when the chipset detects the state of the input pin to be low. bit description 17:16, 7:0 gpio_use_sel2[49:48, 39:32] bits[17:16, 7: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 function. 0 = signal used as native function. 1 = signal used as a gpio. after a full reset (rsmrst#), all multiplexe d signals in the resume and core wells are configured as a gpio rather than as their native function. after just a pltrst#, the gpio in the core well are configured as gpio. notes: 1. the following bits are not implemente d because there is no corresponding gpio: 31:18, 15:8. 2. the following bits are not implemente d because they are determined by the configuration: 0 www.datasheet.co.kr datasheet pdf - http://www..net/
lpc interface bridge registers (d31:f0) 448 datasheet 13.10.7 gp_io_sel2?gpio input/output select 2 register[63:32] offset address: gpiobase +34h attribute: r/w default value: 000000f0h size: 32-bit lockable: no power well: cpu i/o for 17, core for 16, 7:0 13.10.8 gp_lvl2?gpio level for input or output 2 register[63:32] offset address: gpiobase +38h attribute: r/w default value: 00030003h size: 32-bit lockable: no power well: cpu i/o for 17, core for 16:0 bit description 31:18, 15:8 always 0. no corresponding gpio. 17:16, 7:0 gp_io_sel2[49:48, 39:32] ? r/w. 0 = gpio signal is programmed as an output. 1 = corresponding gpio signal (if enab led in the gpio_use_sel2 register) is programmed as an input. bit description 31:18, 15:8 reserved . read-only 0 17:16, 7:0 gp_lvl[49:48, 39:32] ? r/w. if gpio[n] is programmed to be an output (via the corresponding bit in the gp_io_sel register), 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 programmed as an input, then the corresponding 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_se l[n] is 0), writes to these bits have no effect. the value reported in this register is undefined when programmed as native mode. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 449 uhci controllers registers 14 uhci controllers registers 14.1 pci configuration registers (usb?d29:f0/f1/f2/f3) note: register address locations that are not shown in table 14-132 and should be treated as reserved (see section 9.2 for details). table 14-132.uhci controller pci regist er address map (usb?d29:f0/f1/f2/f3) offset mnemonic register name function 0 default function 1 default function 2 default function 3 default type 00?01h vid vendor identification 8086h 8086h 8086h 8086h ro 02?03h did device identification see register description see register description see register description see register description ro 04?05h pcicmd pci command 0000h 0000h 0000h 0000h r/w, ro 06?07h pcists pci status 0280h 0280h 0280h 0280h r/wc, ro 08h rid revision identification see register description see register description see register description see register description ro 09h pi programming interface 00h 00h 00h 00h ro 0ah scc sub class code 03h 03h 03h 03h ro 0bh bcc base class code 0ch 0ch 0ch 0ch ro 0dh mlt master latency timer 00h 00h 00h 00h ro 0eh headtyp header type 80h 00h 00h 00h ro 20?23h base base address 00000001h 00000001h 00000001h 00000001h r/w, ro 2c?2dh svid subsystem vendor identification 0000h 0000h 0000h 0000h r/wo 2e?2fh sid subsystem identification 0000h 0000h 0000h 0000h r/wo 3ch int_ln interrupt line 00h 00h 00h 00h r/w 3dh int_pn interrupt pin see register description. see register description. see register description. see register description. ro 60h usb_relnum serial bus release number 10h 10h 10h 10h ro c0?c1h usb_legkey usb legacy keyboard/mouse control 2000h 2000h 2000h 2000h r/w, ro r/wc c4h usb_res usb resume enable 00h 00h 00h 00h r/w c8h cwp core well policy 00h 00h 00h 00h r/w www.datasheet.co.kr datasheet pdf - http://www..net/
uhci controllers registers 450 datasheet 14.1.1 vid?vendor identi fication register (usb?d29:f0/f1/f2/f3) address offset: 00h ? 01h attribute: ro default value: 8086hsize:16 bits 14.1.2 did?device identi fication register (usb?d29:f0/f1/f2/f3) address offset: 02h ? 03hattribute:ro default value: uhci #1 = see bit descriptionsize:16 bits uhci #2 = see bit description uhci #3 = see bit description uhci #4 = see bit description 14.1.3 pcicmd?pci command re gister (usb?d29:f0/f1/f2/ f3) address offset: 04h ? 05hattribute:r/w, ro default value: 0000hsize:16 bits bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel bit description 15:0 device id ? ro. this is a 16-bit value assigned to the chipset usb universal host controllers. bit description 15:11 reserved 10 interrupt disable ? r/w. 0 = enable. the function is able to generate its interrupt to the interrupt controller. 1 = disable. the function is not ca pable of generating interrupts. note: the corresponding interrupt status bit is not affected by th e interrupt enable. 9 fast back to back enable (fbe) ? ro. hardwired to 0. 8 serr# enable ? ro. reserved as 0. 7 wait cycle control (wcc) ? ro. hardwired to 0. 6 parity error response (per) ? ro. hardwired to 0. 5 vga palette snoop (vps) ? ro. hardwired to 0. 4 postable memory wr ite enable (pmwe) ? ro. hardwired to 0. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 451 uhci controllers registers 14.1.4 pcists?pci status register (usb?d29:f0/f1/f2/f3) address offset: 06h ? 07hattribute:r/wc, ro default value: 0280hsize: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. 3 special cycle enable (sce) ? ro. hardwired to 0. 2 bus master enable (bme) ? r/w. 0 = disable 1 = enable. chipset can act as a mast er on the pci bus for usb transfers. 1 memory space enable (mse) ? ro. hardwired to 0. 0 i/o space enable (iose) ? r/w. this bit controls acce ss to the i/o space registers. 0 = disable 1 = enable accesses to the usb i/o registers. the base address register for usb should be programmed before this bit is set. bit description bit description 15 detected parity error (dpe) ? r/wc. 0 = no parity error detected. 1 = set when a data parity error data parity error is detected on writes to the uhci register space or on read completion s returned to the host controller. 14 reserved as 0b. read only. 13 received master abort (rma) ? r/wc. 0 = no master abort generated by usb. 1 = usb, as a master, gene rated a master abort. 12 reserved . always read as 0. 11 signaled target abort (sta) ? r/wc. 0 = chipset did not terminat e transaction for usb function with a target abort. 1 = usb function is targeted with a transa ction that the chipset terminates with a target abort. 10:9 devsel# timing status (dev_sts) ? ro. this 2-bit field defines the timing for devsel# assertion. these read only bits indicate the ch ipset's devsel# timing when performing a positive decode . chipset generates devsel# with medium timing for usb. 8 data parity error detected (dped) ? ro. hardwired to 0. 7 fast back to back capable (fb2bc) ? ro. hardwired to 1. 6 user definable features (udf) ? ro. hardwired to 0. 5 66 mhz capable ? ro. hardwired to 0. www.datasheet.co.kr datasheet pdf - http://www..net/
uhci controllers registers 452 datasheet 14.1.5 rid?revision iden tification register (usb?d29:f0/f1/f2/f3) offset address: 08h attribute: ro default value: see bit description size: 8 bits 14.1.6 pi?programming interface register (usb?d29:f0/f1/f2/f3) address offset: 09hattribute:ro default value: 00hsize:8 bits 14.1.7 scc?sub class code register (usb?d29:f0/f1/f2/f3) address offset: 0ahattribute:ro default value: 03hsize:8 bits 4 capabilities list ? ro . hardwired to 0. 3 interrupt status ? ro. this bit reflects the state of this function?s interrupt at the input of the enable/disable logic. 0 = interrupt is de-asserted. 1 = interrupt is asserted. the value reported in this bit is independen t of the value in the interrupt enable bit. 2:0 reserved bit description bit description 7:0 revision id ? ro. bit description 7:0 programming interface ? ro. 00h = no specific register level programming interface defined. bit description 7:0 sub class code (scc) ? ro. 03h = usb host controller. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 453 uhci controllers registers 14.1.8 bcc?base clas s code register (usb?d29:f0/f1/f2/f3) address offset: 0bhattribute:ro default value: 0chsize:8 bits 14.1.9 mlt?master latency timer register (usb?d29:f0/f1/f2/f3) address offset: 0dh attribute: ro default value: 00h size: 8 bits 14.1.10 headtyp?header type register (usb?d29:f0/f1/f2/f3) address offset: 0ehattribute:ro default value: fn 0: 80hsize:8 bits fn 1: 00h fn 2: 00h fn 3: 00h for functions 1, 2, and 3, this register is hardwired to 00h. for function 0, bit 7 is determined by the values in the usb function disable bits (11:8 of the function disable register chipset config registers:offset 3418h). bit description 7:0 base class code (bcc) ? ro. 0ch = serial bus controller. bit description 7:0 master latency timer (mlt) ? ro. the usb controller is implemented internal to the chipset and not arbitrated as a pci device . therefore the device does not require a master latency timer. bit description 7 multi-function device ? ro. 0 = single-func tion device. 1 = multi-function device. since the upper functions in this de vice can be indivi dually hidden, this bit is based on the function- disable bits in chipset config space: offset 3418h as follows: d29:f7_disa ble (bit 15) d29:f3_disa ble (bit 11) d29:f2_disa ble (bit10) d29:f1_disa ble (bit 9) multi-function device (this bit) 0b x x x 1 x0bx x 1 xx0bx 1 xxx0b 1 111 1 0 www.datasheet.co.kr datasheet pdf - http://www..net/
uhci controllers registers 454 datasheet 14.1.11 base?base address register (usb?d29:f0/f1/f2/f3) address offset: 20h ? 23hattribute:r/w, ro default value: 00000001hsize:32 bits 14.1.12 svid ? subsys tem vendor identi fication register (usb?d29:f0/f1/f2/f3) address offset: 2ch?2dh attribute: r/wo default value: 0000h size: 16 bits lockable: no power well: core 14.1.13 sid ? subsystem id entification register (usb?d29:f0/f1/f2/f3) address offset: 2eh ? 2fh attribute: r/wo default value: 0000h size: 16 bits lockable: no power well: core 6:0 configuration layout. hardwire d to 00h, which indicates the st andard pci configuration layout. bit description bit description 31:16 reserved 15:5 base address ? r/w. bits [15:5] correspond to i/o address signals ad [15:5], respectively. this gives 32 bytes of relocatable i/o space. 4:1 reserved 0 resource type indicator (rte) ? ro. hardwire d to 1 to indicate that the base address field in this register maps to i/o space. bit description 15:0 subsystem vendor id (svid) ? r/wo. bios se ts the value in this register to identify the subsystem vendor id. the usb_svid register, in combination with the usb subsystem id register, enable s the operating system to distinguish each subsystem from the others. note: the software can write to this register only once per core well reset. writes should be done as a single, 16-bit cycle. bit description 15:0 subsystem id (sid) ? r/wo. bios sets the value in this register to identify the subsystem id. the sid register, in combination with the svid register (d29:f0/f1/f2/ f3:2c), enables the operating system to di stinguish each subsystem from other(s). the value read in this register is the same as what was written to the ide_sid register. note: the software can write to this register only once per core well reset. writes should be done as a single, 16-bit cycle. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 455 uhci controllers registers 14.1.14 int_ln?interrupt line register (usb?d29:f0/f1/f2/f3) address offset: 3chattribute:r/w default value: 00hsize:8 bits 14.1.15 int_pn?interrupt pin register (usb?d29:f0/f1/f2/f3) address offset: 3dhattribute:ro default value: function 0: see descriptionsize:8 bits function 1: see description function 2: see description function 3: see description 14.1.16 usb_relnum?serial bus release number register (usb?d29:f0/f1/f2/f3) address offset: 60hattribute:ro default value: 10hsize:8 bits bit description 7:0 interrupt line (int_ln) ? ro. this data is not used by the chipset. it is to communicate to software the interrupt line that the interrupt pin is connected to. bit description 7:0 interrupt line (int_ln) ? ro. this value tells the software which interrupt pin each usb host controller uses. the upper 4 bits are hardwired to 0000b; the lower 4 bits are determine by the interrupt pi n default values that are programmed in the memory- mapped configuration space as follows: function 0 d29ip.u0p (chipset config registers:offset 3108:bits 3:0) function 1 d29ip.u1p (chipset config registers:offset 3108:bits 7:4) function 2 d29ip.u2p (chipset config registers:offset 3108:bits 11:8) function 3 d29ip.u3p (chipset config registers:offset 3108:bits 15:12) note: this does not determine the mapping to the pirq pins. bit description 7:0 serial bus release number ? ro. 10h = usb controller supports the usb specification , release 1.0. www.datasheet.co.kr datasheet pdf - http://www..net/
uhci controllers registers 456 datasheet 14.1.17 usb_legkey?usb legacy keyboard/mouse control register (usb?d29:f0/f1/f2/f3) address offset: c0h ? c1hattribute:r/w, r/wc, ro default value: 2000hsize:16 bits this register is implemented separately in each of the usb uhci functions. however, the enable and status bits for the trapping logic are or?d and shared, respectively, since their functionality is not spec ific to any one host controller. bit description 15 smi caused by end of pa ss-through (smibyendps) ? r/wc. this bit indicates if the event occurred. note that even if the co rresponding enable bit is not set in bit 7, then this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 0 = software clears this bit by writing a 1 to the bit location in any of the controllers. 1 = event occurred 14 reserved 13 pci interrupt enable (usbpirqen) ? r/w. this bit is used to prevent the usb controller from generating an interrupt due to transactions on its ports. note that, when disabled, it will probably be configured to generate an smi using bi t 4 of this register. default to 1 for compatibilit y with older usb software. 0 = disable 1 = enable 12 smi caused by usb interrupt (smibyusb) ? ro. this bit indicates if an interrupt event occurred from this controller. the inte rrupt from the controller is taken before the enable in bit 13 has any effect to create this read-only bit. no te that even if the corresponding enable bit is not set in bit 4, this bit may still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 0 = software should clear the interrupts via th e usb controllers. writing a 1 to this bit will have no effect. 1 = event occurred. 11 smi caused by port 64 write (trapby64w) ? r/wc. this bit indicates if the event occurred. note that even if th e corresponding enable bit is not set in bit 3, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. note that the a20gate pass-through logic allows specific port 64h writes to complete without setting this bit. 0 = software clears this bit by writing a 1 to the bit location in any of the controllers. 1 = event occurred. 10 smi caused by port 64 read (trapby64r) ? r/wc. this bit indicates if the event occurred. note that even if th e corresponding enable bit is not set in bit 2, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 0 = software clears this bit by writing a 1 to the bit location in any of the controllers. 1 = event occurred. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 457 uhci controllers registers 9 smi caused by port 60 write (trapby60w) ? r/wc. this bit indicates if the event occurred. note that even if the corresponding en able bit is not set in bit 1, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. note that the a20gate pass-through logic allows specific port 64h writes to complete without setting this bit. 0 = software clears this bit by writing a 1 to the bit location in any of the controllers. 1 = event occurred. 8 smi caused by port 60 read (trapby60r) ? r/wc. this bit indicates if the event occurred. note that even if the corresponding enable bit is not set in the bit 0, then this bit will still be active. it is up to the sm m code to use the enable bit to determine the exact cause of the smi#. 0 = software clears this bit by writing a 1 to the bit location in any of the controllers. 1 = event occurred. 7 smi at end of pass-through enable (smiatendps) ? r/w. this bit enables smi at the end of a pass-through. this can occur if an smi is generated in the middle of a pass-through, and needs to be serviced later. 0 = disable 1 = enable 6 pass through state (pstate) ? ro. 0 = if software needs to reset this bit, it should set bit 5 in all of the host controllers to 0. 1 = indicates that the state machine is in the middle of an a20gate pass-through sequence. 5 a20gate pass-through enable (a20passen) ? r/w. 0 = disable. 1 = enable. allows a20gate sequence pass-through function. a specific cycle sequence involving writes to port 60h and 64h does no t result in the setting of the smi status bits. 4 smi on usb irq enable (usbsmien) ? r/w. 0 = disable 1 = enable. usb interrupt will cause an smi event. 3 smi on port 64 writes enable (64wen) ? r/w. 0 = disable 1 = enable. a 1 in bit 11 will cause an smi event. 2 smi on port 64 reads enable (64ren) ? r/w. 0 = disable 1 = enable. a 1 in bit 10 will cause an smi event. 1 smi on port 60 writes enable (60wen) ? r/w. 0 = disable 1 = enable. a 1 in bit 9 will cause an smi event. 0 smi on port 60 reads enable (60ren) ? r/w. 0 = disable 1 = enable. a 1 in bit 8 will cause an smi event. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
uhci controllers registers 458 datasheet 14.1.18 usb_res?usb resu me enable register (usb?d29:f0/f1/f2/f3) address offset: c4hattribute:r/w default value: 00hsize:8 bits 14.1.19 cwp?core well policy register (usb?d29:f0/f1/f2/f3) address offset: c8h attribute: r/w default value: 00h size: 8 bits 14.2 usb i/o registers some of the read/write register bits that deal with changing the state of the usb hub ports function such that on read back they reflect the current state of the port, and not necessarily the state of the last write to the register. this allows the software to poll the state of the port and wait until it is in the proper state before proceeding. a host controller reset, global reset, or port rese t will immediately terminate a transfer on the affected ports and disable the port. this affects the usbcmd register, bit 4 and the portsc registers, bits [12,6,2]. see individual bit descriptions for more detail. bit description 7:2 reserved 1 port1en ? r/w. enable port 1 of the usb controller to respond to wakeup events. 0 = the usb controller will not look at this port for a wakeup event. 1 = the usb controller will monitor this port for remote wakeup and connect/ disconnect events. 0 port0en ? r/w. enable port 0 of the usb controller to respond to wakeup events. 0 = the usb controller will not look at this port for a wakeup event. 1 = the usb controller will monitor this port for remote wakeup and connect/ disconnect events. bit description 7:1 reserved 0 static bus master status policy enable (sbmspe) ? r/w. 0 = the uhci host controller dynamically sets the bus master status bit (power management 1 status register,[pmbase +00h], bit 4) based on the memory accesses that are scheduled. for netbook only, the default setting provides a more accurate indication of snoopable memory ac cesses in order to help with software- invoked entry to c3 and c4 power states. 1 = the uhci host controller statically fo rces the bus master status bit in power management space to 1 whenever the hchalted bit (usb status register, base+02h, bit 5) is cleared. note: the pci power management 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). www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 459 uhci controllers registers notes: 1. these registers are word writable only. byte writes to these registers have unpredictable effects. 14.2.1 usbcmd?usb command register i/o offset: base + (00h ? 01h)attribute:r/w default value: 0000hsize:16 bits the command register indicates the command to be executed by the serial bus host controller. writing to the register causes a command to be executed. the table following the bit description provides additi onal information on the operation of the run/stop and debug bits. table 14-133.usb i/o registers base + offset mnemonic register name default type 00?01h usbcmd usb command 0000h r/w 02?03h usbsts usb status 0020h r/wc 04?05h usbintr usb interrupt enable 0000h r/w 06?07h frnum frame number 0000h r/w (see note 1) 08?0bh frbaseadd frame list base address undefined r/w 0ch sofmod start of frame modify 40h r/w 0d?0fh ? reserved ?? 10?11h portsc0 port 0 status/control 0080h r/wc, ro, r/w (see note 1) 12?13h portsc1 port 1 status/control 0080h r/wc, ro, r/w (see note 1) bit description 15:7 reserved 8 loop back test mode ? r/w. 0 = disable loop back test mode. 1 = chipset is in loop back test mode. when both ports ar e connected together, a write to one port will be seen on the other port and the data wi ll be stored in i/o offset 18h. 7 max packet (maxp) ? r/w. this bit selects the maximum packet size that can be used for full speed bandwidth reclamation at the end of a frame. this value is used by the host controller to determine whether it should initiate another transaction based on the time remaining in the sof counter. use of reclamation packet s larger than the programmed size will cause a babble error if executed during the critical window at frame end. the babble error results in the o ffending endpoint being stalled. software is responsible for ensuring that any packet which could be executed under bandwidth reclamation be within this size limit. 0 = 32 bytes 1 = 64 bytes www.datasheet.co.kr datasheet pdf - http://www..net/
uhci controllers registers 460 datasheet 6 configure flag (cf) ? r/w. this bit has no effect on the hardware. it is provided only as a semaphore service for software. 0 = indicates that software has not co mpleted host controller configuration. 1 = hcd software sets this bit as the last action in its process of configuring the host controller. 5 software debug (swdbg) ? r/w. the swdbg bit must only be manipulated when the controller is in the stopped state. this can be determined by checking the hchalted bit in the usbsts register. 0 = normal mode. 1 = debug mode. in sw debug mode, the host controller clears th e run/stop bit after the completion of each usb transaction. the next transaction is executed when software sets the run/stop bit back to 1. 4 force global resume (fgr) ? r/w. 0 = software resets this bit to 0 after 20 ms has elapsed to stop sending the global resume signal. at that time all usb devices should be ready for bus activity. the 1 to 0 transition causes the port to send a low speed eop signal. this bit will remain a 1 until the eop has completed. 1 = host controller sends the global resume si gnal on the usb, and sets this bit to 1 when a resume event (connect, disconnect, or k-state) is detected while in global suspend mode. 3 enter global suspend mode (egsm) ? r/w. 0 = software resets this bit to 0 to come ou t of global suspend mode. software writes this bit to 0 at the same time that force global resume (bit 4) is written to 0 or after writing bit 4 to 0. 1 = host controller enters the global suspen d mode. no usb transactions occur during this time. the host controller is able to receive resume signals from usb and interrupt the system. software must ensure that the run/stop bit (bit 0) is cleared prior to setting this bit. 2 global reset (greset) ? r/w. 0 = this bit is reset by the software after a minimum of 10 ms has elapsed as specified in chapter 7 of the usb specification. 1 = global reset. the host controller sends the global reset signal on the usb and then resets all its logic, including the internal hub registers. the hu b registers are reset to their power on state. chip hardware re set has the same effect as global reset (bit 2), except that the host controller does not send the global reset on usb. 1 host controller reset (hcreset) ? r/w. the effects of hcrese t on hub registers are slightly different from chip hardware reset and global usb reset. the hcreset affects bits [8,3:0] of the po rt status and control regist er (portsc) of each port. hcreset resets the state machines of th e host controller including the connect/ disconnect state machine (one for each po rt). when the connect/disconnect state machine is reset, the output that signals connect/disconnect are negated to 0, effectively signaling a di sconnect, even if a device is at tached to the port. this virtual disconnect causes the port to be disabled. this disconnect and disabling of the port causes bit 1 (connect status change) and bit 3 (port enable/disable change) of the portsc (d29:f0/f1/f2/f3:base + 10h) to get se t. the disconnect also causes bit 8 of portsc to reset. about 64 bit times after hcreset goes to 0, the connect and low- speed detect will take place, and bits 0 and 8 of th e portsc will change accordingly. 0 = reset by the host controller when the reset process is complete. 1 = reset. when this bit is set, the host controll er module resets it s internal timers, counters, state machines, etc. to their initial value. any transaction currently in progress on usb is immediately terminated. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 461 uhci controllers registers when the usb host controller is in software debug mode (usbcmd register bit 5=1), the single stepping software debug operation is as follows: to enter software debug mode: 1. hcd puts host controller in stop state by setting the run/stop bit to 0. 2. hcd puts host controller in debug mode by setting the swdbg bit to 1. 3. hcd sets up the correct command list and start of frame value for starting point in the frame list single step loop. 4. hcd sets run/stop bit to 1. 0 run/stop (rs) ? r/w. when set to 1, the chipset proceeds with execution of the schedule. the chipset continues execution as long as this bit is set. when this bit is cleared, the chipset completes the current transaction on the usb and then halts. the hc halted bit in the status re gister indicates when the host controller has finished the transaction and has entered the stopped state. the host contro ller clears this bit when the following fatal errors occur: cons istency check failure, pci bus errors. 0 = stop 1 = run note: this bit should only be cleared if there are no active transaction descriptors in the executable schedule or software will reset the host controller prior to setting this bit again. table 14-134.run/stop, debug bit interact ion swdbg (bit 5), run/stop (bit 0) operation swdbg (bit 5) run/stop (bit 0) description 0 0 if executing a command, the host controller completes the command and then stops. the 1.0 ms frame counter is reset and command list execution resumes from start of frame using the frame list pointer selected by the current value in the frnum register. (while run/ stop=0, the frnum register (d29:f0/f1/f2/f3:base + 06h) can be reprogrammed). 0 1 execution of the command list resumes from start of frame using the frame list pointer selected by the current value in the frnum register. the host controller remains running until the run/stop bit is cleared (by software or hardware). 1 0 if executing a command, the host controller completes the command and then stops and the 1.0 ms fram e counter is froze n at its current value. all status are preserved. the host controller begins execution of the command list from where it le ft off when the run/stop bit is set. 1 1 execution of the command list resumes from where the previous execution stopped. the run/stop bit is set to 0 by the host controller when a td is being fetc hed. this causes the ho st controller to stop again after the execution of the td (single step). when the host controller has completed execution, the hc halted bit in the status register is set. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
uhci controllers registers 462 datasheet 5. host controller executes next active td, sets run/stop bit to 0, and stops. 6. hcd reads the usbcmd register to check if the single step execution is completed (hchalted=1). 7. hcd checks results of td execution. go to step 4 to execute next td or step 8 to end software debug mode. 8. hcd ends software debug mode by setting swdbg bit to 0. 9. hcd sets up normal command list and frame list table. 10. hcd sets run/stop bit to 1 to resume normal schedule execution. in software debug mode, when the run/stop bit is set, the host controller starts. when a valid td is found, the run/stop bi t is reset. when the td is finished, the hchalted bit in the usbsts register (bit 5) is set. the sw debug mode skips over inactive tds an d only halts after an active td has been executed. when the last active td in a frame has been executed, the host controller waits until the next sof is sent and then fetc hes the first td of the next frame before halting. this hchalted bit can also be used outside of software debug mode to indicate when the host controller has detected the run/stop bit and has completed the current transaction. outside of the software debug mode, setting the run/stop bit to 0 always resets the sof counter so that when the run/ stop bit is set the host controller starts over again from the frame list location poin ted to by the frame list index (see frnum register description) rather than continuing where it stopped. 14.2.2 usbsts?usb status register i/o offset: base + (02h ? 03h)attribute:r/wc default value: 0020hsize:16 bits this register indicates pending interrupts and various states of the host controller. the status resulting from a transaction on the serial bus is not indicated in this register. bit description 15:6 reserved 5 hchalted ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = the host controller has stopped executing as a result of the ru n/stop bit being set to 0, either by software or by the host controller hardware (debug mode or an internal error). default. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 463 uhci controllers registers 14.2.3 usbintr?usb inte rrupt enable register i/o offset: base + (04h ? 05h)attribute:r/w default value: 0000hsize:16 bits this register enables and disables report ing of the corresponding interrupt to the software. when a bit is set and the corresponding interrupt is active, an interrupt is generated to the host. fatal errors (host controller processor error, (d29:f0/f1/f2/ f3:base + 02h, bit 4, usbsts register) cannot be disabled by the host controller. interrupt sources that are disabled in this re gister still appear in the status register to allow the software to poll for events. 4 host controller process error ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = the host controller has detected a fatal e rror. this indicates that the host controller suffered a consistency check failure while processing a transfer descriptor. an example of a consistency check failure woul d be finding an invalid pid field while processing the packet header portion of the td. when this e rror occurs, the host controller clears the run/stop bit in the command register (d29:f0/f1/f2/ f3:base + 00h, bit 0) to prevent further schedule execution. a hardware interrupt is generated to the system. 3 host system error ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = a serious error occurred duri ng a host system access involving the host controller module. in a pci system, conditions that se t this bit to 1 include pci parity error, pci master abort, and pci target abort. wh en this error occurs, the host controller clears the run/stop bit in the command re gister to prevent further execution of the scheduled tds. a hardware inte rrupt is generated to the system. 2 resume detect (rsm_det) ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = the host controller received a ?resume? signal from a usb device. this is only valid if the host controller is in a global suspend state (command register, d29:f0/ f1/f2/f3:base + 00h, bit 3 = 1). 1 usb error interrupt ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = completion of a usb transaction resulted in an error condition (e.g., error counter underflow). if the td on which the erro r interrupt occurred al so had its ioc bit (d29:f0/f1/f2/f3:base + 04h, bit 2) set, both this bit and bit 0 are set. 0 usb interrupt (usbint) ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = the host controller sets this bit when the cause of an interrupt is a completion of a usb transaction whose transfer descriptor had its ioc bit set. also set when a short packet is detected (actual length field in td is less than maximum length field in td), and short packet detection is enabled in that td. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
uhci controllers registers 464 datasheet 14.2.4 frnum?frame number register i/o offset: base + (06 ? 07h)attribute:r/w (writes must be word writes) default value: 0000hsize:16 bits bits [10:0] of this register contain the current frame number that is included in the frame sof packet. this register reflects the count value of the internal frame number counter. bits [9:0] are used to select a particular entry in the frame list during scheduled execution. this register is updated at the end of each frame time. this register must be written as a word. by te writes are not supported. this register cannot be written unless the host controller is in the stopped state as indicated by the hchalted bit (d29:f0/f1/f2/f3:base + 02h, bit 5). a write to this register while the run/stop bit is set (d29:f0/f1/f2/f3:base + 00h, bit 0) is ignored. 14.2.5 frbaseadd?frame list base address register i/o offset: base + (08h ? 0bh)attribute:r/w default value: undefinedsize:32 bits this 32-bit register contains the beginnin g address of the frame list in the system memory. hcd loads this register prior to starting the schedule execution by the host controller. when written, only the upper 20 bits are used. the lower 12 bits are written bit description 15:5 reserved 4 scratchpad (sp) ? r/w. 3 short packet interrupt enable ? r/w. 0 = disabled. 1 = enabled. 2 interrupt on complete enable (ioc) ? r/w. 0 = disabled. 1 = enabled. 1 resume interrupt enable ? r/w. 0 = disabled. 1 = enabled. 0 timeout/crc interrupt enable ? r/w. 0 = disabled. 1 = enabled. bit description 15:11 reserved 10:0 frame list current index/frame number ? r/w. this field provides the frame number in the sof frame. the value in this register increments at the end of each time frame (approximately every 1 ms). in addition, bits [9:0] are used for the frame list current index and correspond to memory address signals [11:2]. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 465 uhci controllers registers as 0?s (4-kb alignment). the contents of th is register are combined with the frame number counter to enable the host contro ller to step through the frame list in sequence. the two least significant bits are always 00. this requires dword-alignment for all list entries. this configuration supports 1024 frame list entries. 14.2.6 sofmod?start of frame modify register i/o offset: base + (0ch)attribute:r/w default value: 40hsize:8 bits this 1-byte register is used to modify the va lue used in the generation of sof timing on the usb. only the 7 least significant bits are used. when a new value is written into these 7 bits, the sof timing of the next fr ame will be adjusted. this feature can be used to adjust out any offset from the clock source that generates the clock that drives the sof counter. this register can also be used to maintain real time synchronization with the rest of the system so that all devi ces have the same sense of real time. using this register, the frame length can be adju sted across the full range required by the usb specification. its initial programmed value is system dependent based on the accuracy of hardware usb clock and is initialized by system bios. it may be reprogrammed by usb sy stem software at any time. its value will take effect from the beginning of the next frame. this register is reset upon a host controller reset or global reset. software must maintain a copy of its value for reprogramming if necessary. bit description 31:12 base address ? r/w. these bits correspond to memory address signals [31:12], respectively. 11:0 reserved bit description 7 reserved 6:0 sof timing value ? r/w. guidelines for the modifica tion of frame time are contained in chapter 7 of the usb specification. the sof cycle time (number of sof counter clock periods to generate a sof frame length) is equal to 11936 + value in this field. the default value is decimal 64 which gives a sof cycle time of 12000. for a 12 mhz sof counter clock input, this produces a 1 ms frame period. the following table indicates what sof timing value to program into this field for a certain frame period. frame length (# 12 mhz clocks) (decimal) sof timing value (this register) (decimal) 11936 0 11937 1 ?? 11999 63 12000 64 12001 65 ?? 12062 126 12063 127 www.datasheet.co.kr datasheet pdf - http://www..net/
uhci controllers registers 466 datasheet 14.2.7 portsc[0,1]?port status and control register i/o offset: port 0/2/4/6: base + (10h ? 11h)attribute:r/wc, ro, port 1/3/5/7: base + (12h ? 13h)r/w (word writes only) default value: 0080hsize:16 bits note: for function 0, this applies to chipset usb po rts 0 and 1; for function 1, this applies to chipset usb ports 2 and 3; for function 2, this applies to chipset usb ports 4 and 5; and for function 3, this applie s to chipset usb ports 6 and 7. after a power-up reset, global reset, or host controller reset, the initial conditions of a port are: no device connected, port disabled, and the bus line status is 00 (single- ended 0). port reset and enable sequence when software wishes to reset a usb device it will assert the port reset bit in the port status and control register. the minimum reset signaling time is 10 ms and is enforced by software. to complete the reset sequence, software clears the port reset bit. the intel uhci controller must re-detect the port connect after reset signaling is complete before the controller will allow the port enable bit to de set by software. this time is approximately 5.3 us. software has several possible options to meet the timing requirement and a partial list is enumerated below: ? iterate a short wait, setting the port enable bit and reading it back to see if the enable bit is set. ? poll the connect status bit and wait for the hardware to recognize the connect prior to enabling the port. ? wait longer than the hardware detect time after clearing the port reset and prior to enabling the port. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 467 uhci controllers registers bit description 15:13 reserved ? ro. 12 suspend ? r/w . this bit should not be written to a 1 if global suspend is active (bit 3=1 in the usbcmd register). bit 2 and bit 12 of this register defi ne the hub states as follows: when in suspend state, downst ream propagation of data is blocked on this port, except for single-ended 0 resets (global reset and po rt reset). the blocking occurs at the end of the current transaction, if a transaction wa s in progress when this bit was written to 1. in the suspend state, the port is sensit ive to resume detectio n. note that the bit status does not change until the port is suspended and th at there may be a delay in suspending a port if there is a transa ction currently in pr ogress on the usb. 1 = port in suspend state. 0 = port not in suspend state. note: normally, if a transaction is in progress when this bit is set, the port will be suspended when the current transaction completes. however, in the case of a 11 overcurrent indicator ? r/wc. set by hardware. 0 = software clears this bit by writing a 1 to it. 1 = overcurrent pin has gone from in active to active on this port. 10 overcurrent active ? ro. this bit is set and cleared by hardware. 0 = indicates that the overcurre nt pin is inactive (high). 1 = indicates that the overcurrent pin is active (low). 9 port reset ? r/w . 0 = port is not in reset. 1 = port is in reset. when set, the port is disabled and sends the usb reset signaling. 8 low speed device attached (ls) ? ro . 0 = full speed device is attached. 1 = low speed device is attached to this port. 7 reserved ? ro. always read as 1. 6 resume detect (rsm_det) ? r/w. software sets this bit to a 1 to drive resume signaling. the host controller sets this bit to a 1 if a j-to-k transition is detected for at least 32 microseconds while the port is in the suspend state. the chipset will then reflect the k-state back onto the bus as long as the bit remains a 1, and the port is still in the suspend state (bit 12,2 are ?11?). writing a 0 (from 1) causes the port to send a low speed eop. this bit will remain a 1 until the eop has completed. 0 = no resume (k-state) detected/driven on port. 1 = resume detected /driven on port. 5:4 line status ? ro . these bits reflect the d+ (bit 4) an d d? (bit 5) signals lines? logical levels. these bits are used for fault detect an d recovery as well as for usb diagnostics. this field is updated at eof2 time (see chapter 11 of the usb specification). bits [12,2] hub state x,0 disable 0, 1 enable 1, 1 suspend www.datasheet.co.kr datasheet pdf - http://www..net/
uhci controllers registers 468 datasheet 3 port enable/disable change ? r/wc . for the root hub, this bit gets set only when a port is disabled due to disc onnect on that port or due to the appropriate conditions existing at the eof2 point (see chapter 11 of the usb specification). 0 = no change. software clears this bi t by writing a 1 to the bit location. 1 = port enabled/disabled status has changed. 2 port enabled/disabled (port_en) ? r/w . ports can be enabled by host software only. ports can be disabled by either a faul t condition (disconnect event or other fault condition) or by host software . note that the bit status does not change until the port state actually changes and that there may be a delay in disabling or enabling a port if there is a transaction currently in progress on the usb. 0 = disable 1 = enable 1 connect status change ? r/wc . this bit indicates that a change has occurred in the port?s current connect status (see bit 0). the hub device se ts this bit for any changes to the port device connect status, even if system software has not cleared a connect status change. if, for example, the insert ion status changes twice before system software has cleared th e changed condition, hub hardware will be setting? an already- set bit (i.e., the bit will remain set). however, the hub transfers the change bit only once when the host controller requests a da ta transfer to the status change endpoint. system software is re sponsible for determining state change history in such a case. 0 = no change. software clears th is bit by writing a 1 to it. 1 = change in current connect status. 0 current connect status ? ro . this value reflects the current state of the port, and may not correspond directly to the event th at caused the connect status change bit (bit 1) to be set. 0 = no device is present. 1 = device is present on port. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 469 sata controller registers (d31:f2) 15 sata controller registers (d31:f2) 15.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 15-135.sata controller pci register address map (sata?d31:f2) (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 02b0h r/wc, ro 08h rid revision identification see register description. ro 09h pi programming interface see register description. see register description 0ah scc sub class code see register description see register 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 abar ahci base address 00000000h see register 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 www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 470 datasheet note: the chipset sata controller is not arbitrated as a pci device; therefore, it does not need a master latency timer. 40h?41h ide_timp primary ide timing 0000h r/w 42h?43h ide_tims secondary ide timing 0000h r/w 44h sidetim slave ide timing 00h r/w 48h sdma_cnt synchronous dma control 00h r/w 4ah?4bh sdma_tim synchronous dma timing 0000h r/w 54h?57h ide_config ide i/o configuration 00000000h r/w 70h?71h pid pci power management capability id see register description ro 72h?73h pc pci power management capabilities 4002h ro 74h?75h pmcs pci power management control and status 0000h r/w, ro, r/wc 80h?81h msici message signaled interrupt capability id 7005h ro 82h?83h msimc message sign aled interrupt message control 0000h ro, r/w 84h?87h msima message sign aled 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 94h?97h sir sata initialization register 00000000h r/w a0h siri sata indexed registers index 00h r/w a4h strd sata indexed register data xxxxxxxxh r/w a8h?abh scap0 sata capability register 0 00100012h ro ach?afh scap1 sata capability register 1 00000048h ro 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 15-135.sata controller pci register address map (s ata?d31:f2) (sheet 2 of 2) offset mnemonic register name default type www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 471 sata controller registers (d31:f2) 15.1.1 vid?vendor identificati on register (sata?d31:f2) offset address: 00h ? 01h attribute: ro default value: 8086h size: 16 bit lockable: no power well: core 15.1.2 did?device identificati on register (sata?d31:f2) 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:f2) address offset: 04h ? 05h attribute: ro, r/w default value: 0000h size: 16 bits 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 chipset sata controller. note: the value of this field will change dependent upon the value of the map register. bit description 15:11 reserved 10 interrupt disable ? r/w. this disables pin-based intx# interrupts. this bit has no effect on msi operation. 0 = internal intx# messages are generated if there is an interrupt and msi is not enabled. 1 = internal 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. 6 parity error response (per) ? r/w. 0 = disabled. sata controller will not gene rate perr# when a data parity error is detected. 1 = enabled. sata controller will generate pe rr# 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. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 472 datasheet 15.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. 2 bus master enable (bme) ? r/w. this bit controls the chipset?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. 1 memory space enable (mse) ? r/w / ro. this bit contro ls access to the sata controller?s target memory space (for ahci). 0 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 primar y and secondary) as well as the bus mast er i/o registers. 1 = enable. note that the base address regist er for the bus master registers should be programmed before this bit is set. bit description 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 devi ce select time for the sata controller?s pci interface. 8 data parity error detected (dped) ? ro. for chipset, this bit can only be set on read completions received from sibu s where there is a parity error. 0 = data parity error not detected. 1 = sata controller, as a master, either detect s 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. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 473 sata controller registers (d31:f2) 15.1.5 rid?revision identificati on register (sata?d31:f2) offset address: 08h attribute: ro default value: see bit description size: 8 bits 15.1.6 pi?programmin g interface register (sata?d31:f2) 15.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 4 capabilities list (cap_list) ? ro. this bit indicates the presence of a capabilities list. the minimum requirement for the capabilities list must be pci power management for the sata controller. 3 interrupt status (ints) ? ro. reflects the st ate of intx# messages. 0 = interrupt is cleared (ind ependent of the state of in terrupt disable bit in the command register [offset 04h]). 1 = interrupt is to be asserted 2:0 reserved bit description bit description 7:0 revision id ? ro. bit description 7 this read-only bit is a 1 to indicate that the chipset supports bus master operation 6:4 reserved . will always return 0. 3 secondary mode native capable (snc) ? ro. 0 = secondary controller only supports legacy mode. 1 = secondary controller supports both legacy and native modes. the map.mv (d31:f2:offset 90:bits 1:0) must be program as 00b, and this bit is reports as a 1. 2 secondary mode native enable (sne) ? r/w / ro. determines the mode that the se condary channel is operating in. 0 = secondary controller operatin g in legacy (compatibility) mode 1 = secondary controller operating in native pci mode. when map.mv (d31:f2:offset 90:bit s 1:0) is any value other than 00 b, this bit is read-only (ro). software is responsible for cleari ng this bit before en tering combined mode. the map.mv must be program as 00b, and this bit is read/write (r/w). if this bit is set by software, then the pne bit (bit 0 of this register) must also be set by software. while in theory these bits can be progra mmed separately, such a configurat ion is not supported by hardware. 1 primary mode native capable (pnc) ? ro. 0 = primary controller only supports legacy mode. 1 = primary controller supports both legacy and native modes. the map.mv (d31:f2:offset 90:bits 1:0) must be program as 00b, and this bit is reports as a 1. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 474 datasheet 15.1.6.2 when sub class code regi ster (d31:f2:offset 0ah) = 06h address offset: 09h attribute: ro default value: 01h size: 8 bits 15.1.7 scc?sub class code register (sata?d31:f2) address offset: 0ah attribute: ro default value: see bit description size: 8 bits 15.1.8 bcc?base class code register (sata?d31:f2sata?d31:f2) address offset: 0bh attribute: ro default value: 01h size: 8 bits 0 primary mode native enable (pne) ? r/w / ro. determines the mode that the primary channel is operating in. 0 = primary controller operating in legacy (compa tibility) mode. 1 = primary controller operating in native pci mode. when map.mv (d31:f2:offset 90:bits 1:0) is any value other than 00b, this bit is read-only (ro). software is responsible for clearing this bit befo re entering combined mo de. the map.mv must be program as 00b, and this bit is read/write (r/w). if this bit is set by software, then the sne bit (bit 2 of this register) must also be set by software. while in theory these bits can be prog rammed separately, such a configurat ion is not supported by hardware. bit description bit description 7:0 interface (if) ? ro. indicates the sata controll er supports ahci, rev 1.0. bit description 7:0 sub class code (scc) this field specifies the sub-class code of the controller, per the table below: map.sms (d31:f2:offset 90h:bit 7:6) scc register value 00b 01h (ide controller) 01b 06h (ahci controller) bit description 7:0 base class code (bcc) ? ro. 01h = mass storage device www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 475 sata controller registers (d31:f2) 15.1.9 pmlt?primary master latency timer register (sata?d31:f2) address offset: 0dh attribute: ro default value: 00h size: 8 bits 15.1.10 pcmd_bar?primary co mmand block base address register (sata?d31:f2) 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 mo de for the primary controller?s command block. 15.1.11 pcnl_bar?primary contro l 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 mo de for the primary controller?s command block. bit description 7:0 master latency timer count (mltc) ? ro. 00h = hardwired. the sata controller is im plemented internally, and is not arbitrated as a pci device, so it does no t need a master latency timer. bit description 31:16 reserved 15:3 base address ? r/w. this field provides the ba se address of the i/o space (8 consecutive i/o locations). 2: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:2 base address ? r/w. this field provides the ba se 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. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 476 datasheet 15.1.12 scmd_bar?secondary co mmand block base address register (ide d31:f1) 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. 15.1.13 scnl_bar?secondary co ntrol block base address register (ide d31:f1) 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. 15.1.14 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 interf ace 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. bit description 31:16 reserved 15:3 base address ? r/w. this field provides the ba se address of the i/o space (8 consecutive i/o locations). 2: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:2 base address ? r/w. this field provides the ba se 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:4 base address ? r/w. this field provides the ba se address of the i/o space (16 consecutive i/o locations). 3:1 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 477 sata controller registers (d31:f2) 15.1.15 abar ? ahci ba se address register (sata?d31:f2) 15.1.15.1 non ahci capable (chipset feature supported components only) address offset: 24h?27h attribute: ro default value: 00000000h size: 32 bits 15.1.15.2 ahci capable address offset: 24h ? 27h attribute: r/w, ro default value: 00000000h size: 32 bits this register allocates space for the memory registers defined in section 15.3 . for non- achi capable chipset components, this register is reserved and read only, unless the scrae bit (offset 94h:bit 9) is set, in whic h case the register follows the definition given in section 15.1.15.2 . notes: 1. when the map.mv register is programmed for combined mode (00b), this register is ro. software is responsible for clearing th is bit before entering combined mode. 2. the abar register must be set to a value of 0001_0000h or greater. 15.1.16 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 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. bit description bit description 31:0 reserved bit description 31:10 base address (ba) ? r/w. base address of register memory space (aligned to 1 kb) 9:4 reserved 3 prefetchable (pf) ? ro. indicates that this range is not pre-fetchable 2:1 type (tp) ? ro. indicates that this rang e can be mapped anywhere in 32-bit address space. 0 resource type indicator (rte) ? ro. hardwired to 0 to indicate a request for register memory space. bit description 15:0 subsystem vendor id (svid) ? r/wo. value is written by bios. no hardware action taken on this value. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 478 datasheet 15.1.17 sid?subsystem identifica tion register (sata?d31:f2) address offset: 2eh ? 2fh attribute: r/wo default value: 0000h size: 16 bits lockable: no power well: core 15.1.18 cap?capabilities poin ter register (sata?d31:f2) address offset: 34h attribute: ro default value: 80h size: 8 bits 15.1.19 int_ln?interrupt line register (sata?d31:f2) address offset: 3ch attribute: r/w default value: 00h size: 8 bits 15.1.20 int_pn?interrupt pi n register (sata?d31:f2) address offset: 3dh attribute: ro default value: see register description size: 8 bits 15.1.21 ide_timp ? primary ide ti ming register (sata?d31:f2) address offset: primary: 40h ? 41h attribute: r/w secondary: 42h ? 43h default value: 0000h size: 16 bits this register controls the timings driven on the ide cable for pio and 8237 style dma transfers. it also controls operation of the buffer for pio transfers. bit description 15:0 subsystem id (sid) ? r/wo. value is written by bios. no hardware 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 map.mv register (dev 31:f2:90h, bits 1:0) in configuration space indicates that the sata function and pata functions are combined (values of 10b or 10b) or sub class code (cc.scc) (dev 31:f2:0ah) is configure as ide mode (value of 01). bit description 7:0 interrupt line ? r/w. this field is used to communicat e to software the interrupt line 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). www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 479 sata controller registers (d31:f2) note: this register is r/w to maintain software compatibility and enable parallel ata functionality when the pci functions are comb ined. these bits have no effect on sata operation unless otherwise noted. bit description 15 ide decode enable (ide) ? r/w. individually enable/disable the primary or secondary decode. 0 = disable. 1 = enables the chipset to decode the as sociated 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 deco de 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.17 - volume 1 for more on ata modes of operation. 14 drive 1 timing register enable (sitre) ? r/w. 0 = use bits 13:12, 9:8 for both drive 0 and drive 1. 1 = use bits 13:12, 9:8 for drive 0, and us e the slave ide timing register for drive 1 13:12 iordy sample point (isp) ? r/w. the setting of these bits determines the number of pci clocks between ide ior#/iow# asse rtion and the first iordy sample point. 00 = 5 clocks 01 = 4 clocks 10 = 3 clocks 11 = reserved 11:10 reserved 9:8 recovery time (rct) ? r/w. the setting of these bits determines the minimum number of pci clocks between the last iord y sample point and the ior#/iow# strobe of the next cycle. 00 = 4 clocks 01 = 3 clocks 10 = 2 clocks 11 = 1 clock 7 drive 1 dma timing enable (dte1) ? r/w. 0 = disable. 1 = enable the fast timing mode for dma transf ers only for this drive. pio transfers to the ide data port will ru n in compatible timing. 6 drive 1 prefetch/posting enable (ppe1) ? r/w. 0 = disable. 1 = enable prefetch and posting to the ide data port for this drive. 5 drive 1 iordy sample point enable (ie1) ? r/w. 0 = disable iordy sampling for this drive. 1 = enable iordy sampling for this drive. 4 drive 1 fast timing bank (time1) ? r/w. 0 = accesses to the data port will us e compatible timings for this drive. 1 = when this bit =1 and bit 14 = 0, accesses to the data port will use bits 13:12 for the iordy sample point, and bits 9:8 for the recovery time. when this bit = 1 and bit 14 = 1, accesses to the data port wi ll use the iordy samp le point and recover time specified in the slave ide timing register. 3 drive 0 dma timing enable (dte0) ? r/w. 0 = disable 1 = enable fast timing mode for dma transfers only for this drive. pio transfers to the ide data port will run in compatible timing. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 480 datasheet 15.1.22 ide_tims ? slave ide ti ming register (sata?d31:f2) address offset: 44h attribute: r/w default value: 00h size: 8 bits note: this register is r/w to maintain software compatibility and enable parallel ata functionality when the pci functions are comb ined. these bits have no effect on sata operation unless otherwise noted. 2 drive 0 prefetch/posting enable (ppe0) ? r/w. 0 = disable prefetch and posting to the ide data port for this drive. 1 = enable prefetch and posting to the ide data port for this drive. 1 drive 0 iordy sample point enable (ie0) ? r/w. 0 = disable iordy sampling is disabled for this drive. 1 = enable iordy sampling for this drive. 0 drive 0 fast timing bank (time0) ? r/w. 0 = accesses to the data port will us e compatible timings for this drive. 1 = accesses to the data port will use bits 13:12 for the iordy sample point, and bits 9:8 for the recovery time bit description bit description 7:6 secondary drive 1 iordy sample point (sisp1) ? r/w. this field determines the number of pci clocks between ide ior#/i ow# assertion and the first iordy sample point, if the access is to drive 1 data po rt and bit 14 of the ide timing register for secondary is set. 00 = 5 clocks 01 = 4 clocks 10 = 3 clocks 11 = reserved 5:4 secondary drive 1 recovery time (srct1) ? r/w. this field determines the minimum number of pci clocks between the last iordy sample point and the ior#/ iow# strobe of the next cycle, if the access is to drive 1 data port and bit 14 of the ide timing register for secondary is set. 00 = 4 clocks 01 = 3 clocks 10 = 2 clocks 11 = 1 clocks 3:2 primary drive 1 iordy sample point (pisp1) ? r/w. this field determines the number of pci clocks between ior#/iow# assertion and the first iordy sample point, if the access is to drive 1 data port and bi t 14 of the ide timing register for primary is set. 00 = 5 clocks 01 = 4 clocks 10 = 3 clocks 11 = reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 481 sata controller registers (d31:f2) 15.1.23 sdma_cnt?synchronous dma control register (sata?d31:f2) address offset: 48h attribute: r/w default value: 00h size: 8 bits note: this register is r/w to maintain software compatibility and enable parallel ata functionality when the pci functions are comb ined. these bits have no effect on sata operation unless otherwise noted. 15.1.24 sdma_tim?synchronous dma timing register (sata?d31:f2) address offset: 4ah ? 4bh attribute: r/w default value: 0000h size: 16 bits note: this register is r/w to maintain software compatibility and enable parallel ata functionality when the pci functions are comb ined. these bits have no effect on sata operation, unless otherwise noted. 1:0 primary drive 1 recovery time (prct1) ? r/w. this field determines the minimum number of pci clocks between the last iordy sample point and the ior#/ iow# strobe of the next cycle, if the access is to drive 1 data port and bit 14 of the ide timing register for primary is set. 00 = 4 clocks 01 = 3 clocks 10 = 2 clocks 11 = 1 clocks bit description bit description 7:4 reserved 3 secondary drive 1 synchronous dma mode enable (ssde1) ? r/w. 0 = disable (default) 1 = enable synchronous dma mode for secondary channel drive 1 2 secondary drive 0 synchronous dma mode enable (ssde0) ? r/w. 0 = disable (default) 1 = enable synchronous dma mode for secondary drive 0. 1 primary drive 1 synchronous dma mode enable (psde1) ? r/w. 0 = disable (default) 1 = enable synchronous dma mode for primary channel drive 1 0 primary drive 0 synchronous dma mode enable (psde0) ? r/w. 0 = disable (default) 1 = enable synchronous dma mode for primary channel drive 0 www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 482 datasheet bit description 15:14 reserved 13:12 secondary drive 1 cycle time (sct1) ? r/w. for ultra ata mode. the setting of these bits determines the minimum write strobe cycle time (ct). the dmardy#-to- stop (rp) time is also determin ed by the settin g of these bits. 11:10 reserved 9:8 secondary drive 0 cycle time (sct0) ? r/w. for ultra ata mode. the setting of these bits determines the minimum write strobe cycle time (ct). the dmardy#-to- stop (rp) time is also determin ed by the settin g of these bits. 7:6 reserved 5:4 primary drive 1 cycle time (pct1) ? r/w. for ultra ata mode, the setting of these bits determines the minimum write strobe cycle time (ct). the dmardy#-to-stop (rp) time is also determined by the setting of these bits. 3:2 reserved scb1 = 0 (33 mhz clk) scb1 = 1 (66 mhz clk) fast_scb1 = 1 (133 mhz clk) 00 = ct 4 clocks, rp 6 clocks 00 = reserved 00 = reserved 01 = ct 3 clocks, rp 5 clocks 01 = ct 3 clocks, rp 8 clocks 01 = ct 3 clocks, rp 16 clocks 10 = ct 2 clocks, rp 4 clocks 10 = ct 2 clocks, rp 8 clocks 10 = reserved 11 = reserved 11 = reserved 11 = reserved scb1 = 0 (33 mhz clk) scb1 = 1 (66 mhz clk) fast_scb1 = 1 (133 mhz clk) 00 = ct 4 clocks, rp 6 clocks 00 = reserved 00 = reserved 01 = ct 3 clocks, rp 5 clocks 01 = ct 3 clocks, rp 8 clocks 01 = ct 3 clocks, rp 16 clocks 10 = ct 2 clocks, rp 4 clocks 10 = ct 2 clocks, rp 8 clocks 10 = reserved 11 = reserved 11 = reserved 11 = reserved pcb1 = 0 (33 mhz clk) pcb1 = 1 (66 mhz clk) fast_pcb1 = 1 (133 mhz clk) 00 = ct 4 clocks, rp 6 clocks 00 = reserved 00 = reserved 01 = ct 3 clocks, rp 5 clocks 01 = ct 3 clocks, rp 8 clocks 01 = ct 3 clocks, rp 16 clocks 10 = ct 2 clocks, rp 4 clocks 10 = ct 2 clocks, rp 8 clocks 10 = reserved 11 = reserved 11 = reserved 11 = reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 483 sata controller registers (d31:f2) 15.1.25 ide_config?ide i/o configuration register (sata?d31:f2) address offset: 54h ? 57h attribute: r/w default value: 00000000h size: 32 bits note: this register is r/w to maintain software compatibility and enable parallel ata functionality when the pci functions are comb ined. these bits have no effect on sata operation, unless otherwise noted. 1:0 primary drive 0 cycle time (pct0) ? r/w. for ultra ata mode, the setting of these bits determines the minimum write strobe cycle time (ct). the dmardy#-to-stop (rp) time is also determined by the setting of these bits. bit description pcb1 = 0 (33 mhz clk) pcb1 = 1 (66 mhz clk) fast_pcb1 = 1 (133 mhz clk) 00 = ct 4 clocks, rp 6 clocks 00 = reserved 00 = reserved 01 = ct 3 clocks, rp 5 clocks 01 = ct 3 clocks, rp 8 clocks 01 = ct 3 clocks, rp 16 clocks 10 = ct 2 clocks, rp 4 clocks 10 = ct 2 clocks, rp 8 clocks 10 = reserved 11 = reserved 11 = reserved 11 = reserved bit description 31:24 reserved 23:20 scratchpad (sp2). chipset does not perform any actions on these bits. 19:18 sec_sig_mode ? r/w. these bits are used to co ntrol mode of the secondary ide signal pins for mobi le swap bay support. if the srs bit (chipset config registers:offset 3414h:bit 1) is 1, the reset states of bits 19:18 will be 01 (tri-state) instead of 00 (normal). 00 = normal (enabled) 01 = tri-state (disabled) 10 = drive low (disabled) 11 = reserved 17:16 prim_sig_mode ? r/w. these bits are used to control mode of the primary ide signal pins for mobi le swap bay support. if the prs bit (chipset config registers:offset 3414h:bit 1) is 1, the reset states of bits 17:16 will be 01 (tri-state) instead of 00 (normal). 00 = normal (enabled) 01 = tri-state (disabled) 10 = drive low (disabled) 11 = reserved www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 484 datasheet 15 fast secondary drive 1 base clock (fast_scb1) ? r/w. this bit is used in conjunction with the sct1 bits (d31:f2:4ah, bits 13:12) to enable/disable ultra ata/ 100 timings for the secondary slave drive. 0 = disable ultra ata/100 timing for the secondary slave drive. 1 = enable ultra ata/100 timing for the seco ndary slave drive (overrides bit 3 in this register). 14 fast secondary drive 0 base clock (fast_scb0) ? r/w. this bit is used in conjunction with the sct0 bits (d31:f2:4ah, bits 9:8) to enable/disable ultra ata/100 timings for the secondary master drive. 0 = disable ultra ata/100 timing for the secondary master drive. 1 = enable ultra ata/100 timing for the secondary master drive (overrides bit 2 in this register). 13 fast primary drive 1 base clock (fast_pcb1) ? r/w. this bit is used in conjunction with the pct1 bits (d31:f2:4ah, bits 5:4) to enable/disable ultra ata/100 timings for the primary slave drive. 0 = disable ultra ata/100 timing for the primary slave drive. 1 = enable ultra ata/100 timing for the prim ary slave drive (overrides bit 1 in this register). 12 fast primary drive 0 base clock (fast_pcb0) ? r/w. this bit is used in conjunction with the pct0 bits (d31:f2:4ah, bits 1:0) to enable/disable ultra ata/100 timings for the primary master drive. 0 = disable ultra ata/100 timing for the primary master drive. 1 = enable ultra ata/100 timing for the prim ary master drive (overrides bit 0 in this register). 11:8 reserved 7:4 scratchpad (sp1). chipset does no t perform any action on these bits. 3 secondary drive 1 base clock (scb1) ? r/w. 0 = 33 mhz base clock for ultra ata timings. 1 = 66 mhz base clock for ultra ata timings 2 secondary drive 0 base clock (scbo) ? r/w. 0 = 33 mhz base clock for ultra ata timings. 1 = 66 mhz base clock for ultra ata timings 1 primary drive 1 base clock (pcb1) ? r/w. 0 = 33 mhz base clock for ultra ata timings. 1 = 66 mhz base clock for ultra ata timings 0 primary drive 0 base clock (pcb0) ? r/w. 0 = 33 mhz base clock for ultra ata timings. 1 = 66 mhz base clock for ultra ata timings bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 485 sata controller registers (d31:f2) 15.1.26 pid?pci power management capability identification register (sata?d31:f2) address offset: 70h ? 71h attribute: ro default value: xx01h size: 16 bits 15.1.27 pc?pci power manageme nt capabilities register (sata?d31:f2) address offset: 72h ? 73h attribute: ro default value: 4002h size: 16 bits f 15.1.28 pmcs?pci power mana gement control and status register (sata?d31:f2) address offset: 74h ? 75h attribute: ro, r/w, r/wc default value: 0000h size: 16 bits bits description 15:8 next capability (next) ? ro. 00h ? if scc = 01h (ide mode). a8h ? for all other values of scc to po int to the next capability structure. this field is changed to 00h if the scrd bit (d31:f2;offset 94h bit-30) is set. 7:0 capability id (cid) ? ro. indicates that this pointer is a pci power management. bits description 15:11 pme support (pme_sup) ? ro. indicate s pme# can be generated from the d3 hot state in the sata host controller. 10 d2 support (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. pm e# from d3cold state is not supported, therefore this field is 000b. 5 device specific initialization (dsi) ? ro. hardwired to 0 to indicate that no device- specific initialization is required. 4 reserved 3 pme clock (pme_clk) ? ro. hardwired to 0 to indicate that pci clock is not required to generate pme#. 2:0 version (ver) ? ro. hardwired to 010 to indicates support for revision 1.1 of the pci power management specification. bits description 15 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. 14:9 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 486 datasheet 15.1.29 msici?message signal ed interrupt capability identification (sata?d31:f2) address offset: 80h ? 81h attribute: ro default value: 7005h size: 16 bits 15.1.30 msimc?message signaled interrupt message control (sata?d31:f2) address offset: 82h ? 83h attribute: r/w, ro default value: 0000h size: 16 bits 8 pme enable (pmee) ? r/w. 0 = disable. 1 = enable. sata controller generates pme# form d3 hot on a wake event. 7:2 reserved 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 = d3 hot state when in the d3 hot state, the controller?s configurat ion space is available, but the i/o and memory spaces are not. addi tionally, interrupts are blocked. bits description bits description 15:8 next pointer (next): indicates the next item in the list is the pci power management pointer. 7:0 capability id (cid): capabilities id indicates msi. bits description 15:8 reserved 7 64 bit address capable (c64): capable of generating a 32-bit message only. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 487 sata controller registers (d31:f2) 15.1.31 msima? message signaled interrupt message address (sata?d31:f2) address offset: 84h ? 87h attribute: ro, r/w default value: 00000000h size: 32 bits 6:4 multiple message enable (mme): when this field is cleared to ?000? (and msie is set), only a single msi message will be generated for all sata po rts, and bits [15:0] of the message vector will be driven from md[15:0]. when this field is set to ?001? (and msie is set), two msi messages will be generated. bit [15:1] of the message vectors will be driven from md[15:1] and bit [0] of the message vector will be driv en dependent on which sata port is the source of the interrupt: ?0? for port 0, and ?1? for ports 1, 2 and 3. when this field is set to ?010? (and msie is set), four message will be generated, one for each sata port. bits[15:2] of the message vectors will be driven from md[15:2], while bits[1:0] will be driven dependent on which sata port is the source of the interrupt: ?00? for port 0, ?01? for port 1, ?10? for port 2, and ?11? for port 3. values ?011b? to ?111b? are reserved. if this field is set to one of these reserved values, the results are undefined. 3:1 multiple message capable (mmc): indicates that the chipset sata controller supports four inte rrupt messages. 0 msi enable (msie): if set, msi is enabled and traditional interrupt pins are not used to generate interrupts. bits description mme value driven on msi memory write bits[15:2] bit[1] bit[0] 000 md[15:2] md[1] md[0] 001 md[15:2] md[1] ports 0: 0 ports 1,2,3: 1 010 md[15:2] port 0: 0 port 1: 0 port 2: 1 port 3: 1 port 0: 0 port 1: 1 port 2: 0 port 3: 1 011?111 reserved bits description 31:2 address (addr): lower 32 bits of the system specified message address, always dword aligned. 1:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 488 datasheet 15.1.32 msimd?message signaled interrupt message data (sata?d31:f2) address offset: 88h-89h attribute: r/w default value: 0000h size: 16 bits 15.1.33 map?address map re gister (sata?d31:f2) address offset: 90h attribute: r/w default value: 00h size: 8 bits 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 lowe r word of the data bu s 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[1:0]. see the description of the mme field. bits description 7:6 sata mode select (sms) ? r/w: software programs these bi ts to control the mode in which the sata hba should operate: 00b = ide mode 01b = ahci mode 10b = reserved 11b = reserved notes: 1. the sata function device id will chan ge based on the value of this register. 2. when combined mode is used (mv not eq ual to ?0?), only ide mode is allowed. ide mode can be selected when ahci are enabled 3. ahci mode may only be selected when mv = 0 4. programming these bits with values that are invalid (e.g, selecting raid when in combined mode) will result in inde terministic behavior by the hardware. 5:2 reserved . 1:0 map value (mv) : the value in the bits below indicate the address range the sata ports. bios must programs it to value 00, in order to set the port 0 as primary and port 1 as secondary. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 489 sata controller registers (d31:f2) 15.1.34 pcs?port control and st atus register (sata?d31:f2) address offset: 92h ? 93h attribute: r/w, r/wc, ro default value: 0000h size: 16 bits this register is only used in systems that do not support ahci. in ahci enabled systems, bits[3:0] must always be set bits[2,0] and the status of the port is controlled through ahci memory space. bits description 15:6 reserved . 5 port 1 present (p1p) ? ro. the status of this bit ma y change at any time. this bit is cleared when the port is disabled via p1 e. 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. 4 port 0 present (p0p) ? ro. the status of this bit ma y change at any time. this bit is cleared when the port is disabled via p0 e. 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. 3:2 reserved . 1 port 1 enabled (p1e) ? r/w. 0 = disabled. the port is in the ?off? state and cannot de tect any devices. 1 = enabled. the port can transition betwee n the on, partial, and slumber states and can detect devices. note: this bit takes precedence over p1cmd.sud (offset abar+198h:bit 1) 0 port 0 enabled (p0e) ? r/w. 0 = disabled. the port is in the ?off? state and cannot de tect any devices. 1 = enabled. the port can transition betwee n the on, partial, and slumber states and can detect devices. note: this bit takes precedence over p0cmd.sud (offset abar+118h:bit 1) www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 490 datasheet 15.1.35 sir?sata init ialization register address offset: 94h?97h attribute: r/w default value: 00000000h size: 32 bits . bit description 31:29 reserved 30 sata capability regi sters disable (scrd) . when this bit is set, the sata capabili ty registers are disabled. that is, sata capability registers 0 and 1 are both ch anged to read only with the value of 00000000h. also, the next capability bits in the pci power management capability information register (d31:f2;o ffset 70h bits 15:8) are chan ged to 00h, to indicate that the pci power management capability structure is the last pci capability structure in the sata controller. when th is bit is cleared, the sata capability registers are enabled. 29:28 reserved 27:24 sata initialization field 3 (sif3) ? r/w. bios shall always program this register to the value 0ch. all othe r values are reserved. 23 sata initialization field 2 (sif2) ? r/w. bios shall always program this register to the value 1b. all other values are reserved. 22:10 reserved 9 scr access enable (scrae) ? r/w. in no n-ahci mode, this bi t allows ac cess to the sata scr registers (sstatus, scontrol, and serror registers). 0 = the abar (dev31:f2:offset 24h) regist er and mse bit fiel d (dev31:f2:offset 04h:bit 1) remain as defined. 1 = the abar (dev31:f2:offset 24h) regist er and mse bit fiel d (dev31:f2:offset 04h:bit 1) are forced to be read/write. notes: 1. using this mode only allows access to ahci registers pxssts, pxsctl, pxserr. all other ahci space is reserved when this bit is set. 2. proper use of this bit requires: ? abar must be programmed to a valid ba r; mse must be set before software can access ahci space. ? the port implemented bit (d31:f2, of fset abar+0ch) for the corresponding port has to be set to allow access to the ahci port specific pxssts, pxsctl, and pxserr registers. 8:0 sata initialization field 1 (sif1) ? r/w. bios shall always program this register to the value 180h. all other values are reserved. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 491 sata controller registers (d31:f2) 15.1.36 siri?sata indexed registers index address offset: a0h attribute: r/w default value: 00h size: 8 bits . sata indexed registers 15.1.37 strd?sata indexed register data address offset: a4h attribute: r/w default value: xxxxxxxxh size: 32 bits 15.1.37.1 sttt1?sata inde xed registers index 00h (sata tx termination test register 1) address offset: index 00h?03h attribute: r/w default value: 00000000h size: 32 bits . bit description 7:2 index (idx) ? r/w. this field contains a 6-bit index pointer in to the sata indexed register space. data is written into and read from the sird register (d31:f2:a4h). 1:0 reserved index name 00h?03h sata tx termination test register 1 (sttt1) 04h?1bh reserved 1ch?1fh sata test mode enable register (stme) 20h?73h reserved 74h?77h sata tx termination test register 2 (sttt2) 78h?ffh reserved bit description 31:0 data (dta) ? r/w. this field contains a 32-bit data value that is written to the register pointed to by siri (d31:f2;a0h) or read from the register pointed to by siri. bit description 31:2 reserved . 1 port 1 tx termination test enable ? r/w: 0 = port 1 tx termination port testing is disabled. 1 = enables testing of port 1 tx termination. note: this bit only to be used for system board testing. 0 port 0 tx termination test enable ? r/w: 0 = port 0 tx termination port testing is disabled. 1 = enables testing of port 0 tx termination. note: this bit only to be used for system board testing. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 492 datasheet 15.1.37.2 stme?sata indexed registers index c1h (sata test mode enable register) address offset: index 1ch?1fh attribute: r/w default value: 00000000h size: 32 bits . 15.1.37.3 sttt2 ? sata indexed registers index 74h (sata tx termination test register 2) address offset: index 74h ? 77h attribute: r/w default value: 00000000h size: 32 bits . 15.1.38 scap0?sata capability register 0 (sata?d31:f2) address offset: a8h?abh attribute: ro default value: 00100012h size: 32 bits this register is set to 00000000h if the scrd bit (d31:f2;offset 94h bit-30) is set. bit description 31:19 reserved . 18 sata test mode enable bit ? r/w: 0 = entrance to chipset sata test modes are disabled. 1 = this bit allows entrance to chipset sata test modes when set. note: this bit only to be used for system board testing. 17:0 reserved . bit description 31:18 reserved . 17 port 3 tx termination test enable ? r/w: 0 = port 3 tx termination port testing is disabled. 1 = enables testing of port 3 tx termination. note: this bit only to be used for system board testing. 16 port 2 tx termination test enable ? r/w: 0 = port 2 tx termination port testing is disabled. 1 = enables testing of port 2 tx termination. note: this bit only to be used for system board testing. 15:0 reserved . bit description 31:24 reserved 23:20 major revision (majrev) ? ro: major revi sion number of the sata capability pointer implemented. 19:16 minor revision (minrev) ? ro: minor revision number of the sata capability pointer implemented. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 493 sata controller registers (d31:f2) 15.1.39 scap1?sata capability register 1 (sata?d31:f2) address offset: ach?afh attribute: ro default value: 00000048h size: 32 bits this register is set to 00000000h if the scrd bit (d31:f2;offset 94h bit-30) is set. 15:8 next capability pointer (next) ? ro: points to the next capability structure. 00h indicates this is the la st capability pointer. 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 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 regi sters are located 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/da ta pair (in dword granularity). the index and data i/o registers reside within the space defined by lbar in the sata 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 is not supported in chipset. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 494 datasheet 15.1.40 atc?apm trapping cont rol register (sata?d31:f2) address offset: c0h attribute: r/w default value: 00h size: 8 bits . 15.1.41 ats?apm trapping stat us register (sata?d31:f2) address offset: c4h attribute: r/wc default value: 00h size: 8 bits . 15.1.42 sp ? scratch pad register (sata?d31:f2) address offset: d0h attribute: r/w default value: 00000000h size: 32 bits . bit description 7:4 reserved 3 secondary 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 secondary interface must be device 1 for the trap and/or smi# to occur. 2 secondary master trap (smt) ? 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. 1 primary slave trap (pst) ? 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 1 for the trap and/or smi# to occur. 0 primary master trap (pmt) ? r/w. enables trapping and smi# assertion on legacy i/o accesses to 1f0h?1f7h and 3f6h. the acti ve device on the pr imary interface must be device 0 for the trap and/or smi# to occur. bit description 7:4 reserved 3 secondary slave trap (sst) ? r/wc. indicates that a trap occurred to the secondary slave device. 2 secondary master trap (spt) ? r/wc. indicates that a trap occurred to the secondary master device. 1 primary slave trap (pst) ? r/wc. indicates that a trap occurred to the primary slave device. 0 primary 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 software to use. no hardware action is taken on this register. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 495 sata controller registers (d31:f2) 15.1.43 bfcs?bist fis control/st atus register (sata?d31:f2) address offset: e0h ? e3h attribute: r/w, r/wc default value: 00000000h size: 32 bits bits description 31:12 reserved 11 bist fis successful (bfs) ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = bist fis transmitted by chipset received an r_ok completion status from the device. note: this bit must be cleared by softwa re prior to initiating a bist fis. 10 bist fis failed (bff) ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = bist fis transmitted by chipset receiv ed an r_err completion status from the device. note: this bit must be cleared by softwa re prior to initiating a bist fis. 9 port 1 bist fis initiate (p1bfi) ? r/w. when a rising edge is detected on this bit field, the chipset initiates a bist fis to the device on port 1, using the parameters specified in this register and the data spec ified 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 disa ble and re-e nable the port using the pxe bits at offset 92h prior to attempting additional bist fises or to return the chipset to a normal operational mo de. if the bist fis fails to complete, as indicated by the bff bit in the register, then software can clear then set the p1bfi bit to initiate another bist fis. this can be retried until the bist fis eventually completes successfully 8 port 0 bist fis initiate (p0bfi) ? r/w. when a rising edge is detected on this bit field, the chipset initiates a bist fis to the device on port 0, using the parameters specified in this register and the data spec ified 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 disa ble and re-e nable the port using the pxe bits at offset 92h prior to attempting additional bist fises or to return the chipset to a normal operational mo de. if the bist fis fails to complete, as indicated by the bff bit in the register, then software can clear then set the p0bfi bit to initiate another bist fis. this can be retried until the bist fis eventually completes successfully 7:2 bist fis parameters . these 6 bits form the contents of the upper 6 bits of the bist fis pattern definition in any bist fis transmit ted by the chipset. th is 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 en d retimed loopback bit 3: f ? far end analog loopback bit 2: p ? primitive bit for use with transmit mode 1:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 496 datasheet 15.1.44 bftd1?bist fis transmit data1 register (sata?d31:f2) address offset: e4h ? e7h attribute: r/w default value: 00000000h size: 32 bits 15.1.45 bftd2?bist fis transmit data2 register (sata?d31:f2) address offset: e8h ? ebh attribute: r/w default value: 00000000h size: 32 bits 15.2 bus master ide i/ o registers (d31:f2) the bus master ide function uses 16 bytes of i/o space, allocated via the bar register, located in device 31:function 2 configuration 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 va lue, and writes to reserved bits have no effect (but should not be attempted). these registers are only used for legacy operation. software must not use these registers when running ahci. the description of the i/o registers is shown in table 15-136 . 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 by the chipset. 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 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 chipset. 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 transmit 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 register (d31:f2:e0h). table 15-136.bus master id e 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 master ide status register primary 00h r/w, r/ wc, ro 03 ? reserved ?ro www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 497 sata controller registers (d31:f2) 15.2.1 bmic[p,s]?bus master id e command register (d31:f2) address offset: primary: bar + 00h attribute: r/w secondary: bar + 08h default value: 00h size: 8 bits 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 table 15-136.bus master ide i/o register address map bar+ offset mnemonic register default type bit description 7:4 reserved . returns 0. 3 read / write control (r/wc) ? r/w. this bit sets the di rection of the bus master transfer: this bit must not be changed wh en the bus master function is active. 0 = memory reads 1 = memory writes 2:1 reserved . returns 0. 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 the drive has not yet finished its data transfer (the interrupt bi t in the bus master id e 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. bus 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 this bit. note: this bit is intended to be cleared by software after the data transfer is completed, as indicated by either the bu s master ide active bit being cleared or the interrupt bit of the bus master ide status register fo r that ide channel being set, or both. hardware does not clea r this bit automatically. if this bit is cleared to 0 prior to the dma data transfer being initiated by the drive in a www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 498 datasheet 15.2.2 bmis[p,s]?bus master id e 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 7 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 controller execution of a prd that has its prd_int bit set. 6 drive 1 dma capable ? r/w. 0 = not capable. 1 = capable. set by device dependent code (b ios or device driver ) to indicate that drive 1 for this channel is capable of dm a transfers, and that the controller has been initialized for optimum performance. th e chipset does not use this bit. it is intended for systems that do no t attach bmide to the pci bus. 5 drive 0 dma capable ? r/w. 0 = not capable 1 = capable. set by device dependent code (b ios or device driver ) to indicate that drive 0 for this channel is capable of dm a transfers, and that the controller has been initialized for optimum performance. th e chipset does not use this bit. it is intended for systems that do no t attach bmide to the pci bus. 4:3 reserved . returns 0. 2 interrupt ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = set when a device fis is received with the ?i? bit set, provided that software has not disabled interrupts via the ien bit of the device control register (see chapter 5 of the serial ata specification , revision 1.0a). 1 error ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set when the controller encoun ters a target abort or master abort when transferring data on pci. 0 bus master ide active (act) ? ro. 0 = this bit is cleared by the chipset when th e last transfer for a region is performed, where eot for that region is set in the regi on descriptor. it is also cleared by the chipset when the start bus master bit (d 31:f2:bar+ 00h, bit 0) is cleared in the command register. when this bi t 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 chipset when the start bi t is written to the command register. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 499 sata controller registers (d31:f2) 15.2.3 bmid[p,s]?bus master id e descriptor table pointer register (d31:f2) address offset: primary: bar + 04h?07h attribute: r/w secondary: bar + 0ch ? 0fh default value: all bits undefined size: 32 bits 15.3 ahci registers (d31:f2) note: these registers are ahci-specific and available only on chipset components that support ahci (not on the 82801gb chipset) and when the chipset is properly configured. the serial ata status, control, and error registers are special exceptions and may be accessed on all chipset componen ts if properly configured (see section section 15.1.35 for details). the memory mapped registers within the sata controller exist in non-cacheable memory space. additionally, locked accesses ar e 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. the registers are divided 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. bit description 31:2 address of descri ptor table (addr) ? r/w. the bits in this field correspond to a[31:2]. the descriptor table must be dword-aligned. the descriptor table must not cross a 64-k boundary in memory. 1:0 reserved table 15-137.ahci register address map abar + offset mnemon ic 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?3ffh ? reserved www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 500 datasheet 15.3.1 ahci generic host control registers (d31:f2) 15.3.1.1 cap?host capab ilities register (d31:f2) address offset: abar + 00h?03h attribute: r/wo, ro default value: de22ff03h size: 32 bits all bits in this register that ar e r/wo are reset only by pltrst#. table 15-138.generic host co ntroller register address map abar + offset mnemonic register default type 00?03 cap host capabilities de22ff03h r/wo, ro 04?07 ghc global chipset control 00000000h r/w 08?0bh is interrupt status 00000000h r/wc, ro 0ch?0fh pi ports implemented 00000000h r/wo, ro 10h?13h vs ahci version 00010100h ro bit description 31 supports 64-bit addressing (s64a) ? ro. indicates that the sata controller can access 64-bit data structures. the 32-bit upper bits of the port dma descriptor, the prd base, and each prd entry are read/write. 30 supports command queue acceleration (scqa) ? ro. hardwired to 1 to indicate that the sata controller su pports sata command queuing via the dma setup fis. the chipset handles dma setup fises natively, and can handle auto- activate optimizatio n through that fis. 29 supports snotification register (ssntf): ? ro. the chipset sata controller does not support the snotification register. 28 supports interlock switch (sis) ? r/wo. indicates whether the sata 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. 27 supports staggered spin-up (sss) ? r/wo. indicates whether the sata controller supports staggered spin-up on its ports, for use in balancing power spikes. this value is loaded by plat form bios prior to os initialization. 0 = staggered spin-up not supported. 1 = staggered spin-up supported. 26 supports aggressive link power management (salp) ? r/wo. indicates the sata controller supports auto-generating link requ ests to the partial or slumber states when there are no commands to process. 0 = aggressive link power management not supported. 1 = aggressive link powe r management supported. 25 supports activity led (sal) ? ro. indicates that the sata controller supports a single output pin (sataled#) which indicates activity. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 501 sata controller registers (d31:f2) 15.3.1.2 ghc?global chipset control register (d31:f2) address offset: abar + 04h?07h attribute: r/w default value: 00000000h size: 32 bits 24 supports command list override (sclo) ? r/wo. when set to 1, indicates that the hba supports the pxcmd.clo bit and it 's associated func tion. when cleared to '0', the hba is not capable of cleari ng 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. indicates the maximum speed the sata 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.0 specification 18 supports port selector acceleration ? ro. port selectors not supported. 17 supports port multiplier (pms) ? r/wo. chipset does not support port multiplier. bios/sw shall write this bi t to ?0? during ahci initialization. 16 supports port multiplier fis based switching (pmfs) ? ro. reserved , as per the ahci revision 1.0 specification. note: port multiplier not supported by chipset. 15 pio multiple drq block (pmd) ? r/wo. th e sata controller supports pio multiple drq command block 14 slumber state capable (ssc) ? ro. the sata controller supports the slumber state. 13 partial state capable (psc) ? ro. the sa ta controller supports the partial state. 12:8 number of command slots (ncs) ? ro. ha rdwired to 1fh to indicate support for 32 slots. 7:5 reserved . returns 0. 4:0 number of ports (nps) ? ro. hardwired to 3h to indicate support for 4 ports. note that the number of ports indicate d in this field may be more than the number of ports indicated in the pi (abar + 0ch) register. bit description bit description 31 ahci enable (ae) ? r/w. when set, indicates that an ahci driver is loaded and the controller will be talked to via ahci mechan isms. this can be used by an chipset that supports both legacy mechanisms (such as sff-8038i) and ahci to know when the controller will not be talked to as legacy. when set, software will only talk to the ch ipset using ahci. the chipset will not have to allow command processing via both ahci and legacy mechanis ms. when cleared, software will only talk to the chipset using legacy mechanisms. software shall set this bit to 1 before acce ssing other ahci registers. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 502 datasheet 15.3.1.3 is?interrupt status register (d31:f2) address offset: abar + 08h ? 0bh attribute: r/wc, ro default value: 00000000h size: 32 bits this register indicates which of the ports with in the controller have an interrupt pending and require service. 15.3.1.4 pi?ports implemented register (d31:f2) address offset: abar + 0ch?0fh attribute: r/wo, ro default value: 00000000h size: 32 bits this register indicates which ports are exposed to the chipset. 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. 30:2 reserved . returns 0. 1 interrupt enable (ie) ? r/w. this global bit enables interrupts from the chipset. 0 = all interrupt sources from all ports are disabled. 1 = interrupts are allowed from the ahci controller. 0 hba reset (hr) ? r/w. resets chipset ahci controller. 0 = no effect 1 = causes an internal reset of the chipset ahci controller. all state machines that relate to data transfers and queuing return to an idle condition, and all ports are re-initialized via comreset. note: for further details, consul t section 12.3.3 of the serial ata advanced host controller interface specification. bit description bit description 31:2 reserved . returns 0. 1 interrupt pending status port[1] (ips[1]) ? r/wc . 0 = no interrupt pending. 1 = port 1has an interrupt pe nding. software can use this information to determine which ports require serv ice after an interrupt. 0 interrupt pending status port[0] (ips[0]) ? r/wc . 0 = no interrupt pending. 1 = port 0 has an interrupt pending. softwa re can use this information to determine which ports require serv ice after an interrupt. bit description 31:2 reserved . returns 0. 1 ports implemented port 1 (pi1) ? r/wo. 0 = the port is not implemented. 1 = the port is implemented. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 503 sata controller registers (d31:f2) 15.3.1.5 vs?ahci version (d31:f2) address offset: abar + 10h?13h attribute: ro default value: 00010100h size: 32 bits this register indicates the major and minor ve rsion of the ahci spec ification. 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 specification is 1.10 (00010100h). 15.3.2 port registers (d31:f2) 0 ports implemented port 0 (pi0) ? r/wo . 0 = the port is not implemented. 1 = the port is implemented. bit description 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 10. table 15-139.port [1:0] dma regist er address map (sheet 1 of 2) abar + offset mnemonic register 100h?103h p0clb port 0 command list base address 104h?107h p0clbu port 0 command li st base addres s 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?11ch 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?1ffh (netbook only) ? reserved registers are not available and software must not read from or write to registers. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 504 datasheet 15.3.2.1 pxclb?port [1:0] command list base address register (d31:f2) address offset: port 0: abar + 100h attribute: r/w, ro port 1: abar + 180h default value: undefined size: 32 bits 180h?183h p1clb port 1 command list base address 184h?187h p1clbu port 1 command li st 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 194h?197h p1ie port 1 interrupt enable 198h?19ch 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?2ffh ? reserved table 15-139.port [1:0] dma regist er address map (sheet 2 of 2) abar + offset mnemonic register bit description 31:10 command list base address (clb) ? r/w . indicates the 32-bit base 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 length. this address must be 1-kb aligned as indicated by bi ts 31:10 being read/write. note that these bits are not reset on a hba reset. 9:0 reserved ? ro www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 505 sata controller registers (d31:f2) 15.3.2.2 pxclbu?port [1:0] comma nd list base address upper 32-bits register (d31:f2) address offset: port 0: abar + 104h attribute: r/w port 1: abar + 184h default value: undefined size: 32 bits 15.3.2.3 pxfb?port [1:0] fis base address register (d31:f2) address offset: port 0: abar + 108h attribute: r/w, ro port 1: abar + 188h default value: undefined size: 32 bits 15.3.2.4 pxfbu?port [1:0] fis base address upper 32-bits register (d31:f2) address offset: port 0: abar + 10ch attribute: r/w port 1: abar + 18ch default value: undefined size: 32 bits 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 po rt. this base is us ed when fetching commands to execute. note that these bits are not reset on a hba reset. bit description 31:8 fis base address (fb) ? r/w . indicates the 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 hba reset. 7:0 reserved ? ro bit description 31:3 fis base address upper (fbu) ? r/w . indicates the upper 32-bi ts for the received fis base for this port. note that these bits are not reset on a hba reset. 2:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 506 datasheet 15.3.2.5 pxis?port [1:0] interrupt status register (d31:f2) address offset: port 0: abar + 110h attribute: r/wc, ro port 1: abar + 190h default value: 00000000h size: 32 bits bit description 31 cold port detect status (cpds) ? ro . cold presence not supported. 30 task file error status (tfes) ? r/wc. this bit is set whenever the status register is updated by the device and the e rror bit (pxtfd.bit 0) is set. 29 host bus fatal error status (hbfs) ? r/wc . indicates that the chipset encountered an error that it cannot recover from due to a ba d 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 chipset 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 chipset encountered an error on the sata interface wh ich caused the transfer to stop. 26 interface non-fatal error status (infs) ? r/wc. indicates that the chipset encountered an error on the sata interfa ce but was able to continue operation. 25 reserved 24 overflow status (ofs) ? r/wc . indicates that the chipset 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 chipset received a fis from a device whose port multiplier field did not match what was expected. note: port multiplier not supported by chipset. 22 phyrdy change status (prcs) ? ro. when set to one indicates the internal phyrdy signal changed state. this bi t reflects the state of pxserr .diag.n. unlike most of the other bits in the register, th is bit is ro and is only cl eared 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 desi red, otherwise the po wer management state transitions will appear as fals e insertion and removal events. 21:8 reserved 7 device interlock status (dis) ? r/wc. when set, indicates that 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 system s that support an inte rlock switch (cap.sis [abar+00:bit 28] set). for systems that do not suppo rt an interlock switch, th is bit will always be 0. 6 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 register, this bit is only cleare d when pxserr.diag.x is cleared. 0 = no change in curre nt connect status. 1 = change in current connect status. 5 descriptor processed (dps) ? r/wc . a prd with the i bit set has transferred all its data. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 507 sata controller registers (d31:f2) 15.3.2.6 pxie?port [1:0] interru pt enable register (d31:f2) address offset: port 0: abar + 114h attribute: r/w, ro port 1: abar + 194h default value: 00000000h size: 32 bits this register enables and disables the re porting of the corresponding interrupt to system software. when a bit is set (?1?) an d the corresponding interrupt condition is active, then an interrupt is generated. inte rrupt sources that are disabled (?0?) are still reflected in the status registers. 4 unknown fis interrupt (ufs) ? ro. when set to ?1? indicates that an unknown fis was received and has been copied into system memo ry. this bit is cleared to ?0? by software clearing the pxserr.diag.f bit to ?0?. note that this bit does no t directly reflect the pxserr.diag.f bit. pxserr.diag.f is se t immediately when an unknown fis is detected, whereas 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 to ?1? or the two bits may become out of sync. 3 set 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. 2 dma 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. 1 pio 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. 0 device to host register fis interrupt (dhrs) ? r/wc . a d2h register fis has been received with the i bit set, and has been copied into system memory. bit description bit description 31 cold presence detect enab le (cpde) ? ro. cold pres ence detect not supported. 30 task file error enable (tfee) ? r/w . when set, and ghc.ie and pxtfd.sts.err (due to a reception of the e rror register from a received fi s) are set, the chipset will generate an interrupt. 29 host bus fatal error enable (hbfe) ? r/w . when set, and ghc.ie and pxs.hbfs are set, the chipset will generate an interrupt. 28 host bus data error enable (hbde) ? r/w . when set, and ghc.ie and pxs.hbds are set, the chipset 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 chipset 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 chipset will generate an interrupt. 25 reserved - should be written as 0 24 overflow error enable (ofe) ? r/w . when set, and ghc.ie and pxs.ofs are set, the chipset will generate an interrupt. 23 incorrect port multiplier enable (ipme) ? r/w. when set, and ghc.ie and pxis.ipms are set, the chipset will generate an interrupt. note: should be written as 0. port mu ltiplier not supported by chipset. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 508 datasheet 15.3.2.7 pxcmd?port [1:0] command register (d31:f2) address offset: port 0: abar + 118h attribute: r/w, ro, r/wo port 1: abar + 198h default value: 0000w00wh size: 32 bits where w = 00?0b (for?, see bit description) 22 phyrdy change interrupt enable (prce) ? r/w. when set, and ghc.ie is set, and pxis.prcs is set, the chipset shall generate an interrupt. 21:8 reserved - should be written as 0 7 device interlock enable (die) ? r/w. when set, and pxis .dis is set, the chipset will generate an interrupt. for systems that do not suppo rt an interlock switch, this bit shall be a read-only 0. 6 port change interrupt enable (pce) ? r/w . when set, and ghc.ie and pxs.pcs are set, the chipset will generate an interrupt. 5 descriptor processed interrupt enable (dpe) ? r/w . when set, and ghc.ie and pxs.dps are set, the chipset will generate an interrupt 4 unknown fis interrupt enable (ufie) ? r/w . when set, and ghc. ie is set and an unknown fis is received, the chipset will generate this interrupt. 3 set device bits fis interrupt enable (sdbe) ? r/w . when set, and ghc.ie and pxs.sdbs are set, the chipset will generate an interrupt. 2 dma setup fis interrupt enable (dse) ? r/w . when set, and ghc.ie and pxs.dss are set, the chipset will generate an interrupt. 1 pio setup fis interrupt enable (pse) ? r/w . when set, and ghc.ie and pxs.pss are set, the chipset will generate an interrupt. 0 device to host re gister fis interrupt enable (dhre) ? r/w . when set, and ghc.ie and pxs.dhrs are set, the ch ipset will generate an interrupt. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 509 sata controller registers (d31:f2) bit description 31:28 interface communicati on control (icc) ? r/w . this is a four bit field wh ich can be used to control reset and power states of th e 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+1a4 h, port 2: abar+224h, port 3: abar+2a4h). when system software writes a non-reserved value other than no-op (0h), the chipset will perform the action and update this fi eld 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 chipset 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. 27 aggressive slumber / partial (asp) ? r/w . when set, and the alpe bit (bit 26) is set, the chipset will aggressively enter the slumber state when it clears the pxci regi ster and the pxsact register is cleared. when cleared, and the alpe bit is set, the chipset will aggressively enter the partial state when it clears the pxci register and the pxsact regi ster is cleared. 26 aggressive link power ma nagement enable (alpe) ? r/w . when set, the chipset will aggressively enter a lower link powe r state (partial or slumber) base d upon the setting of the asp bit (bit 27). 25 drive led on atapi enable (dlae) ? r/w . when set, the chipset will drive the led pin active for atapi commands (pxclb[chz.a] set) in addition to ata commands. when cleared, the chipset will only drive the led pin active for ata commands. see section 5.17.5 - vo lume 1 for details on the activity led. 24 hdevice is atapi (atapi) ? r/w. when set, the connected device is an atapi device. this bit is used by the chipset to control whether or not to generate the nettop led when commands are active. see section 5.17.5 - volume 1 for details on the activity led. 23:20 reserved value definition fh?7h reserved 6h slumber: this will ca use the chipset to request a transition of the interface to the slumber state. the sata devi ce may reject the request and the interface will remain in its current state 5h?3h reserved 2h partial: this will cause the chipset to request a transition of the interface to the partial state. the sata device may reject the request and the in terface will remain in its current state. 1h active: this will cause the chipset to request a transition of the interface into the active 0h no-op / idle: when software reads this value, it indicates the chipset is not in the process of changing the interface state or sending a device reset, and a new link command may be issued. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 510 datasheet 19 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 soft ware to enable such feat ures as aggressive power management, as disconnects can alwa ys be detected regardless of ph y state with an interlock switch. when this bit is set, it is expected that hpcp (bit 18) in this register is also set. the chipset takes no action on the state of this bit ? it is for system software only. for example, if this bit is cleared, and an interlock sw itch toggles, the chipset still treats it as a proper interlock switch event. note that these bits are not reset on a hba reset. 18 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 wh ich can be hot-plugged. sata by definition is hot-pluggabl e, but not all platforms are constructed to allow the device to be removed (it may be screwed into the chassis, fo r example). this bi t can be used by system software to indicate a feature such as ?eject device? to the end-user. the chipset 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 chipset still treats it as a proper hot-plug event. note that these bits are not reset on a hba reset. 17 port multiplier attached (pma) ? ro / r/w. when this bit is set, a port multiplier is attached to the chipset for this port. when cleared, a port multiplier is not attached to this port. this bit is ro 0 when cap.pms (offset abar +00h:bit 17) = 0 and r/w when cap.pms = 1. note: port multiplier not supported by chipset. 16 port multiplier fis based switching enable (pmf se) ? ro. the chipset does not support fis-based switching. note: port multiplier not supported by chipset. 15 controller running (cr) ? ro. when this bit is set, the dma en gines for a port are running. see section 5.2.2 of the serial ata ahci specification for details on when this bi t is set and cleared by the chipset. 14 fis receive running (fr) ? ro. when set, the fis receive dma engine for the port is running. see section 12.2.2 of the serial ata ahci specification for details on when this bi t is set and cleared by the chipset. 13 interlock switch state (iss) ? ro. for systems that support interlock switches (via cap.sis [abar+00h:bit 28]), if an interlock switch exists on 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 interl ock switches, or if an interlock swit ch is not attached to this port, this bit reports 0. 12:8 current command slot (ccs) ? ro . indicates the current command slot the chipset is processing. this field is valid when the st bit is set in this re gister, and is constantly u pdated by the chipset. this field can be updated as s oon as the chipset recognizes an active command slot, or at some point soon after when it begins processing the command. this field is used by software to determine the current command issue location of the chipset. in queued mode, software shall not us e this field, as its value does not represent the current command being executed. software shal l only use pxci and pxsact when running queued commands. 7:5 reserved bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 511 sata controller registers (d31:f2) 15.3.2.8 pxtfd?port [1:0] task file data register (d31:f2) address offset: port 0: abar + 120h attribute: ro port 1: abar + 1a0h default value: 0000007fh size: 32 bits this is a 32-bit register that copies specif ic fields 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 4 fis receive enable (fre) ? r/w. when set, the chipset 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 chipset, except for the first d2h (device- to-host) register fis after the initialization sequence. system software must not set this bit until pxfb (p xfbu) have been programmed with a valid pointer to the fis receive area, and if softwa re wishes to move the base, this bit must first be cleared, and software must wait for th e fr bit (bit 14) in this register to be cleared. 3 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.sts register. the hba sets this 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 se tting the pxcmd.st bit to '1' from a previous value of '0'. setting this bit to '1' at any other ti me is not supported and will result in indeterminate behavior 2 power on device (pod) ? ro . cold presence de tect not supported. defaults to 1. 1 spin-up device (sud) ? r/w / ro. this bit is r/w and defa ults to 0 for systems that support staggered 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 chipset starts a comreset initialization sequence to the device. 0 start (st) ? r/w . when set, the chipset may process the command list. when cleared, the chipset may not process the command list. whenever this bi t is changed from a 0 to a 1, the chipset starts processing the command list at entry 0. whenever this bit is changed from a 1 to a 0, the pxci register is cleared by the chipset upon the chipset putting the controller into an idle state. refer to section 10.3.1 of the serial ata ahci specif ication for important restri ctions on when st can be set to 1. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 512 datasheet 15.3.2.9 pxsig?port [1:0] signature register (d31:f2) address offset: port 0: abar + 124h attribute: ro port 1: abar + 1a4h 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 th at device. it is updated once after a reset sequence. 15.3.2.10 pxssts?port [1:0] serial ata status register (d31:f2) address offset: port 0: abar + 128h attribute: ro port 1: abar + 1a8h default value: 00000000h size: 32 bits this is a 32-bit register that conveys the current state of the interface and host. the chipset updates it continuously and asynchronously. when the chipset transmits a comreset to the device, this register is updated to its reset values. 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 interface 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 bit description 31:0 signature (sig) ? ro . contains the signature received from a device on the first d2h register fis. the bit order is as follows: bit field 31:24 lba high register 23:16 lba mid register 15:8 lba low register 7:0 sector count register bit description 31:12 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 513 sata controller registers (d31:f2) 15.3.2.11 pxsctl ? port [1:0] serial ata control register (d31:f2) address offset: port 0: abar + 12ch attribute: r/w, ro port 1: abar + 1ach 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 chip set or the interface. reads from the register return the last value written to it. 11:8 interface power management (ipm) ? ro. indicates the cu rrent interface state: all other values reserved. 7:4 current interface speed (spd) ? ro. indicates the negotiated interface communication speed. all other values reserved. chipset supports generation 1 communication rates (1.5 gb/sec) and gen 2 rates (3.0 gb/s). 3:0 device detection (det) ? ro . indicates the interface de vice detection and phy state: all other values reserved. bit description 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 de tected and phy communication not established 1h device presence detected but phy communication not established 3h device presence detected and phy communication established 4h phy in offline mode as a result of the interface being disabled or running in a bist loopback mode bit description 31:20 reserved 19:16 port multiplier port (pmp) ? ro. this field is not used by ahci note: port multiplier not supported by chipset. 15:12 select power management (spm) ? ro. this field is not used by ahci www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 514 datasheet 15.3.2.12 pxserr?port [1:0] serial ata error register (d31:f2) address offset: port 0: abar + 130h attribute: r/wc port 1: abar + 1b0h default value: 00000000h size: 32 bits 11:8 interface power management transitions allowed (ipm) ? r/w. indicates which power states the chipset is allowed to transition to: all other values reserved 7:4 speed allowed (spd) ? r/w. indicates the highest al lowable speed of the interface. this speed is limited by the ca p.iss (abar+00h:bit 23:20) field. all other values reserved chipset supports generation 1 communication rates (1.5 gb/sec) and gen 2 rates (3.0 gb/s). 3:0 device detection initialization (det) ? r/w . controls the chipset?s device detection and interface initialization. all other values reserved. when this field is written to a 1h, the chipset 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 change d to 1h or 4h when pxcmd.st is 0. changing this field while the chipset is running results in undefined behavior. bit description 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 detection or initialization action requested 1h perform interface communication initialization sequence to establish communication. this is fu nctionally 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 www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 515 sata controller registers (d31:f2) bit description 31:16 diagnostics (diag) ? r/wc . contains diagnostic error information for use by diagnostic software in validating correct operation or isolating failure modes: bits description 31:27 reserved 26 exchanged (x) : when set to one this bit indicates a co minit signal was received. this bit is reflected in the interru pt register pxis.pcs. 25 unrecognized fis type (f) : indicates that one or more fiss we re received by the transport layer with good crc, but had a type field that was not recognized. 24 transport state transition error (t) : indicates that an error has occurred in the transition from one state to another within th e transport layer since the last time this bit was cleared. 23 link sequence error (s) : indicates that one or more link state machine error conditions was encountered. the link layer state machine defi nes the conditions under which the link layer detects an erroneous transition. 22 handshake error (h) : indicates that one or more r_err handshake response was received in response to frame transmission. such errors may be th e result of a crc e rror 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 e rrors 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 si gnal was detected by the phy. 17 phy internal error (i) : indicates that the phy dete cted some internal error. 16 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 ch ipset, 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 px is.prcs interrupt status bit and an interrupt will be generated if enabled. software clears this bit by writing a 1 to it. 15:0 error (err) ? r/wc . the err field contains error information for use 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 controll er will stop the current transfer. bits description 15:12 reserved 11 interna l 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 at a protocol was detected. no te: the chipset does not set this bit for all protocol violations that may occur on the sata link. 9 persistent communication or data integrity error (c): a communicat ion error that was not recovered occurred that is expected to be persistent. persistent commun ications errors may arise from faulty interconnect with the de vice, from a device that has be en removed or has failed, or a number of other causes. 8 transient data integrity error (t) : a data integrity error occurred that was not recovered by the interface. 7:2 reserved 1 recovered communications error (m) : communications between the device and host was temporarily lost but was re-established. this can arise from a device temp orarily 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. 0 recovered data integrity error (i) : a data integrity error occurre d that was recovered by the interface through a retry operat ion or other recovery action. www.datasheet.co.kr datasheet pdf - http://www..net/
sata controller registers (d31:f2) 516 datasheet 15.3.2.13 pxsact?port [1:0] serial ata active (d31:f2) address offset: port 0: abar + 134h attribute: r/w port 1: abar + 1b4h default value: 00000000h size: 32 bits 15.3.2.14 pxci?port [1:0] command issue register (d31:f2) address offset: port 0: abar + 138h attribute: r/w port 1: abar + 1b8h default value: 00000000h size: 32 bits bit description 31:0 device status (ds) ? r/w . system software sets this bi t for sata queuing operations prior to setting the pxci.ci bit in the same co mmand slot entry. this field is cleared 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 re sult of a comreset or srst. bit description 31:0 commands issued (ci) ? r/w . this field is set by software to indicate to the chipset that a command has been buil t-in system memory for a command slot and may be sent to the device. when the chipset receives a fis which clears the bsy and drq bits for the command, it clears the corresponding bit in this register for that command slot. this field is also cleared when pxcmd. st (abar+118h/198h/218h/298h:bit 0) is cleared by software. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 517 ehci controller registers (d29:f7) 16 ehci controller registers (d29:f7) 16.1 usb ehci configuration registers (usb ehci?d29:f7) note: register address locations that are not shown in table 16-140 should be treated as reserved (see section 9.2 for details). note: all configuration registers in this section ar e in the core well and reset by a core well reset and the d3-to-d0 warm reset, except as noted. table 16-140.usb ehci pci register address map (usb ehci?d29:f7) (sheet 1 of 2) offset mnemonic register name default value 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 0290h r/w, ro 08h rid revision identification see register description ro 09h pi programming interface 20h ro 0ah scc sub class code 03h ro 0bh bcc base class code 0ch ro 0dh pmlt primary master latency timer 00h ro 10h?13h mem_base memory base address 00000000h r/w, ro 2ch?2dh svid usb ehci subsystem vendor identification xxxxh r/w (special) 2eh?2fh sid usb ehci subsystem identification xxxxh r/w (special) 34h cap_ptr capabilities pointer 50h ro 3ch int_ln interrupt line 00h r/w 3dh int_pn interrupt pin see register description ro 50h pwr_capid pci power management capability id 01h ro 51h nxt_ptr1 next item pointer #1 58h r/w (special) 52h?53h pwr_cap power management capabilities c9c2h r/w (special) www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 518 datasheet 16.1.1 vid?vendor identi fication register (usb ehci?d29:f7) offset address: 00h ? 01h attribute: ro default value: 8086h size: 16 bits 16.1.2 did?device identi fication register (usb ehci?d29:f7) offset address: 02h ? 03h attribute: ro default value: see bit description size: 16 bits 54h?55h pwr_cntl_sts power management control/status 0000h r/w, r/wc, ro 58h debug_capid debug port capability id 0ah ro 59h nxt_ptr2 next item pointer #2 00h ro 5ah?5bh debug_base debug port base offset 20a0h ro 60h usb_relnum usb release number 20h ro 61h fl_adj frame length adjustment 20h r/w 62h?63h pwake_cap port wake capabilities 01ffh r/w 64h?67h ? reserved ?? 68h?6bh leg_ext_cap usb ehci legacy support extended capability 00000001h r/w, ro 6ch?6fh leg_ext_cs usb ehci legacy extended support control/status 00000000h r/w, r/wc, ro 70h?73h special_smi intel specific usb 2.0 smi 00000000h r/w, r/wc 74h?7fh ? reserved ?? 80h access_cntl access control 00h r/w table 16-140.usb ehci pci register addres s map (usb ehci?d29:f7) (sheet 2 of 2) offset mnemonic register name default value type bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel. bit description 15:0 device id ? ro. this is a 16-bit value assigned to the chipset usb ehci controller. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 519 ehci controller registers (d29:f7) 16.1.3 pcicmd?pci co mmand register (usb ehci?d29:f7) address offset: 0h4 ? 05h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:11 reserved 10 interrupt disable ? r/w. 0 = the function is capable of genera ting interrupts. 1 = the function can not generate its interrupt to the interrupt controller. note that the corresponding interrupt status bit (d29:f7:06h, bit 3) is not affected by the interrupt enable. 9 fast back to back enable (fbe) ? ro. hardwired to 0. 8 serr# enable (serr_en) ? r/w. 0 = disables ehc?s capability to generate an serr#. 1 = the enhanced host controller ( ehc) is capable of genera ting (internally) serr# when it receive a completion status other than ?succe ssful? for one of its dma- initiated memory reads on dmi (and su bsequently on its internal interface). 7 wait cycle control (wcc) ? ro. hardwired to 0. 6p arity error response (per) ? ro. 1 = ehci host controller will check for co rrect parity and halt operation when bad parity is detected during the data phase as recommended by the ehci specification. if it detects bad parity on the address or command phases when this bit is set to 1, the host controller does no t take the cycle, halts the host controller (if currently not halted), and sets the host system error bit in the usbsts register. note that this applies to both requests and completions from the system interface. this bit must be set in order for the parity errors to generate serr#. 5 vga palette snoop (vps) ? ro. hardwired to 0. 4 postable memory write enable (pmwe) ? ro. hardwired to 0. 3 special cycle enable (sce) ? ro. hardwired to 0. 2 bus master enable (bme) ? r/w. 0 = disables this functionality. 1 = enables the chipset to act as a master on the pci bus for usb transfers. 1 memory space enable (mse) ? r/w. this bit controls access to the usb 2.0 memory space registers. 0 = disables this functionality. 1 = enables accesses to the usb 2.0 registers. the base address register (d29:f7:10h) for usb 2.0 should be pr ogrammed before this bit is set. 0 i/o space enable (iose) ? ro. hardwired to 0. www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 520 datasheet 16.1.4 pcists?pci status register (usb ehci?d29:f7) address offset: 06h ? 07h attribute: r/w, ro default value: 0290h 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) ? ro. hardwired to 0. 14 signaled system error (sse) ? r/w. 0 = no serr# signaled by chipset. 1 = this bit is set by the chipset when it signals serr# (internally). the ser_en bit (bit 8 of the command register) must be 1 for this bit to be set. 13 received master abort (rma) ? r/w. 0 = no master abort received by ehc on a memory access. 1 = this bit is set when ehc, as a master, receives a master abort status on a memory access. this is treated as a host error and halts the dma engines. this event can optionally generate an serr# by setting the serr# enable bit . 12 received target abort (rta) ? r/w. 0 = no target abort received by ehc on memory access. 1 = this bit is set when ehc, as a master, re ceives a target abort status on a memory access. this is treated as a host error and halts the dma engines. this event can optionally generate an serr# by setting the serr# enable bit (d29:f7:04h, bit 8). 11 signaled target abort (sta) ? ro. this bit is used to indicate when the ehci function responds to a cycle wi th a target abort. there is no reason for this to happen, so this bit will be hardwired to 0. 10:9 devsel# timing status (devt_sts) ? ro. this 2-bit field defines the timing for devsel# assertion. 8 master data parity error detected (dped) ? r/w. 0 = no data parity error detected on usb2.0 read completion packet. 1 = this bit is set by the chipset when a data parity error is detected on a usb 2.0 read completion packet on the internal interface to the ehci host controller and bit 6 of the command regist er is set to 1. 7 fast back to back capable (fb2bc) ? ro. hardwired to 1. 6 user definable features (udf) ? ro. hardwired to 0. 5 66 mhz capable (66 mhz _cap) ? ro. hardwired to 0. 4 capabilities list (cap_list) ? ro. hardwired to 1 indicating that offset 34h contains a valid ca pabilities pointer. 3 interrupt status ? ro. this bit reflects the state of this function?s interrupt at the input of the enable/disable logic. 0 = this bit will be 0 when the interrupt is de-asserted. 1 = this bit is a 1 when th e interrupt is asserted. the value reported in this bit is independen t of the value in the interrupt enable bit. 2:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 521 ehci controller registers (d29:f7) 16.1.5 rid?revision identification register (usb ehci?d29:f7) offset address: 08h attribute: ro default value: see bit description size: 8 bits 16.1.6 pi?programming interface register (usb ehci?d29:f7) address offset: 09h attribute: ro default value: 20h size: 8 bits 16.1.7 scc?sub class code register (usb ehci?d29:f7) address offset: 0ah attribute: ro default value: 03h size: 8 bits 16.1.8 bcc?base clas s code register (usb ehci?d29:f7) address offset: 0bh attribute: ro default value: 0ch size: 8 bits bit description 7:0 revision id ? ro. bit description 7:0 programming interface ? ro. a value of 20h indicates that this usb 2.0 host controller conforms to the ehci specification. bit description 7:0 sub class code (scc) ? ro. 03h = universal serial bus host controller. bit description 7:0 base class code (bcc) ? ro. 0ch = serial bus controller. www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 522 datasheet 16.1.9 pmlt?primary master latency timer register (usb ehci?d29:f7) address offset: 0dh attribute: ro default value: 00h size: 8 bits 16.1.10 mem_base?memory ba se address register (usb ehci?d29:f7) address offset: 10h ? 13h attribute: r/w, ro default value: 00000000h size: 32 bits 16.1.11 svid?usb ehci subsys tem vendor id register (usb ehci?d29:f7) address offset: 2ch ? 2dh attribute: r/w (special) default value: xxxx h size: 16 bits reset: none bit description 7:0 master latency timer count (mltc) ? ro. hardwired to 00h. because the ehci controller is internally implemented with arbitration on an interface (and not pci), it does not need a master latency timer. bit description 31:10 base address ? r/w. bits [31:10] correspond to memory address signals [31:10], respectively. this gives 1-kb of locatable memory space aligned to 1-kb boundaries. 9:4 reserved 3 prefetchable ? ro. hardwired to 0 indicating that this range should not be prefetched. 2:1 type ? ro. hardwired to 00b indicating th at this range can be mapped anywhere within 32-bit address space. 0 resource type indicator (rte) ? ro. hardwired to 0 indicating that the base address field in this regist er maps to memory space. bit description 15:0 subsystem vendor id (svid) ? r/w (special). this register, in combination with the usb 2.0 subsystem id register, enables th e operating system to distinguish each subsystem from the others. note: writes to this register are enabled wh en the wrt_rdonly bit (d29:f7:80h, bit 0) is set to 1. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 523 ehci controller registers (d29:f7) 16.1.12 sid?usb ehci su bsystem id register (usb ehci?d29:f7) address offset: 2eh ? 2fh attribute: r/w (special) default value: xxxxh size: 16 bits reset: none 16.1.13 cap_ptr?capabilit ies pointer register (usb ehci?d29:f7) address offset: 34h attribute: ro default value: 50h size: 8 bits 16.1.14 int_ln?interrupt line register (usb ehci?d29:f7) address offset: 3ch attribute: r/w default value: 00h size: 8 bits 16.1.15 int_pn?interrupt pin register (usb ehci?d29:f7) address offset: 3dh attribute: ro default value: see description size: 8 bits bit description 15:0 subsystem id (sid) ? r/w (special). bios sets the va lue in this register to identify the subsystem id. this register, in combination with th e subsystem vendor id register, enables the operating system to distinguish each subsystem from other(s). note: writes to this register are enabled when the wrt_rdonly bit (d29:f7:80h, bit 0) is set to 1. bit description 7:0 capabilities pointer (cap_ptr) ? ro. this register points to the starting offset of the usb 2.0 capabilities ranges. bit description 7:0 interrupt line (int_ln) ? r/w. this data is not used by the chipset. it is used as a scratchpad register to communicate to softwa re the interrupt line that the interrupt pin is connected to. bit description 7:0 interrupt pin ? ro. this reflects the value of d29ip.eip (chipset config registers:offset 3108:bits 31:28). note: bits 7:4 are always 0h www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 524 datasheet 16.1.16 pwr_capid?pci power management capability id register (usb ehci?d29:f7) address offset: 50h attribute: ro default value: 01h size: 8 bits 16.1.17 nxt_ptr1?next item pointer #1 register (usb ehci?d29:f7) address offset: 51h attribute: r/w (special) default value: 58h size: 8 bits 16.1.18 pwr_cap?power manageme nt capabilities register (usb ehci?d29:f7) address offset: 52h ? 53h attribute: r/w (special) default value: c9c2h size: 16 bits bit description 7:0 power management capability id ? ro. a value of 01h indicates that this is a pci power management ca pabilities field. bit description 7:0 next item pointer 1 value ? r/w (special). this regi ster defaults to 58h, which indicates that the next capa bility registers begin at co nfiguration offset 58h. this register is writable when th e wrt_rdonly bit (d29:f7:80h, bit 0) is set. this allows bios to effectively hide the de bug port capability registers, if necessary. this register should only be written during system initialization before the plug-and-play software has enabled any master-initiated traffic. only values of 58h (debug port visible) and 00h (debug port invisible) are expected to be programmed in this register. note: register not reset by d3-to-d0 warm reset. bit description 15:11 pme support (pme_sup) ? r/w (special). this 5-bit field indica tes the power states in which the function may assert pme#. the chipset ehc does not support the d1 or d2 states. for all other st ates, the chipset ehc is capable of genera ting pme#. software should not need to modify this field. 10 d2 support (d2_sup) ? r/w (special). 0 = d2 state is not supported 1 = d2 state is supported 9 d1 support (d1_sup) ? r/w (special). 0 = d1 state is not supported 1 = d1 state is supported 8:6 auxiliary current (aux_cur) ? r/w (special). the chipset ehc reports 375 ma maximum suspend well current required when in the d3 cold state. this value can be written by bios when a more accurate value is known. 5 device specific initialization (dsi )? r/w (special). the chipset reports 0, indicating that no device-specific initialization is required. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 525 ehci controller registers (d29:f7) notes: 1. normally, this register is read-only to re port capabilities to the power management software. to report different power management capabilities, dependin g on the system in which the chipset is used, bits 15:11 and 8:6 in this register are writable when the wrt_rdonly bit (d29:f7:80h, bit 0) is set. the value written to this register does not affect the hardware other than changing the value returned during a read. 2. reset: core well, but not d3-to-d0 warm reset. 16.1.19 pwr_cntl_sts?power management control/ status register (usb ehci?d29:f7) address offset: 54h ? 55h attribute: r/w, r/wc, ro default value: 0000h size: 16 bits 4 reserved 3 pme clock (pme_clk) ? r/w (special). the chipset reports 0, in dicating that no pci clock is required to generate pme#. 2:0 version (ver) ? r/w (special). the chipset reports 010b, in dicating that it complies with revision 1.1 of the pci power management specification. bit description bit description 15 pme status ? r/wc. 0 = writing a 1 to this bit will clear it and cause the internal pme to deassert (if enabled). 1 = this bit is set when the chipset ehc would normally assert the pme# signal independent of the state of the pme_en bit. note: this bit must be ex plicitly cleared by the operating system each time the operating system is loaded. 14:13 data scale ? ro. hardwired to 00b indicating it does not support the associated data register. 12:9 data select ? ro. hardwired to 0000b indicating it does not support the associated data register. 8 pme enable ? r/w. 0 = disable. 1 = enable. enables chipset ehc to generate an internal pme sign al when pme_status is 1. note: this bit must be explicitly cleared by the operating system each time it is initially loaded. 7:2 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 526 datasheet note: reset (bits 15, 8): suspend well, and not d3 -to-d0 warm reset no r core well reset. 16.1.20 debug_capid?debug port capability id register (usb ehci?d29:f7) address offset: 58h attribute: ro default value: 0ah size: 8 bits 16.1.21 nxt_ptr2?next item pointer #2 register (usb ehci?d29:f7) address offset: 59h attribute: ro default value: 00h size: 8 bits 16.1.22 debug_base?debug port base offset register (usb ehci?d29:f7) address offset: 5ah ? 5bh attribute: ro default value: 20a0h size: 16 bits 1:0 power state ? r/w. this 2-bit field is used both to determine the cu rrent power state of ehc function and to set a new power state. the definition of the field values are: 00 = d0 state 11 = d3 hot state if software attempts to write a value of 10b or 01b in to this field, the write operation must complete normally; however, the data is discarded and no state change occurs. when in the d3 hot state, the chipset must not acce pt accesses to the ehc memory range; but the configuration space must still be accessible. when not in the d0 state, the generation of the interrupt output is bloc ked. specifically, the pirqh is not asserted by the chipset when not in the d0 state. when software changes this value from the d3 hot state to the d0 state, an internal warm (soft) reset is gene rated, and software must re-initialize the function. bit description bit description 7:0 debug port capability id ? ro. hardwired to 0ah indicating that this is the start of a debug port capability structure. bit description 7:0 next item pointer 2 capability ? ro. hardwired to 00h to indicate there are no more capability structur es in this function. bit description 15:13 bar number ? ro. hardwired to 001b to indicate the memory bar begins at offset 10h in the ehci configuration space. 12:0 debug port offset ? ro. hardwired to 0a0h to indica te that the debu g port registers begin at offset a0h in the ehci memory range. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 527 ehci controller registers (d29:f7) 16.1.23 usb_relnum?usb re lease number register (usb ehci?d29:f7) address offset: 60h attribute: ro default value: 20h size: 8 bits 16.1.24 fl_adj?frame length adjustment register (usb ehci?d29:f7) address offset: 61h attribute: r/w default value: 20h size: 8 bits this feature is used to adjust any offset from the clock source that generates the clock that drives the sof counter. when a new value is written into these six bits, the length of the frame is adjusted. its initial prog rammed value is system dependent based on the accuracy of hardware usb clock and is initialized by system bios. this register should only be modified when the hchalted bit (d29:f7:caplength + 24h, bit 12) in the usb2.0_sts register is a 1. changing valu e of this register while the host controller is operating yields undefined results. it should not be reprogrammed by usb system software unless the default or bios programm ed values are incorrect, or the system is restoring the register while returning from a suspended state. these bits in suspend well and not reset by a d3-to-d0 warm rest or a core well reset. bit description 7:0 usb release number ? ro. a value of 20h indicates that this controller follows universal serial bus (usb) sp ecification, revision 2.0 . bit description 7:6 reserved ? ro. these bits are reserved for fu ture use and should read as 00b. 5:0 frame length timing value ? r/w. each decimal value change to this register corresponds to 16 high-speed bit times. the sof cycle ti me (number of sof counter clock periods to generate a sof micro-frame length) is equal to 59488 + value in this field. the default value is decimal 32 (20h ), which gives a sof cycle time of 60000. frame length (# 480 mhz clocks) (decimal) frame length timing value (this register) (decimal) 59488 0 59504 1 59520 2 ?? 59984 31 60000 32 ?? 60480 62 60496 63 www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 528 datasheet 16.1.25 pwake_cap?port wake capability register (usb ehci?d29:f7) address offset: 62 ? 63h attribute: r/w default value: 01ffh size: 16 bits this register is in the suspend power well. the intended use of this register is to establish a policy about which ports are to be used for wake events. bit positions 1?8 in the mask correspond to a physical port implemented on the current ehci controller. a 1 in a bit position indicates that a device connected below the port can be enabled as a wake-up device and the port may be enab led for disconnect/connect or overcurrent events as wake-up events. this is an information-only mask register. the bits in this register do not affect the actual operation of the ehci host controller. the system- specific policy can be established by bios in itializing this register to a system-specific value. system software uses the information in this register when enabling devices and ports for remote wake-up. these bits are not reset by a d3-to- d0 warm rest or a core well reset. 16.1.26 leg_ext_cap?usb ehci legacy support extended capability register (usb ehci?d29:f7) address offset: 68 ? 6bh attribute: r/w, ro default value: 00000001h size: 32 bits power well: suspend note: these bits are not reset by a d3-to-d0 warm rest or a core well reset. bit description 15:9 reserved ? ro. 8:1 port wake up capability mask ? r/w. bit positions 1 through 8 correspond to a physical port implemented on this host controller. for example, bit position 1 corresponds to port 0, bit position 2 corresponds to port 1, etc. 0 port wake implemented ? r/w. a 1 in this bit indica tes that this register is implemented to software. bit description 31:25 reserved ? ro. hardwired to 00h 24 hc os owned semaphore ? r/w. system software sets this bit to request ownership of the ehci controller. ownership is obtained when this bit reads as 1 and the hc bios owned semaphore bit reads as clear. 23:17 reserved ? ro. hardwired to 00h 16 hc bios owned semaphore ? r/w. the bios sets this bit to establish ownership of the ehci controller. system bios will clea r this bit in response to a request for ownership of the ehci contro ller by system software. 15:8 next ehci capability pointer ? ro. hardwired to 00h to indicate that there are no ehci extended capability st ructures in this device. 7:0 capability id ? ro. hardwired to 01h to indicate th at this ehci extended capability is the legacy support capability. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 529 ehci controller registers (d29:f7) 16.1.27 leg_ext_cs?usb ehci legacy support extended control / status register (usb ehci?d29:f7) address offset: 6c ? 6fh attribute: r/w, r/wc, ro default value: 00000000h size: 32 bits power well: suspend note: these bits are not reset by a d3-to-d0 warm rest or a core well reset. bit description 31 smi on bar ? r/wc. software clears this bit by writing a 1 to it. 0 = base address register (bar) not written. 1 = this bit is set to 1 when the base address register (bar) is written. 30 smi on pci command ? r/wc. software clears this bit by writing a 1 to it. 0 = pci command (pcicmd) register not written. 1 = this bit is set to 1 when the pci command (pcicmd) re gister is written. 29 smi on os ownership change ? r/wc. software clears this bit by writing a 1 to it. 0 = no hc os owned semaphore bit change. 1 = this bit is set to 1 when the hc os owned semaphore bit in the leg_ext_cap register (d29:f7:68h, bit 24) transitions from 1 to 0 or 0 to 1. 28:22 reserved ? ro. hardwired to 00h 21 smi on async advance ? ro. this bit is a shadow bit of the interrupt on async advance bit (d29:f7:caplength + 24h, bit 5) in the usb2.0_sts register. note: to clear this bit system software must write a 1 to the interrupt on async advance bit in the usb2.0_sts register. 20 smi on host system error ? ro. this bit is a shadow bit of host system error bit in the usb2.0_sts register (d29:f7:caplength + 24h, bit 4). note: to clear this bit system so ftware must write a 1 to th e host system error bit in the usb2.0_sts register. 19 smi on frame list rollover ? ro. this bit is a shadow bit of frame list rollover bit (d29:f7:caplength + 24h, bit 3) in the usb2.0_sts register. note: to clear this bit system software must write a 1 to the frame list rollover bit in the usb2.0_sts register. 18 smi on port change detect ? ro. this bit is a shadow bi t of port change detect bit (d29:f7:caplength + 24h, bit 2) in the usb2.0_sts register. note: to clear this bit system software must wr ite a 1 to the port change detect bit in the usb2.0_sts register. 17 smi on usb error ? ro. this bit is a shadow bit of usb error interrupt (usberrint) bit (d29:f7:caplength + 24h, bit 1) in the usb2.0_sts register. note: to clear this bit system software must wr ite a 1 to the usb error interrupt bit in the usb2.0_sts register. 16 smi on usb complete ? ro. this bit is a shadow bit of usb interrupt (usbint) bit (d29:f7:caplength + 24h, bit 0) in the usb2.0_sts register. note: to clear this bit system so ftware must write a 1 to th e usb interrupt bit in the usb2.0_sts register. www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 530 datasheet 15 smi on bar enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on ba r (d29:f7:6ch, bit 31) is 1, then the host controller will issue an smi. 14 smi on pci command enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on pci command (d29:f7:6ch, bit 30) is 1, then the host controller will issue an smi. 13 smi on os ownership enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1 and the os ownership change bit (d29:f7:6ch, bit 29) is 1, the host controller will issue an smi. 12:6 reserved ? ro. hardwired to 00h 5 smi on async advance enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the smi on async advance bit (d29:f7:6ch, bit 21) is a 1, the host controller will issue an smi immediately. 4 smi on host system error enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the smi on host system error (d29:f7:6ch, bit 20) is a 1, the host controller will issue an smi. 3 smi on frame list rollover enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the smi on frame list rollover bit (d29:f7:6ch, bit 19) is a 1, the host controller will issue an smi. 2 smi on port change enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the smi on port change de tect bit (d29:f7:6ch, bit 18) is a 1, the host controller will issue an smi. 1 smi on usb error enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the smi on usb error bit (d29:f7:6ch, bit 17) is a 1, the host controller will issue an smi immediately. 0 smi on usb complete enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and th e smi on usb complete bit (d29:f7:6ch, bit 16) is a 1, the host controller will issue an smi immediately. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 531 ehci controller registers (d29:f7) 16.1.28 special_smi?intel spec ific usb 2.0 smi register (usb ehci?d29:f7) address offset: 70h ? 73h attribute: r/w, r/wc default value: 00000000h size: 32 bits power well: suspend note: these bits are not reset by a d3-to-d0 warm rest or a core well reset. bit description 31:30 reserved ? ro. hardwired to 00h 29:22 smi on portowner ? r/wc. software clears these bits by writing a 1 to it. 0 = no port owner bit change. 1 = bits 29:22 correspond to the port owner bits for ports 1 (22) through 8 (29). these bits are set to 1 when the associated port owner bits transition from 0 to 1 or 1 to 0. 21 smi on pmcsr ? r/wc. software clears these bits by writing a 1 to it. 0 = power state bits not modified. 1 = software modified the power state bits in the power manageme nt control/status (pmcsr) register (d29:f7:54h). 20 smi on async ? r/wc. software clears these bits by writing a 1 to it. 0 = no async schedule enable bit change 1 = async schedule enable bit tran sitioned from 1 to 0 or 0 to 1. 19 smi on periodic ? r/wc. software clears this bit by writing a 1 it. 0 = no periodic schedule enable bit change. 1 = periodic schedule enable bit tr ansitions from 1 to 0 or 0 to 1. 18 smi on cf ? r/wc. software clears this bit by writing a 1 it. 0 = no configure flag (cf) change. 1 = configure flag (cf) transitions from 1 to 0 or 0 to 1. 17 smi on hchalted ? r/wc. software clears this bit by writing a 1 it. 0 = hchalted did not transition to 1 (as a re sult of the run/stop bit being cleared). 1 = hchalted transitions to 1 (as a result of the run/stop bit being cleared). 16 smi on hcreset ? r/wc. software clears th is bit by writing a 1 it. 0 = hcreset did not transitioned to 1. 1 = hcreset transitioned to 1. 15:14 reserved ? ro. hardwired to 00h 13:6 smi on portowner enable ? r/w. 0 = disable. 1 = enable. when any of these bits are 1 an d the corresponding smi on portowner bits are 1, then the host controller will issu e an smi. unused ports should have their corresponding bits cleared. 5 smi on pmscr enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on pmscr is 1, then the host controller will issue an smi. 4 smi on async enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on async is 1, then the host controller will issue an smi www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 532 datasheet 16.1.29 access_cntl?access control register (usb ehci?d29:f7) address offset: 80h attribute: r/w default value: 00h size: 8 bits 16.2 memory-mapped i/o registers the ehci memory-mapped i/o space is compos ed of two sets of registers: capability registers and operational registers. note: the chipset ehci controller will not accept memory transactions (neither reads nor writes) as a target that are locked transact ions. the locked transactions should not be forwarded to pci as the address space is known to be allocated to usb. note: when the ehci function is in the d3 pci power state, accesses to the usb 2.0 memory range are ignored and result a master abort. similarly, if the memory space enable (mse) bit (d29:f7:04h, bit 1) is not set in the command register in configuration space, the memory range will not be decoded by the chipset enhanced host controller (ehc). if the mse bit is not set, then the chipset must default to allowing any memory accesses for the range specified in the bar to go to pci. this is because the range may 3 smi on periodic enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on peri odic is 1, then the host controller will issue an smi. 2 smi on cf enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on cf is 1, then the host controller will issue an smi. 1 smi on hchalted enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1 and smi on hchalted is 1, then the host controller will issue an smi. 0 smi on hcreset enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1 and smi on hcreset is 1, then host controller will issue an smi. bit description bit description 7:1 reserved 0 wrt_rdonly ? r/w. when set to 1, this bit enables a select group of normally read- only registers in the ehc function to be writ ten by software. registers that may only be written when this mode is entered are noted in the summary tables and detailed description as ?read/write-special?. th e registers fall into two categories: 1. system-configure d parameters, and 2. status bits www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 533 ehci controller registers (d29:f7) not be valid and, therefore, the cycle must be made available to any other targets that may be currently using that range. 16.2.1 host controller capability registers these registers specify the limits, restrictio ns and capabilities of the host controller implementation. within the host controller capability registers, only the structural parameters register is writable. these re gisters are implemented in the suspend well and is only reset by the standard suspend- well hardware reset, not by hcreset or the d3-to-d0 reset. note: ?read/write special? means that the register is normally read-only, but may be written when the wrt_rdonly bit is set. because these registers are expected to be programmed by bios during initialization, their contents must not get modified by hcreset or d3-to- d0 internal reset. 16.2.1.1 caplength?capability registers length register offset: mem_base + 00h attribute: ro default value: 20h size: 8 bits 16.2.1.2 hciversion?host contro ller interface version number register offset: mem_base + 02h ? 03h attribute: ro default value: 0100h size: 16 bits table 16-141.enhanced host co ntroller capability registers mem_bas e + offset mnemonic register default type 00h caplength capabilities registers length 20h ro 02h?03h hciversion host contro ller interface version number 0100h ro 04h?07h hcsparams host controller structural parameters 00104208h r/w (special), ro 08h?0bh hccparams host controller capability parameters 00006871h ro bit description 7:0 capability register length value ? ro. this register is used as an offset to add to the memory base register (d29:f7:10h) to find the beginning of the operational register space. this field is hardwired to 20h indicating that the operation registers begin at offset 20h. bit description 15:0 host controller interface version number ? ro. this is a two-byte register containing a bcd encoding of the version numbe r of interface that th is host controller interface conforms. www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 534 datasheet 16.2.1.3 hcsparams?host cont roller structural parameters offset: mem_base + 04h ? 07h attribute: r/w (special), ro default value: 00104208h size: 32 bits note: this register is reset by a suspend well reset and not a d3-to-d0 reset or hcreset. note: this register is writable wh en the wrt_rdonly bit is set. bit description 31:24 reserved ? ro. default=0h. 23:20 debug port number (dp_n) ? ro (special). hardwired to 1h indicating that the debug port is on th e lowest numbered po rt on the chipset. 19:16 reserved 15:12 number of companion controllers (n_cc) ? r/w (special). this field indicates the number of companion controllers associated with this usb ehci host controller. a 0 in this field indicates there are no comp anion host controllers. port-ownership hand- off is not supported. only high -speed devices are supported on the host controller root ports. a value of 1 or more in this field indi cates there are companion usb uhci host controller(s). port-ownersh ip hand-offs are supported. high, full- and low-speed devices are supported on the host controller root ports. the chipset allows the default value of 4h to be over-written by bios. when removing classic controllers, they should be disabled in the following order: function 3, function 2, function 1, and function 0, which correspond to ports 7:6, 5:4, 3:2, and 1:0, respectively. 11:8 number of ports per companion controller (n_pcc) ? ro. hardwired to 2h. this field indicates the number of ports supported per companion host cont roller. it is used to indicate the port routing co nfiguration to system software. 7:4 reserved . these bits are reserv ed and default to 0. 3:0 n_ports ? r/w (special). this field specifies the numb er of physical downstream ports implemented on this host controller. the value of this field determines how many port registers are addressable in the operatio nal register space. valid values are in the range of 1h to fh. the chipset reports 8h by default. however, software may write a value less than 8 for some platform configurations. a 0 in this field is undefined. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 535 ehci controller registers (d29:f7) 16.2.1.4 hccparams?host cont roller capability parameters register offset: mem_base + 08h ? 0bh attribute: ro default value: 00006871h size: 32 bits 16.2.2 host controller operational registers this section defines the enhanced host controller operational registers. these registers are located after the capabilities registers. the operational register base must be dword-aligned and is calculated by adding the value in the first capabilities register (caplength) to the base address of the enhanced host controller register address space (mem_base). since caplength is always 20h, table 16-142 already accounts for this offset. all registers are 32 bits in length. bit description 31:16 reserved 15:8 ehci extended capabilities pointer (eecp) ? ro. this field is hardwired to 68h, indicating that the ehci capa bilities list exists and begins at offset 68h in the pci configuration space. 7:4 isochronous scheduling threshold ? ro. this field indicates, relative to the current position of the executing host controller, where software can reliably update the isochronous schedule. when bit 7 is 0, the value of the least significant 3 bits indicates the number of micro-frames a host controller hold a set of isochronous data structures (one or more) before flushing the state. when bit 7 is a 1, then host software assumes the host controller may cache an isochronous data structure for an entire frame. refer to the ehci specification for details on how software uses this information for scheduling isochronous transfers. this field is hardwired to 7h. 3 reserved . these bits are reserved and should be set to 0. 2 asynchronous schedule park capability ? ro. this bit is hardwired to 0 indicating that the host controller does no t support this optional feature 1 programmable frame list flag ? ro. 0 = system software must use a frame list length of 1024 elements with this host controller. the usb2.0_cmd register (d29:f7:caplength + 20h, bits 3:2) frame list size field is a read-only regist er and must be set to 0. 1 = system software can specify and use a sm aller frame list and configure the host controller via the usb2.0_cmd register frame list size field. the frame list must always be aligned on a 4k page boundary . this requirement ensures that the frame list is always physically contiguous. 0 64-bit addressing capability ? ro. this field documents the addressing range capability of this implementation. the value of this field determines whether software should use the 32-bit or 64-bit data structur es. values for this field have the following interpretation: 0 = data structures using 32- bit address memory pointers 1 = data structures using 64-bi t address memory pointers this bit is hardwired to 1. note: chipset only implements 44 bits of addressing. bits 63:44 will always be 0. www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 536 datasheet note: software must read and write these registers using only dword accesses.these registers are divided into two sets. the fi rst set at offsets mem_base + 00:3bh are implemented in the core power well. unless otherwise noted, the core well registers are reset by the assertion of any of the following: ? core well hardware reset ? hcreset table 16-142.enhanced host controlle r operational register address map mem_bas e + offset mnemonic register name default special notes type 20h?23h usb2.0_cmd usb 2.0 command 00080000h r/w, ro 24h?27h usb2.0_sts usb 2.0 status 00001000h r/wc, ro 28h?2bh usb2.0_intr usb 2.0 interrupt enable 00000000h r/w 2ch?2fh frindex usb 2.0 frame index 00000000h r/w, 30h?33h ctrldssegm ent control data structure segment 00000000h r/w, ro 34h?37h perodiclist base period frame list base address 00000000h r/w 38h?3bh asynclistad dr current asynchronous list address 00000000h r/w 3ch?5fh ? reserved 0h ro 60h?63h configflag configure flag 00000000h suspend r/w 64h?67h port0sc port 0 status and control 00003000h suspend r/w, r/wc, ro 68h?6bh port1sc port 1 status and control 00003000h suspend r/w, r/wc, ro 6ch?6fh port2sc port 2 status and control 00003000h suspend r/w, r/wc, ro 70h?73h port3sc port 3 status and control 00003000h suspend r/w, r/wc, ro 74h?77h port4sc port 4 status and control 00003000h suspend r/w, r/wc, ro 78h?7bh port5sc port 5 status and control 00003000h suspend r/w, r/wc, ro 7ch?7fh port6sc port 6 status and control 00003000h suspend r/w, r/wc, ro 80h?83h port7sc port 7 status and control 00003000h suspend r/w, r/wc, ro 84h?9fh ? reserved undefined ro a0h?b3h ? debug port re gisters undefined see register description b4h?3ffh ? reserved undefined ro www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 537 ehci controller registers (d29:f7) ? d3-to-d0 reset the second set at offsets mem_base + 60h to the end of the implemented register space are implemented in the suspend po wer well. unless otherwise noted, the suspend well registers are reset by the assertion of either of the following: ? suspend well hardware reset ? hcreset 16.2.2.1 usb2.0_cmd?usb 2.0 command register offset: mem_base + 20?23h attribute: r/w, ro default value: 00080000h size: 32 bits bit description 31:24 reserved . these bits are reserved and should be set to 0 when writing this register. 23:16 interrupt threshold control ? r/w. system software uses this field to select the maximum rate at which the host controller wi ll issue interrupts. the only valid values are defined below. if software writes an invalid value to this register, the results are undefined. 15:8 reserved . these bits are reserved an d should be set to 0 when writing this register. 11:8 unimplemented asynchronous park mode bits. hardwired to 000b indicating the host controller does not support this optional feature. 7 light host controller reset ? ro. hardwired to 0. the chipset does not implement this optional reset. 6 interrupt on async advance doorbell ? r/w. this bit is used as a doorbell by software to tell the host controller to is sue an interrupt the ne xt time it advances asynchronous schedule. 0 = the host controller sets this bit to a 0 after it has set the interrupt on async advance status bit (d29:f7:caplength + 24h, bit 5) in the usb2.0_sts register to a 1. 1 = software must write a 1 to this bit to ri ng the doorbell. when the host controller has evicted all appropriate cached schedule state, it sets the interrupt on async advance status bit in the usb2.0_sts register. if the interrupt on async advance enable bit in the usb2.0_intr register (d29:f7:caplength + 28h, bit 5) is a 1 then the host controller will assert an in terrupt at the next in terrupt thre shold. see the ehci specification for operational details. note: software should not write a 1 to this bit when the asynchronous schedule is inactive. doing so will yield undefined results. value maximum interrupt interval 00h reserved 01h 1 micro-frame 02h 2 micro-frames 04h 4 micro-frames 08h 8 micro-frames (default, equates to 1 ms) 10h 16 micro-frames (2 ms) 20h 32 micro-frames (4 ms) 40h 64 micro-frames (8 ms) www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 538 datasheet 5 asynchronous schedule enable ? r/w. default 0b. this bit controls whether the host controller skips processi ng the asynchronous schedule. 0 = do not process the asynchronous schedule 1 = use the asynclistaddr register to access the asynchronous schedule. 4 periodic schedule enable ? r/w. default 0b. this bit controls whether the host controller skips processing the periodic schedule. 0 = do not process the periodic schedule 1 = use the periodiclistbase register to access the periodic schedule. 3:2 frame list size ? ro. the chipset hardwires this field to 00b because it only supports the 1024-element frame list size. 1 host controller reset (hcreset) ? r/w. this control bit us ed by software to reset the host controller. the effects of this on root hub registers ar e similar to a chip hardware reset (i.e., rsmrst# assertion and pwro k deassertion on the chipset). when software writes a 1 to th is bit, the host controller re sets its internal pipelines, timers, counters, state machines, etc. to their initial value. any transaction currently in progress on usb is immediat ely terminated. a usb reset is not driven on downstream ports. note: pci configuration registers and host co ntroller capability registers are not effected by this reset. all operational registers, including port re gisters and port state machines are set to their initial values. port ownership reverts to the companion host controller(s), with the side effects described in the ehci spec. soft ware must re-initialize the host controller in order to return the host cont roller to an operational state. this bit is set to 0 by the host controller when the reset process is complete. software cannot terminate the reset process earl y by writing a 0 to this register. software should not set this bit to a 1 when the hchalted bit (d29:f7:caplength + 24h, bit 12) in the usb2.0_sts register is a 0. attempting to reset an actively running host controller will result in undefined behavior. this rese t me be used to leave ehci port test modes. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 539 ehci controller registers (d29:f7) note: the command register indicates the command to be executed by the serial bus host controller. writing to the register causes a command to be executed. 16.2.2.2 usb2.0_sts?usb 2.0 status register offset: mem_base + 24h?27h attribute: r/wc, ro default value: 00001000h size: 32 bits this register indicates pending interrupts and various states of the host controller. the status resulting from a transaction on the serial bus is not indicated in this register. see the interrupts description in section 4 of the ehci specification for additional information concerning usb 2.0 interrupt conditions. note: for the writable bits, software must write a 1 to clear bits that are set. writing a 0 has no effect. 0 run/stop (rs) ? r/w. 0 = stop (default) 1 = run. when set to a 1, the host controller proceeds with execution of the schedule. the host controller continues execution as long as this bit is set. when this bit is set to 0, the host controller completes the current transaction on the usb and then halts. the hchalted bit in the usb2.0_sts register indicates when the host controller has finished the transactio n and has entered the stopped state. software should not wr ite a 1 to this field unless the ho st controller is in the halted state (i.e., hchalted in the usbsts register is a 1). the halted bit is cleared immediately when the run bit is set. the following table expl ains how the different combinatio ns of run and halted should be interpreted: memory read cycles initiated by the ehc that receive any status other than successful will result in this bit being cleared. bit description run/stop halted interpretation 0b 0b in the process of halting 0b 1b halted 1b 0b running 1b 1b invalid - the hchalted bit clears immediately bit description 31:16 reserved . these bits are reserved and should be set to 0 when writing this register. 15 asynchronous schedule status ? ro. this bit reports the cu rrent real status of the asynchronous schedule. 0 = status of the asynchronous schedule is disabled. (default) 1 = status of the asynchronous schedule is enabled. note: the host controller is not required to immediately disable or enable the asynchronous schedule when software transitions the asynchronous schedule enable bit (d29:f7:caplength + 20h, bit 5) in the usb2.0_cmd register. when this bit and the asynchronous schedule enable bit are the same value, the asynchronous schedule is either enabled (1) or disabled (0). www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 540 datasheet 14 periodic schedule status ? ro. this bit reports the current real status of the periodic schedule. 0 = status of the periodic sche dule is disabled. (default) 1 = status of the periodic schedule is enabled. note: the host controller is not required to immediately disable or enable the periodic schedule when softwa re transitions the periodic schedule enable bit (d29:f7:caplength + 20h, bit 4) in the usb2.0_cmd register. when this bit and the periodic schedule enable bit are the same value, the periodic schedule is either enabled (1) or disabled (0). 13 reclamation ? ro. 0=default. this read-only status bit is used to detect an empty asynchronous schedule. the operational mode l and valid transitions for this bit are described in section 4 of the ehci specification. 12 hchalted ? ro. 0 = this bit is a 0 when the run/stop bit is a 1. 1 = the host controller sets this bit to 1 afte r it has stopped executin g as a result of the run/stop bit being set to 0, either by soft ware or by the host controller hardware (e.g., internal error). (default) 11:6 reserved 5 interrupt on async advance ? r/wc. 0=default. system softwa re can force the host controller to issue an inte rrupt the next time the host controller advances the asynchronous schedule by writing a 1 to the interrupt on async advance doorbell bit (d29:f7:caplength + 20h, bit 6) in the us b2.0_cmd register. th is bit indicates the assertion of that interrupt source. 4 host system error ? r/wc. 0 = no serious error occurred during a host sy stem access involving the host controller module 1 = the host controller sets this bit to 1 when a serious error oc curs during a host system access involving the host contro ller module. a hardware interrupt is generated to the system. memory read cycles initiated by the ehc that receive any status other than successful will result in this bit being set. when this error occurs, th e host controller clears the run/stop bit in the usb2.0_cmdregister (d29:f7:caplength + 20h, bit 0) to prevent further execution of the scheduled tds. a hardware interrupt is generate d to the system (if enabled in the interrupt enable register). 3 frame list rollover ? r/wc. 0 = no frame list index rollover from its maximum value to 0. 1 = the host controller sets this bit to a 1 when the frame list index (see section) rolls over from its maximum value to 0. since the chipset only supports the 1024-entry frame list size, the frame list index rolls over every time frnum13 toggles. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 541 ehci controller registers (d29:f7) 14 periodic schedule status ? ro. this bit reports the current re al status of the periodic schedule. 0 = status of the periodic sche dule is disabled. (default) 1 = status of the periodic schedule is enabled. note: the host controller is not required to immediately disable or enable the periodic schedule when softwa re transitions the periodic schedule enable bit (d29:f7:caplength + 20h, bit 4) in the usb2.0_cmd register. when this bit and the periodic schedule enable bit are the same value, the periodic schedule is either enabled (1) or disabled (0). 13 reclamation ? ro. 0=default. this read-only status bit is used to detect an empty asynchronous schedule. the operational mode l and valid transitions for this bit are described in section 4 of the ehci specification. 12 hchalted ? ro. 0 = this bit is a 0 when the run/stop bit is a 1. 1 = the host controller sets this bit to 1 afte r it has stopped executin g as a result of the run/stop bit being set to 0, either by soft ware or by the host controller hardware (e.g., internal error). (default) 11:6 reserved 5 interrupt on async advance ? r/wc. 0=default. system softwa re can force the host controller to issue an inte rrupt the next time the host controller advances the asynchronous schedule by writing a 1 to the interrupt on async advance doorbell bit (d29:f7:caplength + 20h, bit 6) in the us b2.0_cmd register. th is bit indicates the assertion of that interrupt source. 4 host system error ? r/wc. 0 = no serious error occurred during a host system access involving the host controller module 1 = the host controller sets this bit to 1 when a serious error oc curs during a host system access involving the host contro ller module. a hardware interrupt is generated to the system. memory read cycl es initiated by the ehc that receive any status other than successful will result in this bit being set. when this error occurs, the host contro ller clears the run/stop bit in the usb2.0_cmdregister (d29:f7:caplengt h + 20h, bit 0) to prevent further execution of the scheduled tds. a hardware interrupt is generated to the system (if enabled in the interrupt enable register). 3 frame list rollover ? r/wc. 0 = no frame list index rollover from its maximum value to 0. 1 = the host controller sets this bit to a 1 when the frame list index (see section) rolls over from its maximum value to 0. since the chipset only supports the 1024-entry frame list size, the frame list index rolls over every time frnum13 toggles. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 542 datasheet 16.2.2.3 usb2.0_intr?usb 2.0 interrupt enable register offset: mem_base + 28h?2bh attribute: r/w default value: 00000000h size: 32 bits this register enables and disables reporting of the corresponding interrupt to the software. when a bit is set and the corresponding interrupt is active, an interrupt is generated to the host. interrupt sources that are disabled in this register still appear in the usb2.0_sts register to allow the software to poll for events. each interrupt enable bit description indicates whether it is depe ndent on the interrupt threshold mechanism (see section 4 of the ehci specification), or not. 2 port change detect ? r/wc. this bit is allowed to be maintained in the auxiliary power well. alternatively, it is also acceptable that on a d3 to d0 transition of the ehci hc device, this bit is loaded with the or of all of the portsc change bits (including: force port resume, overcurre nt change, enable/disable change and connect status change). regardless of the im plementation, when this bit is readable (i.e., in the d0 state), it must provide a valid vi ew of the port status registers. 0 = no change bit transition from a 0 to 1 or no force port resume bit transition from 0 to 1 as a result of a j-k transiti on detected on a suspended port. 1 = the host controller sets this bi t to 1 when any port for which the port owner bit is set to 0 has a change bit transition fro m a 0 to 1 or a force port resume bit transition from 0 to 1 as a result of a j- k transition detected on a suspended port. 1 usb error interrupt (usberrint) ? r/wc. 0 = no error condition. 1 = the host controller sets this bit to 1 when completion of a usb transaction results in an error condition (e.g., error counter un derflow). if the td on which the error interrupt occurred also had its ioc bit set, both this bit and bit 0 are set. see the ehci specification for a list of the usb errors that will result in this interrupt being asserted. 0 usb interrupt (usbint) ? r/wc. 0 = no completion of a usb transaction whose transfer descriptor had its ioc bit set. no short packet is detected. 1 = the host controller sets this bit to 1 when the cause of an interrupt is a completion of a usb transaction whose transfer descriptor had its ioc bit set. the host controller also sets this bit to 1 when a short packet is detected (actual number of bytes received was less th an the expected number of bytes). bit description bit description 31:6 reserved . these bits are reserved and should be 0 when writing this register. 5 interrupt on async advance enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, an d the interrupt on async advance bit (d29:f7:caplength + 24h, bit 5) in the usb2.0_sts register is a 1, the host controller will issue an interrupt at the next interrupt threshol d. the interrupt is acknowledged by software clearing the interrupt on async advance bit. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 543 ehci controller registers (d29:f7) 16.2.2.4 frindex?frame index register offset: mem_base + 2ch?2fh attribute: r/w default value: 00000000h size: 32 bits the sof frame number value for the bus sof token is derived or alternatively managed from this register. refer to section 4 of the ehci specification for a detailed explanation of the sof value management requirements on the host controller. the value of frindex must be within 125 s (1 micro-frame) ahead of the sof token va lue. the sof value may be implemented as an 11-bit shadow register. for this discussion, this shadow register is 11 bits and is named sofv. sofv updates every 8 micr o-frames. (1 millisecond). an example implementation to achieve this behavior is to increment sofv each time the frindex[2:0] increments from 0 to 1. software must use the value of frindex to derive the current micro-frame number, both for high-speed isochronous schedulin g purposes and to provide the get micro-frame number function required to client driver s. therefore, the value of frindex and the 4 host system error enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, an d the host system error status bit (d29:f7:caplength + 24h, bit 4) in the us b2.0_sts register is a 1, the host controller will issue an interrupt. the interrupt is acknow ledged by software clearing the host system error bit. 3 frame list rollover enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the frame list roll over bit (d29:f7:caplength + 24h, bit 3) in the usb2.0_sts register is a 1, the host controller will issue an interrupt. the interrupt is acknowledged by software cleari ng the frame list rollover bit. 2 port change interrupt enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the port change de tect bit (d29:f7:caplength + 24h, bit 2) in the usb2.0_sts register is a 1, the host controller will issue an interrupt. the interrupt is acknowledged by software clearing the port change detect bit. 1 usb error interrupt enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and th e usberrint bit (d29:f7:caplength + 24h, bit 1) in the usb2.0_sts register is a 1, the host controller will issue an interrupt at the next interrupt thre shold. the interrupt is acknowledged by software by clearing the usberrint bit in the usb2.0_sts register. 0 usb interrupt enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the usbint bit (d29: f7:caplength + 24h, bit 0) in the usb2.0_sts register is a 1, the host controller will issue an interrupt at the next interrupt threshold. th e interrupt is acknowledged by software by clearing the usbint bit in the usb2.0_sts register. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 544 datasheet value of sofv must be kept consistent if ch ip is reset or software writes to frindex. writes to frindex must also write-through frindex[13:3] to sofv[10:0]. in order to keep the update as simple as possible, software should not writ e a frindex value where the three least significant bits are 111b or 000b. note: this register is used by the host controller to index into the periodic frame list. the register updates every 125 microseconds (once each micro-frame). bits [12:3] are used to select a particular entry in the pe riodic frame list during periodic schedule execution. the number of bits used for the index is fixed at 10 for the chipset since it only supports 1024-entry frame lists. this register must be written as a dword. word and byte writes produce undefined results. this register cannot be written unless the host controller is in the halted state as indicated by the hchalted bit (d29:f7:caplength + 24h, bit 12). a write to this register while the run/stop bit (d29:f7:caplength + 20h, bit 0) is set to a 1 (usb2.0_cmd register) produces undefined results. writes to this register also effect the sof value. see section 4 of the ehci specification for details. 16.2.2.5 ctrldssegment?control data structure segment register offset: mem_base + 30h?33h attribute: r/w, ro default value: 00000000h size: 32 bits this 32-bit register corresponds to the most significant address bits [63:32] for all ehci data structures. since the chipset hard wires the 64-bit addressing capability field in hccparams to 1, then this register is used with the link pointers to construct 64-bit addresses to ehci control data structures. th is register is concatenated with the link pointer from either the periodiclistbase , asynclistaddr, or any control data structure link field to construct a 64-bit address. this register allows the host software to locate all control data structures within the same 4 gb memory segment. bit description 31:14 reserved 13:0 frame list current index/frame number ? r/w. the value in this register increments at the end of each time frame (e.g., micro-frame). bits [12:3] are used for the fr ame list current inde x. this means that each location of the frame list is accessed 8 times (frames or micro-frames) before moving to the next index. bit description 31:12 upper address[63:44] ? ro. hardwired to 0s. the chip set ehc is only capable of generating addresses up to 16 terabytes (44 bits of address). 11:0 upper address[43:32] ? r/w. this 12-bit field co rresponds to address bits 43:32 when forming a control data structure address. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 545 ehci controller registers (d29:f7) 16.2.2.6 periodiclistbase?perio dic frame list base address register offset: mem_base + 34h?37h attribute: r/w default value: 00000000h size: 32 bits this 32-bit register contains the beginning address of the periodic frame list in the system memory. since the chipset host controller operates in 64-bit mode (as indicated by the 1 in the 64-bit addressi ng capability field in the hccsparams register) (offset 08h, bit 0), then the most significant 32 bits of every control data structure address comes from the ctrldssegment register. hcd loads this register prior to starting the schedule execution by the host controller. the memory structure referenced by this physical memory pointer is assumed to be 4-kbyte aligned. the contents of this register are combined with the frame index register (frindex) to enable the host controller to step through the periodic frame list in sequence. 16.2.2.7 asynclistaddr?current asynchronous list address register offset: mem_base + 38h?3bh attribute: r/w default value: 00000000h size: 32 bits this 32-bit register contains the address of the next asynchronous queue head to be executed. since the chipset host controller operates in 64-bit mode (as indicated by a 1 in 64-bit addressing capability field in the hccparams register) (offset 08h, bit 0), then the most significant 32 bits of every control data structure address comes from the ctrldssegment register (offset 08h). bi ts [4:0] of this register cannot be modified by system software and will al ways return 0?s when read. the memory structure referenced by this physical memory pointer is assumed to be 32-byte aligned. bit description 31:12 base address (low) ? r/w. these bits correspon d to memory address signals [31:12], respectively. 11:0 reserved . must be written as 0s. during runtime, the value of these bits are undefined. bit description 31:5 link pointer low (lpl) ? r/w. these bits correspon d to memory address signals [31:5], respectively. this field may only reference a queue head (qh). 4:0 reserved . these bits are reserved and their value has no effe ct on operation. www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 546 datasheet 16.2.2.8 configflag?configure flag register offset: mem_base + 60h?63h attribute: r/w default value: 00000000h size: 32 bits this register is in the suspend power well. it is only reset by hardware when the suspend power is initially applied or in response to a host controller reset. 16.2.2.9 portsc?port n status and control register offset: port 0: mem_base + 64h ? 67h port 1: mem_base + 68 ? 6bh port 2: mem_base + 6c ? 6fh port 3: mem_base + 70 ? 73h port 4: mem_base + 74 ? 77h port 5: mem_base + 78 ? 7bh port 6: mem_base + 7c ? 7fh port 7: mem_base + 80 ? 83h attribute: r/w, r/wc, ro default value: 00003000h size: 32 bits a host controller must implement one or more port registers. software uses the n_port information from the structural parameters register to determine how many ports need to be serviced. all ports have the st ructure defined below. software must not write to unreported port status and control registers. this register is in the suspend power well. it is only reset by hardware when the suspend power is initially applied or in resp onse to a host controller reset. the initial conditions of a port are: ? no device connected ? port disabled. when a device is attached, the port state transitions to the attached state and system software will process this as with any status change notification. refer to section 4 of the ehci specification for operational requirements for how change events interact with port suspend mode. bit description 31:1 reserved . read from this field will always return 0. 0 configure flag (cf) ? r/w. host software sets this bit as the last action in its process of configuring the host controller. this bit co ntrols the default port-routing control logic. bit values and side-effects are listed below. see section 4 of the ehci spec for operation details. 0 = port routing control logic default-routes each port to the classic host controllers (default). 1 = port routing control logic default-rout es all ports to this host controller. bit description 31:23 reserved . these bits are reserved for future use and will return a value of 0?s when read. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 547 ehci controller registers (d29:f7) 22 wake on overcurrent enable (wkoc_e) ? r/w. 0 = disable. (default) 1 = enable. writing this bit to a 1 enables th e setting of the pme status bit in the power management control/status register (o ffset 54, bit 15) wh en the overcurrent active bit (bit 4 of this register) is set. 21 wake on disconnect enable (wkdscnnt_e) ? r/w. 0 = disable. (default) 1 = enable. writing this bit to a 1 enables th e setting of the pme status bit in the power management control/status register (offset 54, bit 15) when the current connect status changes from connected to disconnected (i.e., bit 0 of this register changes from 1 to 0). 20 wake on connect enable (wkcnnt_e) ? r/w. 0 = disable. (default) 1 = enable. writing this bit to a 1 enables th e setting of the pme status bit in the power management control/status register (offset 54, bit 15) when the current connect status changes from disconnected to connecte d (i.e., bit 0 of th is register changes from 0 to 1). 19:16 port test control ? r/w. when this field is 0?s, the port is not operating in a test mode. a non-zero value indicates that it is operating in test mode and the specific test mode is indicated by the spec ific value. the encoding of the test mode bits are (0110b ? 1111b are reserved): refer to usb specification revision 2.0, chapter 7 for details on each test mode. 15:14 reserved ? r/w. should be written to =00b. 13 port owner ? r/w. default = 1b. this bit unconditionally goes to a 0 when the configured flag bit in the usb2.0_cmd register makes a 0 to 1 transition. system software uses this field to release ownership of the port to a selected host controller (in the event that the attached de vice is not a high-spe ed device). software writes a 1 to this bit when the attached device is not a high-speed device. a 1 in this bit means that a companion host controller owns and controls the port. see section 4 of the ehci specification for operational details. 12 port power (pp) ? ro. read-only with a value of 1. this indicates that the port does have power. 11:10 line status ? ro.these bits reflect the current logical levels of the d+ (bit 11) and d? (bit 10) signal lines. these bits are used fo r detection of low-speed usb devices prior to the port reset and enable sequen ce. this field is valid only when the port enable bit is 0 and the current connect stat us bit is set to a 1. 00 = se0 10 = j-state 01 = k-state 11 = undefined 9 reserved . this bit will retu rn a 0 when read. bit description value maximum interrupt interval 0000b test mode not enabled (default) 0001b test j_state 0010b test k_state 0011b test se0_nak 0100b test packet 0101b force_enable www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 548 datasheet 8 port reset ? r/w. default = 0. when software wr ites a 1 to this bit (from a 0), the bus reset sequence as defined in the usb specification, revision 2.0 is started. software writes a 0 to this bit to terminate the bus reset sequence. software must keep this bit at a 1 long enough to ensure the reset sequence completes as specified in the usb specification, revision 2.0. 1 = port is in reset. 0 = port is not in reset. note: when software writes a 0 to this bit, th ere may be a delay be fore the bit status changes to a 0. the bit status will no t read as a 0 until after the reset has completed. if the port is in high-speed mode after re set is complete, the host controller will automatically en able this port (e.g., set the port enable bit to a 1). a host controller must terminate the reset and stabilize th e state of the port within 2 milliseconds of software transitioning this bit from 0 to 1. for example: if the port de tects that the attached device is high-speed during reset, then the host controller must ha ve the port in the enabled state within 2 ms of software writing this bit to a 0. the hchalted bit (d29:f7:caplength + 24h, bit 12) in the usb2.0_sts regist er should be a 0 before software attempts to use this bit. the host controller may hold port reset asserted to a 1 when the hchalted bit is a 1. th is bit is 0 if port power is 0. note: system software should not at tempt to reset a port if the hchalted bit in the usb2.0_sts register is a 1. doing so will result in undefined behavior. 7 suspend ? r/w. 0 = port not in suspend state.(default) 1 = port in suspend state. port enabled bit and suspend bit of this re gister define the port states as follows: when in suspend state, downstream propagatio n of data is blocked on this port, except for port reset. note that the bit status does not change un til the port is suspended and that there may be a delay in suspending a po rt depending on the ac tivity on the port. the host controller will unconditionally se t this bit to a 0 when software sets the force port resume bit to a 0 (from a 1). a write of 0 to this bit is ignored by the host controller. if host software sets this bit to a 1 when the port is not enabled (i.e., port enabled bit is a 0) the results are undefined. bit description port enabled suspend port state 0xdisabled 10enabled 11suspend www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 549 ehci controller registers (d29:f7) 6 force port resume ? r/w. 0 = no resume (k-state) detected/driven on port. (default) 1 = resume detected/driven on port. software sets this bit to a 1 to drive resume signaling. the host controller sets this bit to a 1 if a j-to-k transition is detected while the port is in the suspend state. wh en this bit transitions to a 1 because a j- to-k transition is detected, the port change detect bit (d29:f7:caplength + 24h, bit 2) in the usb2.0_sts register is also set to a 1. if software sets this bit to a 1, the host controller must not se t the port change detect bit. note: when the ehci controller owns the po rt, the resume sequence follows the defined sequence documented in the us b specification, revision 2.0. the resume signaling (full-speed 'k') is driv en on the port as long as this bit remains a 1. software must appropriately time the resume and set this bit to a 0 when the appropriate amount of time has elapsed. writing a 0 (from 1) causes the port to return to high-speed mode (forcing the bus below the port into a high-speed idle). this bit will remain a 1 until the port has switched to the high-speed idle. 5 overcurrent change ? r/wc. the functionality of this bit is not dependent upon the port owner. software clears th is bit by writing a 1 to it. 0 = no change. (default) 1 = there is a change to overcurrent active. 4 overcurrent active ? ro. 0 = this port does not have an overcurrent condition. (default) 1 = this port currently has an overcurrent condition. this bit will automatically transition from 1 to 0 when the over cu rrent condition is removed. the chipset automatically disables the port when the overcurrent active bit is 1. 3 port enable/disable change ? r/wc. for the root hub, this bit gets set to a 1 only when a port is disabled due to the appropri ate conditions existing at the eof2 point (see chapter 11 of the usb specification for th e definition of a port error). this bit is not set due to the disabled-to-enabled tran sition, nor due to a disconnect. software clears this bit by writing a 1 to it. 0 = no change in status. (default). 1 = port enabled/disabled status has changed. 2 port enabled/disabled ? r/w. ports can only be enabled by the host controller as a part of the reset and enable. so ftware cannot enable a port by writing a 1 to this bit. ports can be disabled by ei ther a fault condition (disconnect event or other fault condition) or by host software. note that th e bit status does not change until the port state actually changes. there may be a delay in disabling or enabling a port due to other host controll er and bus events. 0 = disable 1 = enable (default) 1 connect status change ? r/wc. this bit indicates a change has occurred in the port?s current connect status. software se ts this bit to 0 by writing a 1 to it. 0 = no change (default). 1 = change in current connect status. the host controller sets this bit for all changes to the port device connect status, even if system software has not cleared an existing connect status change. for example, the insertion status changes twice before system software has cleared the ch anged condition, hub hardware will be ?setting? an already-set bit (i.e ., the bit will remain set). bit description www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 550 datasheet 16.2.3 usb 2.0-based debug port register the debug port?s registers are located in the same memory area, defined by the base address register (mem_base), as the standard ehci registers. the base offset for the debug port registers (a0h) is declared in the debug port base offset capability register at configuration offset 5ah (d 29:f7:offset 5ah). the specific ehci port that supports this debug capability (port 0) is indicated by a 4-bit field (bits 20 ? 23) in the hcsparams register of the ehci controlle r. the address map of the debug port registers is shown in table 16-143 . notes: 1. all of these registers are implemented in the core well and reset by pltrst#, ehc hcreset, and a ehc d3-to-d0 transition . 2. the hardware associated with this register provides no chec ks to ensure that software programs the interface correctly. how the hardware behaves when programmed inappropriately is undefined. 16.2.3.1 cntl_sts?control/status register offset: mem_base + a0h attribute: r/w, r/wc, ro, wo default value: 0000h size: 32 bits 0 current connect status ? ro. this value reflects the current state of the port, and may not correspond directly to the event th at caused the connec t status change bit (bit 1) to be set. 0 = no device is present. (default) 1 = device is present on port. bit description table 16-143.debug port register address map mem_base + offset mnemonic register name default type a0?a3h cntl_sts control/status 00000000h r/w, r/wc, ro, wo a4?a7h usbpid usb pids 00000000h r/w, ro a8?abh databuf[3:0] data buffer (bytes 3:0) 00000000h r/w ac?afh databuf[7:4] data buffer (bytes 7:4) 00000000h r/w b0?b3h config configuration 00007f01h r/w bit description 31 reserved 30 owner_cnt ? r/w. 0 = ownership of the debug port is not forced to the ehci controller (default) 1 = ownership of the debug port is forced to the ehci controller (i.e. immediately taken away from the companion classic usb host controller) if the port was already owned by the ehci controller, then setting this bit has no effect. this bit overrides all of the owners hip-related bits in the standard ehci registers. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 551 ehci controller registers (d29:f7) 29 reserved 28 enabled_cnt ? r/w. 0 = software can clear this by writing a 0 to it. the hardware clears this bit for the same conditions where the port enable /disable change bit (in the portsc register) is set. (default) 1 = debug port is enabled for operation. soft ware can directly set this bit if the port is already enabled in the associated port sc register (this is enforced by the hardware). 27:17 reserved 16 done_sts ? r/wc. software can clear th is by writing a 1 to it. 0 = request not complete 1 = set by hardware to indicate that the request is complete. 15:12 link_id_sts ? ro. this field identifies the link interface. 0h = hardwired. indicates that it is a usb debug port. 11 reserved . this bit returns 0 when re ad. writes have no effect. 10 in_use_cnt ? r/w. set by software to indicate th at the port is in use. cleared by software to indicate that the port is free and may be used by other software. this bit is cleared after reset. (this bi t has no effect on hardware.) 9:7 exception_sts ? ro. this field indicates the exception when the error_good#_sts bit is set. this field should be ignored if the error_good#_sts bit is 0. 000 =no error. (default) note: this should not be seen, since this field should only be checked if there is an error. 001 =transaction error: in dicates the usb 2.0 transaction had an error (crc, bad pid, timeout, etc.) 010 =hardware error. request was attemp ted (or in progress) when port was suspended or reset. all other combinations are reserved 6 error_good#_sts ? ro. 0 = hardware clears this bit to 0 after the proper completion of a read or write. (default) 1 = error has occurred. details on the natu re of the error are provided in the exception field. 5 go_cnt ? wo. 0 = hardware clears this bit when hardwa re sets the done_sts bit. (default) 1 = causes hardware to perform a read or write request. note: writing a 1 to this bit when it is alre ady set may result in undefined behavior. 4 write_read#_cnt ? r/w. software clears this bit to indicate th at the current request is a read. software se ts this bit to indicate th at the current request is a write. 0 = read (default) 1 = write bit description www.datasheet.co.kr datasheet pdf - http://www..net/
ehci controller registers (d29:f7) 552 datasheet notes: 1. software should do read-modify-write operations to this register to preserve the contents of bits not being mo dified. this include reserved bits. 2. to preserve the usage of reserved bits in the future, software should always write the same value read from the bit until it is defined. reserved bits will always return 0 when read. 16.2.3.2 usbpid?usb pids register offset: mem_base + a4h attribute: r/w, ro default value: 0000h size: 32 bits this dword register is used to communicate pid information between the usb debug driver and the usb debug port. the debug port uses some of these fields to generate usb packets, and uses other fields to retu rn pid information to the usb debug driver. 3:0 data_len_cnt ? r/w. this field is used to indicate the size of the data to be transferred. default = 0h. for write operations, this field is set by software to indicate to the hardware how many bytes of data in data buffer are to be transferred to the console. a value of 0h indicates that a zero-length packet should be sent. a value of 1?8 indicates 1?8 bytes are to be transferred. values 9?fh are invalid and how hardware behaves if used is undefined. for read operations, this fiel d is set by hardware to indicate to software how many bytes in data buffer are valid in response to a read operation. a value of 0h indicates that a zero length packet was returned and the state of data buffer is not defined. a value of 1?8 indicates 1?8 bytes were received. hardware is not allowed to return values 9?fh. the transferring of data alwa ys starts with byte 0 in the data area and moves toward byte 7 until the transfer size is reached. bit description bit description 31:24 reserved : these bits will return 0 when re ad. writes will have no effect. 23:16 received_pid_sts[23:16] ? ro. hardware updates this field with the received pid for transactions in either direction. when the controller is writing data, this field is updated with the handshake pid that is received from the devi ce. when the host controller is reading data, this field is updated with the da ta packet pid (if the device sent data), or the handshake pid (if the devi ce naks the request). this field is valid when the hardware clears the go_done#_cnt bit. 15:8 send_pid_cnt[15:8] ? r/w. hardware sends this pid to begin the data packet when sending data to usb (i.e., write_re ad#_cnt is asserted). software typically sets this field to either data0 or data1 pid values. 7:0 token_pid_cnt[7:0] ? r/w. hardware sends this pid as the token pid for each usb transaction. software typically sets this field to either in, out, or setup pid values. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 553 ehci controller registers (d29:f7) 16.2.3.3 databuf[7:0]?data buffer bytes[7:0] register offset: mem_base + a8h?afh attribute: r/w default value: 0000000000000000h size: 64 bits this register can be accessed as 8 separate 8-bit registers or 2 separate 32-bit register. 16.2.3.4 config?configuration register offset: mem_base + b0?b3h attribute: r/w default value: 00007f01h size: 32 bits bit description 63:0 databuffer[63:0] ? r/w. this field is the 8 byte s of the data buffer. bits 7:0 correspond to least significant byte (byte 0). bits 63:56 correspond to the most significant byte (byte 7). the bytes in the data buffer mu st be written with data befo re software initiates a write request. for a read request, the data buffer contains va lid data when done_sts bit (offset a0, bit 16) is cleared by the hard ware, error_good#_sts (offset a0, bit 6) is cleared by the hardware, and the data _length_cnt field (offset a0, bits 3:0) indicates the number of bytes that are valid. bit description 31:15 reserved 14:8 usb_address_cnf ? r/w. this 7-bit field identifies the usb device address used by the controller for all token pid generation. (default = 7fh) 7:4 reserved 3:0 usb_endpoint_cnf ? r/w. this 4-bit field identi fies the endpoint used by the controller for all token pid generation. (default = 01h) www.datasheet.co.kr datasheet pdf - http://www..net/
smbus controller registers (d31:f3) 554 datasheet 17 smbus controller registers (d31:f3) 17.1 pci configuration registers (smbus?d31:f3) note: registers that are not shown should be treated as reserved (see section 9.2 for details). 17.1.1 vid?vendor iden tification register (smbus?d31:f3) address: 00h ? 01h attribute: ro default value: 8086h size: 16 bits table 17-144.smbus controller pci register address map (smbus?d31:f3) offset mnemonic register name default type 00h?01h vid vendor identification 8086 ro 02h?03h did device identification see register description. ro 04h?05h pcicmd pci command 0000h r/w, ro 06h?07h pcists pci status 0280h ro, r/wc 08h rid revision id entification see register description. ro 09h pi programming interface 00h ro 0ah scc sub class code 05h ro 0bh bcc base class code 0ch ro 20h?23h smb_base smbus base address 00000001h r/w, ro 2ch?2dh svid subsystem vendor identification 00h ro 2eh?2fh sid subsystem identification 00h r/wo 3ch int_ln interrupt line 00h r/w 3dh int_pn interrupt pin see description ro 40h hostc host configuration 00h r/w bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 555 smbus controller registers (d31:f3) 17.1.2 did?device identificati on register (smbus?d31:f3) address: 02h ? 03h attribute: ro default value: see bit description size: 16 bits 17.1.3 pcicmd?pci command register (smbus?d31:f3) address: 04h ? 05h attributes: 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 chipset smbus controller. bit description 15:11 reserved 10 interrupt disable ? r/w. 0 = enable 1 = disables smbus to assert its pirqb# signal. 9 fast back to back enable (fbe) ? ro. hardwired to 0. 8 serr# enable (serr_en) ? r/w. 0 = enables serr# generation. 1 = disables serr# generation. 7 wait cycle control (wcc) ? ro. hardwired to 0. 6 parity error response (per) ? r/w. 0 = disable 1 = sets detected parity error bit (d31:f3:06, bit 15) when a parity error is detected. 5 vga palette snoop (vps) ? ro. hardwired to 0. 4 postable memory write enable (pmwe) ? ro. hardwired to 0. 3 special cycle enable (sce) ? ro. hardwired to 0. 2 bus master enable (bme) ? ro. hardwired to 0. 1 memory space enable (mse) ? ro. hardwired to 0. 0 i/o space enable (iose) ? r/w. 0 = disable 1 = enables access to the sm bus i/o space registers as defined by the base address register. www.datasheet.co.kr datasheet pdf - http://www..net/
smbus controller registers (d31:f3) 556 datasheet 17.1.4 pcists?pci status register (smbus?d31:f3) address: 06h ? 07h attributes: ro, r/wc 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. 17.1.5 rid?revision identificati on register (smbus?d31:f3) 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. 1 = parity error detected. 14 signaled system error (sse) ? r/wc. 0 = no system error detected. 1 = system erro r detected. 13 received master abort (rma) ? ro. hardwired to 0. 12 received target abort (rta) ? ro. hardwired to 0. 11 signaled target abort (sta) ? r/wc. 0 = chipset did not terminat e transaction for this function with a target abort. 1 = the function is targeted with a transa ction that the chipset terminates with a target abort. 10:9 devsel# timing status (devt) ? ro. this 2-bit field defines the timing for devsel# assertion for positive decode. 01 = medium timing. 8 data parity error detected (dped) ? ro. hardwired to 0. 7 fast back to back capable (fb2bc) ? ro. hardwired to 1. 6 user definable features (udf) ? ro. hardwired to 0. 5 66 mhz capable (66mhz_cap) ? ro. hardwired to 0. 4 capabilities list (cap_list) ? ro. hardwired to 0 because there are no capability list structures in this function 3 interrupt status (ints) ? ro. this bit indicates that an interrupt is pending. it is independent from the state of the interrupt enable bit in the pci command register. 2:0 reserved bit description 7:0 revision id ? ro. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 557 smbus controller registers (d31:f3) 17.1.6 pi?programmin g interface register (smbus?d31:f3) offset address: 09h attribute: ro default value: 00h size: 8 bits 17.1.7 scc?sub class code register (smbus?d31:f3) address offset: 0ah attributes: ro default value: 05h size: 8 bits 17.1.8 bcc?base clas s code register (smbus?d31:f3) address offset: 0bh attributes: ro default value: 0ch size: 8 bits 17.1.9 smb_base?smbus base address register (smbus?d31:f3) address offset: 20 ? 23h attribute: r/w, ro default value: 00000001h size: 32-bits bit description 7:0 reserved bit description 7:0 sub class code (scc) ? ro. 05h = sm bus serial controller bit description 7:0 base class code (bcc) ? ro. 0ch = serial controller. bit description 31:16 reserved ? ro 15:5 base address ? r/w. this field provides the 32-b yte system i/o base address for the chipset smb logic. 4:1 reserved ? ro 0 io space indicator ? ro. hardwired to 1 in dicating that the smb logic is i/o mapped. www.datasheet.co.kr datasheet pdf - http://www..net/
smbus controller registers (d31:f3) 558 datasheet 17.1.10 svid ? subsys tem vendor identi fication register (smbus?d31:f2/f4) address offset: 2ch ? 2dh attribute: ro default value: 0000h size: 16 bits lockable: no power well: core 17.1.11 sid ? subsystem id entification register (smbus?d31:f2/f4) address offset: 2eh ? 2fh attribute: r/wo default value: 00h size: 16 bits lockable: no power well: core 17.1.12 int_ln?interrupt line register (smbus?d31:f3) address offset: 3ch attributes: r/w default value: 00h size: 8 bits 17.1.13 int_pn?interrupt pin register (smbus?d31:f3) address offset: 3dh attributes: ro default value: see description size: 8 bits bit description 15:0 subsystem vendor id (svid) ? ro. the svid register, in combination with the subsystem id (sid) register, enables the operating system (os) to distinguish subsystems from each other. th e value returned by reads to this register is the same as that which was wr itten by bios into the ide svid register. note: software can write to this register only once per core well re set. writes should be done as a single 16-bit cycle. bit description 15:0 subsystem id (sid) ? ro. the sid register, in combination with the svid register, enables the operating system (os) to distinguish subsystems from each other. the value returned by reads to this register is the same as that which was written by bios into the ide sid register. note: software can write to this register only once per core well re set. writes should be done as a single 16-bit cycle. bit description 7:0 interrupt line (int_ln) ? r/w. this data is not used by the chipset. it is to communicate to software the interrupt line that the interrupt pin is connected to pirqb#. bit description 7:0 interrupt pin (int_pn) ? ro. this reflects the valu e of d31ip.smip in chipset configuration space. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 559 smbus controller registers (d31:f3) 17.1.14 hostc?host configuration register (smbus?d31:f3) address offset: 40h attribute: r/w default value: 00h size: 8 bits 17.2 smbus i/o registers bit description 7:3 reserved 2 i 2 c_en ? r/w. 0 = smbus behavior. 1 = the chipset is enabled to communicate with i 2 c devices. this will change the formatting of some commands. 1 smb_smi_en ? r/w. 0 = smbus interrupts will not generate an smi#. 1 = any source of an smb interrupt will inst ead be routed to gene rate an smi#. refer to section 5.21.4 - volume 1 (interrupts / smi#). this bit needs to be set for smbalert# to be enabled. 0 smbus host enable (hst_en) ? r/w. 0 = disable the smbus host controller. 1 = enable. the smb host cont roller interface is enable d to execute commands. the intren bit (offset smbase + 02h, bit 0) needs to be enabled for the smb host controller to interrupt or smi#. note that the smb host controller will not respond to any new requests until all inte rrupt requests have been cleared. table 17-145.smbus i/o register address map smb_base + offset mnemonic register name default type 00h hst_sts host status 00h r/wc, ro, r/wc (special) 02h hst_cnt host control 00h r/w, wo 03h hst_cmd host command 00h r/w 04h xmit_slva transmit slave address 00h r/w 05h hst_d0 host data 0 00h r/w 06h hst_d1 host data 1 00h r/w 07h host_block_db host block data byte 00h r/w 08h pec packet error check 00h r/w 09h rcv_slva receive slave address 44h r/w 0ah?0bh slv_data receive slave data 0000h ro 0ch aux_sts auxiliary status 00h r/wc, ro 0dh aux_ctl auxiliary control 00h r/w 0eh smlink_pin_ctl smlink pin control (tco compatible mode) see register description r/w, ro www.datasheet.co.kr datasheet pdf - http://www..net/
smbus controller registers (d31:f3) 560 datasheet 17.2.1 hst_sts?host status register (smbus?d31:f3) register offset: smbase + 00h attribute: r/wc, r/wc (special), ro default value: 00h size: 8-bits all status bits are set by hardware and cleared by the software writing a one to the particular bit position. writing a 0 to any bit position has no effect. 0fh smbus_pin_ctl smbus pin control see register description r/w, ro 10h slv_sts slave status 00h r/wc 11h slv_cmd slave command 00h r/w 14h notify_daddr notify device address 00h ro 16h notify_dlow notify data low byte 00h ro 17h notify_dhigh notify data high byte 00h ro table 17-145.smbus i/o register address map smb_base + offset mnemonic register name default type bit description 7 byte done status (ds) ? r/wc. 0 = software can clear this by writing a 1 to it. 1 = host controller received a byte (for bl ock read commands) or if it has completed transmission of a byte (for block write commands) when the 32 -byte buffer is not being used. note that this bit will be set, even on the last byte of the transfer. this bit is not set when transmission is due to the lan interface heartbeat. this bit has no meaning for block transf ers when the 32-byte buffer is enabled. note: when the last byte of a block message is received, the host controller will set this bit. however, it will not immediately set the intr bit (bit 1 in this register). when the interrupt handler clears the ds bit, the message is considered complete, and the host controller will then set the intr bit (and generate another interrupt). thus, for a block message of n bytes, the chipset will generate n+1 interrupts. the interrupt handler needs to be implemented to handle these cases. 6 inuse_sts ? r/wc (special). th is bit is used as semaphore among various independent software threads that may need to use the chipset?s smbus logic, and has no other effect on hardware. 0 = after a full pci reset, a read to this bit returns a 0. 1 = after the first read, subsequent reads will return a 1. a write of a 1 to this bit will reset the next read value to 0. writing a 0 to this bit has no effect. software can poll this bit until it reads a 0, and will then own the usage of the host controller. 5 smbalert_sts ? r/wc. 0 = interrupt or smi# was not generated by smbalert#. software clears this bit by writing a 1 to it. 1 = the source of the interrupt or smi# wa s the smbalert# signal. this bit is only cleared by software writing a 1 to the bit position or by rsmrst# going low. if the signal is programmed as a gp io, then this bit will not be set. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 561 smbus controller registers (d31:f3) 4 failed ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = the source of the interrupt or smi# was a failed bus transaction. this bit is set in response to the kill bit being set to terminate the host transaction. 3 bus_err ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = the source of the interrupt of smi# was a transaction collision. 2 dev_err ? r/wc. 0 = software clears this bit by writing a 1 to it. the chipset will then deassert the interrupt or smi#. 1 = the source of the interrupt or sm i# was due to one of the following: ? invalid command field, ? unclaimed cycle (host initiated), ? host device time-out error. 1 intr ? r/wc (special). this bit can only be set by termination of a command. intr is not dependent on the intren bit (offset smbase + 02h, bit 0) of the host controller register (offset 02h). it is only dependent on the term ination of the command. if the intren bit is not set, then the intr bit will be set, although the interrupt will not be generated. software can poll the in tr bit in this non-interrupt case. 0 = software clears this bit by writing a 1 to it. the chipset then deasserts the interrupt or smi#. 1 = the source of the interrupt or smi# wa s the successful completion of its last command. 0 host_busy ? ro. 0 = cleared by the chipset when th e current transaction is completed. 1 = indicates that the chipset is running a command from the host interface. no smb registers should be accessed while this bit is set, except the block data byte register. the block data byte register can be accessed when this bit is set only when the smb_cmd bits in the host co ntrol register are programmed for block command or i 2 c read command. this is nece ssary in order to check the done_sts bit. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
smbus controller registers (d31:f3) 562 datasheet 17.2.2 hst_cnt?host control register (smbus?d31:f3) register offset: smbase + 02h attribute: r/w, wo default value: 00h size: 8-bits note: a read to this register will clear th e byte pointer of the 32-byte buffer. bit description 7 pec_en ? r/w. 0 = smbus host controller does not perform the transaction with the pec phase appended. 1 = causes the host controller to perform the smbus transaction with the packet error checking phase appended. for writes, the value of the pec byte is transferred from the pec register. for reads, the pec byte is loaded in to the pec register. this bit must be written prior to the write in which the start bit is set. 6 start ? wo. 0 = this bit will always return 0 on reads. the host_busy bit in the host status register (offset 00h) can be used to identify when the chipset has finished the command. 1 = writing a 1 to this bit initiates the command described in the smb_cmd field. all registers should be setup prior to writing a 1 to this bit position. 5 last_byte ? wo. this bit is used for block read commands. 1 = software sets this bit to indicate that the next byte will be the last byte to be received for the block. this causes the chipset to send a nack (instead of an ac k) after receiving the last byte. note: once the second_to_sts bit in tco2_sts regist er (d31:f0, tcobase+6h , bit 1) is set, the last_byte bit also gets set. while the second_to_sts bit is set, the last_byte bit cannot be cleared. this preven ts the chipset from running some of the smbus commands (block read/ write, i 2 c read, block i 2 c write). www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 563 smbus controller registers (d31:f3) 4:2 smb_cmd ? r/w. the bit encoding below indicates wh ich command the chipset is to perform. if enabled, the chipset will generate an interrupt or smi# when the command has completed if the value is for a non-supported or reserved command, the ch ipset will set the device error (dev_err) status bit (offset smbase + 00h, bit 2) and generate an interrupt when the start bit is set. the chipset will perform no command, and will not operate until dev_err is cleared. 000 = quick : the slave address and read/write value (bit 0) are stored in the transmit slave address register. 001 = byte : this command uses the transmit slave address and command registers. bit 0 of the slave address register determines if this is a read or write command. 010 = byte data : this command uses the transmit slave address, command, and data0 registers. bit 0 of the slave address regi ster determines if this is a read or write command. if it is a read, the data0 register will contain the read data. 011 = word data : this command uses the transmit slav e address, command, data0 and data1 registers. bit 0 of the slave addres s register determines if this is a read or write command. if it is a read, after the command completes, the da ta0 and data1 registers will contain the read data. 100 = process call: this command uses the transmit slav e address, command, data0 and data1 registers. bit 0 of the slave address register de termines if this is a read or write command. after the command completes, the data0 and da ta1 registers will contain the read data. 101 = block : this command uses the transmit slave address, command, data0 registers, and the block data byte register. for block write, the coun t is stored in the data0 register and indicates how many bytes of data will be transferred. for block reads, the count is received and stored in the data0 register. bit 0 of the slave address register selects if this is a read or write command. for writes, data is retrieved from the firs t n (where n is equal to the specified count) addresses of the sram array. fo r reads, the data is stored in the block data byte register. 110 = i 2 c read : this command uses the transmit slave address, command, data0, data1 registers, and the block data byte register. the read data is stored in th e block data byte register. the chipset continues reading data until the nak is received. 111 = block process: this command uses the transmit slave address, command, data0 and the block data byte register. for block write, the coun t is stored in the data0 register and indicates how many bytes of data will be transferred. for block read, the count is received and stored in the data0 register. bit 0 of the slave address register always indicate a write command. for writes, data is retrieved from the first m (where m is equal to the specified count) addresses of the sram array. for reads, the data is stored in the block data byte register. note: e32b bit in the auxiliary co ntrol register must be set for this command to work. 1 kill ? r/w. 0 = normal smbus host controller functionality. 1 = kills the current host transaction taking place, sets the failed status bit, and asserts the interrupt (or smi#). this bit, once set, mu st be cleared by software to al low the smbus host controller to function normally. 0 intren ? r/w. 0 = disable. 1 = enable the generation of an interrupt or smi# upon the completion of the command. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
smbus controller registers (d31:f3) 564 datasheet 17.2.3 hst_cmd?host command register (smbus?d31:f3) register offset: smbase + 03h attribute: r/w default value: 00h size: 8 bits 17.2.4 xmit_slva?transmit slave address register (smbus?d31:f3) register offset: smbase + 04h attribute: r/w default value: 00h size: 8 bits this register is transmitted by the host co ntroller in the slave address field of the smbus protocol. 17.2.5 hst_d0?host data 0 register (smbus?d31:f3) register offset: smbase + 05h attribute: r/w default value: 00h size: 8 bits 17.2.6 hst_d1?host data 1 register (smbus?d31:f3) register offset: smbase + 06h attribute: r/w default value: 00h size: 8 bits bit description 7:0 this 8-bit field is transmitte d by the host controller in the command field of the smbus protocol during the execution of any command. bit description 7:1 address ? r/w. this field provides a 7-bit address of the targeted slave. 0 rw ? r/w. direction of the host transfer. 0 = write 1 = read bit description 7:0 data0/count ? r/w. this field contains the 8-bit data sent in the data0 field of the smbus protocol. for block write commands, this register reflects the number of bytes to transfer. this register should be progra mmed to a value between 1 and 32 for block counts. a count of 0 or a count above 32 will result in unpredicta ble behavior. the host controller does not check or log invalid block counts. bit description 7:0 data1 ? r/w. this 8-bit register is transm itted in the data1 field of the smbus protocol during the execution of any command. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 565 smbus controller registers (d31:f3) 17.2.7 host_block_db?host bl ock data byte register (smbus?d31:f3) register offset: smbase + 07h attribute: r/w default value: 00h size: 8 bits 17.2.8 pec?packet error check (pec) register (smbus?d31:f3) register offset: smbase + 08h attribute: r/w default value: 00h size: 8 bits bit description 7:0 block data (bdta) ? r/w. this is either a register, or a pointer into a 32-byte block array, depending upon whether the e32b bit is set in the auxiliary control register. when the e32b bit (offset smbase + 0dh, bit 1) is cleared, this is a register containing a byte of data to be sent on a block writ e or read from on a bl ock read, just as it behaved on the ich3. when the e32b bit is set, reads and writes to this register are us ed to access the 32- byte block data storage array. an internal index pointer is used to address the array, which is reset to 0 by readin g the hctl register (offset 02h). the index pointer then increments automatically upon each access to this register. the transfer of block data into (read) or out of (write) this storage array during an smbus transaction always starts at index address 0. when the e2b bit is set, for writes, software will write up to 32-bytes to this register as part of the setup for the co mmand. after the host controller has sent the address, command, and byte count fields, it will send the bytes in the sram pointed to by this register. when the e2b bit is cleared for writes, software will place a single by te in this register. after the host controller has sent the address, command, an d byte count fi elds, it will send the byte in this register. if there is more data to send, software will write the next series of bytes to the sram pointed to by th is register and clear the done_sts bit. the controller will then send th e next byte. during the time between the last byte being transmitted to the next byte being transmitted, the controller will insert wait-states on the interface. when the e2b bit is set for reads, after rece iving the byte count into the data0 register, the first series of data bytes go into the sr am pointed to by this register. if the byte count has been exhausted or the 32-byte sr am has been filled, the controller will generate an smi# or interrupt (depending on configuration) and set the done_sts bit. software will then read the data. during th e time between when the last byte is read from the sram to when the done_sts bit is cleared, the controller will insert wait- states on the interface. bit description 7:0 pec_data ? r/w. this 8-bit register is written with the 8-bit crc valu e that is used as the smbus pec data prior to a write transa ction. for read transactions, the pec data is loaded from the smbus into this register an d is then read by software. software must ensure that the inuse_sts bit is properly ma intained to avoid having this field over- written by a write transaction following a read transaction. www.datasheet.co.kr datasheet pdf - http://www..net/
smbus controller registers (d31:f3) 566 datasheet 17.2.9 rcv_slva?receive slave address register (smbus?d31:f3) register offset: smbase + 09h attribute: r/w default value: 44h size: 8 bits lockable: no power well: resume 17.2.10 slv_data?receive slave data register (smbus?d31:f3) register offset: smbase + 0ah?0bh attribute: ro default value: 0000h size: 16 bits lockable: no power well: resume this register contains the 16-bit data value written by the external smbus master. the processor can then read the value from this re gister. this register is reset by rsmrst#, but not pltrst# . 17.2.11 aux_sts?auxiliary stat us register (smbus?d31:f3) register offset: smbase + 0ch attribute: r/wc, ro default value: 00h size: 8 bits lockable: no power well: resume . bit description 7 reserved 6:0 slave_addr ? r/w. this field is the slave addres s that the chipset decodes for read and write cycles. the default is not 0, so the smbus slave interface can respond even before the processor comes up (or if the proces sor is dead). this register is cleared by rsmrst#, but not by pltrst#. bit description 15:8 data message byte 1 (data_msg1) ? ro. see section 5.21.7 - volume 1 for a discussion of this field. 7:0 data message byte 0 (data_msg0) ? ro. see section 5.21.7 - volume 1 for a discussion of this field. bit description 7:2 reserved 1 smbus tco mode (stco) ? ro. this bit reflects the st rap setting of tco compatible mode vs. advanced tco mode. 0 = chipset is in the compatible tco mode. 1 = chipset is in the advanced tco mode. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 567 smbus controller registers (d31:f3) 17.2.12 aux_ctl?auxiliary cont rol register (smbus?d31:f3) register offset: smbase + 0dh attribute: r/w default value: 00h size: 8 bits lockable: no power well: resume . 17.2.13 smlink_pin_ctl?smlink pin control register (smbus?d31:f3) register offset: smbase + 0eh attribute: r/w, ro default value: see below size: 8 bits note: this register is in the resume well and is reset by rsmrst#. this register is only applicable in the tco compatible mode. 0 crc error (crce) ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set if a received message contai ned a crc error. when this bit is set, the derr bit of the host status register will also be set. this bit will be set by the controller if a software abort occurs in the middle of the crc portion of the cycle or an abort happens after the chipset has receiv ed the final data bit transmitted by an external slave. bit description bit description 7:2 reserved 1 enable 32-byte buffer (e32b) ? r/w. 0 = disable. 1 = enable. when set, the host block data register is a pointer into a 32-byte buffer, as opposed to a single re gister. this enables the block commands to transfer or receive up to 32-bytes before the ch ipset generates an interrupt. 0 automatically append crc (aac) ? r/w. 0 = chipset will not automa tically append the crc. 1 = the chipset will automatically append the crc. this bit must no t be changed during smbus transactions or undetermined behavior will result. it should be programmed only once during the li fetime of the function. www.datasheet.co.kr datasheet pdf - http://www..net/
smbus controller registers (d31:f3) 568 datasheet 17.2.14 smbus_pin_ctl?smbu s pin control register (smbus?d31:f3) register offset: smbase + 0fh attribute: r/w, ro default value: see below size: 8 bits note: this register is in the resume well and is reset by rsmrst#. bit description 7:3 reserved 2 smlink_clk_ctl ? r/w. 0 = chipset will drive the smlink0 pin low, independent of what the other smlink logic would otherwise indica te for the smlink0 pin. 1 = the smlink0 pin is not overdriven low. the other smlink logic controls the state of the pin. (default) 1 smlink1_cur_sts ? ro. this read-only bit has a de fault value that is dependent on an external signal level. th is pin returns the value on the smlink1 pin. this allows software to read the current state of the pin. 0 = low 1 = high 0 smlink0_cur_sts ? ro. this read-only bit has a de fault value that is dependent on an external signal level. th is pin returns the value on the smlink0 pin. this allows software to read the current state of the pin. 0 = low 1 = high bit description 7:3 reserved 2 smbclk_ctl ? r/w. 1 = the smbclk pin is not overdriven low. the other smbus logic controls the state of the pin. 0 = chipset drives the smbclk pin low, independent of wh at the other smb logic would otherwise indicate for th e smbclk pin. (default) 1 smbdata_cur_sts ? ro. this read-only bit has a default value that is dependent on an external signal level. this pin returns the value on the smbdata pin. this allows software to read the cu rrent state of the pin. 0 = low 1 = high 0 smbclk_cur_sts ? ro. this read-only bit has a de fault value that is dependent on an external signal level. th is pin returns the value on th e smbclk pin. this allows software to read the cu rrent state of the pin. 0 = low 1 = high www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 569 smbus controller registers (d31:f3) 17.2.15 slv_sts?slave status register (smbus?d31:f3) register offset: smbase + 10h attribute: r/wc default value: 00h size: 8 bits note: this register is in the resume well and is reset by rsmrst#. all bits in this register are implemented in the 64 khz clock domain. therefore, software must poll this register until a write takes effect before assuming that a write has completed internally. 17.2.16 slv_cmd?slave comman d register (smbus?d31:f3) register offset: smbase + 11h attribute: r/w default value: 00h size: 8 bits note: this register is in the resume well and is reset by rsmrst#. bit description 7:1 reserved 0 host_notify_sts ? r/wc. the chipset sets this bit to a 1 when it has completely received a successful host notify command on the smlink pins. software reads this bit to determine that the source of the interru pt or smi# was the reception of the host notify command. software clears this bit after reading any information needed from the notify address and data re gisters by writing a 1 to this bit. note that the chipset will allow the notify address and data registers to be over-written once this bit has been cleared. when this bit is 1, the chipse t will nack the first byte (host address) of any new ?host notify? commands on the smlink . writing a 0 to this bit has no effect. bit description 7:2 reserved 2 smbalert_dis ? r/w. 0 = allows the generation of the interrupt or smi#. 1 = software sets this bit to block the generation of the interrupt or smi# due to the smbalert# source. this bit is logically inverted and anded with the smbalert_sts bit (offset smbase + 00h, bit 5). the resulting sign al is distributed to the smi# and/or interrupt generation logic. this bi t does not effect the wake logic. 1 host_notify_wken ? r/w. software sets this bit to 1 to enable the reception of a host notify command as a wake event. when enabled this event is ?or?ed in with the other smbus wake events an d is reflected in the smb_ wak_sts bit of the general purpose event 0 status register. 0 = disable 1 = enable www.datasheet.co.kr datasheet pdf - http://www..net/
smbus controller registers (d31:f3) 570 datasheet 17.2.17 notify_daddr?notify device address register (smbus?d31:f3) register offset: smbase + 14h attribute: ro default value: 00h size: 8 bits note: this register is in the resume well and is reset by rsmrst#. 17.2.18 notify_dlow?notify data low byte register (smbus?d31:f3) register offset: smbase + 16h attribute: ro default value: 00h size: 8 bits note: this register is in the resume well and is reset by rsmrst#. 0 host_notify_intren ? r/w. software sets this bit to 1 to enable the generation of interrupt or smi# when host_notify_sts (offset smbase + 10h, bit 0) is 1. this enable does not affect the se tting of the host_notify_sts bit. when the interrupt is generated, either pirqb# or smi# is generated, depending on the value of the smb_smi_en bit (d31:f3:40h, bit 1). if the host_notify_sts bit is set when this bit is written to a 1, then the interrupt (or smi#) will be generated. the interrupt (or smi#) is logically generated by and?ing the sts and intren bits. 0 = disable 1 = enable bit description bit description 7:1 device_address ? ro. this field contains the 7-bi t device address received during the host notify protocol of the smbus 2.0 sp ecification. software should only consider this field valid when the host_notify_sts bit (d31:f3:smbase +10, bit 0) is set to 1. 0 reserved bit description 7:0 data_low_byte ? ro. this field contains the firs t (low) byte of data received during the host notify protocol of the smbu s 2.0 specification. so ftware should only consider this field valid when the host_n otify_sts bit (d31:f3: smbase +10, bit 0) is set to 1. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 571 smbus controller registers (d31:f3) 17.2.19 notify_dhigh?notify data high byte register (smbus?d31:f3) register offset: smbase + 17h attribute: ro default value: 00h size: 8 bits note: this register is in the resume well and is reset by rsmrst#. bit description 7:0 data_high_byte ? ro. this field contains the second (high) byte of data received during the host notify protocol of the smbu s 2.0 specification. software should only consider this field valid when the host_n otify_sts bit (d31:f3: smbase +10, bit 0) is set to 1. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 572 datasheet 18 intel hd audio controller registers (d27:f0) the intel hd audio controller resides in pci device 27, function 0 on bus 0. this function contains a set of dma engines that are used to move samples of digitally encoded data between system memory and external codecs. note: all registers in this function (including me mory-mapped registers) must be addressable in byte, word, and d-word quantities. th e software must always make register accesses on natural boundaries (i.e. d-word accesses must be on d-word boundaries; word accesses on word boundaries, etc.) in addition, the memory-mapped register space must not be accessed with the lock semantic exclusive-access mechanism. if software attempts exclusive-access mechanis ms to the intel high definition audio memory-mapped space, the results are undefined. note: users interested in providing feedback on the intel high definition audio specification or planning to implement the intel high definition audio specification into a future product will need to execute the intel hd audio specification developer?s agreement . for more information, contact nextgenaudio@intel.com. 18.1 intel hd audio pc i configuration space (intel hd audio? d27:f0) note: address locations that are not shown should be treated as reserved . table 18-146.intel hd audi o pci register address map (intel hd audio d27:f0) (sheet 1 of 3) offset mnemonic register name default access 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 rid revision identification see register description. ro 09h pi programming interface 00h ro 0ah scc sub class code 03h ro 0bh bcc base class code 04h ro 0ch cls cache line size 00h r/w 0dh lt latency timer 00h ro 0eh headtyp header type 00h ro 10h?13h hdbarl intel hd audio lower base address (memory) 00000004h r/w, ro www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 573 intel hd audio controller registers (d27:f0) 14h?17h hdbaru intel hd audio upper base address (memory) 00000000h r/w 2ch?2dh svid subsystem vendor identification 0000h r/wo 2eh?2fh sid subsystem identification 0000h r/wo 34h capptr capability list pointer 50h ro 3ch intln interrupt line 00h r/w 3dh intpn interrupt pin see register description ro 40h hdctl intel high definiti on audio control 00h r/w, ro 44h tcsel traffic class select 00h r/w 4c-4dh - reserved 0000h ro 50h?51h pid pci power management capability id 6001h ro 52h?53h pc power manageme nt capabilities c842 ro 54h?57h pcs power management control and status 00000000h r/w, ro, r/wc 60h?61h mid msi capability id 7005h ro 62h?63h mmc msi message control 0080h r/w, ro 64h?67h mmla msi message lower address 00000000h r/w, ro 68h?6bh mmua smi message upper address 00000000h r/w 6ch?6dh mmd msi message data 0000h r/w 70h?71h pxid pci express* capability identifiers 0010h ro 72h?73h pxc pci express capabilities 0091h ro 74h?77h devcap device capabilities 00000000h ro, r/wo 78h?79h devc device control 0800h r/w, ro 7ah?7bh devs device status 0010h ro 100h?103h vccap virtual channel enhanced capability header 13010002h ro 104h?107h pvccap1 port vc capability register 1 00000001h ro 108h?10bh pvccap2 port vc capability register 2 00000000h ro 10ch?10d pvcctl port vc control 0000h ro 10eh?10fh pvcsts port vc status 0000h ro 110h?103h vc0cap vc0 resource capability 00000000h ro 114h?117h vc0ctl vc0 resource control 800000ffh r/w, ro 11ah?11bh vc0sts vc0 resource status 0000h ro 11ch?11fh vcicap vci resource capability 00000000h ro 120h?123h vcictl vci resource control 00000000h r/w, ro 126h?127h vcists vci resource status 0000h ro 130h?133h rccap root complex link declaration enhanced capability header 00010005h ro 134h?137h esd element self description 0f000100h ro table 18-146.intel hd audio pci register address map (intel hd audio d27:f0) (sheet 2 of 3) offset mnemonic register name default access www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 574 datasheet 18.1.1 vid?vendor identi fication register (intel hd audio controller?d27:f0) offset: 00h-01h attribute: ro default value: 8086hsize:16 bits 18.1.2 did?device iden tification register (intel hd audio controller?d27:f0) offset address: 02h?03h attribute: ro default value: see bit description size: 16 bits 18.1.3 pcicmd?pci command register (intel hd audio controller?d27:f0) offset address: 04h?05h attribute: r/w, ro default value: 0000h size: 16 bits 140h?143h l1desc link 1 description 00000001h ro 148h?14bh l1addl link 1 lower address see register description ro 14ch?14fh l1addu link 1 upper address 00000000h ro table 18-146.intel hd audi o pci register address map (intel hd audio d27:f0) (sheet 3 of 3) offset mnemonic register name default access 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. t bit description 15:11 reserved 10 interrupt disable (id) ? r/w. 0= the intx# signals may be asserted. 1= the intel hd audio controller?s intx# signal will be de-asserted note: this bit does not affect the generation of msis. 9 fast back to back enable (fbe) ? ro. not implemented. hardwired to 0. 8 serr# enable (serr_en) ? r/w. serr# is not generated by the chipset intel high definition audio controller. 7 wait cycle control (wcc) ? ro. not implemented. hardwired to 0. 6 parity error response (per) ? ro. not implemented. hardwired to 0. 5 vga palette snoop (vps) . not implemented. hardwired to 0. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 575 intel hd audio controller registers (d27:f0) 18.1.4 pcists?pci status register (intel hd audio controller?d27:f0) offset address: 06h?07h attribute: ro, r/wc default value: 0010h size: 16 bits 4 memory write and invalidate enable (mwie) ? ro. not im plemented. hardwired to 0. 3 special cycle enable (sce). no t implemented. hardwired to 0. 2 bus master enable (bme) ? r/w. controls standard pci express* bus mastering capabilities for memory and i/o, reads and wr ites. note that this bit also controls msi generation since msis are essentially memory writes. 0 = disable 1 = enable 1 memory space enable (mse) ? r/w. enables memory space addresses to the intel high definition audio controller. 0 = disable 1 = enable 0 i/o space enable (iose)?ro. hardwired to 0 since the intel hi gh definition audio controller does not implement i/o space. bit description bit description 15 detected parity error (dpe) ? ro. not implemente d. hardwired to 0. 14 serr# status (serrs) ? ro. not implemented. hardwired to 0. 13 received master abort (rma) ? r/wc. software clears this bit by writing a 1 to it. 0 = no master abort received. 1 = the intel hd audio controller sets this bit when, as a bus master, it receives a master abort. when set, th e intel high definition audi o controller clears the run bit for the channel that received the abort. 12 received target abort (rta) ? ro. not implemented. hardwired to 0. 11 signaled target abort (sta) ? ro. not implemented. hardwired to 0. 10:9 devsel# timing status (dev_sts) ? ro. does not apply. hardwired to 0. 8 data parity error detected (dped) ? ro. not implemented. hardwired to 0. 7 fast back to back capable (fb2bc) ? ro. does not apply. hardwired to 0. 6 reserved . 5 66 mhz capable (66mhz_cap) ? ro. does not apply. hardwired to 0. 4 capabilities list (cap_list) ? ro. hardwired to 1. indicates that the controller contains a capabilities poin ter list. the first item is pointed to by looking at configuration offset 34h. 3 interrupt status (is) ? ro. 0 = this bit is 0 after th e interrupt is cleared. 1 = this bit is 1 when the intx# is asserted. note that this bit is not set by an msi. 2:0 reserved . www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 576 datasheet 18.1.5 rid?revision iden tification register (intel hd audio controller?d27:f0) offset: 08h attribute: ro default value: see bit description size: 8 bits 18.1.6 pi?programming interface register (intel hd audio controller?d27:f0) offset: 09h attribute: ro default value: 00h size: 8 bits 18.1.7 scc?sub class code register (intel hd audio controller?d27:f0) address offset: 0ah attribute: ro default value: 03h size: 8 bits 18.1.8 bcc?base class code register (intel hd audio controller?d27:f0) address offset: 0bh attribute: ro default value: 04h size: 8 bits 18.1.9 cls?cache line size register (intel hd audio controller?d27:f0) address offset: 0ch attribute: r/w default value: 00h size: 8 bits bit description 7:0 revision id ? ro. bit description 7:0 programming interface ? ro. bit description 7:0 sub class code (scc) ? ro. 03h = audio device bit description 7:0 base class code (bcc) ? ro. 04h = multimedia device bit description 7:0 cache line size ? r/w. implemented as r/ w register, but has no functional impact to the chipset www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 577 intel hd audio controller registers (d27:f0) 18.1.10 lt?latency timer register (intel hd audio controller?d27:f0) address offset: 0dh attribute: ro default value: 00h size: 8 bits 18.1.11 headtyp?header type register (intel hd audio controller?d27:f0) address offset: 0eh attribute: ro default value: 00h size: 8 bits 18.1.12 hdbarl?intel hd audio lower base address register (intel hd audio?d27:f0) address offset: 10h-13h attribute: r/w, ro default value: 00000004h size: 32 bits 18.1.13 hdbaru?intel hd audio upper base address register (intel hd audio controller?d27:f0) address offset: 14h-17h attribute: r/w default value: 00000000h size: 32 bits bit description 7:0 latency timer ? ro. hardwired to 00 bit description 7:0 header type ? ro. hardwired to 00. bit description 31:14 lower base address (lba) ? r/w. this field contains th e base address for the intel hd audio controller?s memory mapped configur ation registers; 16 kb are requested by hardwiring bits 13:4 to 0s. 13:4 ro. hardwired to 0s 3 prefetchable (pref) ? ro. hardwired to 0 to indicate that this bar is not prefetchable. 2:1 address range (addrng) ? ro. hardwired to 10b, indicating that this bar can be located anywhere in 64-bit address space. 0 space type (sptyp) ? ro. hardwired to 0. indicates this bar is located in memory space. bit description 31:0 upper base address (uba) ? r/w. this field provides th e upper 32 bits of the base address for the intel hd au dio controller?s memory ma pped configuration registers. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 578 datasheet 18.1.14 svid?subsystem vendor identification register (intel hd audio controller?d27:f0) address offset: 2ch?2dh attribute: r/wo default value: 0000h size: 16 bits the svid register, in combination with the subsystem id register (d27:f0:2eh), enable the operating environment to distinguish one audio subsystem from the other(s). this register is implemented as write-once register. once a value is written to it, the value can be read back. any subseq uent writes will have no effect. this register is not affected by the d3 hot to d0 transition. 18.1.15 sid?subsystem iden tification register (intel hd audio controller?d27:f0) address offset: 2eh ? 2fh attribute: r/wo default value: 0000h size: 16 bits the sid register, in combination with the subsystem vendor id register (d27:f0:2ch) make it possible for the operating environment to distinguish one audio subsystem from the other(s). this register is implemented as write-once register. once a value is written to it, the value can be read back. any subseq uent writes will have no effect. this register is not affected by the d3 hot to d0 transition. t 18.1.16 capptr?capabilities poin ter register (audio?d30:f2) address offset: 34h attribute: ro default value: 50h size: 8 bits this register indicates the offset for the capability pointer. bit description 15:0 subsystem vendor id ? r/wo. bit description 15:0 subsystem id ? r/wo. bit description 7:0 capabilities pointer (cap_ptr) ? ro. this field indicates that the first capability pointer offset is offset 50h (power management capability) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 579 intel hd audio controller registers (d27:f0) 18.1.17 intln?interrup t line register (intel hd audio controller?d27:f0) address offset: 3ch attribute: r/w default value: 00h size: 8 bits 18.1.18 intpn?interrupt pin register (intel hd audio controller?d27:f0) address offset: 3dh attribute: ro default value: see description size: 8 bits 18.1.19 hdctl?intel hd audio control register (intel hd audio controller?d27:f0) address offset: 40h attribute: r/w, ro default value: 00h size: 8 bits bit description 7:0 interrupt line (int_ln) ? r/w. this data is not used by the chipset. it is used to communicate to software the interrupt line that the interrupt pin is connected to. bit description 7:4 reserved . 3:0 interrupt pin ? ro. this reflects the value of d27ip.zip (chipset config registers:offset 3110h: bits 3:0). bit description 7:4 reserved . 3 bitclk detect cl ear (clkdetclr) ? r/w. 0 = lock detect circuit is operational and maybe enabled. 1 = writing a 1 to this bit clears bit 1 (clk det#) in this register . clkdet# bit remains clear when this bit is set to 1. note: this bit is not affected by the d3 hot to d0 transition. 2 bitclk detect en able (clkdeten) ? r/w. 0 = latches the current state of bit 1 (clkdet#) in this register 1 = enables the clock detection circuit note: this bit is not affected by the d3 hot to d0 transition. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 580 datasheet 18.1.20 tcsel?traffic class select register (intel hd audio controller?d27:f0) address offset: 44h attribute: r/w default value: 00h size: 8 bits this register assigned the value to be placed in the tc field. corb and rirb data will always be assigned tc0. 1 bitclk detected inverted (clkdet#) ? ro. this bit is modified by hardware. it is set to 0 when the chipset detects that the bitclk is toggling, indicating the presence of an ac?97 codec on the link. notes: 1. bit 2 (clkdeten) and bit 3 (clkdetclr) in this register control the operation of this bit and must be manipulated corre ctly in order to get a valid clkdet# indicator. 2. this bit is not affected by the d3hot to d0 transition. 0 intel hd audio signal mode ? r/w. this bit selects the intel high definition audio signals. 0 = reserved 1 = intel high definition audio mode is selected notes: 1. this bit has no effect on the visibility of the intel high defi nition audio function configuration space. 2. this bit is in the resume well and only clear on a power-on re set. software must not makes assumptions about the reset state of this bit and must set it appropriately. bit description bit description 7:3 reserved . 2:0 intel hd audio traffic cl ass assignment (tcsel) ? r/w. this regi ster assigns the value to be placed in the traffic class fi eld for input data, output data, and buffer descriptor transactions. 000 = tc0 001 = tc1 010 = tc2 011 = tc3 100 = tc4 101 = tc5 110 = tc6 111 = tc7 note: these bits are not reset on d3 hot to d0 transition; however, they are reset by pltrst#. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 581 intel hd audio controller registers (d27:f0) 18.1.21 pid?pci power management capability id register (intel hd audio controller?d27:f0) address offset: 50h?51h attribute: ro default value: 6001h size: 16 bits 18.1.22 pc?power management capabilitie s register (intel hd audio controller?d27:f0) address offset: 52h?53h attribute: ro default value: c842h size: 16 bits 18.1.23 pcs?power management co ntrol and status register (intel hd audio controller?d27:f0) address offset: 54h?57h attribute: ro, r/w, r/wc default value: 00000000h size: 32 bits bit description 15:8 next capability (next) ? ro. hardwired to 60h. points to the next capability structure (msi) 7:0 cap id (cap) ? ro. hardwired to 01h. indicates th at this pointer is a pci power management capability. bit description 15:11 pme support ? ro. hardwired to 11001b. indicates pme# can be generated from d3 and d0 states. 10 d2 support ? ro. hardwired to 0. indicates that d2 state is not supported. 9 d1 support ?ro. hardwired to 0. indicates that d1 state is not supported. 8:6 aux current ? ro. hardwired to 001b. reports 55 ma maximum suspend well current required when in the d3 cold state. 5 device specific initialization (dsi) ? ro. hardwired to 0. in dicates that no device specific initialization is required. 4 reserved 3 pme clock (pmec) ? ro. does not apply. hardwired to 0. 2:0 version ? ro. hardwired to 010b. indicates su pport for version 1.1 of the pci power management specification. bit description 31:24 data ? ro. does not apply. hardwired to 0. 23 bus power/clock control enable ? ro. does not apply. hardwired to 0. 22 b2/b3 support ? ro. does not apply. hardwired to 0. 21:16 reserved . www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 582 datasheet 18.1.24 mid?msi capability id register (intel hd audio controller?d27:f0) address offset: 60h?61h attribute: ro default value: 7005h size: 16 bits 15 pme status (pmes) ? r/wc. 0 = software clears the bit by writing a 1 to it. 1 = this bit is set when the intel hd audio controller would normally assert the pme# signal independent of the state of the pme_en bit (bit 8 in this register) this bit is in the resume well and only clea red on a power-on rese t. software must not make assumptions about the reset state of this bit and must se t it appropriately. 14:9 reserved 8 pme enable (pmee) ? r/w. 0 = disable 1 = when set and if corresponding pmes also set, the intel high definition audio controller sets the ac97_sts bit in th e gpe0_sts register (pmbase +28h). this bit is in the resume well and only clea red on a power-on rese t. software must not make assumptions about the reset state of this bit and must se t it appropriately. 7:2 reserved 1:0 power state (ps) ? r/w. this field is used both to determine the current power state of the intel high definition audio co ntroller and to set a new power state. 00 = d0 state 11 = d3 hot state others = reserved notes: 1. if software attempts to write a value of 01b or 10b in to this field, the write operation must complete normally; howeve r, the data is discarded and no state change occurs. 2. when in the d3 hot states, the intel high definition audio controller?s configuration space is available, bu t the i/o and memory space are not. additionally, inte rrupts are blocked. 3. when software changes this value from d3 hot state to the d0 state, an internal warm (soft) reset is gene rated, and software must re-initialize the function. bit description bit description 15:8 next capability (next) ? ro. hardwired to 70h. points to the pci express* capability structure. 7:0 cap id (cap) ? ro. hardwired to 05h. indicates th at this pointer is a msi capability www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 583 intel hd audio controller registers (d27:f0) 18.1.25 mmc?msi messag e control register (intel hd audio controller?d27:f0) address offset: 62h?63h attribute: ro, r/w default value: 0080h size: 16 bits 18.1.26 mmla?msi message lower address register (intel hd audio controller?d27:f0) address offset: 64h?67h attribute: ro, r/w default value: 00000000h size: 32 bits 18.1.27 mmua?msi message upper address register (intel hd audio controller?d27:f0) address offset: 68h?6bh attribute: r/w default value: 00000000h size: 32 bits 18.1.28 mmd?msi message data register (intel hd audio controller?d27:f0) address offset: 6ch?6dh attribute: r/w default value: 0000h size: 16 bits bit description 15:8 reserved 7 64b address capability (64add) ? ro. hardwired to 1 indicating the ability to generate a 64-bit message address 6:4 multiple message enable (mme) ? ro. normally this is a r/w register. however, since only 1 message is supported, these bits are hardwired to 000 = 1 message. 3:1 multiple message capable (mmc) ? ro. hardwired to 0 indicating request for 1 message. 0 msi enable (me) ? r/w. 0 = an msi may not be generated 1 = an msi will be generated instead of an intx signal. bit description 31:2 message lower address (mla) ? r/w. lower address used for msi message. 1:0 reserved . bit description 31:0 message upper address (mua) ? r/w. upper 32-bits of address used for msi message. bit description 15:0 message data (md) ? r/w. data used for msi message. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 584 datasheet 18.1.29 pxid?pci express* capability id register (intel hd audio controller?d27:f0) address offset: 70h-71h attribute: ro default value: 0010h size: 16 bits 18.1.30 pxc?pci express* capabilities register (intel hd audio controller?d27:f0) address offset: 72h?73h attribute: ro default value: 0091h size: 16 bits 18.1.31 devcap?device ca pabilities register (intel hd audio controller?d27:f0) address offset: 74h?77h attribute: r/wo, ro default value: 00000000h size: 32 bits bit description 15:8 next capability (next) ? ro. hardwired to 0. indicates th at this is the last capability structure in the list. 7:0 cap id (cap) ? ro. hardwired to 10h. indicates th at this pointer is a pci express* capability structure bit description 15:14 reserved 13:9 interrupt message number (imn) ? ro. hardwired to 0. 8 slot implemented (si) ? ro. hardwired to 0. 7:4 device/port type (dpt) ? ro. hardwired to 1001b. indi cates that this is a root complex integrated endpoint device. 3:0 capability version (cv) ? ro. hardwired to 0001b. indicates version #1 pci express capability bit description 31:28 reserved 27:26 captured slot power limit scale (spls) ? ro. hardwired to 0. 25:18 captured slot power limit value (splv) ? ro. hardwired to 0. 17:15 reserved 14 power indicator present ? ro. hardwired to 0. 13 attention indicator present ? ro. hardwired to 0. 12 attention button present ? ro. hardwired to 0. 11:9 endpoint l1 acceptable latency ? r/wo. 8:6 endpoint l0s acceptable latency ? r/wo. 5 extended tag field support ? ro. hardwired to 0. indi cates 5-bit tag field support 4:3 phantom functions supported ? ro. hardwired to 0. indicates that phantom functions are not supported www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 585 intel hd audio controller registers (d27:f0) 18.1.32 devc?device control register (intel hd audio controller?d27:f0) address offset: 78h?79h attribute: r/w, ro default value: 0800h size: 16 bits 18.1.33 devs?device status register (intel hd audio controller?d27:f0) address offset: 7ah?7bh attribute: ro default value: 0010h size: 16 bits 2:0 max payload size supported ? ro. hardwired to 0. indicates 128-b maximum payload size capability bit description bit description 15 reserved 14:12 max read request size ? ro. hardwired to 0 enabling 128b maximum read request size. 11 no snoop enable (nsnpen) ? r/w. 0 = the intel hd audio controller will no t set the no snoop bit. in this case, isochronous transfers will not use vc1 (vci) even if it is enabled since vc1 is not snooped. isochronous tr ansfers will use vc0. 1 = the intel high definition audio controller is permitted to set th e no snoop bit in the requester attributes of a bus master transa ction. in this case, vc0 or vc1 may be used for isochronous transfers. note: this bit is not reset on d3 hot to d0 transition; however, it is reset by pltrst#. 10 auxiliary power enable ? ro. hardwired to 0, indicati ng that intel high definition audio device does not draw aux power 9 phantom function enable ? ro. hardwired to 0 disabling phantom functions. 8 extended tag field enable ? ro. hardwired to 0 enabling 5-bit tag. 7:5 max payload size ? ro. hardwired to 0 indicating 128b. 4 enable relaxed ordering ? ro. hardwired to 0 disabling relaxed ordering. 3 unsupported request reporting enable ? ro. not implemented. hardwired to 0. 2 fatal error reporting enable ? ro. not implemente d. hardwired to 0. 1 non-fatal error reporting enable ? ro. not implemented. hardwired to 0. 0 correctable error reporting enable ? ro. not implemente d. hardwired to 0. bit description 15:6 reserved 5 transactions pending ? ro. 0 = indicates that completions for all no n-posted requests ha ve been received. 1 = indicates that intel hd au dio controller has issued non-posted requests that have not been completed. 4 aux power detected ? ro. hardwired to 1 indicating the device is connected to resume power. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 586 datasheet 18.1.34 vccap?virtual channel enhanced capability header (intel hd audio controller?d27:f0) address offset: 100h?103h attribute: ro default value: 13010002h size: 32 bits 18.1.35 pvccap1?port vc capability register 1 (intel hd audio controller?d27:f0) address offset: 104h?107h attribute: ro default value: 00000001h size: 32 bits 3 unsupported request detected ? ro. not implemented. hardwired to 0. 2 fatal error detected ? ro. not implemente d. hardwired to 0. 1 non-fatal error detected ? ro. not implemented. hardwired to 0. 0 correctable error detected ? ro. not implemented. hardwired to 0. bit description bit description 31:20 next capability offset ? ro. hardwired to 130h. points to the next capability header that is the root complex link decl aration enhanced capability header. 19:16 capability version ? ro. hardwired to 1h. 15:0 pci express* exte nded capability ? ro. hardwired to 0002h. bit description 31:12 reserved . 11:10 port arbitration table entry size ? ro. hardwired to 0 sinc e this is an endpoint device. 9:8 reference clock ? ro. hardwired to 0 since th is is an endpoint device. 7 reserved . 6:4 low priority extended vc count ? ro. hardwired to 0. in dicates that only vc0 belongs to the low priority vc group. 3 reserved . 2:0 extended vc count ? ro. hardwired to 001b. indicates that 1 extended vc (in addition to vc0) is supported by the intel hd audio controller. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 587 intel hd audio controller registers (d27:f0) 18.1.36 pvccap2 ? port vc capability register 2 (intel hd audio controller?d27:f0) address offset: 108h?10bh attribute: ro default value: 00000000h size: 32 bits 18.1.37 pvcctl ? port vc control register (intel hd audio controller?d27:f0) address offset: 10ch?10dh attribute: ro default value: 0000h size: 16 bits 18.1.38 pvcsts?port vc status register (intel hd audio controller?d27:f0) address offset: 10eh-10fh attribute: ro default value: 0000h size: 16 bits bit description 31:24 vc arbitration table offset ? ro. hardwired to 0 indicating that a vc arbitration table is not present. 23:8 reserved . 7:0 vc arbitration capability ? ro. hardwired to 0. these bits are not applicable since the intel hd audio controller reports a 0 in the low priority extended vc count bits in the pvccap1 register. bit description 15:4 reserved . 3:1 vc arbitration select ? ro. hardwired to 0. normally these bits are r/w. however, these bits are not applicable since the intel hd audio controller reports a 0 in the low priority extended vc count bits in the pvccap1 register. 0 load vc arbitration table ? ro. hardwired to 0 since an arbitration table is not present. bit description 15:1 reserved . 0 vc arbitration table status ? ro. hardwired to 0 since an arbitration table is not present. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 588 datasheet 18.1.39 vc0cap?vc0 resour ce capability register (intel hd audio controller?d27:f0) address offset: 110h?113h attribute: ro default value: 00000000h size: 32 bits 18.1.40 vc0ctl?vc0 resource control register (intel hd audio controller?d27:f0) address offset: 114h?117h attribute: r/w, ro default value: 800000ffh size: 32 bits bit description 31:24 port arbitratio n table offset ? ro. hardwired to 0 since th is field is not valid for endpoint devices. 23 reserved . 22:16 maximum time slots ? ro. hardwired to 0 since this field is not valid for endpoint devices. 15 reject snoop transactions ? ro. hardwired to 0 since this field is not valid for endpoint devices. 14 advanced packet switching ? ro. hardwired to 0 since th is field is not valid for endpoint devices. 13:8 reserved . 7:0 port arbitratio n capability ? ro. hardwired to 0 since this field is not valid for endpoint devices. bit description 31 vc0 enable ? ro. hardwired to 1 for vc0. 30:27 reserved . 26:24 vc0 id ? ro. hardwired to 0 since the first vc is always assigned as vc0. 23:20 reserved . 19:17 port arbitration select ? ro. hardwired to 0 since this field is not valid for endpoint devices. 16 load port arbitration table ? ro. hardwired to 0 since this field is not valid for endpoint devices. 15:8 reserved . 7:0 tc/vc0 map ? r/w, ro. bit 0 is hardwired to 1 si nce tc0 is always mapped vc0. bits [7:1] are implemented as r/w bits. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 589 intel hd audio controller registers (d27:f0) 18.1.41 vc0sts?vc0 resource status register (intel hd audio controller?d27:f0) address offset: 11ah?11bh attribute: ro default value: 0000h size: 16 bits 18.1.42 vcicap?vci resour ce capability register (intel hd audio controller?d27:f0) address offset: 11ch?11fh attribute: ro default value: 00000000h size: 32 bits 18.1.43 vcictl?vci reso urce control register (intel hd audio controller?d27:f0) address offset: 120h?123h attribute: r/w, ro default value: 00000000h size: 32 bits bit description 15:2 reserved . 1 vc0 negotiation pending ? ro. hardwired to 0 since th is bit does not apply to the integrated intel hd audio device. 0 port arbitration table status ? ro. hardwired to 0 since this field is not valid for endpoint devices. bit description 31:24 port arbitration table offset ? ro. hardwired to 0 since this field is not valid for endpoint devices. 23 reserved . 22:16 maximum time slots ? ro. hardwired to 0 since this field is not valid for endpoint devices. 15 reject snoop transactions ? ro. hardwired to 0 since this field is not valid for endpoint devices. 14 advanced packet switching ? ro. hardwired to 0 since this field is not valid for endpoint devices. 13:8 reserved 7:0 port arbitration capability ? ro. hardwired to 0 since this field is not valid for endpoint devices. bit description 31 vci enable ? r/w. 0 = vci is disabled 1 = vci is enabled note: this bit is not reset on d3 hot to d0 transition; however, it is reset by pltrst#. 30:27 reserved . 26:24 vci id ? r/w. this field assigns a vc id to th e vci resource. this field is not used by the chipset hardware, but it is r/w to avoid confusing software. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 590 datasheet 18.1.44 vcists?vci resource status register (intel hd audio controller?d27:f0) address offset: 126h?127h attribute: ro default value: 0000h size: 16 bits 18.1.45 rccap?root complex link declaration enhanced capability header register (intel hd audio controller? d27:f0) address offset: 130h?133h attribute: ro default value: 00010005h size: 32 bits 23:20 reserved . 19:17 port arbitration select ? ro. hardwired to 0 since this field is not valid for endpoint devices. 16 load port arbitration table ? ro. hardwired to 0 since this field is not valid for endpoint devices. 15:8 reserved . 7:0 tc/vci map ? r/w, ro. this field indicates the tcs that are mapped to the vci resource. bit 0 is hardwired to 0 indicating th at it cannot be mapped to vci. bits [7:1] are implemented as r/w bits. this field is not used by the chipset hardware, but it is r/ w to avoid confusing software. bit description bit description 15:2 reserved . 1 vci negotiation pending ? ro. does not apply. hardwired to 0. 0 port arbitratio n table status ? ro. hardwired to 0 since this field is not valid for endpoint devices. bit description 31:20 next capability offset ? ro. hardwired to 0 indicating this is the last capability. 19:16 capability version ? ro. hardwired to 1h. 15:0 pci express* extend ed capability id ? ro. hardwired to 0005h. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 591 intel hd audio controller registers (d27:f0) 18.1.46 esd?element self description register (intel hd audio controller?d27:f0) address offset: 134h?137h attribute: ro default value: 0f000100h size: 32 bits 18.1.47 l1desc?link 1 description register (intel hd audio controller?d27:f0) address offset: 140h?143h attribute: ro default value: 00000001h size: 32 bits 18.1.48 l1addl?link 1 lo wer address register (intel hd audio controller?d27:f0) address offset: 148h?14bh attribute: ro default value: see register description size: 32 bits bit description 31:24 port number ? ro. hardwired to 0fh indicating that the intel hd audio controller is assigned as port #15d. 23:16 component id ? ro. this field returns the value of the esd.cid field of the chip configuration section. esd.cid is programmed by bios. 15:8 number of link entries ? ro. the intel high definition audio only connects to one device, the chipset egress port. therefore this field reports a value of 1h. 7:4 reserved . 3:0 element type (eltyp) ? ro. the intel high definition audio controller is an integrated root complex de vice. therefore, the fiel d reports a value of 0h. bit description 31:24 target port number ? ro. the intel high definition audio controller targets the chipset?s port #0. 23:16 target component id ? ro. this field returns the value of the esd.cid field of the chip configuration section. esd.cid is programmed by bios. 15:2 reserved . 1 link type ? ro. hardwired to 0 indicating type 0. 0 link valid ? ro. hardwired to 1. bit description 31:14 link 1 lower address ? ro. hardwired to match the rc ba register value in the pci- lpc bridge (d31:f0:f0h). 13:0 reserved . www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 592 datasheet 18.1.49 l1addu?link 1 u pper address register (intel hd audio controller?d27:f0) address offset: 14ch?14fh attribute: ro default value: 00000000h size: 32 bits 18.2 intel hd audio memory-mapped configuration registers (intel hd audio? d27:f0) the base memory location for these memory mapped configuration registers is specified in the hdbar register (d27:f0 :offset 10h and d27:f0:offset 14h). the individual registers are then accessible at hdbar + offset as indicated in the following table. these memory mapped registers must be acce ssed in byte, word, or dword quantities. bit description 31:0 link 1 upper address ? ro. hardwired to 00000000h. table 18-147.intel hd audi o pci register address map (intel hd audio d27:f0) (sheet 1 of 5) hdbar + offset mnemonic register name default access 00h?01h gcap global capabilities 4401h ro 02h vmin minor version 00h ro 03h vmaj major version 01h ro 04h?05h outpay output payload capability 003ch ro 06h?07h inpay input payload capability 001dh ro 08h?0bh gctl global control 00000000h r/w 0ch?0dh wakeen wake enable 0000h r/w 0eh?0fh statests state change status 0000h r/wc 10h?11h gsts global status 0000h r/wc 12h?13h ? reserved 0000h ro 14h?17h ? reserved 00000000h ro 1 8h?19h outstrmpay output stream payload capability 0030h ro 1ah?1bh instrmpay input stream payload capability 0018h ro 1ch?1fh ? reserved 00000000h ro 20h?23h intctl interrupt control 00000000h r/w 24h?27h intsts interrupt status 00000000h ro 30h?33h walclk wall clock counter 00000000h ro 34h?37h ssync stream synchronization 00000000h r/w 40h?43h corblbase corb lower base address 00000000h r/w, ro www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 593 intel hd audio controller registers (d27:f0) 44h?47h corbubase corb upper base address 00000000h r/w 48h?49h corbwp corb write pointer 0000h r/w 4ah?4bh corbrp corb read pointer 0000h r/w 4ch corbctl corb control 00h r/w 4dh corbst corb status 00h r/wc 4eh corbsize corb size 42h ro 50h?53h rirblbase rirb lower base address 00000000h r/w, ro 54h?57h rirbubase rirb upper base address 00000000h r/w 58h?59h rirbwp rirb write pointer 0000h r/w, ro 5ah?5bh rintcnt response interrupt count 0000h r/w 5ch rirbctl rirb control 00h r/w 5dh rirbsts rirb status 00h r/wc 5eh rirbsize rirb size 42h ro 60h?63h ic immediate command 00000000h r/w 64h?67h ir immediate response 00000000h ro 68h?69h irs immediate command status 0000h r/w, r/ wc 70h?73h dplbase dma position lower base address 00000000h r/w, ro 74h?77h dpubase dma position upper base address 00000000h r/w 80?82h isd0ctl input stream descriptor 0 (isd0) control 040000h r/w, ro 83h isd0sts isd0 status 00h r/wc, ro 84h?87h isd0lpib isd0 link position in buffer 00000000h ro 88h?8bh isd0cbl isd0 cyclic buffer length 00000000h r/w 8ch?8dh isd0lvi isd0 last valid index 0000h r/w 8eh?8f isd0fifow isd0 fifo watermark 0004h r/w 90h?91h isd0fifos isd0 fifo size 0077h ro 92h?93h isd0fmt isd0 format 0000h r/w 98h?9bh isd0bdpl isd0 buffer descriptor list pointer- lower base address 00000000h r/w, ro 9ch?9fh isd0bdpu isd0 buffer description list pointer- upper base address 00000000h r/w a0h?a2h isd1ctl input stream descriptor 1(isd01) control 040000h r/w, ro a3h isd1sts isd1 status 00h r/wc, ro a4h?a7h isd1lpib isd1 link position in buffer 00000000h ro a8h?abh isd1cbl isd1 cyclic buffer length 00000000h r/w table 18-147.intel hd audi o pci register address map (intel hd audio d27:f0) (sheet 2 of 5) hdbar + offset mnemonic register name default access www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 594 datasheet ach?adh isd1lvi isd1 last valid index 0000h r/w aeh?afh isd1fifow isd1 fifo watermark 0004h r/w b0h?b1h isd1fifos isd1 fifo size 0077h ro b2?b3h isd1fmt isd1 format 0000h r/w b8?bbh isd1bdpl isd1 buffer descriptor list pointer- lower base address 00000000h r/w, ro bch?bfh isd1bdpu isd1 buffer description list pointer- upper base address 00000000h r/w c0h?c2h isd2ctl input stream descriptor 2 (isd2) control 040000h r/w, ro c3h isd2sts isd2 status 00h r/wc, ro ch4?c7h isd2lpib isd2 link position in buffer 00000000h ro c8h?cbh isd2cbl isd2 cyclic buffer length 00000000h r/w cch?cdh isd2lvi isd2 last valid index 0000h r/w ceh?cfh isd1fifow isd1 fifo watermark 0004h r/w d0h?d1h isd2fifos isd2 fifo size 0077h ro d2h?d3h isd2fmt isd2 format 0000h r/w d8h?dbh isd2bdpl isd2 buffer descriptor list pointer- lower base address 00000000h r/w, ro dch?dfh isd2bdpu isd2 buffer description list pointer- upper base address 00000000h r/w e0h?e2h isd3ctl input stream descriptor 3 (isd3) control 040000h r/w, ro e3h isd3sts isd3 status 00h r/wc, ro e4h?e7h isd3lpib isd3 link position in buffer 00000000h ro e8h?ebh isd3cbl isd3 cyclic buffer length 00000000h r/w ech?edh isd3lvi isd3 last valid index 0000h r/w eeh?efh isd3fifow isd3 fifo watermark 0004h r/w f0h?f1h isd3fifos isd3 fifo size 0077h ro f2h?f3h isd3fmt isd3 format 0000h r/w f8h?fbh isd3bdpl isd3 buffer descriptor list pointer- lower base address 00000000h r/w, ro fch?ffh isd3bdpu isd3 buffer description list pointer- upper base address 00000000h r/w 100h?102h osd0ctl output stream descriptor 0 (osd0) control 040000h r/w, ro 103h osd0sts osd0 status 00h r/wc, ro 104h?107h osd0lpib osd0 link position in buffer 00000000h ro table 18-147.intel hd audi o pci register address map (intel hd audio d27:f0) (sheet 3 of 5) hdbar + offset mnemonic register name default access www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 595 intel hd audio controller registers (d27:f0) 108h?10bh osd0cbl osd0 cyclic buffer length 00000000h r/w 10ch?10dh osd0lvi osd0 last valid index 0000h r/w 10eh?10fh osd0fifow osd0 fifo watermark 0004h r/w 110h?111h osd0fifos osd0 fifo size 00bfh r/w 112?113h osd0fmt osd0 format 0000h r/w 118h?11bh osd0bdpl osd0 buffer descriptor list pointer- lower base address 00000000h r/w, ro 11ch?11fh osd0bdpu osd0 buffer description list pointer- upper base address 00000000h r/w 120h?122h osd1ctl output stream descriptor 1 (osd1) control 040000h r/w, ro 123h osd1sts osd1 status 00h r/wc, ro 124h?127h osd1lpib osd1 link position in buffer 00000000h ro 128h?12bh osd1cbl osd1 cyclic buffer length 00000000h r/w 12ch?12dh osd1lvi osd1 last valid index 0000h r/w 12eh?12fh osd1fifow osd1 fifo watermark 0004h r/w 130h?131h osd1fifos osd1 fifo size 00bfh r/w 132h?133h osd1fmt osd1 format 0000h r/w 138h?13bh osd1bdpl osd1 buffer descriptor list pointer- lower base address 00000000h r/w, ro 13ch?13fh osd1bdpu osd1 buffer description list pointer- upper base address 00000000h r/w 140h?142h osd2ctl output stream descriptor 2 (osd2) control 040000h r/w, ro 143h osd2sts osd2 status 00h r/wc, ro 144h?147h osd2lpib osd2 link position in buffer 00000000h ro 148h?14bh osd2cbl osd2 cyclic buffer length 00000000h r/w 14ch?14dh osd2lvi osd2 last valid index 0000h r/w 14eh?14fh osd2fifow osd2 fifo watermark 0004h r/w 150h?151h osd2fifos osd2 fifo size 00bfh r/w 152h?153h osd2fmt osd2 format 0000h r/w 158h?15bh osd2bdpl osd2 buffer descriptor list pointer- lower base address 00000000h r/w, ro 15ch?15fh osd2bdpu osd2 buffer description list pointer- upper base address 00000000h r/w 160h?162h osd3ctl output stream descriptor 3 (osd3) control 040000h r/w, ro 163h osd3sts osd3 status 00h r/wc, ro table 18-147.intel hd audi o pci register address map (intel hd audio d27:f0) (sheet 4 of 5) hdbar + offset mnemonic register name default access www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 596 datasheet 18.2.1 gcap?global capabilities register (intel hd audio controller?d27:f0) memory address:hdbar + 00h attribute: ro default value: 4401h size: 16 bits 164h?167h osd3lpib osd3 link position in buffer 00000000h ro 168h?16bh osd3cbl osd3 cyclic buffer length 00000000h r/w 16ch?16dh osd3lvi osd3 last valid index 0000h r/w 16eh?16fh osd3fifow osd3 fifo watermark 0004h r/w 170h?171h osd3fifos osd3 fifo size 00bfh r/w 172h?173h osd3fmt osd3 format 0000h r/w 178h?17bh osd3bdpl osd3 buffer descriptor list pointer- lower base address 00000000h r/w, ro 17ch?17fh osd3bdpu osd3 buffer description list pointer- upper base address 00000000h r/w table 18-147.intel hd audi o pci register address map (intel hd audio d27:f0) (sheet 5 of 5) hdbar + offset mnemonic register name default access bit description 15:12 number of output stream supported ? ro. hardwired to 0100b indicating that the chipset intel hd audio controll er supports 4 output streams. 11:8 number of input stream supported ? ro. hardwired to 0100b indicating that the chipset intel high defini tion audio controller supports 4 input streams. 7:3 number of bidirectional stream supported ? ro. hardwired to 0 indicating that the chipset intel high defini tion audio controller suppo rts 0 bidirectional stream. 2 reserved . 1 number of serial data out signals ? ro. hardwired to 0 indicating that the chipset intel high definition audi o controller supports 1 serial data output signal. 0 64-bit address supported ? ro. hardwired to 1b indicating that the chipset intel high definition audio controller supports 64-bit addressing for bdl addresses, data buffer addressees, and co mmand buffer addresses. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 597 intel hd audio controller registers (d27:f0) 18.2.2 vmin?minor version register (intel hd audio controller?d27:f0) memory address:hdbar + 02h attribute: ro default value: 00hsize:8 bits 18.2.3 vmaj?major version register (intel hd audio controller?d27:f0) memory address:hdbar + 03h attribute: ro default value: 01hsize:8 bits 18.2.4 outpay?output payloa d capability register (intel hd audio controller?d27:f0) memory address:hdbar + 04h attribute: ro default value: 003chsize:16 bits bit description 7:0 minor version ? ro. hardwired to 0 indicating th at the chipset supports minor revision number 00h of the in tel hd audio specification. bit description 7:0 major version ? ro. hardwired to 01h indicating th at the chipset supports major revision number 1 of the intel hd audio specification. bit description 15:7 reserved . 6:0 output payload capability ? ro. hardwired to 3ch indicating 60 word payload. this field indicates the total output payload available on the link. this does not include bandwidth used for command and control. this measurement is in 16-bit word quantities per 48 mhz frame. the default link clock of 24.000 mhz (the data is double pumped) provides 1000 bits per frame, or 62. 5 words in total. 40 bits are used for command and control, leaving 60 words available for data payload. 00h = 0 word 01h = 1 word payload. ..... ffh = 256 word payload. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 598 datasheet 18.2.5 inpay?input payloa d capability register (intel hd audio controller?d27:f0) memory address:hdbar + 06h attribute: ro default value: 001dhsize:16 bits 18.2.6 gctl?global control register (intel hd audio controller?d27:f0) memory address:hdbar + 08h attribute: r/w default value: 00000000hsize:32 bits bit description 15:7 reserved . 6:0 input payload capability ? ro. hardwired to 1dh indicating 29 word payload. this field indicates the total output payload available on the link. this does not include bandwidth used for response. this measurement is in 16-b it word quantities per 48 mhz frame. the default link clock of 24.000 mhz provides 500 bits per frame, or 31.25 words in total. 36 bits are used for resp onse, leaving 29 words available for data payload. 00h = 0 word 01h = 1 word payload. ..... ffh = 256 word payload. bit description 31:9 reserved . 8 accept unsolicited response enable ? r/w. 0 = unsolicited responses from the codecs are not accepted. 1 = unsolicited response from the codecs are accepted by the controller and placed into the response input ring buffer. 7:2 reserved . 1 flush control ? r/w. 0 = flush not in progress. 1 = writing a 1 to this bit initiates a flush. when the flush comple tion is received by the controller, hardware sets the flush status bit and clears this flush control bit. before a flush cycle is initiated, the dma position buffer must be programmed with a valid memory address by software , but the dma position buffer bit 0 needs not be set to enable the position reporting mechanism. also, all streams must be stopped (the associated run bit must be 0). when the flush is initiated, the controller wi ll flush the pipelines to memory to ensure that the hardware is ready to transition to a d3 state. setting this bit is not a critical step in the power state transition if the content of the fifios is not critical. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 599 intel hd audio controller registers (d27:f0) 18.2.7 wakeen?wake enable register (intel hd audio controller?d27:f0) memory address:hdbar + 0ch attribute: r/w default value: 0000hsize:16 bits 0 controller reset # ? r/w. 0 = writing a 0 to this bit causes the intel high definition audio co ntroller to be reset. all state machines, fifos, and non-resume well memory mapped configuration registers (not pci configuration registers) in the controller will be reset. the intel high definition audio link reset# sign al will be asserted, and all other link signals will be driven to their default values. after the hardware has completed sequencing into the reset state, it will repo rt a 0 in this bit. software must read a 0 from this bit to verify the controller is in reset. 1 = writing a 1 to this bit causes the controller to exit its reset state and deassert the intel high definition audio link reset# signal. software is responsibl e for setting/ clearing this bit such that the minimum intel high definition audio link reset# signal assertion pulse width specification is met. when the controller hardware is ready to begin operation, it will report a 1 in this bit. software must read a 1 from this bit before accessing any controller re gisters. this bit defaults to a 0 after hardware reset, therefore, software needs to write a 1 to this bit to begin operation. notes: 1. the corb/rirb run bits and all stream ru n bits must be verified cleared to 0 before writing a 0 to this bit in order to assure a clean re-start. 2. when setting or clearing this bit, so ftware must ensure that minimum link timing requirements (m inimum reset# assertion time, etc.) are met. 3. when this bit is 0 indicating that the co ntroller is in reset, writes to all intel high definition audio memory mapped regi sters are ignored as if the device is not present. the only exception is this register itself. the global control register is write-able as a dword, word, or byte even when crst# (this bit) is 0 if the byte enable for the byte contai ning the crst# bit (byte enable 0) is active. if byte enable 0 is not active, writes to the gl obal control register will bit description bit description 15:3 reserved . 2:0 sdin wake enable flags ? r/w. these bits control which sdi signal(s) may generate a wake event. a 1b in the bit mask indicates that the associated sdin signal is enabled to generate a wake. bit 0 is used for sdi0 bit 1 is used for sdi1 bit 2 is used for sdi2 note: these bits are in the resume well an d only cleared on a power on reset. software must not make as sumptions about the reset state of these bits and must set them appropriately. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 600 datasheet 18.2.8 statests?state change status register (intel hd audio controller?d27:f0) memory address:hdbar + 0eh attribute: r/wc default value: 0000hsize:16 bits 18.2.9 gsts?global status register (intel hd audio controller?d27:f0) memory address:hdbar + 10h attribute: r/wc default value: 0000hsize:16 bits bit description 15:3 reserved . 2:0 sdin state change status flags ? r/wc. flag bits that in dicate which sdi signal(s) received a state change event. the bits are cleared by writing 1?s to them. bit 0 = sdi0 bit 1 = sdi1 bit 2 = sdi2 note: these bits are in the resume well an d only cleared on a power on reset. software must not make assumptions ab out the reset state of these bits and must set them appropriately. bit description 15:2 reserved . 1 flush status ? r/wc. 0 = flush not completed 1 = this bit is set to 1 by hardware to indicate that the flush cycle initiated when the flush control bit (hdbar + 08h, bit 1) was set has completed. note: software must write a 1 to clear this bi t before the next time the flush control bit is set to clear the bit. 0 reserved . www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 601 intel hd audio controller registers (d27:f0) 18.2.10 outstrmpay?output st ream payload capability (intel hd audio controller?d27:f0) memory address:hdbar + 18h attribute: ro default value: 0030hsize:16 bits 18.2.11 instrmpay?input st ream payload capability (intel hd audio controller?d27:f0) memory address:hdbar + 1ah attribute: ro default value: 0018hsize:16 bits bit description 15:14 output fifo padding type (opadtype) ? ro. this field indicates how the controller pads the samples in the controller 's buffer (fifo). controllers may not pad at all or may pad to byte or memory container sizes. 0h = controller pads all samples to bytes 1h = reserved 2h = controller pads to memory container size 3h = controller does not pa d and uses samples directly 13:0 output stream payload ca pability (outstrmpay) ? ro. this field indicates maximum number of words per frame for any single output stream . this measurement is in 16 bit word quantities per 48 khz frame. the maximum supported is 48 words (96b); therefore, a value of 30h is reported in this register. the value does not specify the number of words actually transmitted in the frame, but is the size of the data in the controller buffer (fifo) after the samples are padded as specified by opadtype. thus, to compute the supported streams, each sa mple is padded according to opadtype and then multiplied by the number of channels and samples per frame. if this computed value is larger than outstrmpay, then that stream is not supported. the value specified is not affected by striping. software must ensure that a format that would ca use more words per frame than indicated is not programmed into the output stream descriptor register. the value may be larger than the outpay register value in some cases. bit description 15:14 input fifo padding type (ipadtype) ? ro. this field indicates how the controller pads the samples in the controller's buffer (fifo). controllers ma y not pad at all or may pad to byte or memory container sizes. 0h = controller pads all samples to bytes 1h = reserved 2h = controller pads to memory container size 3h = controller does not pa d and uses samples directly www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 602 datasheet 18.2.12 intctl?interrupt control register (intel hd audio controller?d27:f0) memory address:hdbar + 20h attribute: r/w default value: 00000000hsize:32 bits 13:0 input stream payload capability (instrmpay) ? ro. this field indicates the maximum number of words per frame for an y single input stream. this measurement is in 16-bit word quantities per 48-khz frame. the maximum supported is 24 words (48b); therefore, a value of 18h is reported in this register. the value does not specify the number of words actually transmitted in the frame, but is the size of the data as it will be plac ed into the controller's buffer (fifo). thus, samples will be padded according to ipadty pe before being stored into controller buffer. to compute the suppo rted streams, each sample is padded according to ipadtype and then multiplied by the numbe r of channels and sa mples per frame. if this computed value is larger than instrmpa y, then that stream is not supported. as the inbound stream tag is not stored with th e samples it is not included in the word count. the value may be larger than inpay register value in some cases, although values less than inpay may also be invalid due to overhe ad. software must ensure that a format that would cause more words per frame th an indicated is not programmed into the input stream descriptor register. bit description bit description 31 global interrupt enable (gie) ? r/w. global bit to enable device interrupt generation. 0 = disable. 1 = enable. the intel hd audio function is enabled to generate an interrupt. this control is in addition to any bits in the bus specific address space, such as the interrupt enable bit in the pci configuration space. note: this bit is not affected by the d3 hot to d0 transition. 30 controller interrupt enable (cie) ? r/w. enables the general interrupt for controller functions. 0 = disable. 1 = enable. the controller generates an in terrupt when the corre sponding status bit gets set due to a response interrupt, a response buffer overrun, and state change events. note: this bit is not affected by the d3 hot to d0 transition. 29:8 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 603 intel hd audio controller registers (d27:f0) 18.2.13 intsts?interrupt status register (intel hd audio controller?d27:f0) memory address:hdbar + 24h attribute: ro default value: 00000000hsize:32 bits 7:0 stream interrupt enable (sie) ? r/w. 0 = disable. 1 = enable. when set to 1, th e individual streams are enable d to generate an interrupt when the corresponding status bits get set. a stream interrupt will be caused as a resu lt of a buffer with ioc = 1in the bdl entry being completed, or as a result of a fifo error (underrun or ove rrun) occurring. control over the generation of each of these source s is in the associated stream descriptor. the streams are numbered and the sie bits as signed sequentially, based on their order in the register set. bit 0 = input stream 1 bit 1 = input stream 2 bit 2 = input stream 3 bit 3 = input stream 4 bit 4 = output stream 1 bit 5 = output stream 2 bit 6 = output stream 3 bit 7 = output stream 4 bit description bit description 31 global interrupt status (gis) ? ro. this bit is an or of all the interrupt status bits in this register. note: this bit is not affected by the d3 hot to d0 transition. 30 controller interrupt status (cis) ? ro. status of general controller interrupt. 0 = an interrupt condition did not occur as described below. 1 = an interrupt condition occurred due to a response interrupt , a response buffer overrun interrupt, or a sdin state ch ange event. the exact cause can be determined by interrogating ot her registers. this bit is an or of all of the stated interrupt status bits for this register. notes: 1. this bit is set regardless of the state of the corresponding in terrupt enable bit, but a hardware interrupt will not be ge nerated unless the corresponding enable bit is set. 2. this bit is not affected by the d3 hot to d0 transition. 29:8 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 604 datasheet 18.2.14 walclk?wall cloc k counter register (intel hd audio controller?d27:f0) memory address:hdbar + 30h attribute: ro default value: 00000000hsize:32 bits 7:0 stream interrup t status (sis) ? ro. 0 = an interrupt condition did not occur on the corre sponding stream. 1 = an interrupt condition occurred on the corresp onding stream. this bit is an or of all of the stream?s inte rrupt status bits. note: these bits are set regardless of the stat e of the corresponding interrupt enable bits. the streams are numbered and the sie bits a ssigned sequentially, based on their order in the register set. bit 0 = input stream 1 bit 1 = input stream 2 bit 2 = input stream 3 bit 3 = input stream 4 bit 4 = output stream 1 bit 5 = output stream 2 bit 6 = output stream 3 bit 7 = output stream 4 bit description bit description 31:0 wall clock counter ? ro. this 32-bit counter field is incremented on each link bclk period and rolls over from ffff ffffh to 0000 0000h. this counter will roll over to 0 with a period of approximately 179 seconds. this counter is enabled while the bclk bit is set to 1. software uses this counter to synchronize between multiple controllers. will be reset on controller reset. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 605 intel hd audio controller registers (d27:f0) 18.2.15 ssync?stream synchronization register (intel hd audio controller?d27:f0) memory address:hdbar + 34h attribute: r/w default value: 00000000hsize:32 bits 18.2.16 corblbase?corb lower base address register (intel hd audio controller?d27:f0) memory address:hdbar + 40h attribute: r/w, ro default value: 00000000hsize:32 bits bit description 31:8 reserved 7:0 stream synchronization (ssync) ? r/w. 0 = data is not blocked from being sent on or received from the link 1 = the set bits block data from being sent on or receiv ed from the link. each bit controls the associated stream descriptor (i.e., bit 0 corresponds to the first stream descriptor, etc.) to synchronously start a set of dma engines, these bits are first set to 1. the run bits for the associated stream descriptors are then set to 1 to start the dma engines. when all streams are ready (fifordy =1), the associated ssync bits can all be set to 0 at the same time, and transmission or receptio n of bits to or from the link will begin together at the start of the next full link frame. to synchronously stop the streams, first these bits are set, and then the individual run bits in the stream descripto r are cleared by software. if synchronization is not desired, these bits ma y be left as 0, and th e stream will simply begin running normally when the stream?s run bit is set. the streams are numbered and the sie bits as signed sequentially, based on their order in the register set. bit 0 = input stream 1 bit 1 = input stream 2 bit 2 = input stream 3 bit 3 = input stream 4 bit 4 = output stream 1 bit 5 = output stream 2 bit 6 = output stream 3 bit 7 = output stream 4 bit description 31:7 corb lower base address ? r/w. this field is the lo wer address of the command output ring buffer, allowing the corb ba se address to be assigned on any 128-b boundary. this register field must not be written when the dma engine is running or the dma transfer may be corrupted. 6:0 corb lower base unimplemented bits ? ro. hardwired to 0. this requires the corb to be allocated with 128b granularity to allow for cache line fetch optimizations. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 606 datasheet 18.2.17 corbubase?corb uppe r base address register (intel hd audio controller?d27:f0) memory address:hdbar + 44h attribute: r/w default value: 00000000hsize:32 bits 18.2.18 corbwp?corb write pointer register (intel hd audio controller?d27:f0) memory address:hdbar + 48h attribute: r/w default value: 0000hsize:16 bits 18.2.19 corbrp?corb read pointer register (intel hd audio controller?d27:f0) memory address:hdbar + 4ah attribute: r/w default value: 0000hsize:16 bits bit description 31:0 corb upper base address ? r/w. this field is the uppe r 32 bits of the address of the command output ring buffer. this register field must not be written when the dma engine is running or the dm a transfer may be corrupted. bit description 15:8 reserved . 7:0 corb write pointer ? r/w. software writes the last valid corb entry offset into this field in dword granularity. the dma engine fetches commands from the corb until the read pointer matches the write pointer. supports 256 corb entries (256x4b = 1kb). this register field may be writte n when the dma engine is running. bit description 15 corb read pointer reset ? r/w. software writes a 1 to this bit to reset the corb read pointer to 0 and clear any residual prefetched commands in the corb hardware buffer within the intel hd audio controller. th e hardware will physic ally update this bit to 1 when the corb pointer reset is complete. software must read a 1 to verify that the reset completed correctly. software must clear this bit back to 0 and read back the 0 to verify that the clear completed correctly. the corb dma engine must be stopped prior to resetting the read pointer or el se dma transfer may be corrupted. 14:8 reserved . 7:0 corb read pointer (corbrp) ? ro. software reads this field to determine how many commands it can write to the corb without over-running. the value read indicates the corb read pointer offset in dw ord granularity. the offset entry read from this field has been successfully fetched by the dma controller and may be over-written by software. supports 256 corb entries (256 x 4b=1kb). this field may be read while the dma engine is running. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 607 intel hd audio controller registers (d27:f0) 18.2.20 corbctl?corb control register (intel hd audio controller?d27:f0) memory address:hdbar + 4ch attribute: r/w default value: 00hsize:8 bits 18.2.21 corbst?corb status register (intel hd audio controller?d27:f0) memory address:hdbar + 4dh attribute: r/wc default value: 00hsize:8 bits 18.2.22 corbsize?corb size register intel hd audio controller?d27:f0) memory address:hdbar + 4eh attribute: ro default value: 42hsize:8 bits bit description 7:2 reserved . 1 enable corb dma engine ? r/w. after software writes a 0 to this bit, the hardware may not stop immediately. the hardware will physically update the bit to 0 when the dma engine is truly stopped. software must read a 0 from th is bit to verify that the dma engine is truly stopped. 0 = dma stop 1 = dma run 0 corb memory error interrupt enable ? r/w. 0 = disable. 1 = enable. the controller will generate an interrupt if the cmei status bit (hdbar + 4dh: bit 0) is set. bit description 7:1 reserved . 0 corb memory error indication (cmei) ? r/wc. 0 = error not detected. 1 = the controller has detect ed an error in the path wa y between the controller and memory. this may be an ecc bit error or any other type of de tectable data error which renders the command data fetched invalid. note: software can clear this bit by writing a 1 to it. however, this type of error leaves the audio subsystem in an un-viable stat e and typically requ ires a controller reset by writing a 0 to the controll er reset # bit (hdbar + 08h: bit 0). bit description 7:4 corb size capability ? ro. hardwired to 0100b indicating that the chipset only supports a corb size of 256 corb entries (1024b). 3:2 reserved . 1:0 corb size ? ro. hardwired to 10b which sets th e corb size to 256 entries (1024b). www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 608 datasheet 18.2.23 rirblbase?rirb lower base address register (intel hd audio controller?d27:f0) memory address:hdbar + 50h attribute: r/w, ro default value: 00000000hsize:32 bits 18.2.24 rirbubase?rirb upper base address register (intel hd audio controller?d27:f0) memory address:hdbar + 54h attribute: r/w default value: 00000000hsize:32 bits 18.2.25 rirbwp?rirb writ e pointer register (intel hd audio controller?d27:f0) memory address:hdbar + 58h attribute: r/w, ro default value: 0000hsize:16 bits bit description 31:7 rirb lower base address ? r/w. this field is the lo wer address of the response input ring buffer, allowing the rirb base address to be assigned on any 128-b boundary. this register field must not be written when the dma engine is running or the dma transfer may be corrupted. 6:0 rirb lower base unimplemented bits ? ro. ha rdwired to 0. this required the rirb to be allocated with 128-b granularity to allow for cache line fetch optimizations. bit description 31:0 rirb upper base address ? r/w. this field is the upper 32 bits of the address of the response input ring buffer. this register field must no t be written when the dma engine is running or the dm a transfer may be corrupted. bit description 15 rirb write pointer reset ? r/w. software writes a 1 to this bit to reset the rirb write pointer to 0. the rirb dma engine mu st be stopped prior to resetting the write pointer or else dma transfer may be corrupted. this bit is always read as 0. 14:8 reserved . 7:0 rirb write pointer (rirbwp) ? ro. this field is the indicates the last valid rirb entry written by the dma controller. software reads this field to determine how many responses it can read from the rirb. the va lue read indicates the rirb write pointer offset in 2 dword rirb entry units (since each rirb entry is 2 dwords long). supports up to 256 rirb entries (256 x 8 b = 2 kb). th is register field may be written when the dma engine is running. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 609 intel hd audio controller registers (d27:f0) 18.2.26 rintcnt?response in terrupt count register (intel hd audio controller?d27:f0) memory address:hdbar + 5ah attribute: r/w default value: 0000hsize:16 bits 18.2.27 rirbctl?rirb control register (intel hd audio controller?d27:f0) memory address:hdbar + 5ch attribute: r/w default value: 00hsize:8 bits bit description 15:8 reserved . 7:0 n response interrupt count ? r/w. 0000 0001b = 1 response sent to rirb ........... 1111 1111b = 255 responses sent to rirb 0000 0000b = 256 responses sent to rirb the dma engine should be sto pped when changing this field or else an interrupt may be lost. note that each response occu pies 2 dwords in the rirb. this is compared to the total number of responses that have been returned, as opposed to the number of frames in which there were responses. if more than one codec responds in one frame, then the count is increased by the number of responses received in the frame. bit description 7:3 reserved . 2 response overrun interrupt control ? r/w. 0 = hardware will not generated an interrupt as described below. 1 = the hardware will generate an interru pt when the response overrun interrupt status bit (hdbar + 5dh: bit 2) is set. 1 enable rirb dma engine ? r/w. after software writes a 0 to this bit, the hardware may not stop immediately. the hardware will physically update the bit to 0 when the dma engine is truly stopped. software must read a 0 from th is bit to verify that the dma engine is truly stopped. 0 = dma stop 1 = dma run 0 response interrupt control ? r/w. 0 = disable interrupt 1 = generate an interrupt after n number of responses are sent to the rirb buffer or when an empty response slot is encoun tered on all sdi[x] inputs (whichever occurs first). the n coun ter is reset when the interrupt is generated. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 610 datasheet 18.2.28 rirbsts?rirb status register (intel hd audio controller?d27:f0) memory address:hdbar + 5dh attribute: r/wc default value: 00hsize:8 bits 18.2.29 rirbsize?rirb size register (intel hd audio controller?d27:f0) memory address:hdbar + 5eh attribute: ro default value: 42hsize:8 bits 18.2.30 ic?immediate command register (intel hd audio controller?d27:f0) memory address:hdbar + 60h attribute: r/w default value: 00000000hsize:32 bits bit description 7:3 reserved . 2 response overrun interrupt status ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = software sets this bit to 1 when the rirb dma engine is not able to write the incoming responses to memory before a dditional incoming re sponses overrun the internal fifo. when the overrun occurs, th e hardware will drop the responses that overrun the buffer. an interrupt may be generated if the response overrun interrupt control bit is set. note that this status bit is set even if an interrupt is not enabled for this event. 1 reserved . 0 response interrupt ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = hardware sets this bit to 1 when an interrupt has been generated after n number of responses are sent to the rirb buffe r or when an empty response slot is encountered on all sdi[x] inputs (whichever occurs fi rst). note that this status bit is set even if an interrupt is not enabled for this event. bit description 7:4 rirb size capability ? ro. hardwired to 0100b indicating that the chipset only supports a rirb size of 256 rirb entries (2048b) 3:2 reserved . 1:0 rirb size ? ro . hardwired to 10b which sets the corb size to 256 entries (2048b) bit description 31:0 immediate command write ? r/w . the command to be sent to the codec via the immediate command mechanism is written to this register. the command stored in this register is sent out over the link during the next available frame after a 1 is written to the icb bit (hdbar + 68h: bit 0) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 611 intel hd audio controller registers (d27:f0) 18.2.31 ir?immediate response register (intel hd audio controller?d27:f0) memory address:hdbar + 64h attribute: ro default value: 00000000hsize:32 bits 18.2.32 irs?immediate comm and status register (intel hd audio controller?d27:f0) memory address:hdbar + 68h attribute: r/w, r/wc default value: 0000hsize:16 bits bit description 31:0 immediate response read (irr) ? ro. this register contains the response received from a codec resulting from a command sent via the immediate command mechanism. if multiple codecs responded in the same time, there is no assurance as to which response will be latched. th erefore, broadcast-type comman ds must not be issued via the immediate command mechanism. bit description 15:2 reserved . 1 immediate result valid (irv) ? r/wc. 0 = software must clear this bit by writing a 1 to it before issuing a new command so that the software may determine when a new response has arrived. 1 = set to 1 by hardware when a new response is latched into the immediate response register (hdbar + 64). this is a status flag indicating that software may read the response from the immedi ate response register. 0 immediate command busy (icb) ? r/w. when this bit is read as 0, it indicates that a new command may be issued using the im mediate command mech anism. when this bit transitions from 0-to-1 (via software writing a 1), the controller issues the command currently stored in the immediate command register to the codec over the link. when the corresponding response is latched into the immedi ate response register, the controller hardware sets the irv flag and clears the icb bit back to 0. note: an immediate command must not be issued while the corb/rirb mechanism is operating, otherwise the responses conflict. this must be enforced by software. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 612 datasheet 18.2.33 dplbase?dma position lo wer base address register (intel hd audio controller?d27:f0) memory address:hdbar + 70h attribute: r/w, ro default value: 00000000hsize:32 bits 18.2.34 dpubase?dma position u pper base addr ess register (intel hd audio controller?d27:f0) memory address:hdbar + 74h attribute: r/w default value:00000000h size: 32 bits 18.2.35 sdctl?stream descri ptor control register (intel hd audio controller?d27:f0) memory address:input stream[0 ]: hdbar + 80hattribute:r/w, ro input stream[1]: hdbar + a0h input stream[2]: hdbar + c0h input stream[3]: hdbar + e0h output stream[0]: hdbar + 100h output stream[1]: hdbar + 120h output stream[2]: hdbar + 140h output stream[3]: hdbar + 160h default value: 040000h size: 24 bits bit description 31:7 dma position lowe r base address ? r/w. lower 32 bits of the dma position buffer base address. this register field must not be written when any dma engine is running or the dma transfer may be corrupted. this same address is used by the flush control and must be programmed with a vali d value before the flush control bit (hdbar+08h:bit 1) is set. 6:1 dma position lower base unimplemented bits ? ro. hardwired to 0 to force the 128- byte buffer alignment for cache line write optimizations. 0 dma position buffer enable ? r/w. 0 = disable. 1 = enable. the controller will write the dma positions of each of the dma engines to the buffer in the main memory periodically (typically once per frame). software can use this value to determine what data in memory is valid data. bit description 31:0 dma position upper base address ? r/w. upper 32 bits of the dma position buffer base address. this register field must not be written when any dma engine is running or the dma transfer may be corrupted. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 613 intel hd audio controller registers (d27:f0) bit description 23:20 stream number ? r/w. this value reflects the tag associated with the data being transferred on the link. when data controlled by this descriptor is sent out over the link, it will have its stream number encoded on the sync signal. when an input stream is detected on any of the sdi signals that match this value, the data samples are loaded into fifo associated with this descriptor. note that while a single sdi input may contain data from more than one stream number, two different sdi inputs may not be configured with the same stream number. 0000 = reserved 0001 = stream 1 ........ 1110 = stream 14 1111 = stream 15 19 bidirectional direction control ? ro. this bit is only meaningful for bidirectional streams; therefore, this bit is hardwired to 0. 18 traffic priority ? ro. hardwired to 1 indicating that all streams will use vc1 if it is enabled through the pci express* registers. 17:16 stripe control ? ro. this bit is only meaningful for input streams; therefore, this bit is hardwired to 0. 15:5 reserved 4 descriptor error interrupt enable ? r/w. 0 = disable 1 = an interrupt is generated when th e descriptor error status bit is set. 3 fifo error interrupt enable ? r/w. 0 = disable. 1 = enable. this bit controls whether the occurre nce of a fifo error (overrun for input or underrun for output) will cause an interrupt or not. if this bit is not set, bit 3 in the status register will be set, but the interrupt will not occur. either way, the samp les will be dropped. 2 interrupt on completion enable ? r/w. 0 = disable. 1 = enable. this bit controls whether or not an interrupt occu rs when a buffer completes with the ioc bit set in its descriptor. if this bit is not set, bit 2 in the status register will be set, but the interrupt will not occur. 1 stream run (run) ? r/w. 0 = disable. the dma engine associated with this input stream will be disabled. the hardware will report a 0 in this bit when the dma engine is actually stopped. software mu st read a 0 from this bit before modifying related control registers or restarting the dma engine. 1 = enable. the dma engine associated with this input stream will be enabled to transfer data from the fifo to the main memory. the ssync bit must also be cleared in order for the dma engine to run. for output st reams, the cadence generator is reset whenever the run bit is set. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 614 datasheet 18.2.36 sdsts?stream descri ptor status register (intel hd audio controller?d27:f0) memory address:input stream[0 ]: hdbar + 83hattribute:r/wc, ro input stream[1]: hdbar + a3h input stream[2]: hdbar + c3h input stream[3]: hdbar + e3h output stream[0]: hdbar + 103h output stream[1]: hdbar + 123h output stream[2]: hdbar + 143h output stream[3]: hdbar + 163h default value: 00hsize:8 bits 0 stream reset (srst) ? r/w. 0 = writing a 0 causes the co rresponding stream to exit reset. when the stream hardware is ready to begin operation, it will report a 0 in this bit. software must read a 0 from this bit before ac cessing any of the stream registers. 1 = writing a 1 causes th e corresponding stream to be reset. the stream descriptor registers (except the sr st bit itself) and fifo?s for the corresponding stream are reset. afte r the stream hardware has completed sequencing into the reset state, it will report a 1 in this bit. software must read a 1 from this bit to verify that the stream is in reset. the run bit must be cleared before srst is asserted. bit description bit description 7:6 reserved . 5 fifo ready (fifordy) ? ro. for output streams, th e controller hardware will set th is bit to 1 while the output dma fifo contains enough data to maintain the st ream on the link. this bit defaults to 0 on reset because the fifo is cleared on a reset. for input streams, the co ntroller hardware will set this bit to 1 when a valid descriptor is loaded and the engine is ready for the run bit to be set. 4 descriptor error ? r/wc. 0 = no error detected. 1 = a serious error occurred duri ng the fetch of a descriptor. this could be a result of a master abort, a parity or ecc error on the bus, or any other error which renders the current buffer descriptor or buffer descri ptor list useless. this error is treated as a fatal stream error, as the stream cann ot continue running. the run bit will be cleared and the stream will stop. note: software may attempt to restart the stre am engine after addressing the cause of the error and writing a 1 to this bit to clear it. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 615 intel hd audio controller registers (d27:f0) 18.2.37 sdlpib?stream descriptor link position in buffer register (intel hd audio controller?d27:f0) memory address:input stream[0]: hdbar + 84h attribute:ro input stream[1]: hdbar + a4h input stream[2]: hdbar + c4h input stream[3]: hdbar + e4h output stream[0]: hdbar + 104h output stream[1]: hdbar + 124h output stream[2]: hdbar + 144h output stream[3]: hdbar + 164h default value: 00000000hsize:32 bits 18.2.38 sdcbl?stream de scriptor cyclic buffer length register (intel hd audio controller?d27:f0) memory address:input stream[0]: hdbar + 88h attribute: r/w input stream[1]: hdbar + a8h input stream[2]: hdbar + c8h input stream[3]: hdbar + e8h output stream[0]: hdbar + 108h output stream[1]: hdbar + 128h output stream[2]: hdbar + 148h output stream[3]: hdbar + 168h default value: 00000000hsize:32 bits 3 fifo error ? r/wc. the bit is cleare d by writing a 1 to it. 0 = no error detected. 1 = fifo error occurred. this bit is set even if an interrupt is not enabled. for an input stream, this indi cates a fifo overrun occurring while the run bit is set. when this happens, the fifo pointers do no t increment and the incoming data is not written into the fifo, thereby being lost. for an output stream, this in dicates a fifo underrun when there are still buffers to send. the hardware should not transmit anythi ng on the link for the associated stream if there is not valid data to send. 2 buffer completion interrupt status ? r/wc. 0 = last sample of a buffer has not been processed as described below. 1 = set to 1 by the hardware after the last sample of a buffer has been processed, and if the interrupt on completion bit is set in the command byte of the buffer descriptor. it remains acti ve until software clears it by writing a 1 to it. 1:0 reserved . bit description 31:0 link position in buffer ? ro. indicates the number of bytes that have been received off the link. this register will count from 0 to the value in the cyclic buffer length register and then wrap to 0. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 616 datasheet 18.2.39 sdlvi?stream descriptor last valid index register (intel hd audio controller?d27:f0) memory address:input stream [0]: hdbar + 8ch attribute: r/w input stream[1]: hdbar + ach input stream[2]: hdbar + cch input stream[3]: hdbar + ech output stream[0]: hdbar + 10ch output stream[1]: hdbar + 12ch output stream[2]: hdbar + 14ch output stream[3]: hdbar + 16ch default value: 0000hsize:16 bits 18.2.40 sdfifow?stream descript or fifo watermark register (intel hd audio controller?d27:f0) memory address:input stream [0]: hdbar + 8eh attribute: r/w input stream[1]: hdbar + aeh input stream[2]: hdbar + ceh input stream[3]: hdbar + eeh output stream[0]: hdbar + 10eh output stream[1]: hdbar + 12eh output stream[2]: hdbar + 14eh output stream[3]: hdbar + 16eh default value: 0004hsize:16 bits bit description 31:0 cyclic buffer length ? r/w. indicates the number of bytes in the complete cyclic buffer. this register represen ts an integer number of samp les. link position in buffer will be reset when it reaches this value. software may only write to this register afte r global reset, controll er reset, or stream reset has occurred. this value should be only modified when the run bit is 0. once the run bit has been set to enable the engine, software must not write to this register until after the next reset is asserted , or transfer may be corrupted. bit description 15:8 reserved . 7:0 last valid index ? r/w. the value written to this re gister indicates the index for the last valid buffer descript or in bdl. after the controller has processed this descriptor, it will wrap back to the first descriptor in the list and continue processing. this field must be at least 1 (i.e., there must be at least 2 valid entries in the buffer descriptor list before dm a operations can begin). this value should only be mo dified when the run bit is 0. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 617 intel hd audio controller registers (d27:f0) 18.2.41 sdfifos?stream descri ptor fifo size register (intel hd audio controller?d27:f0) memory address:input stream[0]: hdbar + 90hattribute: input: ro input stream[1]: hdbar + b0h output: r/w input stream[2]: hdbar + d0h input stream[3]: hdbar + f0h output stream[0]: hdbar + 110h output stream[1]: hdbar + 130h output stream[2]: hdbar + 150h output stream[3]: hdbar + 170h default value: input stream: 0077hsize:16 bits output stream: 00bfh bit description 15:3 reserved . 2:0 fifo watermark (fifow) ? r/w. this field indicates the minimum number of bytes accumulated/free in the fifo be fore the controller will star t a fetch/eviction of data. 010 = 8b 011 = 16b 100 = 32b (default) others = unsupported notes: 1. when the bit field is pr ogrammed to an unsupported size, the hardware sets itself to the default value. 2. software must read the bit field to test if the value is supported after setting the bit field. www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 618 datasheet 18.2.42 sdfmt?stream descri ptor format register (intel hd audio controller?d27:f0) memory address:input stream[0]: hdbar + 92h attribute: r/w input stream[1]: hdbar + b2h input stream[2]: hdbar + d2h input stream[3]: hdbar + f2h output stream[0]: hdbar + 112h output stream[1]: hdbar + 132h output stream[2]: hdbar + 152h output stream[3]: hdbar + 172h default value: 0000hsize:16 bits bit description 15:8 reserved . 7:0 fifo size ? ro (input stream), r/w (output stream). this fi eld indicates the maximum number of bytes that could be fetche d by the controller at one time. this is the maximum number of bytes that may have been dma?d into memory but not yet transmitted on the link, and is also the maximum possible value that the picb count will increase by at one time. the value in this field is different for input and output streams. it is also dependent on the bits per samples setting for the corresp onding stream. following are the values read/written from/to this register for in put and output streams, and for non-padded and padded bit formats: output stream r/w value : notes: 1. all other values not listed are not supported. 2. when the output stream is programmed to an unsuppo rted size, the hardware sets itself to the default value (bfh). 3. software must read the bit field to test if the value is supported after setting the bit field. input stream ro value : note: the default value is different for input and output streams, and reflects the default state of the bits fi elds (in stream descriptor format registers) for the corresponding stream. value output streams 0fh = 16b 8, 16, 20, 24, or 32 bit output streams 1fh = 32b 8, 16, 20, 24, or 32 bit output streams 3fh = 64b 8, 16, 20, 24, or 32 bit output streams 7fh = 128b 8, 16, 20, 24, or 32 bit output streams bfh = 192b 8, 16, or 32 bit output streams ffh = 256b 20, 24 bit output streams value input streams 77h = 120b 8, 16, 32 bit input streams 9fh = 160b 20, 24 bit input streams www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 619 intel hd audio controller registers (d27:f0) bit description 15 reserved . 14 sample base rate ? r/w 0 = 48 khz 1 = 44.1 khz 13:11 sample base rate multiple ? r/w 000 = 48 khz, 44.1 khz or less 001 = x2 (96 khz, 88.2 khz, 32 khz) 010 = x3 (144 khz) 011 = x4 (192 khz, 176.4 khz) others = reserved . 10:8 sample base rate divisor ? r/w. 000 = divide by 1(48 khz, 44.1 khz) 001 = divide by 2 (24 khz, 22.05 khz) 010 = divide by 3 (16 khz, 32 khz) 011 = divide by 4 (11.025 khz) 100 = divide by 5 (9.6 khz) 101 = divide by 6 (8 khz) 110 = divide by 7 111 = divide by 8 (6 khz) 7 reserved . 6:4 bits per sample (bits) ? r/w. 000 = 8 bits. the data will be packed in memory in 8-bit co ntainers on 16-bit boundaries 001 = 16 bits. the data will be packed in memory in 16-bit quantities on 16-bit boundaries 010 = 20 bits. the data will be packed in memory in 32-bit quantities on 32-bit boundaries 011 = 24 bits. the data will be packed in memory in 32-bit quantities on 32-bit boundaries 100 = 32 bits. the data will be packed in memory in 32-bit quantities on 32-bit boundaries others = reserved . 3:0 number of channels (chan) ? r/w. indicates number of channels in each frame of the stream. 0000 =1 0001 =2 ........ 1111 =16 www.datasheet.co.kr datasheet pdf - http://www..net/
intel hd audio controll er registers (d27:f0) 620 datasheet 18.2.43 sdbdpl?stream descriptor buffer descriptor list pointer lower base address register (intel hd audio controller?d27:f0) memory address:input stream[0 ]: hdbar + 98hattribute: r/w,ro input stream[1]: hdbar + b8h input stream[2]: hdbar + d8h input stream[3]: hdbar + f8h output stream[0]: hdbar + 118h output stream[1]: hdbar + 138h output stream[2]: hdbar + 158h output stream[3]: hdbar + 178h default value: 00000000hsize:32 bits 18.2.44 sdbdpu?stream descriptor buffer descriptor list pointer upper base address register (intel hd audio controller? d27:f0) memory address:input stream [0]: hdbar + 9chattribute: r/w input stream[1]: hdbar + bch input stream[2]: hdbar + dch input stream[3]: hdbar + fch output stream[0]: hdbar + 11ch output stream[1]: hdbar + 13ch output stream[2]: hdbar + 15ch output stream[3]: hdbar + 17ch default value: 00000000hsize:32 bits bit description 31:7 buffer descriptor list po inter lower base address ? r/w. this field is the lower address of the buffer descriptor list. this value should only be modified when the run bit is 0, or dma transfer may be corrupted. 6:0 hardwired to 0 forcing alignment on 128-b boundaries. bit description 31:0 buffer descriptor list pointer upper base address ? r/w. this field is the upper 32-bit address of the buffer descriptor list. this value should only be modified when the run bit is 0, or dma transfer may be corrupted. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 621 pci express* configuration registers 19 pci express* configuration registers 19.1 pci express* configuration registers (pci express?d28:f0/f1/f2/f3) note: register address locations that are not shown in table 19-148 should be treated as reserved . / table 19-148.pci express* conf iguration registers address map (pci express?d28:f0/f1/f2/f3) (sheet 1 of 3) offset mnemonic register name function 0?5 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 rid revision identification see register description. ro 09h pi programming interface 00h ro 0ah scc sub class code 04h ro 0bh bcc base class code 06h ro 0ch cls cache line size 00h r/w 0dh plt primary latency timer 00h ro 0eh headtyp header type 81h ro 18h?1ah bnum bus number 000000h r/w 1ch?1dh iobl i/o base and limit 0000h r/w, ro 1eh?1fh ssts secondary status 0000h r/wc 20h?23h mbl memory base and limit 00000000h r/w 24h?27h pmbl prefetchable memory base and limit 00010001h r/w, ro 28h?2bh pmbu32 prefetchable memory base upper 32 bits 00000000h r/w 2ch?2fh pmlu32 prefetchable memory limit upper 32 bits 00000000h r/w 34h capp capabilities list pointer 40h ro 3ch?3dh intr interrupt informat ion see bit description r/w, ro 3eh?3fh bctrl bridge control 0000h r/w 40h?41h clist capabilities list 8010 ro 42h?43h xcap pci express* capabilities 0041 r/wo, ro 44h?47h dcap device capabilities 00000fe0h ro 48h?49h dctl device control 0000h r/w, ro 4ah?4bh dsts device status 0010h r/wc, ro www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 622 datasheet 4ch?4fh lcap link capabilities see bit description r/w, ro, r/wo 50h?51h lctl link control 0000h r/w, wo, ro 52h?53h lsts link status see bit description ro 54h?57h slcap slot capabilities register 00000060h r/wo, ro 58h?59h slctl slot control 0000h r/w, ro 5ah?5bh slsts slot status 0000h r/wc, ro 5ch?5dh rctl root control 0000h r/w 60h?63h rsts root status 00000000h r/wc, ro 80h?81h mid message signaled interrupt identifiers 9005h ro 82h?83h mc message signaled interrupt message control 0000h r/w, ro 84h?87h ma message signaled interrupt message address 00000000h r/w 88h?89h md message signaled interrupt message data 0000h r/w 90h?91h svcap subsystem vendor capability a00dh ro 94h?97h svid subsystem vendor identification 00000000h r/wo a0h?a1h pmcap power management capability 0001h ro a2h?a3h pmc pci power management capability c802h ro a4?a7h pmcs pci power management control and status 00000000h r/w, ro d8?dbh mpc miscellaneous port configuration 00110000h r/w dc?dfh smscs smi/sci status 00000000h r/wc e1h rpdcgen root port dynamic clock gating enable (netbook only) 00h r/w e2?e3h ipws intel ? pro/wireless 3945abg status 0000h ro 100?103h vch virtual channel capability header 18010002h ro 108h?10bh vcap2 virtual channel capability 2 00000001h ro 10ch?10dh pvc port virtual channel control 0000h r/w 10eh?10fh pvs port virtual channel status 0000h ro 110h?113h v0cap virtual channel 0 resource capability 00000001h ro 114?117h v0ctl virtual channel 0 resource control 800000ffh r/w, ro 11a?11bh v0sts virtual channel 0 resource status 0000h ro 144h?147h ues uncorrectable error status see bit description r/wc, ro 148h?14bh uem uncorrectable error mask 00000000h r/wo, ro 14ch?14fh uev uncorrectable error severity 00060011h ro 150h?153h ces correctable error status 00000000h r/wc 154h?157h cem correctable error mask 00000000h r/wo 158h?15bh aecc advanced error capabilities and control 00000000h ro 170h?173h res root error status 00000000h r/wc, ro 180h?183h rctcl root complex topology capability list 00010005h ro 184h?187h esd element self description see bit description ro table 19-148.pci express* conf iguration regist ers address map (pci express?d28:f0/f1/f2/f3) (sheet 2 of 3) offset mnemonic register name function 0?5 default type www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 623 pci express* configuration registers 19.1.1 vid?vendor identi fication register (pci express?d28:f0/f1/f2/f3) address offset: 00h ? 01h attribute: ro default value: 8086h size: 16 bits 19.1.2 did?device identification register (pci express?d28:f0/f1/f2/f3) address offset: 02h?03h attribute: ro default value: port 1= bit description size: 16 bits port 2= bit description port 3= bit description port 4= bit description 19.1.3 pcicmd?pci command register (pci express?d28:f0/f1/f2/f3) address offset: 04h?05h attribute: r/w, ro default value: 0000h size: 16 bits 190h?193h uld upstream link description 00000001h ro 198h?19fh ulba upstream link base address see bit description ro 318h peetm pci express extended test mode register 00h ro table 19-148.pci express* conf iguration registers address map (pci express?d28:f0/f1/f2/f3) (sheet 3 of 3) offset mnemonic register name function 0?5 default type bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel bit description 15:0 device id ? ro. bit description 15:11 reserved 10 interrupt disable ? r/w. this bit disa bles 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. note: this bit does not affect interrupt forwar ding from devices connected to the root port. assert_intx and deasse rt_intx messages will st ill be forwarded to the internal interrupt controll ers if this bit is set. 9 fast back to back enable (fbe) ? reserved per the pci express* base specification . www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 624 datasheet 19.1.4 pcists?pci status register (pci express?d28:f0/f1/f2/f3) address offset: 06h ? 07h attribute: r/wc, ro default value: 0010h size: 16 bits 8 serr# enable (see) ? r/w. 0 = disable. 1 = enables the root port to generate an serr# message when psts.sse is set. 7 wait cycle control (wcc) ? reserved per the pci express base specification . 6 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 vga palette snoop (vps) ? reserved per the pci express* base specification . 4 postable memory writ e enable (pmwe) ? reserved per the pci express* base specification . 3 special cycle enable (sce) ? reserved per the pci express* base specification . 2 bus master enable (bme) ? r/w. 0 = disable. all cycles from the device are master aborted 1 = enable. allows the root port to forw ard cycles onto the backbone from a pci express* device. 1 memory space enable (mse) ? r/w. 0 = disable. memory cycles within the rang e specified by the memory base and limit registers are master aborted on the backbone. 1 = enable. allows memory cycles within th e range specified by the memory base and limit registers can be forwarde d to the pci express device. 0 i/o space enable (iose) ? r/w. this bit controls access to the i/o space registers. 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 pci express device. bit description bit description 15 detected parity error (dpe) ? r/wc. 0 = no parity error detected. 1 = root port received a command or data from the backbone with a parity error. this is set even if pcimd.per (d28:f0/f1/f2/f3:04, bit 6) is not set. 14 signaled system error (sse) ? r/wc. 0 = no system error signaled. 1 = root port signaled a system e rror to the internal serr# logic. 13 received master abort (rma) ? r/wc. 0 = root port has not received a completion with uns upported request status from the backbone. 1 = root port received a completion wi th unsupported requ est status from the backbone. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 625 pci express* configuration registers 19.1.5 rid?revision identification register (pci express?d28:f0/f1/f2/f3) offset address: 08h attribute: ro default value: see bit description size: 8 bits 19.1.6 pi?programming interface register (pci express?d28:f0/f1/f2/f3) address offset: 09h attribute: ro default value: 00h size: 8 bits 12 received target abort (rta) ? r/wc. 0 = root port has not received a completion with completer abort from the backbone. 1 = root port received a completion wi th completer abort from the backbone. 11 signaled target abort (sta) ? r/wc. 0 = no target abort received. 1 = root port forwarded a targ et abort received from the do wnstream devi ce onto the backbone. 10:9 devsel# timing status (dev_sts) ? reserved per the pci express* base specification . 8 master data parity error detected (dped) ? r/wc. 0 = no data parity error received. 1 = root port received a completion with a data parity error on the backbone and pcimd.per (d28:f0/f1/f2/f3:04, bit 6) is set. 7 fast back to back capable (fb2bc) ? reserved per the pci express* base specification . 6 reserved 5 66 mhz capable ? reserved per the pci express* base specification . 4 capabilities list ? ro. hardwired to 1. indi cates the presence of a capabiliti es list. 3 interrupt status ? ro. indicates status of ho t-plug and power management interrupts on the root port that re sult 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 (d28:f0/f1/f2/f3:04h:bit 10). 2:0 reserved bit description bit description 7:0 revision id ? ro. bit description 7:0 programming interface ? ro. 00h = no specific register level programming interface defined. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 626 datasheet 19.1.7 scc?sub class code register (pci express?d28:f0/f1/f2/f3) address offset: 0ah attribute: ro default value: 04h size: 8 bits 19.1.8 bcc?base class code register (pci express?d28:f0/f1/f2/f3) address offset: 0bh attribute: ro default value: 06h size: 8 bits 19.1.9 cls?cache line size register (pci express?d28:f0/f1/f2/f3) address offset: 0ch attribute: r/w default value: 00h size: 8 bits 19.1.10 plt?primary late ncy timer register (pci express?d28:f0/f1/f2/f3) address offset: 0dh attribute: ro default value: 00h size: 8 bits bit description 7:0 sub class code (scc) ? ro. 04h = pci-to-pci bridge. bit description 7:0 base class code (bcc) ? ro. 06h = indicates the device is a bridge device. bit description 7:0 base class code (bcc) ? r/w. this is read/write but contains no functionality, per the pci express* base specification . bit description 7:3 latency count. reserved per the pci express* base specification. 2:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 627 pci express* configuration registers 19.1.11 headtyp?header type register (pci express?d28:f0/f1/f2/f3) address offset: 0eh attribute: ro default value: 81h size: 8 bits 19.1.12 bnum?bus number register (pci express?d28:f0/f1/f2/f3) address offset: 18?1ah attribute: r/w default value: 000000h size: 24 bits 19.1.13 iobl?i/o base and limit register (pci express?d28:f0/f1/f2/f3) address offset: 1ch?1dh attribute: r/w, ro default value: 0000h size: 16 bits bit description 7 multi-function device ? ro. 0 = single-func tion device. 1 = multi-function device. 6:0 configuration layout. hardwired to 01h , which indicates a pci-to-pci bridge. bit description 23:16 subordinate bus number (sbbn) ? r/w. this field indicates the highest pci bus number below the bridge. 15:8 secondary bus number (scbn) ? r/w. this field indicates the bus number the port. 7:0 primary bus number (pbn) ? r/w. this field indica tes the bus number of the backbone. bit description 15:12 i/o limit address (iola) ? r/w. this field contai ns the 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) ? r/o. this field indica tes that the bridge does not support 32-bit i/o addressing. 7:4 i/o base address (ioba) ? r/w. this field cont ains the 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) ? r/o. this field indi cates that the bridge does not support 32-bit i/o addressing. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 628 datasheet 19.1.14 ssts?secondary status register (pci express?d28:f0/f1/f2/f3) address offset: 1eh?1fh attribute: r/wc default value: 0000h size: 16 bits 19.1.15 mbl?memory base and limit register (pci express?d28:f0/f1/f2/f3) address offset: 20h?23h attribute: r/w default value: 00000000h size: 32 bits accesses that are within the rang es specified in this register will be sent to the attached device if cmd.mse (d28:f0/f1/f2/f3:04:bit 1) is set. accesses from the attached device that are outside the ranges specif ied will be forwarded to the backbone if cmd.bme (d28:f0/f1/f2/f3:04:bit 2) is set. the comparison performed is: mb ad[31:20] ml. bit description 15 detected parity error (dpe) ? r/wc. 0 = no error. 1 = the port received a poisoned tlp. 14 received system error (rse) ? r/wc. 0 = no error. 1 = the port received an err_fatal or err_nonfatal message from the device. 13 received master abort (rma) ? r/wc. 0 = unsupported request not received. 1 = the port received a completion with ?u nsupported request? status from the device. 12 received target abort (rta) ? r/wc. 0 = completion abort not received. 1 = the port received a completion with ?completion abort? status from the device. 11 signaled target abort (sta) ? r/wc. 0 = completion abort not sent. 1 = the port generated a completion with ?completion abort? status to the device. 10:9 secondary devsel# timing status (sdts): reserved per pci express* base specification . 8 data parity error detected (dpd) ? r/wc. 0 = conditions below did not occur. 1 = set when the bctrl.pere (d28:fo/f1/f2/f 3:3e: bit 0) is set, and either of the following two conditions occurs: ? port receives completion marked poisoned. ? port poisons a write request to the secondary side. 7 secondary fast back to back capable (sfbc) : reserved per pci express* base specification . 6 reserved 5 secondary 66 mhz capable (sc66) . reserved per pci express* base specification . 4:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 629 pci express* configuration registers 19.1.16 pmbl?prefetchable memory base and limit register (pci express?d28:f0/f1/f2/f3) address offset: 24h?27h attribute: r/w, ro default value: 00010001h size: 32 bits accesses that are within the ranges specified in this register will be sent to the device if cmd.mse (d28:f0/f1/f2/f3;04, bit 1) is set. accesses from the device that are outside the ranges specified will be forwarded to the backbone if cmd.bme (d28:f0/f1/f2/ f3;04, bit 2) is set. the comparison performed is: pmbu32:pmb ad[63:32]:ad[31:20] pmlu32:pml. 19.1.17 pmbu32?prefetchable me mory base upper 32 bits register (pci express?d28:f0/f1/f2/f3) address offset: 28h?2bh attribute: r/w default value: 00000000h size: 32 bits 19.1.18 pmlu32?prefetchable memory limit upper 32 bits register (pci express?d28:f0/f1/f2/f3) address offset: 2ch?2fh attribute: r/w default value: 00000000h size: 32 bits bit description 31:20 memory limit (ml) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine the upper 1- mb aligned value of the range. 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 of the range. 3:0 reserved bit description 31:20 prefetchable memory limit (pml) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine th e upper 1-mb aligned value of the range. 19:16 64-bit indicator (i64l) ? ro. this fi eld indicates support for 64-bit addressing 15:4 prefetchable memory base (pmb) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine th e lower 1-mb aligned value of the range. 3:0 64-bit indicator (i64b) ? ro. this fiel d indicates support for 64-bit addressing bit description 31:0 prefetchable memory base upper portion (pmbu) ? r/w. this field contains the upper 32-bits of the pref etchable address base. bit description 31:0 prefetchable memory limit upper portion (pmlu) ? r/w. this field contains the upper 32-bits of the pref etchable address limit. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 630 datasheet 19.1.19 capp?capabilities list pointer register (pci express?d28:f0/f1/f2/f3) address offset: 34h attribute: r0 default value: 40h size: 8 bits 19.1.20 intr?interrupt information register (pci express?d28:f0/f1/f2/f3) address offset: 3ch?3dh attribute: r/w, ro default value: see bit description size: 16 bits 19.1.21 bctrl?bridge control register (pci express?d28:f0/f1/f2/f3) address offset: 3eh?3fh attribute: r/w default value: 0000h size: 16 bits bit description 7:0 capabilities pointer (ptr) ? ro. this field indicates th at the pointer for the first entry in the capabilities list is at 40h in configuration space. bit description 15:8 interrupt pin (ipin) ? ro. this field indicates the in terrupt pin driven by the root port. at reset, this register takes on the fo llowing values that reflect the reset state of the d28ip register in chipset configuration space: note: the value that is programmed into d28ip is always reflected in this register. 7:0 interrupt line (iline) ? r/w. default = 00h. this field is a software written value to indicate which interrupt line (vector) the interrupt is connected to. no hardware action is taken on this register. port reset value 1d28ip.p1ip 2d28ip.p2ip 3d28ip.p3ip 4d28ip.p4ip bit description 15:12 reserved 11 discard timer serr# enable (dtse) . reserved per pci express* base specification, revision 1.0a 10 discard timer status (dts) . reserved per pci express* base specification, revision 1.0a. 9 secondary discard timer (sdt) . reserved per pci express* base specification, revision 1.0a. 8 primary discard timer (pdt) . reserved per pci express* base specification, revision 1.0a. 7 fast back to back enable (fbe) . reserved per pci express* base specification, revision 1.0a. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 631 pci express* configuration registers 19.1.22 clist?capabilities list register (pci express?d28:f0/f1/f2/f3) address offset: 40?41h attribute: ro default value: 8010h size: 16 bits 6 secondary bus reset (sbr) ? r/w. this bit triggers a hot reset on the pci express* port. 5 master abort mode (mam): reserved per express specification. 4 vga 16-bit decode (v16) ? r/w. 0 = vga range is enabled. 1 = the i/o aliases of the vga range (see bc trl:ve definition belo w), are not enabled, and only the base i/o ranges can be decoded 3 vga enable (ve) ? r/w. 0 = the ranges below will not be claimed off the backbone by the root port. 1 = the following ranges will be claime d off the backbone by the root port: ? memory ranges a0000h?bffffh ? i/o ranges 3b0h ? 3bbh and 3c0h ? 3dfh, an d all aliases of bits 15:10 in any combination of 1s 2 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. 0 = the root port will not block any forwarding from the backbone as de scribed below. 1 = the root port will block any forwarding from the backbone to the device of i/o transactions addressing the last 768 by tes in each 1-kb block (offsets 100h to 3ffh). 1 serr# enable (se) ? r/w. 0 = the messages de scribed below are not forwarded to the backbone. 1 = err_cor, err_nonfatal, and err_fatal messages received are forwarded to the backbone. 0 parity error respon se enable (pere) ? r/w. 0 = poisoned write tlps and completions indicating poisoned tlps will not set the ssts.dpd (d28:f0/f1/f2/f3/f4/f5:1e, bit 8). 1 = poisoned write tlps and completions indicating poisoned tlps will set the ssts.dpd (d28:f0/f1/f2/f3/f4/f5:1e, bit 8). bit description bit description 15:8 next capabili ty (next) ? ro. value of 80h indicates the location of the next pointer. 7:0 capability id (cid) ? ro. this field indi cates this is a pci express* capability. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 632 datasheet 19.1.23 xcap?pci express* capabilities register (pci express?d28:f0/f1/f2/f3) address offset: 42h?43h attribute: r/wo, ro default value: 0041h size: 16 bits 19.1.24 dcap?device capabilities register (pci express?d28:f0/f1/f2/f3) address offset: 44h?47h attribute: ro default value: 00000fe0h size: 32 bits bit description 15:14 reserved 13:9 interrupt message number (imn) ? ro. the chipset does not have multiple msi interrupt numbers. 8 slot implemented (si) ? r/wo. this field indicates whether the root port is connected to a slot. slot support is platform specific. bios programs this field, and it is maintained until a platform reset. 7:4 device / port type (dt) ? ro. this field indicates this is a pci express* root port. 3:0 capability version (cv) ? ro. this field indicates pci express 1.0. bit description 31:28 reserved 27:26 captured slot power limit scale (csps) ? ro. not supported. 25:18 captured slot power limit value (cspv) ? ro. not supported. 17:15 reserved 14 power indicator present (pip) ? ro. this bit indicates no power indicator is present on the root port. 13 attention indicator present (aip) ? ro. this bit indicates no attention indicator is present on the root port. 12 attention button present (abp) ? ro. this bit indicates no attention button is present on the root port. 11:9 endpoint l1 acceptable latency (e1al) ? ro. this field indicates more than 4 s. this field essentially has no meaning for ro ot ports since root ports are not endpoints. 8:6 endpoint l0 acceptable latency (e0al) ? ro. this field indica tes more than 64 s. this field essentially has no meaning for ro ot ports since root ports are not endpoints. 5 extended tag field supported (etfs) ? ro. this bit indicates that 8-bit tag fields are supported. 4:3 phantom functions supported (pfs) ? ro. this field indicates no phantom functions supported. 2:0 max payload size supported (mps) ? ro. this field indicates the maximum payload size supported is 128b. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 633 pci express* configuration registers 19.1.25 dctl?device control register (pci express?d28:f0/f1/f2/f3) address offset: 48h?49h attribute: r/w, ro default value: 0000h size: 16 bits 19.1.26 dsts?device status register (pci express?d28:f0/f1/f2/f3) address offset: 4ah?4bh attribute: r/wc, ro default value: 0010h size: 16 bits bit description 15 reserved 14:12 max read request size (mrrs) ? ro. hardwired to 0. 11 enable no snoop (ens) ? ro. not supported. the root port will not issue non-snoop requests. 10 aux power pm enable (apme) ? r/w. the os will set this bit to 1 if the device connected has detected aux power. it has no effect on the r oot port otherwise. 9 phantom functions enable (pfe) ? ro. not supported. 8 extended tag field enable (etfe) ? ro. not supported. 7:5 max payload size (mps) ? r/w. the root port only supports 128-b payloads, regardless of the programming of this field. 4 enable relaxed ordering (ero) ? ro. not supported. 3 unsupported request reporting enable (ure) ? r/w. 0 = disable. the root port will ig nore unsupported request errors. 1 = enable. the root port will generate er rors when detecting an unsupported request. 2 fatal error reporting enable (fee) ? r/w. 0 = disable. the root port will ignore fatal errors. 1 = enable. the root port will generate errors when detecting a fatal error. 1 non-fatal error reporting enable (nfe) ? r/w. 0 = disable. the root port will ignore non-fatal errors. 1 = enable. the root port will generate errors when detecting a non-fatal error. 0 correctable error reporting enable (cee) ? r/w. 0 = disable. the root port will ignore correctable errors. 1 = enable. the root port will generate errors when detecting a correctable error. bit description 15:6 reserved 5 transactions pending (tdp) ? ro. this bit has no mean ing for the root port since only one transaction may be pending to the ch ipset, so a read of this bit cannot occur until it has already returned to 0. 4 aux power detected (apd) ? ro. the root port contains aux power for wakeup. 3 unsupported request detected (urd) ? r/wc. this bit indicates an unsupported request was detected. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 634 datasheet 19.1.27 lcap?link capa bilities register (pci express?d28:f0/f1/f2/f3) address offset: 4ch ? 4fh attribute: r/w, ro default value: see bit description size: 32 bits 2 fatal error detected (fed) ? r/wc. this bit indicates a fatal error was detected. 0 = fatal has not occurred. 1 = a fatal error occurred from a data link pr otocol error, link training error, buffer overflow, or malformed tlp. 1 non-fatal error detected (nfed) ? r/wc. this bit indicates a non-fatal error was detected. 0 = non-fatal has not occurred. 1 = a non-fatal error occurred from a pois oned tlp, unexpected completions, unsupported requests, completer abort, or completer timeout. 0 correctable error detected (ced) ? r/wc. this bit indicates a correctable error was detected. 0 = correctable has not occurred. 1 = the port received an internal correcta ble error from receiver errors / framing errors, tlp crc error, dllp crc error, replay num rollover, replay timeout. bit description bit description 31:24 port number (pn) ? ro. this field indicates the po rt number for the root port. this value is different for each implemented port: 23:21 reserved 20 link active reporting capable (larc) ? ro. hardwired to 1 to indicate that this port supports the optional capability of repo rting the dl_active state of the data link control and management state machine. 19:18 reserved 17:15 l1 exit latency (el1) ? ro. set to 010b to indicate an exit latency of 2 s to 4 s. 14:12 l0s exit latency (el0) ? ro. this field indicates as exit latency based upon common-clock configuration. note: lclt.ccc is at d28:f0 /f1/f2/f3:50h:bit 6 function port # value of pn field d28:f0 1 01h d28:f1 2 02h d28:f2 3 03h d28:f3 4 04h lclt.ccc value of el0 (these bits) 0 mpc.ucel (d28:f0/f1/f2/f3:d8h:bits20:18) 1 mpc.ccel (d28:f0/f1/f2/f3:d8h:bits17:15) www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 635 pci express* configuration registers 19.1.28 lctl?link control register (pci express?d28:f0/f1/f2/f3) address offset: 50h-51h attribute: r/w, wo, ro default value: 0000h size: 16 bits 11:10 active state link pm support (apms) ? r/wo. this field indicates what level of active state link power management is supported on the root port. 9:4 maximum link width (mlw) ? ro. for the root ports, several values can be taken, based upon the value of the chipset config uration register fiel d rpc.pc1 (chipset configuration registers:offset 0224h:bits1:0) for ports 1?4. 3:0 maximum link speed (mls) ? ro. set to 1h to indicate the link speed is 2.5 gb/s. bit description bits definition 00b neither l0s nor l1 are supported 01b l0s entry supported 10b l1 entry supported 11b both l0s and l1 entry supported port # rpc.pc1=00b rpc.pc1=11b 1 01h 04h 2 01h 01h 3 01h 01h 4 01h 01h bit description 15:8 reserved 7 extended synch (es) ? r/w. 0 = extended synch disabled. 1 = forces extended transmission of fts ordered sets in fts and extra ts2 at exit from l1 prior to entering l0. 6 common clock configuration (ccc) ? r/w. 0 = the chipset and device are not using a common reference clock. 1 = the chipset and device are operating with a distributed co mmon reference clock. 5 retrain link (rl) ? wo. 0 = this bit always returns 0 when read. 1 = the root port will train its downstream link. note: software uses lsts.lt (d28:f0/f1/f2/f3/f4/f5:52, bit 11) to check the status of training. 4 link disable (ld) ? r/w. 0 = link enabled. 1 = the root port will disable the link. 3 read completion boundary control (rcbc) ? ro. this bit indicates that the read completion boundary is 64 bytes. 2 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 636 datasheet 19.1.29 lsts?link status register (pci express?d28:f0/f1/f2/f3) address offset: 52h?53h attribute: ro default value: see bit description size: 16 bits 1:0 active state link pm control (apmc) ? r/w. this bit indi cates whether the root port should enter l0s or l1 or both. bit description 00b disabled 01b l0s entry is enabled 10b l1 entry is enabled 11b l0s and l1 entry enabled bit description 15:14 reserved 13 data link layer active (dlla) ? ro. d 0 = data link control and management state machine is not in the dl_active state. (default) 1 = data link control and management st ate machine is in the dl_active state. 12 slot clock configuration (scc) ? ro. set to 1b to indicate that the chipset uses the same reference clock as on the platform and does no t generate its own clock. 11 link training (lt) ? ro. 0 = link training completed. (default) 1 = link training is occurring. 10 link training error (lte ) ? ro. not supported. set value is 0b. 9:4 negotiated link width (nlw) ? ro. this field indicates the negotiated width of the given pci express* link. the co ntents of this nlw field is undefined if the link has not successfully trained. note: 000001b = x1 link width, 000010b =x2 linkwidth (not supported), 000100 = x4 linkwidth 3:0 link speed (ls) ? ro. this field indicates the nego tiated link speed of the given pci express* link. 01h = link is 2.5 gb/s. port # possible values 1 000001b, 000010b, 000100b 2 000001b 3 000001b 4 000001b www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 637 pci express* configuration registers 19.1.30 slcap?slot capa bilities register (pci express?d28:f0/f1/f2/f3) address offset: 54h ? 57h attribute: r/wo, ro default value: 00000060h size: 32 bits bit description 31:19 physical slot number (psn) ? r/wo. this is a value that is unique to the slot number. bios sets this field and it remains set until a platform reset. 18:17 reserved 16:15 slot power limit scale (sls) ? r/wo. this field specifies the scale used for the slot power limit value. bios sets this field and it remains set until a platform reset. range of values: 00b = 1.0 x 01b = 0.1 x 10b = 0.01 x 11b = 0.001 x 14:7 slot power limit value (slv) ? r/wo. this field spec ifies the upper limit (in conjunction with sls value), on the upper li mit on power supplied by the slot. the two values together indicate the amount of powe r in watts allowed for the slot. power limit (in watts) is calculated by multiplying the va lue in this field by the value in the slot power limit scale field. bios sets this field and it remain s set until a platform reset. 6 hot plug capable (hpc) ? ro. 1b = hot-plug is supported. 5 hot plug surprise (hps) ? ro. 1b = device may be removed from th e slot without prior notification. 4 power indicator present (pip) ? ro. 0b = power indicator led is not present for this slot. 3 attention indicator present (aip) ? ro. 0b = attention indicator led is not present for this slot. 2 mrl sensor present (msp) ? ro. 0b = mrl sensor is not present. 1 power controller present (pcp) ? ro. 0b = power controller is no t implemented for this slot. 0 attention button present (abp) ? ro. 0b =attention button is not implemented for this slot. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 638 datasheet 19.1.31 slctl?slot control register (pci express?d28:f0/f1/f2/f3) address offset: 58h ? 59h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:13 reserved 12 link active changed enable (lace) ? rw. 0 = disable. 1 = enables generation of a hot plug interr upt when the data link layer link active field (d28:f0/f1/f2/f3/f4/f5:52h:bit 13) is changed. 11 reserved 10 power controller control (pcc) ? ro.this bit has no meaning for module based hot-plug. 9:8 power indicator control (pic) ? r/w. when read, the cu rrent state of the power indicator is returned. when written, the appropriate power_indicator_* messages are sent. defined encodings are: 7:6 attention indicator control (aic) ? r/w. when read, th e current state of the attention indicator is returned. when writ ten, the appropriate attention_indicator_* messages are sent. defined encodings are: 5 hot plug interrupt enable (hpe) ? r/w. 0 = disable. hot plug interrupts based on hot-plug events is disabled. 1 = enables generation of a hot-plug interrupt on enabled hot-plug events. 4 command completed interrupt enable (cce) ? r/w. 0 = disable. hot plug interrupts based on command completions is disabled. 1 = enables the generation of a hot-plug interrupt when a command is completed by the hot-plug controller. 3 presence detect changed enable (pde) ? r/w. 0 = disable. hot plug interrupts based on pr esence detect logic changes is disabled. 1 = enables the generation of a hot-plug interrupt or wake message when the presence detect logic changes state. 2 mrl sensor changed enable (mse) ? r/w. mse not supported. 1 power fault detected enable (pfe) ? r/w. pfe not supported. bits definition 00b reserved 01b on 10b blink 11b off bits definition 00b reserved 01b on 10b blink 11b off www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 639 pci express* configuration registers 19.1.32 slsts?slot status register (pci express?d28:f0/f1/f2/f3) address offset: 5ah ? 5bh attribute: r/wc, ro default value: 0000h size: 16 bits 0 attention button pressed enable (abe) ? r/w. when set, enables the generation of a hot-plug interrupt when the attention button is pressed. 0 = disable. hot plug interrupts based on the attention button being pressed is disabled. 1 = enables the generation of a hot-plug interrupt when the at tention button is pressed. bit description bit description 15:9 reserved 8 link active stat e changed (lasc) ? r/wc. 0 = no change. 1 = value reported in data link layer link active field of the li nk status register (d28:f0/f1/f2/f3/f4/f5:52h:bit 13) is change d. in response to a data link layer state changed event, software must read data link layer link active field of the link status register to determine if the link is active before initiating configuration cycles to the hot plugged device. 7 reserved 6 presence detect state (pds) ? ro. if xcap.si (d28:f0/f1/f2/f3/f4/f5:42h:bit 8) is set indicating that this root po rt spawns a slot), then this bit: 0 = slot is empty. 1 = slot has a device connected. otherwise; if xcap.si is cleared, this bit is always set to 1. 5 mrl sensor state (ms) ? reserved as the mrl sensor is not implemented. 4 command completed (cc) ? r/wc. 0 = issued command not completed. 1 = the hot-plug controller completed an is sued command. this is set when the last message of a command is sent and indicates that software can write a new command to the slot controller. 3 presence detect changed (pdc) ? r/wc. 0 = no change in the pds bit. 1 = the pds bit changed states. 2 mrl sensor changed (msc) ? reserved as the mrl sensor is not implemented. 1 power fault detected (pfd) ? reserved as a power controller is not implemented. 0 attention button pressed (abp) ? r/wc. 0 = the attention button has not been pressed. 1 = the attention bu tton is pressed. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 640 datasheet 19.1.33 rctl?root control register (pci express?d28:f0/f1/f2/f3) address offset: 5ch ? 5dh attribute: r/w default value: 0000h size: 16 bits 19.1.34 rsts?root status register (pci express?d28:f0/f1/f2/f3) address offset: 60h ? 63h attribute: r/wc, ro default value: 00000000h size: 32 bits bit description 15:4 reserved 3 pme interrupt enable (pie) ? r/w. 0 = interrupt gene ration disabled. 1 = interrupt generation enab led when pcists.interrupt status (d28:f0/f1/f2/f3/f4/ f5:60h, bit 16) is in a set state (either due to a 0 to 1 transition, or due to this bit being set with rsts.is already set). 2 system error on fatal error enable (sfe) ? r/w. 0 = disable. an serr# will not be generated. 1 = enable. an serr# will be generated, assuming cm d.see (d28:f0/f1/f2/f3/f4/ f5:04, bit 8) is set, if a fatal error is re ported by any of the devices in the hierarchy of this root port, including fa tal errors in this root port. 1 system error on non-fatal error enable (sne) ? r/w. 0 = disable. an serr# will not be generated. 1 = enable. an serr# will be generated, assuming cm d.see (d28:f0/f1/f2/f3/f4/ f5:04, bit 8) is set, if a non-fatal error is reported by any of the devices in the hierarchy of this root port, including non-fatal errors in this root port. 0 system error on correctable error enable (sce) ? r/w. 0 = disable. an serr# will not be generated. 1 = enable. an serr# will be generated, assuming cm d.see (d28:f0/f1/f2/f3/f4/ f5:04, bit 8) if a correctable error is reported by any of the devices in the hierarchy of this root port, incl uding correctable errors in this root port. bit description 31:18 reserved 17 pme pending (pp) ? ro. 0 = indicates no more pmes are pending. 1 = indicates another pme is pending (this is im plicit because of the de finition of this bit being 1). hardware will set the pme status bit again and update the requestor id appropriately. the pme pending bit is clea red by hardware if no more pmes are pending. 16 pme status (ps) ? r/wc. 0 = pme was not asserted. 1 = pme was asserted by the requestor id in rid. subsequent p mes are kept pending until this bit is cleared. 15:0 pme requestor id (rid) ? ro. this field indicates the pci requestor id of the last pme requestor. the value in this field is valid only when ps is set. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 641 pci express* configuration registers 19.1.35 mid?message signaled in terrupt identifi ers register (pci express?d28:f0/f1/f2/f3) address offset: 80h?81h attribute: ro default value: 9005h size: 16 bits 19.1.36 mc?message signaled inte rrupt message control register (pci express?d28:f0/f1/f2/f3) address offset: 82?83h attribute: r/w, ro default value: 0000h size: 16 bits 19.1.37 ma?message signaled interrupt message address register (pci express?d28:f0/f1/f2/f3) address offset: 84h ? 87h attribute: r/w default value: 00000000h size: 32 bits bit description 15:8 next pointer (next) ? ro. this field indicates the location of the next pointer in the list. 7:0 capability id (cid) ? ro. capabilities id indicates msi. bit description 15:8 reserved 7 64 bit address capable (c64) ? ro. capable of generating a 32-bit message only. 6:4 multiple message enable (mme) ? r/w. these bits are r/w for software compatibility, but only one message is ever sent by the root port. 3:1 multiple message capable (mmc) ? ro. only one message is required. 0 msi enable (msie) ? r/w. 0 = disabled. 1 = enabled and traditional interrupt pins are not used to generate interrupts. note: cmd.bme (d28:f0/f1/f2/f3:04h:bit 2) must be set for an msi to be generated. if cmd.bme is cleared, and th is bit is set, no interrupts (not even pin based) are generated. bit description 31:2 address (addr) ? r/w. this field contains the lo wer 32 bits of the system specified message address; al ways dword aligned. 1:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 642 datasheet 19.1.38 md?message signaled in terrupt message data register (pci express?d28:f0/f1/f2/f3) address offset: 88h ? 89h attribute: r/w default value: 0000h size: 16 bits 19.1.39 svcap?subsystem vend or capability register (pci express?d28:f0/f1/f2/f3) address offset: 90h ? 91h attribute: ro default value: a00dh size: 16 bits 19.1.40 svid?subsystem vendor identification register (pci express?d28:f0/f1/f2/f3) address offset: 94h ? 97h attribute: r/wo default value: 00000000h size: 32 bits 19.1.41 pmcap?power management capability register (pci express?d28:f0/f1/f2/f3) address offset: a0h ? a1h attribute: ro default value: 0001h size: 16 bits bit 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 lo wer word (pci ad[15:0]) during the data phase of the msi memory write transaction. bit description 15:8 next capability (next) ? ro. this field indicates the lo cation of the next pointer in the list. 7:0 capability identifier (cid) ? ro. value of 0dh indicates this is a pci bridge subsystem vendor capability. bit description 31:16 subsystem identifier (sid) ? r/wo. this field indicates the subsystem as identified by the vendor. this field is write once and is locked down until a bridge reset occurs (not the pci bus reset). 15:0 subsystem vendor identifier (svid) ? r/wo. this field indicates the manufacturer of the subsystem. this field is write once an d is locked down until a bridge reset occurs (not the pci bus reset). bit description 15:8 next capability (next) ? ro. this field indicates that this is the last item in the list. 7:0 capability identifier (cid) ? ro. value of 01h indicates this is a pci power management capability. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 643 pci express* configuration registers 19.1.42 pmc?pci power manageme nt capabilities register (pci express?d28:f0/f1/f2/f3) address offset: a2h ? a3h attribute: ro default value: c802h size: 16 bits 19.1.43 pmcs?pci power mana gement control and status register (pci express?d28:f0/f1/f2/f3) address offset: a4h ? a7h attribute: r/w, ro default value: 00000000h size: 32 bits bit description 15:11 pme_support (pmes) ? ro. this field indicates pme# is supported for states d0, d3 hot and d3 cold . the root port does not generate p me#, but reporting that it does is necessary for some legacy operating system s to enable pme# in devices connected behind this root port. 10 d2_support (d2s) ? ro. the d2 state is not supported. 9 d1_support (d1s) ? ro the d1 state is not supported. 8:6 aux_current (ac) ? ro. this field reports 375 ma maximum suspend well current required when in the d3 cold state. 5 device specific initialization (dsi) ? ro. this bit indicates that no device-specific initialization is required. 4 reserved 3 pme clock (pmec) ? ro. this bit indicates that pci cl ock is not required to generate pme#. 2:0 version (vs) ? ro. this field indicates support for revision 1.1 of the pci power management specification . bit description 31:24 reserved 23 bus power / clock control enable (bpce) . reserved per pci express* base specification, revision 1.0a . 22 b2/b3 support (b23s) . reserved per pci express* base specification, revision 1.0a . 21:16 reserved 15 pme status (pmes) ? ro. this bit indicates a pme was received on the downstream link. 14:9 reserved 8 pme enable (pmee) ? r/w. indicates pme is enabled. the root port takes no action on this bit, but it must be r/w for some legacy operating systems to enable pme# on devices connected to this root port. 0 = disable. 1 = enable. note: this bit is sticky and resides in the resume well. the rese t for this bit is rsmrst# which is not assert ed during a warm reset. 7:2 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 644 datasheet 19.1.44 mpc?miscellaneous port configuration register (pci express?d28:f0/f1/f2/f3) address offset: d8h ? dbh attribute: r/w default value: 00110000h size: 32 bits 1:0 power state (ps) ? r/w. this field is used both to determine the current power state of the root port and to set a new power state. the values are: 00 = d0 state 11 = d3 hot state note: when in the d3 hot state, the controller?s config uration space is available, but the i/o and memory spaces are not. type 1 configuration cycles are also not accepted. interrupts are not required to be blocked as software will disable interrupts prior to placing the port into d3hot. if software attempts to write a ?10? or ?01? to these bits, the write will be ignored. bit description bit description 31 power management sci enable (pmce) ? r/w. 0 = disable. sci generation based on a power management ev ent is disabled. 1 = enables the root port to generate sci whenever a power management event is detected. 30 hot plug sci enable (hpce) ? r/w. 0 = disable. sci generation based on a hot-plug event is disabled. 1 = enables the root port to generate sci whenever a hot-plug event is detected. 29 link hold off (lho) ? r/w. 0 = not in link hold off. 1 = the port will not take any tlp. this is used during loopback mode to fill up the downstream queue. 28 address translator enable (ate) ? r/w. this bit is used to enable address translation via the at bits in this register during loopback mode. 0 = disable. 1 = enable. 27 reserved . 26 invalid receive bus number check enable (irbnce) ? r/w. 0 = disable. 1 = enable. receive transaction layer will sign al an error if the bus number of a memory request does not fall within the range be tween scbn and sbbn. if this check is enabled and the request is a memory writ e, it is treated as an unsupported request. if this check is enabled and th e request is a non-posted memory read request, the request is considered a malformed tlp and a fatal error. note: messages, io, configuratio n, and completions are no t checked for valid bus number. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 645 pci express* configuration registers 25 invalid receive range check enable (irrce) ? r/w. 0 = disable. 1 = enable. receive transaction layer will treat the tlp as an unsupported request error if the address range of a memory re quest does not outside the range between prefetchable and non-prefet chable base and limit. note: messages, i/o, configuration, and co mpletions are not checked for valid address ranges. 24 bme receive check enable (bmerce) ? r/w. 0 = disable. 1 = enable. receive transaction layer will treat the tlp as an unsupported request error if a memory read or write request is received and the bus master enable bit is not set. note: messages, io, configuration, and completions are not checked for bme. 23:21 reserved 20:18 unique clock exit latency (ucel) ? r/w. this value represents the l0s exit latency for unique-clock configurations (lctl.ccc = 0) (d 28:f0/f1/f2/f3/f4/ f5:offset 50h:bit 6). it defaults to 512 ns to less than 1 s, but may be overridden by bios. 17:15 common clock exit latency (ccel) ? r/w. this value represents the l0s exit latency for common-clock co nfigurations (lctl.ccc = 1) (d28:f0/f1/f2 /f3:offset 50h:bit 6). it defaults to 128 ns to less than 256 ns, but may be overridden by bios. 14:8 reserved 7 port i/oxapic enable (pae) ? r/w. 0 = hole is disabled. 1 = a range is opened through the bri dge for the followin g memory addresses: 6:2 reserved 1 hot plug smi enable (hpme) ? r/w. 0 = disable. smi generati on based on a hot-plug event is disabled. 1 = enables the root port to generate smi whenever a hot-plug event is detected. 0 power management sm i enable (pmme) ? r/w. 0 = disable. smi generation based on a power management event is disabled. 1 = enables the root port to generate sm i whenever a power management event is detected. bit description port # address 1 fec1_0000h ? fec1_7fffh 2 fec1_8000h ? fec1_ffffh 3 fec2_0000h ? fec2_7fffh 4 fec2_8000h ? fec2_ffffh www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 646 datasheet 19.1.45 smscs?smi/sci status register (pci express?d28:f0/f1/f2/f3) address offset: dch ? dfh attribute: r/wc default value: 00000000h size: 32 bits bit description 31 power management sci status (pmcs) ? r/wc. 0 = interrupt not needed. 1 = pme control logic needs to generate an interrupt, and this interrupt has been routed to generate an sci. 30 hot plug sci status (hpcs) ? r/wc. 0 = interrupt not needed. 1 = hot-plug controller needs to generate an interrupt, and has this interrupt been routed to generate an sci. 29:5 reserved 4 hot plug link active state changed smi status (hplas) ? r/wc. 0 = no change 1 = slsts.lasc (d28:f0/f1/f2/f3:5a, bit 8) transitioned from 0-to-1, and mpc.hpme (d28:f0/f1/f2/f3:d8, bit 1) is set. when th is bit is set, an sm i# will be generated. 3 hot plug command comple ted smi status (hpccm) ? r/wc. 0 = no change 1 = slsts.cc (d28:f0/f1/f2/f3/:5a, bit 4) transitioned from 0-to-1, and mpc.hpme (d28:f0/f1/f2/f3:d8, bit 1) is set. when th is bit is set, an sm i# will be generated. 2 hot plug attention button smi status (hpabm) ? r/wc. 0 = no change 1 = slsts.abp (d28:f0/f1/f2/f3:5a, bit 0) transitioned from 0-to-1, and mpc.hpme (d28:f0/f1/f2/f3:d8, bit 1) is set. when th is bit is set, an sm i# will be generated. 1 hot plug presence detect smi status (hppdm) ? r/wc. 0 = no change 1 = slsts.pdc (d28:f0/f1/f2/f3:5a, bit 3) transitions from 0-to-1, and mpc.hpme (d28:f0/f1/f2/f3:d8, bit 1) is set. when th is bit is set, an sm i# will be generated. 0 power management smi status (pmms) ? r/wc. 0 = no change 1 = rsts.ps (d28:f0/f1/f2/f3:60, bit 16) transitions from 0-to-1, and mpc.pmme (d28:f0/f1/f2/f3:d8, bit 1) is set. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 647 pci express* configuration registers 19.1.46 rpdcgen - root port dy namic clock gating enable (pci express-d28:f0/f1/ f2/f3) (netbook only) address offset: e1h attribute: r/w default value: 00h size: 8-bits 19.1.47 ipws?intel ? pro/wireless 3945abg status (pci express?d28:f0/f1/ f2/f3) (netbook only) address offset: e2h?e3h attribute: ro default value: 0007h size: 16 bits 19.1.48 vch?virtual channel ca pability header register (pci express?d28:f0/f1/f2/f3) address offset: 100h ? 103h attribute: ro default value: 18010002h size: 32 bits bits description 7:4 reserved . ro 3 shared resource dynamic link cl ock gating enable (srdlcgen) ? rw. 0 = disables dynamic clock gating of the shared resource link clock domain. 1 = enables dynamic clock gating on the root port shared resource link clock domain. only the value from port 1 is used for ports 1?4. 2 shared resource dynamic backbone clock gate enable (srdbcgen) ? rw. 0 = disables dynamic clock gating of the shared resource backbone clock domain. 1 = enables dynamic clock gating on the r oot port shared reso urce backbone clock domain. only the value from port 1 is used for ports 1?4. 1 root port dynamic link clock gate enable (rpdlcgen) ? rw. 0 = disables dynamic clock gating of the root port link clock domain. 1 = enables dynamic clock gating on the root port link clock domain. 0 root port dynamic backbone clock gate enable (rpdbcgen) ? rw. 0 = disables dynamic clock gating of th e root port backbone clock domain. 1 = enables dynamic clock gating on th e root port backbone clock domain. bit description 15 intel pro/wireless 3945abg status (ipwstat) ? ro. this bit is set if the link has trained to l0 in intel pro/wireless 3945abg mode. 14:0 reserved bit description 31:20 next capability offset (nco) ? ro. this field indicates the next item in the list. 19:16 capability version (cv) ? ro. this field indicates that this is version 1 of the capability structure by the pci sig. 15:0 capability id (cid) ? ro. this field indicates that this is the virtual channel capability item. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 648 datasheet 19.1.49 vcap2?virtual channe l capability 2 register (pci express?d28:f0/f1/f2/f3) address offset: 108h ? 10bh attribute: ro default value: 00000001h size: 32 bits 19.1.50 pvc?port virtual ch annel control register (pci express?d28:f0/f1/f2/f3) address offset: 10ch ? 10dh attribute: r/w default value: 0000h size: 16 bits 19.1.51 pvs ? port virtual channel status register (pci express?d28:f0/f1/f2/f3) address offset: 10eh ? 10fh attribute: ro default value: 0000h size: 16 bits bit description 31:24 vc arbitration table offset (ato) ? ro. this field indicates that no table is present for vc arbitration since it is fixed. 23:0 reserved . bit description 15:4 reserved . 3:1 vc arbitration select (as) ? r/w. this field indicates which vc should be programmed in the vc arbitration table. the root port takes no action on the setting of this field since there is no arbitration table. 0 load vc arbitration table (lat) ? r/w. this bit indicates that the table programmed should be loaded into the vc ar bitration table. this bit always returns 0 when read. bit description 15:1 reserved . 0 vc arbitration table status (vas) ? ro. this bit indicates the coherency status of the vc arbitration table when it is being update d. this field is always 0 in the root port since there is no vc arbitration table. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 649 pci express* configuration registers 19.1.52 v0cap ? virtual channel 0 resource capability register (pci express?d28:f0/f1/f2/f3) address offset: 110h ? 113h attribute: ro default value: 00000001h size: 32 bits 19.1.53 v0ctl ? virtual channel 0 resource control register (pci express?d28:f0/f1/f2/f3) address offset: 114h ? 117h attribute: r/w, ro default value: 800000ffh size: 32 bits 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; 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. this field indicates that this vc uses fixed port arbitration. bit description 31 virtual channel enable (en ) ? ro. always set to 1. virtual channel 0 cannot be disabled. 30:27 reserved . 26:24 virtual channel identifier (vcid) ? ro. this field indicate s the id to use for this virtual channel. 23:20 reserved . 19:17 port arbitration select (pas) ? r/w. this field indicate s which port table is being programmed. the root complex takes 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 port does not implement an arbitration table for this virtual channel. 15:8 reserved . www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 650 datasheet 19.1.54 v0sts ? virtual channel 0 resource status register (pci express?d28:f0/f1/f2/f3) address offset: 11ah ? 11bh attribute: ro default value: 0000h size: 16 bits 19.1.55 ues ? uncorrectable error status register (pci express?d28:f0/f1/f2/f3 address offset: 144h ? 147h attribute: r/wc, ro default value: 00000000000x0xxx 0x0x0000000x0000bsize:32 bits this register maintains its state through a platform reset. it loses its state upon suspend. 7:1 transaction class / virtual channel map (tvm) ? r/w. this field 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 . transaction class 0 must always be mapped to vc0. bit description bit transaction class 7 transaction class 7 6 transaction class 6 5 transaction class 5 4 transaction class 4 3 transaction class 3 2 transaction class 2 1 transaction class 1 0 transaction class 0 bit description 15:2 reserved . 1 vc negotiation pending (np) ? ro. 0 = negotiation is not pending. 1 = virtual channel is still being negotiated with ingress ports. 0 port arbitration tables status (ats) . there is no port arbitration table for this vc; this bit is reserved as 0. bit description 31:21 reserved 20 unsupported request error status (ure) ? r/wc. 0 = unsupported request was not received. 1 = unsupported requ est was received. 19 ecrc error status (ee) ? ro. ecrc is not supported. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 651 pci express* configuration registers 19.1.56 uem ? uncorrec table error mask (pci express?d28:f0/f1/f2/f3) address offset: 148h ? 14bh attribute: r/wo, ro default value: 00000000h size: 32 bits when set, the corresponding error in the ue s register is masked, and the logged error will cause no action. when cleared, the corresponding error is enabled. 18 malformed tlp status (mt) ? r/wc. 0 = malformed tlp was not received. 1 = malformed tlp was received. 17 receiver overflow status (ro) ? r/wc. 0 = receiver overflow did not occur. 1 = receiver overflow occurred. 16 unexpected completion status (uc) ? r/wc. 0 = unexpected completion was not received. 1 = unexpected completion was received. 15 completion abort status (ca) ? r/wc. 0 = completer abort was not received. 1 = completer abort was received. 14 completion timeout status (ct) ? r/wc. 0 = completion did not time out. 1 = completion timed out. 13 flow control protocol error status (fcpe) ? ro. flow control protocol errors not supported. 12 poisoned tlp status (pt) ? r/wc. 0 = poisoned tlp was not received. 1 = poisoned tlp was received. 11:5 reserved 4 data link protocol error status (dlpe) ? r/wc. 0 = data link protocol error did not occur. 1 = data link protocol error occurred. 3:1 reserved 0 training error status (te) ? ro. training errors not supported. bit description bit description 31:21 reserved 20 unsupported request error mask (ure) ? r/wo. 0 = the corresponding error in the ues regi ster (d28:f0/f1/f2/f3:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3:144) is masked. 19 ecrc error mask (ee) ? ro. ecrc is not supported. 18 malformed tlp mask (mt) ? r/wo. 0 = the corresponding error in the ues regi ster (d28:f0/f1/f2/f3:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3:144) is masked. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 652 datasheet 19.1.57 uev ? uncorrecta ble error severity (pci express?d28:f0/f1/f2/f3) address offset: 14ch ? 14fh attribute: ro default value: 00060011h size: 32 bits 17 receiver overflow mask (ro) ? r/wo. 0 = the corresponding error in the ues regi ster (d28:f0/f1/f2/f3:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3:144) is masked. 16 unexpected completion mask (uc) ? r/wo. 0 = the corresponding error in the ues regi ster (d28:f0/f1/f2/f3:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3:144) is masked. 15 completion abort mask (ca) ? r/wo. 0 = the corresponding error in the ues regi ster (d28:f0/f1/f2/f3:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3:144) is masked. 14 completion timeout mask (ct) ? r/wo. 0 = the corresponding error in the ues regi ster (d28:f0/f1/f2/f3:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3:144) is masked. 13 flow control protocol error mask (fcpe) ? ro. flow control protocol errors not supported. 12 poisoned tlp mask (pt) ? r/wo. 0 = the corresponding error in the ues regi ster (d28:f0/f1/f2/f3:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3:144) is masked. 11:5 reserved 4 data link protocol error mask (dlpe) ? r/wo. 0 = the corresponding error in the ues regi ster (d28:f0/f1/f2/f3:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3:144) is masked. 3:1 reserved 0 training error mask (te) ? ro. training errors not supported bit description bit description 31:21 reserved 20 unsupported request error severity (ure) ? ro. 0 = error considered no n-fatal. (default) 1 = error is fatal. 19 ecrc error severity (ee) ? ro. ecrc is not supported. 18 malformed tlp severity (mt) ? ro. 0 = error considered non-fatal. 1 = error is fatal. (default) 17 receiver overflow severity (ro) ? ro. 0 = error considered non-fatal. 1 = error is fatal. (default) 16 unexpected completion severity (uc) ? ro. 0 = error considered no n-fatal. (default) 1 = error is fatal. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 653 pci express* configuration registers 19.1.58 ces ? correctable error status register (pci express?d28:f0/f1/f2/f3) address offset: 150h ? 153h attribute: r/wc default value: 00000000h size: 32 bits 15 completion abort severity (ca) ? ro. 0 = error considered non-fatal. (default) 1 = error is fatal. 14 completion timeout severity (ct) ? ro. 0 = error considered non-fatal. (default) 1 = error is fatal. 13 flow control protocol error severity (fcp e) ? ro. flow control protocol errors not supported. 12 poisoned tlp severity (pt) ? ro. 0 = error considered non-fatal. (default) 1 = error is fatal. 11:5 reserved 4 data link protocol error severity (dlpe) ? ro. 0 = error considered non-fatal. 1 = error is fatal. (default) 3:1 reserved 0 training error severity (te) ? ro. te is not supported. bit description 31:13 reserved 12 replay timer timeout status (rtt) ? r/wc. 0 = replay timer did not time out. 1 = replay timer timed out. 11:9 reserved 8 replay number rollover status (rnr) ? r/wc. 0 = replay number did not roll over. 1 = replay number rolled over. 7 bad dllp status (bd) ? r/wc. 0 = bad dllp was not received. 1 = bad dllp was received. 6 bad tlp status (bt) ? r/wc. 0 = bad tlp was not received. 1 = bad tlp was received. 5:1 reserved 0 receiver error status (re) ? r/wc. 0 = receiver error did not occur. 1 = receiver error occurred. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 654 datasheet 19.1.59 cem ? correctable error mask register (pci express?d28:f0/f1/f2/f3) address offset: 154h ? 157h attribute: r/wo default value: 00000000h size: 32 bits when set, the corresponding error in the ce s register is masked, and the logged error will cause no action. when cleared, the corresponding error is enabled. 19.1.60 aecc ? advanced error ca pabilities and control register (pci express?d28:f0/f1/f2/f3) address offset: 158h ? 15bh attribute: ro default value: 00000000h size: 32 bits bit description 31:13 reserved 12 replay timer timeout mask (rtt) ? r/wo. 0 = no mask 1 = mask for replay timer timeout. 11:9 reserved 8 replay number rollover mask (rnr) ? r/wo. 0 = no mask 1 = mask for replay number rollover. 7 bad dllp mask (bd) ? r/wo. 0 = no mask 1 = mask for bad dllp reception. 6 bad tlp mask (bt) ? r/wo. 0 = no mask 1 = mask for bad tlp reception. 5:1 reserved 0 receiver error mask (re) ? r/wo. 0 = no mask 1 = mask for receiver errors. bit description 31:9 reserved 8 ecrc check enable (ece) ? ro. ecrc is not supported. 7 ecrc check capable (ecc) ? ro. ecrc is not supported. 6 ecrc generation enable (ege) ? ro. ecrc is not supported. 5 ecrc generation capable (egc) ? ro. ecrc is not supported. 4:0 first error pointer (fep) ? ro. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 655 pci express* configuration registers 19.1.61 res ? root erro r status register (pci express?d28:f0/f1/f2/f3) address offset: 170h ? 173h attribute: r/wc, ro default value: 00000000h size: 32 bits 19.1.62 rctcl ? root complex topology capability list register (pci express?d28:f0/f1/f2/f3) address offset: 180 ? 183h attribute: ro default value: 00010005h size: 32 bits bit description 31:27 advanced error interrupt message number (aemn) ? ro. there is only one error interrupt allocated. 26:4 reserved 3 multiple err_fatal/nonfatal received (menr) ? ro. for chipset, only one error will be captured. 2 err_fatal/nonfatal received (enr) ? r/wc. 0 = no error message received. 1 = either a fatal or a non-fata l error message is received. 1 multiple err_cor received (mcr) ? ro. for chipset, only one error will be captured. 0 err_cor received (cr) ? r/wc. 0 = no error message received. 1 = a correctable error message is received. bit description 31:20 next capability (next) ? ro. this field indicates the next item in the list, in this case, end of list. 19:16 capability version (cv) ? ro. this field indicates th e version of the capability structure. 15:0 capability id (cid) ? ro. this field indicates this is a root complex topology capability. www.datasheet.co.kr datasheet pdf - http://www..net/
pci express* configuration registers 656 datasheet 19.1.63 esd ? element self description register (pci express?d28:f0/f1/f2/f3) address offset: 184h ? 187h attribute: ro default value: see description size: 32 bits 19.1.64 uld ? upstream link description register (pci express?d28:f0/f1/f2/f3) address offset: 190h ? 193h attribute: ro default value: 00000001h size: 32 bits bit description 31:24 port number (pn) ? ro. this field indicates the ingress port number for the root port. there is a different value per port: 23:16 component id (cid) ? ro. this field returns the valu e of the esd.cid field (chipset configuration space: offset 0104h:bits 23:16) of the chip configuration section, that is programmed by platform bios, since the root port is in the sa me component as the rcrb. 15:8 number of link entries (nle) ? ro. (default value is 01h). this field indicates one link entry (corresponding to the rcrb). 7:4 reserved . 3:0 element type (et) ? ro. (default value is 0h). this field indicates that the element type is a root port. port # value 1 01h 2 02h 3 03h 4 04h bit description 31:24 target port number (pn) ? ro. this field indicates the port number of the rcrb. 23:16 target component id (tcid) ? ro. this field returns th e value of the esd.cid field (chipset configuration space: offset 0104h:bits 23:16) of the chip configuration section, that is programmed by platform bios, since the root port is in the same component as the rcrb. 15:2 reserved . 1 link type (lt) ? ro. this bit indicates that the link points to the chipset rcrb. 0 link valid (lv) ? ro. this bit indicates that this link entry is valid. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 657 pci express* configuration registers 19.1.65 ulba ? upstream link base address register (pci express?d28:f0/f1/f2/f3) address offset: 198h ? 19fh attribute: ro default value: see description size: 64 bits 19.1.66 peetm ? pci ex press extended test mode register (pci express?d28:f0/f1/f2/f3) address offset: 318h attribute: ro default value: see description size: 8 bits bit description 63:32 base address upper (bau) ? ro. the rcrb of the chipset is in 32-bit space. 31:0 base address lower (bal) ? ro. this field matches the rcba register (d31:f0:offset f0h) va lue in the lpc bridge. bit description 7:3 reserved 2 scrambler bypass mode (bau) ? r/w. 0 = normal operation. scrambler and descrambler are used. 1 = bypasses the data scrambler in the transmit direction and the data de-scrambler in the receive direction. note: this functionality intended for debug/testing only. note: if bypassing scrambler with chipset root po rt 1 in x4 configuration, each chipset root port must have this bit set. 1:0 reserved www.datasheet.co.kr datasheet pdf - http://www..net/
high precision event timer registers 658 datasheet 20 high precision event timer registers the timer registers are memory-mapped in a non-indexed scheme. this allows the processor to directly access each register without having to use an index register. the timer register space is 1024 bytes. the registers are generally aligned on 64-bit boundaries to simplify implementation with ia64 processors. there are four possible memory address ranges beginning at 1) fed0_0000h, 2) fed0_1000h, 3) fed0_2000h., 4) fed0_4000h. the choice of address range will be selected by configuration bits in the high precision timer configuration register (chipset configuration registers:offset 3404h). behavioral rules: 1. software must not attempt to read or write across register boundaries. for example, a 32-bit access should be to offset x0h, x4h, x8h, or xch. 32-bit accesses should not be to 01h, 02h, 03h, 05h, 06h, 07h, 09h, 0ah, 0bh, 0dh, 0eh, or 0fh. any accesses to these offsets will result in an unexpected behavior, and may result in a master abort. however, these accesse s should not result in system hangs. 64- bit accesses can only be to x0h and must not cross 64-bit boundaries. 2. software should not write to read-only registers. 3. software should not expect any particular or consistent value when reading reserved registers or bits. 20.1 memory mapped registers table 20-149.memory-mapped registers (sheet 1 of 2) offset mnemonic register default type 000?007h gcap_id general capabilities and identification 0429b17f8 086a201h ro 008?00fh ? reserved ? ? 010?017h gen_conf general configuration 0000h r/w 018?01fh ? reserved ? ? 020?027h gintr_sta general interrupt status 00000000 00000000h r/wc, r/ w 028?0efh ? reserved ?? 0f0?0f7h main_cnt main counter value n/a r/w 0f8?0ffh ? reserved ?? 100?107h tim0_conf timer 0 configuration and capabilities n/a r/w, ro 108?10fh tim0_comp timer 0 comparator value n/a r/w www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 659 high precision event timer registers notes: 1. reads to reserved registers or bits will return a value of 0. 2. software must not attempt locks to the me mory-mapped i/o ranges for high precision event timers. if attempted, the lock is no t honored, which means potential deadlock conditions may occur. 20.1.1 gcap_id?general capabilitie s and identification register address offset: 00h attribute: ro default value: 0429b17f8086a201h size: 64 bits 110?11fh ? reserved ?? 120?127h tim1_conf timer 1 configuration and capabilities n/a r/w, ro 128?12fh tim1_comp timer 1 comparator value n/a r/w 130?13fh ? reserved ?? 140?147h tim2_conf timer 2 configuration and capabilities n/a r/w, ro 148?14fh tim2_comp timer 2 comparator value n/a r/w 150?15fh ? reserved ?? 160?3ffh ? reserved ?? table 20-149.memory-mapped registers (sheet 2 of 2) offset mnemonic register default type bit description 63:32 main counter tick period (counter_clk_per_cap) ? ro. this field indicates the period at which the counter increments in femptoseconds (10^-15 seconds). this will return 0429b17fh when read. this indicates a period of 69841279h fs (69.841279 ns). 31:16 vendor id capabili ty (vendor_id_cap) ? ro. this is a 16-bit value assigned to intel. 15 legacy replacement rout capable (leg_rt_cap) ? ro. hardwired to 1. legacy replacement interrupt rout option is supported. 14 reserved . this bit returns 0 when read. 13 counter size capability (count_size_cap) ? ro. hardwired to 1. counter is 64-bit wide. 12:8 number of timer capability (num_tim_cap) ? ro. this field indicates the number of timers in this block. 02h = three timers. 7:0 revision identification (rev_id) ? ro. this indicates which revision of the function is implemented. default value will be 01h. www.datasheet.co.kr datasheet pdf - http://www..net/
high precision event timer registers 660 datasheet 20.1.2 gen_conf?general configuration register address offset: 010h attribute: r/w default value: 00000000 00000000h size: 64 bits 20.1.3 gintr_sta?general interrupt status register address offset: 020h attribute: r/w, r/wc default value: 00000000 00000000h size: 64 bits . bit description 63:2 reserved . these bits return 0 when read. 1 legacy replacement rout (leg_rt_cnf) ? r/w. if the enable_cnf bit and the leg_rt_cnf bit are both set, then the interrupts will be routed as follows: ? timer 0 is routed to irq0 in 8259 or irq2 in the i/o apic ? timer 1 is routed to irq8 in 8259 or irq8 in the i/o apic ? timer 2-n is routed as per the rout ing in the timer n config registers. ? if the legacy replacement rout bit is set, the individual routing bits for timers 0 and 1 (apic) will have no impact. ? if the legacy replacement rout bit is not se t, the individual rout ing bits for each of the timers are used. ? this bit will default to 0. bios can set it to 1 to enable the legacy replacement routing, or 0 to disable th e legacy replacement routing. 0 overall enable (enable_cnf) ? r/w. this bit must be set to enable any of the timers to generate interrupts. 0 = disable. the main counter will halt (will not increment) and no interrupts will be caused by any of these timers. for level- triggered interrupts, if an interrupt is pending when the enable_cnf bit is changed from 1-to -0, the interrupt status indications (in the various txx_int_sts bits) will not be cleared. software must write to the txx_int_sts bits to clear the interrupts. 1 = enable. note: this bit will default to 0. bios can set it to 1 or 0. bit description 63:3 reserved . these bits will return 0 when read. 2 timer 2 interrupt active (t02_int_sts) ? r/w. same functionality as timer 0. 1 timer 1 interrupt active (t01_int_sts) ? r/w. same functionality as timer 0. 0 timer 0 interrupt active (t00_int_sts) ? r/wc. the functionality of this bit depends on whether the edge or level-triggered mode is used for this timer. (default = 0) if set to level-triggered mode: this bit will be set by hardware if the corre sponding timer interrupt is active. once the bit is set, it can be cleared by software writing a 1 to the same bit position. writes of 0 to this bit will have no effect. if set to edge-triggered mode: this bit should be ignored by software. so ftware should always write 0 to this bit. note: defaults to 0. in edge tri ggered mode, this bit will al ways read as 0 and writes will have no effect. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 661 high precision event timer registers 20.1.4 main_cnt?main co unter value register address offset: 0f0h attribute: r/w default value: n/a size: 64 bits . 20.1.5 timn_conf?timer n conf iguration and capabilities register address offset: timer 0: 100?107h, attribute: ro, r/w timer 1: 120?127h, timer 2: 140?147h default value: n/a size: 64 bits note: the letter n can be 0, 1, or 2, referring to timer 0, 1 or 2. bit description 63:0 counter value (counter_val[63:0]) ? r/w. reads return the current value of the counter. writes load the new value to the counter. notes: 1. writes to this register should only be done while the counter is halted. 2. reads to this register return th e current value of the main counter. 3. 32-bit counters will always return 0 for the upper 32-bits of this register. 4. if 32-bit software attempts to read a 64-bit counter, it sh ould first halt the counter. since this delays the interrupts for all of the timers, this should be done only if the consequences are understood. it is strongly recommended that 32-bit software only operate the timer in 32-bit mode. 5. reads to this register are monotonic. no two consecutive reads return the same value. the second of two reads always returns a larger value (unless the timer has rolled over to 0). bit description 63:56 reserved . these bits will return 0 when read. 55:52, 43 timer interrupt rout capabi lity (timern_int_rout_cap) ? ro. timer 0, 1:bits 52, 53, 54, and 55 in this field (corresponding to irq 20, 21, 22, and 23) have a value of 1. writes will have no effect. timer 2:bits 43, 52, 53, 54, and 55 in this field (c orresponding to irq 11, 20, 21, 22, and 23) have a value of 1. writes will have no effect. note: 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. 51:44, 42:14 reserved. these bits return 0 when read. www.datasheet.co.kr datasheet pdf - http://www..net/
high precision event timer registers 662 datasheet 13:9 interrupt rout (timern_int_rout_cnf) ? r/w. this 5-bit field indica tes the routing for the interrupt to the i/o (x) apic . software writes to this field to sele ct which interrupt in the i/o (x) will be used for this timer?s in terrupt. if the value is not supported by this particular timer, then the value read back will not match what is written. the software must only write valid values. notes: 1. if the legacy replacement rout bit is set, th en timers 0 and 1 will ha ve a different routing, and this bit field has no e ffect for those two timers. 2. timer 0,1: software is responsible to make sure it programs a valid value (20, 21, 22, or 23) for this field. the chipset logic does not check the validity of the value written. 3. timer 2: software is responsible to make sure it programs a valid value (11, 20, 21, 22, or 23) for this field. the chipse t logic does not check the va lidity of the value written. 8 timer n 32-bit mode (timern_32mode_cnf) ? r/w or ro. software can set this bit to force a 64-bit timer to behave as a 32-bit ti mer. this is typically needed if so ftware is not willing to halt the main counter to read or write a particular timer, and the software is not capable of atomic 64-bit operations to the timer. this bit is only relevant if the timer is operating in 64-bit mode in which case that timer can be forced to 32-bit mode by setting this bit. when timer 0 is switched to 32-bit mode, the upper 32-bits are loaded with 0?s which will re main when the timer is switched back to 64-bit mode. if the timer is not in 64-bit mode, then this bit will always be read as 0 and writes will have no effect. timer 0:bit is read/wri te (default to 0). 0 = 64 bit; 1= 32 bit timers 1, 2:hardwired to 0. writes have no effect since these timers are 32-bit only. 7 reserved . this bit returns 0 when read. 6 timer n value set (timern_val_set_cnf) ? r/w. software uses this bit only for timer 0 if it has been set to periodic mode. by writing this bit to a 1, the software is then allowed to directly set the timer?s accumulator. software does not have to write this bit back to 1 (it automatically clears). software should not write a 1 to this bit positi on if the timer is set to non-periodic mode. note: this bit will return 0 when read . writes will only have an effect for timer 0 if it is set to periodic mode. writes will have no effect for timers 1 and 2. 5 timer n size (timern_size_cap) ? ro. this read only field in dicates the size of the timer. timer 0:value is 1 (64-bits). timers 1, 2:value is 0 (32-bits). 4 periodic interrupt capable (timern_per_int_cap) ? ro. if this bit is 1, the hardware supports a periodic mode fo r this timer?s interrupt. timer 0: hardwired to 1 (suppo rts the periodic interrupt). timers 1, 2: hardwired to 0 (doe s not support periodic interrupt). 3 timer n type (timern_type_cnf) ? r/w or ro. timer 0:bit is read/write. 0 = disable timer to ge nerate periodic interrupt ; 1 = enable timer to generate a periodic interrupt. timers 1, 2: hardwired to 0. writes have no effect. 2 timer n interrupt enable (timern_int_enb_cnf) ? r/w. this bit must be set to enable timer n to cause an interrupt when it times out. 0 = enable. 1 = disable (default). the timer can still count an d generate appropriate st atus bits, but will not cause an interrupt. bit description www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 663 high precision event timer registers note: reads or writes to unimpleme nted timers should not be attempted. read from any unimplemented registers will re turn an undetermined value. 20.1.6 timn_comp?timer n co mparator value register address offset: timer 0: 108h?10fh, timer 1: 128h?12fh, timer 2: 148h?14fh attribute: r/w default value: n/a size: 64 bit 1 timer interrupt type (timern_int_type_cnf) ? r/w. 0 = the timer interrupt is edge triggered. this mean s that an edge-type inte rrupt is generated. if another interrupt occurs, anot her edge will be generated. 1 = the timer interrupt is level triggered. this me ans that a level-triggered interrupt is generated. the interrupt will be held active until it is clea red by writing to the bit in the general interrupt status register. if another interru pt occurs before the interrupt is cleared, the interrupt will remain active. 0 reserved. these bits will return 0 when read. bit description bit description 63:0 timer compare value ? r/w. reads to this register retu rn the current valu e of the comparator timers 0, 1, or 2 are config ured to non-periodic mode: writes to this register load the value against wh ich the main counter should be compared for this timer. ? when the main counter equals the value last writ ten to this register, th e corresponding interrupt can be generated (if so enabled). ? the value in this register does not chan ge based on the inte rrupt being generated. timer 0 is configured to periodic mode: ? when the main counter equals the value last writ ten to this register, th e corresponding interrupt can be generated (if so enabled). ? after the main counter equals the value in this register, the value in this register is increased by the value last written to the register. for example, if the value written to the register is 00000123h, then 1. an interrupt will be generated when the main counter reaches 00000123h. 2. the value in this register will then be adjusted by the hardware to 00000246h. 3. another interrupt will be generated when the main counter reaches 00000246h 4. the value in this register will then be adjusted by the hardware to 00000369h ? as each periodic interrupt occurs, the value in this register will increment. when the incremented value is greater than the maximum value possible for this register (fff fffffh for a 32-bit timer or ffffffffffffffffh for a 64-bit timer), the value will wrap around through 0. for example, if the current value in a 32-bit timer is ffff0000h an d the last value written to this register is 20000, then after the next interrupt the value will change to 00010000h default value for each timer is al l 1s for the bits that are implem ented. for example, a 32-bit timer has a default value of 00000000ffffffffh. a 64-bit timer has a default value of ffffffffffffffffh. www.datasheet.co.kr datasheet pdf - http://www..net/
serial peripheral interface (spi) 664 datasheet 21 serial peripheral interface (spi) the serial peripheral interface resides in me mory mapped space. this function contains registers that allow for the setup and progra mming of devices that reside on the spi interface. note: all registers in this function (including me mory-mapped registers) must be addressable in byte, word, and dword quantities. the software must always make register accesses on natural boundaries (i.e., dword accesses must be on dword boundaries; word accesses on word boundaries, etc.) in a ddition, the memory-mapped register space must not be accessed with the lock semantic exclusive-access mechanism. if software attempts exclusive-access mechanisms to the spi memory-mapped space, the results are undefined. 21.1 serial peripheral interface memory mapped configuration registers the spi host interface registers are memo ry-mapped in the rcrb chipset register space with a base address (spibar) of 3020h and are located within the range of 3020h to 308fh. the individual registers are then accessible at spibar + offset as indicated in the following table. these memory mapped registers must be acce ssed in byte, word, or dword quantities. table 21-150.serial peripheral inte rface (spi) register address map (spi memory mapped configuration register s) (sheet 1 of 2) spibar + offset mnemonic register name default access 00h?01h spis spi status see register description ro, r/wc, r/wlo 02h?03h spic spi control 0001h r/w 04h?07h spia spi address 00000000h r/w 08h?0fh spid0 spi data 0 see register description r/w 10h?17h spid1 spi data 1 00000000 00000000h r/w 18h?1fh spid2 spi data 2 00000000 00000000h r/w 20h?27h spid3 spi data 3 00000000 00000000h r/w 28h?2fh spid4 spi data 4 00000000 00000000h r/w 30h?37h spid5 spi data 5 00000000 00000000h r/w www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 665 serial peripheral interface (spi) 21.1.1 spis?spi status register (spi memory mapped configuration registers) memory address:spibar + 00h attribute: ro, r/wc, r/wlo default value: see bit descriptionsize:16 bits 38h?3fh spid6 spi data 6 00000000 00000000h r/w 40h?47h spid7 spi data 7 00000000 00000000h r/w 50h?53h bbar bios base address configuration 00000000h r/w 54h?55h preop prefix opcode configuration 0004h r/w 56h?57h optype opcode type configuration 0000h r/w 58h?5fh opmenu opcode menu configuration 00000000 00000005h r/w 60h?63h pbr0 protected bios range 0 00000000h r/w 64h?67h pbr1 protected bios range 1 00000000h r/w 68h?6bh pbr2 protected bios range 2 00000000h r/w 6ch?6fh ? reserved ?? table 21-150.serial peripheral interface (spi) register address map (spi memory mapped configuratio n registers) (sheet 2 of 2) spibar + offset mnemonic register name default access bit description 15 spi configuration lock-down ? r/wlo. 0 = no lock-down (default) 1 = spi static configuration information in offsets 50h through 6fh can not be overwritten. once set to 1, this bit ca n only be cleared by a hardware reset. 14:4 reserved 3 blocked access status ? r/wc. 0 = not blocked (default) 1 = hardware sets this bit to 1 when an access is blocked fr om running on the spi interface due to one of the protection poli cies or when any of the programmed cycle registers is written while a pr ogrammed access is already in progress. this bit is set for both programmed accesses and dire ct memory reads th at get blocked. note: this bit remains asserted until cleared by software writing a 1 or hardware reset. 2 cycle done status ? r/wc. 0 = not done (default) 1 = the chipset sets this bit to 1 when the spi cycle completes (i.e., scip bit is 0) after software sets the scgo bit. note: this bit remains asserted until cleared by software writing a 1 or hardware reset. note: software must make sure this bit is cleared prior to enabling the spi smi# assertion for a new programmed access. note: this bit gets set after the status regist er polling sequence completes after reset deasserts. it is cleared befo re and during that sequence. www.datasheet.co.kr datasheet pdf - http://www..net/
serial peripheral interface (spi) 666 datasheet 21.1.2 spic?spi control register (spi memory mapped co nfiguration registers) memory address:spibar + 02h attribute: r/w default value: 4005hsize:16 bits 1 spi access grant ? ro. this bit is used by the softwa re to know when the other spi master will not be initiating any long transactions on the spi bus. 0 = default 1 = it is set by hardware in response to so ftware setting the spi access request bit and completing the future pending handshake with the lan component. note: this bit is cleared in response to soft ware clearing the spi access request bit. 0 spi cycle in progress (scip) ? ro. 0 = cycle not in progress (default) 1 = hardware sets this bit when software sets the spi cycle go bit in the command register. this bit remains set until the cycle completes on the spi interface. hardware automatically sets and clears th is bit so that software can determine when read data is valid an d/or when it is safe to begin programming the next command. this bit reports 1b during the status register poll ing sequence after re set deasserts; it is cleared when that sequence completes. note: software must only program the ne xt command when this bit is 0. bit description bit description 15 spi smi# enable ? r/w. 0 = disable. 1 = enable. the spi asserts an smi# reques t when the cycle done status bit is 1. 14 data cycle ? r/w. 0 = no data is delivered for this cycle, an d the dbc and data fi elds themselves are don't cares. 1 = there is data that corresp onds to this transaction. 13:8 data byte count (dbc) ? r/w. this field specifies the number of bytes to shift in or out during the data portion of the spi cycl e. the valid settings (in decimal) are any value from 0 to 63. the number of bytes tran sferred is the value of this field plus 1. for example, when this field is 000000b, then there is 1 byte to transfer and that 111111b means there are 64 bytes to transfer. 7 reserved 6:4 cycle opcode pointer ? r/w. this field selects one of the programmed opcodes in the opcode menu to be used as the spi co mmand/opcode. in the case of an atomic cycle sequence, th is determines the second command. 3 sequence prefix opcode pointer ? r/w. this field selects one of the two programmed prefix opcodes for use when pe rforming an atomic cycle sequence. by making this programmable, the chipset su pports flash devices th at have different opcodes for enabling writes to the data space vs. status register 0 = a value of 0 points to the opcode in the least significant byte of the prefix opcodes register. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 667 serial peripheral interface (spi) 21.1.3 spia?spi address register (spi memory mapped configuration registers) memory address:spibar + 04h attribute: r/w default value: 00000000hsize:32 bits 2 atomic cycle sequence (acs) ? r/w. 0 = no atomic cycle sequence. 1 = when set to 1 along with the scgo assertion, the chipset will execute a sequence of commands on the spi interface without allowing the lan component to arbitrate and interleave cycles. 1 spi cycle go (scgo) ? r/w. this bit always returns 0 on reads. 0 = spi cycle not started. 1 = a write to this register with a 1 in this bit starts the spi cycle defined by the other bits of this register. the ?spi cycle in progress? (scip) bit gets set by this action. note: writes to this bit while the cycle in progress bit is set are ignored. note: other bits in this regist er can be programmed for the same transaction when writing this bit to 1. 0 spi access request ? r/w. this bit is used by software to request that the other spi master stop initiating long transactions on the spi bus. 0 = no request. 1 = request that the other spi master stop in itiating long transact ions on the spi bus. note: this bit defaults to a 1 and must be cleared by bios after completing the accesses for th e boot process. bit description 31:24 reserved 23:0 spi cycle address (sca) ? r/w. this field is shifte d out as the spi address (msb first). bits 23:0 correspon d to address bits 23:0. www.datasheet.co.kr datasheet pdf - http://www..net/
serial peripheral interface (spi) 668 datasheet 21.1.4 spid[n] ?spi data n register (spi memory mapped co nfiguration registers) memory address:spi data [0]: spibar + 08hattribute: r/w spi data [1]: spibar + 10h spi data [2]: spibar + 18h spi data [3]: spibar + 20h spi data [4]: spibar + 28h spi data [5]: spibar + 30h spi data [6]: spibar + 38h spi data [7]: spibar + 40h default value: see notes 1 and 2 belowsize:64 bits notes: 1. for spi data [7:1] registers only: default value is 0000000000000000h. 2. for spi data 0 register default value only: th is register is initialized to 0 by the reset assertion. however, the least significant byte of this register is loaded with the first status register read of the atomic cycle sequence that the hardwa re automatically runs out of reset. therefore, bit 0 of this register can be read later to determine if the platform encountered the boundary case in which the spi flash was busy with an internal instruction when the platform reset deasserted. bit description 63:0 spi cycle data [n] (scd[n]) ? r/w. this field is shifted out as the spi data on the master-out slave-in data pin during the da ta portion of the sp i cycle. the scd[n] register does not begin shifting until spid[n-1] has completely shifted in/out. this register also shifts in the data from th e master-in slave-out pin into this register during the data portion of the spi cycle. note: the data is always shifted starting with the least significant byte, msb to lsb, followed by the next least significant byte , msb to lsb, etc. specifically, the shift order on spi in terms of bits within this register is: 7-6-5-4-3-2-1-0-15-14-13- ?8-23-22-?16-31?24-39..32?etc. bit 56 is the last bit shifted out/in. there are no alignment assumptions; byte 0 always represents the value specified by the cycle address. note: the data in this register may be mo dified by the hardware during any programmed spi transaction. direct memo ry reads do not modify the contents of this register. www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 669 serial peripheral interface (spi) 21.1.5 bbar?bios base address register (spi memory mapped configuration registers) memory address:spibar + 50h attribute: r/w default value: 00000000hsize:32 bits note: this register is not writable when the spi configuration lock-down bit (spibar + 00h:15) is set. 21.1.6 preop?prefix opcode configuration register (spi memory mapped configuration registers) memory address:spibar + 54h attribute: r/w default value: 0004hsize:16 bits note: this register is not writable when the spi configuration lock-down bit (spibar + 00h:15) is set. bit description 31:24 reserved . 23:8 bottom of system flash ? r/w. this field determines the bottom of the system bios. the chipset will not run programm ed commands nor me mory reads whose address field is less than this value. this field corresponds to bits 23:8 of the 3-byte address; bits 7:0 are assumed to be 00h for this vector when comparing to a potential spi address. note: software must always program 1s into th e upper, don?t care, bits of this field based on the flash size. hardware does no t know the size of the flash array and relies upon the correct programming by software. the default value of 0000h results in all cycles allowed. note: in the event that this value is progra mmed below some of the bios memory segments, described abov e, this protection policy takes precedence. 7:0 reserved bit description 15:8 prefix opcode 1 ? r/w. software programs an spi opcode into this field that is permitted to run as the first comm and in an atomic cycle sequence. 7:0 prefix opcode 0 ? r/w. software programs an spi opcode into this field that is permitted to run as the first comm and in an atomic cycle sequence. www.datasheet.co.kr datasheet pdf - http://www..net/
serial peripheral interface (spi) 670 datasheet 21.1.7 optype?opcode type configuration register (spi memory mapped co nfiguration registers) memory address:spibar + 56h attribute: r/w default value: 0000hsize:16 bits entries in this register correspond to the entries in the opcode menu configuration register. note: the definition below only provides write pr otection for opcodes that have addresses associated with them. therefore, any erase or write opcodes that do not use an address should be avoided (for example, ?chip erase? and ?auto-address increment byte program?) note: this register is not writable when the spi configuration lock-down bit (spibar + 00h:15) is set. 21.1.8 opmenu?opcode menu configuration register (spi memory mapped co nfiguration registers) memory address:spibar + 58h attribute: r/w default value: 0000000000000005hsize:64 bits eight entries are available in this register to give bios a sufficient set of commands for communicating with the flash device, while also restricting what malicious software can do. this keeps the hardware flexible enough to operate with a wide variety of spi devices. note: it is recommended that bios avoid progra mming write enable op codes in this menu. malicious software could then perform writes and erases to the spi flash without using the atomic cycle mechanism. this could cause functional failures in a shared flash bit description 15:14 opcode type 7 ? r/w. see the desc ription for bits 1:0 13:12 opcode type 6 ? r/w. see the desc ription for bits 1:0 11:10 opcode type 5 ? r/w. see the desc ription for bits 1:0 9:8 opcode type 4 ? r/w. see the desc ription for bits 1:0 7:6 opcode type 3 ? r/w. see the desc ription for bits 1:0 5:4 opcode type 2 ? r/w. see the desc ription for bits 1:0 3:2 opcode type 1 ? r/w. see the desc ription for bits 1:0 1:0 opcode type 0 ? r/w. this field specifies in formation about the corresponding opcode 0. this information allows the hardwa re to, 1) know whether to use the address field and, 2) provide bios and shared flash protection capabilities . the encoding of the two bits is: 00 = no address associated with this opcode; read cycle type 01 = no address associated with this opcode; write cycle type 10 = address required; read cycle type 11 = address required; write cycle type www.datasheet.co.kr datasheet pdf - http://www..net/
datasheet 671 serial peripheral interface (spi) environment. write enable opcodes should only be programmed in the prefix opcodes. note: this register is not writable when the spi configuration lock-down bit (spibar + 00h:15) is set. 21.1.9 pbr[n]?protected bios range [n] (spi memory mapped configuration registers) memory address:pbr[0]: spibar + 60h attribute: r/w pbr[1]: spibar + 64h pbr[2]: spibar + 68h default value:00000000h size: 32 bits note: this register is not writable when the spi configuration lock-down bit (spibar + 00h:15) is set. bit description 63:56 allowable opcode 7 ? r/w. see the description for bits 7:0 55:48 allowable opcode 6 ? r/w. see the description for bits 7:0 47:40 allowable opcode 5 ? r/w. see the description for bits 7:0 39:32 allowable opcode 4 ? r/w. see the description for bits 7:0 31:24 allowable opcode 3 ? r/w. see the description for bits 7:0 23:16 allowable opcode 2 ? r/w. see the description for bits 7:0 15:8 allowable opcode 1 ? r/w. see the description for bits 7:0 7:0 allowable opcode 0 ? r/w. software programs an sp i opcode into this field for use when initiating spi commands through the control register. bit description 31 write protection enable ? r/w. 0 = disable. the base and limit fields are ignored when this bit is cleared. 1 = enable. the base and limit fiel ds in this register are valid. 30:24 reserved 23:12 protected range limit ? r/w. this field corresponds to spi address bits 23:12 and specifies the upper limit of the protected range. note: any address greater than the value progra mmed in this field is unaffected by this protected range. 11:0 protected range base ? r/w. this field corresponds to spi address bits 23:12 and specifies the lower base of the protected range. note: address bits 11:0 are assumed to be 000h for the base comparison. any address less than the value programmed in this field is unaffected by this protected range. www.datasheet.co.kr datasheet pdf - http://www..net/

▲Up To Search▲

Price & Availability of NM10

	To Download NM10 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .