Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cross-platform inconsistency in I2C bus speeds #24067

Closed
pabigot opened this issue Apr 3, 2020 · 2 comments · Fixed by #24159
Closed

cross-platform inconsistency in I2C bus speeds #24067

pabigot opened this issue Apr 3, 2020 · 2 comments · Fixed by #24159
Assignees
Labels
area: I2C bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@pabigot
Copy link
Collaborator

pabigot commented Apr 3, 2020

The I2C bus specification in section 5 specifies these named speeds:

  • Standard up to 100 kHz
  • Fast up to 400 kHz
  • Fast+ up to 1 MHz
  • High up to 3.4 MHz
  • Ultra up to 5 MHz (unidirectional only)

Evaluation in #23971 (review) plus code review show that NXP (mcux, mcux_lpi2c, imx) and SiLabs (gecko) I2C drivers use 1 MHz for Fast, and do not implement Fast+.

The interpretation of named I2C bus speeds in Zephyr should be (a) documented and (b) consistent.

@pabigot pabigot added the bug The issue is a bug, or the PR is fixing a bug label Apr 3, 2020
@carlescufi carlescufi added area: I2C priority: low Low impact/importance bug labels Apr 7, 2020
@carlescufi
Copy link
Member

@mnkp and @MaureenHelm could you send a patch to correct Fast so it becomes Fast+?

@MaureenHelm
Copy link
Member

@mnkp and @MaureenHelm could you send a patch to correct Fast so it becomes Fast+?

yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: I2C bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants