Port bhi160 to new locks & fix initialization behavior
- Dec 29, 2019
-
-
rahix authoredThe orientation sensor uses a different axis mapping than the other sensors. Document this. Signed-off-by:
Rahix <rahix@rahix.de> -
rahix authored
Don't open all 4 virtual sensors all time time; only open the one which is actually displayed. This prevents the storm of queue-full message on the serial terminal. Signed-off-by:Rahix <rahix@rahix.de> -
rahix authored
If initialization fails, bhi160 API calls should not infinitely block waiting for it to complete; they should fail immediately with an error stating that something went wrong. Add a flag that indicates the driver to not accept API requests because initialization was not finished properly. Signed-off-by:Rahix <rahix@rahix.de>
-
- Dec 28, 2019
-
-
rahix authored
As discussed in issue #133, the BHI160 changes its interrupt behavior during initialization. In commit 2f56ff36 ("fix(bhi160): Call bhy_mapping_matrix_set twice for the first time") a quick workaround for this issue was added. Replace this hack with a proper fix by reconfiguring the interrupt on the host side according to the specification. (Finally) fixes #133. Fixes: 2f56ff36 ("fix(bhi160): Call bhy_mapping_matrix_set twice for the first time") Link: https://git.card10.badge.events.ccc.de/card10/firmware/issues/133#note_5894 Signed-off-by:
Rahix <rahix@rahix.de> -
rahix authored
Port the bhi160 mutex and hwlock usage in bhi.c to the new mutex API. This will hopefully increase system stability. Signed-off-by:Rahix <rahix@rahix.de>
-