All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-pm@vger.kernel.org, linux-rtc@vger.kernel.org,
	rjw@rjwysocki.net, gabriele.mzt@gmail.com
Subject: Re: [PATCH 1/3] rtc: cmos: allow using ACPI for RTC alarm instead of HPET
Date: Thu, 19 Apr 2018 16:05:38 +0200	[thread overview]
Message-ID: <20180419140538.GG7369@piout.net> (raw)
In-Reply-To: <1522072683-3968-1-git-send-email-rui.zhang@intel.com>

Hi,


On 26/03/2018 21:58:01+0800, Zhang Rui wrote:
> It's found that the HPET timer prevents the platform from entering
> Low Power S0 on some new Intel platforms.
> 
> This means that
> 1. users can still use RTC wake Alarm for suspend-to-idle, but the system
>    never enters Low Power S0, which is a waste of power.
> or
> 2. if users want to put the system into Low Power S0, they can not use
>    RTC as the wakeup source.
> 
> To fix this, we need to stop using the HPET timer for wake alarm.
> But disabling CONFIG_HPET_EMULATE_RTC is not an option because HPET
> emulates PIT at the same time, and this is needed on some of these
> platforms.
> 
> Thus, introduce a new mode (use_acpi_alarm) to the rtc_cmos driver,
> so that, even with CONFIG_HPET_EMULATE_RTC enabled, it's still possible to
> use ACPI SCI for RTC Alarm, including UIE/AIE/wkalrm, instead of HPET.
> 
> Only necessary changes are made for the new "use_acpi_alarm" mode, including
> 1. drop all the calls to HPET emulation code, including the HPET irq
>    handler for rtc interrupt.
> 2. enabling/disabling ACPI RTC Fixed event upon RTC UIE/AIE request.
> 3. acknowledge the RTC Alarm in ACPI RTC Fixed event handler.
> 
> There is no functional change made in this patch if the new mode is not
> enabled.
> 
> Note: this "use_acpi_alarm" mode is made based on the assumption that
> ACPI RTC Fixed event is reliable both at runtime and during system wakeup.
> And this has been verified on a couple of platforms I have, including
> a MS Surface Pro 4 (SKL), a Lenovo Yoga 900 (SKL), and a HP 9360 (KBL).
> 
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>
> ---
>  drivers/rtc/rtc-cmos.c | 111 +++++++++++++++++++++++++++++++++++--------------
>  1 file changed, 80 insertions(+), 31 deletions(-)
> 

I've applied the series but it didn't apply cleanly, please check
https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git/log/?h=rtc-next

-- 
Alexandre Belloni, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-04-19 14:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 13:58 [PATCH 1/3] rtc: cmos: allow using ACPI for RTC alarm instead of HPET Zhang Rui
2018-03-26 13:58 ` [PATCH 2/3] rtc: cmos: acknowledge ACPI driven wake alarms upon resume Zhang Rui
2018-03-26 13:58 ` [PATCH 3/3] rtc: cmos: introduce quirks to enable use_acpi_alarm mode Zhang Rui
2018-04-19 14:05 ` Alexandre Belloni [this message]
2018-04-20  5:59   ` [PATCH 1/3] rtc: cmos: allow using ACPI for RTC alarm instead of HPET Zhang Rui
2018-04-20  6:46     ` Alexandre Belloni
2018-04-24 13:15       ` Zhang Rui
2018-04-24 13:30         ` Alexandre Belloni

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=20180419140538.GG7369@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=gabriele.mzt@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@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.