Searched refs:calls (Results 126 – 150 of 204) sorted by relevance
123456789
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-dev.rst | 22 is the case for all API calls is an ongoing one, but the overall goal is
|
| D | bluetooth-arch.rst | 66 Controller communicate directly through function calls and queues in RAM. The
|
| /Zephyr-latest/doc/develop/api/ |
| D | terminology.rst | 158 or :c:macro:`SYS_INIT()` calls that may be invoked with ``PRE_KERNEL_1``
|
| /Zephyr-latest/subsys/net/l2/openthread/ |
| D | Kconfig | 51 started manually, with respective API calls or CLI/NCP commands.
|
| /Zephyr-latest/subsys/testsuite/ztest/ |
| D | Kconfig | 213 that while tests will still be marked as skipped on failed zassume calls, the final test
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 174 system boot). These calls can occur at any time, but the driver is
208 * The driver can ignore calls to :c:func:`sys_clock_set_timeout`, as every
|
| D | timers.rst | 225 :c:func:`k_sleep` and :c:func:`k_usleep` calls.
|
| /Zephyr-latest/boards/wiznet/w5500_evb_pico/doc/ |
| D | index.rst | 216 command that directly calls OpenOCD (assuming a SEGGER JLink adapter is used):
|
| /Zephyr-latest/cmake/bintools/ |
| D | bintools_template.cmake | 31 # This is done, so that unexpected calls to non-implemented command can be easily detected.
|
| /Zephyr-latest/doc/develop/test/ |
| D | bsim.rst | 149 This build scripts use the common compile.source which provide a function (compile) which calls
|
| /Zephyr-latest/subsys/shell/ |
| D | Kconfig | 95 to limit number of peripheral access calls.
|
| /Zephyr-latest/tests/benchmarks/thread_metric/ |
| D | thread_metric_readme.txt | 97 Zephyr's version does not spawn a reporting thread. Instead it calls
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.2.rst | 525 * Added async API system calls
554 * Added system calls
879 * :github:`22290` - ARC crashes due to concurrent system calls
995 * :github:`21432` - watchdog subsystem has no system calls
996 * :github:`21431` - missing async uart.h system calls
1176 * :github:`14650` - missing system calls in Counter driver APIs
|
| D | release-notes-1.13.rst | 15 * Introduce system calls for BSD socket APIs
118 * Introduce system calls for BSD socket APIs.
501 * :github:`8587` - ZTEST should support multiple calls to mocked function
572 * :github:`8203` - Implement system calls for the new socket APIs
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 185 Finally, the sending thread calls a mailbox send API to initiate the
305 characterizes the message it wants to receive. It then calls one of the
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | memory_domain.rst | 100 A small subset of kernel APIs, invoked as system calls, require heap memory
102 directly by user mode. In order to use these system calls, invoking threads
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | fatal.rst | 241 function has a default implementation with weak linkage that calls
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | demand_paging.rst | 90 Paging statistics can be obtained via various function calls when
|
| D | heap.rst | 55 or more complicated. Unlike ``k_heap``, all calls to any ``sys_heap``
|
| /Zephyr-latest/boards/ti/cc3220sf_launchxl/doc/ |
| D | index.rst | 243 offload point, enabling Zephyr BSD socket API calls to be directed to the
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob.rst | 115 calls :c:member:`block_end <bt_mesh_blob_io.block_end>`. When the transfer is complete, the BLOB
|
| /Zephyr-latest/doc/kernel/services/ |
| D | polling.rst | 305 that is passed a signal will return after any code in the system calls
|
| /Zephyr-latest/doc/develop/west/ |
| D | west-apis.rst | 146 These should be reverted back to automethod calls at the next release.
|
| /Zephyr-latest/doc/services/rtio/ |
| D | index.rst | 85 and device on the bus it is embodied in what RTIO calls an iodev.
|
| /Zephyr-latest/boards/ti/cc3235sf_launchxl/doc/ |
| D | index.rst | 243 offload point, enabling Zephyr BSD socket API calls to be directed to the
|
123456789
