From: Takashi Iwai <tiwai@suse.de>
To: Denis Turischev <denis.turischev@compulab.co.il>
Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
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: Tue, 07 Jan 2014 11:03:00 +0100 [thread overview]
Message-ID: <s5hd2k4qfcb.wl%tiwai@suse.de> (raw)
In-Reply-To: <52CAA2D4.2040103@compulab.co.il>
At Mon, 06 Jan 2014 14:34:28 +0200,
Denis Turischev wrote:
>
> Hi Sarah,
>
> On 01/03/2014 02:03 AM, Sarah Sharp wrote:
> > Denis, do all of Compulab's Haswell systems reboot on shutdown? Are
> > they all running a Phoenix BIOS? Can you send me the output of `sudo
> > lspci -vvv -s` for the xHCI host?
>
> oem@oem-Intense-PC2 ~ $ sudo lspci -vvv -s 00:14.0
> 00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04) (prog-if 30 [XHCI])
> Subsystem: Intel Corporation Device 7270
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 59
> Region 0: Memory at f0620000 (64-bit, non-prefetchable) [size=64K]
> Capabilities: [70] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
> Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
> Address: 00000000fee0200c Data: 41b1
> Kernel driver in use: xhci_hcd
>
> > Basically, I'm trying to find a common variable to key off. I suspect
> > BIOS vendor is probably the right thing, instead of system vendor.
>
> By the way the quirk introduced by commit e95829f474f0db3a4d940cae1423783edd966027 "xhci: Switch PPT
> ports to EHCI on shutdown." works for Lynx Point as well at least on Intense-PC2. I mean we can add
> XHCI_SPURIOUS_REBOOT flag that invokes usb_disable_xhci_ports().
>
> May be this solution works for HP and other systems without side effects?
No, we already tested it at first, but didn't fix the behavior on HP
machines. It was harmless as far as we've tested, though.
Takashi
next prev parent reply other threads:[~2014-01-07 10:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 16:29 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 [this message]
2014-01-07 23:11 ` Sarah Sharp
2014-01-08 12:57 ` Denis Turischev
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=s5hd2k4qfcb.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=art1@vhex.net \
--cc=dashing.meng@gmail.com \
--cc=denis.turischev@compulab.co.il \
--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 \
/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
Powered by JetHome