| /hal_espressif-latest/components/bt/esp_ble_mesh/mesh_core/ |
| D | friend.c | 787 if (frnd->clear.frnd == prev_friend) { in find_clear()
799 k_delayed_work_submit(&frnd->clear.timer, in friend_clear_sent()
800 K_SECONDS(frnd->clear.repeat_sec)); in friend_clear_sent()
801 frnd->clear.repeat_sec *= 2U; in friend_clear_sent()
813 .addr = frnd->clear.frnd, in send_friend_clear()
841 clear.timer.work); in clear_timeout()
844 BT_DBG("LPN 0x%04x (old) Friend 0x%04x", frnd->lpn, frnd->clear.frnd); in clear_timeout()
846 duration = k_uptime_get_32() - frnd->clear.start; in clear_timeout()
849 frnd->clear.frnd = BLE_MESH_ADDR_UNASSIGNED; in clear_timeout()
858 BT_DBG("LPN 0x%04x (old) Friend 0x%04x", frnd->lpn, frnd->clear.frnd); in clear_procedure_start()
[all …]
|
| D | provisioner_prov.h | 289 void bt_mesh_provisioner_set_prov_bearer(bt_mesh_prov_bearer_t bearers, bool clear);
|
| D | settings.c | 63 clear:1; /* 1 if key needs clearing, 0 if storing */ member
1818 if (update->clear) { in store_pending_keys()
2183 update->clear = 0U; in bt_mesh_store_subnet()
2196 free_slot->clear = 0U; in bt_mesh_store_subnet()
2210 update->clear = 0U; in bt_mesh_store_app_key()
2223 free_slot->clear = 0U; in bt_mesh_store_app_key()
2260 update->clear = 1U; in bt_mesh_clear_subnet()
2273 free_slot->clear = 1U; in bt_mesh_clear_subnet()
2287 update->clear = 1U; in bt_mesh_clear_app_key()
2300 free_slot->clear = 1U; in bt_mesh_clear_app_key()
|
| D | net.h | 133 } clear; member
|
| /hal_espressif-latest/components/wpa_supplicant/src/common/ |
| D | dpp.c | 990 u8 clear[4 + DPP_MAX_NONCE_LEN + 4 + 1]; in dpp_auth_build_req() local
1045 pos = clear; in dpp_auth_build_req()
1107 siv_len = pos - clear; in dpp_auth_build_req()
1108 wpa_hexdump(MSG_DEBUG, "DPP: AES-SIV cleartext", clear, siv_len); in dpp_auth_build_req()
1109 if (aes_siv_encrypt(auth->k1, auth->curve->hash_len, clear, siv_len, in dpp_auth_build_req()
1151 u8 clear[DPP_AUTH_RESP_CLEAR_LEN]; in dpp_auth_build_resp() local
1200 pos = clear; in dpp_auth_build_resp()
1280 siv_len = pos - clear; in dpp_auth_build_resp()
1281 wpa_hexdump(MSG_DEBUG, "DPP: AES-SIV cleartext", clear, siv_len); in dpp_auth_build_resp()
1282 if (aes_siv_encrypt(siv_key, auth->curve->hash_len, clear, siv_len, in dpp_auth_build_resp()
[all …]
|
| /hal_espressif-latest/components/wpa_supplicant/src/crypto/ |
| D | des-internal.c | 399 int des_encrypt(const u8 *clear, const u8 *key, u8 *cypher) in des_encrypt() argument
416 work[0] = WPA_GET_BE32(clear); in des_encrypt()
417 work[1] = WPA_GET_BE32(clear + 4); in des_encrypt()
|
| D | crypto.h | 112 int des_encrypt(const u8 *clear, const u8 *key, u8 *cypher);
542 void crypto_bignum_deinit(struct crypto_bignum *n, int clear);
821 void crypto_ec_point_deinit(struct crypto_ec_point *p, int clear);
|
| /hal_espressif-latest/components/driver/spi/ |
| D | spi_bus_lock.c | 272 IRAM_ATTR static inline uint32_t lock_status_fetch_clear(spi_bus_lock_t *lock, uint32_t clear) in lock_status_fetch_clear() argument
274 return atomic_fetch_and(&lock->status, ~clear); in lock_status_fetch_clear()
288 IRAM_ATTR static inline uint32_t lock_status_clear(spi_bus_lock_t* lock, uint32_t clear) in lock_status_clear() argument
291 uint32_t state = lock_status_fetch_clear(lock, clear); in lock_status_clear()
292 return state & (~clear); in lock_status_clear()
|
| /hal_espressif-latest/tools/esptool_py/docs/en/espefuse/ |
| D | burn-bit-cmd.rst | 15 …ite protected. Note that this option can not disable write protection, or clear any bit which has …
|
| D | burn-block-data-cmd.rst | 19 …write protected. Note that this option can't disable write protection, or clear any bit which has …
|
| D | burn-custom-mac-cmd.rst | 14 …write protected. Note that this option can't disable write protection, or clear any bit which has …
|
| D | burn-key-digest-cmd.rst | 27 …write protected. Note that this option can't disable write protection, or clear any bit which has …
|
| D | index.rst | 64 …ng ``--path-efuse-file``, you can save the written data to a file. Delete the file to clear eFuses.
|
| /hal_espressif-latest/tools/esptool_py/ |
| D | CHANGELOG.md | 35 - **esp32s3**: clear boot control register on hard reset
81 - **esptool**: clear boot control register on ESP32-S3
209 - **cmds**: Make clear that flash type is from eFuse and not detection
|
| D | CONTRIBUTING.rst | 65 * Are comments and documentation written in clear English, with no spelling or grammar errors?
|
| D | LICENSE | 53 program proprietary. To prevent this, we have made it clear that any
226 This section is intended to make thoroughly clear what is believed to
|
| /hal_espressif-latest/components/wpa_supplicant/esp_supplicant/src/crypto/ |
| D | crypto_mbedtls-bignum.c | 69 void crypto_bignum_deinit(struct crypto_bignum *n, int clear) in crypto_bignum_deinit() argument
|
| D | crypto_mbedtls.c | 784 int des_encrypt(const u8 *clear, const u8 *key, u8 *cypher) in des_encrypt() argument
805 ret = mbedtls_des_crypt_ecb(&des, clear, cypher); in des_encrypt()
|
| D | crypto_mbedtls-ec.c | 165 void crypto_ec_point_deinit(struct crypto_ec_point *p, int clear) in crypto_ec_point_deinit() argument
|
| /hal_espressif-latest/tools/esptool_py/test/ |
| D | test_merge_bin.py | 435 total_blocks.clear()
|
| /hal_espressif-latest/components/bt/controller/esp32/ |
| D | Kconfig.in | 367 … If the period value is non-zero, the controller will periodically clear the device information
374 …2. When the refresh period is up, the controller will clear all device information and start filte…
|
| /hal_espressif-latest/components/bt/controller/esp32c3/ |
| D | Kconfig.in | 321 … If the period value is non-zero, the controller will periodically clear the device information
328 …2. When the refresh period is up, the controller will clear all device information and start filte…
|
| /hal_espressif-latest/tools/esptool_py/docs/en/esptool/ |
| D | advanced-commands.rst | 104 …the flash chip to write the status register contents. This can be used to clear write protection b…
|
| /hal_espressif-latest/components/bt/controller/esp32c6/ |
| D | Kconfig.in | 615 … If the period value is non-zero, the controller will periodically clear the device information
622 …2. When the refresh period is up, the controller will clear all device information and start filte…
|
| /hal_espressif-latest/components/bt/controller/esp32h2/ |
| D | Kconfig.in | 607 … If the period value is non-zero, the controller will periodically clear the device information
614 …2. When the refresh period is up, the controller will clear all device information and start filte…
|
