Lock using TryLock

[Hadatko]

Signed-off-by: Cervenka Dusan cervenka@acrios.com

Prerequisites

• [X] I have checked latest main branch and the issue still exists.
• [X] I did not see it is stated as known-issue in release notes.
• [X] No similar GitHub issue is related to this change.
• [X] My code follows the commit guidelines of this project.
• [X] I have performed a self-review of my own code.
• [X] My changes generate no new warnings.
• [ ] I have added tests that prove my fix is effective or that my feature works.

Describe the pull request

I am just curious if there is a reason why not to use trylock in loop for lock implementation. TryLock and Lock looked to me a bit inconsistent.

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Tests

• Test configuration (please complete the following information):
  • Hardware setting:
  • Toolchain:
  • Test Tool preparation:
  • Any other dependencies:
• Test executed Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
  • [ ] Build Test
  • [ ] Run Test

[Hadatko]

If implementation of TryLock is not an issue then why not use it for Lock implementation?