diff options
| -rw-r--r-- | embassy-usb-driver/src/lib.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/embassy-usb-driver/src/lib.rs b/embassy-usb-driver/src/lib.rs index 71e5267c6..d7238dc7d 100644 --- a/embassy-usb-driver/src/lib.rs +++ b/embassy-usb-driver/src/lib.rs | |||
| @@ -273,8 +273,8 @@ pub trait EndpointOut: Endpoint { | |||
| 273 | /// calls to `data_in` or `data_out` for the status zero-length packet. The status stage should | 273 | /// calls to `data_in` or `data_out` for the status zero-length packet. The status stage should |
| 274 | /// be triggered by either `accept()`, or `data_in` with `last = true`. | 274 | /// be triggered by either `accept()`, or `data_in` with `last = true`. |
| 275 | /// | 275 | /// |
| 276 | /// Note that the host can abandon a control request and send a new STATUS packet any time. If | 276 | /// Note that the host can abandon a control request and send a new SETUP packet any time. If |
| 277 | /// a STATUS packet arrives at any time during `data_out`, `data_in`, `accept` or `reject`, | 277 | /// a SETUP packet arrives at any time during `data_out`, `data_in`, `accept` or `reject`, |
| 278 | /// the driver must immediately return (with `EndpointError::Disabled` from `data_in`, `data_out`) | 278 | /// the driver must immediately return (with `EndpointError::Disabled` from `data_in`, `data_out`) |
| 279 | /// to let the stack call `setup()` again to start handling the new control request. Not doing | 279 | /// to let the stack call `setup()` again to start handling the new control request. Not doing |
| 280 | /// so will cause things to get stuck, because the host will never read/send the packet we're | 280 | /// so will cause things to get stuck, because the host will never read/send the packet we're |