From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xhci: Add reset on resume quirk for asrock p67 host
Date: Wed, 15 Jun 2011 23:41:23 +0200 [thread overview]
Message-ID: <4DF92703.7000408@gmail.com> (raw)
In-Reply-To: <20110615212135.GH5382@xanatos>
Op 15-06-11 23:21, Sarah Sharp schreef:
> On Wed, Jun 15, 2011 at 05:00:17PM -0400, Alan Stern wrote:
>> On Wed, 15 Jun 2011, Sarah Sharp wrote:
>>
>>> On Wed, Jun 15, 2011 at 10:29:01PM +0200, Maarten Lankhorst wrote:
>>>> The asrock p67 xhci controller completely dies on resume,
>>>> add a quirk for this, to bring the host back online after a suspend.
>>>>
>>>> This should be backported to stable kernels as far back as 2.6.34.
>>> Why 2.6.34? Only kernels as old as 2.6.37 had xHCI suspend and resume
>>> support. Before 2.6.37, the xHCI driver would prevent the system from
>>> suspending at all.
>>>
>>> Otherwise looks fine.
>>>
>>> Sarah Sharp
>>>
>>>> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
>>>> index 06e7023..42fd032 100644
>>>> --- a/drivers/usb/host/xhci.c
>>>> +++ b/drivers/usb/host/xhci.c
>>>> @@ -759,6 +759,8 @@ int xhci_resume(struct xhci_hcd *xhci, bool hibernated)
>>>> msleep(100);
>>>>
>>>> spin_lock_irq(&xhci->lock);
>>>> + if (xhci->quirks & XHCI_RESET_ON_RESUME)
>>>> + hibernated = 0;
>> Shouldn't this be "hibernated = true;"? You want the driver to treat
>> suspend as though it were hibernation, not the other way around.
> Yes, good catch. Maarten, can you respin this patch (and with the
> note that it should be backported as far as 2.6.37).
>
> Sarah Sharp
Odd! I could have sworn I had a succesful suspend with the quirk printed
in dmesg. The hang appears to not happen 100% of the time then. Weird,
wish I had saved the log. Will respin the patch.
Of course the act of observing made it impossible to reproduce. :-/
~Maarten
next prev parent reply other threads:[~2011-06-15 21:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 7:07 device plugged into xhci port not detected after a resume Maarten Lankhorst
2011-06-15 15:38 ` Greg KH
2011-06-15 16:17 ` Maarten Lankhorst
2011-06-15 16:58 ` Sarah Sharp
2011-06-15 17:29 ` Maarten Lankhorst
2011-06-15 17:39 ` Maarten Lankhorst
2011-06-15 19:59 ` Sarah Sharp
2011-06-15 20:19 ` Sarah Sharp
2011-06-15 20:29 ` [PATCH] xhci: Add reset on resume quirk for asrock p67 host Maarten Lankhorst
2011-06-15 20:36 ` Sarah Sharp
2011-06-15 20:38 ` Maarten Lankhorst
2011-06-15 20:39 ` Sarah Sharp
2011-06-15 21:00 ` Alan Stern
2011-06-15 21:21 ` Sarah Sharp
2011-06-15 21:41 ` Maarten Lankhorst [this message]
2011-06-15 22:15 ` Maarten Lankhorst
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=4DF92703.7000408@gmail.com \
--to=m.b.lankhorst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.