From: mattias.wallin@stericsson.com (Mattias Wallin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/3] clocksource: add db8500 PRCMU timer
Date: Thu, 2 Jun 2011 12:18:35 +0200 [thread overview]
Message-ID: <4DE7637B.3060901@stericsson.com> (raw)
In-Reply-To: <20110602094622.GS3660@n2100.arm.linux.org.uk>
On 06/02/2011 11:46 AM, Russell King - ARM Linux wrote:
> Why don't we just find a way of fixing sched_clock so that the value
> doesn't reset over a suspend/resume cycle?
Even if the value isn't reset during suspend/resume we want the
clocksource to keep counting. Or is it ok to have the clocksource stop
or freeze during suspend?
Then we have cpuidle. Is it ok to stop/freeze the timer during cpuidle
sleep states?
My view is that sched_clock and the clocksource read should return the
time since boot and keep counting during sleep and suspend. (In this
case we use the same timer for both sched_clk and clocksource.)
> IOW, lets fix the problem
> for_everyone_ rather than only fixing it for one platform at a time.
I agree that fixing it for everyone would be better and I can give it a
try if I get pointed in the right direction.
WARNING: multiple messages have this Message-ID (diff)
From: Mattias Wallin <mattias.wallin@stericsson.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCHv2 0/3] clocksource: add db8500 PRCMU timer
Date: Thu, 2 Jun 2011 12:18:35 +0200 [thread overview]
Message-ID: <4DE7637B.3060901@stericsson.com> (raw)
In-Reply-To: <20110602094622.GS3660@n2100.arm.linux.org.uk>
On 06/02/2011 11:46 AM, Russell King - ARM Linux wrote:
> Why don't we just find a way of fixing sched_clock so that the value
> doesn't reset over a suspend/resume cycle?
Even if the value isn't reset during suspend/resume we want the
clocksource to keep counting. Or is it ok to have the clocksource stop
or freeze during suspend?
Then we have cpuidle. Is it ok to stop/freeze the timer during cpuidle
sleep states?
My view is that sched_clock and the clocksource read should return the
time since boot and keep counting during sleep and suspend. (In this
case we use the same timer for both sched_clk and clocksource.)
> IOW, lets fix the problem
> for_everyone_ rather than only fixing it for one platform at a time.
I agree that fixing it for everyone would be better and I can give it a
try if I get pointed in the right direction.
next prev parent reply other threads:[~2011-06-02 10:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 9:34 [PATCHv2 0/3] clocksource: add db8500 PRCMU timer Mattias Wallin
2011-06-02 9:34 ` Mattias Wallin
2011-06-02 9:46 ` Russell King - ARM Linux
2011-06-02 9:46 ` Russell King - ARM Linux
2011-06-02 10:18 ` Mattias Wallin [this message]
2011-06-02 10:18 ` Mattias Wallin
2011-06-02 11:01 ` Russell King - ARM Linux
2011-06-02 11:01 ` Russell King - ARM Linux
2011-06-02 12:10 ` Mattias Wallin
2011-06-02 12:10 ` Mattias Wallin
2011-06-02 12:57 ` Santosh Shilimkar
2011-06-02 12:57 ` Santosh Shilimkar
2011-06-02 13:04 ` Russell King - ARM Linux
2011-06-02 13:04 ` Russell King - ARM Linux
2011-06-02 13:16 ` Santosh Shilimkar
2011-06-02 13:16 ` Santosh Shilimkar
2011-06-02 18:47 ` john stultz
2011-06-02 18:47 ` john stultz
2011-06-08 13:44 ` Mattias Wallin
2011-06-08 13:44 ` Mattias Wallin
2011-06-09 21:59 ` Russell King - ARM Linux
2011-06-09 21:59 ` Russell King - ARM Linux
2011-06-10 8:54 ` Mattias Wallin
2011-06-10 8:54 ` Mattias Wallin
2011-06-10 16:00 ` Mattias Wallin
2011-06-10 16:00 ` Mattias Wallin
2011-07-10 14:19 ` Russell King - ARM Linux
2011-07-10 14:19 ` Russell King - ARM Linux
2012-02-04 12:30 ` Russell King - ARM Linux
2012-02-04 12:30 ` Russell King - ARM Linux
2012-02-05 15:11 ` Linus Walleij
2012-02-05 15:11 ` Linus Walleij
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=4DE7637B.3060901@stericsson.com \
--to=mattias.wallin@stericsson.com \
--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 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.