From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: 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 22:38:34 +0200 [thread overview]
Message-ID: <4DF9184A.9030308@gmail.com> (raw)
In-Reply-To: <20110615203631.GF5382@xanatos>
Hi Sarah,
Op 15-06-11 22:36, Sarah Sharp schreef:
> 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.
Oh my bad, I was just looking at my previous commit, expected
resume to already be available since xhci was in the kernel for so long.
Should I resend or will you amend the commit message?
~Maarten
next prev parent reply other threads:[~2011-06-15 20:38 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 [this message]
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
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=4DF9184A.9030308@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 \
/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.