Lines Matching refs:slave

1 Linux I2C slave interface description
6 Linux can also be an I2C slave if the I2C controller in use has slave
7 functionality. For that to work, one needs slave support in the bus driver plus
9 example for the latter is the slave-eeprom driver, which acts as a dual memory
11 EEPROM, the Linux I2C slave can access the content via sysfs and handle data as
18               e.g. sysfs        I2C slave events        I/O registers
33 I2C slave backends behave like standard I2C clients. So, you can instantiate
35 is that i2c slave backends have their own address space. So, you have to add
37 instantiating the slave-eeprom driver from userspace at the 7 bit address 0x64
40   # echo slave-24c02 0x1064 > /sys/bus/i2c/devices/i2c-1/new_device
54 I2C slave events
61 'client' describes the i2c slave device. 'event' is one of the special event
127 * write the slave_callback which handles the above slave events
131 Check the i2c-slave-eeprom driver as an example.
137 If you want to add slave support to the bus driver:
139 * implement calls to register/unregister the slave and add those to the
141   slave address and enable slave specific interrupts. If you use runtime pm, you
143   on always to be able to detect its slave address. When unregistering, do the
146 * Catch the slave interrupts and send appropriate i2c_slave_events to the backend.
158 automatically ACK when detecting their slave addresses, so there is no option
162 Currently, there is no slave event to report if the master did ACK or NACK a
176 * Buffers should be opt-in and slave drivers will always have to support