PI7C8154ANAE Pericom Semiconductor, PI7C8154ANAE Datasheet - Page 30

• Manufacturer Part Number: PI7C8154ANAE
• Description: IC PCI-PCI BRIDGE ASYNC 304-PBGA
• Manufacturer: Pericom Semiconductor

Specifications of PI7C8154ANAE

• Applications: *
• Interface: *
• Voltage - Supply: *
• Package / Case: 304-BGA
• Mounting Type: Surface Mount
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

2.7.5
2.7.6
completed, or until a target response (target abort or master abort) other than a target retry is
received.
DELAYED READ COMPLETION ON TARGET BUS
When delayed read request reaches the head of the delayed transaction queue, PI7C8154A
arbitrates for the target bus and initiates the read transaction only if all previously queued posted
write transactions have been delivered. PI7C8154A uses the exact read address and read command
captured from the initiator during the initial delayed read request to initiate the read transaction. If
the read transaction is a non-prefetchable read, PI7C8154A drives the captured byte enable bits
during the next cycle. If the transaction is a prefetchable read transaction, it drives all byte enable
bits to zero for all data phases. If PI7C8154A receives a target retry in response to the read
transaction on the target bus, it continues to repeat the read transaction until at least one data
transfer is completed, or until an error condition is encountered. If the transaction is terminated via
normal master termination or target disconnect after at least one data transfer has been completed,
PI7C8154A does not initiate any further attempts to read more data.
If PI7C8154A is unable to obtain read data from the target after 2
attempts, PI7C8154A will report system error. The number of attempts is programmable.
PI7C8154A also asserts P_SERR# if the primary SERR# enable bit is set in the command register.
See Section 5.4 for information on the assertion of P_SERR#.
Once PI7C8154A receives DEVSEL# and TRDY# from the target, it transfers the data read to the
opposite direction read data queue, pointing toward the opposite inter-face, before terminating the
transaction. For example, read data in response to a downstream read transaction initiated on the
primary bus is placed in the upstream read data queue. The PI7C8154A can accept one DWORD of
read data each PCI clock cycle; that is, no master wait states are inserted. The number of
DWORD’s transferred during a delayed read transaction matches the prefetch address boundary
given in Table 2-4 (assuming no disconnect is received from the target).
DELAYED READ COMPLETION ON INITIATOR BUS
When the transaction has been completed on the target bus, and the delayed read data is at the head
of the read data queue, and all ordering constraints with posted write transactions have been
satisfied, the PI7C8154A transfers the data to the initiator when the initiator repeats the transaction.
For memory read transactions, PI7C8154A aliases memory read line and memory read multiple bus
commands to memory read when matching the bus command of the transaction to the bus
command in the delayed transaction queue if bit[3] of offset 74h is set to ‘1’. PI7C8154A returns a
target disconnect along with the transfer of the last DWORD of read data to the initiator. If
PI7C8154A initiator terminates the transaction before all read data has been transferred, the
remaining read data left in data buffers is discarded.
When the master repeats the transaction and starts transferring prefetchable read data from data
buffers while the read transaction on the target bus is still in progress and before a read boundary is
reached on the target bus, the read transaction starts operating in flow-through mode. Because data
is flowing through the data buffers from the target to the initiator, long read bursts can then be
sustained. In this case, the read transaction is allowed to continue until the initiator terminates the
transaction, or until an aligned 4KB address boundary is reached, or until the buffer fills, whichever
comes first. When the buffer empties, PI7C8154A reflects the stalled condition to the initiator by
disconnecting the initiator with data. The initiator may retry the transaction later if data are needed.
If the initiator does not need any more data, the initiator will not continue the disconnected
Page 30 of 112
24
(default) or 2
ASYNCHRONOUS 2-PORT
DEC 2009 REVISION 1.02
PCI-to-PCI BRIDGE
Advance Information
32
(maximum)
PI7C8154A