![](http://datasheet.mmic.net.cn/Pericom/PI7C8154BNAIE_datasheet_99378/PI7C8154BNAIE_62.png)
PI7C8154B
ASYNCHRONOUS 2-PORT
PCI-to-PCI BRIDGE
Advance Information
Page 62 of 114
JUNE 2008 REVISION 1.1
Target abort detected during posted write transaction.
Master abort detected during posted write transaction.
Posted write data discarded after 224 (default) attempts to deliver (224 target retries received).
Parity error reported on target bus during posted write transaction (see previous section)
Delayed write data discarded after 224 (default) attempts to deliver (224 target retries received)
Delayed read data cannot be transferred from target after 224 (default) attempts (224 target
retries received)
Master timeout on delayed transaction
The device-specific P_SERR# status register reports the reason for the assertion of P_SERR#. Most
of these events have additional device-specific disable bits in the P_SERR# event disable register
that make it possible to mask out P_SERR# assertion for specific events. The master timeout
condition has a SERR# enable bit for that event in the bridge control register and therefore does not
have a device-specific disable bit.
6
EXCLUSIVE ACCESS
This chapter describes the use of the LOCK# signal to implement exclusive access to a target for
transactions that cross the bridge.
6.1
CONCURRENT LOCKS
The primary and secondary bus lock mechanisms operate concurrently except when a locked
transaction crosses the bridge. A primary master can lock a primary target without affecting the
status of the lock on the secondary bus, and vice versa. This means that a primary master can lock a
primary target at the same time that a secondary master locks a secondary target.
6.2
ACQUIRING EXCLUSIVE ACCESS ACROSS PI7C8154B
For any PCI bus, before acquiring access to the LOCK# signal and starting a series of locked
transactions, the initiator must first check that both of the following conditions are met:
The PCI bus must be idle.
The LOCK# signal must be de-asserted.
The initiator leaves the LOCK# signal de-asserted during the address phase and asserts LOCK# one
clock cycle later. Once a data transfer is completed from the target, the target lock has been
achieved.
6.2.1
LOCKED TRANSACTIONS IN DOWNSTREAM DIRECTION
Locked transactions can cross the bridge only in the downstream direction, from the primary bus to
the secondary bus.
When the target resides on another PCI bus, the master must acquire not only the lock on its own
PCI bus but also the lock on every bus between its bus and the target’s bus. When the bridge
detects on the primary bus, an initial locked transaction intended for a target on the secondary bus,