Home
last modified time | relevance | path

Searched full:additionally (Results 1 – 25 of 150) sorted by relevance

123456

/Zephyr-Core-3.5.0/doc/hardware/peripherals/canbus/
Disotp.rst22 Additionally, it adds a flow control mechanism to influence the sender's
32 the entire payload data and additionally, the first few bytes of payload data.
/Zephyr-Core-3.5.0/samples/drivers/ipm/ipm_ivshmem/boards/
Dqemu_cortex_a53.conf15 # Additionally, our test also uses malloc
/Zephyr-Core-3.5.0/lib/posix/
DKconfig.fs19 is additionally bounded by CONFIG_POSIX_MAX_FDS.
/Zephyr-Core-3.5.0/samples/drivers/virtualization/ivshmem/doorbell/boards/
Dqemu_cortex_a53.conf15 # Additionally, our test also uses malloc
Dqemu_kvm_arm64.conf15 # Additionally, our test also uses malloc
/Zephyr-Core-3.5.0/modules/trusted-firmware-a/
DKconfig11 additionally generate a TF-A image for the Secure Execution
/Zephyr-Core-3.5.0/tests/lib/thrift/ThriftTest/
Doverlay-tls.conf6 # Additionally, upstream Apache Thrift uses socketpair for cancellation rather
/Zephyr-Core-3.5.0/dts/bindings/sensor/
Dst,vl53l1x.yaml16 VDD is not present). Additionally, if XSHUT is connected
/Zephyr-Core-3.5.0/doc/develop/sca/
Dsparse.rst11 address spaces do not get confused. Additionally it supports a ``force``
/Zephyr-Core-3.5.0/samples/bluetooth/direct_adv/
DREADME.rst11 boot direct advertising to the bonded central will be performed. Additionally this sample
/Zephyr-Core-3.5.0/include/zephyr/
Dirq_offload.h28 * Additionally, when CONFIG_IRQ_OFFLOAD_NESTED is set by the
/Zephyr-Core-3.5.0/boards/arm/nrf5340_audio_dk_nrf5340/
DKconfig30 Additionally, the option allocates GPIO pins that will be used by UARTE
/Zephyr-Core-3.5.0/boards/arm/nrf5340dk_nrf5340/
DKconfig30 Additionally, the option allocates GPIO pins that will be used by UARTE
/Zephyr-Core-3.5.0/boards/arm/raytac_mdbt53_db_40_nrf5340/
DKconfig30 Additionally, the option allocates GPIO pins that will be used by UARTE
/Zephyr-Core-3.5.0/boards/arm/raytac_mdbt53v_db_40_nrf5340/
DKconfig30 Additionally, the option allocates GPIO pins that will be used by UARTE
/Zephyr-Core-3.5.0/soc/arm/nxp_lpc/lpc54xxx/
DKconfig.soc52 This is the address the second core will boot from. Additionally this
/Zephyr-Core-3.5.0/boards/arm/thingy53_nrf5340/
DKconfig43 Additionally, the option allocates GPIO pins that will be used by UARTE
/Zephyr-Core-3.5.0/samples/bluetooth/peripheral_accept_list/
DREADME.rst12 accepted if the central device is on the accept list. Additionally, scan response
/Zephyr-Core-3.5.0/samples/basic/hash_map/
DREADME.rst30 Additionally, it is possible to use one of the other Hashmap implementations by specifying
/Zephyr-Core-3.5.0/boards/arm/bl5340_dvk/
DKconfig31 Additionally, the option allocates GPIO pins that will be used by UARTE
/Zephyr-Core-3.5.0/samples/boards/nrf/nrfx/
DREADME.rst13 so that the nrfx_gpiote driver can use it. Additionally, it shows
/Zephyr-Core-3.5.0/samples/boards/mimxrt1060_evk/system_off/
DREADME.rst14 additionally set an alarm 10 seconds in the future to wake up the processor
/Zephyr-Core-3.5.0/tests/subsys/portability/cmsis_rtos_v1/src/
Dkernel_apis.c20 * Additionally, if RC is used for low frequency clock then it has 5% tolerance.
/Zephyr-Core-3.5.0/samples/tfm_integration/
Dtfm_integration.rst38 Additionally, secure boot in TF-M ensures integrity of run time software and
/Zephyr-Core-3.5.0/include/zephyr/arch/arm64/
Dirq.h82 * We additionally set the priority in the interrupt controller at

123456