Skip to content
Snippets Groups Projects
  1. Dec 22, 2019
    • rahix's avatar
      chore(hw-locks): Rename to hwlock_acquire_timeout · 610a3048
      rahix authored
      
      Rename hwlock_acquire() to hwlock_acquire_timeout() in preparation for
      future changes to the hw-lock API.  Change all uses of the hw-lock API
      to reflect this change.
      
      This commit does not introduce any functional changes, except getting
      rid of the timeout usage warnings.  This change is no-op, because the
      hwlock_acquire() implementation already replaces any non-zero timeout
      value with portMAX_DELAY.
      
      Signed-off-by: default avatarRahix <rahix@rahix.de>
      610a3048
    • rahix's avatar
      feat(hw-locks): hwlock_release() should return void · 18202736
      rahix authored
      
      With the switch to the new mutex API, hwlock_release() cannot fail under
      any circumstances.  To emphasize this, make it return void instead of
      int (Previously it just always returned 0).
      
      Signed-off-by: default avatarRahix <rahix@rahix.de>
      18202736
    • rahix's avatar
      feat(hw-locks): Switch to new mutex API · d93c7f00
      rahix authored
      
      Reimplement the hw-lock module to use the new mutex API.  This slightly
      changes the semantics of locking a hw-lock as the new mutex API does not
      allow timeouts.  When a hwlock_acquire() with a (non-infinite) timeout
      is attempted, a warning is printed to the serial console.
      
      Additionally, instead of returning -EINVAL on use of a non-existent
      hardware lock, the new implementation triggers a firmware panic.
      
      Signed-off-by: default avatarRahix <rahix@rahix.de>
      d93c7f00
  2. Dec 21, 2019
  3. Dec 10, 2019
  4. Dec 09, 2019
  5. Dec 06, 2019
Loading