Messages in this thread | | | Date | Thu, 01 Aug 2013 01:16:36 +0200 | From | Daniel Lezcano <> | Subject | Re: [PATCH v4 0/5] Memory mapped architected timers |
| |
On 08/01/2013 12:38 AM, Stephen Boyd wrote: > On 07/24, Stephen Boyd wrote: >> On 07/22, Mark Rutland wrote: >>> Hi Stephen, >>> >>> On Fri, Jul 19, 2013 at 12:59:27AM +0100, Stephen Boyd wrote: >>>> This patchset adds support for memory mapped architected timers. We >>>> don't have any other global broadcast timer in our system, so we use the >>>> mmio timer during low power modes. The first patch changes the register >>>> accessor to an enum per Thomas' request. The second patch is the binding. >>>> The next two patches lay some groundwork so that the last patch is simpler. >>>> The final patch adds support for mmio timers. >>>> >>>> Patches are based on v3.11-rc1. >>> >>> Be aware that as of v3.11-rc2 this doesn't cleanly apply, as the >>> __cpuinit removal broke the final patch's context in a couple of places. >>> It would be nice to get rid of the new cpuinit additions too... >>> >>> With that cleaned up locally, I've gave this a spin on tc2 and a >>> Foundation model to test the cp15/system timers, hotplugging CPUs and >>> running a basic test (`time sleep 5`). That all seems to work. >>> >>> Unfortunately I have no way of testing the memory-mapped timer support, >>> but I trust you've tested that locally. >>> >>> For the series: >>> >>> Acked-by: Mark Rutland <mark.rutland@arm.com> >>> >> >> Thanks Mark. >> >> Daniel, can you pick up these patches please? >> > > Ping Daniel?
Applied to my tree as 3.12 material
Thanks -- Daniel
-- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |