lkml.org 
[lkml]   [2004]   [Dec]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [SoftwareSuspend-devel] 2.6 Suspend PM issues
Hi!

> > > > By what was discussed wrt ALSA issue I gather that you still resume
> > > > _all_ drivers after doing the atomic copy?
> > > >
> > > > As explained earlier this year, if this is the case, it is firstly
> > > > unacceptable as it will result in loss of data in many applications and
> > > > secondly very clumsy.
> > > >
> > > > Example With 2.4 OK, with 2.6 It would fail:
> > > > A datalogger connected to a seral port of a notebook in the field. Data
> > > > transfer in progress which can be put on hold bo lowering RTS (HW
> > > > handshake) but _cannot_ be restarted. Battery low, must suspend to
> > > > change battery, upon resume transfer can continue.
> > > >
> > > > Will this be taken care of?
> >
> > Driver will get enough info in its resume routine ("hey, it is resume,
> > but it is only resume after atomic copy"), so it can ignore the resume
> > if it really needs to.
>
> Each driver has to make the decision when to ignore resume? that would add a
> lot of bloat as well as lots of work to implement and test the changes for
> 100s of drivers...

No, only those drivers where extra resume does some damage. So far I
know about one, and that's your data logging device.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:08    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean