From: Thomas Gleixner <tglx@linutronix.de>
To: John Stultz <john.stultz@linaro.org>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
santosh shilimkar <santosh.shilimkar@oracle.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@gmail.com>,
Maxime Coquelin <maxime.coquelin@st.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
kernel@stlinux.com,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Felipe Balbi <balbi@ti.com>,
Tony Lindgren <tony@atomide.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH v2] clocksource: arm_global_timer: fix suspend resume
Date: Fri, 20 Nov 2015 20:25:14 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1511202021330.3931@nanos> (raw)
In-Reply-To: <CALAqxLVLQLaAq7fPwJnyOWP_dXV39Dh+QreecxSVY35wi=N0Og@mail.gmail.com>
On Fri, 20 Nov 2015, John Stultz wrote:
> So its unlikely that the hardware both stays running through suspend,
> but also might halt in idle. That would be "unique".
The amount of creativity put into the next variants of differently
broken timers is amazing. So I wouldn't be too surprised if such a
thing actually surfaces.
Thanks,
tglx
next prev parent reply other threads:[~2015-11-20 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 13:57 [PATCH v2] clocksource: arm_global_timer: fix suspend resume Grygorii Strashko
2015-11-20 17:23 ` santosh shilimkar
2015-11-20 18:35 ` Grygorii Strashko
2015-11-20 18:46 ` Marc Zyngier
2015-11-20 18:52 ` santosh shilimkar
2015-11-20 19:12 ` Grygorii Strashko
2015-11-20 19:11 ` John Stultz
2015-11-20 19:09 ` John Stultz
2015-11-20 19:25 ` Thomas Gleixner [this message]
2015-11-20 19:28 ` Grygorii Strashko
2015-11-20 19:32 ` John Stultz
2015-11-20 20:42 ` Grygorii Strashko
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=alpine.DEB.2.11.1511202021330.3931@nanos \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=daniel.lezcano@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=john.stultz@linaro.org \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=maxime.coquelin@st.com \
--cc=santosh.shilimkar@oracle.com \
--cc=srinivas.kandagatla@gmail.com \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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