Searched full:typically (Results 1 – 25 of 290) sorted by relevance
12345678910>>...12
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_core.rst | 14 data from the network. The ``net_recv_data()`` is typically used by network
17 interface which is typically created by the device driver.
19 For sending, the ``net_send_data()`` can be used. Typically applications do not
|
| D | net_linkaddr.rst | 14 connectivity works correctly in the network stack. Typically the link layer
|
| /Zephyr-latest/dts/bindings/cpu/ |
| D | espressif,riscv.yaml | 16 - 0: ESP32_CPU_CLK_SRC_XTAL - Uses the external crystal clock typically at 40 MHz.
29 description: Value of the external XTAL connected to ESP32. This is typically 40 MHz.
|
| D | espressif,xtensa-lx6.yaml | 16 - 0: ESP32_CPU_CLK_SRC_XTAL - Uses the external crystal clock typically at 40 MHz.
|
| /Zephyr-latest/dts/bindings/sensor/ |
| D | raspberrrypi,pico-temp.yaml | 19 Vbe voltage in microvolts at 27 degrees C. Vbe = 0.706V typically.
33 Typically, a slope of -1.721mV per degree.
|
| /Zephyr-latest/include/zephyr/arch/posix/ |
| D | posix_trace.h | 29 * (typically STDOUT)
31 * outputs (typically STDERR)
|
| /Zephyr-latest/include/zephyr/display/ |
| D | ssd16xx.h | 16 /** The black RAM buffer. This is typically the buffer used to
21 /* The red RAM buffer. This is typically the old frame buffer
|
| /Zephyr-latest/dts/bindings/input/ |
| D | pixart,paw32xx.yaml | 21 The input code for the X axis to report for the device, typically any of
28 The input code for the Y axis to report for the device, typically any of
|
| D | pixart,pat912x.yaml | 20 The input code for the X axis to report for the device, typically any of
26 The input code for the Y axis to report for the device, typically any of
|
| D | pixart,pmw3610.yaml | 26 The input code for the X axis to report for the device, typically any of
33 The input code for the Y axis to report for the device, typically any of
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | fetch_and_get.rst | 41 specific Kconfig. The device specific Kconfig typically allows selecting the
50 There are typically two options provided for each driver where to run trigger
63 * Driver dedicated threads *do* get their own priority typically which lets you
|
| D | triggers.rst | 7 generated events. Typically sensors allow setting up these events to cause
|
| /Zephyr-latest/include/zephyr/bluetooth/audio/ |
| D | tmap.h | 72 * Audio streams in this role are typically bi-directional.
80 * Audio streams in this role are typically bi-directional.
87 * Audio streams in this role are typically uni-directional.
94 * Audio streams in this role are typically uni-directional.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | comparator.rst | 13 Comparators can typically set a trigger which triggers on output changes. This trigger can
23 Embedded comparators can typically be configured at runtime. When enabled, an initial
|
| /Zephyr-latest/tests/net/all/ |
| D | README.txt | 3 as typically the generated configuration is not usable.
|
| /Zephyr-latest/dts/common/ |
| D | skeleton.dtsi | 5 * add a compatible value. The bootloader will typically populate the memory
|
| /Zephyr-latest/dts/bindings/interrupt-controller/ |
| D | nxp,pint.yaml | 23 Number of inputs available to the PINT engine. These inputs are typically
|
| /Zephyr-latest/dts/bindings/clock/ |
| D | st,stm32h7-rcc.yaml | 12 node (typically 'clk_hse, clk_csi', 'pll', ...).
15 Last, bus clocks (typically HCLK, PCLK1, PCLK2) should be configured using matching
|
| D | st,stm32h7rs-rcc.yaml | 12 node (typically 'clk_hse, clk_csi', 'pll', ...).
15 Last, bus clocks (typically HCLK, PCLK1, PCLK2) should be configured using matching
|
| /Zephyr-latest/dts/bindings/w1/ |
| D | zephyr,w1-serial.yaml | 6 # driver. Typically 2 IOs are needed, but some microcontrollers have
|
| /Zephyr-latest/soc/intel/apollo_lake/doc/ |
| D | supported_features.txt | 32 Typically, the master clock is 100MHz, and the firmware by default sets
39 the UART block of interest. Typically a devicetree overlay file would be
|
| /Zephyr-latest/boards/shields/nrf7002ek/boards/ |
| D | nrf9160dk_nrf9160_ns.overlay | 14 /* Typically we use GPIO extender to resolve these conflicts but the
|
| /Zephyr-latest/dts/bindings/gpio/ |
| D | nxp,lpc-gpio-port.yaml | 27 as an interrupt source for their pins (typically ports 0 and 1),
|
| /Zephyr-latest/include/zephyr/net/ |
| D | net_config.h | 41 * Typically this means that the device has IPv6 address set.
47 * Typically this means that the device has IPv4 address set.
|
| /Zephyr-latest/modules/hal_nordic/ |
| D | Kconfig.nrf_regtool | 26 3. Print even more details, which are typically only useful for
|
12345678910>>...12
