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] Regression due to 020bbcb "usb: hub: Power-cycle on root-hub ports"
Date: Mon, 08 Jul 2013 12:03:55 -0600	[thread overview]
Message-ID: <51DAFF0B.4080603@wwwdotorg.org> (raw)
In-Reply-To: <201307081903.18836.marex@denx.de>

On 07/08/2013 11:03 AM, Marek Vasut wrote:
> Dear Stephen Warren,
> 
>> On 07/08/2013 07:25 AM, Vivek Gautam wrote:
>>> On Mon, Jul 8, 2013 at 6:33 PM, Marek Vasut <marex@denx.de> wrote:
>>>>> On Mon, Jul 1, 2013 at 10:11 PM, Stephen Warren <swarren@wwwdotorg.org> 
> wrote:
>>>>>> On 07/01/2013 07:49 AM, Vivek Gautam wrote:
>>>>>>> On Sun, Jun 30, 2013 at 10:08 PM, Marek Vasut <marex@denx.de> wrote:
>>>>>>>>> (Sorry to those on to/cc; I'm resending this so it goes to the
>>>>>>>>> correct mailing list)
>>>>>>>
>>>>>>> Dear Stephen,
>>>>>>> sorry for the delay in responding to this.
>>>>>>>
>>>>>>>>> Commit 020bbcb "usb: hub: Power-cycle on root-hub ports" causes a
>>>>>>>>> regression on Tegra systems.
...
>>>> Vivek, what do I have to revert to fix this flub? I will do that now,
>>>> since this discussion is stalled.
>>>
>>> 0bf796f usb: hub: Parallelize power-cycling of root-hub ports
>>> 020bbcb usb: hub: Power-cycle on root-hub ports
>>>
>>> Above two patches are the one which changed the hub_power_on()
>>> functionality. If Stephen can confirm that reverting these patches
>>> really solves the problem on Tegra,
>>> we can revert them.
>>
>> Yes, I have been reverting those two commits locally for a while, and it
>> solves the problem for me.
> 
> Reverted, please test u-boot-usb/master .

Well, it works, but it turns out the reverts aren't needed. Simon Glass
already found the problem, and fixed it with:

ed10e66 usb: Correct CLEAR_FEATURE code in ehci-hcd

Sorry for not noticing this earlier, but since there hadn't been any
news in this thread, and there weren't any relevant changes to the
power-cycling code affected by the problematic patches, it didn't occur
to me that the problem may have already been fixed elsewhere, so I
didn't ever retest the issue with a newer commit than that one where I
originally found the problem:-(

  reply	other threads:[~2013-07-08 18:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51BA3ECA.3070101@wwwdotorg.org>
2013-06-13 22:03 ` [U-Boot] Regression due to 020bbcb "usb: hub: Power-cycle on root-hub ports" Stephen Warren
2013-06-30 16:38   ` Marek Vasut
2013-07-01 13:49     ` Vivek Gautam
2013-07-01 16:41       ` Stephen Warren
2013-07-02 17:01         ` Vivek Gautam
2013-07-08 13:03           ` Marek Vasut
2013-07-08 13:25             ` Vivek Gautam
2013-07-08 15:58               ` Stephen Warren
2013-07-08 17:03                 ` Marek Vasut
2013-07-08 18:03                   ` Stephen Warren [this message]
2013-07-08 18:25                     ` Marek Vasut
2013-07-08 18:28                       ` Stephen Warren
2013-07-08 19:50                         ` Marek Vasut
2013-07-08 19:53                           ` Stephen Warren
2013-07-09  7:46                             ` Vivek Gautam

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=51DAFF0B.4080603@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