From: Michael Frank <mhf@berlios.de>
To: softwaresuspend-devel@lists.berlios.de
Cc: Pavel Machek <pavel@ucw.cz>,
Patrick Mochel <mochel@digitalimplant.org>,
Nigel Cunningham <ncunningham@linuxmail.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [SoftwareSuspend-devel] 2.6 Suspend PM issues
Date: Sun, 19 Dec 2004 11:14:24 +0800 [thread overview]
Message-ID: <200412191114.25930.mhf@berlios.de> (raw)
In-Reply-To: <20041218075003.GA3015@elf.ucw.cz>
On Saturday 18 December 2004 15:50, Pavel Machek wrote:
> 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.
>
> ...which will not work anyway, swsusp1 or swsusp2. Have you actually
> tried it?
I put suspend support into 2.4 serial driver and use it. It does work.
2.6 serial driver suspend was not working a year ago, have not tried since.
>
> During boot, BIOS is probably going to play with RTS anyway. So no
> matter what you do during suspend, you are probably going to screw it
> up anyway on the boot just before resume.
Luckily not on several of my machines and the linux 2.4 driver at least
does not turn the lines on until resume tells it to do so...
>
> So there are currently 0 examples where extra resume hurts.
still 1 ;) and the same thing would apply to using an USB dongle and
there will be many applications were it hurts as well.
Then, extra resume is not required, it's bad when it causes strain on the
power source (notebook battery low), is a clumsy implementation and slows
suspend process down.
Michael
next prev parent reply other threads:[~2004-12-19 3:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200412171315.50463.mhf@berlios.de>
2004-12-17 5:57 ` [SoftwareSuspend-devel] 2.6 Suspend PM issues Nigel Cunningham
2004-12-17 9:26 ` Pavel Machek
2004-12-18 2:14 ` Michael Frank
2004-12-18 7:42 ` Pavel Machek
2004-12-18 7:50 ` Pavel Machek
2004-12-19 3:14 ` Michael Frank [this message]
2004-12-19 17:36 ` Pavel Machek
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=200412191114.25930.mhf@berlios.de \
--to=mhf@berlios.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=ncunningham@linuxmail.org \
--cc=pavel@ucw.cz \
--cc=softwaresuspend-devel@lists.berlios.de \
/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