linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Robinson <pbrobinson@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Peter Robinson <pbrobinson@gmail.com>
Subject: [PATCH 1/2] pinctrl: intel: on enable on x86 arches and COMPILE_TEST
Date: Sun, 27 Dec 2015 12:22:51 +0000	[thread overview]
Message-ID: <1451218972-22156-2-git-send-email-pbrobinson@gmail.com> (raw)
In-Reply-To: <1451218972-22156-1-git-send-email-pbrobinson@gmail.com>

If you select CONFIG_PINCTR for another unrelated architecture
you need to set all the Intel pinctrl options even though they're not
required. Mask them if not required.

Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
---
 drivers/pinctrl/intel/Kconfig | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/pinctrl/intel/Kconfig b/drivers/pinctrl/intel/Kconfig
index 4d2efad..68fa13a 100644
--- a/drivers/pinctrl/intel/Kconfig
+++ b/drivers/pinctrl/intel/Kconfig
@@ -2,6 +2,8 @@
 # Intel pin control drivers
 #
 
+if X86_GENERIC || COMPILE_TEST
+
 config PINCTRL_BAYTRAIL
 	bool "Intel Baytrail GPIO pin control"
 	depends on GPIOLIB && ACPI
@@ -50,3 +52,5 @@ config PINCTRL_SUNRISEPOINT
 	  Sunrisepoint is the PCH of Intel Skylake. This pinctrl driver
 	  provides an interface that allows configuring of PCH pins and
 	  using them as GPIOs.
+
+endif
-- 
2.5.0


  reply	other threads:[~2015-12-27 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-27 12:22 pinctrl: adjust dependencies closer to arch/SoC Peter Robinson
2015-12-27 12:22 ` Peter Robinson [this message]
2015-12-28 12:00   ` [PATCH 1/2] pinctrl: intel: on enable on x86 arches and COMPILE_TEST Mika Westerberg
2015-12-28 12:13     ` Peter Robinson
2015-12-28 12:37       ` Mika Westerberg
2015-12-27 12:22 ` [PATCH 2/2] pinctrl: AMD: depend on Seattle or x86 Peter Robinson
2016-01-05 14:58   ` 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=1451218972-22156-2-git-send-email-pbrobinson@gmail.com \
    --to=pbrobinson@gmail.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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).