On Wed, Jul 16, 2014 at 08:57:21PM +0100, Doug Anderson wrote: > Heiko, > > On Tue, Jul 15, 2014 at 4:01 PM, Heiko Stübner <heiko@xxxxxxxxx> wrote: > > Enable HAVE_ARM_ARCH_TIMER and add a rockchip,rk3288 compatible. > > > > Signed-off-by: Heiko Stuebner <heiko@xxxxxxxxx> > > --- > > arch/arm/mach-rockchip/Kconfig | 1 + > > arch/arm/mach-rockchip/rockchip.c | 1 + > > 2 files changed, 2 insertions(+) > > > > diff --git a/arch/arm/mach-rockchip/Kconfig b/arch/arm/mach-rockchip/Kconfig > > index e4564c2..d168669 100644 > > --- a/arch/arm/mach-rockchip/Kconfig > > +++ b/arch/arm/mach-rockchip/Kconfig > > @@ -6,6 +6,7 @@ config ARCH_ROCKCHIP > > select ARCH_REQUIRE_GPIOLIB > > select ARM_GIC > > select CACHE_L2X0 > > + select HAVE_ARM_ARCH_TIMER > > Do we want to think about allowing someone to enable the A9-based > Rockchip SoCs separately than the A12-based ones? I know it doesn't > hurt to have the arch timer code present on A9 SoCs (it will figure > things out at runtime), but people trying to build an A9-based system > might not want the extra code? More likely, people using the A12-based system won't want the CACHE_L2X0 code (which adds an outer_cache.sync check to wmb()). Will -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
