Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Look at Zephyr I2C API #6

Open
Zelzahn opened this issue Apr 16, 2024 · 1 comment
Open

Look at Zephyr I2C API #6

Zelzahn opened this issue Apr 16, 2024 · 1 comment

Comments

@Zelzahn
Copy link
Collaborator

Zelzahn commented Apr 16, 2024

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.

@sunfishcode
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants