Problems encountered by i2c-ismt drivers

Open
#346 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c

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.

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

Dominant language
Shell
Stars
72
Forks
237
Avg merge
7d 19h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sonic-net/sonic-linux-kernel

All issues in sonic-net/sonic-linux-kernel

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.