PI7C8150BNDIE Pericom Semiconductor, PI7C8150BNDIE Datasheet - Page 29

• Manufacturer Part Number: PI7C8150BNDIE
• Description: IC PCI-PCI BRIDGE ASYNC 256-PBGA
• Manufacturer: Pericom Semiconductor

Specifications of PI7C8150BNDIE

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

3.6.4
3.6.5
3.6.6
DELAYED READ REQUESTS
PI7C8150B treats all read transactions as delayed read transactions, which means
that the read request from the initiator is posted into a delayed transaction queue.
Read data from the target is placed in the read data queue directed toward the initiator bus
interface and is transferred to the initiator when the initiator repeats
the read transaction.
When PI7C8150B accepts a delayed read request, it first samples the read address, read bus
command, and address parity. When IRDY_L is asserted, PI7C8150B then samples the
byte enable bits for the first data phase. This information is entered into the delayed
transaction queue. PI7C8150B terminates the transaction by signaling a target retry to the
initiator. Upon reception of the target retry, the initiator is required to continue to repeat the
same read transaction until at least one data transfer is completed, or until a target response
(target abort or master abort) other than a target retry is received.
DELAYED READ COMPLETION WITH TARGET
When delayed read request reaches the head of the delayed transaction queue, PI7C8150B
arbitrates for the target bus and initiates the read transaction only if all previously queued
posted write transactions have been delivered. PI7C8150B 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, PI7C8150B 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 PI7C8150B 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, PI7C8150B does not initiate
any further attempts to read more data.
If PI7C8150B is unable to obtain read data from the target after 2
(maximum) attempts, PI7C8150B will report system error. The number of attempts is
programmable. PI7C8150B also asserts P_SERR_L if the primary SERR_L enable bit is
set in the command register. See Section 6.4 for information on the assertion of
P_SERR_L.
Once PI7C8150B receives DEVSEL_L and TRDY_L 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
PI7C8150B 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 depends on the conditions given in Table 3-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 PI7C8150B transfers the data to the initiator when the initiator
Page 29 of 109
ASYNCHRONOUS 2-PORT PCI-TO-PCI BRIDGE
ADVANCE INFORMATION
April 2009 – Revision 1.08
24
(default) or 2
PI7C8150B
32