| /Zephyr-latest/dts/bindings/stepper/ |
| D | stepper-controller.yaml | 7 invert-direction:
10 Invert motor direction.
41 The GPIO pins used to send direction signals to the stepper motor.
42 Pin will be driven high for forward direction and low for reverse direction.
|
| /Zephyr-latest/dts/bindings/adc/ |
| D | maxim,max1125x-base.yaml | 14 gpio0-direction:
16 description: this option for gpio0 direction enable for input, disable for output
17 gpio1-direction:
19 description: this option for gpio0 direction enable for input, disable for output
|
| /Zephyr-latest/samples/bluetooth/direction_finding_connectionless_tx/ |
| D | README.rst | 2 :name: Direction Finding Periodic Advertising Beacon
5 Implement Bluetooth LE Direction Finding CTE Broadcaster functionality.
10 A simple application demonstrating the Bluetooth LE Direction Finding CTE Broadcaster
16 * Nordic nRF SoC based board with Direction Finding support (example boards:
20 Check your SoC's product specification for Direction Finding support if you are
42 sample application may be used. To build this sample with direction finding
49 * Make sure the same GPIO pins are assigned to Direction Finding Extension in file
83 In addition to the devicetree configuration, to successfully use the Direction
|
| /Zephyr-latest/tests/bluetooth/mesh/brg/src/ |
| D | main.c | 19 uint8_t direction; member
34 test_vector[i].direction = i < (TEST_VECT_SZ / 2) ? 1 : 2; in setup()
83 err = bt_mesh_brg_cfg_tbl_add(test_vector[i].direction, test_vector[i].net_idx1, in check_fill_all_bt_entries()
258 err = bt_mesh_brg_cfg_tbl_add(test_vector[i].direction, test_vector[i % 2].net_idx1, in ZTEST()
273 err = bt_mesh_brg_cfg_tbl_add(test_vector[i].direction, in ZTEST()
278 err = bt_mesh_brg_cfg_tbl_add(test_vector[i].direction, in ZTEST()
295 err = bt_mesh_brg_cfg_tbl_add(test_vector[i].direction, in ZTEST()
300 err = bt_mesh_brg_cfg_tbl_add(test_vector[i].direction, in ZTEST()
316 err = bt_mesh_brg_cfg_tbl_add(test_vector[i].direction, test_vector[1].net_idx1, in ZTEST()
376 .direction = BT_MESH_BRG_CFG_DIR_ONEWAY, in ZTEST()
[all …]
|
| /Zephyr-latest/drivers/stepper/step_dir/ |
| D | step_dir_stepper_common.h | 25 * @brief Common step direction stepper config.
38 * @brief Initialize common step direction stepper config from devicetree instance.
56 * @brief Initialize common step direction stepper config from devicetree instance.
63 * @brief Common step direction stepper data.
70 enum stepper_direction direction; member
94 * @brief Initialize common step direction stepper data from devicetree instance.
104 * @brief Initialize common step direction stepper data from devicetree instance.
123 * @brief Common function to initialize a step direction stepper device at init time.
127 * @param dev Step direction stepper device instance.
189 * @brief Run the stepper with a given velocity in a given direction.
[all …]
|
| /Zephyr-latest/samples/bluetooth/direction_finding_central/ |
| D | README.rst | 2 :name: Direction Finding Central
5 Connect to a Bluetooth LE Direction Finding peripheral and request Constant Tone Extension.
10 A simple application demonstrating the Bluetooth LE Direction Finding CTE reception in
17 * Nordic nRF SoC based board with Direction Finding support (example boards:
21 Check your SoC's product specification for Direction Finding support if you are
42 application may be used. To build this sample with direction finding support
49 * Make sure the same GPIO pins are assigned to Direction Finding Extension in file
|
| D | prj.conf | 9 CONFIG_BT_DEVICE_NAME="Direction Finding Central"
15 # Enable Direction Finding Feature RX in connected mode
|
| D | sample.yaml | 2 name: Direction Finding Central
3 description: Sample application showing central role of Direction Finding in connected
|
| /Zephyr-latest/samples/bluetooth/direction_finding_peripheral/ |
| D | README.rst | 2 :name: Direction Finding Peripheral
5 Implement Bluetooth LE Direction Finding peripheral transmitting CTE in connected mode.
10 A simple application demonstrating the Bluetooth LE Direction Finding CTE transmission in
16 * Nordic nRF SoC based board with Direction Finding support (example boards:
20 Check your SoC's product specification for Direction Finding support if you are
41 application may be used. To build this sample with direction finding support
48 * Make sure the same GPIO pins are assigned to Direction Finding Extension in file
|
| D | sample.yaml | 2 name: Direction Finding Peripheral
3 description: Sample application showing peripheral role of Direction Finding in
|
| /Zephyr-latest/samples/bluetooth/direction_finding_connectionless_rx/ |
| D | README.rst | 2 :name: Direction Finding Periodic Advertising Locator
5 Implement Bluetooth LE Direction Finding CTE Locator functionality.
10 A simple application demonstrating the Bluetooth LE Direction Finding CTE Locator
17 * Nordic nRF SoC based board with Direction Finding support (example boards:
21 Check your SoC's product specification for Direction Finding support if you are
42 application may be used. To build this sample with direction finding support
49 * Make sure the same GPIO pins are assigned to Direction Finding Extension in file
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | brg_cfg.c | 40 if (brg_tbl[k].direction != 0) { in brg_tbl_compact()
178 /* Setting direction to 0, entry will be cleared in brg_tbl_compact. */ in brg_tbl_netkey_removed_evt()
179 brg_tbl[i].direction = 0; in brg_tbl_netkey_removed_evt()
236 int bt_mesh_brg_cfg_tbl_add(uint8_t direction, uint16_t net_idx1, uint16_t net_idx2, uint16_t addr1, in bt_mesh_brg_cfg_tbl_add() argument
245 if (direction != BT_MESH_BRG_CFG_DIR_ONEWAY && direction != BT_MESH_BRG_CFG_DIR_TWOWAY) { in bt_mesh_brg_cfg_tbl_add()
249 if ((direction == BT_MESH_BRG_CFG_DIR_ONEWAY && in bt_mesh_brg_cfg_tbl_add()
251 (direction == BT_MESH_BRG_CFG_DIR_TWOWAY && !BT_MESH_ADDR_IS_UNICAST(addr2))) { in bt_mesh_brg_cfg_tbl_add()
260 /* Check if entry already exists, if yes, then, update the direction field and it is a in bt_mesh_brg_cfg_tbl_add()
269 brg_tbl[i].direction = direction; in bt_mesh_brg_cfg_tbl_add()
281 brg_tbl[bt_mesh_brg_cfg_row_cnt].direction = direction; in bt_mesh_brg_cfg_tbl_add()
[all …]
|
| /Zephyr-latest/include/zephyr/bluetooth/audio/ |
| D | pacs.h | 64 * Iterate capabilities with endpoint direction specified.
66 * @param dir Direction of the endpoint to look capability for.
79 * @param dir Direction of the endpoint to register capability for.
91 * @param dir Direction of the endpoint to unregister capability for.
101 * @param dir Direction of the endpoints to change location for.
112 * @param dir Direction of the endpoints to change available contexts for.
123 * @param dir Direction of the endpoints to get contexts for.
139 * @param dir Direction of the endpoints to change available contexts for.
155 * @param dir Direction of the endpoints to get contexts for.
166 * @param dir Direction of the endpoints to change available contexts for.
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig.df | 36 bool "LE Direction Finding"
39 Enable support for Bluetooth 5.1 Direction Finding
44 # Bluetooth v5.1 Direction Finding
61 This sampling mode is optional for Direction Finding according to
70 mode is optional for Direction Finding according to Bluetooth v5.1.
72 # Features related with Direction Finding
136 direction finding connected mode.
143 Enable reception and sampling of Constant Tone Extension in direction
257 bool "Bluetooth Direction Finding debug support enable"
259 This option enables debug support for the Direction Finding
[all …]
|
| /Zephyr-latest/samples/bluetooth/direction_finding_connectionless_rx/boards/ |
| D | nrf52833dk_nrf52833.conf | 4 # Enable Direction Finding Feature including AoA and AoD
7 # Disable Direction Finding TX mode
|
| D | nrf52833dk_nrf52820.conf | 4 # Enable Direction Finding Feature including AoA and AoD
7 # Disable Direction Finding TX mode
|
| /Zephyr-latest/drivers/gpio/ |
| D | gpio_altera_pio.c | 26 uint8_t direction; member
43 const int direction = cfg->direction; in gpio_pin_direction() local
52 /* Check if the direction is Bidirectional */ in gpio_pin_direction()
53 if (direction != 0) { in gpio_pin_direction()
74 const int direction = cfg->direction; in gpio_altera_configure() local
84 /* Check if the direction is Bidirectional */ in gpio_altera_configure()
85 if (direction != 0) { in gpio_altera_configure()
307 .direction = DT_INST_ENUM_IDX(n, direction), \
|
| /Zephyr-latest/samples/bluetooth/hci_ipc/ |
| D | nrf5340_cpunet_df-bt_ll_sw_split.conf | 69 # Direction Finding
74 # Direction Finding Tx
80 # Direction Finding Rx
|
| /Zephyr-latest/dts/bindings/display/ |
| D | st,stm32-ltdc.yaml | 58 description: First pixel in x direction on layer 0. Defaults to 0.
62 description: Last pixel in x direction on layer 0. Defaults to width.
66 description: First pixel in y direction on layer 0. Defaults to 0.
70 description: Last pixel in y direction on layer 0. Defaults to height.
|
| /Zephyr-latest/include/zephyr/usb/ |
| D | usb_ch9.h | 31 uint8_t direction : 1; member
33 uint8_t direction : 1;
51 /** USB Setup packet RequestType Direction values (from Table 9-2) */
67 /** Get data transfer direction from bmRequestType */
75 * @brief Check if request transfer direction is to host.
78 * @return true If transfer direction is to host
82 return setup->RequestType.direction == USB_REQTYPE_DIR_TO_HOST; in usb_reqtype_is_to_host()
86 * @brief Check if request transfer direction is to device.
89 * @return true If transfer direction is to device
93 return setup->RequestType.direction == USB_REQTYPE_DIR_TO_DEVICE; in usb_reqtype_is_to_device()
[all …]
|
| /Zephyr-latest/drivers/dai/nxp/sai/ |
| D | sai.c | 134 LOG_ERR("invalid direction: %d", dir); in sai_get_properties()
149 * 3) What this piece of code does is it makes the SYNC direction
150 * use the ASYNC direction's BCLK that comes from its input pad.
178 * direction will have the BYP bit toggled.
271 * the direction (TX/RX) we're enabling. Enabling the in sai_config_set()
272 * data line for the opposite direction will lead to FIFO in sai_config_set()
273 * overrun/underrun when working with a SYNC direction. in sai_config_set()
277 * which one configures both direction but only starts in sai_config_set()
278 * the SYNC direction which would lead to a FIFO underrun. in sai_config_set()
463 * here as they do not disable the ASYNC direction. in sai_dir_disable()
[all …]
|
| /Zephyr-latest/drivers/dma/ |
| D | dma_intel_adsp_hda.c | 43 __ASSERT(dma_cfg->channel_direction == cfg->direction, in intel_adsp_hda_dma_host_in_config()
44 "Unexpected channel direction, HDA host in supports " in intel_adsp_hda_dma_host_in_config()
77 __ASSERT(dma_cfg->channel_direction == cfg->direction, in intel_adsp_hda_dma_host_out_config()
78 "Unexpected channel direction, HDA host out supports " in intel_adsp_hda_dma_host_out_config()
111 __ASSERT(dma_cfg->channel_direction == cfg->direction, in intel_adsp_hda_dma_link_in_config()
112 "Unexpected channel direction, HDA link in supports " in intel_adsp_hda_dma_link_in_config()
141 __ASSERT(dma_cfg->channel_direction == cfg->direction, in intel_adsp_hda_dma_link_out_config()
142 "Unexpected channel direction, HDA link out supports " in intel_adsp_hda_dma_link_out_config()
187 switch (cfg->direction) { in intel_adsp_hda_dma_host_reload()
231 stat->dir = cfg->direction; in intel_adsp_hda_dma_status()
[all …]
|
| /Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/hal/nrf5/radio/ |
| D | radio_df.h | 22 /* Provides number of available antennas for Direction Finding. */
25 /* Sets Direction Finding AOA mode. */
27 /* Sets Direction Finding AOD mode. */
52 /* Resets Direction Finding radio configuration */
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/bridge/ |
| D | brg_table_state_change.sh | 15 # 5. Tester adds an entry to the bridging table to bridge traffic in one direction from tester to
19 # 9. Tester adds a reverse entry to the bridging table to bridge traffic in the other direction from
23 # 11. Tester removes the reverse entry from the bridging table and updates direction of the first
|
| /Zephyr-latest/samples/bluetooth/hci_uart_3wire/ |
| D | overlay-all-bt_ll_sw_split.conf | 74 # Direction Finding
79 # Direction Finding Tx
85 # Direction Finding Rx
|
