From: Duncan Sands <baldrick@free.fr>
To: usbatm@lists.infradead.org
Cc: Pavel Machek <pavel@ucw.cz>,
matthieu castet <castet.matthieu@free.fr>,
greg@kroah.com, ueagle <ueagleatm-dev@gna.org>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/3] UEAGLE : be suspend friendly
Date: Thu, 5 Oct 2006 09:17:35 +0200 [thread overview]
Message-ID: <200610050917.36442.baldrick@free.fr> (raw)
In-Reply-To: <20061004220548.GC8667@elf.ucw.cz>
Hi Pavel,
> > Signed-off-by: matthieu castet <castet.matthieu@free.fr>
> > Index: linux/drivers/usb/atm/ueagle-atm.c
> > ===================================================================
> > --- linux.orig/drivers/usb/atm/ueagle-atm.c 2006-09-22 21:39:56.000000000 +0200
> > +++ linux/drivers/usb/atm/ueagle-atm.c 2006-09-22 21:40:45.000000000 +0200
> > @@ -1177,6 +1177,9 @@
> > ret = uea_stat(sc);
> > if (ret != -EAGAIN)
> > msleep(1000);
> > + if (try_to_freeze())
> > + uea_err(INS_TO_USBDEV(sc), "suspend/resume not supported, "
> > + "please unplug/replug your modem\n");
>
> 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). Maybe Matthieu is trying
for something better - hopefully he will explain. Since this is a modem, it
would be nice if the internet connection sprang back to life on resume, which
requires more work than unplug/plug. I've no idea what needs to be done to achieve
this. These modems use the ATM networking layer by the way, I don't know if that
makes things easier or harder.
Ciao,
Duncan.
next prev parent reply other threads:[~2006-10-05 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 19:46 [PATCH 1/3] UEAGLE : be suspend friendly matthieu castet
2006-10-04 22:05 ` Pavel Machek
2006-10-05 7:17 ` Duncan Sands [this message]
2006-10-05 16:22 ` [linux-usb-devel] " Alan Stern
2006-10-05 18:14 ` Pavel Machek
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=200610050917.36442.baldrick@free.fr \
--to=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=pavel@ucw.cz \
--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