60442a221a
Remove mutex locking in favour of the standard IRQ locking mechanism. The primary problem with the mutex implementation is that mutex locking is forbidden in ISR's. This means that any logging from an interrupt context (e.g. LOG_PANIC in an exception handler), will itself trigger another assertion due its attempt to use a mutex. Furthermore, mutexes are a relatively heavyweight locking scheme, which doesn't necessarily make sense in the context of extremely short locking periods that would be expected from RTT. This change aligns Zephyr with the default RTT locking scheme, which uses interrupt masking to perform access control. Resolves #79403. Signed-off-by: Jordan Yates <jordan@embeint.com> |
||
|---|---|---|
| .. | ||
| acpica | ||
| canopennode | ||
| cmsis | ||
| cmsis-dsp | ||
| cmsis-nn | ||
| fatfs | ||
| hal_ambiq | ||
| hal_ethos_u | ||
| hal_gigadevice | ||
| hal_infineon | ||
| hal_nordic | ||
| hal_nxp | ||
| hal_rpi_pico | ||
| hal_silabs | ||
| hal_st | ||
| hostap | ||
| liblc3 | ||
| littlefs | ||
| loramac-node | ||
| lvgl | ||
| lz4 | ||
| mbedtls | ||
| nanopb | ||
| openthread | ||
| percepio | ||
| segger | ||
| tflite-micro | ||
| thrift | ||
| trusted-firmware-a | ||
| trusted-firmware-m | ||
| uoscore-uedhoc | ||
| zcbor | ||
| Kconfig | ||
| Kconfig.altera | ||
| Kconfig.atmel | ||
| Kconfig.chre | ||
| Kconfig.cypress | ||
| Kconfig.eos_s3 | ||
| Kconfig.esp32 | ||
| Kconfig.imx | ||
| Kconfig.infineon | ||
| Kconfig.intel | ||
| Kconfig.libmetal | ||
| Kconfig.mcuboot | ||
| Kconfig.mcux | ||
| Kconfig.microchip | ||
| Kconfig.nuvoton | ||
| Kconfig.nxp_s32 | ||
| Kconfig.open-amp | ||
| Kconfig.picolibc | ||
| Kconfig.renesas_fsp | ||
| Kconfig.rust | ||
| Kconfig.simplelink | ||
| Kconfig.sof | ||
| Kconfig.stm32 | ||
| Kconfig.sysbuild | ||
| Kconfig.syst | ||
| Kconfig.telink | ||
| Kconfig.tinycrypt | ||
| Kconfig.vega | ||
| Kconfig.wurthelektronik | ||
| Kconfig.xtensa | ||
| modules.cmake | ||