Renesas IDT Tsi574, User Manual

Page: 131 / 514

6. Event Notification > Port-write Notifications 131
Tsi574 User Manual
June 6, 2016
Integrated Device Technology
www.idt.com
6.6 Port-write Notifications
In the Tsi574, all RapidIO ports can generate port-write messages based on interrupt events. The
system is notified of most events that occur in the Tsi574 RapidIO interfaces through the RapidIO
port-write message. The port-write function is enabled by default, but can be disabled through the
PW_DIS field in the
“RapidIO Port x Mode CSR” on page 302 . Table 13 on page 120 indicates which
events cause RapidIO port-write messages.
When the port-write function is enabled, the occurrence of an enabled port-write capable event causes
a port-write message to be sent to the destination ID specified in the
“RapidIO Port-Write Target
Device ID CSR” on page 285 . If the event occurs but the interrupt capability is disabled (through the
appropriate interrupt enable register) no port-write message is generated. The port-write message is
generated for each event regardless of whether there is already a pending interrupt bit for the event set
in the interrupt status register. However, when a new event occurs before the previous port-write has
been sent, no port-write is sent for the new event. The second port-write is only sent when the first one
is cleared. The outstanding port-writes, if any, are indicated in register
“RapidIO Port Write
Outstanding Request Register” on page 381 .
The port-write packet does not have a guaranteed delivery and does not have an associated response
(see
RapidIO Interconnect Specification (Revision 1.3) ). Depending on system design, a port write can
be sent repeatedly until cleared. A programmable timeout counter controls the frequency the port-write
packets are transmitted (defined in
the PW_TIMER field of the
“RapidIO Port-Write Timeout Control
Register” on page 380 ). When this timer expires, and the port write has not yet been cleared, another
port-write is sent and the timer begins counting again.
Non-outstanding ackID Link_response received with an ackID that is not outstanding
The status of this error is contained in the LR_ILL_ACKID bit in the
“RapidIO Port x Error Detect CSR” on page 286 .
No
Protocol error An unexpected packet or control symbol was received.
The status of this error is contained in the PROT_ERR bit in the “RapidIO
Port x Error Detect CSR” on page 286 .
Yes
Delineation error Received unaligned /SC/ or /PD/ or undefined code-group.
The status of this error is contained in the DELIN_ERR bit in the
“RapidIO Port x Error Detect CSR” on page 286 .
No
Unsolicited acknowledge control
symbol An unexpected acknowledge control symbol was received.
The status of this error is contained in the CS_ACK_ILL bit in the
“RapidIO Port x Error Detect CSR” on page 286 .
Yes
Link time-out An acknowledge-response or Link-response is not received within the
specified time-out interval, see the RIO_SW_LT_CTL register.
The status of this error is contained in the LINK_TO bit in the “RapidIO
Port x Error Detect CSR” on page 286 .
No
Table 14: Error Rate Error Events (Continued)
RapidIO Error Description
Capture
Registers