public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: 2.6.0-test6: APM unable to suspend (the 2.6.0-test2 saga continues)
Date: Wed, 31 Dec 2003 00:00:29 +0100	[thread overview]
Message-ID: <20031230230028.GA778@ucw.cz> (raw)
In-Reply-To: <20031230195303.F13556@flint.arm.linux.org.uk>

On Tue, Dec 30, 2003 at 07:53:03PM +0000, Russell King wrote:
> On Tue, Dec 30, 2003 at 07:40:03PM +0000, Russell King wrote:
> > On Tue, Dec 30, 2003 at 10:47:10AM -0800, Linus Torvalds wrote:
> > > On Tue, 30 Dec 2003, Russell King wrote:
> > > > 
> > > > - i8042_noaux=1 - this doesn't seem to make any difference, although
> > > >   this does appear to leave the CTR set as 0x65, which appears to be
> > > >   the BIOS-set value.
> > > 
> > > Doesn't that leave the kbd mask the same? In particular, it still sets the 
> > > "disable" bit, aka I8042_CTR_KBDDIS later on..
> > 
> > Seems to.  With noaux unset, CTR is set to 0x47.
> > 
> > > What happens if you just define I8042_CTR_KBDDIS to zero?
> > 
> > That still causes suspend to fail.  I've separately tested I8042_CTR_KBDINT
> > set to zero as well, and that still causes failure.
> 
> I just tried this change to i8042.c, and suspend magically started
> working.
> 
> @@ -814,8 +815,8 @@
>         i8042_port_register(&i8042_kbd_values, &i8042_kbd_port);
>   
>         init_timer(&i8042_timer);
> -       i8042_timer.function = i8042_timer_func;
> -       mod_timer(&i8042_timer, jiffies + I8042_POLL_PERIOD);
> +//     i8042_timer.function = i8042_timer_func;
> +//     mod_timer(&i8042_timer, jiffies + I8042_POLL_PERIOD);
>   
>         register_reboot_notifier(&i8042_notifier);
>   
> So it looks like i8042 could do with hooking some power management
> to disable this timer before suspend and resume it afterwards.
> 
> Vojtech?

Agreed. There should already be some in -mm kernels, and I'll make sure
the timer is deleted before suspend. Thanks for finding this.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-12-30 23:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05 16:10 2.6.0-test6: APM unable to suspend (the 2.6.0-test2 saga continues) Russell King
2003-12-28 17:46 ` Russell King
2003-12-28 18:25   ` Russell King
2003-12-28 20:49     ` Linus Torvalds
2003-12-30 11:43       ` Russell King
2003-12-30 16:50         ` Russell King
2003-12-30 18:17           ` Russell King
2003-12-30 18:47             ` Linus Torvalds
2003-12-30 19:40               ` Russell King
2003-12-30 19:53                 ` Russell King
2003-12-30 23:00                   ` Vojtech Pavlik [this message]
2003-12-31  1:45                     ` Dmitry Torokhov
2003-12-31 12:40                       ` Vojtech Pavlik
2004-01-03  3:43                         ` Rusty Russell
2004-01-03 18:28             ` 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=20031230230028.GA778@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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