The current async interface targets an I2C Master.
Hereby I propose to also create an async interface for an I2C slave device.
It would be nice that the length of on incoming message is flexible, (controlled by the master, not by the slave).
The slave does get a buffer from the software, big enough to contain all possible incoming messages.
If the master does send more than the size of the buffer, an error is raised.
At the end of an I2C message, the actual length of the received bytes, and the actual slave address should be reported to the software.
The current async interface targets an I2C Master.
Hereby I propose to also create an async interface for an I2C slave device.
It would be nice that the length of on incoming message is flexible, (controlled by the master, not by the slave). The slave does get a buffer from the software, big enough to contain all possible incoming messages. If the master does send more than the size of the buffer, an error is raised. At the end of an I2C message, the actual length of the received bytes, and the actual slave address should be reported to the software.