OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/lib/CMakeLists.txt

15 lines
529 B
CMake
Raw Normal View History

kernel: add user mode work_q capability This allows for workqueues to be started in user mode. No additional kernel objects or system calls are defined other than starting the workqueue in user mode; for permission purposes the embedded queue and thread objects are sufficient. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-11-13 06:25:19 +08:00
zephyr_sources(thread_entry.c work_q.c)
lib: posix: Implement generic file descriptor table The table allows to wrap read/write (i.e. POSIX-compatible) semantics of any I/O object in POSIX-compatible fd (file descriptor) handling. Intended I/O objects include files, sockets, special devices, etc. The table table itself consists of (underlying obj*, function table*) pairs, where function table provides entries for read(), write, and generalized ioctl(), where generalized ioctl handles all other operations, up to and including closing of the underlying I/O object. Fixes: #7405 Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2018-10-08 18:55:03 +08:00
zephyr_sources(fdtable.c)
lib: move crc from drivers to lib/ Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-15 02:44:49 +08:00
add_subdirectory(crc)
libc: some architectures do not require baremetal libc When building a native application, we use the host provided libc, so do not build minimal libc or newlib. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-22 08:26:00 +08:00
add_subdirectory_ifdef(CONFIG_JSON_LIBRARY json)
if(NOT CONFIG_NATIVE_APPLICATION)
lib: move crc from drivers to lib/ Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-15 02:44:49 +08:00
add_subdirectory(libc)
libc: some architectures do not require baremetal libc When building a native application, we use the host provided libc, so do not build minimal libc or newlib. Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com> Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-22 08:26:00 +08:00
endif()
lib: move ring_buffer from misc/ to lib/ Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-15 02:57:03 +08:00
add_subdirectory_if_kconfig(ring_buffer)
lib: Add base64 library Since base64 is such a simple and commonly used feature it makes no sense to build the whole of mbedTLS for it. Instead take the implementation that comes with mbedTLS and import it as a native library outside of ext/ for all to use directly. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2018-03-23 03:05:26 +08:00
add_subdirectory_if_kconfig(base64)
lib: user mode compatible mempools We would like to offer the capability to have memory pool heap data structures that are usable from user mode threads. The current k_mem_pool implementation uses IRQ locking and system-wide membership lists that make it incompatible with user mode constraints. However, much of the existing memory pool code can be abstracted to some common functions that are used by both k_mem_pool and the new sys_mem_pool implementations. The sys_mem_pool implementation has the following differences: * The alloc/free APIs work directly with pointers, no internal memory block structures are exposed to the end user. A pointer to the source pool is provided for allocation, but freeing memory just requires the pointer and nothing else. * k_mem_pool uses IRQ locks and required very fine-grained locking in order to not affect system latency. sys_mem_pools just use a semaphore to protect the pool data structures at the API level, since there aren't implications for system responsiveness with this kind of concurrency control. * sys_mem_pools do not support the notion of timeouts for requesting memory. * sys_mem_pools are specified at compile time with macros, just like kernel memory pools. Alternative forms of specification at runtime will be a later enhancement. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-03-07 09:12:37 +08:00
add_subdirectory(mempool)
lib: posix: Add top-level define for all POSIX APIs - CONFIG_POSIX_API It so happened that previously CONFIG_PTHREAD_IPC served this role. But pthreads and IPC is only parts of POSIX, orthogonal to other services. Move CONFIG_POSIX_FS, etc. out from CONFIG_PTHREAD_IPC. Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2018-09-27 23:08:12 +08:00
add_subdirectory_ifdef(CONFIG_POSIX_API posix)
lib/cmsis_rtos_v1: Implement support for thread APIs These APIs allow defining, creating and controlling of thread related functionalities. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-06-05 11:33:12 +08:00
add_subdirectory_ifdef(CONFIG_CMSIS_RTOS_V1 cmsis_rtos_v1)
lib/cmsis_rtos_v2: Implement support for thread APIs These APIs allow defining, creating and controlling of thread related functionalities. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 14:49:03 +08:00
add_subdirectory_ifdef(CONFIG_CMSIS_RTOS_V2 cmsis_rtos_v2)
lib: Red/Black balanced tree data structure A balanced tree implementation for Zephyr as we grow into bigger regimes where simpler data structures aren't appropriate. This implements an intrusive balanced tree that guarantees O(log2(N)) runtime for all operations and amortized O(1) behavior for creation and destruction of whole trees. The algorithms and naming are conventional per existing academic and didactic implementations, c.f.: https://en.wikipedia.org/wiki/Red%E2%80%93black_tree The implementation is size-optimized to prioritize runtime memory usage. The data structure is intrusive, which is to say the struct rbnode handle is intended to be placed in a separate struct the same way other such structures (e.g. Zephyr's dlist list) and requires no data pointer to be stored in the node. The color bit is unioned with a pointer (fairly common for such libraries). Most notably, there is no "parent" pointer stored in the node, the upper structure of the tree being generated dynamically via a stack as the tree is recursed. So the overall memory overhead of a node is just two pointers, identical with a doubly-linked list. Code size above dlist is about 2-2.5k on most architectures, which is significant by Zephyr standards but probably still worthwhile in many situations. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2018-03-22 04:31:06 +08:00
add_subdirectory(rbtree)