Home
last modified time | relevance | path

Searched full:worth (Results 1 – 25 of 38) sorted by relevance

12

/Zephyr-latest/include/zephyr/sys/
Dlibc-hooks.h89 * it is not worth placing in its own partition.
91 * storage in z_libc_partition since it is not worth placing in its
/Zephyr-latest/drivers/spi/
Dspi_nrfx_common.c50 * The expected time to wait is quite short so it is not worth paying in spi_nrfx_wake_request()
/Zephyr-latest/soc/st/stm32/stm32f4x/
Dpower.c40 * so it is worth always using the low-power regulator. in pm_state_set()
/Zephyr-latest/doc/services/file_system/
Dindex.rst52 Here is the list of samples worth looking at:
/Zephyr-latest/dts/bindings/gpio/
Dnxp,s32-gpio.yaml34 as the interrupt controller for the corresponding GPIO. It's worth noting that
/Zephyr-latest/drivers/fuel_gauge/sbs_gauge/
Dsbs_gauge.h58 * Why not compute at runtime: It's not worth the memory given having more than a single fuel gauge
/Zephyr-latest/dts/bindings/pinctrl/
Despressif,esp32-pinctrl.yaml108 Another thing worth noting is that all pin properties should be grouped.
/Zephyr-latest/drivers/sensor/tdk/icm42688/
Dicm42688_emul.c188 /* Epsilon is equal to 1.5 bit-counts worth of error. */ in icm42688_emul_get_accel_ranges()
291 /* Epsilon is equal to 1.5 bit-counts worth of error. */ in icm42688_emul_get_gyro_ranges()
/Zephyr-latest/subsys/mgmt/mcumgr/grp/os_mgmt/
DKconfig127 It is worth disabling this option when THREAD_STACK_INFO is disabled,
/Zephyr-latest/dts/bindings/memory-controllers/
Dst,stm32-fmc-sdram.yaml9 is worth to note that while settings are independent, some are shared or are
/Zephyr-latest/arch/arm64/core/
Dreset.S137 * It is worth noting that this is NOT the final logic id (arch_curr_cpu()->id)
/Zephyr-latest/include/zephyr/dt-bindings/mipi_dbi/
Dmipi_dbi.h119 * This should be used when the controller can send a frame worth of data
133 * This should be used when the controller sends a frame worth of data
/Zephyr-latest/subsys/bluetooth/host/
Dbuf.c221 /* we have a view, eat `len`'s worth of data from the parent */ in bt_buf_make_view()
/Zephyr-latest/drivers/timer/
Dmcux_gpt_timer.c229 /* Set initial trigger value to one tick worth of cycles */ in sys_clock_driver_init()
/Zephyr-latest/subsys/fs/
DKconfig.fatfs48 system, it may be worth disabling this option.
/Zephyr-latest/include/zephyr/pm/
Dpolicy.h146 * are worth entering or not.
/Zephyr-latest/doc/services/pm/
Ddevice_runtime.rst95 suspend the device if necessary. It is worth to note that in both cases, the
/Zephyr-latest/arch/arm/core/cortex_a_r/
Dreset.S221 * It is worth noting that this is NOT the final logic id (arch_curr_cpu()->id)
/Zephyr-latest/boards/native/doc/
Darch_soc.rst364 It is worth noting that the embedded SW library is first pre-linked. That is that all symbols which
369 It is also worth noting that all expected Zephyr sections are built and ordered with the Zephyr
/Zephyr-latest/drivers/counter/
Dcounter_smartbond_timer.c82 * during sleep by PDC. It's worth noting that during sleep the clock source of
/Zephyr-latest/drivers/flash/
Dflash_ite_it8xxx2.c286 * chunk worth of data. in ramcode_flash_cmd_write()
/Zephyr-latest/include/zephyr/
Dbindesc.h310 * memory, so it's worth making sure that the layout is really what we
/Zephyr-latest/subsys/net/ip/
Dipv6_pe.c731 * somewhere. Currently this does not look like worth fixing. in renewal_cb()
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/
Dbap.rst376 configuration or set a different one, it is worth noting that it doesn't change
/Zephyr-latest/doc/hardware/pinctrl/
Dindex.rst424 It is worth to note that the only relationship between a device and its

12