From: Stephen Boyd <sboyd@codeaurora.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Mark Rutland <mark.rutland@arm.com>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, wxt@rock-chips.com,
dianders@chromium.org
Subject: Re: [PATCH] clocksource: arm_arch_timer: Don't assume clock runs in suspend
Date: Tue, 18 Oct 2016 18:55:37 -0700 [thread overview]
Message-ID: <86354ffe-9757-2a1f-92c9-9602fa08a057@codeaurora.org> (raw)
In-Reply-To: <20161019013612.GA107490@google.com>
On 10/18/2016 06:36 PM, Brian Norris wrote:
> I believe we do not on either rk3288 or rk3399. We'd have to be powering
> off almost the entire system before we'd be able to gate the 24 MHz
> oscillator, AIUI.
>
Great! That avoids a major headache.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-10-19 1:55 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
[not found] ` <57DBA81F.2060404-5wv7dgnIgG8@public.gmane.org>
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
[not found] ` <20161019012441.GW8871-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-10-19 1:36 ` Brian Norris
2016-10-19 1:55 ` Stephen Boyd [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=86354ffe-9757-2a1f-92c9-9602fa08a057@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=briannorris@chromium.org \
--cc=daniel.lezcano@linaro.org \
--cc=dianders@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=tglx@linutronix.de \
--cc=wxt@rock-chips.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