From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: versatile: enable the right LEDs
Date: Tue, 5 Jan 2016 15:02:09 +0100 [thread overview]
Message-ID: <1452002529-3335-3-git-send-email-linus.walleij@linaro.org> (raw)
In-Reply-To: <1452002529-3335-1-git-send-email-linus.walleij@linaro.org>
The Versatile now only has device tree boot support, and the
device tree version does not support CONFIG_LEDS_VERSATILE.
Instead select CONFIG_LEDS_SYSCON and MFD_SYSCON, so we can
get LEDs support from the same generic driver that drives
most other ARM reference boards.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
arch/arm/configs/versatile_defconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/configs/versatile_defconfig b/arch/arm/configs/versatile_defconfig
index 75ef20462030..295408ea9dc7 100644
--- a/arch/arm/configs/versatile_defconfig
+++ b/arch/arm/configs/versatile_defconfig
@@ -54,6 +54,7 @@ CONFIG_SPI=y
CONFIG_GPIOLIB=y
CONFIG_GPIO_PL061=y
# CONFIG_HWMON is not set
+CONFIG_MFD_SYSCON=y
CONFIG_FB=y
CONFIG_FB_ARMCLCD=y
CONFIG_FRAMEBUFFER_CONSOLE=y
@@ -66,7 +67,7 @@ CONFIG_MMC=y
CONFIG_MMC_ARMMMCI=y
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y
-CONFIG_LEDS_VERSATILE=y
+CONFIG_LEDS_SYSCON=y
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
CONFIG_LEDS_TRIGGER_CPU=y
--
2.4.3
next prev parent reply other threads:[~2016-01-05 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 14:02 [PATCH 0/2] Add LEDs support for the ARM Versatile DT Linus Walleij
2016-01-05 14:02 ` [PATCH 1/2] ARM: versatile: add the syscon LEDs to the DT Linus Walleij
2016-01-05 15:37 ` Rob Herring
2016-01-05 23:24 ` Linus Walleij
2016-01-08 10:47 ` Arnd Bergmann
2016-01-05 14:02 ` Linus Walleij [this message]
2016-01-08 10:46 ` [PATCH 2/2] ARM: versatile: enable the right LEDs Arnd Bergmann
2016-01-08 10:48 ` [PATCH 0/2] Add LEDs support for the ARM Versatile DT Arnd Bergmann
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=1452002529-3335-3-git-send-email-linus.walleij@linaro.org \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.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