From: Jean Delvare <jdelvare@suse.de>
To: linux-gpio@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>
Subject: [PATCH RESEND] pinctrl: intel: Turn Baytrail support to tristate
Date: Wed, 25 Jan 2017 16:26:08 +0100 [thread overview]
Message-ID: <20170125162608.58bfbfb1@endymion> (raw)
The pinctrl-baytrail driver builds just fine as a module so give
users this option.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>
---
This was discussed almost one year ago, with no clear conclusion, but
also no evidence that the driver can't be built as a module. Is there
any way to push this forward?
drivers/pinctrl/intel/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-4.7-rc7.orig/drivers/pinctrl/intel/Kconfig 2016-07-12 14:35:36.024835842 +0200
+++ linux-4.7-rc7/drivers/pinctrl/intel/Kconfig 2016-07-12 14:35:44.735904433 +0200
@@ -3,7 +3,7 @@
#
config PINCTRL_BAYTRAIL
- bool "Intel Baytrail GPIO pin control"
+ tristate "Intel Baytrail GPIO pin control"
depends on GPIOLIB && ACPI
select GPIOLIB_IRQCHIP
select PINMUX
--
Jean Delvare
SUSE L3 Support
next reply other threads:[~2017-01-25 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 15:26 Jean Delvare [this message]
2017-01-25 16:15 ` [PATCH RESEND] pinctrl: intel: Turn Baytrail support to tristate Andy Shevchenko
2017-01-25 16:16 ` Mika Westerberg
2017-01-26 9:05 ` Jean Delvare
2017-01-26 9:29 ` Mika Westerberg
2017-01-27 8:55 ` Jean Delvare
2017-01-26 8:37 ` Heikki Krogerus
2017-01-26 8:55 ` Linus Walleij
2017-01-26 9:19 ` Mika Westerberg
2017-01-26 9:26 ` Takashi Iwai
2017-01-26 9:38 ` Mika Westerberg
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=20170125162608.58bfbfb1@endymion \
--to=jdelvare@suse.de \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.