Searched full:two (Results 1 – 25 of 1277) sorted by relevance
12345678910>>...52
| /Zephyr-Core-3.5.0/scripts/dts/python-devicetree/tests/test-bindings/ |
| D | interrupt-2-cell.yaml | 3 description: Interrupt controller with two cells
5 compatible: "interrupt-two-cell"
9 - two
|
| D | phandle-array-controller-2.yaml | 3 description: Controller with two data values
9 - two
|
| /Zephyr-Core-3.5.0/drivers/sensor/ite_tach_it8xxx2/ |
| D | Kconfig | 13 it8xxx2 supports two 16-bit tachometer sensor, each sensor has two
14 input channel and we can select one input from two channel.
|
| /Zephyr-Core-3.5.0/soc/xtensa/espressif_esp32/esp32_net/ |
| D | Kconfig.soc | 38 to the final octet of the base MAC address. If the number of universal MAC addresses is two,
39 only two interfaces (WiFi station and Bluetooth) receive a universally administered MAC address.
41 The remaining two interfaces (WiFi softap and Ethernet) receive local MAC addresses.
48 bool "Two"
|
| /Zephyr-Core-3.5.0/include/zephyr/sys/ |
| D | math_extras.h | 35 * @brief Add two unsigned 16-bit integers.
44 * @brief Add two unsigned 32-bit integers.
54 * @brief Add two unsigned 64-bit integers.
63 * @brief Add two size_t integers.
82 * @brief Multiply two unsigned 16-bit integers.
91 * @brief Multiply two unsigned 32-bit integers.
100 * @brief Multiply two unsigned 64-bit integers.
109 * @brief Multiply two size_t integers.
|
| /Zephyr-Core-3.5.0/samples/subsys/usb/cdc_acm_composite/ |
| D | sample.yaml | 2 description: Application with two CDC ACM instances requires at least
3 two OUT and four IN endpoints on the USB device controller.
|
| /Zephyr-Core-3.5.0/drivers/sensor/lsm6dso/ |
| D | Kconfig | 70 a maximum of two external sensors (if more than two are enabled
71 the system would enumerate only the first two found)
|
| /Zephyr-Core-3.5.0/drivers/sensor/iis2iclx/ |
| D | Kconfig | 70 a maximum of two external sensors (if more than two are enabled
71 the system would enumerate only the first two found)
|
| /Zephyr-Core-3.5.0/drivers/sensor/ism330dhcx/ |
| D | Kconfig | 70 a maximum of two external sensors (if more than two are enabled
71 the system would enumerate only the first two found)
|
| /Zephyr-Core-3.5.0/dts/bindings/memory-controllers/ |
| D | st,stm32-fmc-sdram.yaml | 134 - SDCLK: SDRAM clock period. If two SDRAM devices are used both should
136 - RBURST: Enable burst read mode. If two SDRAM devices are used both
139 latency. If two SDRAM devices are used both should have the same
151 Activate command in number of memory clock cycles. If two SDRAM
156 well as the delay between two consecutive Refresh commands. It is
157 expressed in number of memory clock cycles. If two SDRAM devices are
163 of memory clock cycles. If two SDRAM devices are used, the TRP must be
|
| /Zephyr-Core-3.5.0/samples/bluetooth/encrypted_advertising/ |
| D | README.rst | 27 * Two boards with Bluetooth Low Energy support
28 * Two boards with a push button connected via a GPIO pin, see the :zephyr:code-sample:`button`
39 This sample uses two applications, so two devices need to be setup.
43 The two devices should automatically connect if they are close enough.
|
| /Zephyr-Core-3.5.0/boards/shields/x_nucleo_53l0a1/doc/ |
| D | index.rst | 18 Two VL53L0X satellites can be connected using the two 10 pin connectors.
45 The 7 segment display is connected to two GPIO expanders, each of one handles
48 * **Rightmost two digits**: ``EXPANDER1``, 0x42
49 * **Leftmost two digits**: ``EXPANDER2``, 0x43
|
| /Zephyr-Core-3.5.0/samples/userspace/shared_mem/ |
| D | README.rst | 35 followed by two series of repeating messages. The repeating messages
38 output is the first message without spaces. The two messages are
43 Two definitions can be inserted to change the wheel settings and print
45 two lines in CMakeLists.txt.
|
| /Zephyr-Core-3.5.0/drivers/sensor/lsm6dso16is/ |
| D | Kconfig | 70 a maximum of two external sensors (if more than two are enabled
71 the system would enumerate only the first two found)
|
| /Zephyr-Core-3.5.0/drivers/sensor/lsm6dsv16x/ |
| D | Kconfig | 70 a maximum of two external sensors (if more than two are enabled
71 the system would enumerate only the first two found)
|
| /Zephyr-Core-3.5.0/samples/net/vlan/ |
| D | README.rst | 5 Setup two virtual LAN networks and use net-shell to view the networks' settings.
10 The VLAN sample application for Zephyr will setup two virtual LAN networks.
44 The default configuration file prj.conf creates two virtual LAN networks
54 can be executed on the Linux host. It creates two VLAN interfaces *vlan.100*
|
| /Zephyr-Core-3.5.0/samples/bluetooth/mtu_update/ |
| D | README.rst | 29 This sample demonstrates the exchange of MTU between two devices to allow a
36 will exchange their MTUs and choose the minimum of the two. Thus the two MTU can
65 This sample use two applications, two devices need to be setup.
69 The two devices will connect only if they are close to each other, because of
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/ |
| D | qemu_802154_setup.rst | 10 This page describes how to set up a virtual network between two QEMUs that
17 For the steps below, you will need two terminal windows:
47 If you want to capture the network traffic between the two QEMUs, type:
76 You should see data passed between the two QEMUs.
|
| /Zephyr-Core-3.5.0/drivers/pwm/ |
| D | Kconfig.nrf_sw | 17 GPIOTE channel and two PPI/DPPI channels and per pin.
20 channel and two or three (when the fork feature is not available)
|
| /Zephyr-Core-3.5.0/tests/ztest/ztress/src/ |
| D | main.c | 38 /* Set of two threads */ in ZTEST()
45 /* Set of two threads and timer. Test is setup manually, without helper macro. */ in ZTEST()
86 /* Set of two threads */ in ZTEST()
96 /* Set of two threads and timer */ in ZTEST()
112 /* Set of two threads. First thread has no ending condition (exec_cnt and in ZTEST()
122 /* Set of two threads. Second thread and timer context has no ending in ZTEST()
|
| /Zephyr-Core-3.5.0/arch/xtensa/core/ |
| D | README-WINDOWS.rst | 29 themselves. Instead they place the rotation amount in two places
30 (yes, two; see below): the 2-bit CALLINC field of the PS register, and
31 the top two bits of the return address placed in A0.
39 top two bits from the return address in A0 and subtracts that value
41 in two places. They have to be stored on the stack across potentially
73 Finally: note that hardware checks the two bits of WINDOWSTART after
|
| /Zephyr-Core-3.5.0/tests/subsys/fs/fs_api/src/ |
| D | test_fs.h | 22 /* kenel only reserve two slots for specific file system.
23 * By disable that two file systems, test cases can make
|
| /Zephyr-Core-3.5.0/samples/subsys/canbus/isotp/ |
| D | README.rst | 5 Use ISO-TP library to exchange messages between two boards.
11 Messages are exchanged between two boards. A long message, that is sent with
33 * Two boards with CAN bus support, connected together
|
| /Zephyr-Core-3.5.0/boards/arm/mikroe_clicker_2/doc/ |
| D | mikroe_clicker_2.rst | 9 microcontroller. It is equipped with two mikrobus sockets and furthermore has
10 two headers for general signal break out.
26 - Two MikroBUS connectors
27 - Two headers with general connections
29 Furthermore the board contains two LEDs and two push buttons that are connected
64 The two mikroBUS interfaces are aliased in the device tree so that their
|
| /Zephyr-Core-3.5.0/samples/net/eth_native_posix/ |
| D | README.rst | 70 If you want to connect two Zephyr instances together, you can do it like this:
72 Create two Zephyr config files prj1.conf and prj2.conf. You can use
103 Then compile and run two Zephyr instances
119 Bridge the two Zephyr instances together:
142 Note that in this setup you cannot access these two Zephyr devices from
|
12345678910>>...52
