ESP8266 Community Forum

Posted: **Mon Jun 04, 2018 9:00 pm**

I have two devices sharing the HSPI bus. They are both interrupt driven (interrupt drives a GPIO pin) and may also be accessed from the user context. What is the preferred/proper way to disable interrupts (e.g. ETS_GPIO_INTR_DISABLE()) in a way that can be nested so that user-context code can safely access the shared resources?

I'm used to a function that disables interrupts and returns the prior interrupt state that you restore when you exit the section. Is there something similar for ESP8266?

Posted: **Thu Sep 20, 2018 7:41 pm**

Although it hasn't solved all of my issues, the InterruptLock class is quite elegant for managing critical sections:

Code: Select all

#include <interrupts.h>

{
   InterruptLock lock;
   criticalStuff();
}

ESP8266 Community Forum

Proper way to implement nested critical sections

Proper way to implement nested critical sections

Re: Proper way to implement nested critical sections