SPRUI30H November 2015 – May 2024 DRA745 , DRA746 , DRA750 , DRA756
The general-purpose input signal state can be read directly through EVE_GPIN0 (for inputs 31:0) and EVE_GPIN1 (for inputs 63:32). These registers/GPIN signals are also mapped to the ARP32 INTC2 and INTC3 registers respectively.
The GPIs are used to convey state information (readable in the GPIN registers), or they are enabled as interrupts through the corresponding ARP32_INTn_IRQENABLE_SET register. A rising edge on the GP input is latched as a new interrupt in the corresponding ARP32_INTn_IRQSTATUS register.
The EVE subsystem also provides 64 GPOs. These outputs are manipulated by EVE_GPOUTm, EVE_GPOUTm_SET, EVE_GPOUTm_CLR, and EVE_GPOUTm_PULSE. The EVE_GPOUT0 register group controls eve_gpout[31:0] signals and the EVE_GPOUT1 register group controls eve_gpout[63:32] signals. The current state of the output is detected by reading any of the EVE_GPOUTm, EVE_GPOUTm_SET, EVE_GPOUTm_CLR, or EVE_GPOUTm_PULSE registers. The 64 GPOs are used to drive interrupts or state information to other EVEs in a multi-EVE system.
The GPOUTn register can be explicitly set with the corresponding write data word. Byte or halfword writes are permitted in this case (though support may depend on the specific initiator). A read-modify-write sequence can be required if different tasks own different bits within the GPOUT bank. In this case, access for the read-modify-write sequence must be assured. The EVE_GPOUTm_SET register unconditionally drives the corresponding output event to 1. GPIOm_CLR unconditionally drives the corresponding output event to 0. The EVE_GPOUTm_PULSE register unconditionally drives the output to one for four cycles, then deasserts the signal to 0. If the signal is 1, then the EVE_GPOUTm_PULSE simply deasserts the output signal. Software must ensure the output is low before using the EVE_GPOUTm_PULSE feature.
There are several GPOUT signals connected to arbitration/pressure bits (MFlag bits) in the device.
For EVE1 port 1 and EVE1 port 2 (EVE1 TC0 and EVE1 TC1) MFlag is driven by eve1_gpout[63] and eve1_gpout[62] respectively; eve1_gpout[63] is connected to DMM_P1 and EMIF and eve1_gpout[62] is connected to DMM_P2 and EMIF.
EVE2 MFlag is driven by eve2_gpout[63] and eve2_gpout[62] for EVE2_P1 and EVE2_P2 respectively; gpout[63] is connected to DMM_P2 and EMIF and gpout[62] is connected to DMM_P1 and EMIF.
EVE signals are described in Figure 8-3 through Figure 8-4.
EVE MFlag signals are not used inside L3_MAIN. Within the device main interconnect bandwidth regulators are used to control pressure/arbitration of EVE traffic.