From: Adam Belay <abelay-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
To: Alan Stern <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>
Cc: Linux-pm mailing list <linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: Some thoughts on suspend/resume development
Date: Fri, 11 Mar 2005 19:18:38 -0500 [thread overview]
Message-ID: <1110586718.12485.234.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0503111133040.1203-100000-3WpdWqXrU/qjv4eRiOYp3g@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]
On Fri, 2005-03-11 at 11:42 -0500, Alan Stern wrote:
> On Fri, 11 Mar 2005, Pavel Machek wrote:
>
> > > This is why I'm in favor of power domains (power parents and children
> > > that can be independent of physical device relations). Power domains
> > > are common for internal devices, not just external devices. Still, if
> > > you disable a physical parent, then the device is no longer operational.
> > > Disable the usb host controller, and the external disk drive cannot be
> > > used (in fact data may be lost). So it's necessary to stop every child
> > > device first, and generally also power it off if we can control the
> > > power source.
> >
> > I just don't see it like that.
> >
> > Remember old scsi disks where formatting took half an hour? You may do
> > something like
> >
> > invoke scsi format operation
> > power down usb controller
> > <half an hour later>
> > power up usb controller
> > get the results
> >
> > Now, that was probably bad example, but I do think some devices might
> > do usefull work even with their parents disabled.
Yes, but at a logical (class) level the parent device would never be
disabled, right? I guess it would be possible to model such a situation
if we take advantage of the driver class design. I hadn't considered it
before, but I'll try to keep it in mind. It would be interesting to see
how common it might be.
>
> There's another aspect to it as well. You can suspend the USB host
> controller and then _still_ use the external disk, if the host controller
> is automatically resumed when the next disk I/O request arrives. Whereas
> if you would stop the disk and its driver, the next I/O request might
> simply languish in a plugged queue. I suppose this would depend on
> whether the disk driver was smart enough to leave its queue unplugged
> under the right circumstances, so perhaps this isn't a great example.
> (And you're right about the possibility of data being lost -- although
> it's pretty unlikely -- which makes this an even worse example.)
>
> Alan Stern
Yes, so I think if we ensure that the parent device is enabled at a
logical level, and that the power source is active, it would be possible
to do such a thing. I'm guessing this is something not to worry about
too much now; do you think so?
Thanks,
Adam
[-- Attachment #2: Type: text/plain, Size: 171 bytes --]
_______________________________________________
linux-pm mailing list
linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
http://lists.osdl.org/mailman/listinfo/linux-pm
next prev parent reply other threads:[~2005-03-12 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050311084733.GB1705@elf.ucw.cz>
[not found] ` <20050311084733.GB1705-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-11 16:42 ` Some thoughts on suspend/resume development Alan Stern
[not found] ` <Pine.LNX.4.44L0.0503111133040.1203-100000-3WpdWqXrU/qjv4eRiOYp3g@public.gmane.org>
2005-03-12 0:18 ` Adam Belay [this message]
[not found] ` <1110586718.12485.234.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-12 4:42 ` Alan Stern
[not found] <Pine.LNX.4.44L0.0503051036440.22405-100000@netrider.rowland.org>
[not found] ` <Pine.LNX.4.50.0503080831160.31139-100000@monsoon.he.net>
[not found] ` <1110341383.12485.57.camel@localhost.localdomain>
[not found] ` <Pine.LNX.4.50.0503090522140.9502-100000@monsoon.he.net>
[not found] ` <1110405526.12485.130.camel@localhost.localdomain>
[not found] ` <1110405526.12485.130.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-11 17:38 ` Patrick Mochel
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=1110586718.12485.234.camel@localhost.localdomain \
--to=abelay-et1tbqhtxzrqt0dzr+alfa@public.gmane.org \
--cc=linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.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