6. Event Management > Event Notification
CPS-1848 User Manual
146
June 2, 2014
Formal Status
This document is confidential and is subject to an NDA.
Integrated Device Technology
6.3.3
Lane Event Notification
In order for lane errors to trigger any event notification function, the bit associated with the event(s) of interest must be enabled
in the
Lane {0..47} Error Report Enable Register
.
Lane events can trigger interrupt or Standard port-write notification. To enable Standard port-write notification for Lane events,
the
.LANE_PW_EN bit must be set. Once this bit is set, lane events that are in the
will cause a port-write to be sent.
To enable interrupt notification for any lane event, the
.LANE_INT_EN bit must be set. Once this
bit is set, lane events that are enabled in
Lane {0..47} Error Report Enable Register
will cause the interrupt line to be asserted.
To enable Error Log reporting of all enabled lane events for a port, the
Port {0..17} Operations Register
must be set. Once this bit is set for all lanes assigned to that port, all lane events that are enabled in the
will be reported to the Error Log. For more information on how the Error Log can assert interrupts and
Error Log Event Notification Programming Model
.
6.3.4
I
2
C Event Notification
I
2
C events can trigger interrupt or Standard port-write notification. To enable Standard port-write notification for I
2
C events, the
. I2C_PW_EN bit must be set. Once this bit is set, I
2
C events that are enabled as described in
will cause a port-write to be sent.
To enable interrupt notification for any I
2
.I2C_INT_EN bit must be set. Once this bit is
set, I
2
C events that are enabled as described in
will cause the interrupt line to be asserted.
To enable Error Log reporting of I
2
Aux Port Error Report Enable Register
.I2C_LOG_EN bit must be set. Once
this bit is set, I
2
C events that are enabled as described in
will be reported to the Error Log. For more information on
how the Error Log can assert interrupts and send IDT port-writes, see
Error Log Event Notification Programming Model
.
Loss of alignment
Port {0..17} Implementation
Specific Error Report Enable
Register
.LOA_EN = 1 and
Port {0..17} Operations
Register
.PORT_PW_EN = 1
Port {0..17} Implementation
Specific Error Report Enable
Register
.LOA_EN = 1 and
Port {0..17} Operations
Register
.PORT_INT_EN = 1
Port {0..17} Implementation
Specific Error Report Enable
Register
.LOA_EN = 1 and
Port {0..17} Operations
Register
.PORT_LOG_EN = 1
Bad control character sequence
Port {0..17} Implementation
Specific Error Report Enable
Register
.BAD_CTL_EN = 1 and
Port {0..17} Operations
Register
.PORT_PW_EN = 1
Port {0..17} Implementation
Specific Error Report Enable
Register
.BAD_CTL_EN = 1 and
Port {0..17} Operations
Register
.PORT_INT_EN = 1
Port {0..17} Implementation
Specific Error Report Enable
Register
.BAD_CTL_EN = 1 and
Port {0..17} Operations
Register
.PORT_LOG_EN = 1
Lanes reordered
Port {0..17} Implementation
Specific Error Report Enable
Register
.REORDER_EN = 1 and
Port {0..17} Operations
Register
.PORT_PW_EN = 1
Port {0..17} Implementation
Specific Error Report Enable
Register
Port {0..17} Operations
Register
.PORT_INT_EN = 1
Port {0..17} Implementation
Specific Error Report Enable
Register
.REORDER_EN = 1 and
Port {0..17} Operations
Register
.PORT_LOG_EN = 1
Table 53: Physical Layer Event Notification Control (Continued)
Event
Standard Port-Write Reporting
Interrupt Reporting
Error Log Reporting