kaspar/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2025-12-16 01:53:51 +01:00
Code Releases Activity

cpu/esp8266: doc fixes for esp_task thread

Browse Source
This commit is contained in:
Gunar Schorcht 2018-12-26 17:10:37 +01:00 committed by Schorcht
parent 09da830a2a
commit 8076f393f3
2 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
cpu/esp8266/doc.txt
View File

@ -715,10 +715,10 @@ necessary, for example, if you want to use the built-in WLAN module. The
SDK is also used automatically when software timers are used by activating
the `esp_sw_timer` module.
Internally, the SDK uses its own priority-based multitasking, the **ETS**,
to handle hardware components such as the WiFi interface, or to implement
event-driven functions such as software timers. ETS periodically executes
all ETS tasks with pending events in an infinite loop with the ROM
Internally, the SDK uses its own priority-based multitasking sytsem,
the **ETS**, to handle hardware components such as the WiFi interface, or to
implement event-driven functions such as software timers. ETS periodically
executes all ETS tasks with pending events in an infinite loop with the ROM
function `ets_run`.
ETS doesn't process interrupts directly in interrupt service routines.
@ -726,8 +726,8 @@ Instead, they use the `ets_post` ROM function to send an event to one of the
ETS tasks, which then processes the interrupts asynchronously. Context
switches are not possible in interrupt service routines.
To use SDK functions and keep the system alive, ETS tasks with pending have to
be handled. For that purpose
To use SDK functions and keep the system alive, ETS tasks with pending events
have to be handled. For that purpose
- the `ets_task_func` RIOT thread with highest possible priority is used
- the ROM functions `ets_run` and `ets_post` are overwritten.

12
cpu/esp8266/sdk/ets_task.c
View File

@ -9,10 +9,10 @@
*/
/*
* Internally, the SDK uses its own priority-based multitasking, the *ETS*,
* to handle hardware components such as the WiFi interface, or to implement
* event-driven functions such as software timers. ETS periodically executes
* all ETS tasks with pending events in an infinite loop with the ROM
* Internally, the SDK uses its own priority-based multitasking system,
* the *ETS*, to handle hardware components such as the WiFi interface, or to
* implement event-driven functions such as software timers. ETS periodically
* executes all ETS tasks with pending events in an infinite loop with the ROM
* function *ets_run*.
*
* ETS doesn't process interrupts directly in interrupt service routines.
@ -20,8 +20,8 @@
* ETS tasks, which then processes the interrupts asynchronously. Context
* switches are not possible in interrupt service routines.
*
* To use SDK functions and keep the system alive, ETS tasks with pending have
* to be handled. For that purpose
* To use SDK functions and keep the system alive, ETS tasks with pending
* events have to be handled. For that purpose
*
* - the *ets_task_func* RIOT thread with highest possible priority is used
* - the ROM functions *ets_run* and *ets_post* are overwritten.