From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 1/1] ARM64: defconfig: enable the leds-pwm driver and default-on trigger
Date: Fri, 03 Mar 2017 10:43:14 -0800 [thread overview]
Message-ID: <m2efye2ocd.fsf@baylibre.com> (raw)
In-Reply-To: <20170219222325.7085-2-martin.blumenstingl@googlemail.com> (Martin Blumenstingl's message of "Sun, 19 Feb 2017 23:23:25 +0100")
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> This enables the leds-pwm driver to support LEDs which are PWM-powered
> (and thus dimmable). Additionally we have to enable the "default-on"
> trigger - this was not required before because the gpio-leds driver has
> a separate "default-state" property which can be used to enable the LED
> by default.
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Applied to v4.12/defconfig of amlogic tree.
Kevin
> ---
> arch/arm64/configs/defconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 33b744d54739..b36d02ce6154 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -394,8 +394,10 @@ CONFIG_MMC_SUNXI=y
> CONFIG_NEW_LEDS=y
> CONFIG_LEDS_CLASS=y
> CONFIG_LEDS_GPIO=y
> +CONFIG_LEDS_PWM=y
> CONFIG_LEDS_SYSCON=y
> CONFIG_LEDS_TRIGGERS=y
> +CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
> CONFIG_LEDS_TRIGGER_HEARTBEAT=y
> CONFIG_LEDS_TRIGGER_CPU=y
> CONFIG_RTC_CLASS=y
prev parent reply other threads:[~2017-03-03 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 22:23 [PATCH 0/1] ARM64: defconfig: add support for PWM LEDs Martin Blumenstingl
2017-02-19 22:23 ` [PATCH 1/1] ARM64: defconfig: enable the leds-pwm driver and default-on trigger Martin Blumenstingl
2017-03-03 18:43 ` Kevin Hilman [this message]
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=m2efye2ocd.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@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;
as well as URLs for NNTP newsgroup(s).