From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Amireddy Mallikarjuna reddy
<mallikarjunax.reddy@linux.intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH] leds: LEDS_BLINK_LGM should depend on X86
Date: Tue, 16 Mar 2021 14:39:46 +0100 [thread overview]
Message-ID: <20210316133946.2376963-1-geert+renesas@glider.be> (raw)
The Intel Lightning Mountain (LGM) Serial Shift Output controller (SSO)
is only present on Intel Lightning Mountain SoCs. Hence add a
dependency on X86, to prevent asking the user about this driver when
configuring a kernel without Intel Lightning Mountain platform support.
While at it, merge the other dependencies into a single statement.
Fixes: c3987cd2bca34ddf ("leds: lgm: Add LED controller driver for LGM SoC")
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
drivers/leds/blink/Kconfig | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/leds/blink/Kconfig b/drivers/leds/blink/Kconfig
index 6dedc58c47b3ea16..852e634002cda7cf 100644
--- a/drivers/leds/blink/Kconfig
+++ b/drivers/leds/blink/Kconfig
@@ -9,10 +9,8 @@ if LEDS_BLINK
config LEDS_BLINK_LGM
tristate "LED support for Intel LGM SoC series"
- depends on GPIOLIB
- depends on LEDS_CLASS
- depends on MFD_SYSCON
- depends on OF
+ depends on X86 || COMPILE_TEST
+ depends on GPIOLIB && LEDS_CLASS && MFD_SYSCON && OF
help
Parallel to serial conversion, which is also called SSO controller,
can drive external shift register for LED outputs.
--
2.25.1
next reply other threads:[~2021-03-16 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 13:39 Geert Uytterhoeven [this message]
2021-04-25 20:57 ` [PATCH] leds: LEDS_BLINK_LGM should depend on X86 Pavel Machek
2021-04-26 7:06 ` Geert Uytterhoeven
2021-04-27 9:12 ` Pavel Machek
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=20210316133946.2376963-1-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=arnd@arndb.de \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mallikarjunax.reddy@linux.intel.com \
--cc=pavel@ucw.cz \
/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).