From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: arm_arch_timer: Don't assume clock runs in suspend
Date: Tue, 18 Oct 2016 18:24:41 -0700 [thread overview]
Message-ID: <20161019012441.GW8871@codeaurora.org> (raw)
In-Reply-To: <20161004174903.GA3098@localhost>
On 10/04, Brian Norris wrote:
> Hi Marc,
>
> On Thu, Sep 29, 2016 at 05:08:47PM +0100, Marc Zyngier wrote:
> > On Tue, 27 Sep 2016 18:23:11 -0700
> > Brian Norris <briannorris@chromium.org> wrote:
> > > On Tue, Sep 20, 2016 at 08:47:07AM +0100, Marc Zyngier wrote:
> > > <Begin side note>
> > > rk3288 (ARMv7 system widely used for our Chromebooks) has the same
> > > issue, except the kernel we're using for production (based on v3.14)
> > > doesn't have the following commit, which stopped utilizing the RTC:
> > >
> > > commit 0fa88cb4b82b5cf7429bc1cef9db006ca035754e
> > > Author: Xunlei Pang <pang.xunlei@linaro.org>
> > > Date: Wed Apr 1 20:34:38 2015 -0700
> > >
> > > time, drivers/rtc: Don't bother with rtc_resume() for the nonstop clocksource
> > >
> > > And any mainline testing on rk3288 doesn't see the problem, because
> > > mainline doesn't support its lowest-power sleep modes well enough (see
> > > ROCKCHIP_ARM_OFF_LOGIC_DEEP in arch/arm/mach-rockchip/pm.c).
> >
> > Arghh... So even my favourite Chromebook (from which I'm typing this
> > email) is affected? Not very nice...
>
> Yep. But if you're running mainline, you just get to have high S3 power
> consumption instead!
Just curious, do we enter this state during cpuidle as well? Or
is it only across suspend that the clock stops working?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-10-19 1:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 5:49 [PATCH] clocksource: arm_arch_timer: Don't assume clock runs in suspend Brian Norris
2016-09-16 8:06 ` Marc Zyngier
2016-09-16 8:10 ` Daniel Lezcano
2016-09-19 23:14 ` Brian Norris
2016-09-20 7:47 ` Marc Zyngier
2016-09-28 1:23 ` Brian Norris
2016-09-29 16:08 ` Marc Zyngier
2016-10-04 17:49 ` Brian Norris
2016-10-19 1:24 ` Stephen Boyd [this message]
2016-10-19 1:36 ` Brian Norris
2016-10-19 1:55 ` Stephen Boyd
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=20161019012441.GW8871@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).