Searched full:typical (Results 1 – 25 of 77) sorted by relevance
1234
| /Zephyr-Core-3.5.0/dts/bindings/watchdog/ |
| D | ti,tps382x.yaml | 15 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-Core-3.5.0/drivers/sensor/tmp108/ |
| D | tmp108_trigger.c | 37 /* 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-Core-3.5.0/dts/bindings/regulator/ |
| D | nxp,pca9420.yaml | 52 VIN input current limit, in microamperes. Value reflects typical value,
53 below you can find min/typical/max values:
|
| /Zephyr-Core-3.5.0/subsys/sensing/ |
| D | Kconfig | 25 Typical values are 6
|
| /Zephyr-Core-3.5.0/dts/bindings/led/ |
| D | pwm-leds.yaml | 20 persistence time of the human eye). Typical values for the PWM period
|
| /Zephyr-Core-3.5.0/boards/posix/native_sim/ |
| D | board_soc.h | 12 * The "SOC" does not provide almost any of the typical SOC functionality
|
| /Zephyr-Core-3.5.0/drivers/flash/ |
| D | jesd216.h | 319 /* Extract typical and maximum erase times from DW10.
329 * @param typ_ms where to store the typical erase time (in
333 * @retval positive is a multiplier that converts typical erase times
366 /* Typical time for chip (die) erase, in milliseconds */
369 /* Typical time for first byte program, in microseconds */
372 /* Typical time per byte for byte program after first, in
377 /* Typical time for page program, in microseconds */
380 /* Multiplier to get maximum time from typical times. */
|
| /Zephyr-Core-3.5.0/drivers/reset/ |
| D | Kconfig | 13 information about reset controller device. The typical use-case is
|
| /Zephyr-Core-3.5.0/dts/bindings/sensor/ |
| D | raspberrrypi,pico-temp.yaml | 22 using the following equation typical case.
|
| /Zephyr-Core-3.5.0/drivers/syscon/ |
| D | Kconfig | 15 of device. The typical use-case is for some other node's driver, or
|
| /Zephyr-Core-3.5.0/subsys/demand_paging/backing_store/ |
| D | Kconfig | 12 the application. This will be typical as these tend to be very
|
| /Zephyr-Core-3.5.0/boards/posix/native_posix/ |
| D | board_soc.h | 11 * The "SOC" does not provide almost any of the typical SOC functionality
|
| /Zephyr-Core-3.5.0/boards/posix/nrf_bsim/ |
| D | board_soc.h | 11 * The "SOC" does not provide almost any of the typical SOC functionality
|
| /Zephyr-Core-3.5.0/dts/bindings/spi/ |
| D | spi-controller.yaml | 53 choice for a typical "CSn" pin. GPIO_ACTIVE_HIGH may be used if
|
| /Zephyr-Core-3.5.0/doc/services/storage/stream/ |
| D | stream_flash.rst | 11 One typical use of a stream write operation is when receiving a new firmware
|
| /Zephyr-Core-3.5.0/tests/lib/sys_util/src/ |
| D | main.c | 17 * @brief Test wait_for works as expected with typical use cases
|
| /Zephyr-Core-3.5.0/subsys/logging/backends/ |
| D | Kconfig.net | 50 should be selected so that typical messages will fit the buffer.
|
| /Zephyr-Core-3.5.0/samples/drivers/watchdog/ |
| D | README.rst | 12 A typical use case for a watchdog is that the board is restarted in case some piece of code
|
| /Zephyr-Core-3.5.0/samples/basic/custom_dts_binding/ |
| D | README.rst | 18 For typical use cases like LEDs or buttons, the existing :dtcompatible:`gpio-leds` or
|
| /Zephyr-Core-3.5.0/dts/bindings/led_strip/ |
| D | ws2812.yaml | 16 at least 550 ns, with 700 ns or so typical. Pixel order is GRB.
|
| /Zephyr-Core-3.5.0/boards/shields/frdm_cr20a/doc/ |
| D | index.rst | 35 - Receiver sensitivity: –102 dBm, typical
|
| /Zephyr-Core-3.5.0/dts/bindings/display/ |
| D | ftdi,ft800.yaml | 20 typical main clock was 48MHz and this value is 5, the PCLK
|
| /Zephyr-Core-3.5.0/modules/mbedtls/configs/ |
| D | config-coap.h | 98 * The optimal size here depends on the typical size of records.
|
| /Zephyr-Core-3.5.0/doc/develop/flash_debug/ |
| D | host-tools.rst | 27 The typical command to flash the board is:
78 Typical flash layout and configuration
88 A typical flash layout for devices without a ROM bootloader is:
128 A typical flash layout for devices with a ROM bootloader and storage
|
| /Zephyr-Core-3.5.0/dts/bindings/gpio/ |
| D | gpio-controller.yaml | 20 for GPIOs. The typical example is something like this: the hardware
|
1234
