Searched full:through (Results 1 – 25 of 1142) sorted by relevance
12345678910>>...46
/Zephyr-latest/dts/bindings/mtd/ |
D | nxp,imx-flexspi-device.yaml | 17 CSINTERVALUNIT field in registers FLASHA1CR0 through FLASHB2CR0. The 25 CSINTERVAL field in registers FLASHA1CR0 through FLASHB2CR0. The 33 registers FLASHA1CR0 through FLASHB2CR0. The default corresponds to the 41 registers FLASHA1CR0 through FLASHB2CR0. The default corresponds to the 48 Data valid time, in nanoseconds. See the registers DLLACR through 56 column address. See the CAS field in registers FLASHA1CR0 through 64 addressable. See the WA field in registers FLASHA1CR0 through 81 field in registers FLASHA1CR2 through FLASHB2CR2. The default 89 field in registers FLASHA1CR2 through FLASHB2CR2. The default
|
/Zephyr-latest/dts/bindings/gpio/ |
D | digilent,pmod.yaml | 8 through 3 correspond to IO1 through IO4, and parent pins 4 through 7 9 correspond to IO5 through IO8, as depicted below for a 12-pin connector. 22 through 7 are omitted from the GPIO nexus node, resulting in a mapping
|
D | arduino-header-r3.yaml | 15 labeled from A0 at the top through A5 at the bottom. 19 digital input signals labelled from D8 at the bottom through D13 24 through 5 correspond to A0 through A5, and parent pins 6 through 21 25 correspond to D0 through D15, as depicted below:
|
D | arduino-nano-header-r3.yaml | 12 signals labeled from A0 through A7, as well a digital signal D13. The 16 through 13 correspond to D0 through D13, and parent pins 14 through 21 17 correspond to A0 through A7, as depicted below.
|
D | seeed-xiao-header.yaml | 14 labeled from 0 at the top through 6 at the bottom. 17 top through 7 at the bottom. 20 through 10 correspond to D0 through D10, as depicted below:
|
D | arduino-mkr-header.yaml | 18 through 14 correspond to D0 through D21, and parent pins 15 through 21 19 correspond to A0 through A6, as depicted below.
|
D | adafruit-feather-header.yaml | 16 through 5 correspond to A0 through A5, and parent pins 6 through 20
|
D | particle-gen3-header.yaml | 17 0 through 8 correspond to the pins on the 12-pin header, starting 18 from the bottom; and pins 9 through 21 correspond to pins on the 19 16-pin header, skipping the bottom pin then assigning 9 through 19,
|
/Zephyr-latest/dts/bindings/ethernet/ |
D | microchip,lan865x.yaml | 12 tx-cut-through-mode: 14 description: Enable TX cut through mode 15 rx-cut-through-mode: 17 description: Enable RX cut through mode
|
/Zephyr-latest/tests/kernel/profiling/profiling_api/src/ |
D | main.c | 41 * @brief Test stack usage through main thread 44 * stack usage through main thread. 57 * @brief Test stack usage through idle thread 60 * stack usage through idle thread. 74 * @brief Test stack usage through system workqueue 77 * stack usage through system workqueue.
|
/Zephyr-latest/dts/bindings/adc/ |
D | arduino,uno-adc.yaml | 8 has analog input signals labeled from A0 at the top through A5 at 12 pins 0 through 5 correspond to A0 through A5.
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | heartbeat.rst | 9 The Heartbeat feature is configured through the :ref:`bluetooth_mesh_models_cfg_srv` model. 14 Heartbeat messages are sent as transport control packets through the network, 17 the active features on the node. Through this, a receiving node can determine 18 how many relays the message had to go through to arrive at the receiver, and 31 Heartbeat publication is controlled through the Configuration models, and can
|
D | health_srv.rst | 36 through some physical behavior like blinking, playing a sound or vibrating. 38 device they're provisioning, as well as through the Health models at runtime. 47 The remaining time for the attention period may be queried through
|
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/provision/ |
D | pb_remote_parallel.sh | 10 # 3. The provisioner provisions an unprovisioned device idx 2 through the node with RPR server; 11 # 4. The provisioner scans for an unprovisioned device idx 3 through the node with RPR server; 13 # 6. The provisioner provisions an unprovisioned device idx 3 through the node with RPR server;
|
D | pb_remote_reprovision.sh | 7 # Test a node re-provisioning through Remote Provisioning models. Procedure: 10 # 3. The provisioner starts scanning for an unprovisioned device through the node with RPR server;
|
D | pb_remote_nppi_robustness.sh | 8 # 1. Provisioner provisions the second device (prov_device_pb_remote_server) with RPR server through 11 # through RPR (5 second timeout) and provisions it
|
/Zephyr-latest/boards/shields/x_nucleo_iks4a1/doc/ |
D | index.rst | 49 development. It can be connected at the same time of external MEMS through 52 LSM6DSV16X through aux SPI (3/4 w) 61 selected through J4 and J5 jumpers. Additional information about X-NUCLEO-IKS4A1 85 through a direct control of the on-board environmental sensors (temperature, 86 pressure and magnetometer) and external sensor (DIL24) through the auxiliary 101 Measurement Unit) functionalities by collecting external data through 103 pressure and magnetometer) and external sensor (DIL24) through the auxiliary 116 board through DIL24 adapter, it is possible to exploit this functionality 118 to connect the DIL24 to the external board through SPI lines in order to 131 (by plugging it on JP6 and JP7 connectors) through the LSM6DSO16IS.
|
/Zephyr-latest/tests/cmake/hwm/board_extend/oot_root/boards/native/native_sim_extend/ |
D | Kconfig | 15 This kconfig is promptless and is expected to be set through the 22 This kconfig is promptless and is expected to be set through the
|
/Zephyr-latest/cmake/toolchain/xt-clang/ |
D | generic.cmake | 11 # However, CMake doesn't recognize it when invoking through xt-clang. 12 # This results in CMake going through all possible combinations of
|
/Zephyr-latest/doc/kernel/usermode/ |
D | overview.rst | 90 - We prevent re-entry from user to supervisor mode except through the 118 - We do not protect against denial of service attacks through thread CPU 133 through the following mechanisms: 138 must be done on the thread's behalf through system calls, or specifically 146 manipulation of kernel objects is done through system call interfaces. Device 161 user mode through system calls involves an extra layer of handler functions, 163 the object, check the validity of other parameters through bounds checking or 176 kernel objects will need to go through pre-defined pools of available objects.
|
/Zephyr-latest/drivers/interrupt_controller/ |
D | Kconfig.intel_vtd | 13 Such interrupt remapping hardware is provided through Intel VT-D 21 bool "XAPIC mode pass-through"
|
/Zephyr-latest/cmake/toolchain/xcc/ |
D | generic.cmake | 16 # However, CMake doesn't recognize it when invoking through xt-xcc. 17 # This results in CMake going through all possible combinations of
|
/Zephyr-latest/drivers/serial/ |
D | Kconfig.xen | 28 manages all domain outputs through the consoleio interface. 39 bool "Early printk/stdout through console_io Xen interface"
|
/Zephyr-latest/samples/userspace/syscall_perf/ |
D | README.rst | 10 user thread has to go through a system call compared to a supervisor thread that 19 current thread. The user thread has to go through a system call.
|
/Zephyr-latest/dts/bindings/sensor/ |
D | nordic,nrf-qdec.yaml | 28 For pins P0.0 through P0.31, use the pin number. For example, 33 For pins P1.0 through P1.31, add 32 to the pin number. For
|
12345678910>>...46