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

x/exp/io/i2c: Devfs should not use read() and write() calls #15264

Open
rakyll opened this Issue Apr 12, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@rakyll
Copy link
Member

rakyll commented Apr 12, 2016

Only a subset of the I2C and SMBus protocols can be implemented by using read() and write() calls, e.g. full duplex transmission is not supported. Most user-space programs directly depend on the I2C driver functions.

See i2c_smbus_read_word_data and i2c_smbus_write_word_data at the kernel driver reference (https://www.kernel.org/doc/Documentation/i2c/dev-interface).

@rakyll rakyll self-assigned this Apr 12, 2016

@rakyll rakyll added this to the Unreleased milestone Apr 12, 2016

@rakyll rakyll changed the title exp/io/i2c: Devfs should not use read() and write() calls x/exp/io/i2c: Devfs should not use read() and write() calls Apr 12, 2016

@gopherbot

This comment has been minimized.

Copy link

gopherbot commented Apr 13, 2016

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

gopherbot pushed a commit to golang/exp that referenced this issue Apr 19, 2016

io/i2c: depend on ioctl calls to read/write
Tested with a Grove-LCD RGB Backlight.

Updates golang/go#15264.

Change-Id: Iba3653de83c2355686674907ee93bed0cb17a663
Reviewed-on: https://go-review.googlesource.com/21960
Reviewed-by: Minux Ma <minux@golang.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.