From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758082AbbA0KQr (ORCPT ); Tue, 27 Jan 2015 05:16:47 -0500 Received: from cpsmtpb-ews05.kpnxchange.com ([213.75.39.8]:53898 "EHLO cpsmtpb-ews05.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754030AbbA0KQo (ORCPT ); Tue, 27 Jan 2015 05:16:44 -0500 Message-ID: <1422353800.14015.35.camel@x220> Subject: Re: [PATCH v5 1/5] ARM: mediatek: Add config options for mediatek SoCs. From: Paul Bolle To: "Joe. C" Cc: Valentin Rothberg , Matthias Brugger , Hongzhou Yang , Rob Herring , Linus Walleij , Sascha Hauer , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Grant Likely , Catalin Marinas , Vladimir Murzin , Ashwin Chaugule , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , dandan.he@mediatek.com, alan.cheng@mediatek.com, toby.liu@mediatek.com, maoguang.meng@mediatek.com, huang eddie , Jean-Christophe PLAGNIOL-VILLARD Date: Tue, 27 Jan 2015 11:16:40 +0100 In-Reply-To: References: <1421818097-9281-1-git-send-email-hongzhou.yang@mediatek.com> <1421818097-9281-2-git-send-email-hongzhou.yang@mediatek.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 27 Jan 2015 10:16:41.0137 (UTC) FILETIME=[57DC7210:01D03A1A] X-RcptDomain: vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Joe, On Thu, 2015-01-22 at 13:54 +0100, Matthias Brugger wrote: > 2015-01-21 6:28 GMT+01:00 Hongzhou Yang : > > From: Yingjoe Chen > > > > The upcoming MTK pinctrl driver have a big pin table for each SoC > > and we don't want to bloat the kernel binary if we don't need it. > > Add config options so we can build for one SoC only. > > > > Acked-by: Linus Walleij > > Signed-off-by: Yingjoe Chen > > Signed-off-by: Hongzhou Yang > > Applied to v3.20-next/soc This became commit ad8a221e1f49 ("ARM: mediatek: Add config options for mediatek SoCs.") in today's linux-next (ie, next-20150127). I noticed because a script I use to check linux-next spotted a problem with it. > > --- > > arch/arm/mach-mediatek/Kconfig | 22 +++++++++++++++++++++- > > 1 file changed, 21 insertions(+), 1 deletion(-) > > > > diff --git a/arch/arm/mach-mediatek/Kconfig b/arch/arm/mach-mediatek/Kconfig > > index f73f588..f7e463c 100644 > > --- a/arch/arm/mach-mediatek/Kconfig > > +++ b/arch/arm/mach-mediatek/Kconfig > > @@ -1,6 +1,26 @@ > > -config ARCH_MEDIATEK > > +menuconfig ARCH_MEDIATEK > > bool "Mediatek MT65xx & MT81xx SoC" if ARCH_MULTI_V7 > > select ARM_GIC > > select MTK_TIMER > > help > > Support for Mediatek MT65xx & MT81xx SoCs > > + > > +if ARCH_MEDIATEK > > + > > +config MACH_MT6589 > > + bool "MediaTek MT6589 SoCs support" > > + default ARCH_MEDIATEK > > + > > +config MACH_MT6592 > > + bool "MediaTek MT6592 SoCs support" > > + default ARCH_MEDIATEK > > + > > +config MACH_MT8127 > > + bool "MediaTek MT8127 SoCs support" > > + default ARCH_MEDIATEK > > + > > +config MACH_MT8135 > > + bool "MediaTek MT8135 SoCs support" > > + default ARCH_MEDIATEK > > + > > +endif None of these four new MACH_MT* Kconfig symbols are currently used in linux-next. I assume that patches that actually use them (either as a Kconfig symbol or as a CONFIG_* macro) are still pending. Is that correct? Thanks, Paul Bolle From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Bolle Subject: Re: [PATCH v5 1/5] ARM: mediatek: Add config options for mediatek SoCs. Date: Tue, 27 Jan 2015 11:16:40 +0100 Message-ID: <1422353800.14015.35.camel@x220> References: <1421818097-9281-1-git-send-email-hongzhou.yang@mediatek.com> <1421818097-9281-2-git-send-email-hongzhou.yang@mediatek.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Joe. C" Cc: Valentin Rothberg , Matthias Brugger , Hongzhou Yang , Rob Herring , Linus Walleij , Sascha Hauer , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Grant Likely , Catalin Marinas , Vladimir Murzin , Ashwin Chaugule , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , dandan.he-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org, alan.cheng-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org, toby.liu@mediat List-Id: devicetree@vger.kernel.org Joe, On Thu, 2015-01-22 at 13:54 +0100, Matthias Brugger wrote: > 2015-01-21 6:28 GMT+01:00 Hongzhou Yang : > > From: Yingjoe Chen > > > > The upcoming MTK pinctrl driver have a big pin table for each SoC > > and we don't want to bloat the kernel binary if we don't need it. > > Add config options so we can build for one SoC only. > > > > Acked-by: Linus Walleij > > Signed-off-by: Yingjoe Chen > > Signed-off-by: Hongzhou Yang > > Applied to v3.20-next/soc This became commit ad8a221e1f49 ("ARM: mediatek: Add config options for mediatek SoCs.") in today's linux-next (ie, next-20150127). I noticed because a script I use to check linux-next spotted a problem with it. > > --- > > arch/arm/mach-mediatek/Kconfig | 22 +++++++++++++++++++++- > > 1 file changed, 21 insertions(+), 1 deletion(-) > > > > diff --git a/arch/arm/mach-mediatek/Kconfig b/arch/arm/mach-mediatek/Kconfig > > index f73f588..f7e463c 100644 > > --- a/arch/arm/mach-mediatek/Kconfig > > +++ b/arch/arm/mach-mediatek/Kconfig > > @@ -1,6 +1,26 @@ > > -config ARCH_MEDIATEK > > +menuconfig ARCH_MEDIATEK > > bool "Mediatek MT65xx & MT81xx SoC" if ARCH_MULTI_V7 > > select ARM_GIC > > select MTK_TIMER > > help > > Support for Mediatek MT65xx & MT81xx SoCs > > + > > +if ARCH_MEDIATEK > > + > > +config MACH_MT6589 > > + bool "MediaTek MT6589 SoCs support" > > + default ARCH_MEDIATEK > > + > > +config MACH_MT6592 > > + bool "MediaTek MT6592 SoCs support" > > + default ARCH_MEDIATEK > > + > > +config MACH_MT8127 > > + bool "MediaTek MT8127 SoCs support" > > + default ARCH_MEDIATEK > > + > > +config MACH_MT8135 > > + bool "MediaTek MT8135 SoCs support" > > + default ARCH_MEDIATEK > > + > > +endif None of these four new MACH_MT* Kconfig symbols are currently used in linux-next. I assume that patches that actually use them (either as a Kconfig symbol or as a CONFIG_* macro) are still pending. Is that correct? Thanks, Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: pebolle@tiscali.nl (Paul Bolle) Date: Tue, 27 Jan 2015 11:16:40 +0100 Subject: [PATCH v5 1/5] ARM: mediatek: Add config options for mediatek SoCs. In-Reply-To: References: <1421818097-9281-1-git-send-email-hongzhou.yang@mediatek.com> <1421818097-9281-2-git-send-email-hongzhou.yang@mediatek.com> Message-ID: <1422353800.14015.35.camel@x220> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Joe, On Thu, 2015-01-22 at 13:54 +0100, Matthias Brugger wrote: > 2015-01-21 6:28 GMT+01:00 Hongzhou Yang : > > From: Yingjoe Chen > > > > The upcoming MTK pinctrl driver have a big pin table for each SoC > > and we don't want to bloat the kernel binary if we don't need it. > > Add config options so we can build for one SoC only. > > > > Acked-by: Linus Walleij > > Signed-off-by: Yingjoe Chen > > Signed-off-by: Hongzhou Yang > > Applied to v3.20-next/soc This became commit ad8a221e1f49 ("ARM: mediatek: Add config options for mediatek SoCs.") in today's linux-next (ie, next-20150127). I noticed because a script I use to check linux-next spotted a problem with it. > > --- > > arch/arm/mach-mediatek/Kconfig | 22 +++++++++++++++++++++- > > 1 file changed, 21 insertions(+), 1 deletion(-) > > > > diff --git a/arch/arm/mach-mediatek/Kconfig b/arch/arm/mach-mediatek/Kconfig > > index f73f588..f7e463c 100644 > > --- a/arch/arm/mach-mediatek/Kconfig > > +++ b/arch/arm/mach-mediatek/Kconfig > > @@ -1,6 +1,26 @@ > > -config ARCH_MEDIATEK > > +menuconfig ARCH_MEDIATEK > > bool "Mediatek MT65xx & MT81xx SoC" if ARCH_MULTI_V7 > > select ARM_GIC > > select MTK_TIMER > > help > > Support for Mediatek MT65xx & MT81xx SoCs > > + > > +if ARCH_MEDIATEK > > + > > +config MACH_MT6589 > > + bool "MediaTek MT6589 SoCs support" > > + default ARCH_MEDIATEK > > + > > +config MACH_MT6592 > > + bool "MediaTek MT6592 SoCs support" > > + default ARCH_MEDIATEK > > + > > +config MACH_MT8127 > > + bool "MediaTek MT8127 SoCs support" > > + default ARCH_MEDIATEK > > + > > +config MACH_MT8135 > > + bool "MediaTek MT8135 SoCs support" > > + default ARCH_MEDIATEK > > + > > +endif None of these four new MACH_MT* Kconfig symbols are currently used in linux-next. I assume that patches that actually use them (either as a Kconfig symbol or as a CONFIG_* macro) are still pending. Is that correct? Thanks, Paul Bolle