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

43 lines
923 B
CMake
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
lib: syscalls: use zephyr_syscall_header This adds a few line use zephyr_syscall_header() to include headers containing syscall function prototypes. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2023-03-14 05:47:23 +08:00
zephyr_syscall_header(
${ZEPHYR_BASE}/include/zephyr/sys/mutex.h
)
lib: flatten all loose components into one lib lib/ was starting to get messy and inconsitent. Files being either dumped in the root or in sub-directories without a clear plan. Move all library components into one single folder and call it 'os'. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-01-19 19:57:38 +08:00
zephyr_sources(
lib: cbprintf: add support for deferred formatting In applications like logging the call site where arguments to formatting are available may not be suitable for performing the formatting, e.g. when the output operation can sleep. Add API that supports capturing data that may be transient into a buffer that can be saved, and API that then produces the output later using the packaged arguments. [ Documentation and commit log from Peter Bigot. ] Signed-off-by: Nicolas Pitre <npitre@baylibre.com> Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no>
2021-03-03 12:14:24 +08:00
cbprintf_packaged.c
lib: os: make snprintk fns generally available The intention of disabling CONFIG_PRINTK is that all invocations of it will compile to nothing, saving a lot of runtime overhead and footprint since all the format strings are completely dropped; instances of printk() and related functions are no-ops. However, some subsystems need snprintk() for string processing, since the snprintf() implementations in even minimal C library are too costly in text footprint or stack usage for some applications. This processing is required for the application to even function. This patch continues to have disabling CONFIG_PRINTK to cause the non snprintk functions to become no-ops, but now we always compile the necessary bits for snprintk(), relying on gc-sections to discard them if unused. z_vprintk() is now unconditionally defined in the header since it is not tied to any particular output sink and is intended for users who know exactly what they are doing (it's in zephyr private scope). Relates to: #21564 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2020-01-03 03:57:43 +08:00
printk.c
lib: os: add sys_sem data type For systems with userspace, the sys_sem exist in user memory working as counter semaphore for user mode thread. The implemention of sys_sem is based on k_futex. And the majority of the synchronization operations are performed in user mode to reduce the calling of system call. And for systems without userspace enabled, sys_sem behaves like k_sem. Fixes: #15139. Signed-off-by: Wentong Wu <wentong.wu@intel.com>
2019-07-24 16:04:55 +08:00
sem.c
lib: flatten all loose components into one lib lib/ was starting to get messy and inconsitent. Files being either dumped in the root or in sub-directories without a clear plan. Move all library components into one single folder and call it 'os'. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-01-19 19:57:38 +08:00
thread_entry.c
)
lib: os: build fdtable conditionally Stop building fdtable by default, make it conditional and build it only when needed. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2023-09-25 20:30:16 +08:00
zephyr_sources_ifdef(CONFIG_FDTABLE fdtable.c)
lib: onoff: add a config for on-off and build conditionally Do not build this service unconditionally. Partial fix of #50654 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2022-09-27 00:53:00 +08:00
lib: add cbprintf capability This commit adds a C99 stdio value formatter capability where generated text is emitted through a callback. This allows generation of arbitrarily long output without a buffer, functionality that is core to printk, logging, and other system and application needs. The formatter supports most C99 specifications, excluding: * %Lf long double conversion * wide character output Kconfig options allow disabling features like floating-point conversion if they are not necessary. By default most conversions are enabled. The original z_vprintk() implementation is adapted to meet the interface requirements of cbvprintf, and made available as an opt-in feature for space-constrained applications that do not need full formatting support. Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no>
2020-11-08 20:24:22 +08:00
zephyr_sources_ifdef(CONFIG_CBPRINTF_COMPLETE cbprintf_complete.c)
zephyr_sources_ifdef(CONFIG_CBPRINTF_NANO cbprintf_nano.c)
lib/os: Replace cbvprintf and printfcb family when using picolibc Picolibc already provides the functionality offered by cbprintf, so there's no reason to use the larger and less functional version included in zephyr. Signed-off-by: Keith Packard <keithp@keithp.com>
2021-10-20 12:49:15 +08:00
if(NOT CONFIG_PICOLIBC)
zephyr_sources(cbprintf.c)
endif()
debug: Revert ASSERT options dependency f4df23c9 added dependency on ASSERT to some options prefixed with ASSERT_ assuming that they are no used elsewhere. Turned out that there are subsystem specific assert macros (e.g. BT_ASSERT) which relies on those options. Removing the dependency. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2022-03-25 16:40:29 +08:00
if (CONFIG_ASSERT OR CONFIG_ASSERT_VERBOSE)
zephyr_sources(assert.c)
endif()
kernel: remove old work queue implementation Now that the old API has been reimplemented with the new API remove the old implementation and its tests. Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no>
2020-11-25 06:47:47 +08:00
zephyr_sources_ifdef(CONFIG_USERSPACE mutex.c user_work.c)
lib/os: P4 Work Queue: Pooled Parallel Preemptible Priority-based This adds a somewhat special purpose IPC mechanism. It's intended for applications which have a "work queue" like architecture of discrete callback items, but which need the ability to schedule those items independently in separate threads across multiple CPUs. So P4 Work items: 1. Can run at any Zephyr scheduler priority and with any deadline (this feature assumes EDF scheduling is enabled) 2. Can be submitted at any time and from any context, including being resubmitted from within their own handler. 3. Will preempt any lower priority work as soon as they are runnable, according to the standard rules of Zephyr priority scheduling. 4. Run from a pool of worker threads that can be allocated efficiently (i.e. you need as many as the number of CPUs plus the number of preempted in-progress items, but no more). Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2020-07-29 04:14:23 +08:00
lib: os: Add mpsc (multiple producer, single consumer) packet buffer Added module for storing variable length packets in a ring buffer. Implementation assumes multiple producing contexts and single consumer. API provides zero copy functionality with alloc, commit, claim, free scheme. Additionally, there are functions optimized for storing single word packets and packets consisting of a word and a pointer. Buffer can work in two modes: saturation or overwriting the oldest packets when buffer has no space to allocate for a new buffer. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2021-01-14 14:59:52 +08:00
zephyr_sources_ifdef(CONFIG_MPSC_PBUF mpsc_pbuf.c)
lib: os: Rename icmsg_buf to spsc_pbuf Move icmsg_buf to lib/os and rename to spsc_pbuf (Single Producer Single Consumer Packet Buffer). It is a generic module and initially was created as internal module for ipc service. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2022-05-17 21:49:59 +08:00
zephyr_sources_ifdef(CONFIG_SPSC_PBUF spsc_pbuf.c)
lib/os: P4 Work Queue: Pooled Parallel Preemptible Priority-based This adds a somewhat special purpose IPC mechanism. It's intended for applications which have a "work queue" like architecture of discrete callback items, but which need the ability to schedule those items independently in separate threads across multiple CPUs. So P4 Work items: 1. Can run at any Zephyr scheduler priority and with any deadline (this feature assumes EDF scheduling is enabled) 2. Can be submitted at any time and from any context, including being resubmitted from within their own handler. 3. Will preempt any lower priority work as soon as they are runnable, according to the standard rules of Zephyr priority scheduling. 4. Run from a pool of worker threads that can be allocated efficiently (i.e. you need as many as the number of CPUs plus the number of preempted in-progress items, but no more). Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2020-07-29 04:14:23 +08:00
zephyr_sources_ifdef(CONFIG_SCHED_DEADLINE p4wq.c)
power: move reboot functionality to os lib Reboot functionality has nothing to do with PM, so move it out to the subsys/os folder. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2021-04-27 17:56:39 +08:00
zephyr_sources_ifdef(CONFIG_REBOOT reboot.c)
lib: os: add support for system power off Add a new API to perform an immediate system power off: `sys_poweroff()`. Until now, this functionality has been implemented via the system power management module, but in a clunky fashion. The way system PM works is by defining some idle states in devicetree, that, given some properties (e.g. minimal residency, exit latency, etc.) are automatically selected when system goes to idle based on the expected next wake-up. However, system off is a power state that one typically wants to control manually from the application because it implies state loss, and in most cases, configuring some sort of wake-up source. So in general, it is not desired to let the system enter this state automatically. This led to the following stuff in-tree: from `boards/arm/mimxrt595_evk/mimxrt595_evk_cm33.dts`: ```c /* * Deep power-down mode is supported in this SoC through * 'PM_STATE_SOFT_OFF' state. There is no entry for this in device tree, * user can call pm_state_force to enter this state. */ ``` That is, state not being defined in devicetree so that PM subsystem doesn't pick it automatically, but still implemented in in the PM hooks: from `soc/arm/nxp_imx/rt5xx/power.c`, `pm_state_set()`: ```c case PM_STATE_SOFT_OFF: set_deepsleep_pin_config(); POWER_EnterDeepPowerDown(EXCLUDE_FROM_DEEP_POWERDOWN); break; ``` And to actually make use of this state, users had to do this kind of abominations: ```c pm_state_force(0u, &(struct pm_state_info){ PM_STATE_SOFT_OFF, 0, 0 }); /* Now we need to go sleep. This will let the idle thread runs and * the pm subsystem will use the forced state. To confirm that the * forced state is used, lets set the same timeout used previously. */ k_sleep(K_SECONDS(SLEEP_S)); printk("ERROR: System off failed\n"); while (true) { /* spin to avoid fall-off behavior */ } ``` Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2023-07-20 17:46:41 +08:00
zephyr_sources_ifdef(CONFIG_POWEROFF poweroff.c)
lib/os: P4 Work Queue: Pooled Parallel Preemptible Priority-based This adds a somewhat special purpose IPC mechanism. It's intended for applications which have a "work queue" like architecture of discrete callback items, but which need the ability to schedule those items independently in separate threads across multiple CPUs. So P4 Work items: 1. Can run at any Zephyr scheduler priority and with any deadline (this feature assumes EDF scheduling is enabled) 2. Can be submitted at any time and from any context, including being resubmitted from within their own handler. 3. Will preempt any lower priority work as soon as they are runnable, according to the standard rules of Zephyr priority scheduling. 4. Run from a pool of worker threads that can be allocated efficiently (i.e. you need as many as the number of CPUs plus the number of preempted in-progress items, but no more). Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2020-07-29 04:14:23 +08:00
zephyr_library_include_directories(
${ZEPHYR_BASE}/kernel/include
${ZEPHYR_BASE}/arch/${ARCH}/include
)