You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are proprietary SPI and I2C implementations out there doesn't work with a bus and chip select number. We shouldn't force this in the driver interface.
I suggest Opener not to accept any arguments:
type Opener interface {
Open() (Conn, error)
}
The Devfs might require a bus and chip select number or the device filename.
type Devfs struct {
Bus, CS int
}
The text was updated successfully, but these errors were encountered:
Note: The problem and the suggested solution also applies to the i2c package.
rakyll
changed the title
x/exp/io/spi: Opener should not require bus and cs number
x/exp/io/spi/driver: Opener should not require bus and cs number
May 20, 2016
There are proprietary SPI and I2C implementations out there doesn't work with a bus and chip select number. We shouldn't force this in the driver interface.
I suggest Opener not to accept any arguments:
The Devfs might require a bus and chip select number or the device filename.
The text was updated successfully, but these errors were encountered: