Texas Instruments OMAP5912 Reference Manual page 1426

USB Device Controller
3.7.5 Autodecoded Versus Non-Autodecoded Control Requests
Table 55.
Autodecoded Versus Non-Autodecoded Control Requests
Request Recipient Status
GET_ Device
STATUS
Interface
Endpoint
CLEAR/SET Device
FEATURE
Interface
Notes: 1) Transactions on endpoints other than zero are ignored if the device is not configured (addressed state).
2) If some endpoints are not used by the interface currently set, transactions on these endpoints are not ignored;
the MPU must set halt feature for the endpoint. This does not happen if USB host works correctly.
3) If endpoint 0 is halted, per USB 1.1 Specification (see 9.4.5: Get_Status), all requests are stalled except
GET_STATUS, CLEAR_FEATURE, and SET_FEATURE requests.
4) Requests are handled with respect to USB 1.1 when specified as such, but many device reactions are not speci-
fied by USB 1.1.
5) During a SET_ADDRESS autodecoded command, only the 7 LSBs are significant for the new address (decimal
value from 0 to 127); all others are discarded.
134 Universal Serial Bus (USB)
MPU Required Action
Autodecoded None
(function of
AUTODEC_
DIS register
bit)
Non- The MPU must stall the
autodecoded command (via
SYSCON2.STALL_
CMD bit) if interface number is
not correct. No feature is
defined for interface.
Autodecoded None
(function of
AUTODEC_
DIS register
bit)
Autodecoded None
(DS_CHG IT is asserted to the
(function of
MPU after any DEVSTAT.R_
AUTODEC_
WK_OK bit modification).
DIS register
bit)
Autodecoded None.
(No feature is defined in USB
(function of
1.1 spec for interface. These
AUTODEC_
requests are stalled).
DIS register
bit)
Device Behavior if
Device Is Not Configured
Device status is returned
(SYSCON1.SELF_PWR
and DEVSTAT.R_WK_OK
bits).
Command is passed to the
MPU.
The core automatically
stalls the command if
endpoint number is
different from 0.
The core handles the
request.
Command is stalled
anyway.
SPRU761A