7d605551cd
The low-level Wi-Fi driver registers two peripheral interrupts to the same CPU interrupt. Although the registered ISR is the same for both peripherals interrupt, it's needed to call `up_enable_irq` to ensure that the interrupt matrix is being set accordingly. Please note that the current implementation of the ESP32-S3's IRQ driver - although allow us to set a callback for each IRQ, which represents the peripherals interrupt - doesn't allow us to call both callbacks when these IRQs refers to a same CPU interrupt. `g_cpu0_intmap` (or `g_cpu1_intmap`) associates each CPU interrupt to a single IRQ/peripheral and, then, when a CPU interrupt is triggered, only the last registered IRQ's callback will be called. This isn't a problem here because 1) the registered callback is the same for both IRQ's (in fact, it considers the CPU interrupt) and 2) we know in advance which peripheral interrupts will be attached to which CPU interrupt and, then, we can set them directly. |
||
|---|---|---|
| .. | ||
| esp32 | ||
| esp32s2 | ||
| esp32s3 | ||
| lx6 | ||
| lx7 | ||
| xtensa | ||
| .gitignore | ||
| arch.h | ||
| elf.h | ||
| inttypes.h | ||
| irq.h | ||
| limits.h | ||
| loadstore.h | ||
| setjmp.h | ||
| simcall.h | ||
| spinlock.h | ||
| stdarg.h | ||
| syscall.h | ||
| types.h | ||