public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ush: ehci: initialize altnext pointers in QH
Date: Fri, 07 Feb 2014 09:44:58 -0700	[thread overview]
Message-ID: <52F50D8A.3030507@wwwdotorg.org> (raw)
In-Reply-To: <201402071450.28929.marex@denx.de>

On 02/07/2014 06:50 AM, Marek Vasut wrote:
> On Friday, February 07, 2014 at 07:47:14 AM, Stephen Warren wrote:
>> On 02/06/2014 07:53 PM, Marek Vasut wrote:
>>> On Thursday, February 06, 2014 at 09:13:05 PM, Stephen Warren wrote:
>>>> From: Stephen Warren <swarren@nvidia.com>
>>>>
>>>> A QH's overlay QTD altnext pointer should be explicitly marked invalid
>>>> so that the EHCI controller knows to look at the QTD next pointer.
>>>> Update the driver to do this.
...
>>>> diff --git a/drivers/usb/host/ehci-hcd.c b/drivers/usb/host/ehci-hcd.c
>>>>
>>>> @@ -1186,6 +1187,7 @@ create_int_queue(struct usb_device *dev, unsigned
>>>> long pipe, int queuesize, qh->qh_link = QH_LINK_TERMINATE;
>>>>
>>>>  		qh->qh_overlay.qt_next = (uint32_t)td;
>>>>
>>>> +		qh->qh_overlay.qt_altnext = QT_NEXT_TERMINATE;
>>>
>>> So next is td and altnext is terminate here ?
>>
>> Yes. TERMINATE really just means INVALID, so the EHCI controller gets
>> the pointer from qt_next rather than qt_altnext.
> 
> Hmmmm ... not really clear or self-explaining, is it. If you have time to 
> produce a RFC to clean this up, I'm all for checking it.

Looking at section 3.5.1 "Next qTD Pointer", this bit is in fact named
Terminate (hence it's referred to as the T bit), so this naming seems to
be ingrained in the EHCI specification, so I'm uninclined to change it
in U-Boot.

      reply	other threads:[~2014-02-07 16:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 20:13 [U-Boot] [PATCH 1/2] ush: ehci: initialize altnext pointers in QH Stephen Warren
2014-02-06 20:13 ` [U-Boot] [PATCH 2/2] usb: ehci: fully align interrupt QHs/QTDs Stephen Warren
2014-02-07  2:53   ` Marek Vasut
2014-02-07  6:48     ` Stephen Warren
2014-02-07 13:48       ` Marek Vasut
2014-02-07 16:24         ` Stephen Warren
2014-02-08 14:01           ` Marek Vasut
2014-02-21  4:17             ` Stephen Warren
2014-02-07  2:53 ` [U-Boot] [PATCH 1/2] ush: ehci: initialize altnext pointers in QH Marek Vasut
2014-02-07  6:47   ` Stephen Warren
2014-02-07 13:50     ` Marek Vasut
2014-02-07 16:44       ` Stephen Warren [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52F50D8A.3030507@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox