This is a different way to implement the same functionality as read_device_registers() and write_device_register() when scheduling multiple read/write operations on the same device.
In addition it's now possible to perform read and write operations while holding the same lock. This was not possible with read_device_registers() and write_device_register() and is expected to improve usability and robustness.
However it is not possible to use feeph.i2c.BurstHandler() to schedule multiple read/write operations on different devices. This regression was a conscious choice in favor of a more convenient interface.
This is a different way to implement the same functionality as
read_device_registers()andwrite_device_register()when scheduling multiple read/write operations on the same device.read_device_registers()andwrite_device_register()and is expected to improve usability and robustness.feeph.i2c.BurstHandler()to schedule multiple read/write operations on different devices. This regression was a conscious choice in favor of a more convenient interface.