Marius Vikhammer 6fb996b1ac newlib: revert back from spinlocks to using newlib locks for time.h ... Spinlocks from spinlock.h do not disable the scheduler and thus cannot safely be directly used as a locking mechanism. A task holding the lock can get pre-empted, and at that point the new running task will also be allowed to take the spinlock and access whatever it was protecting. Another issue is that the task holding a spinlock could migrate to a different core which in turn would cause the application to fail asserts. The current implementation assumes the core that takes the lock is also the core that releases it. Closes https://github.com/espressif/esp-idf/issues/5762		2020-09-03 09:56:02 +08:00
..
CMakeLists.txt	newlib: separate low-level code in time.c implementation	2020-08-10 15:11:37 +08:00
esp_time_impl.c	newlib: revert back from spinlocks to using newlib locks for time.h	2020-09-03 09:56:02 +08:00