portability: cmsis: Clarify Kconfig set max limit on dynamic objects
Clarify that all max limit on RTOS objects set by Kconfig only apply to objects whose control blocks were dynamically allocated. The CMSIS-RTOSv2 impl layer itself does not restrict the number of statically created RTOS objects. Signed-off-by: Utsav Munendra <utsavm@meta.com>
This commit is contained in:
parent
c006922b22
commit
9379c35dbf
2 changed files with 30 additions and 12 deletions
|
@ -186,4 +186,16 @@ ZTEST(cmsis_mutex, test_mutex_static_allocation)
|
|||
|
||||
zassert_true(osMutexDelete(id) == osOK, "osMutexDelete failed");
|
||||
}
|
||||
|
||||
ZTEST(cmsis_mutex, test_mutex_static_multiple_new)
|
||||
{
|
||||
osMutexId_t id;
|
||||
|
||||
for (int i = 0; i < 100; ++i) {
|
||||
id = osMutexNew(&mutex_attrs2);
|
||||
zassert_not_null(id, "Failed creating mutex using static cb");
|
||||
|
||||
zassert_true(osMutexDelete(id) == osOK, "osMutexDelete failed");
|
||||
}
|
||||
}
|
||||
ZTEST_SUITE(cmsis_mutex, NULL, NULL, NULL, NULL, NULL);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue