Searched full:apis (Results 1 – 25 of 670) sorted by relevance
12345678910>>...27
| /Zephyr-latest/doc/develop/west/ |
| D | west-not-found.rst | 3 .. _west-apis:
4 .. _west-apis-west:
5 .. _west-apis-commands:
6 .. _west-apis-westcommand:
7 .. _west-apis-configuration:
8 .. _west-apis-log:
9 .. _west-apis-manifest:
10 .. _west-apis-util:
12 West APIs
15 The west APIs are not documented since either west was missing or the zephyr
|
| D | west-apis.rst | 3 .. _west-apis:
4 .. _west-apis-west:
6 West APIs
9 This page documents the Python APIs provided by :ref:`west <west>`, as well as
10 some additional APIs used by the :ref:`west extensions <west-extensions>` in
23 .. _west-apis-commands:
214 .. _west-apis-commands-output:
248 .. _west-apis-configuration:
274 Deprecated APIs
277 The following APIs also use :py:class:`west.configuration.ConfigFile`, but they
[all …]
|
| /Zephyr-latest/doc/_doxygen/ |
| D | groups.dox | 20 @brief Device Driver APIs
21 @defgroup io_interfaces Device Driver APIs
25 @brief Miscellaneous Drivers APIs
26 @defgroup misc_interfaces Miscellaneous Drivers APIs
31 @brief Multi Function Device Drivers APIs
32 @defgroup mfd_interfaces Multi Function Device Drivers APIs
57 @brief Data Structure APIs
58 @defgroup datastructure_apis Data Structure APIs
64 @brief APIs to interact with third-party services or applications
69 @brief Modem APIs
[all …]
|
| /Zephyr-latest/doc/services/pm/api/ |
| D | index.rst | 3 Power Management APIs
6 System PM APIs
26 Device PM APIs
33 Device Runtime PM APIs
|
| /Zephyr-latest/doc/develop/api/ |
| D | overview.rst | 6 The table lists Zephyr's APIs and information about them, including their
25 * APIs with major versions equal or larger than one (x.y.z | x >= 1 ) are
27 * All existing stable APIs in Zephyr will be start with version 1.0.0.
44 Version for existing APIs are initially set based on the current state of the
45 APIs:
49 - and finally 1.0.0 indicates a :ref:`stable <api_lifecycle_stable>` APIs.
51 Changes to APIs in the future will require adapting the version following the
|
| D | api_lifecycle.rst | 6 Developers using Zephyr's APIs need to know how long they can trust that a
8 maintaining and extending Zephyr's APIs need to be able to introduce
9 new APIs that aren't yet fully proven, and to potentially retire old APIs when they're
20 An up-to-date table of all APIs and their maturity level can be found in the
29 Experimental APIs denote that a feature was introduced recently, and may change
33 The following requirements apply to all new APIs:
39 of said API (in the case of peripheral APIs, this corresponds to one driver)
46 Peripheral APIs (Hardware Related)
66 where the API is defined. Unstable APIs shall have a version where the minor
73 Peripheral APIs (Hardware Related)
[all …]
|
| D | design_guidelines.rst | 13 Many APIs involve passing a callback as a parameter or as a member of a
68 Conditional Data and APIs
71 APIs and libraries may provide features that are expensive in RAM or
111 A distinction is needed between APIs that are not supported and those that are
114 - APIs that are supported but not implemented shall return ``-ENOSYS``.
116 - Optional APIs that are not supported by the hardware should be implemented and
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | index.rst | 3 Networking APIs
6 Zephyr provides support for the standard BSD socket APIs (defined in
10 Apart of the standard API, Zephyr provides a set of custom networking APIs and
20 apis.rst
|
| /Zephyr-latest/include/zephyr/drivers/mm/ |
| D | mm_drv_bank.h | 9 * @brief Memory Banks Driver APIs
11 * This contains generic APIs to be used by a system-wide memory management
15 * to protect the data when using these APIs.
26 * @brief Memory Banks Driver APIs
27 * @defgroup mm_drv_bank_apis Memory Banks Driver APIs
29 * This contains APIs for a system-wide memory management driver to
33 * to protect the data when using these APIs.
|
| /Zephyr-latest/drivers/sensor/st/stmemsc/ |
| D | stmemsc.h | 23 * standard stmemsc i2c APIs.
40 * specific stmemsc i2c APIs that set reg_addr MSB to '1' in order to allow
58 * custom stmemsc i2c APIs specified by driver.
73 * standard stmemsc i3c APIs.
92 * stmemsc spi APIs.
109 * specific stmemsc sp APIs that set reg_addr bit6 to '1' in order to allow
127 * custom stmemsc spi APIs specified by driver.
|
| /Zephyr-latest/tests/kernel/threads/thread_apis/ |
| D | testcase.yaml | 8 kernel.threads.apis:
10 kernel.threads.apis.pinonly:
|
| /Zephyr-latest/doc/services/portability/ |
| D | index.rst | 6 OS abstraction layers (OSAL) provide wrapper function APIs that
8 These APIs make it easier and quicker to develop for, and port code to
|
| /Zephyr-latest/doc/project/ |
| D | documentation.rst | 9 Well documented APIs enhance the experience for developers and are an essential
11 documentation tool that the zephyr project uses for documenting APIs. It
20 APIs for the most part document the implementation of requirements or advertised
32 environment. Tests are documented using references to the APIs or functionality
33 they validate by creating a link back to the APIs and by adding a reference to
|
| /Zephyr-latest/samples/bluetooth/handsfree/ |
| D | README.rst | 5 Use the Hands-Free Profile (HFP) APIs.
10 Application demonstrating usage of the Hands-free Profile (HFP) APIs.
|
| /Zephyr-latest/samples/bluetooth/handsfree_ag/ |
| D | README.rst | 5 Use the Hands-Free Profile Audio Gateway (AG) APIs.
10 Application demonstrating usage of the Hands-free Audio Gateway (AG) APIs.
|
| /Zephyr-latest/boards/native/native_sim/ |
| D | native_posix_compat.h | 8 * This file provides in native_sim a set of APIs the native_posix board provided
11 * Note that all these APIs should be considered deprecated in native_sim, as this
|
| /Zephyr-latest/include/zephyr/dt-bindings/mipi_dsi/ |
| D | mipi_dsi.h | 11 * @brief MIPI-DSI driver APIs
12 * @defgroup mipi_dsi_interface MIPI-DSI driver APIs
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.mem_domain | 39 APIs:
48 thread access to memory. Memory domain APIs may only be invoked from
53 tables, these APIs don't need to be implemented as the underlying
|
| /Zephyr-latest/scripts/native_simulator/common/src/include/ |
| D | nsi_main_semipublic.h | 17 * These APIs are exposed for special use cases in which a developer needs to
23 * These APIs should be used with care, and not be used when the native
|
| /Zephyr-latest/doc/services/ |
| D | misc.rst | 11 Checksum APIs
19 Structured Data APIs
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | atomic.rst | 19 Using the kernel's atomic APIs to manipulate an atomic variable
44 An atomic variable is manipulated using the APIs listed at the end of
74 the APIs listed at the end of this section that end with :c:func:`_bit`.
94 For consistency and correctness, all Zephyr atomic APIs are expected
129 All atomic services APIs can be used by both threads and ISRs.
|
| /Zephyr-latest/include/zephyr/tracing/ |
| D | tracing.h | 35 * @brief Tracing APIs
36 * @defgroup subsys_tracing_apis Tracing APIs
41 * @brief Thread Tracing APIs
42 * @defgroup subsys_tracing_apis_thread Thread Tracing APIs
310 * @brief Work Tracing APIs
311 * @defgroup subsys_tracing_apis_work Work Tracing APIs
407 * @brief Work Queue Tracing APIs
408 * @defgroup subsys_tracing_apis_work_q Work Queue Tracing APIs
481 * @brief Work Delayable Tracing APIs
482 * @defgroup subsys_tracing_apis_work_delayable Work Delayable Tracing APIs
[all …]
|
| /Zephyr-latest/include/zephyr/storage/ |
| D | disk_access.h | 11 * This file contains APIs for disk access.
18 * @brief Storage APIs
19 * @defgroup storage_apis Storage APIs
26 * @brief Disk Access APIs
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/philosophers/ |
| D | README.rst | 2 :name: Dining Philosophers (CMSIS RTOS V2 APIs)
10 multi-thread synchronization problem) using CMSIS RTOS V2 APIs. This particular
54 CMSIS RTOS V2 APIs. This particular implementation demonstrates the
|
| /Zephyr-latest/subsys/secure_storage/src/its/ |
| D | CMakeLists.txt | 17 This means that the data and keys stored via the PSA APIs may not be secure at rest.")
22 This means that the data and keys stored via the PSA APIs will not be secure at rest.
|
12345678910>>...27
