Home
last modified time | relevance | path

Searched full:consequently (Results 1 – 25 of 26) sorted by relevance

12

/Zephyr-latest/doc/security/standards/
Dindex.rst11 and enforcements are rapidly emerging, and consequently, security standards. These
/Zephyr-latest/dts/bindings/timer/
Dst,stm32-lptim.yaml30 and consequently higher core sleep durations, but impacts the tick precision.
/Zephyr-latest/samples/basic/custom_dts_binding/
DREADME.rst12 Consequently, also GPIO pins are configured in the devicetree and assigned to a specific purpose
/Zephyr-latest/kernel/include/
Dgen_offset.h19 * Consequently, changes made to such symbols may require modifications to the
/Zephyr-latest/kernel/
DKconfig.smp93 reduce the number of IPIs (and consequently ISRs) processed by the
/Zephyr-latest/doc/kernel/services/data_passing/
Dlifos.rst29 queue. Consequently, a data item that holds N bytes of application data
Dfifos.rst29 the queue. Consequently, a data item that holds N bytes of application
/Zephyr-latest/subsys/bluetooth/
DKconfig213 it will be split up into multiple events and consequently, reassembled into a
/Zephyr-latest/doc/kernel/services/scheduling/
Dindex.rst126 Consequently, if a cooperative thread performs lengthy computations,
157 Consequently, if a preemptive thread performs lengthy computations,
/Zephyr-latest/doc/kernel/services/synchronization/
Dmutexes.rst87 owning thread's priority was previously raised. Consequently it is recommended
/Zephyr-latest/boards/nordic/nrf9160dk/
Dboard.c223 * and consequently the chip will not respond to any command. in early_init()
/Zephyr-latest/arch/arm/core/cortex_a_r/
Dswap_helper.S81 * used since this thread has used it. Consequently, the caller-saved
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Dmain.h166 * The application can consequently call bt_mesh_auth_method_set_<*> to
204 * the application needs to consequently call the
/Zephyr-latest/include/zephyr/crypto/
Dcrypto.h290 * Consequently ivlen = keylen - ctrlen. 'ctrlen' is
/Zephyr-latest/subsys/net/ip/
Dipv6.c705 * the IPv6 header. Consequently the "nexthdr" field of an Extension in net_ipv6_input()
/Zephyr-latest/include/zephyr/drivers/
Dadc.h123 * CONFIG_ADC_CONFIGURABLE_INPUTS is not defined and consequently the
/Zephyr-latest/tests/kernel/context/src/
Dmain.c863 * Consequently, the best we can do for now to test busy waiting is in busy_wait_thread()
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.ll_sw_split887 Consequently, this reduces on-air radio utilization due to redundant
/Zephyr-latest/tests/benchmarks/latency_measure/
DREADME.rst360 caller is in user or kernel space and consequently whether a system call
/Zephyr-latest/drivers/flash/
Dnrf_qspi_nor.c1074 * Consequently, the flash chip can be in the DPD mode at this point. in qspi_init()
/Zephyr-latest/doc/releases/
Dmigration-guide-3.7.rst716 is removed. Consequently, :code:`BT_MESH_MODEL_HEALTH_SRV` definition is changed
Drelease-notes-3.4.rst1010 and consequently higher core sleep durations but impacts the tick precision.
Drelease-notes-3.5.rst649 nRF91 Series. Consequently, the driver was renamed to pwm_nrf_sw.
/Zephyr-latest/doc/develop/application/
Dindex.rst923 potentially affected by the changes. Consequently, rebuilding an application
/Zephyr-latest/include/zephyr/bluetooth/
Dgatt.h1507 * opcode, additional fields, and any attribute value payload. Consequently,

12