Searched refs:implementation (Results 1 – 25 of 394) sorted by relevance
12345678910>>...16
| /Zephyr-latest/lib/libc/common/ |
| D | Kconfig | 7 common implementation of abort().
12 common implementation of asctime().
18 common implementation of asctime_r().
24 common implementation of ctime().
30 common implementation of ctime_r().
35 common implementation of gmtime_r().
41 Simple implementation of localtime() & localtime_r().
48 common implementation of time().
51 bool "Common C library malloc implementation"
54 Common implementation of malloc family that uses the kernel heap
[all …]
|
| /Zephyr-latest/subsys/secure_storage/ |
| D | Kconfig | 10 The secure storage subsystem provides an implementation of the PSA Secure Storage API
29 prompt "Internal Trusted Storage (ITS) API implementation"
32 bool "Zephyr's ITS implementation"
36 Use Zephyr's implementation of the ITS API.
41 bool "Custom ITS implementation"
43 A custom implementation of the ITS API is present.
61 Zephyr's ITS implementation calls into it.
71 Zephyr's ITS implementation calls into it.
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 …]
|
| D | Kconfig.its_store | 5 prompt "ITS store module implementation"
13 bool "ITS store module implementation using ZMS for storage"
19 This implementation of the ITS store module makes direct use of ZMS for storage.
22 overhead compared to the settings-based implementation, both in terms of runtime
28 bool "ITS store module implementation using the settings subsystem for storage"
37 bool "No ITS store module implementation"
40 bool "Custom ITS store module implementation"
|
| /Zephyr-latest/cmake/modules/ |
| D | FindThreads.cmake | 5 # FindThreads module for locating threads implementation.
13 # The threads library to use. Zephyr provides threads implementation and no
20 # The original implementation tries to find threads library using various
22 # program to check if the implementation is provided by libc), but it's not
23 # able to detect pthread implementation provided by Zephyr.
|
| /Zephyr-latest/tests/subsys/ipc/ipc_sessions/interoperability/ |
| D | Kconfig | 14 bool "ICMSG backend with SPSC packet buffer (old implementation)"
18 Chosing this backend results in single endpoint implementation based
22 bool "icmsg IPC library (old implementation)"
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 15 See the :ref:`implementation guidelines <conn_mgr_impl_guidelines>` for details on writing conforma…
22 The :ref:`implementation API <conn_mgr_impl_api>` allows connectivity implementations to be :ref:`d…
24 … in :c:struct:`conn_mgr_conn_api` struct (which should be populated with implementation callbacks).
29 …alled on the iface, and they will be translated to the corresponding implementation functions in :…
35 This binding structure will contain a reference to the bound iface, the connectivity implementation…
37 …ion can then be iterated over to find out what (if any) connectivity implementation has been bound…
41 A single connectivity implementation may be bound to multiple ifaces.
59 Since a single connectivity implementation may be shared by several Zephyr ifaces, each binding ins…
66 Defining an implementation
69 A connectivity implementation may be defined as follows:
[all …]
|
| D | index.rst | 10 implementation.rst
|
| /Zephyr-latest/doc/services/portability/posix/implementation/ |
| D | index.rst | 26 As a library, Zephyr's POSIX API implementation makes an effort to be a thin abstraction layer
32 elsewhere, unless required both by the POSIX API implementation and some other feature. An
33 example where the implementation should remain part of the POSIX implementation is
34 ``getopt()``. Examples where the implementation should be part of separate libraries are
37 - When the POSIX API and another Zephyr subsystem both rely on a feature, the implementation of
41 depends on ``libzfoo`` for the implementation of some functionality "foo" in Zephyr. If
76 :ref:`System Call <syscalls>` is needed as part of the implementation, the declaration and the
77 implementation of that system call should be hidden behind the POSIX API.
|
| /Zephyr-latest/soc/microchip/miv/miv/ |
| D | Kconfig.soc | 10 Microchip Mi-V implementation#
16 Microchip Mi-V system implementation
|
| /Zephyr-latest/cmake/toolchain/iar/ |
| D | Kconfig | 15 bool "Use the IAR semihosting implementation."
18 Use the semihosting implementation in the IAR library
19 instead of the Zephyr implementation.
|
| /Zephyr-latest/doc/services/storage/secure_storage/ |
| D | index.rst | 6 | The secure storage subsystem provides an implementation of the functions defined in the
9 that don't already have an implementation of the API.
16 As such, it provides an implementation of the API on those that don't already have one, ensuring
19 cannot enable the subsystem because TF-M already provides an implementation of the API.
30 The secure storage subsystem's implementation of the PSA Secure Storage API:
35 | See below for important ways the implementation deviates from the specification.
41 * does not yet provide an implementation of the Protected Storage (PS) API as of this writing.
44 (unless a `custom implementation <#whole-api>`_ of the PS API is provided).
46 Below are some ways the implementation deviates from the specification
78 To configure the implementation of the PSA Secure Storage API provided by Zephyr, have a look at the
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_offload.rst | 17 to provide an alternate implementation for an IP stack. This means that the
36 alternate implementation of the networking stack, exposing socket API for their
40 implementation on how to integrate network offloading at socket level.
|
| D | sockets.rst | 13 Zephyr offers an implementation of a subset of the BSD Sockets API (a part
18 compatible API implementation for Zephyr:
71 communication. Secure functions for the implementation are provided by
72 mbedTLS library. Secure sockets implementation allows use of both TLS and DTLS
160 option. A network driver that wants to register a new socket implementation
165 An arbitrary name for the socket implementation.
168 Socket implementation's priority. The higher the priority, the earlier this
169 particular implementation will be processed when creating a new socket.
178 type and protocol are supported by the offloaded socket implementation.
184 Every offloaded socket implementation should also implement a set of socket
[all …]
|
| /Zephyr-latest/subsys/usb/device_next/class/ |
| D | Kconfig.cdc_ecm | 6 bool "USB CDC ECM implementation [EXPERIMENTAL]"
11 USB CDC Ethernet Control Model (ECM) implementation"
|
| D | Kconfig.cdc_acm | 6 bool "USB CDC ACM implementation [EXPERIMENTAL]"
15 USB device CDC ACM class implementation.
|
| D | Kconfig.cdc_ncm | 6 bool "USB CDC NCM implementation [EXPERIMENTAL]"
12 USB CDC Network Control Model (NCM) implementation
|
| /Zephyr-latest/soc/microchip/miv/polarfire/ |
| D | Kconfig.soc | 10 Microchip RV64 implementation
16 Microchip MPFS system implementation
|
| /Zephyr-latest/drivers/adc/ |
| D | Kconfig.gecko | 13 Enable the driver implementation for the Silabs GeckoEXX32 Incremental ADC
22 Enable the driver implementation for the Silabs GeckoEFM32 ADC
|
| /Zephyr-latest/subsys/net/conn_mgr/ |
| D | Kconfig | 43 bool "Generic WiFi management connectivity implementation"
47 Which implementation is compiled is controlled via CONNECTIVITY_WIFI_MGMT_IMPL.
55 bool "Application specific implementation of the connectivity backend"
57 The application defines its own implementation of CONNECTIVITY_WIFI_MGMT.
|
| /Zephyr-latest/subsys/ipc/ipc_service/backends/ |
| D | Kconfig | 26 Chosing this backend results in single endpoint implementation based
36 Chosing this backend results in multi endpoint implementation based
47 Chosing this backend results in multi endpoint implementation based
|
| /Zephyr-latest/modules/loramac-node/ |
| D | Kconfig | 34 bool "Semtech Secure Element software implementation"
38 software implementation
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v1/philosophers/ |
| D | README.rst | 11 implementation demonstrates the usage of multiple preemptible and cooperative
13 which uses CMSIS RTOS V1 API implementation in Zephyr.
52 An implementation of a solution to the Dining Philosophers
54 CMSIS RTOS V1 APIs. This particular implementation demonstrates the
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/philosophers/ |
| D | README.rst | 11 implementation demonstrates the usage of multiple preemptible and cooperative
13 which uses CMSIS RTOS V2 API implementation in Zephyr.
52 An implementation of a solution to the Dining Philosophers
54 CMSIS RTOS V2 APIs. This particular implementation demonstrates the
|
| /Zephyr-latest/tests/bsim/bluetooth/ll/edtt/tests_scripts/ |
| D | ll.set1.llcp.test_list | 30 #LL/CON/CEN/BI-06-C # This test implementation is not valid, and will fail with refactored LLCP
52 #LL/CON/CEN/BV-74-C # Needs testcase implementation update
53 #LL/CON/CEN/BV-76-C # Needs testcase implementation update
54 #LL/CON/CEN/BV-77-C # Needs testcase implementation update
55 #LL/CON/PER/BI-08-C # This test implementation is not valid, and will fail with refactored LLCP
|
| /Zephyr-latest/tests/bsim/bluetooth/ll/cis/ |
| D | Kconfig | 23 timeout implementation.
30 implementation.
43 implementation.
|
12345678910>>...16
