esp-idf/components/esp_hw_support
KonstantinKondrashov 28aec9594a fix(app_update): Fix CI test_switch_ota by increasing deepsleep
It increases the deepsleep time from 2000 to 20000.
2000 is too small for esp32-s3 chip.
2023-07-21 13:58:20 +08:00
..
dma feat(esp_gdma): add hal interface for common operations 2023-07-10 13:45:57 +08:00
include fix(app_update): Fix CI test_switch_ota by increasing deepsleep 2023-07-21 13:58:20 +08:00
port fix(rtc_clk): fix the issue of missing configuration for calibration cycles of the internal 32 kHz RC 2023-07-04 11:23:07 +08:00
test_apps feat(esp_gdma): add hal interface for common operations 2023-07-10 13:45:57 +08:00
.build-test-rules.yml ci: add access psram with DFS unity test 2023-06-19 10:15:08 +08:00
CMakeLists.txt feat(esp_gdma): add hal interface for common operations 2023-07-10 13:45:57 +08:00
Kconfig Merge branch 'bringup/esp32h2_light_sleep_for_rebase' into 'master' 2023-06-28 10:37:18 +08:00
README.md
adc_share_hw_ctrl.c refactor(adc_calib): Simplify 2nd step coefficient calculation 2023-07-06 14:22:03 +08:00
clk_ctrl_os.c
cpu.c
esp_clk.c
esp_dpa_protection.c
esp_ds.c
esp_etm.c
esp_gpio_reserve.c
esp_hmac.c
esp_memory_utils.c
hw_random.c bugfix: remove the workaround implemented in MR 22773 about the lp_timer 2023-06-26 21:05:16 +08:00
intr_alloc.c
linker.lf feat(esp_gdma): add hal interface for common operations 2023-07-10 13:45:57 +08:00
lp_periph_ctrl.c uart: Support LP_UART port with UART driver on esp32c6 2023-06-16 07:31:40 +00:00
mac_addr.c
modem_clock.c example: bringup light sleep example for esp32h2 2023-06-26 21:05:16 +08:00
mspi_timing_by_mspi_delay.c
mspi_timing_by_mspi_delay.h
mspi_timing_config.c
mspi_timing_config.h
mspi_timing_tuning.c
periph_ctrl.c
regi2c_ctrl.c fix(regi2c): wrong ADC_CALI_PD_WORKAROUND on c6, h2 2023-07-06 17:54:31 +08:00
rtc_module.c fix(soc): soc header files can pass CI check 2023-06-26 23:00:45 +08:00
rtc_wdt.c
sar_periph_ctrl_common.c
sdkconfig.rename
sdkconfig.rename.esp32
sdkconfig.rename.esp32c3
sdkconfig.rename.esp32s2
sdkconfig.rename.esp32s3
sleep_clock.c Merge branch 'ble_dev/support_esp32h2_modem_clock_selection' into 'master' 2023-07-06 13:58:11 +08:00
sleep_cpu.c Power Management: support CPU powered down in light sleep for esp32h2 2023-06-26 20:57:55 +08:00
sleep_cpu_asm.S Power Management: support CPU powered down in light sleep for esp32h2 2023-06-26 20:57:55 +08:00
sleep_gpio.c Power Management: support DFS and PMU feature for esp32h2 2023-06-26 20:57:55 +08:00
sleep_modem.c ieee802154: change BLE_BB/ieee802154_BB 2023-07-03 02:21:58 +00:00
sleep_modes.c fix(app_update): Fix CI test_switch_ota by increasing deepsleep 2023-07-21 13:58:20 +08:00
sleep_retention.c ieee802154: support light sleep 2023-07-03 02:21:58 +00:00
sleep_system_peripheral.c Power Management: support TOP domain powered down in light sleep for esp32h2 2023-06-26 20:58:59 +08:00
sleep_wake_stub.c

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 {
    }