From: Denis Turischev <denis.turischev@compulab.co.il>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Oliver Neukum <oneukum@suse.de>,
dashing.meng@gmail.com, Niklas Schnelle <niklas@komani.de>,
Giorgos <ganastasiouGR@gmail.com>,
art1@vhex.net
Subject: Re: [PATCH v1] xhci: Switch Intel Lynx Point ports to EHCI on shutdown
Date: Wed, 08 Jan 2014 14:57:11 +0200 [thread overview]
Message-ID: <52CD4B27.2030200@compulab.co.il> (raw)
In-Reply-To: <20140107231103.GD4199@xanatos>
On 01/08/2014 01:11 AM, Sarah Sharp wrote:
> Denis, what do you mean by "works for Lynx Point"? Do you mean that
> adding the quirk to switch the ports on EHCI on shutdown (e95829f474)
> for the Intense-PC2 *instead of* the commit to put the host in D3 on
> shutdown (638298dc66) works? Or do you mean you need both patches for
> your system?
>
> If you only need the quirk to switch the ports to EHCI on shutdown, then
> we could apply that broadly to Lynx Point LP, and see whether other
> BIOSes tolerate that quirk.
Yes, switching the ports on EHCI on shutdown is enough for Intense-PC2.
I don't need both patches.
next prev parent reply other threads:[~2014-01-08 12:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 16:29 xhci: Switch Intel Lynx Point ports to EHCI on shutdown Denis Turischev
2013-12-19 16:38 ` Greg KH
2013-12-19 17:07 ` [PATCH v1] " Denis Turischev
2013-12-19 18:21 ` Sarah Sharp
2013-12-20 10:41 ` Denis Turischev
2013-12-20 23:45 ` Sarah Sharp
2013-12-21 16:45 ` Holger Freyther
2013-12-22 7:47 ` Denis Turischev
2014-01-03 0:03 ` Sarah Sharp
2014-01-03 3:40 ` littlebat
2014-01-03 18:14 ` Oliver Neukum
2014-01-03 19:34 ` art1
2014-01-06 12:34 ` Denis Turischev
2014-01-07 10:03 ` Takashi Iwai
2014-01-07 23:11 ` Sarah Sharp
2014-01-08 12:57 ` Denis Turischev [this message]
2014-02-04 11:10 ` [PATCH] " Denis Turischev
2014-02-18 7:42 ` [RESEND] " Denis Turischev
2014-02-18 18:54 ` Sarah Sharp
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=52CD4B27.2030200@compulab.co.il \
--to=denis.turischev@compulab.co.il \
--cc=art1@vhex.net \
--cc=dashing.meng@gmail.com \
--cc=ganastasiouGR@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=niklas@komani.de \
--cc=oneukum@suse.de \
--cc=sarah.a.sharp@linux.intel.com \
--cc=tiwai@suse.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 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.