Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755247AbbLVM2Y (ORCPT ); Tue, 22 Dec 2015 07:28:24 -0500 Received: from foss.arm.com ([217.140.101.70]:53560 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755191AbbLVM2V (ORCPT ); Tue, 22 Dec 2015 07:28:21 -0500 From: Andre Przywara To: Maxime Ripard , Chen-Yu Tsai , arnd@arndb.de Cc: marc.zyngier@arm.com, catalin.marinas@arm.com, will.deacon@arm.com, linux-sunxi@googlegroups.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [RFC PATCH 5/5] arm64: Introduce Allwinner SoC config option Date: Tue, 22 Dec 2015 12:27:47 +0000 Message-Id: <1450787267-26836-6-git-send-email-andre.przywara@arm.com> X-Mailer: git-send-email 2.5.1 In-Reply-To: <1450787267-26836-1-git-send-email-andre.przywara@arm.com> References: <1450787267-26836-1-git-send-email-andre.przywara@arm.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1086 Lines: 34 To prepare for supporting the Allwinner A64 SoC, introduce a config option to allow compiling Allwinner (aka. sunxi) specific drivers for ARM64. This patch just defines the ARCH_SUNXI symbol to allow Allwinner specific drivers to be selected during kernel configuration. Signed-off-by: Andre Przywara --- arch/arm64/Kconfig.platforms | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms index 4043c35..235e376 100644 --- a/arch/arm64/Kconfig.platforms +++ b/arch/arm64/Kconfig.platforms @@ -1,5 +1,10 @@ menu "Platform selection" +config ARCH_SUNXI + bool "Allwinner sunxi 64-bit SoC Family" + help + This enables support for Allwinner sunxi based SoCs like the A64. + config ARCH_BCM_IPROC bool "Broadcom iProc SoC Family" help -- 2.5.1 -- 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/