All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Ulrich Eckhardt <usb@uli-eckhardt.de>,
	Andrew Lutomirski <luto@mit.edu>,
	"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Ming Lei <ming.lei@canonical.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, Huang Ying <ying.huang@intel.com>
Subject: Re: Unreliable USB3 with NEC uPD720200 and Delock Cardreader
Date: Mon, 26 Nov 2012 22:48:03 +0100	[thread overview]
Message-ID: <87boekave4.fsf@nemi.mork.no> (raw)
In-Reply-To: <20121126191002.GE6504@xanatos> (Sarah Sharp's message of "Mon, 26 Nov 2012 11:10:02 -0800")

Sarah Sharp <sarah.a.sharp@linux.intel.com> writes:

> It looks like both Ulrich and Andrew have the same issue.  I also have a
> Lenovo x220, and I confirmed that when I turn on PCI runtime suspend,
> the NEC host controller does not report port status changes when a new
> USB device is plugged in.
>
> I'm running 3.6.7, and I'm pretty sure that runtime suspend worked for
> the NEC host on some older kernel.  I don't think the NEC host went into
> D3cold on that kernel, though.  Is there a way to disable D3cold and
> just use D3hot instead?

Yes, you have /sys/bus/pci/devices/.../d3cold_allowed
See Documentation/ABI/testing/sysfs-bus-pci

If this really is a problem with the D3cold support that went into 3.6
then I guess you should include Huang Ying in the discussions as well
(CCed).


Bjørn

       reply	other threads:[~2012-11-26 21:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121126191002.GE6504@xanatos>
2012-11-26 21:48 ` Bjørn Mork [this message]
2012-11-28 22:54   ` Unreliable USB3 with NEC uPD720200 and Delock Cardreader Sarah Sharp
2012-12-06  0:33     ` Sarah Sharp
2012-12-06  0:43       ` Rafael J. Wysocki
2012-12-07  0:28         ` Sarah Sharp
2012-12-07 21:00           ` Rafael J. Wysocki
2012-12-12  2:32             ` Huang Ying
2012-12-12  2:34               ` Andrew Lutomirski
2012-12-12  3:18                 ` huang ying
2012-12-13 19:53               ` Sarah Sharp
2012-12-06  7:17       ` Huang Ying
2012-12-06 12:43         ` Rafael J. Wysocki
     [not found] <50841CCC.9030809@uli-eckhardt.de>
2012-10-22 23:40 ` Sarah Sharp
2012-10-23 13:54   ` Bjorn Helgaas
2012-10-23 17:14   ` Ulrich Eckhardt
2012-10-24 20:18     ` Bjorn Helgaas
2012-10-24 21:10       ` Rafael J. Wysocki
2012-10-24 21:13         ` Bjorn Helgaas
2012-10-24 21:31           ` Rafael J. Wysocki
2012-10-25  1:24             ` Ming Lei
2012-10-25 13:33               ` Bjorn Helgaas
2012-10-25 17:43               ` Ulrich Eckhardt
2012-10-25 18:19                 ` Alan Stern
2012-10-27 13:02                   ` Ulrich Eckhardt
2012-10-25 17:15           ` Ulrich Eckhardt
2012-10-25 20:11             ` Rafael J. Wysocki
2012-10-26 16:41               ` Ulrich Eckhardt
2012-10-25 20:09       ` Rafael J. Wysocki

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=87boekave4.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=luto@mit.edu \
    --cc=ming.lei@canonical.com \
    --cc=rjw@sisk.pl \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=stern@rowland.harvard.edu \
    --cc=usb@uli-eckhardt.de \
    --cc=ying.huang@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.