| /hal_espressif-3.6.0/components/wpa_supplicant/src/crypto/ |
| D | dh_groups.c | 1150 #define DH_GROUP(id,safe) \ argument
1153 dh_group ## id ## _order, sizeof(dh_group ## id ## _order), safe }
|
| /hal_espressif-3.6.0/docs/en/api-reference/storage/ |
| D | spi_flash_concurrency.rst | 29 …se operation, the other CPU is put into a blocked state, and all non-IRAM-safe interrupts are disa…
33 .. _iram-safe-interrupt-handlers:
|
| /hal_espressif-3.6.0/docs/zh_CN/api-reference/storage/ |
| D | spi_flash_concurrency.rst | 33 .. _iram-safe-interrupt-handlers:
|
| /hal_espressif-3.6.0/components/spi_flash/ |
| D | README_legacy.rst | 45 …se operation, the other CPU is put into a blocked state, and all non-IRAM-safe interrupts are disa…
47 …ocked state to avoid reading flash cache accidentally. All interrupts not safe for IRAM are disabl…
49 .. _iram-safe-interrupt-handlers:
|
| /hal_espressif-3.6.0/docs/en/api-guides/ |
| D | memory-types.rst | 31 Constant data may also be placed into DRAM, for example if it is used in an non-flash-safe ISR (see…
68 …n registering the interrupt handler. For more information, see :ref:`iram-safe-interrupt-handlers`.
90 There are some possible issues with placement in IRAM, that may cause problems with IRAM-safe inter…
|
| D | openthread.rst | 90 The OpenThread APIs are not thread-safe. When calling OpenThread APIs from other tasks, make sure t…
|
| /hal_espressif-3.6.0/docs/en/api-guides/performance/ |
| D | ram-usage.rst | 131 …ided these functions are not (incorrectly) used from ISRs, this option is safe to enable in all co…
136 …POST_FROM_IRAM_ISR` prevents posting ``esp_event`` events from :ref:`iram-safe-interrupt-handlers`…
142 …the workaround and placed into IRAM instead. For most applications, it is safe to move many of the…
159 … (allocated with :c:macro:`ESP_INTR_FLAG_IRAM` flag), refer to :ref:`iram-safe-interrupt-handlers`…
|
| D | speed.rst | 216 …ly suspended when writing to the built-in SPI flash chip. Only :ref:`iram-safe-interrupt-handlers`…
231 …- If you're sure the entire interrupt handler can run from IRAM (see :ref:`iram-safe-interrupt-han…
232 …safe, if it is going to be executed frequently then consider moving the handler function to IRAM a…
|
| /hal_espressif-3.6.0/components/soc/esp32/include/soc/ |
| D | emac_mac_struct.h | 64 …uint32_t safe : 1; /*When this bit is set the MAC compares the SA field of the received frames wi… member
|
| /hal_espressif-3.6.0/components/bootloader/subproject/main/ld/esp32s2/ |
| D | bootloader.ld | 165 * safe access to up to 16 bytes after the last real instruction, add
|
| /hal_espressif-3.6.0/components/bootloader/subproject/main/ld/esp32h2/ |
| D | bootloader.ld | 163 * safe access to up to 16 bytes after the last real instruction, add
|
| /hal_espressif-3.6.0/components/bootloader/subproject/main/ld/esp32/ |
| D | bootloader.ld | 177 * safe access to up to 16 bytes after the last real instruction, add
|
| /hal_espressif-3.6.0/components/bootloader/subproject/main/ld/esp32c3/ |
| D | bootloader.ld | 165 * safe access to up to 16 bytes after the last real instruction, add
|
| /hal_espressif-3.6.0/components/bootloader/subproject/main/ld/esp32s3/ |
| D | bootloader.ld | 165 * safe access to up to 16 bytes after the last real instruction, add
|
| /hal_espressif-3.6.0/docs/en/api-reference/system/ |
| D | async_memcpy.rst | 44 …must be called after driver is installed successfully. This API is thread safe, so it can be calle…
|
| D | freertos_additions.rst | 185 For ISR safe versions of the functions used above, call :cpp:func:`xRingbufferSendFromISR`, :cpp:fu…
252 …ad of :cpp:func:`xRingbufferReceive` to receive both parts of a split item in a thread safe manner.
410 …internal RAM. Please refer to the :ref:`SPI flash API documentation <iram-safe-interrupt-handlers>…
|
| /hal_espressif-3.6.0/docs/en/api-reference/peripherals/ |
| D | spi_master.rst | 79 …task, the driver is thread safe. However, if multiple tasks try to access the same SPI Device, the…
352 :ref:`iram-safe-interrupt-handlers`). Application code and data used by current task
371 safe.
496 …r callback will crash due to cache miss. For more details, see :ref:`iram-safe-interrupt-handlers`.
|
| /hal_espressif-3.6.0/components/usb/ |
| D | maintainers.md | 137 The HCD API is thread safe however the following limitations should be noted:
141 - `hcd_port_command()` is thread safe, but only one port command can be executed at any one time. T…
|
| /hal_espressif-3.6.0/examples/wifi/espnow/ |
| D | README.md | 27 to make ESPNOW data more safe and more reliable.
|
| /hal_espressif-3.6.0/components/hal/esp32/include/hal/ |
| D | emac_ll.h | 270 mac_regs->gmacff.safe = filter; in emac_ll_set_src_addr_filter()
|
| /hal_espressif-3.6.0/docs/en/api-reference/network/ |
| D | esp_netif.rst | 7 - The APIs it provides are thread safe, even if the underlying TCP/IP stack APIs are not.
|
| /hal_espressif-3.6.0/components/freemodbus/ |
| D | Kconfig | 231 This allows to avoid delays related to processing of non-IRAM-safe interrupts
|
| /hal_espressif-3.6.0/components/esp_system/ld/esp32/ |
| D | sections.ld.in | 349 * safe access to up to 16 bytes after the last real instruction, add
|
| /hal_espressif-3.6.0/components/esp_system/ld/esp32s2/ |
| D | sections.ld.in | 370 * safe access to up to 16 bytes after the last real instruction, add
|
| /hal_espressif-3.6.0/components/esp_system/ld/esp32c3/ |
| D | sections.ld.in | 229 * safe access to up to 16 bytes after the last real instruction, add
|
