Searched full:implementation (Results 1 – 25 of 1062) sorted by relevance
12345678910>>...43
| /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 | 9 The secure storage subsystem provides an implementation of the PSA Secure Storage API
28 prompt "Internal Trusted Storage (ITS) API implementation"
31 bool "Zephyr's ITS implementation"
35 Use Zephyr's implementation of the ITS API.
40 bool "Custom ITS implementation"
42 A custom implementation of the ITS API is present.
60 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"
39 bool "No ITS store module implementation"
42 bool "Custom ITS store module implementation"
|
| /Zephyr-latest/include/zephyr/arch/xtensa/ |
| D | atomic_xtensa.h | 14 * inline implementation here that is more or less identical
17 /** Implementation of @ref atomic_get. */
60 /** Implementation of @ref atomic_cas. */
67 /** Implementation of @ref atomic_ptr_cas. */
89 /** Implementation of @ref atomic_set. */
96 /** Implementation of @ref atomic_add. */
103 /** Implementation of @ref atomic_sub. */
110 /** Implementation of @ref atomic_inc. */
117 /** Implementation of @ref atomic_dec. */
124 /** Implementation of @ref atomic_or. */
[all …]
|
| D | cache.h | 27 /** Implementation of @ref arch_dcache_flush_range. */
43 /** Implementation of @ref arch_dcache_flush_and_invd_range. */
59 /** Implementation of @ref arch_dcache_invd_range. */
75 /** Implementation of @ref arch_dcache_invd_all. */
89 /** Implementation of @ref arch_dcache_flush_all. */
103 /** Implementation of @ref arch_dcache_flush_and_invd_all. */
117 /** Implementation of @ref arch_dcache_enable. */
123 /** Implementation of @ref arch_dcache_disable. */
133 /** Implementation of @ref arch_icache_line_size_get. */
139 /** Implementation of @ref arch_icache_flush_all. */
[all …]
|
| /Zephyr-latest/include/zephyr/net/ |
| D | conn_mgr_connectivity_impl.h | 27 * @brief Connection Manager Connectivity Implementation API
28 * @defgroup conn_mgr_connectivity_impl Connection Manager Connectivity Implementation API
45 * @brief When called, the connectivity implementation should start attempting to
56 * @brief When called, the connectivity implementation should disconnect (disassociate), or
67 * @brief Called once for each iface that has been bound to a connectivity implementation
79 * @brief Implementation callback for conn_mgr_if_set_opt.
81 * Used to set implementation-specific connectivity settings.
86 * It is up to the connectivity implementation to interpret optname. Options can be
88 * connectivity implementation.
100 * @brief Implementation callback for conn_mgr_if_get_opt.
[all …]
|
| D | conn_mgr_connectivity.h | 71 * When set, indicates that the connectivity implementation bound to this iface should
106 * If the provided iface has been bound to a connectivity implementation, initiate
116 * @retval -ENOTSUP if the iface does not have a connectivity implementation.
117 * @retval implementation-specific status code otherwise.
124 * If the provided iface has been bound to a connectivity implementation, disconnect/disassociate
132 * @retval -ENOTSUP if the iface does not have a connectivity implementation.
133 * @retval implementation-specific status code otherwise.
139 * to a connectivity implementation.
142 * @retval true if connectivity is supported (a connectivity implementation has been bound).
148 * @brief Set implementation-specific connectivity options.
[all …]
|
| /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 …]
|
| /Zephyr-latest/doc/services/portability/posix/implementation/ |
| D | index.rst | 3 Implementation Details
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/tests/net/conn_mgr_conn/src/ |
| D | test_conn_impl.h | 29 /* The number of times an A-implementation API func has been called (other than init) */
32 /* The number of times a B-implementation API func has been called (other than init) */
38 /* The number of times A-implementation init was called (should always be 1) */
41 /* The number of times B-implementation init was called (should always be 1) */
47 /* If true, the implementation should time out on connect. */
50 /* If nonzero, the implementation should fail to connect and raise this fatal error. */
71 /* Create an invalid L2 connectivity implementation with NULL API */
75 /* Create an L2 connectivity implementation without the optional init */
|
| /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/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.
50 prompt "Implementation of the generic wifi_mgmt connectivity backend"
55 bool "Application specific implementation of the connectivity backend"
57 The application defines its own implementation of CONNECTIVITY_WIFI_MGMT.
|
| /Zephyr-latest/doc/services/ |
| D | secure_storage.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/include/zephyr/ |
| D | syscall.h | 31 * directly call the implementation
37 * All system calls require a verifier function and an implementation
44 * implementation function. See documentation for that typedef for
45 * more information. - The implementation function will be named
46 * z_impl_k_foo(). This is the actual implementation of the system
67 * implementation like normal arguments
69 * Even if the system call implementation has no return value, these always
72 * Once everything has been validated, the real implementation will be executed.
82 * @return system call return value, or 0 if the system call implementation
|
| /Zephyr-latest/arch/posix/core/ |
| D | cpuhalt.c | 12 * An implementation of the architecture-specific
14 * It can be called within an implementation of _pm_save_idle(),
17 * An implementation of arch_cpu_atomic_idle(), which
29 #error "The POSIX architecture needs a custom busy_wait implementation. \
31 /* Each POSIX arch board (or SOC) must provide an implementation of
|
| /Zephyr-latest/arch/arm/core/cortex_m/ |
| D | Kconfig | 155 In an ARMv8-M Mainline implementation with the Security Extension
157 In an ARMv8-M Baseline implementation with the Security Extension
187 implementation, or the use of an ARMv8-M processor
188 supporting the Baseline implementation.
192 is also referred to as a Baseline Implementation. A
193 Baseline implementation has a subset of the instructions,
194 registers, and features, of a Mainline implementation.
204 implementation.
219 implementation, or the use of a backwards-compatible
220 ARMv8-M processor implementation supporting the Main
[all …]
|
| /Zephyr-latest/lib/libc/ |
| D | Kconfig | 10 Select a C library implementation that provides a complete C library
11 implementation, rather than the subset provided by MINIMAL_LIBC.
18 Select a printf implementation that provides a complete
19 implementation including floating point support.
25 complete implementation and which would be selected when
63 prompt "C Library Implementation"
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| 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/modules/ |
| D | Kconfig.renesas_fsp | 60 Includes RSIP-E51A implementation for SCE driver
67 Includes SCE7 implementation for SCE driver
74 Includes SCE5 implementation for SCE driver
81 Includes TRNG implementation for SCE driver
|
| /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/drivers/serial/ |
| D | uart_b91.c | 230 /* API implementation: irq handler */
245 /* API implementation: configure */
294 /* API implementation: config_get */
306 /* API implementation: driver initialization */
337 /* API implementation: poll_out */
350 /* API implementation: poll_in */
366 /* API implementation: err_check */
376 /* API implementation: fifo_fill */
399 /* API implementation: fifo_read */
418 /* API implementation: irq_tx_enable */
[all …]
|
| /Zephyr-latest/soc/andestech/ae350/ |
| D | Kconfig.soc | 8 Andes V5 AE350 SoC Series Implementation"
14 Andes AE350 SoC implementation"
|
| /Zephyr-latest/tests/bsim/bluetooth/ll/cis/ |
| D | Kconfig | 23 timeout implementation.
30 implementation.
43 implementation.
|
| /Zephyr-latest/soc/microchip/miv/miv/ |
| D | Kconfig.soc | 10 Microchip Mi-V implementation#
16 Microchip Mi-V system implementation
|
| /Zephyr-latest/soc/microchip/miv/polarfire/ |
| D | Kconfig.soc | 10 Microchip RV64 implementation
16 Microchip MPFS system implementation
|
12345678910>>...43
