07c370817c
According to the current design on the armv7-a platform, only fiq is processed in TEE, while irq and fiq are processed in REE. If we enable the irq function in TEE, when we process some signal-related scenarios in TEE, such as the ostest sighand testcase, this testcase will call up_irq_enable() to enable irq interrupt in the arm_sigdeliver() function. After the signal processing logic is executed, irq will be disabled again. During the interval of enabling irq, some external device irq interrupts will be enabled, but these external device irqs do not have corresponding handlers registered in TEE, so an "unexpected irq isr exception" will be triggered. Therefore, a better implementation is to keep the original implementation of the up_irq_enable() function, that is, to enable only fiq in TEE and to enable irq and fiq in REE. Then for vendor-specific requirements, such as the need to briefly enable irq during the TEE initialization process and then disable irq before starting APz in TEE, we directly provide a separate implementation of enabling irq in the vendor, without modifying the implementation of the public up_enable_irq() function. Signed-off-by: guoshichao <guoshichao@xiaomi.com> |
||
|---|---|---|
| .github | ||
| arch | ||
| audio | ||
| binfmt | ||
| boards | ||
| cmake | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| dummy | ||
| fs | ||
| graphics | ||
| include | ||
| libs | ||
| mm | ||
| net | ||
| openamp | ||
| pass1 | ||
| sched | ||
| syscall | ||
| tools | ||
| video | ||
| wireless | ||
| .asf.yaml | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| INVIOLABLES.md | ||
| Kconfig | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| ReleaseNotes | ||
Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).
For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.
Getting Started
First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.
Documentation
You can find the current NuttX documentation on the Documentation Page.
Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.
The old NuttX documentation is still available in the Apache wiki.
Supported Boards
NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.
Contributing
If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.
License
The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.