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.

Sign up for GitHub

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

Jump to bottom

x/exp/io/i2c: flush after write #16155

Closed
rakyll opened this issue Jun 22, 2016 · 3 comments
Closed

x/exp/io/i2c: flush after write #16155

rakyll opened this issue Jun 22, 2016 · 3 comments
Labels
FrozenDueToAge
Milestone
Unreleased

Comments

@rakyll
Copy link
Contributor

rakyll commented Jun 22, 2016 •
edited

Devfs implementations of the drivers need to flush after writes. Otherwise, for a significant amount of time you don't see the write buffer is being flushed. Critical for protocols depend on small chunk of byte writes such as i2c and SPI where timing is critical.
@rakyll rakyll added this to the Unreleased milestone Jun 22, 2016
@rakyll rakyll self-assigned this Jun 22, 2016
@rakyll rakyll changed the title x/exp/io/i2c, x/exp/io/spi: flush after write x/exp/io/i2c: flush after write Jun 29, 2016
@gopherbot
Copy link

CL https://golang.org/cl/24601 mentions this issue.

@gopherbot
Copy link

CL https://golang.org/cl/24583 mentions this issue.

@gopherbot
Copy link

CL https://golang.org/cl/24584 mentions this issue.

@golang golang locked and limited conversation to collaborators Jun 30, 2017
@rsc rsc unassigned rakyll Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
2 participants
@rakyll @gopherbot