sonic-net / sonic-net/sonic-linux-kernel
Problems encountered by i2c-ismt drivers
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 72
- Forks
- 237
- Avg merge
- 7d 19h
- Merged PRs (30d)
- 8
Description
Code Path：drivers/i2c/busses/i2c-ismt.c
Issue：An occasional I2C deadlock(SCL is high voltage level and SDA is low voltage level) cannot be recovered, making the I2C controller unusable.
Regarding this issue, our solution is:
The solution is the same as the i2c-i801 driver, which also imports 9 clock unlock functions
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
Read drivers/i2c/busses/i2c-ismt.c and compare its recovery path with the i2c-i801 driver, focusing on the proposed nine clock-unlock functions. Done means the occasional I2C deadlock, where SCL is high and SDA is low, can be recovered without leaving the controller unusable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100