USB HOST DRIVER V03 Freescale Semiconductor / Motorola, USB HOST DRIVER V03 Datasheet - Page 19

no-image

USB HOST DRIVER V03

Manufacturer Part Number
USB HOST DRIVER V03
Description
USB Host Driver v03
Manufacturer
Freescale Semiconductor / Motorola
Datasheet
For a full description of Device requests, refer to the Programming Interface section.
2.5. Pipe Object.
Pipe objects provide the ability to perform data flow transactions through the pipes on the
Device. Each pipe object points to a particular Device endpoint. The USB 1.1
specification defines control, bulk, interrupt and isochronous endpoint types. The bulk
and isochronous endpoints specify the data flow direction from Device to PC, or from PC
to Device. A MOTUSB pipe object can be used for any endpoint type except for control.
The interface with the MOTUSB endpoint object is the same for any endpoint type.
Once the Device becomes configured, the Client application can open handles to pipe
objects. Each interface configuration on the Device defines a particular set of endpoints
through which data transmission can be performed. So only handles for pipes supported
by an active configuration, and interfaces configured within it can be obtained. No pipe
handles can be valid or opened on an unconfigured Device. Note that 'Set Configuration'
and 'Set Interface' requests will fail if pipe connections to a Device exist.
2.5.1.
MOTUSB represents pipe object connections as for the Device objects, but with a
somewhat different naming scheme. A pipe object connection can be created
independently of a Device object connection. So in order to establish a connection to a
pipe object, the programmer may use a procedure similar to the one described above, but
specifying a different file name.
NOTE: As mentioned above USDI monopolizes endpoint #0, so no pipe connection to
this endpoint can be established. MOTUSB Device objects expose functionality that can
be applied to this endpoint.
The file name format for pipe objects is as follows:
<Device instance name> \ <decimal endpoint address>, where
M
Device instance name is string obtained from the
decimal endpoint address is an endpoint address for which a pipe should be open.
Getting status of specified recipient
Device locking / unlocking
Interface Alternate Setting control
Sending Class or Vendor Requests
Device replugging emulation
Device resetting
Opening Connection To Pipe.
PRELIMINARY—SUBJECT TO CHANGE WITHOUT NOTICE
Setup API
call in DevicePath member;
Driver Model.
SetupDiGetDeviceInterfaceDetail
2-8

Related parts for USB HOST DRIVER V03