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_v1/Kconfig

71 lines
1.9 KiB
Plaintext
Raw Normal View History

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
#
# Copyright (c) 2018 Intel Corporation
#
# SPDX-License-Identifier: Apache-2.0
#
config CMSIS_RTOS_V1
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
bool "CMSIS RTOS v1 API"
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
default n
help
This enables CMSIS RTOS v1 API support. This is an OS-integration
layer which allows applications using CMSIS RTOS APIs to build on
Zephyr.
if CMSIS_RTOS_V1
lib/cmsis_rtos_v1: Implement support for Signal Event APIs Signals are used to trigger execution states between threads. These APIs provide functionalities like signal set, clear and wait. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-08-02 18:39:39 +08:00
config THREAD_CUSTOM_DATA
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
bool "Thread custom data"
lib/cmsis_rtos_v1: Implement support for Signal Event APIs Signals are used to trigger execution states between threads. These APIs provide functionalities like signal set, clear and wait. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-08-02 18:39:39 +08:00
default y
help
This option allows each thread to store 32 bits of custom data,
which can be accessed using the k_thread_custom_data_xxx() APIs.
config POLL
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
bool "Async I/O Framework"
lib/cmsis_rtos_v1: Implement support for Signal Event APIs Signals are used to trigger execution states between threads. These APIs provide functionalities like signal set, clear and wait. Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2018-08-02 18:39:39 +08:00
default y
help
Asynchronous notification framework. Enable the k_poll() and
k_poll_signal() APIs. The former can wait on multiple events
concurrently, which can be either directly triggered or triggered by
the availability of some kernel objects (semaphores and fifos).
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
config CMSIS_MAX_THREAD_COUNT
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
int "Maximum thread count in CMSIS RTOS application"
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
default 10
range 0 255
help
Mention max number of threads in CMSIS RTOS compliant application.
There's a limitation on the number of threads due to memory
related constraints.
config CMSIS_THREAD_MAX_STACK_SIZE
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
int "Max stack size threads can be allocated in CMSIS RTOS application"
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
default 512
help
Mention max stack size threads can be allocated in CMSIS RTOS application.
lib/cmsis_rtos_v1: 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-06-19 15:03:12 +08:00
config CMSIS_TIMER_MAX_COUNT
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
int "Maximum timer count in CMSIS application"
lib/cmsis_rtos_v1: 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-06-19 15:03:12 +08:00
default 5
range 0 255
help
Mention maximum number of timers in CMSIS compliant application.
lib/cmsis_rtos_v1: 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-07-06 18:14:11 +08:00
config CMSIS_MUTEX_MAX_COUNT
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
int "Maximum mutex count in CMSIS application"
lib/cmsis_rtos_v1: 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-07-06 18:14:11 +08:00
default 5
range 0 255
help
Mention maximum number of mutexes in CMSIS compliant application.
lib/cmsis_rtos_v1: 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-07-09 18:13:28 +08:00
config CMSIS_SEMAPHORE_MAX_COUNT
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
int "Maximum semaphore count in CMSIS application"
lib/cmsis_rtos_v1: 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-07-09 18:13:28 +08:00
default 5
range 0 255
help
Mention maximum number of semaphores in CMSIS compliant application.
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
config NUM_PREEMPT_PRIORITIES
int
default 7
endif