You copied the Doc URL to your clipboard.

TCU interrupt signals

The TCU interrupt signals are edge-triggered. The interrupt controller must detect the rising edge of these signals.

The TCU can also output the Secure and Non-secure Event queue, SYNC complete commands, and global interrupts as Message Signaled Interrupts (MSIs) on the QTW/DVM interface. If the system supports capturing MSIs from the TCU, there is no requirement to connect the corresponding interrupt signals in this interface.

The following table shows the TCU interrupt signals.

Table A-9 TCU interrupt interface signals

Signal

Direction

Description

event_q_irpt_s

Output

Event queue, Secure interrupt. Asserts a Secure interrupt to indicate that the Event queue is not empty or has overflowed.

event_q_irpt_ns

Output

Event queue, Non-secure interrupt. Asserts a Non-secure interrupt to indicate that the Event queue is not empty or has overflowed.

cmd_sync_irpt_ns

Output

SYNC complete, Non-secure interrupt. Asserts a Non-secure interrupt to indicate that the CMD_SYNC command is complete.

cmd_sync_irpt_s

Output

SYNC complete, Secure interrupt. Asserts a Secure interrupt to indicate that the CMD_SYNC command is complete.

global_irpt_ns

Output

Asserts a global Non-secure interrupt.

global_irpt_s

Output

Asserts a global Secure interrupt.

ras_irpt

Output

Asserts a Reliability, Availability, and Serviceability (RAS) interrupt.

Note

The MMU-600 cannot output RAS interrupts as MSIs. This output must be connected to an interrupt controller.

pmu_irpt

Output

Asserts a PMU interrupt.

Note

The MMU-600 cannot output PMU interrupts as MSIs. This output must be connected to an interrupt controller.

evento

Output

Event output for connection to processors. This signal is asserted for one cycle to indicate an event that enables processors to wake up from WFE low-power state.

pri_q_irpt_ns

Output

Asserts a Page Request Interface (PRI) queue interrupt.

Was this page helpful? Yes No