From: john stultz <johnstul@us.ibm.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Pavel Machek <pavel@ucw.cz>, Mikael Pettersson <mikpe@it.uu.se>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] APM resume breakage from 2.6.18-rc1 clocksource changes
Date: Mon, 10 Jul 2006 15:50:16 -0700 [thread overview]
Message-ID: <1152571816.9062.29.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0607110035300.17704@scrub.home>
On Tue, 2006-07-11 at 00:37 +0200, Roman Zippel wrote:
> Hi,
>
> On Mon, 10 Jul 2006, Pavel Machek wrote:
>
> > APM can only keep interrupts disabled on non-IBM machines, presumably
> > due to BIOS problems.
>
> Is it possible to disable the timer interrupt before suspend and just
> reinit the timer afterwards?
The timer interrupt is re-enabled, via the timer_sysclass::resume hook,
while the timekeeping code is re-enabled via the
timekeeping_sysclass::resume hook. The issue being that I'm not sure
there's a defined way to specify the .resume calling order.
The timekeeping_suspended flag is a bit heavy handed, but I think it
might be the safest bet (assuming Mikael finds it works for him).
thanks
-john
next prev parent reply other threads:[~2006-07-10 22:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 23:52 [BUG] APM resume breakage from 2.6.18-rc1 clocksource changes Mikael Pettersson
2006-07-10 7:55 ` Pavel Machek
2006-07-10 17:58 ` john stultz
2006-07-10 18:08 ` Pavel Machek
2006-07-10 18:19 ` john stultz
2006-07-10 22:37 ` Roman Zippel
2006-07-10 22:50 ` john stultz [this message]
2006-07-10 22:59 ` Roman Zippel
2006-07-11 8:07 ` Thomas Gleixner
2006-07-11 9:29 ` Roman Zippel
2006-07-11 11:07 ` Thomas Gleixner
2006-07-11 23:31 ` Roman Zippel
2006-07-12 0:42 ` john stultz
2006-07-13 20:27 ` Thomas Gleixner
2006-07-13 22:05 ` john stultz
2006-07-14 6:56 ` Thomas Gleixner
2006-07-16 15:52 ` Roman Zippel
2006-07-16 15:50 ` Roman Zippel
2006-07-16 16:09 ` Thomas Gleixner
2006-07-16 16:15 ` Roman Zippel
2006-07-10 23:17 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-07-10 23:36 Mikael Pettersson
2006-07-09 23:53 Mikael Pettersson
2006-07-09 20:58 Mikael Pettersson
2006-07-09 21:20 ` john stultz
2006-07-09 21:31 ` Valdis.Kletnieks
2006-07-09 21:44 ` Pavel Machek
2006-07-09 22:51 ` Alan Cox
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=1152571816.9062.29.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=pavel@ucw.cz \
--cc=zippel@linux-m68k.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