Searched full:each (Results 1 – 25 of 1566) sorted by relevance
12345678910>>...63
| /Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 8 Tests are organized into bash scripts under the test_scripts folder. Each
10 mesh subsystem, and each folder has a corresponding test_<subfolder>.c under the
32 ``RunTest`` to skip starting processes for each application in the ``$SKIPPED``
68 harnesses. ``mesh_test.sh`` is sourced in each test script, and its ``RunTest``
69 function is called once in each script with the following parameters:
75 ``RunTest`` starts one mesh application for each selected harness, before
85 The mesh_test module is never called from the framework, so each test harness
87 All utility functions can be replaced by custom behavior in each harness if the
93 Each test needs a separate test script and one or more test harnesses that
97 directory, and each test case needs a separate test script with a single test
[all …]
|
| /Zephyr-Core-3.5.0/dts/bindings/pwm/ |
| D | infineon,xmc4xxx-ccu8-pwm.yaml | 9 to each other.
19 pwm_ccu81. Each module has four slices, and each slice has
23 The CCU8 modules use the CCU clock source. Each slice applies
25 defined by the 'slice-prescaler' property. Additionally, each
67 channels 2/3 are in slice 1, and so on. Each channel can have its own
94 Defines the clock divider for each slice.
103 Defines the clock divider for dead time counter for each slice.
112 Defines the dead time in nanoseconds for the high-side PWM signal for each channel.
118 Defines the dead time in nanoseconds for the low-side PWM signal for each channel.
|
| D | infineon,xmc4xxx-ccu4-pwm.yaml | 9 Each module has four slices and each slice has one channel.
14 The CCU4 modules uses the CCU clock source. Each slice applies a separate
73 Defines the clock divider for each channel.
|
| /Zephyr-Core-3.5.0/drivers/wifi/esp32/ |
| D | Kconfig.esp32 | 59 Set the number of WiFi static RX buffers. Each buffer takes approximately
75 will be allocated (provided sufficient free RAM). The size of each dynamic
78 For each received data frame, the WiFi driver makes a copy to an RX buffer
94 initialized and released when WiFi is de-initialized. The size of each
97 If "Dynamic" is selected, each WiFi TX buffer is allocated as needed
100 The size of each dynamic TX buffer depends on the length of each data
124 Set the number of WiFi static TX buffers. Each buffer takes approximately
128 For each transmitted data frame from the higher layer TCP/IP stack,
141 For each TX packet from uplayer, such as LWIP etc, WiFi driver needs to
153 Set the number of WiFi dynamic TX buffers. The size of each
[all …]
|
| /Zephyr-Core-3.5.0/drivers/watchdog/ |
| D | Kconfig.nxp_fs26 | 26 Sets the maximum value of the watchdog error counter. Each time a
28 watchdog error counter is decremented by 1 each time the watchdog is
37 Sets the maximum value of the watchdog refresh counter. Each time the
38 watchdog is properly refreshed, this counter is incremented by 1. Each
40 also good, the fault error counter is decremented by 1. Each time
|
| /Zephyr-Core-3.5.0/dts/bindings/test/ |
| D | vnd,pinctrl-test.yaml | 13 Test pin controller pin configuration nodes. Each node is composed by one or
14 more groups, each defining the configuration for a set of pins.
18 Test pin controller pin configuration group. Each group contains a list of
56 An array of pins sharing the same group properties. Each entry is a
|
| /Zephyr-Core-3.5.0/dts/bindings/memory-controllers/ |
| D | atmel,sam-smc.yaml | 36 each MCK cycle will be equivalent to 8ns. Since the memory full cycle is
123 where each value is configured in terms of MCK cycles. The SMC
125 consecutive reads/writes are used. Each value is encoded in
127 The effective value for each element is: 128 x setup[5] + setup[4:0]
135 each value is configured in terms of MCK cycles and a value of 0 is forbidden.
136 Each value is encoded in 7 bits where the highest bit adds an offset of 256
137 cycles. The effective value for each element is: 256 x setup[6] + setup[5:0]
150 Effective value for each element: 256 x cycle[8:7] + cycle[6:0]
|
| /Zephyr-Core-3.5.0/samples/drivers/led_lp50xx/ |
| D | README.rst | 12 First, for each LED information is retrieved using the led_get_info syscall
15 :c:func:`led_write_channels` syscall) and then to each LED one by one (using the
21 For all the LEDs first (using channel API) and then for each LED one by one:
23 For each color in red green blue white yellow purple cyan orange:
|
| /Zephyr-Core-3.5.0/cmake/modules/ |
| D | zephyr_module.cmake | 83 # Match <key>:<value> for each line of file, each corresponding to
101 # Match "<name>":"<path>" for each line of file, each corresponding to
114 # Match "<name>":"<path>" for each line of file, each corresponding to
134 # Match "<name>":"<path>" for each line of file, each corresponding to
154 # Match "<name>":"<path>" for each line of file, each corresponding to
|
| /Zephyr-Core-3.5.0/samples/drivers/led_pwm/ |
| D | README.rst | 11 device instance found in DT is used. For each LEDs attached to this device
18 For each PWM LEDs (one after the other):
32 device node must match "pwm-leds". And for each LED, a child node must be
|
| /Zephyr-Core-3.5.0/drivers/led/ |
| D | Kconfig.lp3943 | 12 LP3943 LED driver has 16 channels each with multi-programmable
13 states at a specified rate. Each channel can drive up to 25 mA
|
| D | Kconfig.pca9633 | 12 PCA9633 LED driver has 4 channels each with multi-programmable
13 states. Each channel can drive up to 25 mA per LED.
|
| /Zephyr-Core-3.5.0/tests/bsim/ |
| D | README.md | 51 Each test is defined by a shell script with the extension `.sh`.
54 Each of these test scripts expects the binaries their require already built, and will execute
61 It is recommended to have a single test for each test script.
63 Each test must have a unique simulation id, to enable running different tests in parallel.
78 they should strive for using separate simulation ids for each simulation part,
79 in that way ensuring that the simulation radio activity of each segment can be inspected a
|
| /Zephyr-Core-3.5.0/drivers/pwm/ |
| D | Kconfig.it8xxx2 | 12 Supports three 16-bit prescalers each with 8-bit cycle timer, and
13 eight PWM channels each with 8-bit duty cycle.
|
| /Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/tests_scripts/friendship/ |
| D | msg_va_collision.sh | 13 # 2.1. Friend sends a message to each virtual address, LPN receives both messages.
17 # 3.2. Friend sends a message to each virtual address. LPN receives both, but successfully decrypts
22 # 4.2. Friend sends a message to each virtual address, but non of them are received by LPN.
|
| /Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/common/include/ |
| D | cavs-idc.h | 16 * Each core has a set of registers its is supposed to use, but all
20 * Each core has a "ITC" register associated with each other core in
26 * On the target core, there is a "TFC" register for each core that
57 * Finally note the two control registers at the end of each core's
86 /* cAVS interrupt mask bits. Each core has one of these structs
87 * indexed in the intctrl[] array. Each external interrupt source
88 * indexes one bit in one of the state substructs (one each for Xtensa
102 * INTENABLE/INTERRUPT/INTSET/INTCLEAR special registers on each core
|
| /Zephyr-Core-3.5.0/dts/bindings/sensor/ |
| D | maxim,max31875.yaml | 37 The number of bits used for each temperature sample.
39 Each 1-bit increase doubles the conversion time.
40 Similarly, each 1-bit decrease halves the conversion time.
|
| /Zephyr-Core-3.5.0/tests/drivers/regulator/voltage/dts/bindings/ |
| D | test-regulator-voltage.yaml | 15 Regulators to be tested. Each entry must have a matching ADC entry in
22 ADC channels to be used. Each entry must have a matching entry in
31 require more, though. Each entry must have a matching entry in
|
| /Zephyr-Core-3.5.0/tests/drivers/disk/disk_access/ |
| D | README.txt | 15 starts by reading sectors from a variety of start locations. Each location is
16 read from several times, each time with a different number of desired sectors.
23 follows the same flow as the read test, but at each step writes data to the
|
| /Zephyr-Core-3.5.0/samples/drivers/led_is31fl3216a/ |
| D | README.rst | 12 Each LED is gradually pulsed until it reach 100% of luminosity and gradually
15 Once each LED was pulsed, multiple LEDs are pulse simultaneously using the
21 For each LED:
|
| /Zephyr-Core-3.5.0/drivers/wifi/winc1500/ |
| D | Kconfig.winc1500 | 46 Set the number of buffer the driver will have access to in each of
54 This sets the size of each buffer, in each buffer pools.
|
| /Zephyr-Core-3.5.0/dts/bindings/mtd/ |
| D | fixed-partitions.yaml | 52 the start address of flash0 in memory to each partition's
63 represent the start offset of each partition.
70 represent the size of each partition in bytes.
74 Each child node of the fixed-partitions node represents
|
| /Zephyr-Core-3.5.0/drivers/led_strip/ |
| D | Kconfig.lpd880x | 11 Each LPD880x LED driver chip has some output channels
15 Each chip also includes data and clock out pins for
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/api/ |
| D | traffic-class.rst | 18 the number of receive queues. Each traffic class queue corresponds to a
19 specific kernel work queue. Each kernel work queue has a priority.
22 and chapter 34.5 table 34-1. Each traffic class is in turn mapped to a certain
|
| /Zephyr-Core-3.5.0/scripts/build/ |
| D | gen_image_info.py | 17 - LMA address of each segment
18 - VMA address of each segment
19 - LMA adjusted of each segment if the LMA addresses has been adjusted after linking
20 - Size of each segment
|
12345678910>>...63
