tmedicci opened a new pull request, #11141: URL: https://github.com/apache/nuttx/pull/11141
## Summary * esp32/ble: Lock the scheduler before creating the pinned thread * esp32s3/wireless: Fix typo * esp32/ble: fix saving/restoring the interrupt status flags Whenever we enter/leave a critical section, the interrupt status is saved and, then, restored. However, for the ESP32's BLE adapter, entering/leaving a critical section is done on separate functions that need to be registered as a callback. The status flag was being saved as a global variable. However, calling nested enter_critical_section would overwrite this global variable that was storing the previous flag and, when leaving the last critical section, the restored status would be different from the one expected. The proposed solution for this issue is to create a global array to store the interrupt status flags for nested calls. * esp32/irq: Allow IRAM ISRs to run during SPI flash operation This provides an interface to register ISRs that run from IRAM and keeps track of the non-IRAM interrupts. It enables, for instance, to avoid disabling all the interrupts during a SPI flash operation: IRAM-enabled ISRs are, then, able to run during these operations. * esp32/spiflash: Make it similar to ESP32-S3 by removing cache state * esp32s3/spiflash: Fix comment and remove unused variable * esp32/ble: enable the BLE interrupt during an SPI flash operation This enables us to create a cache to offload semaphores and message queue operations and treat them when the SPI flash operation is finished. By doing that, we avoid packet losses during an SPI flash operation. ## Impact Improve BLE usage on ESP32 by allowing its ISR to run during an SPI flash operation. ## Testing Internal CI testing + ESP32-DevKitC V4 -- 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]
