Re: [PATCH] arm: omap4: allow disabling MPU local timer if 32K timer is enabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Feb 11, 2012 at 6:03 PM, Russell King - ARM Linux
<linux@xxxxxxxxxxxxxxxx> 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.

thanks,
-- 
Ming Lei
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux