From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-arm-kernel@lists.infradead.org,
Marc Zyngier <marc.zyngier@arm.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: architected timers: Mark the clockevent with the C3_STOP feature
Date: Wed, 4 Jul 2012 11:26:17 +0100 [thread overview]
Message-ID: <20120704102617.GC16639@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1341395673-29660-1-git-send-email-santosh.shilimkar@ti.com>
On Wed, Jul 04, 2012 at 03:24:33PM +0530, Santosh Shilimkar wrote:
> ARM arch timers stop in low power state and hence can not wakeup CPUs in
> deeper idle states when used as cloc event devices. Marking these clock event
> devices with C3_STOP so that during lowpower states, the tick is managed by
> wakeup capable broadcast timer.
Will tells me that the arch timers don't stop in low power modes, they
just can't produce wakeup events. Apparantly the spec says:
The system counter must be implemented in an always-on power domain.
Use of lower-frequency modes must not affect the implemented accuracy.
Are you sure your above description of the problem is correct?
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: architected timers: Mark the clockevent with the C3_STOP feature
Date: Wed, 4 Jul 2012 11:26:17 +0100 [thread overview]
Message-ID: <20120704102617.GC16639@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1341395673-29660-1-git-send-email-santosh.shilimkar@ti.com>
On Wed, Jul 04, 2012 at 03:24:33PM +0530, Santosh Shilimkar wrote:
> ARM arch timers stop in low power state and hence can not wakeup CPUs in
> deeper idle states when used as cloc event devices. Marking these clock event
> devices with C3_STOP so that during lowpower states, the tick is managed by
> wakeup capable broadcast timer.
Will tells me that the arch timers don't stop in low power modes, they
just can't produce wakeup events. Apparantly the spec says:
The system counter must be implemented in an always-on power domain.
Use of lower-frequency modes must not affect the implemented accuracy.
Are you sure your above description of the problem is correct?
next prev parent reply other threads:[~2012-07-04 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 9:54 [PATCH] ARM: architected timers: Mark the clockevent with the C3_STOP feature Santosh Shilimkar
2012-07-04 9:54 ` Santosh Shilimkar
2012-07-04 9:56 ` Marc Zyngier
2012-07-04 9:56 ` Marc Zyngier
2012-07-04 10:00 ` Shilimkar, Santosh
2012-07-04 10:00 ` Shilimkar, Santosh
2012-07-04 10:26 ` Russell King - ARM Linux [this message]
2012-07-04 10:26 ` Russell King - ARM Linux
2012-07-04 10:41 ` Shilimkar, Santosh
2012-07-04 10:41 ` Shilimkar, Santosh
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=20120704102617.GC16639@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=santosh.shilimkar@ti.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 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.