zephyr/lib/os/CMakeLists.txt

zephyr_sources_if_kconfig(base64.c)

zephyr_sources(
  crc32_sw.c
  crc16_sw.c
  crc8_sw.c
  crc7_sw.c
  fdtable.c
  mempool.c
  rb.c
  thread_entry.c
  work_q.c
  )

zephyr_sources_ifdef(CONFIG_JSON_LIBRARY json.c)

zephyr_sources_if_kconfig(printk.c)

zephyr_sources_if_kconfig(ring_buffer.c)

zephyr_sources_ifdef(CONFIG_ASSERT assert.c)

zephyr_sources_ifdef(CONFIG_USERSPACE mutex.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			`zephyr_sources_if_kconfig(base64.c)`

			`zephyr_sources(`
			`crc32_sw.c`
			`crc16_sw.c`
			`crc8_sw.c`
			`crc7_sw.c`
			`fdtable.c`
			`mempool.c`
			`rb.c`
			`thread_entry.c`
			`work_q.c`
			`)`

			`zephyr_sources_ifdef(CONFIG_JSON_LIBRARY json.c)`

printk: move into lib/os Last file under misc/. Put it alongside other support functions in lib/os. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-01-19 20:04:48 +08:00			`zephyr_sources_if_kconfig(printk.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			`zephyr_sources_if_kconfig(ring_buffer.c)`
misc: Add k_panic on assert Replaced forever loop in assert with call to a function. In post_assert_action() function, k_panic is called. Forever loop was preventing logs to be printed and had behavior ependent on the context (low prioriy thread - system continue to ork, irq - system is blocked). Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no> 2019-01-25 20:56:10 +08:00
			`zephyr_sources_ifdef(CONFIG_ASSERT assert.c)`
lib: os: add sys_mutex data type For systems without userspace enabled, these work the same as a k_mutex. For systems with userspace, the sys_mutex may exist in user memory. It is still tracked as a kernel object, but has an underlying k_mutex that is looked up in the kernel object table. Future enhancements will optimize sys_mutex to not require syscalls for uncontended sys_mutexes, using atomic ops instead. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com> 2019-03-28 06:44:52 +08:00
			`zephyr_sources_ifdef(CONFIG_USERSPACE mutex.c)`