public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Gettys <jg@laptop.org>
To: David Brownell <david-b@pacbell.net>
Cc: linux-pm@osdl.org, linux-usb-devel@lists.sourceforge.net,
	Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, Mattia Dongili <malattia@linux.it>,
	Jiri Slaby <jirislaby@gmail.com>
Subject: Re: [linux-pm] [PATCH] get USB suspend to work again on 2.6.17-mm1
Date: Sat, 24 Jun 2006 22:42:57 -0400	[thread overview]
Message-ID: <1151203377.15365.389.camel@localhost.localdomain> (raw)
In-Reply-To: <200606222034.44085.david-b@pacbell.net>

On Thu, 2006-06-22 at 20:34 -0700, David Brownell wrote:

> Under what scenario could it possibly be legitimate to suspend a
> usb device -- or interface, or anything else -- with its children
> remaining active?  The ability to guarantee that could _never_ happen
> was one of the fundamental motivations for the driver model ...
> 

I'm not sure this directly applies, but....

The Marvell wireless chip we're using this generation in the OLPC
machine is interfaced via USB.  Not ideal, but there's no other game in
town to let us keep the mesh network up while the main machine is STR.

We intend to leave the Marvell chip on (it can forward packets in the
mesh network, and/or wake up the CPU if there are inbound packets for
the machine that matter), and turn off the USB interface it is attached
to.
                        Regards,
                             - Jim

-- 
Jim Gettys
One Laptop Per Child



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

  parent reply	other threads:[~2006-06-25  2:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 20:29 [PATCH] get USB suspend to work again on 2.6.17-mm1 Greg KH
2006-06-22 21:27 ` Jiri Slaby
2006-06-22 21:28 ` Mattia Dongili
2006-06-22 21:34 ` Mattia Dongili
2006-06-22 23:24 ` David Brownell
2006-06-22 23:51   ` Greg KH
2006-06-23  2:45     ` Alan Stern
2006-06-23  4:26       ` Greg KH
2006-06-23 14:28         ` Alan Stern
2006-06-23  3:34     ` David Brownell
2006-06-23  4:24       ` Greg KH
2006-06-23 14:51         ` Alan Stern
2006-06-23 15:38           ` David Brownell
2006-06-26 23:57           ` Greg KH
2006-06-27  2:04             ` David Brownell
2006-06-27 15:24               ` Alan Stern
2006-06-27 23:28                 ` Greg KH
2006-06-27 23:26               ` Greg KH
2006-06-27  9:03             ` Pavel Machek
2006-06-27 17:38               ` David Brownell
2006-06-27 23:20                 ` Greg KH
2006-06-25  2:42       ` Jim Gettys [this message]
2006-06-25  4:32         ` [linux-pm] " David Brownell

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=1151203377.15365.389.camel@localhost.localdomain \
    --to=jg@laptop.org \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@osdl.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=malattia@linux.it \
    /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