/Zephyr-Core-3.5.0/include/zephyr/drivers/ |
D | ptp_clock.h | 28 int (*adjust)(const struct device *dev, int increment); 76 static inline int ptp_clock_adjust(const struct device *dev, int increment) in ptp_clock_adjust() argument 81 return api->adjust(dev, increment); in ptp_clock_adjust()
|
/Zephyr-Core-3.5.0/drivers/dma/ |
D | dma_stm32.c | 214 static int dma_stm32_get_memory_increment(enum dma_addr_adj increment, in dma_stm32_get_memory_increment() argument 217 switch (increment) { in dma_stm32_get_memory_increment() 227 LOG_ERR("Memory increment error. %d", increment); in dma_stm32_get_memory_increment() 234 static int dma_stm32_get_periph_increment(enum dma_addr_adj increment, in dma_stm32_get_periph_increment() argument 237 switch (increment) { in dma_stm32_get_periph_increment() 247 LOG_ERR("Periph increment error. %d", increment); in dma_stm32_get_periph_increment()
|
D | dma_stm32_bdma.c | 404 static int bdma_stm32_get_memory_increment(enum dma_addr_adj increment, in bdma_stm32_get_memory_increment() argument 407 switch (increment) { in bdma_stm32_get_memory_increment() 417 LOG_ERR("Memory increment error. %d", increment); in bdma_stm32_get_memory_increment() 424 static int bdma_stm32_get_periph_increment(enum dma_addr_adj increment, in bdma_stm32_get_periph_increment() argument 427 switch (increment) { in bdma_stm32_get_periph_increment() 437 LOG_ERR("Periph increment error. %d", increment); in bdma_stm32_get_periph_increment()
|
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/ |
D | sar_cfg.rst | 94 * Acknowledgment delay increment (see the `SAR Acknowledgment Delay Increment`_ state). 103 …unicast~retransmissions~interval~step + unicast~retransmissions~interval~increment \times (TTL - 1) 123 min(SegN + 0.5 , acknowledgment~delay~increment) \times segment~reception~interval 219 SAR Unicast Retransmissions Interval Increment holds a value that controls the interval increment 221 address. The increment is measured in milliseconds. 224 default value. The Kconfig option value is used to calculate the increment using the following 270 This state holds a value that controls the delay increment of an interval used for delaying the 271 transmission of an acknowledgment message after receiving a new segment. The increment is measured 275 value. The increment value is calculated to be
|
/Zephyr-Core-3.5.0/samples/boards/up_squared/gpio_counter/ |
D | README.rst | 11 The sample enables a pin as GPIO input (active high) that triggers the increment 75 the board will start to execute the sample. Apply input to trigger the increment
|
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/host/l2cap/split/tester/src/ |
D | main.c | 548 int increment = -1; in send_l2cap_sdu() local 576 increment = 1; in send_l2cap_sdu() 578 increment = -1; in send_l2cap_sdu() 580 mps += increment; in send_l2cap_sdu()
|
/Zephyr-Core-3.5.0/samples/sensor/qdec/ |
D | README.rst | 69 The reported increment/decrement can be larger/smaller than the one shown
|
/Zephyr-Core-3.5.0/doc/kernel/services/other/ |
D | atomic.rst | 50 in mid-increment if a thread calling the function is interrupted if 59 /* increment invocation counter */
|
/Zephyr-Core-3.5.0/drivers/ethernet/ |
D | eth_stm32_hal.c | 1774 static int ptp_clock_stm32_adjust(const struct device *dev, int increment) in ptp_clock_stm32_adjust() argument 1781 if ((increment <= (int32_t)(-NSEC_PER_SEC)) || in ptp_clock_stm32_adjust() 1782 (increment >= (int32_t)NSEC_PER_SEC)) { in ptp_clock_stm32_adjust() 1789 if (increment >= 0) { in ptp_clock_stm32_adjust() 1790 heth->Instance->MACSTNUR = increment; in ptp_clock_stm32_adjust() 1792 heth->Instance->MACSTNUR = ETH_MACSTNUR_ADDSUB | (NSEC_PER_SEC + increment); in ptp_clock_stm32_adjust() 1800 if (increment >= 0) { in ptp_clock_stm32_adjust() 1801 heth->Instance->PTPTSLUR = increment; in ptp_clock_stm32_adjust() 1803 heth->Instance->PTPTSLUR = ETH_PTPTSLUR_TSUPNS | (-increment); in ptp_clock_stm32_adjust()
|
D | eth_e1000.c | 394 static int ptp_clock_e1000_adjust(const struct device *dev, int increment) in ptp_clock_e1000_adjust() argument 397 ARG_UNUSED(increment); in ptp_clock_e1000_adjust()
|
D | eth_native_posix.c | 678 int increment) in ptp_clock_adjust_native_posix() argument 681 ARG_UNUSED(increment); in ptp_clock_adjust_native_posix()
|
D | eth_sam_gmac.c | 2436 static int ptp_clock_sam_gmac_adjust(const struct device *dev, int increment) in ptp_clock_sam_gmac_adjust() argument 2442 if ((increment <= -NSEC_PER_SEC) || (increment >= NSEC_PER_SEC)) { in ptp_clock_sam_gmac_adjust() 2446 if (increment < 0) { in ptp_clock_sam_gmac_adjust() 2447 gmac->GMAC_TA = GMAC_TA_ADJ | GMAC_TA_ITDT(-increment); in ptp_clock_sam_gmac_adjust() 2449 gmac->GMAC_TA = GMAC_TA_ITDT(increment); in ptp_clock_sam_gmac_adjust()
|
D | eth_mcux.c | 1702 static int ptp_clock_mcux_adjust(const struct device *dev, int increment) in ptp_clock_mcux_adjust() argument 1710 if ((increment <= (int32_t)(-NSEC_PER_SEC)) || in ptp_clock_mcux_adjust() 1711 (increment >= (int32_t)NSEC_PER_SEC)) { in ptp_clock_mcux_adjust() 1721 context->base->ATPER = NSEC_PER_SEC - increment; in ptp_clock_mcux_adjust()
|
/Zephyr-Core-3.5.0/tests/net/ptp/clock/src/ |
D | main.c | 211 static int my_ptp_clock_adjust(const struct device *dev, int increment) in my_ptp_clock_adjust() argument 216 eth_ctx->time.nanosecond += increment; in my_ptp_clock_adjust()
|
/Zephyr-Core-3.5.0/samples/modules/canopennode/ |
D | README.rst | 42 Pressing the button labelled ``SW3`` will increment the button press 61 Pressing the button labelled ``SW3`` will increment the button press 80 Pressing the button labelled ``USER`` will increment the button press counter 99 Pressing the button labelled ``USER`` will increment the button press counter
|
/Zephyr-Core-3.5.0/subsys/bluetooth/mesh/ |
D | Kconfig | 1525 hex "Retransmissions interval increment of missing segments to unicast address" 1529 This value controls the interval increment used for delaying the 1531 a unicast address. The increment is measured in milliseconds and 1566 hex "Acknowledgment delay increment" 1570 This value controls the delay increment of an interval used for 1572 receiving a new segment. The increment is measured in segments 1673 100th increment. If the node sends messages very frequently a 1676 increment) can make sense. When the stack gets initialized it
|
/Zephyr-Core-3.5.0/doc/contribute/ |
D | contributor_expectations.rst | 134 - Changes to APIs must increment the API version number according to the API
|
/Zephyr-Core-3.5.0/scripts/ |
D | spelling.txt | 562 incrment||increment
|
/Zephyr-Core-3.5.0/doc/services/device_mgmt/ |
D | mcumgr.rst | 485 Let's suppose we want to increment those counters by ``1``, ``2`` and ``3``
|
/Zephyr-Core-3.5.0/doc/contribute/coding_guidelines/ |
D | index.rst | 614 …containing an increment (++) or decrement (--) operator should have no other potential side effect…
|
/Zephyr-Core-3.5.0/subsys/bluetooth/controller/ |
D | Kconfig.ll_sw_split | 512 packet sequence numbers do not increment according to the SDU interval
|
/Zephyr-Core-3.5.0/doc/ |
D | zephyr.doxyfile.in | 86 # level increment doubles the number of directories, resulting in 4096
|
/Zephyr-Core-3.5.0/doc/releases/ |
D | release-notes-3.3.rst | 682 * Atmel SAM: Added support to select fixed or increment address mode when using
|