1. 10 Nov, 2019 4 commits
  2. 09 Nov, 2019 4 commits
  3. 03 Nov, 2019 6 commits
    • Rahix's avatar
      chore(fatfs): Port to new mutex API · 86c7418a
      Rahix authored
      Using a bare FreeRTOS mutex is deprecated.  Replace it with the new
      `struct mutex`.  This should increase stability of the module.  In the
      process of switching, also remove the `EPIC_FAT_STATIC_SEMAPHORE` define
      as it is no longer needed with the new mutex API.
      Signed-off-by: Rahix's avatarRahix <rahix@rahix.de>
      86c7418a
    • Rahix's avatar
      chore(api-lock): Port to new mutex API · 75278836
      Rahix authored
      Using a bare FreeRTOS mutex is deprecated.  Replace it with the new
      `struct mutex`.  This should increase stability.
      
      Additionally, fix a bug in `lifecycle.c:do_load()` where the function
      would return without unlocking the API mutex if `hardware_reset()`
      returns an error.
      Signed-off-by: Rahix's avatarRahix <rahix@rahix.de>
      75278836
    • Rahix's avatar
      chore(sensor-streams): Port to new mutex API · 44ea81f2
      Rahix authored
      Using a bare FreeRTOS mutex is deprecated.  Replace it with the new
      `struct mutex`.  This should increase stability of the module.
      Signed-off-by: Rahix's avatarRahix <rahix@rahix.de>
      44ea81f2
    • Rahix's avatar
      chore(lifecycle): Port to new mutex API · cc5f0e29
      Rahix authored
      Using a bare FreeRTOS mutex is deprecated.  Replace it with the new
      `struct mutex`.  This should increase stability of the module.
      Signed-off-by: Rahix's avatarRahix <rahix@rahix.de>
      cc5f0e29
    • Rahix's avatar
      feat(epicardium): Add a proper mutex implementation · 9a5a46cd
      Rahix authored
      In the current firmware, different locking mechanisms a littered around
      the code-base.  Among them are bare FreeRTOS mutexes and the hw-locks.
      The callers for these often specify timeouts but don't make much effort
      in A) picking robust values for the timeout and B) recovering gracefully
      from a timeout happening.  Most of the time, we return -EBUSY to _Python
      code_.  This is really really bad API design.  The firmware needs to
      have enough integrity to ensure these situations can't ever occur.
      
      To combat this, add a new locking primitive: The `struct mutex`.  The
      intention is to replace all other locking and synchronization APIs with
      this one.  This will provide one central place to debug any sort of
      locking issues.
      
      The `struct mutex` API is based on a few assumptions about locking.
      Those are detailed in `Documentation/epicardium/mutex.rst`, which is
      part of this commit.  The most important one is:
      
          Locking can **never** fail.
      
      By requiring this to be true, we eliminate the need for drivers to
      contain (often incorrect) logic for dealing with locking fails.  This
      should drastically improve the stability of the firmware in regards to
      lock-related bugs.
      
      This commit does not introduce any functional changes yet.
      Signed-off-by: Rahix's avatarRahix <rahix@rahix.de>
      9a5a46cd
    • Rahix's avatar
      Merge 'Super basic ECG log plotter' · c7e40e27
      Rahix authored
      See merge request !333
      c7e40e27
  4. 02 Nov, 2019 2 commits
  5. 23 Oct, 2019 3 commits
  6. 22 Oct, 2019 1 commit
  7. 19 Oct, 2019 3 commits
  8. 18 Oct, 2019 8 commits
  9. 10 Oct, 2019 1 commit
  10. 09 Oct, 2019 1 commit
  11. 06 Oct, 2019 4 commits
  12. 05 Oct, 2019 3 commits