[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1511202021330.3931@nanos>
Date: Fri, 20 Nov 2015 20:25:14 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: John Stultz <john.stultz@...aro.org>
cc: Grygorii Strashko <grygorii.strashko@...com>,
santosh shilimkar <santosh.shilimkar@...cle.com>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Srinivas Kandagatla <srinivas.kandagatla@...il.com>,
Maxime Coquelin <maxime.coquelin@...com>,
lkml <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, kernel@...inux.com,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>, Felipe Balbi <balbi@...com>,
Tony Lindgren <tony@...mide.com>,
Santosh Shilimkar <ssantosh@...nel.org>,
Marc Zyngier <marc.zyngier@....com>
Subject: Re: [PATCH v2] clocksource: arm_global_timer: fix suspend resume
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists