CC3220SF-LAUNCHXL: Which behaviour is expected if a thread runs into wait due to a lock of mutex or semaphore another thread is currently owning

Part Number: CC3220SF-LAUNCHXL

Hi there,

which behaviour is expected if a thread runs into wait due to a lock of mutex or semaphore another thread is currently owning. Assume we are using the posix interface and tirtos.

Will the thread owning the lock pushed in terms of priority to complete his task as fast as possible to unlock the semaphore or mutex ?

BR,

Arnaud

  • I believe (from a brief check of the SDK's POSIX HAL sources in source/ti/posix/tirtos) that the current POSIX implementation  (at least over TIRTOS) doesn't make use of the Priority Inheritance feature of TIRTOS. Thus, priority inversion will happen - the blocked higher priority task will effectively gets his priority lowered temporarily.