From: Stephen Warren <swarren@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: [RFC 2/3] arm/tegra: Select PINMUX Kconfig variables
Date: Thu, 8 Dec 2011 15:13:09 -0700 [thread overview]
Message-ID: <1323382390-14892-3-git-send-email-swarren@nvidia.com> (raw)
In-Reply-To: <1323382390-14892-1-git-send-email-swarren@nvidia.com>
FIXME: This needs to be rebased on top of the T30 support so that
T20 doesn't select the T30 pinmux driver.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
---
DO NOT MERGE this: The FIXME in the commit comment needs to be addressed
first.
arch/arm/mach-tegra/Kconfig | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-tegra/Kconfig b/arch/arm/mach-tegra/Kconfig
index 91aff7c..b548688 100644
--- a/arch/arm/mach-tegra/Kconfig
+++ b/arch/arm/mach-tegra/Kconfig
@@ -13,6 +13,9 @@ config ARCH_TEGRA_2x_SOC
select USB_ARCH_HAS_EHCI if USB_SUPPORT
select USB_ULPI if USB_SUPPORT
select USB_ULPI_VIEWPORT if USB_SUPPORT
+ select PINCTRL
+ select PINCTRL_TEGRA20
+ select PINCTRL_TEGRA30
help
Support for NVIDIA Tegra AP20 and T20 processors, based on the
ARM CortexA9MP CPU and the ARM PL310 L2 cache controller
--
1.7.0.4
next prev parent reply other threads:[~2011-12-08 22:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 22:13 [RFC 0/3] pinctrl: add a driver for NVIDIA Tegra Stephen Warren
2011-12-08 22:13 ` [RFC 1/3] " Stephen Warren
2011-12-09 14:01 ` Linus Walleij
2011-12-09 17:07 ` Tony Lindgren
2011-12-09 23:49 ` Linus Walleij
2011-12-11 19:36 ` Tony Lindgren
2011-12-09 17:28 ` Stephen Warren
2011-12-09 18:00 ` Tony Lindgren
2011-12-09 23:55 ` Linus Walleij
2011-12-12 18:06 ` Stephen Warren
2011-12-13 0:27 ` Linus Walleij
2011-12-08 22:13 ` Stephen Warren [this message]
2011-12-08 22:13 ` [RFC 3/3] New pinmux testing hacks Stephen Warren
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=1323382390-14892-3-git-send-email-swarren@nvidia.com \
--to=swarren@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.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®