Ouss4 edited a comment on pull request #5336: URL: https://github.com/apache/incubator-nuttx/pull/5336#issuecomment-1041269093
> but ESP32 chip only have two swi interrupt: These are internal CPU interrupts, which means each CPU has both ESP32_CPUINT_SOFTWARE0 and ESP32_CPUINT_SOFTWARE1. They have the same interrupt number but controlled from each CPU's registers. For instance `INTENABLE` of CPU0 enables/disables ESP32_CPUINT_SOFTWARE0/ESP32_CPUINT_SOFTWARE1 of CPU0. The thing that I see is going to be a bit messy is how we dispatch the interrupts. Since they have the same numbers so in NuttX they will have the same `irq` number. EDIT: On a second thought, I don't think this will get that messy. I had the GPIO example in my mind, but this is a bit different. The only issue is enabling the interrupt using `up_enable_irq`, because this function tries to get the CPU from the map. If we only need to enable the software interrupt once and never disable it again, I think we can bypass this. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
