Searched full:behind (Results 1 – 25 of 59) sorted by relevance
123
/Zephyr-latest/samples/net/cloud/mqtt_azure/ |
D | Kconfig | 44 behind proxy. 51 behind proxy.
|
D | README.rst | 54 the sample behind a proxy:
|
/Zephyr-latest/lib/utils/ |
D | winstream.c | 88 uint32_t seq0 = *seq, start, end, wseq, len, behind, copy, suffix; in sys_winstream_read() local 104 behind = wseq - *seq; in sys_winstream_read() 105 if (behind > idx_sub(ws, ws->end, ws->start)) { in sys_winstream_read() 111 copy = idx_sub(ws, ws->end, behind); in sys_winstream_read() 112 len = MIN(buflen, behind); in sys_winstream_read()
|
/Zephyr-latest/dts/bindings/bluetooth/ |
D | zephyr,bt-hci-uart.yaml | 3 description: Bluetooth HCI behind a UART device (H:4)
|
D | zephyr,bt-hci-3wire-uart.yaml | 3 description: Bluetooth HCI behind a 3-Wire UART device (H:5)
|
/Zephyr-latest/doc/services/crypto/ |
D | index.rst | 8 behind the operation of the different algorithms and how they were implemented.
|
/Zephyr-latest/doc/connectivity/networking/ |
D | index.rst | 7 Zephyr kernel. Use the information to understand the principles behind the
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | index.rst | 7 Zephyr OS. You can use this information to understand the principles behind the
|
/Zephyr-latest/doc/project/ |
D | issues.rst | 14 reason behind it by following the references in the code.
|
/Zephyr-latest/doc/kernel/data_structures/ |
D | index.rst | 19 behind this design is to allow the collections to be used in contexts
|
/Zephyr-latest/lib/hash/ |
D | hash_func32_djb2.c | 9 * behind it (and other DJB software) is quite amazing. Thanks Dan!!
|
/Zephyr-latest/soc/mediatek/mt8xxx/ |
D | mtk_adsp_load.py | 257 behind = seq - last_seq 258 if behind > ((end - start) % wlen): 260 copy = (end - behind) % wlen 261 suffix = min(behind, wlen - copy) 265 l2 = behind - suffix
|
/Zephyr-latest/doc/develop/west/ |
D | built-in.rst | 138 leaving behind any branches which were already checked out. This is 143 behind some commits which are no longer referred to by any branch. These 171 does not even try to rebase and leaves your branches behind just like a
|
D | why.rst | 18 Although the motivation behind splitting the Zephyr codebase into multiple
|
/Zephyr-latest/doc/services/portability/posix/implementation/ |
D | index.rst | 77 implementation of that system call should be hidden behind the POSIX API.
|
/Zephyr-latest/dts/bindings/misc/ |
D | zephyr,swdp-gpio.yaml | 82 GPIO pin used to disable the SWDIO output buffer behind optional
|
/Zephyr-latest/tests/subsys/fs/fcb/src/ |
D | fcb_test_reset.c | 115 /* Add a 3rd one, should go behind corrupt entry */ in ZTEST()
|
/Zephyr-latest/drivers/timer/ |
D | smartbond_timer.c | 145 * used for wakeup) is behind timer value or is equal to it. in sys_clock_set_timeout()
|
D | gecko_burtc_timer.c | 85 * writing it behind the memory barrier is enough in burtc_isr()
|
/Zephyr-latest/drivers/led/ |
D | lp5569.c | 143 /* If the device is behind a power domain, it will start in in lp5569_init()
|
/Zephyr-latest/samples/boards/nordic/nrf53_sync_rtc/ |
D | README.rst | 20 may be slightly behind (usually 1 tick) due to latency introduced by the
|
/Zephyr-latest/soc/intel/intel_adsp/tools/ |
D | cavstool.py | 689 behind = seq - last_seq 690 if behind > ((end - start) % wlen): 692 copy = (end - behind) % wlen 693 suffix = min(behind, wlen - copy) 695 if suffix < behind: 696 result += win_read(base, 16, behind - suffix)
|
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/ |
D | isoal.h | 87 /** Number of bytes accessible behind the dbuf pointer */ 178 /** Number of bytes accessible behind the dbuf pointer */
|
/Zephyr-latest/include/zephyr/sys/ |
D | sem.h | 192 * Behind the scenes this pattern expands to a for-loop whose body is executed
|
/Zephyr-latest/subsys/usb/device_next/ |
D | usbd_desc.c | 51 LOG_DBG("Add %u behind %u", new_nd->str.idx, tmp_nd->str.idx); in desc_add_and_update_idx()
|
123