> - If I understand correctly you cannot register an i2c slave without > also registering a master, right? I don't think this is troubling in > practice, is it? > For abstraction I would prefer to make these different concepts > though.
You need to register an adapter, yes. It does not need to populate the callback for sending messages, so it could be slave only. But an adapter is needed, because it is the glue between a client and the wired lines. > - The IMHO most (even only?) useful slave is "i2cslvdev", i.e. a > userspace device. With that you wouldn't need device tree stuff, the > driver would just offer the device if supported. Userspace then could > care about the rest (slave address, functionality, ...). I don't think it is the only useful one. A callback into userspace is expensive, so stuff like shared memory (my eeprom simulator) or a shared ringbuffer will come in handy, too. That being said, a slave device like you described is probably the next user we see using the slave interface :)
signature.asc
Description: Digital signature
