Home
last modified time | relevance | path

Searched full:depending (Results 1 – 25 of 240) sorted by relevance

12345678910

/Zephyr-Core-2.7.6/drivers/serial/
DKconfig.stellaris20 This tells the driver to configure the UART port at boot, depending on
28 This tells the driver to configure the UART port at boot, depending on
36 This tells the driver to configure the UART port at boot, depending on
DKconfig.sifive20 This tells the driver to configure the UART port at boot, depending on
43 This tells the driver to configure the UART port at boot, depending on
/Zephyr-Core-2.7.6/subsys/net/ip/
DKconfig.stack16 be bigger depending on what features are enabled.
25 be bigger depending on what features are enabled.
/Zephyr-Core-2.7.6/drivers/i2s/
DKconfig.sam_ssc29 an output or an input depending on whether the receiver is working
40 an output or an input depending on whether the receiver is working
/Zephyr-Core-2.7.6/include/ipc/
Dipc_service.h84 * @retval Other errno codes depending on the implementation of the backend.
95 * @retval Other errno codes depending on the implementation of the backend.
/Zephyr-Core-2.7.6/subsys/net/l2/ieee802154/
DKconfig68 Select which features level you want on the device. Depending on it,
103 Simultaneously reassemble 802.15.4 fragments depending on
/Zephyr-Core-2.7.6/cmake/linker/ld/gcc/
Dlinker_flags.cmake4 # linker flags themselves are not depending on actual configurations.
/Zephyr-Core-2.7.6/doc/reference/kernel/threads/
Dnothread.rst112 work, depending on driver implementation.
115 work, depending on driver implementation.
/Zephyr-Core-2.7.6/include/arch/xtensa/
Dexc.h24 /* Xtensa uses a variable length stack frame depending on how many
/Zephyr-Core-2.7.6/subsys/net/lib/conn_mgr/
DKconfig14 L4 events "connected" or "disconnected" depending on the result.
/Zephyr-Core-2.7.6/dts/bindings/bluetooth/
Dzephyr,bt-hci-spi-slave.yaml22 GPIO flags are just for example and may be different depending on
/Zephyr-Core-2.7.6/dts/bindings/clock/
Dst,stm32f100-pll-clock.yaml16 with, depending on the case:
Dst,stm32f0-pll-clock.yaml16 with, depending on the case:
Dst,stm32f105-pll-clock.yaml17 with, depending on the case:
/Zephyr-Core-2.7.6/tests/kernel/timer/starve/
DREADME.txt12 minutes, hours, or days to fail, depending on the hardware clock rate
/Zephyr-Core-2.7.6/dts/bindings/gpio/
Dmikro-bus.yaml28 Board's silkscreen may vary depending you board, but coherent with
/Zephyr-Core-2.7.6/doc/_extensions/zephyr/
Ddtcompatible-role.py20 that happens if a binding behaves differently depending on the bus the
/Zephyr-Core-2.7.6/samples/sensor/th02/
DREADME.rst28 devices to I2C. No additional wiring is required. Depending on the board you are
/Zephyr-Core-2.7.6/include/arch/arm64/
Dmacro.inc25 * to three 'movk' depending on the immediate value.
/Zephyr-Core-2.7.6/arch/arm/core/aarch32/cortex_a_r/
Dexc.S23 * depending on the application exception handler implementation.
148 * depending on the type of fault that caused it.
/Zephyr-Core-2.7.6/tests/kernel/device/src/
Dmmio.c51 * We also perform some checks depending on configuration:
148 * We also perform some checks depending on configuration:
212 * We also perform some checks depending on configuration:
/Zephyr-Core-2.7.6/doc/_static/js/
Dscorer.js37 // Additive scores depending on the priority of the object
/Zephyr-Core-2.7.6/doc/guides/optimizations/
Dfootprint.rst56 Depending on your application and platform needs, you can disable MPU/MMU
/Zephyr-Core-2.7.6/samples/bluetooth/hci_pwr_ctrl/
DREADME.rst19 such that energy is being saved depending on how powerful the RSSI of the
/Zephyr-Core-2.7.6/samples/bluetooth/hci_uart/
DREADME.rst70 Depending on the serial port you are using you will need to modify the
103 Depending on the serial port you are using you will need to modify the

12345678910