public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	David Brownell <david-b@pacbell.net>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: USB rejecting sleep
Date: Mon, 19 Dec 2005 13:51:45 +1100	[thread overview]
Message-ID: <1134960706.6162.2.camel@gaston> (raw)
In-Reply-To: <20051218222516.GA19183@kroah.com>

On Sun, 2005-12-18 at 14:25 -0800, Greg KH wrote:
> On Mon, Dec 19, 2005 at 09:13:50AM +1100, Benjamin Herrenschmidt wrote:
> > On Sun, 2005-12-18 at 13:50 -0800, Greg KH wrote:
> > 
> > > Yes it is, and I have a patch in my tree now that fixes this up and
> > > keeps the suspend process working properly for usb drivers that do not
> > > have a suspend function.
> > > 
> > > Hm, I wonder if it should go in for 2.6.15?
> > 
> > Do you have an URL I can send to those users to test ?
> 
> Here's the patch itself, feel free to spread it around.
> 
> It's also at:
>   kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/usb/usbcore-allow-suspend-resume-even-if-drivers-don-t-support-it.patch

Ok, I did a bit more tests here with a Keyspan adapter on my laptop
(well known driver for not having the suspend/resume routines).

The good thing is with the patch, the machine goes to sleep. However,
the device is not disconnected/reconnected. What happens it that the bus
gets suspended anyway and the driver stays around (possibly getting
errors on some URBs).

This is fine, but not optimal, since that means most of the time that
the device will not work on resume unless disconnected/reconnected. (For
keyspan, it seems that the HW does support the suspend state, thus it's
just a matter of closing/re-opening the port, I suppose it would be easy
enough to fix the driver).

So this patch is good for it doesn't prevent sleep anymore, but it also
doesn't do what we decided it should do. I think David is right that we
should be able to disconnect the device without actually removing the
device & driver from sysfs, just let that happen at resume time.

Ben.



  parent reply	other threads:[~2005-12-19  2:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-18 20:27 USB rejecting sleep Benjamin Herrenschmidt
2005-12-18 20:58 ` David Brownell
2005-12-18 21:01   ` Benjamin Herrenschmidt
2005-12-18 22:07     ` Marcel Holtmann
2005-12-18 23:11   ` Alan Stern
2005-12-18 21:50 ` Greg KH
2005-12-18 22:13   ` Benjamin Herrenschmidt
2005-12-18 22:25     ` Greg KH
2005-12-18 23:16       ` Benjamin Herrenschmidt
2005-12-19  2:51       ` Benjamin Herrenschmidt [this message]
2005-12-19  3:11         ` Alan Stern
2005-12-19  3:24           ` Benjamin Herrenschmidt
2005-12-19 14:45             ` Alan Stern
2005-12-22 16:02   ` Pavel Machek
2005-12-27  4:19     ` Greg KH

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=1134960706.6162.2.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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