linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: linux-gpio@vger.kernel.org, linus.walleij@linaro.org,
	andy.shevchenko@gmail.com, arnd@arndb.de, rdunlap@infradead.org
Subject: [PATCH] drivers: x86: pcengines-apuv2: fix dependencies
Date: Tue,  5 Mar 2019 01:24:59 +0100	[thread overview]
Message-ID: <1551745499-6687-1-git-send-email-info@metux.net> (raw)

pcengines-apuv2 board driver needs to explicitly select LEDS_CLASS,
INPUT, INPUT_KEYBOARD, so these are automatically defined correctly
(eg. LEDS_CLASS=y if PCENGINES_APU2=y)

Cc: linux-gpio@vger.kernel.org
Cc: linus.walleij@linaro.org
Cc: andy.shevchenko@gmail.com
Cc: arnd@arndb.de
Cc: rdunlap@infradead.org
Reported-by: kbuild test robot <lkp@intel.com>
Reported-by: arnd@arndb.de
Reported-by: rdunlap@infradead.org
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
---
 drivers/platform/x86/Kconfig | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
index 851ea92..7d53380 100644
--- a/drivers/platform/x86/Kconfig
+++ b/drivers/platform/x86/Kconfig
@@ -1307,7 +1307,10 @@ config PCENGINES_APU2
 	tristate "PC Engines APUv2/3 front button and LEDs driver"
 	select GPIO_AMD_FCH
 	select KEYBOARD_GPIO_POLLED
+	select LEDS_CLASS
 	select LEDS_GPIO
+	select INPUT
+	select INPUT_KEYBOARD
 	help
 	  This driver provides support for the front button and LEDs on
 	  PC Engines APUv2/APUv3 board.
-- 
1.9.1

             reply	other threads:[~2019-03-05  0:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05  0:24 Enrico Weigelt, metux IT consult [this message]
2019-03-05  0:34 ` [PATCH] drivers: x86: pcengines-apuv2: fix dependencies Randy Dunlap

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=1551745499-6687-1-git-send-email-info@metux.net \
    --to=info@metux.net \
    --cc=andy.shevchenko@gmail.com \
    --cc=arnd@arndb.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).