Home
last modified time | relevance | path

Searched full:strictly (Results 1 – 25 of 45) sorted by relevance

12

/Zephyr-Core-3.5.0/dts/bindings/regulator/
Dnordic,npm1100.yaml8 strictly following the BUCK node name. For example:
Dnordic,npm6001-regulator.yaml8 children nodes, strictly following the BUCK0..3, LDO0..1 node names. For
Dadi,adp5360-regulator.yaml8 defined as children nodes, strictly following the BUCK and BUCKBOOST node
Dnordic,npm1300-regulator.yaml8 The regulators need to be defined as child nodes, strictly following the
Dnxp,pca9420.yaml8 children nodes, strictly following the BUCK1, BUCK2, LDO1 and LDO2 node names.
/Zephyr-Core-3.5.0/include/zephyr/drivers/
Dcache.h87 * @p addr or a padded @p size is not strictly necessary.
130 * time, so having an aligned @p addr or a padded @p size is not strictly
221 * @p addr or a padded @p size is not strictly necessary.
264 * time, so having an aligned @p addr or a padded @p size is not strictly
/Zephyr-Core-3.5.0/include/zephyr/arch/
Dcache.h97 * @p addr or a padded @p size is not strictly necessary.
144 * time, so having an aligned @p addr or a padded @p size is not strictly
252 * @p addr or a padded @p size is not strictly necessary.
299 * time, so having an aligned @p addr or a padded @p size is not strictly
/Zephyr-Core-3.5.0/include/zephyr/
Dcache.h210 * @p addr or a padded @p size is not strictly necessary.
242 * @p addr or a padded @p size is not strictly necessary.
336 * time, so having an aligned @p addr or a padded @p size is not strictly
369 * time, so having an aligned @p addr or a padded @p size is not strictly
Dspinlock.h252 /* Strictly we don't need atomic_clear() here (which is an in k_spin_unlock()
/Zephyr-Core-3.5.0/cmake/
Dtarget_toolchain_flags.cmake32 # Loading of templates are strictly not needed as they do not set any
/Zephyr-Core-3.5.0/arch/arm/core/cortex_m/
Dswap_helper.S231 /* ISB is not strictly necessary here (stack pointer is not being
304 /* ISB is not strictly necessary here (stack pointer is not being
545 /* ISB is not strictly necessary here (stack pointer is not being
/Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/cavs/include/intel_tgl_adsp/
Dadsp_shim.h88 /* Host memory window control. Not strictly part of the shim block. */
/Zephyr-Core-3.5.0/doc/develop/languages/cpp/
Dindex.rst82 The scope of the minimal C++ library is strictly limited to providing the basic
/Zephyr-Core-3.5.0/tests/kernel/sched/deadline/src/
Dmain.c75 * permits 31 (strictly: the deadline time of the in ZTEST()
/Zephyr-Core-3.5.0/drivers/timer/
Dapic_tsc.c73 * Interpreted strictly, the IA SDM description of the in sys_clock_set_timeout()
/Zephyr-Core-3.5.0/include/zephyr/arch/arm/
Darch.h162 * so we make sure the region is strictly larger than this size by
/Zephyr-Core-3.5.0/tests/kernel/mem_slab/mslab/src/
Dmain.c215 /* not strictly necessary, but keeps coverity checks happy */ in ZTEST()
/Zephyr-Core-3.5.0/include/zephyr/sys/
Drb.h77 * Compares the two nodes and returns true if node A is strictly less
Dtimeutil.h180 * strictly after the base instant in both the reference and local
/Zephyr-Core-3.5.0/subsys/net/lib/lwm2m/
Dlwm2m_registry.h164 * smalles object instance id strictly larger than @p obj_inst_id.
/Zephyr-Core-3.5.0/arch/arm/core/
Duserspace.S281 /* ISB is not strictly necessary here (stack pointer is not being
570 /* ISB is not strictly necessary here (stack pointer is not being
/Zephyr-Core-3.5.0/arch/arm/core/cortex_a_r/
Dswap_helper.S414 /* ISB is not strictly necessary here (stack pointer is not being
/Zephyr-Core-3.5.0/doc/security/
Dsecure-coding.rst93 than one user or process shall not be shared if not strictly
/Zephyr-Core-3.5.0/arch/xtensa/core/
Dxtensa-asm2-util.S146 * strangely when RFI doesn't "return" to a INTLEVEL strictly lower
/Zephyr-Core-3.5.0/doc/services/crypto/
Dtinycrypt.rst90 than the ones strictly required by the intended application. In other words,

12