From: Thomas Hood <jdthood@mail.com>
To: linux-kernel@vger.kernel.org
Cc: Russell King <rmk@arm.linux.org.uk>
Subject: Re: APM driver patch summary
Date: 19 Dec 2001 08:49:20 -0500 [thread overview]
Message-ID: <1008769762.1156.18.camel@thanatos> (raw)
In-Reply-To: <1008737165.1155.0.camel@thanatos>
In-Reply-To: <1008737165.1155.0.camel@thanatos>
Well, I'm not having any problems with the latest "notify
listeners before drivers" patch, and it does fix the problems
I was having.
I'm not sure that this is an appropriate change for 2.4,
but the decision about whether to put it in is up to Stephen.
In the meantime I will try to keep the patch up to date as
2.4 kernels are released. Definitely it should go into 2.5
though. (The idle fixes, on the other hand, should go into
2.4.)
I've just spent a couple of hours auditing the code and I
haven't found any other problems ( ... not that that proves
anything). One little worry: apm_event_handler() seems to
assume that it is called once per second, and that it will
therefore set APM_STATE_BUSY once every four seconds, as the
spec says it should. In fact it gets called a lot more often
than that, as this bit of syslog shows:
------------------------------------------------------
Dec 18 18:00:20 thanatos apmd[266]: apmd_call_proxy: executing:
'/etc/apm/apmd_proxy' 'suspend'
Dec 18 18:00:20 thanatos kernel: apm: setting state busy
Dec 18 18:00:21 thanatos last message repeated 7 times
------------------------------------------------------
However, the APM spec does not put a ceiling on how often
the state is set to BUSY, so it should be okay.
--
Thomas
next parent reply other threads:[~2001-12-19 13:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1008737165.1155.0.camel@thanatos>
2001-12-19 13:49 ` Thomas Hood [this message]
2001-12-23 3:22 APM driver patch summary Thomas Hood
2001-12-23 12:12 ` Andreas Steinmetz
-- strict thread matches above, loose matches on Subject: below --
2001-12-22 3:35 Thomas Hood
2001-12-22 10:42 ` Andreas Steinmetz
2001-12-22 14:44 ` Andreas Steinmetz
2001-12-22 16:13 ` Thomas Hood
2002-01-04 19:56 ` Borsenkow Andrej
2002-01-05 11:58 ` Andreas Steinmetz
2001-12-18 21:46 Thomas Hood
2001-12-18 21:24 Thomas Hood
2001-12-18 21:42 ` Russell King
[not found] ` <E16GYl6-0000nz-00@phalynx>
2001-12-19 10:23 ` Russell King
2001-12-18 1:22 Thomas Hood
2001-12-18 10:02 ` Russell King
2001-12-17 18:28 Thomas Hood
2001-12-17 22:04 ` Russell King
2001-12-17 22:22 ` Russell King
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=1008769762.1156.18.camel@thanatos \
--to=jdthood@mail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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