mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Duncan Sands <baldrick@free.fr>,
	usbatm@lists.infradead.org,
	linux-usb-devel@lists.sourceforge.net, greg@kroah.com,
	linux-kernel@vger.kernel.org, ueagle <ueagleatm-dev@gna.org>,
	matthieu castet <castet.matthieu@free.fr>
Subject: Re: [linux-usb-devel] [PATCH 1/3] UEAGLE : be suspend friendly
Date: Thu, 5 Oct 2006 20:14:26 +0200	[thread overview]
Message-ID: <20061005181426.GA27838@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0610051221520.6596-100000@iolanthe.rowland.org>

Hi!

> > > Plug/unplug should be easy enough to simulate from usb driver, no?
> > 
> > if a USB driver doesn't define suspend/resume methods, then the core simply
> > unplugs it on suspend, and replugs on resume (IIRC).
> 
> No longer true, and IIRC it never was.  All that happens is that URB 
> submissions fail with -EHOSTUNREACH once the device is suspended.

Could we get "old" behaviour for devices like this? "printk("please
unplug/replug me\n")" is not a good solution.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-10-05 18:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03 19:46 matthieu castet
2006-10-04 22:05 ` Pavel Machek
2006-10-05  7:17   ` Duncan Sands
2006-10-05 16:22     ` [linux-usb-devel] " Alan Stern
2006-10-05 18:14       ` Pavel Machek [this message]
2006-10-05 20:29         ` Alan Stern
2006-10-06 15:10           ` Duncan Sands
2006-10-06 18:20             ` Alan Stern

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=20061005181426.GA27838@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=baldrick@free.fr \
    --cc=castet.matthieu@free.fr \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    --cc=ueagleatm-dev@gna.org \
    --cc=usbatm@lists.infradead.org \
    /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

all inboxes | Powered by JetHome®