From: Alexander Shiyan <shc_work@mail.ru>
To: linux-leds@vger.kernel.org
Cc: Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
Philippe Retornaz <philippe.retornaz@epfl.ch>,
Alexander Shiyan <shc_work@mail.ru>
Subject: [PATCH 2/5] leds: leds-mc13783: Use LED core PM functions
Date: Sat, 14 Dec 2013 15:00:48 +0400 [thread overview]
Message-ID: <1387018850-6974-2-git-send-email-shc_work@mail.ru> (raw)
In-Reply-To: <1387018850-6974-1-git-send-email-shc_work@mail.ru>
Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
---
drivers/leds/leds-mc13783.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/leds/leds-mc13783.c b/drivers/leds/leds-mc13783.c
index e61bdb5..670b936 100644
--- a/drivers/leds/leds-mc13783.c
+++ b/drivers/leds/leds-mc13783.c
@@ -184,6 +184,7 @@ static int __init mc13xxx_led_probe(struct platform_device *pdev)
leds->led[i].leds = leds;
leds->led[i].cdev.name = name;
leds->led[i].cdev.default_trigger = trig;
+ leds->led[i].cdev.flags |= LED_CORE_SUSPENDRESUME;
leds->led[i].cdev.brightness_set = mc13xxx_led_set;
leds->led[i].cdev.brightness = LED_OFF;
--
1.8.3.2
next prev parent reply other threads:[~2013-12-14 11:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 11:00 [PATCH 1/5] leds: leds-mc13783: Add MC34708 LED support Alexander Shiyan
2013-12-14 11:00 ` Alexander Shiyan [this message]
2013-12-16 19:53 ` [PATCH 2/5] leds: leds-mc13783: Use LED core PM functions Bryan Wu
2013-12-16 20:06 ` Alexander Shiyan
2013-12-16 20:10 ` Bryan Wu
2013-12-14 11:00 ` [PATCH 3/5] leds: leds-mc13783: Use proper "max_brightness" value for LEDs Alexander Shiyan
2013-12-16 20:28 ` Bryan Wu
2013-12-14 11:00 ` [PATCH 4/5] leds: leds-mc13783: Remove unnecessary cleaning of registers on exit Alexander Shiyan
2013-12-16 20:29 ` Bryan Wu
2013-12-16 19:51 ` [PATCH 1/5] leds: leds-mc13783: Add MC34708 LED support Bryan Wu
2013-12-16 20:00 ` Alexander Shiyan
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=1387018850-6974-2-git-send-email-shc_work@mail.ru \
--to=shc_work@mail.ru \
--cc=cooloney@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=philippe.retornaz@epfl.ch \
--cc=rpurdie@rpsys.net \
/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).