On Tue, 13 Jun 2006, David Brownell wrote:
> > What I mean is:
> >
> > echo -n 2 >/sys/.../4-2/4-2:1.0/power/state
> >
> > does nothing, while
> >
> > echo -n 2 >/sys/.../4-2/power/state
> >
> > calls all the interface drivers' suspend methods and then suspends the
> > device itself.
> > > while a request directed at an interface does nothing (but
> > > returns 0).
> >
> > That seems odd. For example, how is the _device_ ever going to
> > be able to suspend, if the interfaces always stay active???
> >
> > There needs to be some mechanism whereby the interface drivers
> > g
On Tue, 13 Jun 2006, David Brownell wrote:
> > Interesting you should bring this up. As part of my autosuspend
> > development, I decided it would simplify things if devices and their
> > interfaces were always suspended together.
>
> And for such discussions, the canonical example is a USB sp
On Friday 09 June 2006 7:36 am, Alan Stern wrote:
> On Thu, 8 Jun 2006, David Brownell wrote:
>
> > Agreed that with USB at least we know some good things to do which
> > we have not yet done ... like autosuspending devices, and thereby
> > reducing VBUS consumption by factors on the order of 100.
