All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, maximlevitsky@gmail.com,
	david-b@pacbell.net, hpa@zytor.com, rjw@sisk.pl,
	tglx@linutronix.de, linux-kernel@vger.kernel.org, "Pallipadi,
	Venkatesh" <venkatesh.pallipadi@intel.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: + rtc-disable-hpet-emulation-on-suspend.patch added to -mm tree
Date: Wed, 14 Oct 2009 07:56:39 +0200	[thread overview]
Message-ID: <20091014055639.GA784@elte.hu> (raw)
In-Reply-To: <200910132208.n9DM83xa031357@imap1.linux-foundation.org>


* akpm@linux-foundation.org <akpm@linux-foundation.org> wrote:

> ------------------------------------------------------
> Subject: rtc: disable hpet emulation on suspend
> From: Maxim Levitsky <maximlevitsky@gmail.com>
> 
> I noticed that rtc wont generate interrupts after a resume from disk.
> Here hpet rtc emulation is used.
> 
> Problem is that rtc hpet comparator, isn't reinitialized after resume.
> Easiest way to solve this, is always mask all hpet interrupts on suspend
> This is triggered, when suspending with alarm set.
> 
> 
> Otherwise, hpet driver will think it doesn't need to reinitialize
> the rtc comparator, thus rtc interrupts won't work.
> 
> This emulation isn't need for wakealarm.

> -		hpet_mask_rtc_irq_bit(mask);
>  
> +		/* shut down hpet emulation - we don't need it for alarm */
> +		hpet_mask_rtc_irq_bit(RTC_PIE|RTC_AIE|RTC_UIE);
>  		cmos_checkintr(cmos, tmp);

Would be nice to also unconditionally reinitialize the hpet/rtc after 
resume - regardless of what state we left it in.

Also, are you sure this does not break things like 
CONFIG_PM_TEST_SUSPEND=y which rely on wakealarm?

	Ingo

  reply	other threads:[~2009-10-14  5:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 22:08 + rtc-disable-hpet-emulation-on-suspend.patch added to -mm tree akpm
2009-10-14  5:56 ` Ingo Molnar [this message]
2009-10-14  6:27   ` Maxim Levitsky
2009-10-14  6:35     ` Ingo Molnar

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=20091014055639.GA784@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=david-b@pacbell.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.