SPRUI30H November 2015 – May 2024 DRA745 , DRA746 , DRA750 , DRA756
This section describes the integration of the module in the device, including information about clocks, resets, and hardware requests. Figure 9-3 summarizes the integration of the module in the device.
Table 9-6 and Table 9-7 list the integration attributes and clock and resets, respectively.
Module Instance | Attributes | |
Power Domain | Interconnect | |
VIP1 VIP2 VIP3 | PD_CAM | L4_PER3 for configuration L3_MAIN for data (through VPDMA module) |
Clocks | ||||
---|---|---|---|---|
Module Instance | Destination Signal Name | Source Signal Name | Source | Description |
VIP1 | L3_CLK PROC_CLK | VIP1_GCLK | PRCM | L3_CLK is the clock used to drive and receive data over the bus to L3_MAIN. The VIP subsystem uses this clock to fetch external data and transfer this data to internal processing PROC_CLK is the clock used to drive data processing within the VIP subsystem. |
L4_CLK | VIP1_GCLK/2 | PRCM | L4_CLK is the interface clock for Memory Mapped Registers (MMR) configuration bus | |
VIP2 | L3_CLK PROC_CLK | VIP2_GCLK | PRCM | L3_CLK is the clock used to drive and receive data over the bus to L3_MAIN. The VIP subsystem uses this clock to fetch external data and transfer this data to internal processing PROC_CLK is the clock used to drive data processing within the VIP subsystem. |
L4_CLK | VIP2_GCLK/2 | PRCM | L4_CLK is the interface clock for Memory Mapped Registers (MMR) configuration bus | |
VIP3 | L3_CLK PROC_CLK | VIP3_GCLK | PRCM | L3_CLK is the clock used to drive and receive data over the bus to L3_MAIN. The VIP subsystem uses this clock to fetch external data and transfer this data to internal processing PROC_CLK is the clock used to drive data processing within the VIP subsystem. |
L4_CLK | VIP3_GCLK/2 | PRCM | L4_CLK is the interface clock for Memory Mapped Registers (MMR) configuration bus | |
Resets | ||||
Module Instance | Destination Signal Name | Source Signal Name | Source | Description |
VIP1 | VIP_RST | CAM_RST | PRCM | VIP1 Reset |
VIP2 | VIP_RST | CAM_RST | PRCM | VIP2 Reset |
VIP3 | VIP_RST | CAM_RST | PRCM | VIP3 Reset |
Interrupt Requests | ||||
Module Instance | Source Signal Name | Destination IRQ_CROSSBAR Input | Default Mapping | Description |
VIP1 | VIP1_IRQ1 | IRQ_CROSSBAR_351 | N/A | VIP1 interrupt requests. These IRQ source signals are not mapped by default to any device INTC. |
VIP1_IRQ2 | IRQ_CROSSBAR_392 | N/A | ||
VIP2 | VIP2_IRQ1 | IRQ_CROSSBAR_352 | N/A | VIP2 interrupt requests. These IRQ source signals are not mapped by default to any device INTC. |
VIP2_IRQ2 | IRQ_CROSSBAR_393 | N/A | ||
VIP3 | VIP3_IRQ1 | IRQ_CROSSBAR_353 | N/A | VIP3 interrupt requests. These IRQ source signals are not mapped by default to any device INTC. |
VIP3_IRQ2 | IRQ_CROSSBAR_394 | N/A |
The “Default Mapping” column in Table 9-8
VIP Hardware Requests shows the default mapping of module IRQ source
signals. These module IRQ source signals can also be mapped to other lines of
each device Interrupt controller through the IRQ_CROSSBAR module,
respectively.
For more information about the
IRQ_CROSSBAR module, see IRQ_CROSSBAR Module Functional Description, in
Control Module.
For more information
about the device interrupt controllers, see Interrupt Controllers.