Differences

This shows you the differences between two versions of the page.

--- irq_controller [2025/04/17 18:12] – arisotura
+++ irq_controller [2025/05/16 22:33] (current) – arisotura
@@ Line 94: / Line 94: @@
 In practice, some IRQ lines likely stay active only for a very short time, while others will stay active as long as the underlying IRQ conditions are met (ie. from hardware components that have their own IRQ status registers; the IRQ line may stay active until the IRQ status register is cleared).
-IRQ trigger type 1 seems to detect a rising edge in the IRQ line, but the IRQ controller fails to fully process and signal the IRQ if the line doesn't stay active long enough. This is pure speculation. Not sure why trigger type 1 would have this problem but not trigger type 5 (the supposed level-trigger type).
+IRQ trigger type 5 seems to fail to register an interrupt when the pulse is too short (ie. doesn't work for VBlank IRQ).
 The trigger type might also play a role in whether/how the IRQ line is buffered or treated? Values 0-7 are possible. Different values affect the different bits (8/12/13/14) in the IRQ enable registers. Some values don't work at all.
@@ Line 130: / Line 130: @@
 | 0x01      | 1       | Timer 1 |
 | 0x02      | 1       | SDIO |
-| 0x03      | 5       | UART0? |
+| 0x03      | 5       | UART0 |
 | 0x04      | 5       | UART1 |
 | 0x05      | 5       | UART2 |
@@ Line 144: / Line 144: @@
 | 0x0F      | 5       | I2C |
 | 0x10      | 5       | vcapt/camera |
-| 0x11      | 5       | vcapt/camera |
+| 0x11      | 5       | H264 encoder |
-| 0x12      | 5       | vout |
+| 0x12      | 5       | H264 decoder |
 | 0x13      | 5       | ??? |
-| 0x14      | 5       | vcapt/camera |
+| 0x14      | 5       | Camera controller |
 | 0x15      | 1       | VBlank end |
 | 0x16      | 1       | VBlank start |