Home
last modified time | relevance | path

Searched refs:acceptable (Results 1 – 25 of 32) sorted by relevance

12

/Zephyr-latest/tests/drivers/spi/spi_loopback/boards/
Dnucleo_h723zg.overlay7 /* Set div-q to get test clk freq into acceptable SPI freq range */
Dnucleo_h743zi.overlay7 /* Set div-q to get test clk freq into acceptable SPI freq range */
Dnucleo_h745zi_q_stm32h745xx_m4.overlay7 /* Set div-q to get test clk freq into acceptable SPI freq range */
Dnucleo_h745zi_q_stm32h745xx_m7.overlay7 /* Set div-q to get test clk freq into acceptable SPI freq range */
Dnucleo_h753zi.overlay7 /* Set div-q to get test clk freq into acceptable SPI freq range */
/Zephyr-latest/drivers/flash/
DKconfig.rv32m116 this is acceptable or not will depend on the use case.
DKconfig.lpc17 this is acceptable or not will depend on the use case.
DKconfig.mcux21 this is acceptable or not will depend on the use case.
/Zephyr-latest/tests/drivers/spi/spi_loopback/
Doverlay-stm32-spi-16bits.overlay7 /* Set div-q to get test clk freq into acceptable SPI freq range */
/Zephyr-latest/subsys/mgmt/mcumgr/mgmt/
DKconfig27 acceptable, true must be returned by all the registered notification handlers.
/Zephyr-latest/samples/subsys/fs/littlefs/
DREADME.rst92 At the moment, only two types of block devices are acceptable in this sample: SDMMC and MMC.
/Zephyr-latest/tests/kernel/timer/timer_behavior/
DREADME5 1. Timer variance and standard deviation is below defined acceptable values.
/Zephyr-latest/doc/contribute/
Dbin_blobs.rst102 The following binary blob types are acceptable in Zephyr:
115 acceptable. For example, a proprietary and hardware agnostic TCP/IP stack
118 Note that just because a blob has an acceptable type does not imply that it will
/Zephyr-latest/
DCODE_OF_CONDUCT.md42 acceptable behavior and will take appropriate and fair corrective action in
/Zephyr-latest/doc/connectivity/networking/conn_mgr/
Dimplementation.rst242 …* It is acceptable to gate this behind a small timeout (separate from the connection timeout) for …
282 …While connectivity implementations must not break, it is acceptable for implementations to have po…
284 …rectly instructs an underlying technology to disassociate, it would be acceptable for the connecti…
Dmain.rst53 * Both IPv4 and IPv6 addresses are acceptable.
/Zephyr-latest/doc/build/dts/
Dbindings-upstream.rst72 There are only two acceptable ways to write property ``description:``
/Zephyr-latest/boards/adi/max32672evkit/doc/
Dindex.rst244 Refer to the MAX32672 data sheet for acceptable voltage values.
/Zephyr-latest/doc/develop/west/
Dbuilt-in.rst125 ``always``. SHAs may be given as unique prefixes as long as they are acceptable
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Daccess.rst40 the minimum acceptable payload length and the callback to pass them to. Models
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig940 Minimum acceptable block size in a BLOB transfer. The transfer block
950 Maximum acceptable block size in a BLOB transfer. The transfer block
1626 Request did not receive any acceptable Friend Offers.
1645 int "Minimum size of acceptable friend queue (MinQueueSizeLog)"
/Zephyr-latest/doc/kernel/services/
Dinterrupts.rst169 interrupt latency. A high interrupt latency, however, may not be acceptable
289 known at build time, in some cases this may not be acceptable. It is also
/Zephyr-latest/doc/safety/
Dsafety_overview.rst62 measures needed to reduce those risks to acceptable levels.
/Zephyr-latest/doc/kernel/services/timing/
Dclocks.rst280 acceptable.
/Zephyr-latest/boards/intel/adsp/doc/
Dchromebooks_adsp.rst347 but anywhere is acceptable):

12