Home
last modified time | relevance | path

Searched full:typical (Results 1 – 25 of 104) sorted by relevance

12345

/Zephyr-latest/subsys/sensing/
DKconfig45 Typical values are 6
53 Typical values are 4096
68 Typical values are 9
76 Typical values are 1024
86 Typical values are 8
/Zephyr-latest/dts/bindings/watchdog/
Dti,tps382x.yaml15 then reset is triggered. The reset has a typical delay time of 200 ms for
25 Time-out period in milliseconds. Typical for TPS3823/4/8 and TPS3823A is
/Zephyr-latest/tests/lib/sys_util/src/
Dmain.c17 * @brief Test wait_for works as expected with typical use cases
42 * @brief Test NUM_VA_ARGS works as expected with typical use cases
57 * @brief Test NUM_VA_ARGS_LESS_1 works as expected with typical use cases
/Zephyr-latest/drivers/sensor/ti/tmp108/
Dtmp108_trigger.c37 /* Wait for typical wake up time, retry if the read fails in tmp108_trigger_handle_one_shot()
38 * assuming the chip should wake up and take a reading after the typical in tmp108_trigger_handle_one_shot()
/Zephyr-latest/dts/bindings/regulator/
Dnxp,pca9420.yaml52 VIN input current limit, in microamperes. Value reflects typical value,
53 below you can find min/typical/max values:
/Zephyr-latest/dts/bindings/led/
Dpwm-leds.yaml20 persistence time of the human eye). Typical values for the PWM period
/Zephyr-latest/boards/native/native_sim/
Dboard_soc.h12 * The "SOC" does not provide almost any of the typical SOC functionality
/Zephyr-latest/drivers/reset/
DKconfig13 information about reset controller device. The typical use-case is
/Zephyr-latest/dts/bindings/sensor/
Draspberrrypi,pico-temp.yaml22 using the following equation typical case.
/Zephyr-latest/drivers/flash/
Djesd216.h321 /* Extract typical and maximum erase times from DW10.
331 * @param typ_ms where to store the typical erase time (in
335 * @retval positive is a multiplier that converts typical erase times
368 /* Typical time for chip (die) erase, in milliseconds */
371 /* Typical time for first byte program, in microseconds */
374 /* Typical time per byte for byte program after first, in
379 /* Typical time for page program, in microseconds */
382 /* Multiplier to get maximum time from typical times. */
DKconfig.nordic_qspi_nor62 most typical NOR flash chips to erase a sector.
/Zephyr-latest/dts/bindings/counter/
Dnordic,nrf-timer.yaml34 up to the nRF54 series, and still remains the most typical maximum frequency for nRF54
/Zephyr-latest/drivers/syscon/
DKconfig15 of device. The typical use-case is for some other node's driver, or
/Zephyr-latest/arch/x86/core/intel64/
Dsmp.c21 * z_sched_ipi() doesn't have the same signature as a typical ISR, so in arch_smp_init()
/Zephyr-latest/boards/native/native_posix/
Dboard_soc.h11 * The "SOC" does not provide almost any of the typical SOC functionality
/Zephyr-latest/subsys/demand_paging/backing_store/
DKconfig12 the application. This will be typical as these tend to be very
/Zephyr-latest/boards/native/nrf_bsim/
Dboard_soc.h11 * The "SOC" does not provide almost any of the typical SOC functionality
/Zephyr-latest/dts/bindings/mipi-dbi/
Dmipi-dbi-spi-device.yaml36 without releasing it. A typical use case is variable length SPI packets
/Zephyr-latest/doc/services/storage/stream/
Dstream_flash.rst11 One typical use of a stream write operation is when receiving a new firmware
/Zephyr-latest/include/zephyr/drivers/sensor/
Dtsl2591.h33 * See datasheet for actual typical gain scales these modes correspond to.
/Zephyr-latest/dts/bindings/spi/
Dspi-controller.yaml53 choice for a typical "CSn" pin. GPIO_ACTIVE_HIGH may be used if
Dspi-device.yaml58 without releasing it. A typical use case is variable length SPI packets
/Zephyr-latest/samples/drivers/watchdog/
DREADME.rst12 A typical use case for a watchdog is that the board is restarted in case some piece of code
/Zephyr-latest/kernel/
DKconfig.mem_domain27 Typical uses might be a set of page tables for that memory domain.
/Zephyr-latest/dts/bindings/led_strip/
Dws2812.yaml16 at least 550 ns, with 700 ns or so typical. Pixel order is GRB.

12345