From: Franklin S Cooper Jr <fcooper@ti.com>
To: robh+dt@kernel.org, linux@arm.linux.org.uk, ssantosh@kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Franklin S Cooper Jr <fcooper@ti.com>
Subject: [PATCH 2/5] ARM: keystone: defconfig: Enable PINCTRL SINGLE for Keystone 2
Date: Wed, 27 Apr 2016 09:11:45 -0500 [thread overview]
Message-ID: <1461766308-27669-3-git-send-email-fcooper@ti.com> (raw)
In-Reply-To: <1461766308-27669-1-git-send-email-fcooper@ti.com>
Newer Keystone 2 devices utilize pinmuxing. Enable PINCTRL SINGLE
which is used to handle pinmuxing.
Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
---
arch/arm/configs/keystone_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/keystone_defconfig b/arch/arm/configs/keystone_defconfig
index 5bcc9cf..d068421 100644
--- a/arch/arm/configs/keystone_defconfig
+++ b/arch/arm/configs/keystone_defconfig
@@ -208,3 +208,4 @@ CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_ANSI_CPRNG=y
CONFIG_CRYPTO_USER_API_HASH=y
CONFIG_CRYPTO_USER_API_SKCIPHER=y
+CONFIG_PINCTRL_SINGLE=y
--
2.7.0
next prev parent reply other threads:[~2016-04-27 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 14:11 [PATCH 0/5] ARM:Keystone: Add pinmuxing support Franklin S Cooper Jr
2016-04-27 14:11 ` [PATCH 1/5] ARM: Keystone: Enable PINCTRL for Keystone ARCH Franklin S Cooper Jr
2016-04-27 14:11 ` Franklin S Cooper Jr [this message]
2016-04-27 14:11 ` [PATCH 3/5] ARM: dts: k2g: Add pinctrl support Franklin S Cooper Jr
2016-04-27 14:11 ` [PATCH 4/5] ARM: dts: keystone: Header file for pinctrl constants Franklin S Cooper Jr
2016-04-27 14:11 ` [PATCH 5/5] ARM: dts: k2g-evm: Add pinmuxing for UART0 Franklin S Cooper Jr
2016-06-03 18:42 ` [PATCH 0/5] ARM:Keystone: Add pinmuxing support Franklin Cooper Jr.
2016-06-03 18:55 ` Santosh Shilimkar
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=1461766308-27669-3-git-send-email-fcooper@ti.com \
--to=fcooper@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
/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
all inboxes | Powered by JetHome®