From ecb75ba669c352360948864220758ca96a1063e5 Mon Sep 17 00:00:00 2001 From: JoveToo Date: Sun, 24 Dec 2017 16:42:00 +0100 Subject: [PATCH] fix typo Merges https://github.com/espressif/esp-idf/pull/1429 --- docs/api-reference/system/esp_timer.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api-reference/system/esp_timer.rst b/docs/api-reference/system/esp_timer.rst index 3e0b8c8f81..53c07a1b8f 100644 --- a/docs/api-reference/system/esp_timer.rst +++ b/docs/api-reference/system/esp_timer.rst @@ -6,7 +6,7 @@ Overview Although FreeRTOS provides software timers, these timers have a few limitations: -- Mmaximum resolution is equal to RTOS tick period +- Maximum resolution is equal to RTOS tick period - Timer callbacks are dispatched from a low-priority task Hardware timers are free from both of the limitations, but often they are less convenient to use. For example, application components may need timer events to fire at certain times in the future, but the hardware timer only contains one "compare" value used for interrupt generation. This means that some facility needs to be built on top of the hardware timer to manage the list of pending events can dispatch the callbacks for these events as corresponding hardware interrupts happen.