I2C design
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 46
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
First of all I fixed badly designed mutex handling in commit: qermit/afcipm@49c59599dfea6070e974c0da5043facc325b8272
It was to prevent other tasks changing this shared structure.
I've also introduced a initial i2c multiplexer handling.
In this case memory copy is just waist of resources and limits usage of I2C bus function in a master mode. Just pointer to rx/tx data shall be assigned while only one task may take ownership over I2C bus.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing commit qermit/afcipm@49c59599dfea6070e974c0da5043facc325b8272, which contains the mutex-handling changes described here. Trace the shared structure and I2C master-mode ownership assumptions, then determine how the proposed pointer-based transfers and multiplexer handling should be validated; the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100