SPRUIE9D May 2017 – May 2024 DRA74P , DRA75P , DRA76P , DRA77P
Address Offset | 0x0000 0000 | ||
Physical Address | 0x4224 0000 | Instance | ISP6P5_SYS1 |
Description | IP Revision Identifier (X.Y.R) Used by software to track features, bugs, and compatibility | ||
Type | R |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
REVISION |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:0 | REVISION | IP Revision | R | See (1) |
ISS ISP |
Address Offset | 0x0000 0004 | ||
Physical Address | 0x4224 0004 | Instance | ISP6P5_SYS1 |
Description | GENERIC PARAMETER REGISTER Information about the IP module's hardware configuration. Actual field format and encoding is up to the module's designer to decide. | ||
Type | R |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | ISIF_RFM_LINE_SIZE | RESERVED | IPIPE_LINE_SIZE |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:29 | RESERVED | R | 0x0 | |
28:16 | ISIF_RFM_LINE_SIZE | Memory line size for the data reformatter in the ISIF module. | R | 0xb00 |
15:13 | RESERVED | R | 0x0 | |
12:0 | IPIPE_LINE_SIZE | Memory line size for the IPIPE module | R | 0xb00 |
ISS ISP |
Address Offset | 0x0000 0008 | ||
Physical Address | 0x4224 0008 | Instance | ISP6P5_SYS1 |
Description | GENERIC PARAMETER REGISTER Information about the IP module's hardware configuration. Actual field format and encoding is up to the module's designer to decide. | ||
Type | R |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | H3A_LINE_SIZE |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:13 | RESERVED | R | 0x0 | |
12:0 | H3A_LINE_SIZE | Memory line size for the H3A module | R | 0xb00 |
ISS ISP |
Address Offset | 0x0000 0010 | ||
Physical Address | 0x4224 0010 | Instance | ISP6P5_SYS1 |
Description | Clock management configuration | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | STANDBYMODE | RESERVED | SOFTRESET | AUTO_IDLE |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:6 | RESERVED | R | 0x0 | |
5:4 | STANDBYMODE | Configuration of the local initiator state management mode. By definition, initiator may generate read/write transaction as long as it is out of STANDBY state. | RW | 0x2 |
0x0: Force-standby mode: local initiator is unconditionally placed in standby state. Backup mode, for debug only. | ||||
0x1: No-standby mode: local initiator is unconditionally placed out of standby state. Backup mode, for debug only. | ||||
0x3: Reserved | ||||
0x2: Smart-standby mode: local initiator standby status depends on local conditions, i.e. the module's functional requirement from the initiator. IP module shall not generate (initiator-related) wakeup events. Generation of the MStandby signal shall be initiated by the firmware by writing ISP5_CTRL.MSTANDBY = 1. | ||||
3:2 | RESERVED | R | 0x0 | |
1 | SOFTRESET | Software reset. The soft reset will cause the MStandby to be asserted as the reset value of the ISP5_CTRL.MSTANDBY bit is 1. After a soft reset, the software shall ensure not to perform any access for 16 clock cycles (OCP-slave port frequency) after writing this bit. The OCP slave port is running at half the frequency of the functional clock. Before issuing a soft reset, the software shall ensure that no more traffic is being generated by the ISP5. Basically, it means that either the camera module shall be stopped from sending data and/or that the ISP5 modules are disabled. The last interrupt triggered by the ISP5 design upon completion of the frame processing is rsz_int_dma. This rsz_int_dma event shall be used to enable clean termination of the processing. The software shall wait a few hundred cycles to trigger the soft reset after upon assertion of the rsz_int_dma, this is to ensure that the BL is completely drained. Furthermore the software shall set the ISP5 in standbymode before issuing the soft reset: Set ISP5_SYSCONFIG.STANDBYMODE = 2 (smart standby) Set ISP5_CTRL.MSTANDBY to 1 Poll for ISP5_CTRL.MSTANDBY_WAIT = 1. Then, the soft reset can be applied ISP5_SYSCONFIG.SOFTRESET = 1. | RW | 0x0 |
0x0: Reset done, no pending action | ||||
0x1: Reset (software or other) ongoing | ||||
0 | AUTO_IDLE | Auto clock gating. Always enabled. | R | 0x1 |
ISS ISP |
Address Offset | 0x0000 0020 | ||
Physical Address | 0x4224 0020 | Instance | ISP6P5_SYS1 |
Description | End Of Interrupt number specification | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | LINE_NUMBER |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:2 | RESERVED | R | 0x0 | |
1:0 | LINE_NUMBER | Software End Of Interrupt (EOI) control. Write number of interrupt output. | RW | 0x0 |
0x0: Reads always 0 (no EOI memory) | ||||
0x1: EOI for interrupt output line #1 | ||||
0x3: EOI for interrupt output line #3 | ||||
0x2: EOI for interrupt output line #2 |
ISS ISP |
Address Offset | 0x0000 0024 | ||
Physical Address | 0x4224 0024 | Instance | ISP6P5_SYS1 |
Description | Per-event raw interrupt status vector. Raw status is set even if event is not enabled. Write 1 to set the (raw) status, mostly for debug. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQSTATUS_RAW2 | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
18 | RSZ_FIFO_OVF | Resizer module overflow This event is set when overflow happens in the RESIZER module. This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. Depending on the mode bein used, the overflow can happen at different places: 1. Bypass mode: overflow happened in the input circular buffer. 2. Pass through mode: overflow happened on the module output interface (MTC) 3. Normal resize mode: overflow happened in the input circular buffer. This event signals that overflow happened in the input data buffering submodule. 1. In normal resizer mode or bypass mode, this event will be triggered when the This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) |
ISS ISP |
Address Offset | 0x0000 0028 | ||
Physical Address | 0x4224 0028 | Instance | ISP6P5_SYS1 |
Description | Per-event 'enabled' interrupt status vector. Enabled status isn't set unless event is enabled. Write 1 to clear the status after interrupt has been serviced (raw status gets cleared, i.e. even if not enabled). The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQSTATUS2 | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event |
Address Offset | 0x0000 002C | ||
Physical Address | 0x4224 002C | Instance | ISP6P5_SYS1 |
Description | Per-event interrupt enable bit vector. Write 1 to set (enable interrupt). Readout equal to corresponding _CLR register. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQENABLE_SET2. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt |
ISS ISP |
Address Offset | 0x0000 0030 | ||
Physical Address | 0x4224 0030 | Instance | ISP6P5_SYS1 |
Description | Per-event interrupt enable bit vector. Write 1 to clear (disable interrupt). Readout equal to corresponding _SET register. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQENABLE_CLR2. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
15 | RSZ_INT_DMA | RESIZER module event: This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
14 | RSZ_INT_LAST_PIX | RESIZER module event: This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
13 | RSZ_INT_REG | RESIZER module event: This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt |
Address Offset | 0x0000 0034 | ||
Physical Address | 0x4224 0034 | Instance | ISP6P5_SYS1 |
Description | Per-event raw interrupt status vector. Raw status is set even if event is not enabled. Write 1 to set the (raw) status, mostly for debug. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQSTATUS_RAW2 | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
18 | RSZ_FIFO_OVF | Resizer module overflow This event is set when overflow happens in the RESIZER module. This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. Depending on the mode bein used, the overflow can happen at different places: 1. Bypass mode: overflow happened in the input circular buffer. 2. Pass through mode: overflow happened on the module output interface (MTC) 3. Normal resize mode: overflow happened in the input circular buffer. This event signals that overflow happened in the input data buffering submodule. 1. In normal resizer mode or bypass mode, this event will be triggered when the This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) |
ISS ISP |
Address Offset | 0x0000 0038 | ||
Physical Address | 0x4224 0038 | Instance | ISP6P5_SYS1 |
Description | Per-event 'enabled' interrupt status vector. Enabled status isn't set unless event is enabled. Write 1 to clear the status after interrupt has been serviced (raw status gets cleared, i.e. even if not enabled). The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQSTATUS2 | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event |
ISS ISP |
Address Offset | 0x0000 003C | ||
Physical Address | 0x4224 003C | Instance | ISP6P5_SYS1 |
Description | Per-event interrupt enable bit vector. Write 1 to set (enable interrupt). Readout equal to corresponding _CLR register. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQENABLE_SET2. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt |
ISS ISP |
Address Offset | 0x0000 0040 | ||
Physical Address | 0x4224 0040 | Instance | ISP6P5_SYS1 |
Description | Per-event interrupt enable bit vector. Write 1 to clear (disable interrupt). Readout equal to corresponding _SET register. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQENABLE_CLR2. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
15 | RSZ_INT_DMA | RESIZER module event: This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
14 | RSZ_INT_LAST_PIX | RESIZER module event: This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
13 | RSZ_INT_REG | RESIZER module event: This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt |
ISS ISP |
Address Offset | 0x0000 0044 | ||
Physical Address | 0x4224 0044 | Instance | ISP6P5_SYS1 |
Description | Per-event raw interrupt status vector. Raw status is set even if event is not enabled. Write 1 to set the (raw) status, mostly for debug. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQSTATUS_RAW2 | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
18 | RSZ_FIFO_OVF | Resizer module overflow This event is set when overflow happens in the RESIZER module. This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. Depending on the mode bein used, the overflow can happen at different places: 1. Bypass mode: overflow happened in the input circular buffer. 2. Pass through mode: overflow happened on the module output interface (MTC) 3. Normal resize mode: overflow happened in the input circular buffer. This event signals that overflow happened in the input data buffering submodule. 1. In normal resizer mode or bypass mode, this event will be triggered when the This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) |
ISS ISP |
Address Offset | 0x0000 0048 | ||
Physical Address | 0x4224 0048 | Instance | ISP6P5_SYS1 |
Description | Per-event 'enabled' interrupt status vector. Enabled status isn't set unless event is enabled. Write 1 to clear the status after interrupt has been serviced (raw status gets cleared, i.e. even if not enabled). The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQSTATUS2 | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event |
ISS ISP |
Address Offset | 0x0000 004C | ||
Physical Address | 0x4224 004C | Instance | ISP6P5_SYS1 |
Description | Per-event interrupt enable bit vector. Write 1 to set (enable interrupt). Readout equal to corresponding _CLR register. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQENABLE_SET2. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt |
ISS ISP |
Address Offset | 0x0000 0050 | ||
Physical Address | 0x4224 0050 | Instance | ISP6P5_SYS1 |
Description | Per-event interrupt enable bit vector. Write 1 to clear (disable interrupt). Readout equal to corresponding _SET register. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQENABLE_CLR2. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
15 | RSZ_INT_DMA | RESIZER module event: This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
14 | RSZ_INT_LAST_PIX | RESIZER module event: This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
13 | RSZ_INT_REG | RESIZER module event: This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt |
ISS ISP |
Address Offset | 0x0000 0054 | ||
Physical Address | 0x4224 0054 | Instance | ISP6P5_SYS1 |
Description | Per-event raw interrupt status vector. Raw status is set even if event is not enabled. Write 1 to set the (raw) status, mostly for debug. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQSTATUS_RAW2 | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
18 | RSZ_FIFO_OVF | Resizer module overflow This event is set when overflow happens in the RESIZER module. This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. Depending on the mode bein used, the overflow can happen at different places: 1. Bypass mode: overflow happened in the input circular buffer. 2. Pass through mode: overflow happened on the module output interface (MTC) 3. Normal resize mode: overflow happened in the input circular buffer. This event signals that overflow happened in the input data buffering submodule. 1. In normal resizer mode or bypass mode, this event will be triggered when the This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Set event (debug) | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Set event (debug) |
ISS ISP |
Address Offset | 0x0000 0058 | ||
Physical Address | 0x4224 0058 | Instance | ISP6P5_SYS1 |
Description | Per-event 'enabled' interrupt status vector. Enabled status isn't set unless event is enabled. Write 1 to clear the status after interrupt has been serviced (raw status gets cleared, i.e. even if not enabled). The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQSTATUS2 | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Clear (raw) event |
ISS ISP |
Address Offset | 0x0000 005C | ||
Physical Address | 0x4224 005C | Instance | ISP6P5_SYS1 |
Description | Per-event interrupt enable bit vector. Write 1 to set (enable interrupt). Readout equal to corresponding _CLR register. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQENABLE_SET2. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
15 | RSZ_INT_DMA | This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
14 | RSZ_INT_LAST_PIX | This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
13 | RSZ_INT_REG | This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Enable interrupt | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Enable interrupt |
ISS ISP |
Address Offset | 0x0000 0060 | ||
Physical Address | 0x4224 0060 | Instance | ISP6P5_SYS1 |
Description | Per-event interrupt enable bit vector. Write 1 to clear (disable interrupt). Readout equal to corresponding _SET register. The ISP5 outputs 4 interrupt lines ISP5_IRQ0 to ISP5_IRQ3. Any internal ISP5 event can be merged on the 4 lines. A same event shall be enabled on only one interrupt line. There is another interrupt register in the memory map, look for ISP5_IRQENABLE_CLR2. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
OCP_ERR_IRQ | RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_DPC_INI | RESERVED | IPIPE_INT_EOF | H3A_INT_EOF | RSZ_INT_EOF1 | RSZ_INT_EOF0 | RESERVED | RSZ_FIFO_IN_BLK_ERR | RSZ_FIFO_OVF | RSZ_INT_CYC_RZB | RSZ_INT_CYC_RZA | RSZ_INT_DMA | RSZ_INT_LAST_PIX | RSZ_INT_REG | H3A_INT | AF_INT | AEW_INT | IPIPEIF_IRQ | IPIPE_INT_HST | IPIPE_INT_BSC | IPIPE_INT_DMA | IPIPE_INT_LAST_PIX | IPIPE_INT_REG | ISIF_INT_3 | ISIF_INT_2 | ISIF_INT_1 | ISIF_INT_0 |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | OCP_ERR_IRQ | An OCP error has been received on the ISP5 master port. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
30 | RESERVED | R | 0x0 | |
29 | IPIPE_INT_DPC_RNEW1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
28 | IPIPE_INT_DPC_RNEW0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
27 | IPIPE_INT_DPC_INI | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
26 | RESERVED | R | 0x0 | |
25 | IPIPE_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
24 | H3A_INT_EOF | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
23 | RSZ_INT_EOF1 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer B engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
22 | RSZ_INT_EOF0 | RESIZER module event: This event signals that the BL has received the eof signal from the resizer A engine which happens one the last transfer in the frame has happened. Note that because the BL has FIFOs it may take some additional time before true data transfter completion to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
21:20 | RESERVED | R | 0x0 | |
19 | RSZ_FIFO_IN_BLK_ERR | This event signals that the minimum vertical blanking period has not been respected causing errors in the input data buffering submodule. This event will be triggered when the rsz_int_reg event of frame N is triggered before the rsz_int_dma of frame N + 1. This event would typically happen at the transition between two frames because there is not enough vertical blanking between frames: the firmware shall take care to ensure enough vertical blanking. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
18 | RSZ_FIFO_OVF | This event would typically happen while processing a frame because the video port pixel clock is too high: the firmware shall take care to use a lower pixel clock at the input of the resizer module. The hardware cannot recover from this error. It will be required to perform a reset of the IP. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
17 | RSZ_INT_CYC_RZB | RESIZER module event: This event is the circular interrupt for RESIZER #B. An event can be triggered every time that RSZ_IRQ_RZB output lines have been written out to the RZB_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, this value should be such that the circular buffer vertical size (set by the RZB_SDR_Y_PTR_E register) is a multiple of RSZ_IRQ_RZB. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
16 | RSZ_INT_CYC_RZA | RESIZER module event: This event is the circular interrupt for RESIZER #A. An event can be triggered every time that RSZ_IRQ_RZA output lines have been written out to the RZA_SDR_Y buffer. The range can go from 1 to 8192 lines. Usually, the circular buffer vertical size (set by the RZA_SDR_Y_PTR_E register) should be a multiple of RSZ_IRQ_RZA. Note that at the time the interrupt is triggered, the actual data write has not taken place. It may take a few hundred of cycles to complete the data write into system memory. This is not an issue since the start of the buffer is read first. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
15 | RSZ_INT_DMA | RESIZER module event: This event is triggered when the last eof (of the two MTC interfaces) is sent out to the BL and that the resizer core has returned to idle. rsz_int_dma is a true indication that all processing is finished for the particular frame on both resizer engines. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
14 | RSZ_INT_LAST_PIX | RESIZER module event: This event is triggered when the last pixel of the valid area is received. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
13 | RSZ_INT_REG | RESIZER module event: This event is triggered when the first pixel of the valid area is received. Shadowed registers can be updated at any time but the new value will take effect on the next rsz_int_reg event. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
12 | H3A_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
11 | AF_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
10 | AEW_INT | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
9 | IPIPEIF_IRQ | IPIPEIF module interrupt | RW | 0x0 |
0x0: No action | ||||
0x1: Disable interrupt | ||||
8 | IPIPE_INT_HST | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
7 | IPIPE_INT_BSC | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
6 | IPIPE_INT_DMA | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
5 | IPIPE_INT_LAST_PIX | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
4 | IPIPE_INT_REG | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
3 | ISIF_INT_3 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
2 | ISIF_INT_2 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
1 | ISIF_INT_1 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt | ||||
0 | ISIF_INT_0 | RW | 0x0 | |
0x0: No action | ||||
0x1: Disable interrupt |
ISS ISP |
Address Offset | 0x0000 0064 | ||
Physical Address | 0x4224 0064 | Instance | ISP6P5_SYS1 |
Description | Per-line DMA enable bit vector Write 1 to set (enable DMA request generation). Readout equal to corresponding _CLR register. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_LAST_PIX | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_HST | IPIPE_INT_BSC |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:5 | RESERVED | R | 0x0 | |
4 | IPIPE_INT_DPC_RNEW1 | Enable for ISP5 DMA request generation on line #2 This DMA request shall be set to transfer the DPC data from memory to the IPIPE internal RAM. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable DMA | ||||
3 | IPIPE_INT_LAST_PIX | Enable for ISP5 DMA request generation on line #3 This DMA request shall be set to transfer the GAMMA data from memory to the IPIPE internal RAM or to initialize the DPC table. One shall set the ISP5_CTRL.DMA3_CFG register before enabling this DMA request. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable DMA | ||||
2 | IPIPE_INT_DPC_RNEW0 | Enable for ISP5 DMA request generation on line #2 This DMA request shall be set to transfer the DPC data from memory to the IPIPE internal RAM. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable DMA | ||||
1 | IPIPE_INT_HST | Enable for ISP5 DMA request generation on line #1 This DMA request shall be set to transfer the HIST data from the IPIPE internal RAM to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable DMA | ||||
0 | IPIPE_INT_BSC | Enable for ISP5 DMA request generation on line #0 This DMA request shall be set to transfer the BSC data from the IPIPE internal RAM to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Enable DMA |
ISS ISP |
Address Offset | 0x0000 0068 | ||
Physical Address | 0x4224 0068 | Instance | ISP6P5_SYS1 |
Description | Per-line DMA clear bit vector Write 1 to clear (disable DMA request generation). Readout equal to corresponding _SET register. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | IPIPE_INT_DPC_RNEW1 | IPIPE_INT_LAST_PIX | IPIPE_INT_DPC_RNEW0 | IPIPE_INT_HST | IPIPE_INT_BSC |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:5 | RESERVED | R | 0x0 | |
4 | IPIPE_INT_DPC_RNEW1 | Clear for ISP5 DMA request generation on line ISP5_DMA_REQ[2]. This DMA request shall be set to transfer the DPC data from memory to the IPIPE internal RAM. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable DMA | ||||
3 | IPIPE_INT_LAST_PIX | Clear for ISP5 DMA request generation on ISP5_DMA_REQ[3]. This DMA request shall be set to transfer the GAMMA data from memory to the IPIPE internal RAM. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable DMA | ||||
2 | IPIPE_INT_DPC_RNEW0 | Clear for ISP5 DMA request generation on ISP5_DMA_REQ[2]. This DMA request shall be set to transfer the DPC data from memory to the IPIPE internal RAM. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable DMA | ||||
1 | IPIPE_INT_HST | Clear for ISP5 DMA request generation on ISP5_DMA_REQ[1]. This DMA request shall be set to transfer the HIST data from the IPIPE internal RAM to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable DMA | ||||
0 | IPIPE_INT_BSC | Clear for ISP5 DMA request generation on ISP5_DMA_REQ[0]. This DMA request shall be set to transfer the BSC data from the IPIPE internal RAM to memory. | RW | 0x0 |
0x0: No action | ||||
0x1: Disable DMA |
ISS ISP |
Address Offset | 0x0000 006C | ||
Physical Address | 0x4224 006C | Instance | ISP6P5_SYS1 |
Description | ISP5 CONTROL REGISTER | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
DMA3_CFG | RESERVED | BSC_RD_CHK | HST_RD_CHK | DPC_EVT_INI | MSTANDBY | VD_PULSE_EXT | PCLK_INV | MFLAG | MSTANDDBY_WAIT | GLBCE_CLK_ENABLE | NSF3V_CLK_ENABLE | CNFB_CLK_ENABLE | CNFA_CLK_ENABLE | BL_CLK_ENABLE | ISIF_CLK_ENABLE | H3A_CLK_ENABLE | RSZ_CLK_ENABLE | IPIPE_CLK_ENABLE | IPIPEIF_CLK_ENABLE | SYNC_ENABLE | PSYNC_CLK_SEL | VBUSM_CIDS | VBUSM_CPRIORITY | OCP_WRNP |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:30 | DMA3_CFG | This bitfield selects the DMA transfer configuration which is used with the ISP5_DMA_REQ[3] DMA request signal. This DMA request is generated from IPIPE_INT_LAST_PIXEL event. One can choose to use this DMA request to either transfer the DPC initialization data, the gamma table or both. | RW | 0x0 |
0x0: No DMA request associated with ISP5_DMA_REQ[3]. | ||||
0x1: DPC DMA request associated with ISP5_DMA_REQ[3]. Expected DMA transfer size is 2 KBytes in the range 0x8000-0x87FF. DPC_EVT_INI shall be set to 0. | ||||
0x3: DPC + GAMMA DMA request associated with ISP5_DMA_REQ[3]. Expected DMA transfer size is 8 KBytes in the range 0x8000-0x87FF and 0xA800-0xBFFF. DPC_EVT_INI shall be set to 0. | ||||
0x2: GAMMA DMA request associated with ISP5_DMA_REQ[3]. Expected DMA transfer size is 6 KBytes in the range 0xA800-0xBFFF. | ||||
29:28 | RESERVED | R | 0x0 | |
27 | BSC_RD_CHK | When the BSC computation is enabled and the BSC DMA request not used to read out the data, this register enables to ensure that the data were read fast enough, else an interrupt IPIPE_BSC_ERR is triggered. The hardware sets automatically this bit to 1 when software can start reading the memory. It is the software responsibility to set this bit to 0 after reading the data. Once the CPU has read the BSC data, it SHALL clear this register, else the PIPE_BSC_ERR will occur. | RW | 0x0 |
0x0: No interrupt generation can happen | ||||
0x1: The CPU can read the data from the memory. Needs to complete fast enough to avoid the interrupt generation. | ||||
26 | HST_RD_CHK | When the HISTOGRAM computation is enabled and the HST DMA request not used to read out the data, this register enables to ensure that the data were read fast enough, else an interrupt IPIPE_HST_ERR is triggered. The hardware sets automatically this bit to 1 when software can start reading the memory. It is the software responsibility to set this bit to 0 after reading the data. Once the CPU has read the histogram data, it SHALL clear this register, else the PIPE_HST_ERR will occur. | RW | 0x0 |
0x0: No interrupt generation can happen | ||||
0x1: The CPU can read the data from the memory. Needs to complete fast enough to avoid the interrupt generation. | ||||
25 | DPC_EVT_INI | Select the IPIPE module event to be used to generate the DMA requests for the DPC submodule. | RW | 0x0 |
0x0: IPIPE_INT_LAST_PIX event is selected. | ||||
0x1: IPIPE_INT_DPC_INI event is selected. | ||||
24 | MSTANDBY | MStandby signal assertion and de-assertion control for power management transitions. After software reset, this bit is asserted. Write '1' to transition from normal mode to idle mode. The firmware needs to ensure that no more ISP5 processing is ongoing before setting up this bit. Write '0' to transition from idle mode to normal mode. The software should poll ISP5_CTRL.MSTANDBY_WAIT = 0 after writing ISP5_CTRL.MSTANDBY = 0 in a transition from idle to normal mode. | RW | 0x1 |
0x0: De-assert MStandby signal. May not be immediate due to power management handshaking btw the MStandby and Wait signals. | ||||
0x1: Assert MStandby signal | ||||
23 | VD_PULSE_EXT | VD pulse extension enable This bit enables or disables the VD extension bridge. By default, the bridge is enabled. At ISS level, it is expected that IPS5_CTRL.VD_PULSE_EXT = 1 when the VPORT gets data from the CSI2 RX module and IPS5_CTRL.VD_PULSE_EXT = 0 when the VPORT gets data from the parallel interface or the CCP2 RX module. There shall be at least three clock cycles between the time this bit is modified and the HD/VD pulse for start of frame comes. | RW | 0x1 |
0x0: Disabled | ||||
0x1: Enabled | ||||
22 | PCLK_INV | Pixel clock inversion This bit enables or disables pixel clock inversion. The ISP5 always samples the data on the rising edge of the pixel clock. Enabling the inversion shifts the resampling period by 1/2 a pixel clock period. PCLK needs to be disabled at ISS level before setting this bit. | RW | 0x0 |
0x0: Normal | ||||
0x1: Inversed | ||||
21 | MFLAG | MFlag signal generation control This bit controls how the OCP MFlag signal is generated on the ISS NOC. | RW | 0x0 |
0x0: The MFlag value is dynamic. | ||||
0x1: The MFlag value is static. The value is set with the ISP5_CTRL.VBUSM_CPRIORITY bitfield. | ||||
20 | MSTANDDBY_WAIT | MStandby / Wait power management status bit. The power management framework of the ISP5 is based on the handshaking of the MStandby and Wait signals. The software is not supposed to write insidle the ISP5 slave port and initiate traffic when ISP5_CTRL.MSTANDBY bit is written. The software can poll this bit to know when MStandby signal is deasserted. | R | 0x0 |
0x0: MStandby signal is de-asserted | ||||
0x1: MStandby signal is asserted | ||||
19 | GLBCE_CLK_ENABLE | GLBCE clock enable | RW | 0x0 |
0x0: Disable | ||||
0x1: Enable | ||||
18 | NSF3V_CLK_ENABLE | NSF3V clock enable | RW | 0x0 |
0x0: Disable | ||||
0x1: Enable | ||||
17 | CNFB_CLK_ENABLE | CNFB clock enable | RW | 0x0 |
0x0: Disable. Since CNF-B is removed , it doesn't have any effect | ||||
0x1: Enable. Since CNF-B is removed , it doesn't have any effect. | ||||
16 | CNFA_CLK_ENABLE | CNFA clock enable | RW | 0x0 |
0x0: Disable | ||||
0x1: Enable | ||||
15 | BL_CLK_ENABLE | BL clock enable | RW | 0x0 |
0x0: Disable | ||||
0x1: Enable | ||||
14 | ISIF_CLK_ENABLE | ISIF clock enable The ISP5 will return OCP_ERROR if one tries to program the module MMR or memory when the clock is disabled. There shall be at least three clock cycles between the time this bit is modified and the HD/VD pulse for start of frame comes. | RW | 0x0 |
0x0: Disable | ||||
0x1: Enable | ||||
13 | H3A_CLK_ENABLE | H3A clock enable The ISP5 will return OCP_ERROR if one tries to program the module MMR or memory when the clock is disabled. | RW | 0x0 |
0x0: Disable | ||||
0x1: Enable | ||||
12 | RSZ_CLK_ENABLE | RESIZER clock enable The ISP5 will return OCP_ERROR if one tries to program the module MMR or memory when the clock is disabled. | RW | 0x0 |
0x0: Disable | ||||
0x1: Enable | ||||
11 | IPIPE_CLK_ENABLE | IPIPE clock enable The ISP5 will return OCP_ERROR if one tries to program the module MMR or memory when the clock is disabled. If DPC is working before NSF3V (working as pre-NSF3V DPC), this bit must be asserted for SW to access DPC MMR entries. | RW | 0x0 |
0x0: Disable | ||||
0x1: Enable | ||||
10 | IPIPEIF_CLK_ENABLE | IPIPEIF clock enable The ISP5 will return OCP_ERROR if one tries to program the module MMR or memory when the clock is disabled. | RW | 0x0 |
0x0: Disable | ||||
0x1: Enable | ||||
9 | SYNC_ENABLE | PCLK Sync module enable | RW | 0x0 |
0x0: Disable. Shall only be used when the video port is not receiving data, e.g., data is read from the IPIPEIF module memory read port. | ||||
0x1: Enable. Shall be used when the video port is receiving data. | ||||
8 | PSYNC_CLK_SEL | PCLK Sync clock select. This bit selects the clock which is used to resynchronize the input pixel clock. | RW | 0x0 |
0x0: Use ISP6_CFG_CLK. Can be used if the input pixel clock is always lower than 213 MHz. Also, this option must not be chosen if DPC is used with CAL if (CAL - DPC - NSF3V - CAL case.) | ||||
0x1: ISP6_FUNC_CLK. Shall be used if the pixel clock is higher than 213 MHz or DPC is used with CAL port. (CAL - DPC - NSF3V - CAL) | ||||
7:4 | VBUSM_CIDS | BL MAX VBUSM CIDs The BL module supports up to 16 CIDs/tags. This bitfield setsup the maximum number of CISs/tags that the BL can use. The actual number of CIDs/tags is setup by VBUSM_CIDS + 1. Tag number 0 to VBUSM_CIDS are used. | RW | 0xf |
3:1 | VBUSM_CPRIORITY | BL VBUSM priority setting | RW | 0x4 |
0x6: Normal Priority VBUSM cpriority[2:0] = 6 | ||||
0x1: High Priority VBUSM cpriority[2:0] = 1 | ||||
0x7: Normal Priority VBUSM cpriority[2:0] = 7 | ||||
0x0: High Priority VBUSM cpriority[2:0] = 0 | ||||
0x2: Medium Priority VBUSM cpriority[2:0] = 2 | ||||
0x4: Normal Priority VBUSM cpriority[2:0] = 4 | ||||
0x5: Normal Priority VBUSM cpriority[2:0] = 5 | ||||
0x3: Medium Priority VBUSM cpriority[2:0] = 3 | ||||
0 | OCP_WRNP | ISP5 OCP master port non-posted write control. | RW | 0x0 |
0x0: All writes are non posted. | ||||
0x1: All writes are posted. |
Address Offset | 0x0000 0070 | ||
Physical Address | 0x4224 0070 | Instance | ISP6P5_SYS1 |
Description | PATTERN GENERATOR REGISTER | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | SRC_SEL | EN | WEN | HDPOL | VDPOL |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:6 | RESERVED | R | 0x0 | |
5:4 | SRC_SEL | Input mux selection | RW | 0x0 |
0x0: ISP5 video port is selected. | ||||
0x1: Reserved | ||||
0x3: Pattern generator is selected. | ||||
0x2: Reserved | ||||
3 | EN | RW | 0x0 | |
0x0: Pattern generator off | ||||
0x1: Enable pattern generator | ||||
2 | WEN | RW | 0x0 | |
0x0: WEN is always activated | ||||
0x1: WEN is on 8 cycles and off 8 cycles | ||||
1 | HDPOL | RW | 0x0 | |
0x0: Active high | ||||
0x1: Active low | ||||
0 | VDPOL | RW | 0x0 | |
0x0: Active high | ||||
0x1: Active low |
ISS ISP |
Address Offset | 0x0000 0074 | ||
Physical Address | 0x4224 0074 | Instance | ISP6P5_SYS1 |
Description | PATTERN GENERATOR REGISTER | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | VDW | RESERVED | HDW |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:28 | RESERVED | R | 0x0 | |
27:16 | VDW | Pattern generator VD width Width = VDW+1 | RW | 0x0 |
15:13 | RESERVED | R | 0x0 | |
12:0 | HDW | Pattern generator HD width Width = HDW+1 | RW | 0x0 |
ISS ISP |
Address Offset | 0x0000 0078 | ||
Physical Address | 0x4224 0078 | Instance | ISP6P5_SYS1 |
Description | PATTERN GENERATOR REGISTER | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
PPLN | HLPFR |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:16 | PPLN | Pattern Generator: pixels per line, PPLN+1 | RW | 0x0 |
15:0 | HLPFR | Pattern Generator: half lines per frame, HLPFR+1 | RW | 0x0 |
ISS ISP |
Address Offset | 0x0000 007C | ||
Physical Address | 0x4224 007C | Instance | ISP6P5_SYS1 |
Description | ISP5 memory access register. One need to pay attention when setting the bit fields in this register such that there is no conflict between the cpu and module accesses. Usually, the ISP5 modules shall have access to the memories and it's only when the isp5 is idle (vertical blanking period or module disabled that the cpu can access the memories. CPU has memory access If the cpu has memory access (read or write) and CPU has priority, it will cause data corruption if the module tries to perform concurrent memory accesses. The module cannot know that the read or write access has not taken place because of cpu accesses. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
IPIPEIF_CMP_LUT2 | IPIPEIF_DECMP_LUT1 | IPIPEIF_DECMP_LUT0 | ISP_GLBCE_TB | RESERVED | IPIPE_GAMMA_RGB_COPY | RESERVED | IPIPE_BSC_TB1 | IPIPE_BSC_TB0 | IPIPE_HST_TB3 | IPIPE_HST_TB2 | IPIPE_HST_TB1 | IPIPE_HST_TB0 | IPIPE_D3L_TB3 | IPIPE_D3L_TB2 | IPIPE_D3L_TB1 | IPIPE_D3L_TB0 | IPIPE_GBC_TB | IPIPE_YEE_TB | IPIPE_GMM_TBR | IPIPE_GMM_TBG | IPIPE_GMM_TBB | IPIPE_DPC_TB | ISIF_DCLAMP | ISIF_LSC_TB1 | ISIF_LSC_TB0 | ISIF_LIN_TB | RESERVED |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31 | IPIPEIF_CMP_LUT2 | IPIPEIF Companding LUT memory access priority. | RW | 0x0 |
0x0: MODULE access has higher priority. | ||||
0x1: CPU access has higher priority. | ||||
30 | IPIPEIF_DECMP_LUT1 | IPIPEIF Memory Read path Decompanding LUT memory access priority. | RW | 0x0 |
0x0: MODULE access has higher priority. | ||||
0x1: CPU access has higher priority. | ||||
29 | IPIPEIF_DECMP_LUT0 | IPIPEIF VPORT Decompanding LUT memory access priority. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority | ||||
28 | ISP_GLBCE_TB | ISP GLBCE TB memory access priority This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
27:25 | RESERVED | Reserved | R | 0x0 |
24 | IPIPE_GAMMA_RGB_COPY | GAMMA table RGB Copy This bit shall be enable when one wants to use the same Gamma table for the R, G and B color components. When the CPU writes the R table, it is automatically copied to the G and B tables if this bit is set. | RW | 0x0 |
0x0: Copy disable Independent RGB gamma table | ||||
0x1: Copy enable Common RGB Gamma table | ||||
23:21 | RESERVED | R | 0x0 | |
20 | IPIPE_BSC_TB1 | IPIPE BSC TB1 memory access priority This memory is expected to be read by the CPU or the DMA to get BSC information during vertical blanking period. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
19 | IPIPE_BSC_TB0 | IPIPE BSC TB0 memory access priority This memory is expected to be read by the CPU or the DMA to get BSC information during vertical blanking period. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
18 | IPIPE_HST_TB3 | IPIPE histogram memory #3 access priority This memory is expected to be read by the CPU or the DMA to get HST information during vertical blanking period. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
17 | IPIPE_HST_TB2 | IPIPE histogram memory #2 access priority This memory is expected to be read by the CPU or the DMA to get HST information during vertical blanking period. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
16 | IPIPE_HST_TB1 | IPIPE histogram memory #1 access priority This memory is expected to be read by the CPU or the DMA to get HST information during vertical blanking period. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
15 | IPIPE_HST_TB0 | IPIPE histogram memory #0 access priority This memory is expected to be read by the CPU or the DMA to get HST information during vertical blanking period. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
14 | IPIPE_D3L_TB3 | D3L TB3 memory access priority This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
13 | IPIPE_D3L_TB2 | D3L TB2 memory access priority This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
12 | IPIPE_D3L_TB1 | D3L TB1 memory access priority This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
11 | IPIPE_D3L_TB0 | D3L TB0 memory access priority This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
10 | IPIPE_GBC_TB | IPIPE GBC TB memory access priority This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
9 | IPIPE_YEE_TB | YEE TB memory access priority This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
8 | IPIPE_GMM_TBR | IPIPE Gamma LUT R memory arbitration This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
7 | IPIPE_GMM_TBG | IPIPE Gamma LUT G memory arbitration This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
6 | IPIPE_GMM_TBB | IPIPE Gamma LUT B memory arbitration This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
5 | IPIPE_DPC_TB | IPIPE defect pixel memory arbitration This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
4 | ISIF_DCLAMP | ISIF DC accumulation memory arbitration This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
3 | ISIF_LSC_TB1 | ISIF LSC memory 1 access This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE has memory access When the module has memory access, the potential concurrent CPU accesses (on the ISP5 memory map) to read the memory are stalled. The CPU will eventually get back the data during the horizontal or vertical blanking periods when the module is not making access anymore. | ||||
0x1: CPU has memory access When the cpu has memory access (read or write), it will cause data corruption if the module tries to perform concurrent memory accesses. The module cannot know that the read or write access has not taken place because of cpu accesses. | ||||
2 | ISIF_LSC_TB0 | ISIF LSC memory 0 access This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE has memory access. When the module has memory access, the potential concurrent CPU accesses (on the ISP5 memory map) to read the memory are stalled. The CPU will eventually get back the data during the horizontal or vertical blanking periods when the module is not making access anymore. | ||||
0x1: CPU has memory access When the cpu has memory access (read or write), it will cause data corruption if the module tries to perform concurrent memory accesses. The module cannot know that the read or write access has not taken place because of cpu accesses. | ||||
1 | ISIF_LIN_TB | ISIF linearity compensation memory arbitration This memory is expected to be written during ISP5 initialization and potentially updated during vertical blanking periods. | RW | 0x0 |
0x0: MODULE access has higher priority | ||||
0x1: CPU access has higher priority. | ||||
0 | RESERVED | R | 0x0 |
ISS ISP |
Address Offset | 0x0000 0080 | ||
Physical Address | 0x4224 0080 | Instance | ISP6P5_SYS1 |
Description | MEMORY REQUEST MINIMUM INTERVAL REGISTER | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
ISIF_R | IPIPEIF_R |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:16 | ISIF_R | Sets the minimum interval btw two consecutive memory requests for the ISIF-Read port. Specified in number of interface clock cycles. | RW | 0x0 |
15:0 | IPIPEIF_R | Sets the minimum interval btw two consecutive memory requests for the IPIPEIF-Read port. Specified in number of interface clock cycles. | RW | 0x0 |
ISS ISP |
Address Offset | 0x0000 0084 | ||
Physical Address | 0x4224 0084 | Instance | ISP6P5_SYS1 |
Description | MEMORY REQUEST MINIMUM INTERVAL REGISTER | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
H3A_W | RESERVED |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:16 | H3A_W | Sets the minimum interval btw two consecutive memory requests for the H3A-Write port. Specified in number of interface clock cycles. | RW | 0x0 |
15:0 | RESERVED | R | 0x0 |
Address Offset | 0x0000 0088 | ||
Physical Address | 0x4224 0088 | Instance | ISP6P5_SYS1 |
Description | BL VBUSM TUNING REGISTER The settings in the register are static and not expected to be modified dynamically. | ||
Type | RW |
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | MFLAG_THRES | LASTCMD_DLY |
Bits | Field Name | Description | Type | Reset |
---|---|---|---|---|
31:6 | RESERVED | R | 0x0 | |
5 | MFLAG_THRES | MFLAG Threshold value The value of this bit field is a threshold which is compared to the MFlag output of the ISP5. If the BL MFlag signal is greater or equal to this thresold the last beat of the VBUSM command is delayed by LASTCMD_DLY cycles. Only values 0, 1 are valid, the least significant bit is tied off to 1 to make a 2-bit bitfield. | RW | 0x1 |
0x0: Thres = 1 | ||||
0x1: Thres = 3 | ||||
4:0 | LASTCMD_DLY | The value of this bitfield represents a delay expressed in cycles (L3 clock). This value is used to delay the last beat of the VBUSM command such that the ISP5 does not loose arbitration at the NOC level because the BL does not generate back to back requests by default. The last beat is delayed untill the counter expires or the new request is accepted. This delay is used when the MFlag output of the ISP5 is greater or equal to MFLAG_THRES. One can set this value to 0 to disable the last command beat delay. | RW | 0x4 |