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
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: