You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i2c_transfer_signal appears to be an async version of i2c_transfer, which is similar to wasi-i2c's tranasction function. I filed #8 to collect some thoughts about async.
I'm not familiar enough with this space to know how i2c_recover_bus would be used. So my question is, how does the embedded-hal ecosystem handle this, since they don't appear to have a "recover bus" operation in their API either.
Currently, the specification closely follows the one from
embedded_hal
. There are some differences with the Zephyr API documentation that I think a closer look is warranted. See i2c_transfer_signal and i2c_recover_bus.The text was updated successfully, but these errors were encountered: