From: Bevan Weiss <bevan.weiss@gmail.com>
To: lee@kernel.org, pavel@kernel.org, linux-leds@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Bevan Weiss <bevan.weiss@gmail.com>
Subject: [PATCH 1/1] leds/build: allow tristate for leds-syscon
Date: Mon, 2 Mar 2026 17:26:46 +1100 [thread overview]
Message-ID: <20260302062646.938576-2-bevan.weiss@gmail.com> (raw)
In-Reply-To: <20260302062646.938576-1-bevan.weiss@gmail.com>
Having leds-syscon as only bool (y/n) config poses issues with OpenWrt
build system where all boards under a subtarget need to share the same
config options. This results in kernel bloat for all boards when only
a few actually need leds-syscon.
This change allows leds-syscon to be tristate (y/m/n), which means it can
be built as a module for all boards, and then selectively packaged for
their unique rootfs's
Signed-off-by: Bevan Weiss <bevan.weiss@gmail.com>
---
drivers/leds/Kconfig | 4 ++--
drivers/leds/leds-syscon.c | 3 +++
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/leds/Kconfig b/drivers/leds/Kconfig
index 597d7a79c988..ea3afc76a9c6 100644
--- a/drivers/leds/Kconfig
+++ b/drivers/leds/Kconfig
@@ -903,8 +903,8 @@ config LEDS_POWERNV
will be called leds-powernv.
config LEDS_SYSCON
- bool "LED support for LEDs on system controllers"
- depends on LEDS_CLASS=y
+ tristate "LED support for LEDs on system controllers"
+ depends on LEDS_CLASS
depends on MFD_SYSCON
depends on OF
help
diff --git a/drivers/leds/leds-syscon.c b/drivers/leds/leds-syscon.c
index d633ad519d0c..13a9cdc13367 100644
--- a/drivers/leds/leds-syscon.c
+++ b/drivers/leds/leds-syscon.c
@@ -135,3 +135,6 @@ static struct platform_driver syscon_led_driver = {
},
};
builtin_platform_driver(syscon_led_driver);
+
+MODULE_DESCRIPTION("SYSCON LED driver");
+MODULE_LICENSE("GPL");
--
2.43.0
next prev parent reply other threads:[~2026-03-02 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 6:26 [PATCH 0/1] leds/build: allow tristate for leds-syscon Bevan Weiss
2026-03-02 6:26 ` Bevan Weiss [this message]
2026-03-04 10:49 ` Bevan Weiss
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=20260302062646.938576-2-bevan.weiss@gmail.com \
--to=bevan.weiss@gmail.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.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