USB services: Difference between revisions
No edit summary |
No edit summary |
||
| Line 153: | Line 153: | ||
== GetStateChangeEvent == | == GetStateChangeEvent == | ||
Returns an event handle for state changes. Signalled when Switch<->host USB comms change between started/stopped. USB cable connected/disconnected while at least 1 interface was enabled, or interface enabled/disabled while the USB cable was connected which then caused USB-comms state to change. | Returns an event handle for state changes. Signalled when Switch<->host USB comms change between started/stopped. USB cable connected/disconnected while at least 1 interface was enabled, or interface enabled/disabled while the USB cable was connected which then caused USB-comms state to change. | ||
This is signalled before the endpoints are actually ready for data-transfer - there's currently no known way to properly check for that. | |||
== SetVidPidBcd == | == SetVidPidBcd == | ||
| Line 231: | Line 233: | ||
=== GetSetupEvent === | === GetSetupEvent === | ||
Returns an event handle. Unknown what triggers signalling. | Returns an event handle. Unknown what triggers signalling, not signalled during interface-enable / device<>host USB-comms init. | ||
=== EnableInterface === | === EnableInterface === | ||
| Line 290: | Line 292: | ||
Used for data-transfer with input/output endpoints. | Used for data-transfer with input/output endpoints. | ||
The user-process must flush dcache for the buffer before using this command. | |||
==== GetCompletionEvent ==== | ==== GetCompletionEvent ==== | ||