max/embassy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

usb/driver: fix STATUS -> SETUP

Browse Source
This commit is contained in:
Dario Nieuwenhuis 2023-01-05 14:46:31 +01:00 committed by GitHub
parent b72da125eb
commit 3c537a9fae
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
embassy-usb-driver/src/lib.rs
View File

@ -273,8 +273,8 @@ pub trait EndpointOut: Endpoint {
/// calls to `data_in` or `data_out` for the status zero-length packet. The status stage should /// calls to `data_in` or `data_out` for the status zero-length packet. The status stage should
/// be triggered by either `accept()`, or `data_in` with `last = true`. /// be triggered by either `accept()`, or `data_in` with `last = true`.
/// ///
/// Note that the host can abandon a control request and send a new STATUS packet any time. If /// Note that the host can abandon a control request and send a new SETUP packet any time. If
/// a STATUS packet arrives at any time during `data_out`, `data_in`, `accept` or `reject`, /// a SETUP packet arrives at any time during `data_out`, `data_in`, `accept` or `reject`,
/// the driver must immediately return (with `EndpointError::Disabled` from `data_in`, `data_out`) /// the driver must immediately return (with `EndpointError::Disabled` from `data_in`, `data_out`)
/// to let the stack call `setup()` again to start handling the new control request. Not doing /// to let the stack call `setup()` again to start handling the new control request. Not doing
/// so will cause things to get stuck, because the host will never read/send the packet we're /// so will cause things to get stuck, because the host will never read/send the packet we're