[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120817093213.GT11011@atomide.com>
Date: Fri, 17 Aug 2012 02:32:13 -0700
From: Tony Lindgren <tony@...mide.com>
To: Catalin Marinas <catalin.marinas@....com>
Cc: linux-arch@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
Will Deacon <will.deacon@....com>
Subject: Re: [PATCH v2 30/31] arm64: Build infrastructure
* Catalin Marinas <catalin.marinas@....com> [120814 11:00]:
> --- /dev/null
> +++ b/arch/arm64/Kconfig
> @@ -0,0 +1,261 @@
> +config ARM64
> + def_bool y
> + select OF
> + select OF_EARLY_FLATTREE
> + select IRQ_DOMAIN
> + select HAVE_AOUT
> + select HAVE_DMA_ATTRS
> + select HAVE_DMA_API_DEBUG
> + select HAVE_IDE
> + select HAVE_MEMBLOCK
> + select RTC_LIB
> + select SYS_SUPPORTS_APM_EMULATION
> + select HAVE_GENERIC_DMA_COHERENT
> + select GENERIC_IOMAP
> + select HAVE_IRQ_WORK
> + select HAVE_PERF_EVENTS
> + select HAVE_ARCH_TRACEHOOK
> + select PERF_USE_VMALLOC
> + select HAVE_HW_BREAKPOINT if PERF_EVENTS
> + select HAVE_GENERIC_HARDIRQS
> + select GENERIC_HARDIRQS_NO_DEPRECATED
> + select HAVE_SPARSE_IRQ
> + select SPARSE_IRQ
> + select GENERIC_IRQ_SHOW
> + select GENERIC_SMP_IDLE_THREAD
> + select NO_BOOTMEM
> + help
> + ARM 64-bit (AArch64) Linux support.
Anything we should select here for ARM generic timers and
interrupts assuming we can always expect to boot using those?
Other than that:
Acked-by: Tony Lindgren <tony@...mide.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists