Searched +full:steps +full:- +full:per +full:- +full:period (Results 1 – 21 of 21) sorted by relevance
/Zephyr-latest/dts/bindings/input/ |
D | gpio-qdec.yaml | 2 # SPDX-License-Identifier: Apache-2.0 15 #include <zephyr/dt-bindings/input/input-event-codes.h> 18 compatible = "gpio-qdec"; 21 steps-per-period = <4>; 23 sample-time-us = <2000>; 24 idle-timeout-ms = <200>; 27 compatible: "gpio-qdec" 33 type: phandle-array 38 led-gpios: 39 type: phandle-array [all …]
|
/Zephyr-latest/tests/drivers/pwm/pwm_api/src/ |
D | test_pwm.c | 4 * SPDX-License-Identifier: Apache-2.0 13 * - Test Steps 14 * -# Bind PWM_0 port 0. 15 * -# Set PWM period and pulse using pwm_set_cycles() or pwm_set(). 16 * -# Use multimeter or other instruments to measure the output 18 * - Expected Results 19 * -# The output of PWM_OUT_0 will differ according to the value 20 * of period and pulse. 21 * Always on -> Period : Pulse (1 : 1) -> 3.3V 22 * Half on -> Period : Pulse (2 : 1) -> 1.65V [all …]
|
/Zephyr-latest/samples/subsys/display/lvgl/boards/ |
D | native_posix.overlay | 4 * SPDX-License-Identifier: Apache-2.0 7 #include <zephyr/dt-bindings/input/input-event-codes.h> 8 #include <zephyr/dt-bindings/lvgl/lvgl.h> 16 compatible = "gpio-qdec"; 18 steps-per-period = <4>; 20 sample-time-us = <2000>; 21 idle-timeout-ms = <200>; 25 compatible = "gpio-keys"; 59 compatible = "zephyr,lvgl-button-input"; 61 input-codes = <INPUT_KEY_B>; [all …]
|
/Zephyr-latest/tests/drivers/build_all/input/ |
D | app.overlay | 4 * SPDX-License-Identifier: Apache-2.0 7 #include <zephyr/dt-bindings/input/input-event-codes.h> 11 #address-cells = <1>; 12 #size-cells = <1>; 17 #io-channel-cells = <1>; 18 #address-cells = <1>; 19 #size-cells = <0>; 26 zephyr,acquisition-time = <ADC_ACQ_TIME_DEFAULT>; 32 gpio-controller; 34 #gpio-cells = <0x2>; [all …]
|
/Zephyr-latest/drivers/wifi/nrf_wifi/ |
D | Kconfig.nrfwifi | 1 # Nordic Wi-Fi driver for nRF70 series SoCs 5 # SPDX-License-Identifier: Apache-2.0 21 Nordic Wi-Fi Driver 124 bool "Wi-Fi interface auto start on boot" 145 bool "Low power mode in nRF Wi-Fi chipsets" 169 module-dep = LOG 170 module-str = Log level for Wi-Fi nRF70 driver 171 module-help = Sets log level for Wi-Fi nRF70 driver 193 # Wi-Fi and SR Coexistence Hardware configuration. 195 bool "Wi-Fi and SR coexistence support" [all …]
|
/Zephyr-latest/include/zephyr/bluetooth/ |
D | cs.h | 8 * SPDX-License-Identifier: Apache-2.0 112 /** Applicable for mode-2 and mode-3 only: 115 * - @ref BT_LE_CS_TEST_OVERRIDE_3_NO_TONE_EXT 116 * - @ref BT_LE_CS_TEST_OVERRIDE_3_INITIATOR_TONE_EXT_ONLY 117 * - @ref BT_LE_CS_TEST_OVERRIDE_3_REFLECTOR_TONE_EXT_ONLY 118 * - @ref BT_LE_CS_TEST_OVERRIDE_3_INITIATOR_AND_REFLECTOR_TONE_EXT 132 * +--------------------------------+------------------------------------------+ 134 * +--------------------------------+------------------------------------------+ 137 * +--------------------------------+------------------------------------------+ 141 * +--------------------------------+------------------------------------------+ [all …]
|
D | conn.h | 6 * Copyright (c) 2015-2016 Intel Corporation 8 * SPDX-License-Identifier: Apache-2.0 73 * Connection Interval: 30-50 ms 208 * after a packet containing a Link Layer PDU with a non-zero Length 224 * a packet containing a Link Layer PDU with a non-zero Length 240 * a packet containing a Link Layer PDU with a non-zero Length 265 /** Supported AA-Only RTT precision. */ 267 /** AA-Only RTT variant is not supported. */ 269 /** 10ns time-of-flight accuracy. */ 271 /** 150ns time-of-flight accuracy. */ [all …]
|
D | hci_types.h | 1 /* hci.h - Bluetooth Host Control Interface types */ 4 * Copyright (c) 2015-2016 Intel Corporation 7 * SPDX-License-Identifier: Apache-2.0 52 /* Bluetooth spec v5.4 Vol 4, Part E - 5.4.3 HCI Synchronous Data Packets */ 59 /* Bluetooth spec v5.4 Vol 4, Part E - 5.4.4 HCI Event Packet */ 82 /* Bluetooth spec v5.4 Vol 4, Part E - 5.4.2 ACL Data Packets */ 124 /* Bluetooth spec v5.4 Vol 4, Part E - 5.4.5 HCI ISO Data Packets */ 131 /* Bluetooth spec v5.4 Vol 4, Part E - 5.4.1 HCI Command Packet */ 608 /* Minor Device Class field - Computer Major Class */ 618 /* Minor Device Class field - Phone Major Class */ [all …]
|
/Zephyr-latest/doc/project/ |
D | release_process.rst | 6 The Zephyr project releases on a time-based cycle, rather than a feature-driven 10 A time-based release process enables the Zephyr project to provide users with a 12 roughly 4-month release cycle allows the project to coordinate development of 19 - Release tagging procedure: 21 - linear mode on main branch, 22 - release branches for maintenance after release tagging. 23 - Each release period will consist of a development phase followed by a 29 - Development phase: all changes are considered and merged, subject to 31 - Stabilisation phase: the release manager creates a vN-rc1 tag and the tree 33 - CI sees the tag, builds and runs tests; Test teams analyse the report from the [all …]
|
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/lll/ |
D | lll_df.c | 4 * SPDX-License-Identifier: Apache-2.0 42 * They are aimed for: reference period and switch-sample period. 91 if (pdu->adv_ext_ind.ext_hdr_len) { in lll_df_cte_tx_enable() 94 ext_hdr = &pdu->adv_ext_ind.ext_hdr; in lll_df_cte_tx_enable() 102 if (ext_hdr->cte_info) { in lll_df_cte_tx_enable() 108 lll_df_cte_tx_configure(df_cfg->cte_type, df_cfg->cte_length, in lll_df_cte_tx_enable() 109 df_cfg->ant_sw_len, df_cfg->ant_ids); in lll_df_cte_tx_enable() 111 lll_sync->cte_started = 1U; in lll_df_cte_tx_enable() 112 *cte_len_us = CTE_LEN_US(df_cfg->cte_length); in lll_df_cte_tx_enable() 114 if (lll_sync->cte_started) { in lll_df_cte_tx_enable() [all …]
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | shell.rst | 30 sub-commands. Every time the device boots up, make sure to call ``mesh init`` before any of the 43 The simplest way to provision the device is through self-provisioning. To do this the user must 49 devices, as long as they're assigned non-overlapping unicast addresses. Alternatively, to provision 51 ``mesh prov pb-adv on`` or ``mesh prov pb-gatt on``. The beacons can be picked up by an external 68 ``mesh prov local`` command above), we can perform self-configuration through any of the 73 uart:~$ mesh models cfg get-comp 89 uart:~$ mesh test net-send 82020100 120 .. list-table:: Parameter formats 122 :header-rows: 1 124 * - Type [all …]
|
/Zephyr-latest/include/zephyr/bluetooth/mesh/ |
D | access.h | 8 * SPDX-License-Identifier: Apache-2.0 52 #define BT_MESH_ADDR_ALL_NODES 0xffff /**< all-nodes */ 53 #define BT_MESH_ADDR_RELAYS 0xfffe /**< all-relays */ 54 #define BT_MESH_ADDR_FRIENDS 0xfffd /**< all-friends */ 55 #define BT_MESH_ADDR_PROXIES 0xfffc /**< all-proxies */ 56 #define BT_MESH_ADDR_DFW_NODES 0xfffb /**< all-directed-forwarding-nodes */ 57 #define BT_MESH_ADDR_IP_NODES 0xfffa /**< all-ipt-nodes */ 58 #define BT_MESH_ADDR_IP_BR_ROUTERS 0xfff9 /**< all-ipt-border-routers */ 393 /** Macro for encoding exact message length for fixed-length messages. */ 394 #define BT_MESH_LEN_EXACT(len) (-len) [all …]
|
/Zephyr-latest/doc/kernel/services/timing/ |
D | clocks.rst | 46 ---------- 66 word, these conversions expand to a 2-4 operation sequence, requiring 96 their duration and period. 127 being 32 bits. Large uptime counts in non-tick units will experience 129 timing-sensitive applications with long uptimes will be configured to 142 ------------- 146 a double-linked list, with an attendant delta count in ticks from the 150 expected to be embedded within subsystem-defined data structures (for 155 multiple-conversion steps internal to the kernel, so precision is 166 ------------- [all …]
|
/Zephyr-latest/subsys/bluetooth/mesh/shell/ |
D | cfg.c | 4 * SPDX-License-Identifier: Apache-2.0 281 while (p2_elem.elem_buf->len) { in cmd_get_comp() 286 if (p2_elem.data_buf->len) { in cmd_get_comp() 288 p2_elem.data_buf->len); in cmd_get_comp() 456 return -EINVAL; in cmd_net_transmit() 555 (void)memset(key_val + len, 0, sizeof(key_val) - len); in cmd_net_key_add() 625 (void)memset(key_val + len, 0, sizeof(key_val) - len); in cmd_net_key_update() 717 (void)memset(key_val + len, 0, sizeof(key_val) - len); in cmd_app_key_add() 790 (void)memset(key_val + len, 0, sizeof(key_val) - len); in cmd_app_key_upd() 1170 (void)memset(label + len, 0, sizeof(label) - len); in cmd_mod_sub_add_va() [all …]
|
/Zephyr-latest/include/zephyr/ |
D | kernel.h | 4 * SPDX-License-Identifier: Apache-2.0 53 #define K_PRIO_COOP(x) (-(CONFIG_NUM_COOP_PRIORITIES - (x))) 56 #define K_HIGHEST_THREAD_PRIO (-CONFIG_NUM_COOP_PRIORITIES) 60 #define K_LOWEST_APPLICATION_THREAD_PRIO (K_LOWEST_THREAD_PRIO - 1) 245 * bits, arch-specific use high bits. 259 * registers. This instructs the kernel to take additional steps to save 289 * from within a user-provided callback they have been invoked. 290 * Effectively it serves as a tiny bit of zero-overhead TLS data. 299 * This instructs the kernel to take additional steps to save and 322 * and SSE registers. This instructs the kernel to take additional steps to [all …]
|
/Zephyr-latest/drivers/led/ |
D | lp5562.c | 4 * SPDX-License-Identifier: Apache-2.0 13 * The LP5562 is a 4-channel LED driver that communicates over I2C. The four 23 * - Set the brightness. 24 * - Fade the brightness over time. 25 * - Loop parts of the program or the whole program. 26 * - Add delays. 27 * - Synchronize between the engines. 69 * The wait command has six bits for the number of steps (max 63) with up to 70 * 15.6ms per step if the prescaler is set to 1. We round the step length 71 * however to 16ms for easier handling, so the maximum blinking period is [all …]
|
/Zephyr-latest/doc/kernel/services/threads/ |
D | index.rst | 69 value -- for example, to allow device hardware used by the thread 75 re-spawned before it can be used. 91 thread self-exits, or the target thread aborts (either due to a 96 re-used for any purpose, including spawning a new thread. Note that 125 A thread can be prevented from executing for an indefinite period of time 134 A thread can prevent itself from executing for a specified period of time 176 - There may need to be additional memory reserved for memory management 178 - If guard-based stack overflow detection is enabled, a small write-protected 181 - If userspace is enabled, a separate fixed-size privilege elevation stack must 183 - If userspace is enabled, the thread's stack buffer must be appropriately [all …]
|
/Zephyr-latest/include/zephyr/arch/ |
D | arch_interface.h | 4 * SPDX-License-Identifier: Apache-2.0 8 * @defgroup arch-interface Architecture Interface 13 * call architecture-specific API so will have the prototypes for the 14 * architecture-specific APIs here. Architecture APIs that aren't used in this 17 * The set of architecture-specific APIs used internally by public macros and 53 * @defgroup arch-timing Architecture timing APIs 54 * @ingroup arch-interface 82 * through the full 64 bit space, wrapping at 2^64-1. Hardware with 92 * @addtogroup arch-threads 126 * buffer, defined as the area usable for thread stack context and thread- [all …]
|
/Zephyr-latest/doc/releases/ |
D | release-notes-3.1.rst | 61 * Split CAN classic and CAN-FD APIs: 90 was moved from Kconfig to :ref:`devicetree <dt-guide>`. 91 See the :dtcompatible:`st,stm32f1-pinctrl` devicetree binding for more information. 182 * MIPI-DSI 184 * Added a :ref:`MIPI-DSI api <mipi_dsi_api>`. This is an experimental API, 196 * Added support for enabling/disabling CAN-FD mode at runtime using :c:macro:`CAN_MODE_FD`. 220 * Added support for Provisioners over PB-GATT 231 * Implemented ISO-AL TX unframed fragmentation 232 * Added support for back-to-back receiving of PDUs on nRF5x platforms 249 newly created informational-only callback struct :c:struct:`bt_conn_auth_info_cb`. [all …]
|
D | release-notes-3.3.rst | 14 * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery) 17 CMSIS-DSP as the default backend. 30 * CVE-2023-0359: Under embargo until 2023-04-20 32 * CVE-2023-0779: Under embargo until 2023-04-22 66 removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding. 71 * Starting from this release ``zephyr-`` prefixed tags won't be created 82 image states). Use of a truncated hash or non-sha256 hash will still work 88 registration function at boot-up. If applications register this then 93 application code, these will now automatically be registered at boot-up (this 129 This may cause out-of-tree scripts or commands to fail if they have relied [all …]
|
D | release-notes-2.7.rst | 17 * Support for M-Profile Vector Extensions (MVE) on ARMv8.1-M 18 * Improved thread safety for Newlib and C++ on SMP-capable systems 20 * New Action-based Power Management API 23 * Linker Support for Tightly-Coupled Memory in RISC-V 25 * Support for extended PCI / PCIe capabilities, improved MIS-X support 33 * The kernel now supports both 32- and 64-bit architectures 36 * We added support for Point-to-Point Protocol (PPP) 37 * We added support for UpdateHub, an end-to-end solution for over-the-air device updates 38 * We added support for ARM Cortex-R Architecture 40 * Expanded support for ARMv6-M architecture [all …]
|