From: Biao Huang <biao.huang@mediatek.com>
To: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
Matthias Brugger <matthias.bgg@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: devicetree@vger.kernel.org, srv_heupstream@mediatek.com,
Erin Lo <erin.lo@mediatek.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ARM: mediatek: Add MT2701 config options for mediatek SoCs.
Date: Thu, 26 Nov 2015 16:44:28 +0800 [thread overview]
Message-ID: <1448527472-20651-2-git-send-email-biao.huang@mediatek.com> (raw)
In-Reply-To: <1448527472-20651-1-git-send-email-biao.huang@mediatek.com>
From: Erin Lo <erin.lo@mediatek.com>
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. Add MT2701.
Signed-off-by: Erin Lo <erin.lo@mediatek.com>
---
arch/arm/mach-mediatek/Kconfig | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm/mach-mediatek/Kconfig b/arch/arm/mach-mediatek/Kconfig
index aeece17..37dd438 100644
--- a/arch/arm/mach-mediatek/Kconfig
+++ b/arch/arm/mach-mediatek/Kconfig
@@ -9,6 +9,10 @@ menuconfig ARCH_MEDIATEK
if ARCH_MEDIATEK
+config MACH_MT2701
+ bool "MediaTek MT2701 SoCs support"
+ default ARCH_MEDIATEK
+
config MACH_MT6589
bool "MediaTek MT6589 SoCs support"
default ARCH_MEDIATEK
--
1.7.9.5
next prev parent reply other threads:[~2015-11-26 8:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 8:44 [PATCH 0/5] pinctrl: mediatek: add pinctrl/GPIO/EINT driver for mt2701 Biao Huang
2015-11-26 8:44 ` Biao Huang [this message]
[not found] ` <1448527472-20651-2-git-send-email-biao.huang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-09 22:44 ` [PATCH 1/5] ARM: mediatek: Add MT2701 config options for mediatek SoCs Linus Walleij
2015-11-26 8:44 ` [PATCH 2/5] dt-bindings: mediatek: Modify pinctrl bindings for mt2701 Biao Huang
2015-11-27 20:38 ` Rob Herring
2015-12-08 10:56 ` biao huang
2015-11-26 8:44 ` [PATCH 3/5] pinctrl: dt bindings: Add pinfunc header file " Biao Huang
[not found] ` <1448527472-20651-4-git-send-email-biao.huang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-09 22:47 ` Linus Walleij
2015-11-26 8:44 ` [PATCH 4/5] pinctrl: mediatek: Add Pinctrl/GPIO/EINT driver " Biao Huang
2015-12-09 22:52 ` Linus Walleij
[not found] ` <CACRpkda2vgrVEisH=akc5aj6h4LW+mBTqgbAiF3E=3zcu6A28A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-12-10 2:34 ` biao huang
2015-11-26 8:44 ` [PATCH 5/5] arm: dts: Add pinctrl/GPIO/EINT node " Biao Huang
2015-12-09 22:48 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1448527472-20651-2-git-send-email-biao.huang@mediatek.com \
--to=biao.huang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=erin.lo@mediatek.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox