pi7c8154a Pericom Semiconductor Corporation, pi7c8154a Datasheet - Page 52
![no-image](/images/no-image-200.jpg)
pi7c8154a
Manufacturer Part Number
pi7c8154a
Description
2-port Pci-to-pci Bridge
Manufacturer
Pericom Semiconductor Corporation
Datasheet
1.PI7C8154A.pdf
(112 pages)
Available stocks
Company
Part Number
Manufacturer
Quantity
Price
Company:
Part Number:
pi7c8154aNAE
Manufacturer:
XILINX
Quantity:
192
4.4
Note: The superscript accompanying some of the table entries refers to any applicable ordering rule
listed in this section. Many entries are not governed by these ordering rules; therefore, the
implementation can choose whether or not the transactions pass each other.
The entries without superscripts reflect the PI7C8154A’s implementation choices.
The following ordering rules describe the transaction relationships. Each ordering rule is followed
by an explanation, and the ordering rules are referred to by number in Table 4-1. These ordering
rules apply to posted write transactions, delayed write and read requests, and delayed write and
read completion transactions crossing PI7C8154A in the same direction. Note that delayed
completion transactions cross PI7C8154A in the direction opposite that of the corresponding
delayed requests.
1. Posted write transactions must complete on the target bus in the order in which they were
received on the initiator bus. The subsequent posted write transaction can be setting a flag that
covers the data in the first posted write transaction; if the second transaction were to complete
before the first transaction, a device checking the flag could subsequently consume stale data.
2. A delayed read request traveling in the same direction as a previously queued posted write
transaction must push the posted write data ahead of it. The posted write transaction must complete
on the target bus before the delayed read request can be attempted on the target bus. The read
transaction can be to the same location as the write data, so if the read transaction were to pass the
write transaction, it would return stale data.
3. A delayed read completion must ‘‘pull’’ ahead of previously queued posted write data traveling
in the same direction. In this case, the read data is traveling in the same direction as the write data,
and the initiator of the read transaction is on the same side of PI7C8154A as the target of the write
transaction. The posted write transaction must complete to the target before the read data is
returned
to the initiator. The read transaction can be a reading to a status register of the initiator of the
posted write data and therefore should not complete until the write transaction is complete.
4. Delayed write requests cannot pass previously queued posted write data. For posted memory
write transactions, the delayed write transaction can set a flag that covers the data in the posted
write transaction. If the delayed write request were to complete before the earlier posted write
transaction, a device checking the flag could subsequently consume stale data.
5. Posted write transactions must be given opportunities to pass delayed read and write requests
and completions. Otherwise, deadlocks may occur when some bridges which support delayed
transactions and other bridges which do not support delayed transactions are being used in the same
system. A fairness algorithm is used to arbitrate between the posted write queue and the delayed
transaction queue.
DATA SYNCHRONIZATION
Data synchronization refers to the relationship between interrupt signaling and data delivery. The
PCI Local Bus Specification, Revision 2.2, provides the following alternative methods for
synchronizing data and interrupts:
Pass
Delayed Write Request
Delayed Read Completion
Delayed Write Completion
Posted
Write
No
No
Yes
4
3
Page 52 of 112
Delayed Read
Request
No
Yes
Yes
Delayed Write
Request
No
Yes
Yes
Delayed Read
Completion
Yes
No
No
ASYNCHRONOUS 2-PORT
JULY 2004 REVISION 1.00
PCI-to-PCI BRIDGE
Advance Information
Delayed Write
Completion
Yes
No
No
PI7C8154A