From: Anup Patel <anup.patel@broadcom.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Device Tree <devicetree@vger.kernel.org>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>
Cc: 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>,
Florian Fainelli <f.fainelli@gmail.com>,
Yendapally Reddy Dhananjaya Reddy <yrdreddy@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Vikram Prakash <vikramp@broadcom.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Anup Patel <anup.patel@broadcom.com>
Subject: [PATCH 1/6] arm64: Select COMMON_CLK_IPROC, PINCTRL and GPIOLIB for iProc SoCs
Date: Wed, 10 Feb 2016 11:40:46 +0530 [thread overview]
Message-ID: <1455084651-29325-2-git-send-email-anup.patel@broadcom.com> (raw)
In-Reply-To: <1455084651-29325-1-git-send-email-anup.patel@broadcom.com>
We select COMMON_CLK_IPROC, PINCTRL, and GPIOLIB in arm64 Kconfig
for ARCH_BCM_IPROC so that we can use COMMON_CLK, PINCTRL and GPIOLIB
with iProc SoC drivers.
Signed-off-by: Anup Patel <anup.patel@broadcom.com>
Signed-off-by: Ray Jui <rjui@broadcom.com>
Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yrdreddy@broadcom.com>
---
arch/arm64/Kconfig.platforms | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
index 21074f6..e20b50c 100644
--- a/arch/arm64/Kconfig.platforms
+++ b/arch/arm64/Kconfig.platforms
@@ -2,6 +2,9 @@ menu "Platform selection"
config ARCH_BCM_IPROC
bool "Broadcom iProc SoC Family"
+ select COMMON_CLK_IPROC
+ select PINCTRL
+ select ARCH_REQUIRE_GPIOLIB
help
This enables support for Broadcom iProc based SoCs
--
1.9.1
next prev parent reply other threads:[~2016-02-10 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 6:10 [PATCH 0/6] More updates for NS2 DT Anup Patel
2016-02-10 6:10 ` Anup Patel [this message]
2016-02-10 6:10 ` [PATCH 2/6] arm64: dts: Add SDHCI DT node for NS2 Anup Patel
2016-02-10 6:10 ` [PATCH 3/6] arm64: dts: Add ARM SP804 timer DT nodes " Anup Patel
2016-02-10 6:10 ` [PATCH 4/6] dt-bindings: watchdog: Add ARM SP805 DT bindings Anup Patel
2016-02-10 22:08 ` Florian Fainelli
2016-02-12 15:23 ` Rob Herring
2016-02-10 6:10 ` [PATCH 5/6] arm64: dts: Add ARM SP805 watchdog DT node for NS2 Anup Patel
2016-02-10 6:10 ` [PATCH 6/6] arm64: dts: Add PCIe0 and PCIe4 DT nodes " Anup Patel
2016-02-12 23:50 ` [PATCH 0/6] More updates for NS2 DT Florian Fainelli
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=1455084651-29325-2-git-send-email-anup.patel@broadcom.com \
--to=anup.patel@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=vikramp@broadcom.com \
--cc=will.deacon@arm.com \
--cc=yrdreddy@broadcom.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;
as well as URLs for NNTP newsgroup(s).