-
Notifications
You must be signed in to change notification settings - Fork 3k
Add non-blocking write function for USBCDC #7090
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
Conversation
@jorisa There's feature usb branch that might address this (@c1728p9 can confirm and review this). This should be the branch https://github.com/ARMmbed/mbed-os/tree/feature-hal-spec-usb-device |
/morph build |
Build : SUCCESSBuild number : 2316 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1939 |
/morph mbed2-build |
Updated comment since this PR feels like it's more of a feature addition than a fix. Rerunning test since failures appear to be focused around a device that had to be restarted today. |
/morph mbed2-build |
We're looking into some CI issues at the moment. The test will be restarted when the dust has settled. |
Re-queued since failure was due to a newly discovered htrun bug. /morph test |
Description
For certain applications it is desirable to do a non-blocking write when sending larger blocks of data over USBSerial. I am proposing to add a second function to USBCDC to support this. Does anyone have suggestions on how to implement this in the API?
There could be an optional argument bool blocking=true, or a second function writeBlockNB, or make it always non-blocking?
Pull request type