USB Transactions
13-76
Table 13–25. Autodecoded Versus Non-Autodecoded Control Requests (Continued)
Request
Device Behavior if
Device not Configured
LH Required Action
Status
Recipient
CLEAR/SET
FEATURE
Device
Autodecoded
None
(DS_Chg interrupt is asserted to
the local host after any the
R_WK_OK bit modification).
The core handles the
request.
Interface
Autodecoded
None
(No feature is defined in USB
1.1 spec for interface. These
requests are stalled).
Command is stalled.
Endpoint
Non-autode-
coded
The local host must stall the
command (via the Stall_Cmd
bit) if endpoint
number/type/direction is not
correct.
The local host must reset the
endpoint after having handled
the pending transactions (if
CLEAR) or set halt condition (if
SET). For EP 0, local host only
has to clear or set halt condition:
FIFO and data PID are always
correct for next setup.
Command is passed to the
local host.
SET_
ADDRESS
Device
Autodecoded
None
(Whether the device is
addressed or not is available in
DEVSTAT register. A valid
SET_ADDRESS request with
address number from 0
generates a DS_Chg interrupt to
the local host).
-
Default: device moves
into the addressed
state if address num-
ber is different from 0.
-
Addressed: device
takes the new address
value or moves in de-
fault state if address
number is 0.
-
Configured: request is
STALLed.
GET_
DESCRIPTOR
All
Non-autode-
coded
The local host must write
descriptor data into endpoint 0
FIFO.
Command is passed to the
local host.