| Electronic Components Datasheet Search |
|
CS5920 Datasheet(PDF) 101 Page - Applied Micro Circuits Corporation |
|
|
|||||||||||||||||||||||||||||
CS5920 Datasheet(HTML) 101 Page - Applied Micro Circuits Corporation |
|
101 / 160 page ![]() S5920 – PCI Product Revision 1.01 – November 28, 2005 AMCC Confidential and Proprietary DS1596 101 Data Book Target Latency The PCI specification requires that a selected target relinquish the bus should an access to that target require more than eight PCI clock periods (16 clocks for the first data phase, 8 clocks for each subsequent data phase). This prevents slow target devices from potentially monopolizing the PCI bus and also allows more accurate estimations for bus access latency. Note that a special mode is available to the user which will allow for this mechanism to be disabled, thus vio- lating the PCI 2.1 Specification. If a value of 0 is programmed into the serial nvRAM location 45h, bit 0, target latency is ignored. In this case, the S5920 will never issue a retry/disconnect in the event of a slow Add-On device. This programmable bit is only pro- vided for flexibility, and most users should leave this bit set to 1. nvRAM Location 45h, bit 0 = 0 : No disconnect for slow Add-On device. nvRAM Location 45h, bit 0 = 1 : PCI 2.1 compliant Target Locking It is possible for a PCI bus master to obtain exclusive access to a target (“locking”) through use of the PCI bus signal LOCK#. LOCK# is different from the other PCI bus signals because its ownership may belong to any bus master, even if it does not currently have own- ership of the PCI bus. The ownership of LOCK#, if not already claimed by another master, may be achieved by the current PCI bus master on the clock period fol- lowing the initial assertion of FRAME#. Figure 6 describes the signal relationship for establishing a lock. The ownership of LOCK#, once established, per- sists even while other bus masters control the bus. Ownership can only be relinquished by the master which originally established the lock. PCI Bus Access Latency Components Figure 50. Figure 5. Target-Initiated Retry Figure 51. Figure 6. Engaging the LOCK# Signal Bus Access Latency REQ# Asserted GNT# Asserted FRAME# Asserted TRDY# Asserted --Arbitration Latency-- --Bus Acquisition-- Latency --Target Latency-- FRAME# IRDY# TRDY# DEVSEL# STOP# 1 2 3 4 5 PCLK (I) (T) (I) Driven by Initiator (T) Driven by Target (I) (T) (T) Target Retry Signaled Initiator Sequences IRDY# + FRAME# to return to IDLE state FRAME# AD[31:0] IRDY# TRDY# DEVSEL# 1 2 3 4 5 PCLK Address Data (I) (T ) (I) Driven by Initiator (T) Driven by Target LOCK# (I) (I) (T) (T) LOCK MECHANISM AVAILABLE LOCK ESTABLISHED BUS IDLE LOCK MAINTAINED TARGET BECOMES LOCKED LOCK MECHANISM AVAI LABLE UPON FIRST ACCESS |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |