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

105 lines
3.2 KiB
Plaintext
Raw Normal View History

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
# Copyright (c) 2018 Intel Corporation
# SPDX-License-Identifier: Apache-2.0
kconfig: Clean up header comments and make them consistent Use this short header style in all Kconfig files: # <description> # <copyright> # <license> ... Also change all <description>s from # Kconfig[.extension] - Foo-related options to just # Foo-related options It's clear enough that it's about Kconfig. The <description> cleanup was done with this command, along with some manual cleanup (big letter at the start, etc.) git ls-files '*Kconfig*' | \ xargs sed -i -E '1 s/#\s*Kconfig[\w.-]*\s*-\s*/# /' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 20:45:29 +08:00
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
config CMSIS_RTOS_V2
bool "CMSIS RTOS v2 API"
depends on POLL
depends on THREAD_NAME
depends on THREAD_STACK_INFO
depends on THREAD_MONITOR
depends on INIT_STACKS
lib: cmsis_rtos_v2: Additional Kconfig dependency Added Kconfig dependency that NUM_PREEMPT_PRIORITIES must be at least osPriorityISR (56). This was enforced by a build assert message but not decribed in the Kconfig. Signed-off-by: Carlos Stuart <carlosstuart1970@gmail.com>
2019-02-06 16:10:54 +08:00
depends on NUM_PREEMPT_PRIORITIES >= 56
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
help
This enables CMSIS RTOS v2 API support. This is an OS-integration
layer which allows applications using CMSIS RTOS V2 APIs to build
on Zephyr.
if CMSIS_RTOS_V2
config CMSIS_V2_THREAD_MAX_COUNT
int "Maximum thread count in CMSIS RTOS V2 application"
default 15
range 0 255
help
Mention max number of threads in CMSIS RTOS V2 compliant application.
There's a limitation on the number of threads due to memory
related constraints.
lib: cmsis_rtos_v2: Dynamic thread stacks Implemented dynamic thread stacks for CMSIS threads by declaring an array of default sized thread stacks. Allocation cannot be done on the heap as some architectures require strict alignment for stacks so the macro must be used to define the stack to ensure most compatibility. Added a Kconfig variable to limit the number of dynamic threads on the system (they also count towards total CMSIS thread count). This is so a developer can have fine grained control over how many dynamic threads can be allocated because all their stacks must be allocated up front so could use a lot of memory needlessly if oversubscribed. The default value is 0 which effectively disabled dynamic threads but also reduces the memory impact to almost none. Fixed an assert bug where thread_num was being tested against the maximum allowed CMSIS threads - it previous checked for less than or equal which actually (due to when the increment happens) allowed there to be one more thread. The check now correctly uses less than and only allowed up to the defined maximum. Signed-off-by: Carlos Stuart <carlosstuart1970@gmail.com>
2019-02-06 16:25:58 +08:00
config CMSIS_V2_THREAD_DYNAMIC_MAX_COUNT
int "Maximum dynamic thread count in CMSIS RTOS V2 application"
default 0
range 0 255
help
Mention max number of dynamic threads in CMSIS RTOS V2 compliant
application. There's a limitation on the number of threads due to memory
related constraints. Dynamic threads are a subset of all other CMSIS
threads i.e. they also count towards that maximum too.
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
config CMSIS_V2_THREAD_MAX_STACK_SIZE
int "Max stack size threads can be allocated in CMSIS RTOS V2 application"
lib: cmsis_v2: increase stack sizes if coverage Set to 4096, coverage targets have lots of RAM. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2019-05-02 23:32:02 +08:00
default 4096 if COVERAGE
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
default 512
help
Mention max stack size threads can be allocated in CMSIS RTOS V2 application.
lib/cmsis_rtos_v2: Implement support for timer APIs These APIs provide the support of virtual timers. All timers can be started, restarted, or stopped. Timers can be configured as one-shot or periodic. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:17:35 +08:00
lib: cmsis_rtos_v2: Dynamic thread stacks Implemented dynamic thread stacks for CMSIS threads by declaring an array of default sized thread stacks. Allocation cannot be done on the heap as some architectures require strict alignment for stacks so the macro must be used to define the stack to ensure most compatibility. Added a Kconfig variable to limit the number of dynamic threads on the system (they also count towards total CMSIS thread count). This is so a developer can have fine grained control over how many dynamic threads can be allocated because all their stacks must be allocated up front so could use a lot of memory needlessly if oversubscribed. The default value is 0 which effectively disabled dynamic threads but also reduces the memory impact to almost none. Fixed an assert bug where thread_num was being tested against the maximum allowed CMSIS threads - it previous checked for less than or equal which actually (due to when the increment happens) allowed there to be one more thread. The check now correctly uses less than and only allowed up to the defined maximum. Signed-off-by: Carlos Stuart <carlosstuart1970@gmail.com>
2019-02-06 16:25:58 +08:00
config CMSIS_V2_THREAD_DYNAMIC_STACK_SIZE
int "Dynamic stack size threads are allocated in CMSIS RTOS V2 application"
lib: cmsis_v2: increase stack sizes if coverage Set to 4096, coverage targets have lots of RAM. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2019-05-02 23:32:02 +08:00
default 4096 if COVERAGE
lib: cmsis_v2: set default dynamic stack size Set to same default as regular stacks. This doesn't use any extra memory until CMSIS_V2_THREAD_DYNAMIC_MAX_COUNT is set. 0 is not a valid default if that is set. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2019-05-02 23:30:29 +08:00
default 512
lib: cmsis_rtos_v2: Dynamic thread stacks Implemented dynamic thread stacks for CMSIS threads by declaring an array of default sized thread stacks. Allocation cannot be done on the heap as some architectures require strict alignment for stacks so the macro must be used to define the stack to ensure most compatibility. Added a Kconfig variable to limit the number of dynamic threads on the system (they also count towards total CMSIS thread count). This is so a developer can have fine grained control over how many dynamic threads can be allocated because all their stacks must be allocated up front so could use a lot of memory needlessly if oversubscribed. The default value is 0 which effectively disabled dynamic threads but also reduces the memory impact to almost none. Fixed an assert bug where thread_num was being tested against the maximum allowed CMSIS threads - it previous checked for less than or equal which actually (due to when the increment happens) allowed there to be one more thread. The check now correctly uses less than and only allowed up to the defined maximum. Signed-off-by: Carlos Stuart <carlosstuart1970@gmail.com>
2019-02-06 16:25:58 +08:00
help
Mention dynamic stack size threads are allocated in CMSIS RTOS V2 application.
lib/cmsis_rtos_v2: Implement support for timer APIs These APIs provide the support of virtual timers. All timers can be started, restarted, or stopped. Timers can be configured as one-shot or periodic. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:17:35 +08:00
config CMSIS_V2_TIMER_MAX_COUNT
int "Maximum timer count in CMSIS RTOS V2 application"
default 5
range 0 255
help
Mention maximum number of timers in CMSIS RTOS V2 compliant application.
lib/cmsis_rtos_v2: Implement support for mutex APIs These APIs allow creating, acquiring, releasing and deleting the mutexes. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:20:19 +08:00
config CMSIS_V2_MUTEX_MAX_COUNT
int "Maximum mutex count in CMSIS RTOS V2 application"
default 5
range 0 255
help
Mention max number of mutexes in CMSIS RTOS V2 compliant application.
lib/cmsis_rtos_v2: Implement support for semaphore APIs These APIs allow creating, acquiring, releasing and deleting of semaphores. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:23:44 +08:00
config CMSIS_V2_SEMAPHORE_MAX_COUNT
int "Maximum semaphore count in CMSIS RTOS V2 application"
default 5
range 0 255
help
Mention max number of semaphores in CMSIS RTOS V2 compliant application.
lib/cmsis_rtos_v2: Implement support for mempool APIs These APIs allow creating, allocating and freeing of mempools. Note: "Mempool" in CMSIS actually means memslabs in Zephyr. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:30:31 +08:00
config CMSIS_V2_MEM_SLAB_MAX_COUNT
int "Maximum mem slab count in CMSIS RTOS V2 application"
default 5
range 0 255
help
Mention maximum number of memory slabs in CMSIS RTOS V2 compliant application.
lib/cmsis_rtos_v2: Implement support for Message Queue APIs These APIs provide message queue functionality like create, put and get. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:35:13 +08:00
lib: cmsis_rtos_v2: Dynamic memory pools Implemented dynamic allocation of memory pools in a similar to manner to what was already implemented for message queues. Added all the same checks on size vs. maximum allowed and current heap. Added an additional Kconfig variable to define the maximum size of a dynamically allocated memory pool. Signed-off-by: Carlos Stuart <carlosstuart1970@gmail.com>
2019-02-06 16:13:37 +08:00
config CMSIS_V2_MEM_SLAB_MAX_DYNAMIC_SIZE
int "Maximum dynamic mem slab/pool size in CMSIS RTOS V2 application"
default 0
help
Mention maximum dynamic size of memory slabs/pools in CMSIS RTOS V2 compliant application.
lib/cmsis_rtos_v2: Implement support for Message Queue APIs These APIs provide message queue functionality like create, put and get. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:35:13 +08:00
config CMSIS_V2_MSGQ_MAX_COUNT
int "Maximum message queue count in CMSIS RTOS V2 application"
default 5
range 0 255
help
Mention maximum number of message queues in CMSIS RTOS V2 compliant application.
lib/cmsis_rtos_v2: Implement support for Event Flag APIs Events are used to trigger execution states between threads. These APIs provide functionalities like event set, clear and wait. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:38:17 +08:00
lib: cmsis_rtos_v2: Message queue checks Added some additional checks when creating a message queue to ensure the size of the queue does not exceed the size of the buffer passed in via the optional attributes. Added a new Kconfig option to limit the maximum size of a message queue dynamically allocated on the heap. Added a check to ensure the heap is at least large enough to hold a maximum size dynamically allocated queue. Signed-off-by: Carlos Stuart <carlosstuart1970@gmail.com>
2019-02-06 16:12:28 +08:00
config CMSIS_V2_MSGQ_MAX_DYNAMIC_SIZE
int "Maximum dynamic message queue size in CMSIS RTOS V2 application"
default 0
help
Mention maximum dynamic size of message queues in CMSIS RTOS V2 compliant application.
lib/cmsis_rtos_v2: Implement support for Event Flag APIs Events are used to trigger execution states between threads. These APIs provide functionalities like event set, clear and wait. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-10-30 15:38:17 +08:00
config CMSIS_V2_EVT_FLAGS_MAX_COUNT
int "Maximum event flags count in CMSIS RTOS V2 application"
default 5
range 0 255
help
Mention maximum number of event flags in CMSIS RTOS V2 compliant application.
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
endif