Home
last modified time | relevance | path

Searched refs:retries (Results 76 – 87 of 87) sorted by relevance

1234

/Zephyr-latest/drivers/modem/
Dhl7800.c1008 k_timeout_t timeout, int retries, bool no_id_resp) in send_at_cmd() argument
1055 retries--; in send_at_cmd()
1056 if (retries < 0) { in send_at_cmd()
1057 retries = 0; in send_at_cmd()
1059 } while (ret != 0 && retries > 0); in send_at_cmd()
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Dreports.py363 suite['retries'] = instance.retries
Dtestplan.py657 instance.retries += 1
/Zephyr-latest/scripts/tests/twister/
Dtest_testplan.py1587 assert expected_instances[n]['retries'] == i.retries
/Zephyr-latest/arch/xtensa/core/
DREADME_MMU.txt96 restarted, which retries the refill process, which succeeds in
/Zephyr-latest/drivers/sdhc/
Drcar_mmc.c891 attempts = cmd->retries + 1; in rcar_mmc_request()
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.ll_sw_split1067 save current consumption on retries (in case peer has no buffers to
1072 would happen in the next connection event instead of repeated retries
/Zephyr-latest/doc/releases/
Dmigration-guide-3.6.rst552 ``retries`` is replaced with a pointer to :c:struct:`coap_transmission_parameters`. This allows to
Drelease-notes-3.6.rst476 a fixed number of retries.
Drelease-notes-2.5.rst70 * The :c:func:`coap_pending_init` function now accepts an additional ``retries``
Drelease-notes-3.1.rst1533 * :github:`44507` - net: tcp: No retries of a TCP FIN message
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig986 int "Number of retries per block"

1234