From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
linux-leds@vger.kernel.org
Subject: Re: [PATCH 09/27] leds: Allow compile test of GPIO consumers if !GPIOLIB
Date: Thu, 07 May 2015 14:14:20 +0200 [thread overview]
Message-ID: <554B571C.90901@samsung.com> (raw)
In-Reply-To: <1430843563-18615-9-git-send-email-geert@linux-m68k.org>
On 05/05/2015 06:32 PM, Geert Uytterhoeven wrote:
> The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is
> not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer
> functionality only, can still be compiled if GPIOLIB is not enabled.
>
> Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, where
> appropriate.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Bryan Wu <cooloney@gmail.com>
> Cc: Richard Purdie <rpurdie@rpsys.net>
> Cc: linux-leds@vger.kernel.org
> ---
> drivers/leds/Kconfig | 2 +-
> drivers/leds/trigger/Kconfig | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
> index 966b9605f5f0660c..8161cddc3f8d597a 100644
> --- a/drivers/leds/Kconfig
> +++ b/drivers/leds/Kconfig
> @@ -395,7 +395,7 @@ config LEDS_INTEL_SS4200
> config LEDS_LT3593
> tristate "LED driver for LT3593 controllers"
> depends on LEDS_CLASS
> - depends on GPIOLIB
> + depends on GPIOLIB || COMPILE_TEST
> help
> This option enables support for LEDs driven by a Linear Technology
> LT3593 controller. This controller uses a special one-wire pulse
> diff --git a/drivers/leds/trigger/Kconfig b/drivers/leds/trigger/Kconfig
> index 49794b47b51c498d..5bda6a9b56bbd90b 100644
> --- a/drivers/leds/trigger/Kconfig
> +++ b/drivers/leds/trigger/Kconfig
> @@ -72,7 +72,7 @@ config LEDS_TRIGGER_CPU
> config LEDS_TRIGGER_GPIO
> tristate "LED GPIO Trigger"
> depends on LEDS_TRIGGERS
> - depends on GPIOLIB
> + depends on GPIOLIB || COMPILE_TEST
> help
> This allows LEDs to be controlled by gpio events. It's good
> when using gpios as switches and triggering the needed LEDs
>
Acked-by: Jacek Anaszewski <j.anaszewski@samsung.com>
--
Best Regards,
Jacek Anaszewski
next prev parent reply other threads:[~2015-05-07 12:14 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 14:33 [PATCH 00/27] gpio: Allow compile test of GPIO consumers if !GPIOLIB Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 01/27] drm/bridge: ptn3460: #include <linux/gpio/consumer.h>, depend on GPIOLIB Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 02/27] drm/bridge: ps8622: " Geert Uytterhoeven
2015-06-05 11:21 ` Thierry Reding
2015-05-05 16:32 ` [PATCH 03/27] tpm: Allow compile test of GPIO consumers if !GPIOLIB Geert Uytterhoeven
2015-05-05 20:57 ` Peter Hüwe
2015-05-05 16:32 ` [PATCH 04/27] extcon: " Geert Uytterhoeven
2015-05-06 5:38 ` Chanwoo Choi
2015-05-05 16:32 ` [PATCH 05/27] hwmon: " Geert Uytterhoeven
2015-05-05 19:31 ` Guenter Roeck
2015-05-05 16:32 ` [PATCH 06/27] i2c: " Geert Uytterhoeven
2015-05-12 13:23 ` wsa
2015-05-05 16:32 ` [PATCH 07/27] iio: " Geert Uytterhoeven
2015-05-07 10:37 ` Jonathan Cameron
2015-05-05 16:32 ` [PATCH 08/27] input: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 09/27] leds: " Geert Uytterhoeven
2015-05-06 7:58 ` Jacek Anaszewski
2015-05-06 8:31 ` Geert Uytterhoeven
2015-05-07 12:14 ` Jacek Anaszewski [this message]
2015-05-05 16:32 ` [PATCH 10/27] [media] wl128x: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 11/27] mfd: " Geert Uytterhoeven
2015-05-07 7:37 ` Lee Jones
2015-05-05 16:32 ` [PATCH 12/27] misc: ti-st: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 13/27] mtd: " Geert Uytterhoeven
2015-05-20 22:51 ` Brian Norris
2015-05-05 16:32 ` [PATCH 14/27] net: phy: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 15/27] power: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 16/27] regulator: " Geert Uytterhoeven
2015-05-06 15:20 ` Mark Brown
2015-05-05 16:32 ` [PATCH 17/27] spi: " Geert Uytterhoeven
2015-05-06 15:21 ` Mark Brown
2015-05-05 16:32 ` [PATCH 18/27] staging: android: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 19/27] staging: fbtft: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 20/27] Staging: iio: " Geert Uytterhoeven
2015-05-07 10:38 ` Jonathan Cameron
2015-05-05 16:32 ` [PATCH 21/27] serial: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 22/27] usb: phy: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 23/27] backlight: " Geert Uytterhoeven
2015-05-07 7:37 ` Lee Jones
2015-05-05 16:32 ` [PATCH 24/27] fbdev: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 25/27] w1: " Geert Uytterhoeven
2015-05-05 16:32 ` [PATCH 26/27] watchdog: " Geert Uytterhoeven
2015-05-05 19:31 ` Guenter Roeck
2015-05-05 16:32 ` [PATCH 27/27] net: rfkill: " Geert Uytterhoeven
2015-06-05 11:20 ` [PATCH 01/27] drm/bridge: ptn3460: #include <linux/gpio/consumer.h>, depend on GPIOLIB Thierry Reding
2015-06-05 11:42 ` Geert Uytterhoeven
2015-05-12 10:20 ` [PATCH 00/27] gpio: Allow compile test of GPIO consumers if !GPIOLIB 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=554B571C.90901@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=arnd@arndb.de \
--cc=cooloney@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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