From: Oleksij Rempel <o.rempel@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 2/4] led: Add blink/flash to led command
Date: Sat, 11 Mar 2017 15:02:35 +0100 [thread overview]
Message-ID: <20170311140237.6958-2-o.rempel@pengutronix.de> (raw)
In-Reply-To: <20170311140237.6958-1-o.rempel@pengutronix.de>
From: Sascha Hauer <s.hauer@pengutronix.de>
The LED framework now supports blinking/flashing LEDs, so
add this functionality to the led command.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
commands/led.c | 44 +++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 43 insertions(+), 1 deletion(-)
diff --git a/commands/led.c b/commands/led.c
index 354f74d..a53f0df 100644
--- a/commands/led.c
+++ b/commands/led.c
@@ -29,6 +29,44 @@ static int do_led(int argc, char *argv[])
unsigned long value;
struct led *led;
int ret;
+ int opt;
+ int flash = 0, blink = 0;
+ int blink_on_ms = 500;
+ int blink_off_ms = 500;
+
+ while ((opt = getopt(argc, argv, "fb")) > 0) {
+ switch(opt) {
+ case 'f':
+ flash = 1;
+ break;
+ case 'b':
+ blink = 1;
+ break;
+ }
+ }
+
+ if (flash || blink) {
+ int args = argc - optind;
+
+ if (!args || (flash && blink))
+ return COMMAND_ERROR_USAGE;
+
+ led = led_by_name_or_number(argv[optind]);
+ if (!led) {
+ printf("no such LED: %s\n", argv[optind]);
+ return 1;
+ }
+
+ if (args > 1)
+ blink_on_ms = simple_strtoul(argv[optind + 1], NULL, 0);
+ if (args > 2)
+ blink_off_ms = simple_strtoul(argv[optind + 2], NULL, 0);
+
+ if (flash)
+ return led_flash(led, blink_on_ms);
+ if (blink)
+ return led_blink(led, blink_on_ms, blink_off_ms);
+ }
if (argc == 1) {
int i = 0;
@@ -73,9 +111,13 @@ static int do_led(int argc, char *argv[])
BAREBOX_CMD_HELP_START(led)
BAREBOX_CMD_HELP_TEXT("Control the value of a LED. The exact meaning of VALUE is unspecified,")
BAREBOX_CMD_HELP_TEXT("it can be a brightness, or a color. Most often a value of '1' means on")
-BAREBOX_CMD_HELP_TEXT("and '0' means off.")
+BAREBOX_CMD_HELP_TEXT("and '0' means off. Basic usage is 'led <led> <value>'. LEDs can be given")
+BAREBOX_CMD_HELP_TEXT("by name or number.")
BAREBOX_CMD_HELP_TEXT("")
BAREBOX_CMD_HELP_TEXT("Without arguments the available LEDs are listed.")
+BAREBOX_CMD_HELP_TEXT("Options:")
+BAREBOX_CMD_HELP_OPT ("-b <led> [duration-on-ms] [duration-off-ms]", "blink a LED")
+BAREBOX_CMD_HELP_OPT ("-f <led> [duration-ms]", "flash a LED")
BAREBOX_CMD_HELP_END
BAREBOX_CMD_START(led)
--
2.7.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-03-11 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 14:02 [PATCH 1/4] led: Allow blinking/flashing on led level Oleksij Rempel
2017-03-11 14:02 ` Oleksij Rempel [this message]
2017-03-11 14:02 ` [PATCH 3/4] led: trigger: Use led triggers Oleksij Rempel
2017-03-11 14:02 ` [PATCH 4/4] led-trigger: rework Oleksij Rempel
2017-03-11 14:04 ` [PATCH 1/4] led: Allow blinking/flashing on led level Oleksij Rempel
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=20170311140237.6958-2-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=barebox@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