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

Add more I/O blocking conditions #2

Open
Rybec opened this issue Jun 4, 2021 · 0 comments
Open

Add more I/O blocking conditions #2

Rybec opened this issue Jun 4, 2021 · 0 comments

Comments

@Rybec
Copy link
Owner

Rybec commented Jun 4, 2021

Currently users who want slow, hardware managed I/O to block, so other tasks can run, have to write their own blocking conditions. Very common types of I/O should have blocking conditions built into pyRTOS.

I need to look into how CircuitPython handles things like I2C and SPI. If they use similar APIs, it might be possible to make a single condition that works for both.

What other kinds of I/O would benefit from blocking conditions? LCD and Matrix display rendering? Do the APIs for those provide any way of checking whether a rendering operation has finished? If not, how hard would it be to add that?

These are the kinds of I/O I am aware of that might benefit from this:

  • SPI
  • I2C
  • UART
  • I2S
  • SDIO

Would higher level communication, like rendering, be included in the lower level stuff above, or would it require its own blocking conditions? If it requires its own blocking conditions, perhaps this issue should be limited to low level I/O and we should have a separate issue for higher level I/O.

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

1 participant