Searched refs:API (Results 1 – 25 of 745) sorted by relevance
12345678910>>...30
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 3 API Lifecycle
7 given API will not change in future releases. At the same time, developers
15 :alt: API Life Cycle
18 API Life Cycle
35 - Documentation of the API (usage)
38 - The API introduction should be accompanied by at least one implementation
39 of said API (in the case of peripheral APIs, this corresponds to one driver)
40 - At least one sample using the new API (may only build on one single board)
42 When introducing a new and experimental API, mark the API version in the headers
43 where the API is defined. An experimental API shall have a version where the minor
[all …]
|
| D | overview.rst | 3 API Overview
7 current :ref:`stability level <api_lifecycle>`. More details about API changes
14 change at any time. The public API SHOULD NOT be considered stable.
16 * If minor version is up to one (0.1.z), API is considered
18 * If minor version is larger than one (0.y.z | y > 1), API is considered
21 * Version 1.0.0 defines the public API. The way in which the version number
22 is incremented after this release is dependent on this public API and how it
34 compatible functionality is introduced to the public API. It MUST be
35 incremented if any public API functionality is marked as deprecated. It MAY
41 breaking change was made to the API.
[all …]
|
| /Zephyr-latest/doc/connectivity/usb/host/api/ |
| D | uhc.rst | 3 USB host controller (UHC) driver API
6 The USB host controller driver API is described in
8 as the ``UHC driver`` API.
10 UHC driver API is experimental and is subject to change without notice.
12 Driver API reference
|
| /Zephyr-latest/doc/connectivity/usb/device/api/ |
| D | usb_dc.rst | 3 USB device controller driver API
6 The USB device controller driver API is described in
8 as the ``usb_dc`` API.
10 This API has some limitations by design, it does not follow :ref:`device_model_api`
13 API reference
|
| D | usb_device.rst | 3 USB device stack API
6 API reference
9 There are two ways to transmit data, using the 'low' level read/write API or
10 the 'high' level transfer API.
12 Low level API
21 High level API
23 transfer API will automatically split the data transmission into one or more
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | uart.rst | 10 on the method, different API functions are used according to below sections:
22 With the Interrupt-driven API, possibly slow communication can happen in the
27 The Asynchronous API allows to read and write data in the background using DMA
33 Interrupt-driven API and the Asynchronous API should NOT be used at
38 so that only the callbacks associated with one API is active at a time.
44 Most importantly, the Kconfig options define whether the polling API (default),
45 the interrupt-driven API or the asynchronous API can be used. Only enable the
59 API Reference
67 Polling API
75 Interrupt-driven API
[all …]
|
| D | flash.rst | 11 Offsets used by the user API are expressed in relation to
14 API for retrieving the layout of pages (see :kconfig:option:`CONFIG_FLASH_PAGE_LAYOUT`).
18 API for retrieving the layout of pages).
22 User API Reference
26 Implementation interface API Reference
|
| D | i2c.rst | 22 support the target mode. Zephyr has API for both roles.
26 I2C Controller API
29 Zephyr's I2C controller API is used when an I2C peripheral controls the bus,
34 This API is supported in all in-tree I2C peripheral drivers and is
39 I2C Target API
42 Zephyr's I2C target API is used when an I2C peripheral responds to
47 This API is supported in very few in-tree I2C peripheral drivers. The
48 API is considered experimental, as it is not compatible with the
59 API Reference
|
| /Zephyr-latest/doc/connectivity/usb/device_next/api/ |
| D | udc.rst | 3 USB device controller (UDC) driver API
6 The USB device controller driver API is described in
8 as the ``UDC driver`` API.
10 UDC driver API is experimental and is subject to change without notice.
12 driver to UDC driver API, or add a new driver, please use
15 API reference
|
| D | usbd_hid_device.rst | 3 HID device API
6 HID device specific API defined in :zephyr_file:`include/zephyr/usb/class/usbd_hid.h`.
8 API Reference
|
| D | usbd_dfu.rst | 3 USB DFU device API
6 USB DFU device specific API defined in :zephyr_file:`include/zephyr/usb/class/usbd_dfu.h`.
8 API Reference
|
| D | uac2_device.rst | 3 Audio Class 2 device API
6 USB Audio Class 2 device specific API defined in :zephyr_file:`include/zephyr/usb/class/usbd_uac2.h…
8 API Reference
|
| D | usbd_midi2.rst | 3 MIDI 2.0 Class device API
6 USB MIDI 2.0 device specific API defined in :zephyr_file:`include/zephyr/usb/class/usbd_midi2.h`.
8 API Reference
|
| D | usbd.rst | 3 USB device stack (next) API
6 New USB device stack API is experimental and is subject to change without notice.
8 API reference
|
| D | usbd_msc_device.rst | 3 USB Mass Storage Class device API
6 USB Mass Storage Class device API defined in
9 API Reference
|
| /Zephyr-latest/samples/tfm_integration/tfm_psa_test/ |
| D | README.rst | 71 [Check 1] Call get API for UID 6 which is not set
72 [Check 2] Call get_info API for UID 6 which is not set
73 [Check 3] Call remove API for UID 6 which is not set
74 [Check 4] Call get API for UID 6 which is removed
75 [Check 5] Call get_info API for UID 6 which is removed
76 [Check 6] Call remove API for UID 6 which is removed
78 [Check 7] Call get API for different UID 5
79 [Check 8] Call get_info API for different UID 5
80 [Check 9] Call remove API for different UID 5
83 [Check 1] Call get API for UID 6 which is not set
[all …]
|
| /Zephyr-latest/doc/services/crypto/api/ |
| D | index.rst | 10 API Reference
13 Generic API for crypto drivers
17 Ciphers API
|
| /Zephyr-latest/doc/services/storage/secure_storage/ |
| D | index.rst | 7 …`Platform Security Architecture (PSA) Secure Storage API <https://arm-software.github.io/psa-api/s…
9 that don't already have an implementation of the API.
14 The secure storage subsystem makes the PSA Secure Storage API available on all board targets with
16 As such, it provides an implementation of the API on those that don't already have one, ensuring
17 functional support for the API.
19 cannot enable the subsystem because TF-M already provides an implementation of the API.
21 | In addition to providing functional support for the API, depending on
23 may secure the data stored via the PSA Secure Storage API at rest.
30 The secure storage subsystem's implementation of the PSA Secure Storage API:
34 | Its foremost goal is functional support for the API on all board targets.
[all …]
|
| /Zephyr-latest/subsys/secure_storage/ |
| D | Kconfig | 10 The secure storage subsystem provides an implementation of the PSA Secure Storage API
12 It allows making use of the PSA Secure Storage API and persistent keys in the PSA Crypto
13 API in a standard and portable way.
16 In addition to providing functional support for the PSA Secure Storage API, depending on
29 prompt "Internal Trusted Storage (ITS) API implementation"
36 Use Zephyr's implementation of the ITS API.
43 A custom implementation of the ITS API is present.
54 Increasing this value increases the stack usage when serving PSA ITS API calls.
78 prompt "Protected Storage (PS) API implementation"
84 The PS API doesn't have an implementation of its own, and directly calls into the ITS API.
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/eeprom/ |
| D | api.rst | 3 EEPROM API
9 The EEPROM API provides read and write access to Electrically Erasable
19 API Reference
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_offload.rst | 16 The network offloading API provides hooks that a device vendor can use
21 API Reference
34 In addition to the network offloading API, Zephyr allows offloading of networking
35 functionality at the socket API level. With this approach, vendors who provide an
36 alternate implementation of the networking stack, exposing socket API for their
|
| D | ieee802154.rst | 40 API Reference
43 IEEE 802.15.4 API Overview
54 IEEE 802.15.4 Management API
57 This is the main subsystem-specific API of interest to IEEE 802.15.4
69 IEEE 802.15.4 Driver API
72 This is the main API of interest to IEEE 802.15.4 **driver developers**.
79 IEEE 802.15.4 L2 / Native Stack API
84 network layers (L3+), its socket and network context abstractions. This API is
89 OpenThread L2 Adaptation Layer API
93 stack together with Zephyr's IEEE 802.15.4 protocol agnostic driver API. This
[all …]
|
| /Zephyr-latest/include/zephyr/drivers/misc/ |
| D | README | 4 Zephyr Device Drivers API. Such drivers have only device-specific API providing
5 functionalities not covered by any Generic Device Driver API.
14 buffer required by generic display driver API. Instead, it exposes higher
16 rendering. These operations are controlled by a vendor-specific API designed
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/ |
| D | hci_raw.rst | 10 HCI RAW channel API is intended to expose HCI interface to the remote entity.
12 Bluetooth stack is not used. RAW API provides direct access to packets which
15 API Reference
|
| /Zephyr-latest/doc/services/portability/posix/option_groups/ |
| D | index.rst | 17 :header: API, Supported
38 :header: API, Supported
83 :header: API, Supported
110 :header: API, Supported
129 :header: API, Supported
190 :header: API, Supported
212 :header: API, Supported
231 :header: API, Supported
269 :header: API, Supported
282 :header: API, Supported
[all …]
|
12345678910>>...30
