| /hal_espressif-3.6.0/tools/unit-test-app/components/test_utils/test/ |
| D | ccomp_timer_test_inst.c | 158 ccomp_test_call_t calls; in perform_test_at_hit_rate() local
164 prepare_calls(hit_rate, alts, sizeof(alts)/sizeof(alts[0]), 10000, &calls); in perform_test_at_hit_rate()
177 perform_calls(&calls); in perform_test_at_hit_rate()
185 free(calls.funcs); in perform_test_at_hit_rate()
192 ccomp_test_call_t calls; in ccomp_test_ref_time() local
194 prepare_calls(0, alts, 1, 10000, &calls); in ccomp_test_ref_time()
198 perform_calls(&calls); in ccomp_test_ref_time()
204 free(calls.funcs); in ccomp_test_ref_time()
|
| /hal_espressif-3.6.0/components/app_trace/sys_view/ext/ |
| D | heap_trace_module.c | 63 U32 *calls = (U32 *)callers; in esp_sysview_heap_trace_alloc() local
72 pPayload = SEGGER_SYSVIEW_EncodeU32(pPayload, calls[i]); in esp_sysview_heap_trace_alloc()
81 U32 *calls = (U32 *)callers; in esp_sysview_heap_trace_free() local
89 pPayload = SEGGER_SYSVIEW_EncodeU32(pPayload, calls[i]); in esp_sysview_heap_trace_free()
|
| /hal_espressif-3.6.0/docs/en/api-reference/network/ |
| D | esp-wifi-mesh.rst | 61 …calls to Wi-Fi API are made. This is due to the fact that the self-organizing mode will internally…
225 …IFI-MESH stack will internally make calls to Wi-Fi APIs. Therefore, **the application layer should…
289 …calls any Wi-Fi APIs**. This will prevent the ESP-WIFI-MESH stack from attempting to call any Wi-F…
291 Therefore, application calls to Wi-Fi APIs should be placed in between calls of :cpp:func:`esp_mesh…
|
| D | esp_netif_driver.rst | 22 …er hand gets called from the I/O driver, so that the driver's code simply calls :cpp:func:`esp_net…
|
| /hal_espressif-3.6.0/tools/ci/ |
| D | check_callgraph.py | 43 self.calls = list() # type: List[str]
193 if target not in last_function.calls:
194 last_function.calls.append(target)
300 for target_rtl_func_name in source_rtl_func.calls + source_rtl_func.refs:
|
| /hal_espressif-3.6.0/docs/en/api-guides/ |
| D | openthread.rst | 63 - s1.1 The main task calls :cpp:func:`esp_vfs_eventfd_register` to initialize the eventfd virtual f…
65 - s1.2 The main task calls :cpp:func:`nvs_flash_init` to initialize the NVS where the Thread networ…
67 - s1.3 **Optional**, The main task calls :cpp:func:`esp_netif_init` only when it wants to create th…
69 - s1.4: The main task calls :cpp:func:`esp_event_loop_create` to create the system Event task and i…
|
| /hal_espressif-3.6.0/docs/en/api-reference/system/ |
| D | power_management.rst | 118 … - **SPI slave**: between calls to :cpp:func:`spi_slave_initialize` and :cpp:func:`spi_slave_free`.
119 …- **Ethernet**: between calls to :cpp:func:`esp_eth_driver_install` and :cpp:func:`esp_eth_driver_…
120 …- **WiFi**: between calls to :cpp:func:`esp_wifi_start` and :cpp:func:`esp_wifi_stop`. If modem sl…
121 …- **TWAI**: between calls to :cpp:func:`twai_driver_install` and :cpp:func:`twai_driver_uninstall`.
122 …:SOC_BT_SUPPORTED and esp32: - **Bluetooth**: between calls to :cpp:func:`esp_bt_controller_enable…
123 …:SOC_BT_SUPPORTED and not esp32: - **Bluetooth**: between calls to :cpp:func:`esp_bt_controller_en…
|
| D | pthread.rst | 18 …ead blocks on an OS synchronization structure like a mutex, or the thread calls any of the functio…
120 …ment is supported and will be called if a thread function exits normally, calls ``pthread_exit()``…
143 …sp_pthreads.h`` header offers custom extensions to control how subsequent calls to ``pthread_creat…
151 …w thread created will inherit the creator's configuration (if that thread calls ``pthread_create()…
|
| D | mem_alloc.rst | 7 …by program control flow) and *heap* (dynamic memory allocated by function calls), as well as stati…
33 … calling ``malloc()``, the ESP-IDF ``malloc()`` implementation internally calls ``heap_caps_malloc…
116 …nal SPI RAM under 4MiB in size can be allocated using standard ``malloc`` calls, or via ``heap_cap…
133 … handler (ISR) context. However this is not recommended, as heap function calls may delay other in…
|
| D | freertos.rst | 63 … - Task that simply calls ``app_main``. This task will self delete when ``app_main`` returns
86 … - Task that simply calls ``app_main``. This task will self delete when ``app_main`` returns
|
| D | esp_event.rst | 67 …// For simplicity sake this example calls esp_event_post_to from app_main, but posting can be done…
160 …ter a single handler to multiple events individually, i.e. using multiple calls to :cpp:func:`esp_…
161 For those multiple calls, the specific event base and event ID can be specified with which the hand…
|
| D | intr_alloc.rst | 41 calls code for DevA but does nothing. Then, ISR handler calls code for DevB, but while doing that,
|
| /hal_espressif-3.6.0/examples/build_system/cmake/import_prebuilt/main/ |
| D | CMakeLists.txt | 9 # `main` calls a function from the library, so link it to `main`
|
| /hal_espressif-3.6.0/docs/en/api-reference/storage/ |
| D | vfs.rst | 11 …orwards the call to that driver. VFS also forwards read, write, and other calls for the given file…
13 … ``/file.txt`` to it together with appropriate mode flags. All subsequent calls to C library funct…
189 2. The application calls ``fopen("/data/config.json", ...)``.
190 3. The VFS component calls ``myfs_open("/config.json", ...)``.
209 … the FIFO. Due to this non-blocking read behavior, higher level C library calls, such as ``fscanf(…
213 …nfigure this separately for input and output either via menuconfig, or by calls to the functions `…
|
| /hal_espressif-3.6.0/docs/en/api-guides/jtag-debugging/ |
| D | debugging-examples.rst | 50 …program halted is expanded showing the call stack. It represents function calls that lead up to th…
52 …hat contains much longer call stack. You will see there, besides function calls, numbers like ``0x…
122 …s. The difference is that "Step Into (F5)" is entering inside subroutines calls, while "Step Over …
135 If you press "Step Into (F5)" instead, then debugger will step inside subroutine calls.
272 You can use ``bt`` or ``backtrace`` to see what function calls lead up to this code::
343 The thread list shows the last function calls per each thread together with the name of C source fi…
366 … several entries. This will let you check what exact sequence of function calls lead to the code w…
458 …nd ``n``). The difference is that ``step`` is entering inside subroutines calls, while ``next`` st…
494 If you enter ``s`` instead, then debugger will step inside subroutine calls::
636 Step program, proceeding through subroutine calls.
[all …]
|
| /hal_espressif-3.6.0/examples/bluetooth/esp_ble_mesh/ble_mesh_wifi_coexist/tutorial/ |
| D | BLE_Mesh_WiFi_Coexist_Example_Walkthrough.md | 99 This demo calls the `board_init` function to:
141 This demo calls the `bluetooth_init` function to:
182 This demo calls the `ble_mesh_init` function to:
238 This demo calls the `wifi_console_init` function:
|
| /hal_espressif-3.6.0/examples/bluetooth/esp_ble_mesh/ble_mesh_fast_provision/fast_prov_server/tutorial/ |
| D | EspBleMesh.md | 80 4. The device calls the `esp_ble_mesh_set_fast_prov_action` API to change itself into the role of a…
83 7. The device calls the `esp_ble_mesh_set_fast_prov_action` API to change itself into the role of a…
|
| /hal_espressif-3.6.0/examples/bluetooth/esp_ble_mesh/ble_mesh_node/onoff_client/tutorial/ |
| D | BLE_Mesh_Node_OnOff_Client_Example_Walkthrough.md | 144 The Generic Onoff Client Model calls the `esp_ble_mesh_generic_client_get_state` API to get the sta…
156 The Generic Onoff Client Model calls the `esp_ble_mesh_generic_client_set_state` API to set the sta…
177 The Generic Onoff Server Model calls the `esp_ble_mesh_model_publish` API to publish messages. Only…
|
| /hal_espressif-3.6.0/components/esp_ipc/ |
| D | Kconfig | 11 …cross-core function calls. See IPC documentation for more details. The default IPC stack size shou…
|
| /hal_espressif-3.6.0/docs/en/api-guides/performance/ |
| D | ram-usage.rst | 56 - Enabling :ref:`newlib-nano-formatting` will reduce the stack usage of any task that calls ``print…
58 - Avoid deep recursive function calls. Individual recursive function calls don't always add a lot o…
96 Normally, optimizing heap usage consists of analyzing the usage and removing calls to ``malloc()`` …
138 …sertion for HAL component will save some IRAM especially for HAL code who calls `HAL_ASSERT` a lot…
|
| /hal_espressif-3.6.0/components/freertos/port/xtensa/ |
| D | readme_xtensa.txt | 474 API calls (solicited frame) are described in human readable form in
599 and then calls the handler (found in the handler table) for the
603 If the interrupt is for the system timer, it calls a special interrupt
604 handler for the system timer tick, which calls _frxt_timer_int then
608 Finally, the handler calls _frxt_int_exit to allow FreeRTOS to perform
657 triggers the debugger (if connected) or calls _xt_panic to freeze the
707 The debug vector handler calls the simulator if running on the ISS,
710 expected, so the debug handler calls _xt_panic to freeze the processor.
717 the debugger (if connected) or calls _xt_panic to freeze the
|
| /hal_espressif-3.6.0/components/esp_netif/ |
| D | README.md | 55 - calls esp_netif_receive to pass incoming data to network stack
|
| /hal_espressif-3.6.0/components/freertos/ |
| D | CMakeLists.txt | 101 # if it is included in the build. It then calls `app_main`
|
| /hal_espressif-3.6.0/examples/system/perfmon/ |
| D | README.md | 33 1. Example starts and calls the first test. This test calls the test function `exec_test_function` …
320 2. Example calls the second test, which runs the same function under tests. This time, a user-provi…
|
| /hal_espressif-3.6.0/components/ulp/ |
| D | README.rst | 23 …Because some of the instruction macros expand to inline function calls, defining such array in glo…
|
