diff options
| author | Stephen Warren <swarren@nvidia.com> | 2014-02-07 09:53:50 -0700 |
|---|---|---|
| committer | Marek Vasut <marex@denx.de> | 2014-03-10 18:53:36 +0100 |
| commit | 2456b97f0c9411d0bc2637ba1033a910c8b4b971 (patch) | |
| tree | 1c88cdc0bf55fb5c4fd9ca8d3ac6aac104167ba1 /board/ivm | |
| parent | 247161b8160fc699b0a517f081220bb50bc502a8 (diff) | |
| download | u-boot-imx-2456b97f0c9411d0bc2637ba1033a910c8b4b971.zip u-boot-imx-2456b97f0c9411d0bc2637ba1033a910c8b4b971.tar.gz u-boot-imx-2456b97f0c9411d0bc2637ba1033a910c8b4b971.tar.bz2 | |
ush: ehci: initialize altnext pointers in QH
Section 4.10.2 "Advance Queue" of ehci-specification-for-usb.pdf
specifies how an EHCI controller loads a new QTD for processing if the
QH is not already marked as active. It states:
=====
If the field Bytes to Transfer is not zero and the T-bit in the Alternate
Next qTD Pointer is set to zero, then the host controller uses the
Alternate Next qTD Pointer. Otherwise, the host controller uses the Next
qTD Pointer. If Next qTD Pointer’s T-bit is set to a one, then the host
controller exits this state and uses the horizontal pointer to the next
schedule data structure.
=====
Hence, we must ensure that the alternate next QTD pointer's T-bit
(TERMINATE) is set, so the EHCI controller knows to use the next QTD
pointer.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Diffstat (limited to 'board/ivm')
0 files changed, 0 insertions, 0 deletions