[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170125162608.58bfbfb1@endymion>
Date: Wed, 25 Jan 2017 16:26:08 +0100
From: Jean Delvare <jdelvare@...e.de>
To: linux-gpio@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Linus Walleij <linus.walleij@...aro.org>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Takashi Iwai <tiwai@...e.de>
Subject: [PATCH RESEND] pinctrl: intel: Turn Baytrail support to tristate
The pinctrl-baytrail driver builds just fine as a module so give
users this option.
Signed-off-by: Jean Delvare <jdelvare@...e.de>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: Heikki Krogerus <heikki.krogerus@...ux.intel.com>
Cc: Linus Walleij <linus.walleij@...aro.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
Powered by blists - more mailing lists