Lines Matching +full:no +full:- +full:eeprom
5 by Wolfram Sang <wsa@sang-engineering.com> in 2014-15
10 example for the latter is the slave-eeprom driver, which acts as a dual memory
12 EEPROM, the Linux I2C slave can access the content via sysfs and handle data as
16 use a character device, be in-kernel only, or something completely different::
20 +-----------+ v +---------+ v +--------+ v +------------+
21 | Userspace +........+ Backend +-----------+ Driver +-----+ Controller |
22 +-----------+ +---------+ +--------+ +------------+
24 ----------------------------------------------------------------+-- I2C
25 --------------------------------------------------------------+---- Bus
35 them as described in the document instantiating-devices.rst. The only
38 instantiating the slave-eeprom driver from userspace at the 7 bit address 0x64
41 # echo slave-24c02 0x1064 > /sys/bus/i2c/devices/i2c-1/new_device
56 ----------------
131 -----------------
140 Check the i2c-slave-eeprom driver as an example.
144 ------------------
162 Check the i2c-rcar driver as an example.
166 --------------
172 automatically ACK when detecting their slave addresses, so there is no option
176 Currently, there is no slave event to report if the master did ACK or NACK a
184 -------------
190 * Buffers should be opt-in and backend drivers will always have to support
191 byte-based transactions as the ultimate fallback anyhow because this is how
201 error-prone.