Lines Matching full:it
74 When a USB 3.0 device is plugged into a USB 2.0 port or hub, then it will report
75 its version as USB 2.1, to indicate that it is actually a USB 3.0 device.
78 operations vector, it helps to understand how USB devices are organized
121 on it, and receives periodic updates whenever there is information available.
128 A device may describe an interval as 10ms at which point it will read or
129 write the next batch of data every 10ms and transform it for the user.
172 work necessary to allow the client device driver to access it.
173 Once the pipe is open, it either makes one-shot transfers specific to the
174 transfer type or it starts performing a periodic poll of an endpoint.
209 To initialize a device driver with the USBA, it must first call
213 structure that it must fill out.
216 for instructions on how it should be filled out.
225 functions it registered with the call to
249 The definition for it can be found in
259 Note, that the structure needs to be packed, as though it were read from
284 the next section), unwind all of the resources it has allocated, and
288 Otherwise, at this point it's safe to assume that the instance of the
311 As this call always succeeds, at this point, it is safe for the driver
323 If it has been called before the device registers, then it will fail to register
325 However, setting it after that point will corrupt the state of the USBA and
332 and it's trying to extract the minor number, it must take into account
414 If the device driver wishes to have private ioctls, it may check the
451 functions that it has register in the
488 once, it should strive not to hold its own internal locks while waiting
491 If the device driver does not pay attention to these conditions, it can easily
512 from one of those functions, it is expected that it will later call
523 from its entry point, then it must not call
529 Host controller drivers need to be ready for this and report it.
533 Otherwise, it should instead return an error.
543 entry point, it already has to look at the pipe handle it's been given
544 to determine the attributes of the endpoint it's looking at.
545 However, before it does that it needs to look at the USB address of the device
575 to indicate that it has finished.
591 Every USB device has an address assigned to it.
627 down whatever it created as part of opening the pipe.
628 In addition, if the pipe was an interrupt-IN pipe, if it has not already had
629 polling stop, it should stop the polling as part of closing the pipe.
631 When a request to stop interrupt polling comes in and it is directed
634 However, it should continue keeping track of what changes have occurred for the
641 If for some reason it calls asking to stop polling on an isochronous transfer,
655 is made for it, no more and no less.
667 The driver must not use the original request structure until it is ready
677 Note, it is possible that memory will not be available to duplicate such a
710 If that timeout expires, it needs to stop the endpoint, remove that request, and
733 Due to the periodic nature of even outbound requests, it is less likely
747 for a given outstanding transfer once a second and then if it reaches zero,
758 A device may have one or more configurations that it supports that can be
785 Host controllers use this and act on it to perform bulk transfers to USB
792 Host controllers use this and act on it to perform bulk transfers to USB
799 Host controllers use this and act on it to perform bulk transfers to USB
806 Host controllers use this and act on it to perform bulk transfers to USB
844 generally enable it and set it to a moderate rate.