Searched full:stages (Results 1 – 25 of 30) sorted by relevance
12
/hal_espressif-3.5.0/components/hal/include/hal/ |
D | wdt_types.h | 28 * @brief Stages of a Watchdog Timer. A WDT has 4 stages.
|
D | wdt_hal.h | 51 * - Disables the WDT and all of its stages
|
/hal_espressif-3.5.0/components/usb/ |
D | hub.c | 66 * @brief Stages of device enumeration listed in their order of execution 68 …* - These stages MUST BE LISTED IN THE ORDER OF THEIR EXECUTION as the enumeration will simply inc… 71 …* - The short descriptor stages are used to fetch the start particular descriptors that don't have… 156 …int expect_num_bytes; /**< Expected number of bytes for IN transfers stages. Set to 0 fo… 653 …//String descriptor stages are allow to fail. We just don't fetch them and treat enumeration as su… in enum_set_next_stage() 663 //These stages are not waiting for a callback, so we need to re-trigger the enum event in enum_set_next_stage() 813 //Transfer submission stages in enum_handle_events() 830 //Transfer check stages in enum_handle_events()
|
/hal_espressif-3.5.0/ |
D | .gitlab-ci.yml | 1 stages: 35 …# XXX_ATTEMPTS variables (https://docs.gitlab.com/ce/ci/yaml/README.html#job-stages-attempts) are …
|
/hal_espressif-3.5.0/components/esp_system/ |
D | int_wdt.c | 69 //Todo: Check if there's a way to avoid reconfiguring the stages on each feed. in tick_hook() 94 //Todo: Check if there's a way to avoid reconfiguring the stages on each feed. in tick_hook()
|
/hal_espressif-3.5.0/components/hal/ |
D | wdt_hal_iram.c | 38 //Disable RTC WDT, all stages, and all interrupts. in wdt_hal_init() 66 //Disable WDT and stages. in wdt_hal_init()
|
/hal_espressif-3.5.0/docs/en/api-guides/ |
D | unit-tests-legacy.rst | 129 …ons to users. It need user interactions (select cases and select different stages) to run the case. 218 The case will only pass if the last stage passes and all previous stages trigger reset.
|
D | startup.rst | 87 …ore the ``app_main`` function starts running inside the main task. This is split into three stages: 95 …Understanding all stages of ESP-IDF app initialization is often not necessary. To understand initi…
|
D | unit-tests.rst | 117 …ns to users. It needs user interactions (select cases and select different stages) to run the case. 228 …ll the test runner whether a test case is a multiple devices or multiple stages of test case. Thes… 246 … second stage. The case only passes if the last stage passes and all previous stages trigger reset.
|
D | ulp-legacy.rst | 62 …ing files are generated for debugging purposes and are not used at later stages of the build proce…
|
D | ulp.rst | 61 …ing files are generated for debugging purposes and are not used at later stages of the build proce…
|
/hal_espressif-3.5.0/tools/unit-test-app/ |
D | README.md | 47 Unit test uses 3 stages in CI: `build`, `assign_test`, `unit_test`. 126 …* There're some special UT cases (multiple stages case, multiple devices cases) which requires use…
|
/hal_espressif-3.5.0/components/ulp/ |
D | component_ulp_common.mk | 6 # Define names for files generated at different stages
|
/hal_espressif-3.5.0/components/unity/include/ |
D | unity_test_runner.h | 106 * Multiple stages test cases will handle the case that test steps are separated by DUT reset.
|
/hal_espressif-3.5.0/docs/en/api-reference/peripherals/ |
D | usb_host.rst | 164 With reference the graph above, the typical lifecycle involves the following key stages. 327 The typical life cycle of a client task and class driver will go through the following stages:
|
/hal_espressif-3.5.0/components/unity/ |
D | unity_runner.c | 130 // to do a reset for all stages except the last stage. in unity_run_single_test()
|
/hal_espressif-3.5.0/tools/ci/python_packages/ttfw_idf/ |
D | IDFAssignTest.py | 163 print('multiple devices/stages cases must contains at least two test functions')
|
/hal_espressif-3.5.0/components/bootloader_support/src/esp32h2/ |
D | flash_encrypt.c | 23 /* Static functions for stages of flash encryption */
|
/hal_espressif-3.5.0/components/bootloader_support/src/flash_encryption/ |
D | flash_encrypt.c | 37 /* Static functions for stages of flash encryption */
|
/hal_espressif-3.5.0/components/esptool_py/esptool/ |
D | .gitlab-ci.yml | 4 stages:
|
/hal_espressif-3.5.0/examples/bluetooth/bluedroid/classic_bt/bt_spp_acceptor/ |
D | ESP32_SSP.md | 38 There are four stages defined in the Secure Simple Pairing LM process:
|
/hal_espressif-3.5.0/examples/protocols/modbus/tcp/ |
D | example_test.py | 125 """ The method to initialize and handle test stages
|
/hal_espressif-3.5.0/docs/en/api-reference/storage/ |
D | spi_flash.rst | 172 3. The OS functions, provides support of some OS functions (e.g. lock, delay) in different stages (…
|
/hal_espressif-3.5.0/make/ |
D | component_wrapper.mk | 7 # This makefile comprises multiple stages, marked in blocked comments below.
|
/hal_espressif-3.5.0/components/esp_http_server/src/ |
D | esp_httpd_priv.h | 197 * - ESP_FAIL : in case of failure in any of the stages of processing
|
12