Remove unnessary calls to up_mdelay in sensors
- Dominant language
- C
- Stars
- 4k
- Forks
- 1.7k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 230
Description
We have a lot of calls to `up_mdelay` in the sensor drivers. There are other places that this is an issue as well.
Generally if we do not need a small critical time we should not be using this. I would suggest that most uses of up_mdelay are likely wrong, `up_usleep` is more likely in places that it is actually required.
This causes poor system performance and does not play nicely with the simulator.
Contributor guide
Research direction
Start by searching the sensor drivers and other uses of up_mdelay, then compare each delay's purpose with the issue's guidance about up_usleep. Done means unnecessary calls are removed or changed where appropriate without breaking required timing, system performance, or simulator behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, operating-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100