esp-idf/components/esp_hw_support
morris cbd210b431 Merge branch 'refactor/rename_to_esp_clk_tree_prefix_v5.1' into 'release/v5.1'
esp_clk_tree: Rename clk_tree_xxx to esp_clk_tree_xxx (v5.1)

See merge request espressif/esp-idf!23449
2023-04-28 17:11:46 +08:00
..
dma gdma: avoid manually start/stop when channel is controled by ETM 2023-04-06 10:49:32 +08:00
include Merge branch 'refactor/rename_to_esp_clk_tree_prefix_v5.1' into 'release/v5.1' 2023-04-28 17:11:46 +08:00
port Merge branch 'refactor/rename_to_esp_clk_tree_prefix_v5.1' into 'release/v5.1' 2023-04-28 17:11:46 +08:00
test_apps esp32h4: remove esp32h4 target from peripherals 2023-04-26 18:53:10 +08:00
.build-test-rules.yml ci: move linux host tests to test app folder 2023-03-27 17:41:44 +08:00
CMakeLists.txt esp_clk_tree: Rename clk_tree_xxx to esp_clk_tree_xxx, add compilation warning to clk_tree.h 2023-04-27 11:11:18 +00:00
Kconfig rtc_sleep: workaround systimer stall issue during lightsleep on ESP32C3 2023-03-15 20:33:03 +08:00
README.md
adc_share_hw_ctrl.c
clk_ctrl_os.c esp_clk_tree: Rename clk_tree_xxx to esp_clk_tree_xxx, add compilation warning to clk_tree.h 2023-04-27 11:11:18 +00:00
cpu.c
esp_clk.c esp32h4: remove esp32h4 target from peripherals 2023-04-26 18:53:10 +08:00
esp_ds.c esp32h4: remove esp32h4 target from peripherals 2023-04-26 18:53:10 +08:00
esp_etm.c
esp_gpio_reserve.c gpio: support runtime preserve 2023-03-17 11:59:49 +08:00
esp_hmac.c
esp_memory_utils.c esp_hw_support: Update memory ptr location/property checks 2023-04-26 04:01:38 +00:00
hw_random.c
intr_alloc.c
linker.lf gpio: support runtime preserve 2023-03-17 11:59:49 +08:00
mac_addr.c
modem_clock.c workaround: bypass clock power_domain maintaining since esp32h2 sleep is not supported 2023-03-29 13:23:32 +08:00
mspi_timing_config.h mspi: support 120M DDR flash and psram on S3 (experimental) 2023-04-03 10:30:50 +08:00
mspi_timing_tuning.c mspi: support 120M DDR flash and psram on S3 (experimental) 2023-04-03 10:30:50 +08:00
periph_ctrl.c esp_hw_support: Fix check for SOC_MODEM_CLOCK_IS_INDEPENDENT definition 2023-03-16 01:50:22 +08:00
regi2c_ctrl.c
rtc_module.c
rtc_wdt.c
sdkconfig.rename
sdkconfig.rename.esp32
sdkconfig.rename.esp32c3
sdkconfig.rename.esp32s2
sdkconfig.rename.esp32s3
sleep_clock.c
sleep_cpu.c esp_pm: check sleep retention frame integrity in ci UT 2023-04-26 17:36:46 +08:00
sleep_cpu_asm.S bugfix: fix wrong RvCoreCriticalSleepFrame ptr value after wake restore 2023-04-26 17:36:42 +08:00
sleep_gpio.c
sleep_modem.c fix the issue of failure of receiving beacons in modem state caused by enabling light sleep in wifi min/max modem sleep mode 2023-04-07 05:57:15 +00:00
sleep_modes.c ulp: added sleep support for lp core 2023-04-27 09:51:41 +08:00
sleep_retention.c bugfix: no need to do retention in deepsleep 2023-03-17 19:45:56 +08:00
sleep_system_peripheral.c
sleep_wake_stub.c esp32h4: remove esp32h4 target from peripherals 2023-04-26 18:53:10 +08:00

README.md

esp_hw_support (G1 component)

This component contains hardware-related operations for supporting the system. These operations are one level above that of hal in that:

  1. it uses system services such as memory allocation, logging, scheduling
  2. it may be multi-step operations involving/affecting multiple parts of the SoC
  3. it offers a service for other components vary from multiple layers (G1, G2 and G3) of ESP-IDF

Implementations that don't fit other components cleanly, but are not worth creating a new component for (yet) may also be placed here as long as they don't pull dependencies other than the core system components.

Event-Task Service (esp_etm)

esp_etm driver design

esp_etm driver is divided into two parts:

  • The core driver, which focuses on ETM channel allocation and offers APIs to connect the channel with ETM tasks and ETM events that come from other peripherals.
  • Peripheral side extensions, e.g. GPTimer support generating different kinds of ETM events, and accept multiple ETM tasks. These extensions are implemented in the peripheral driver, and can be located in different components. Usually, the task and event extensions will simply inherit the interface that defined in the core driver.

See the following class diagram, we take the GPIO and GPTimer as the example to illustrate the architecture of esp_etm driver.

classDiagram
    esp_etm_channel_t "1" --> "1" esp_etm_event_t : Has
    esp_etm_channel_t "1" --> "1" esp_etm_task_t : Has
    class esp_etm_channel_t {
        -int chan_id
        -esp_etm_event_t event
        -esp_etm_task_t task
        +enable() esp_err_t
        +disable() esp_err_t
        +connect(event, task) esp_err_t
        +dump() esp_err_t
    }

    class esp_etm_event_t {
        <<interface>>
        #int event_id
        #etm_trigger_peripheral_t trig_periph
        #del() esp_err_t
    }

    class esp_etm_task_t {
        <<interface>>
        #int task_id
        #etm_trigger_peripheral_t trig_periph
        #del() esp_err_t
    }

    gpio_etm_event_t --|> esp_etm_event_t : Inheritance
    class gpio_etm_event_t {
        -int chan_id
        +bind_gpio(gpio_num_t gpio) esp_err_t
    }

    gpio_etm_task_t --|> esp_etm_task_t : Inheritance
    class gpio_etm_task_t {
        -int chan_id
        +add_gpio(gpio_num) esp_err_t
        +rm_gpio(gpio_num) esp_err_t
    }

    gptimer_t "1" --> "1..*" gptimer_etm_event_t : Has
    gptimer_t "1" --> "1..*" gptimer_etm_task_t : Has
    class gptimer_t {
        -gptimer_etm_event_t[] events
        -gptimer_etm_task_t[] tasks
    }

    gptimer_etm_event_t --|> esp_etm_event_t : Inheritance
    class gptimer_etm_event_t {
    }

    gptimer_etm_task_t --|> esp_etm_task_t : Inheritance
    class gptimer_etm_task_t {
    }