| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
allow consumers of iicbus_transfer() to send messages with repeated starts.
Reviewed by: imp
|
|
|
|
|
|
|
| |
upcoming i2c(8) diag utility.
Reviewed by: bms, stas
Obtained from: Semihalf
|
|
|
|
|
|
| |
seems like a good idea.
Submitted by: sam
|
|
|
|
|
|
|
|
|
| |
forcing all transfers to do the start read/write stop by hand. Some
smart bridges prefer this sort of operation, and this allows us to
support their features more easily. When bridges don't support it, we
fall back to using the old-style opertaions. Expand the ioctl
interface to expose this function. Unlike the old-style interface,
this interface is thread safe, even on old bridges.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
devices dynamically. That means,
+ only one /dev/iic or /dev/smb device for each smb/iic bus to access
+ I2C/SMB device address must be given to any ioctl
+ new devices may be plugged and accessed after boot, which was
impossible previously (device addresses were hardcoded into
the kernel)
|
|
Submitted by: nsouch
I2C and SMB ioctls
|