Lines Matching full:apis
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)
79 Hardware Agnostic APIs
82 For hardware agnostic APIs, multiple applications using it are required to
99 - Stable APIs can get backward compatible updates, bug fixes and security fixes
114 where the API is defined. Stable APIs shall have a version where the major
214 Unstable APIs can be removed without deprecation at any time.
215 Deprecation and removal of APIs will be announced in the "API Changes"
220 - Deprecation Time (stable APIs): 2 Releases
231 contains the ``DEPRECATED`` word in it) that, when enabled, reverts the APIs
241 tracking removal of deprecated APIs.
245 state. The Zephyr maintainers will track usage of deprecated APIs on