All of lore.kernel.org
 help / color / mirror / Atom feed
From: baolu <baolu.lu@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] xhci: clear root port wake on bits if controller isn't wake-up capable
Date: Thu, 12 Jun 2014 09:18:18 +0800	[thread overview]
Message-ID: <5398FFDA.5050601@linux.intel.com> (raw)
In-Reply-To: <20140611152604.GA27630@kroah.com>


On 06/11/2014 11:26 PM, Greg Kroah-Hartman wrote:
> On Wed, Jun 11, 2014 at 06:25:20AM +0800, Lu Baolu wrote:
>> When the xHCI PCI host is suspended, if do_wakeup is false in xhci_pci_suspend,
>> xhci_bus_suspend needs to clear all root port wake on bits. Otherwise some Intel
>> platform may get a spurious wakeup, even if PCI PME# is disabled.
>>
>> http://marc.info/?l=linux-usb&m=138194006009255&w=2
>>
>> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
>> ---
>>   drivers/usb/host/xhci-hub.c | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
> Should this also be a stable kernel patch?  If so, how far back?
Yes.

This patch should be back-ported to kernels as old as 2.6.37, that
contains the commit 9777e3ce907d4cb5a513902a87ecd03b52499569
"USB: xHCI: bus power management implementation".

Thanks,
-baolu
>
> thanks,
>
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>


      reply	other threads:[~2014-06-12  1:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 22:25 [PATCH 1/1] xhci: clear root port wake on bits if controller isn't wake-up capable Lu Baolu
2014-06-11 15:26 ` Greg Kroah-Hartman
2014-06-12  1:18   ` baolu [this message]

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=5398FFDA.5050601@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@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.