From: "Frédéric Mahé" <frederic.mahe@cirad.fr>
To: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: "Frédéric Mahé" <frederic.mahe@cirad.fr>,
"Alexandre Ghiti" <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH] riscv: defconfig: enable GPIO LEDs and their triggers
Date: Mon, 9 Nov 2026 12:16:33 +0100 [thread overview]
Message-ID: <20261109111637.294236-1-frederic.mahe@cirad.fr> (raw)
Many riscv boards describe gpio-leds in their device tree, 13 of them
with a heartbeat trigger, but defconfig does not enable the LED
subsystem, so these LEDs stay unused.
Enable LEDS_GPIO and the triggers used by in-tree riscv device trees
(heartbeat, disk-activity, default-on), as arm64 defconfig does.
Tested on a Banana Pi BPI-F3: sys-led blinks with the heartbeat trigger.
This patch was prepared with the help of an AI assistant (Claude),
which also ran the build and boot tests.
Signed-off-by: Frédéric Mahé <frederic.mahe@cirad.fr>
---
arch/riscv/configs/defconfig | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/riscv/configs/defconfig b/arch/riscv/configs/defconfig
index 04ae305d5..670380a9f 100644
--- a/arch/riscv/configs/defconfig
+++ b/arch/riscv/configs/defconfig
@@ -245,6 +245,13 @@ CONFIG_MMC_SPI=y
CONFIG_MMC_DW=y
CONFIG_MMC_DW_STARFIVE=y
CONFIG_MMC_SUNXI=y
+CONFIG_NEW_LEDS=y
+CONFIG_LEDS_CLASS=y
+CONFIG_LEDS_GPIO=y
+CONFIG_LEDS_TRIGGERS=y
+CONFIG_LEDS_TRIGGER_DISK=y
+CONFIG_LEDS_TRIGGER_HEARTBEAT=y
+CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_DRV_SUN6I=y
CONFIG_DMADEVICES=y
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.47.3
reply other threads:[~2026-11-09 11:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261109111637.294236-1-frederic.mahe@cirad.fr \
--to=frederic.mahe@cirad.fr \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@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
all inboxes | Powered by JetHome®