From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap4: allow disabling MPU local timer if 32K timer is enabled
Date: Sat, 11 Feb 2012 10:26:44 +0000 [thread overview]
Message-ID: <20120211102644.GD13587@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CACVXFVNJ=L_H_whTm6AyEc++B=Tw_Jfnzmn-QRYwbbBqiH7H1g@mail.gmail.com>
On Sat, Feb 11, 2012 at 06:19:41PM +0800, Ming Lei wrote:
> On Sat, Feb 11, 2012 at 6:03 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Sat, Feb 11, 2012 at 04:31:25PM +0800, Ming Lei wrote:
> >> With 32K gp timer, tick can be driven and system can run well, so
> >> allow MPU local timer to be disabled if someone requires it, otherwise
> >> MPU local timer is always chosen as the default clock_event_device.
> >
> > The point being?
>
> IMO, 32K gp timer may be more energy-saving than MPU local timer
> because gp timer has much less clock frequency and only half interrupts
> generated in tick mode compared with mpu local timer.
>
> >
> > What if you want to use NO_HZ?
>
> 32K gp timer supports oneshot mode, so it should support NO_HZ. In my test
> .config, NO_HZ is enabled and system can run well.
Have you actually checked the tick rate of your timer in /proc/interrupts?
Have you checked /proc/timer_list to see what mode the system is in?
next prev parent reply other threads:[~2012-02-11 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 8:31 [PATCH] arm: omap4: allow disabling MPU local timer if 32K timer is enabled Ming Lei
2012-02-11 10:03 ` Russell King - ARM Linux
2012-02-11 10:19 ` Ming Lei
2012-02-11 10:26 ` Russell King - ARM Linux [this message]
2012-02-11 12:42 ` Ming Lei
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=20120211102644.GD13587@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).