PI7C7300DNAE Pericom Semiconductor, PI7C7300DNAE Datasheet - Page 65

• Manufacturer Part Number: PI7C7300DNAE
• Description: IC PCI-PCI BRIDGE 3PORT 272-BGA
• Manufacturer: Pericom Semiconductor

Specifications of PI7C7300DNAE

• Applications: *
• Interface: *
• Voltage - Supply: *
• Package / Case: 272-PBGA
• Mounting Type: Surface Mount
• Maximum Operating Temperature: + 85 C
• Minimum Operating Temperature: - 40 C
• Mounting Style: SMD/SMT
• Operating Supply Voltage: 3 V to 3.6 V
• Supply Current (max): 660 mA
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

8.2.2
8.3
Pericom Semiconductor
When the locked delayed memory read request transaction moves to the head of the
delayed transaction queue, PI7C7300D initiates the transaction as a locked read
transaction by de-asserting LOCK# on the target bus during the first address phase, and
by asserting LOCK# one cycle later. If LOCK# is already asserted (used by another
initiator), PI7C7300D waits to request access to the secondary bus until LOCK# is de-
asserted when the target bus is idle. Note that the existing lock on the target bus could
not have crossed PI7C7300D. Otherwise, the pending queued locked transaction would
not have been queued. When PI7C7300D is able to complete a data transfer with the
locked read transaction, the lock is established on the secondary bus.
When the initiator repeats the locked read transaction on the primary bus with the same
address, transaction type, and byte enable bits, PI7C7300D transfers the read data back to
the initiator, and the lock is then also established on the primary bus.
For PI7C7300D to recognize and respond to the initiator, the initiator’s subsequent
attempts of the read transaction must use the locked transaction sequence (de-assert
LOCK# during address phase, and assert LOCK# one cycle later). If the LOCK#
sequence is not used in subsequent attempts, a master timeout condition may result.
When a master timeout condition occurs, SERR# is conditionally asserted (see Section
7.4), the read data and queued read transaction are discarded, and the LOCK# signal is
de-asserted on the target bus.
Once the intended target has been locked, any subsequent locked transactions initiated on
the initiator bus that are forwarded by PI7C7300D are driven as locked transactions on
the target bus.
The first transaction to establish LOCK# must be Memory Read. If the first transaction is
not Memory read, the following transactions behave accordingly:
When PI7C7300D receives a target abort or a master abort in response to the delayed
locked read transaction, this status is passed back to the initiator, and no locks are
established on either the target or the initiator bus. PI7C7300D resumes forwarding
unlocked transactions in both directions.
LOCKED TRANSACTION IN UPSTREAM DIRECTION
PI7C7300D ignores upstream lock and transactions. PI7C7300D will pass these
transactions as normal transactions without lock established.
ENDING EXCLUSIVE ACCESS
- Type 0 Configuration Read/Write induces master abort
- Type 1 Configuration Read/Write induces master abort
- I/O Read induces master abort
- I/O Write induces master abort
- Memory Write induces master abort
Page 65 of 107
3-PORT PCI-TO-PCI BRIDGE
November 2005 - Revision 1.01
PI7C7300D