OpenDevicePartnership / OpenDevicePartnership/tps6699x
Replace custom long registers with device-driver
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4
- Forks
- 13
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 11
Description
As of device-driver 1.0.9 (https://github.com/diondokter/device-driver/pull/221), long registers (>128 bits) are back on the menu. We have several register definitions in the registers module only because of this bug, so we should migrate those over to the device.yaml now that they're unblocked.
Contributor guide
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 comparing the register definitions in the registers module with the existing device.yaml, focusing on registers longer than 128 bits. Identify every definition kept only because of the earlier device-driver limitation, then verify that those definitions are represented in device.yaml and no longer need custom handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100