Message ID | 20130611100457.GB22334@e106331-lin.cambridge.arm.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Tue, Jun 11, 2013 at 11:04:57AM +0100, Mark Rutland wrote: > On Fri, Jun 07, 2013 at 06:39:02PM +0100, Mark Rutland wrote: > > Hi Russell, > > > > Please pull these arch_timer cleanups I've been holding onto for a while. > > They're the same as my last posting [1], but have been rebased to v3.10-rc3. > > > > Thanks, > > Mark. > > > > [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-May/170602.html > > It looks like there was a final ARM_ARCH_TIMER select in multi_v7_defconfig > that's causing architected timer support to not get selected, which the patch > below should fix if appended to the series. I've grepped for ARM_ARCH_TIMER, > and it looks like it's the the last remaining occurence. So what do you want to do with this? Is it needed to be included in your set of patches in your pull request? And I think I remember seeing some other patches related to this change too...
On Mon, Jun 17, 2013 at 02:20:05PM +0100, Russell King - ARM Linux wrote: > On Tue, Jun 11, 2013 at 11:04:57AM +0100, Mark Rutland wrote: > > On Fri, Jun 07, 2013 at 06:39:02PM +0100, Mark Rutland wrote: > > > Hi Russell, > > > > > > Please pull these arch_timer cleanups I've been holding onto for a while. > > > They're the same as my last posting [1], but have been rebased to v3.10-rc3. > > > > > > Thanks, > > > Mark. > > > > > > [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-May/170602.html > > > > It looks like there was a final ARM_ARCH_TIMER select in multi_v7_defconfig > > that's causing architected timer support to not get selected, which the patch > > below should fix if appended to the series. I've grepped for ARM_ARCH_TIMER, > > and it looks like it's the the last remaining occurence. > > So what do you want to do with this? Is it needed to be included in your > set of patches in your pull request? Sorry, I was a bit trigger happy with this patch. It doesn't need to go through with the patches in the pull request, and I think the patches I posted earlier today [1] are a better solution. > > And I think I remember seeing some other patches related to this change > too... Indeed. They should be able to go through separately as there's no strict dependence. [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/177001.html Thanks, Mark.
diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index 2e67a27..c5bdbc9 100644 --- a/arch/arm/configs/multi_v7_defconfig +++ b/arch/arm/configs/multi_v7_defconfig @@ -17,7 +17,7 @@ CONFIG_ARCH_SPEAR13XX=y CONFIG_MACH_SPEAR1310=y CONFIG_MACH_SPEAR1340=y CONFIG_SMP=y -CONFIG_ARM_ARCH_TIMER=y +CONFIG_HAVE_ARM_ARCH_TIMER=y CONFIG_AEABI=y CONFIG_HIGHMEM=y CONFIG_HIGHPTE=y