zhangyu-duck opened a new pull request, #21308: URL: https://github.com/apache/nuttx/pull/21308
*Note: Please adhere to [Contributing Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).* ## Summary TriCore interrupt nesting support: - split the single interrupt entry (tricore_doirq) into tricore_irq_direct (fast, nestable dispatch that triggers a low-priority GPSR if a context switch is needed) and tricore_irq_taskswitch (deferred context switch at the lowest SRPN, runs after all nested interrupts complete) - when CONFIG_ARCH_IRQPRIO is disabled, all IRQs go through a single sw-managed entry tricore_irq_sched (ack, dispatch and context switch, no nesting); when enabled, SRPN 1 is the scheduling GPSR and SRPN 2~255 use the nestable direct path - return 0 in up_getusrsp() when regs is NULL, since the fast irq path does not save regs - read the irq number from the ICU LASR register of the current core instead of translating the SRPN through g_srpn_to_irq ## Dependency Depends on the irq pr2 PR (zhangyu-duck:tricore_irq_pr2). This branch is stacked on top of it, so it also contains the commits of the dependent PR(s); only the last 4 commit(s) belong to this PR: - arch/tricore: support interrupt nested - arch/tricore: support sw-managed single-entry IRQ dispatch - arch/tricore: return 0 in up_getusrsp when regs is NULL - arch/tricore: use lasr register to get irq number ## Impact TriCore architecture only (arch/tricore). Interrupt nesting is controlled by CONFIG_ARCH_IRQPRIO. No impact on other architectures. ## Testing Built triboard_tc4x9_com:nsh (TC4xx, cmake) and a2g-tc397-5v-tft:nsh (TC3xx, both make and cmake) with tricore-elf-gcc on Ubuntu host. Each commit passes checkpatch and builds on its own. Tested on both TC4xx (TC4x9) and TC3xx (TC397) boards: system boots normally and ostest passes. ``` nsh> uname -a NuttX 13.1.0 51161b9c255 Oct 31 2026 21:33:35 tricore triboard_tc4x9_com nsh> ostest ... ostest_main: Exiting with status 0 ``` -- 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]
