From: Andrew Morton <akpm@linux-foundation.org>
To: Derek Basehore <dbasehore@chromium.org>
Cc: rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org,
Maxim Levitsky <maximlevitsky@gmail.com>
Subject: Re: [PATCH] Don't disable hpet emulation on suspend
Date: Wed, 10 Apr 2013 16:58:01 -0700 [thread overview]
Message-ID: <20130410165801.ec54e0fdb27e11724f5646bc@linux-foundation.org> (raw)
In-Reply-To: <1365554173-24475-1-git-send-email-dbasehore@chromium.org>
On Tue, 9 Apr 2013 17:36:13 -0700 Derek Basehore <dbasehore@chromium.org> wrote:
> There's a bug where rtc alarms are ignored after the rtc cmos suspends but
> before the system finishes suspend. Since hpet emulation is disabled and it
> still handles the interrupts, a wake event is never registered which is done
> from the rtc layer. This reverts an earlier commit which disables hpet
> emulation. To fix the problem mentioned in that commit, the hpet_rtc_timer_init
> function is called directly on resume.
>
> This reverts commit d1b2efa83fbf7b33919238fa29ef6ab935820103.
>
> ...
>
> --- a/drivers/rtc/rtc-cmos.c
> +++ b/drivers/rtc/rtc-cmos.c
> @@ -804,9 +804,8 @@ static int cmos_suspend(struct device *dev)
> mask = RTC_IRQMASK;
> tmp &= ~mask;
> CMOS_WRITE(tmp, RTC_CONTROL);
> + 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);
> }
> spin_unlock_irq(&rtc_lock);
> @@ -870,6 +869,7 @@ static int cmos_resume(struct device *dev)
> rtc_update_irq(cmos->rtc, 1, mask);
> tmp &= ~RTC_AIE;
> hpet_mask_rtc_irq_bit(RTC_AIE);
> + hpet_rtc_timer_init();
> } while (mask & RTC_AIE);
> spin_unlock_irq(&rtc_lock);
> }
huh, so it's been broken for three years.
This calls hpet_rtc_timer_init() under spin_lock_irq() which is OK with
the current implementation. And things should be OK when
CONFIG_HPET_EMULATE_RTC=n.
Maxim, can you please review/test/etc?
prev parent reply other threads:[~2013-04-10 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 0:36 Derek Basehore
2013-04-10 23:58 ` Andrew Morton [this message]
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=20130410165801.ec54e0fdb27e11724f5646bc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=dbasehore@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®