1. 27 Jan, 2020 2 commits
  2. 24 Jan, 2020 6 commits
  3. 20 Jan, 2020 2 commits
  4. 09 Jan, 2020 1 commit
  5. 05 Jan, 2020 1 commit
  6. 04 Jan, 2020 1 commit
  7. 03 Jan, 2020 3 commits
  8. 02 Jan, 2020 1 commit
  9. 31 Dec, 2019 1 commit
    • Rahix's avatar
      revert(bhi160): Re-add hack to fix axis mapping · 448ec494
      Rahix authored
      Originally, commit 1a3dfad3 ("fix(bhi160): Fix interrupt behavior
      during initialization") was supposed to fix the BHI160 axis-mapping
      issue (see #133) but apparently on some devices it still
      needs the original hack to work.  Revert the removal of the axis-mapping
      hack from commit 2f56ff36 ("fix(bhi160): Call bhy_mapping_matrix_set
      twice for the first time").
      
      Fixes: 1a3dfad3 ("fix(bhi160): Fix interrupt behavior during initialization")
      Link: #133
      
      
      Signed-off-by: Rahix's avatarRahix <rahix@rahix.de>
      448ec494
  10. 30 Dec, 2019 2 commits
  11. 29 Dec, 2019 14 commits
  12. 28 Dec, 2019 3 commits
  13. 26 Dec, 2019 2 commits
  14. 22 Dec, 2019 1 commit
    • Rahix's avatar
      Merge 'Port hardware locks to new mutex API' · b46a9e7a
      Rahix authored
      Move hw-locks to new mutex API in multiple steps to keep diffs readable.  The
      users of hw-locks are **not** ported to the new-semantics; this needs to be
      done as a follow up.  One patch is included, porting the MAX30001 driver in
      commit 6da4644e ("chore(max30001): Port to new mutex and hw-lock APIs").
      
      See merge request card10/firmware!356
      b46a9e7a