summaryrefslogtreecommitdiff
path: root/board/bc3450
diff options
context:
space:
mode:
authorSergei Shtylyov <sshtylyov@ru.mvista.com>2010-06-28 22:44:49 +0400
committerWolfgang Denk <wd@denx.de>2010-06-29 23:03:40 +0200
commit9fb3b5085787baad8a133e347ad12c5b3a022e98 (patch)
tree05d5a40fac3db8159a16b2f62aee2585ad0fd1d9 /board/bc3450
parent0d7f4abcf6bbef06504c82e03f11054468262430 (diff)
downloadu-boot-imx-9fb3b5085787baad8a133e347ad12c5b3a022e98.zip
u-boot-imx-9fb3b5085787baad8a133e347ad12c5b3a022e98.tar.gz
u-boot-imx-9fb3b5085787baad8a133e347ad12c5b3a022e98.tar.bz2
EHCI: zero out QH transfer overlay in ehci_submit_async()
ehci_submit_async() doesn't really zero out the QH transfer overlay (as the EHCI specification suggests) which leads to the controller seeing the "token" field as the previous call has left it, i.e.: - if a timeout occured on the previous call (Active bit left as 1), controller incorrectly tries to complete a previous transaction on a newly programmed endpoint; - if a halt occured on the previous call (Halted bit set to 1), controller just ignores the newly programmed TD(s) and the function then keeps returning error ad infinitum. This turned out to be caused by the wrong orger of the arguments to the memset() call in ehci_alloc(), so the allocated TDs weren't cleared either. While at it, stop needlessly initializing the alternate next TD pointer in the QH transfer overlay... Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com> Acked-by: Remy Bohmer <linux@bohmer.net>
Diffstat (limited to 'board/bc3450')
0 files changed, 0 insertions, 0 deletions