From: techping.chan at gmail.com <techping.chan@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/6] cmd: led: add command led list
Date: Mon, 27 Mar 2017 22:38:43 +0800 [thread overview]
Message-ID: <1490625523-11594-6-git-send-email-techping.chan@gmail.com> (raw)
In-Reply-To: <1490625523-11594-1-git-send-email-techping.chan@gmail.com>
From: Ziping Chen <techping.chan@gmail.com>
Add command "led list" to list all led(s) can be operated.
Signed-off-by: Ziping Chen <techping.chan@gmail.com>
---
cmd/led.c | 27 ++++++++++++++++++++++++++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/cmd/led.c b/cmd/led.c
index 3849a79..3f70666 100644
--- a/cmd/led.c
+++ b/cmd/led.c
@@ -230,6 +230,30 @@ int do_led (cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[])
}
if (error_count != 0)
return CMD_RET_FAILURE;
+ } else if (strcmp("list", argv[1]) == 0) {
+ int node, len;
+ match = 1;
+ node = fdt_path_offset(gd->fdt_blob, "/leds");
+ if (node < 0) {
+ printf("led: null led found\n");
+ return CMD_RET_FAILURE;
+ }
+ node = fdt_first_subnode(gd->fdt_blob, node);
+ if (node < 0) {
+ printf("led: null led found\n");
+ return CMD_RET_FAILURE;
+ }
+ printf(" led_name\n");
+ printf("----------------------------------------\n");
+ printf(" %s\n", fdt_getprop(gd->fdt_blob, node,
+ "label", &len));
+ while (1) {
+ node = fdt_next_subnode(gd->fdt_blob, node);
+ if (node < 0)
+ break;
+ printf(" %s\n", fdt_getprop(gd->fdt_blob, node,
+ "label", &len));
+ }
} else if (argc > 2) {
match = 1;
if (dm_led_set(argv[1], cmd) < 0)
@@ -287,6 +311,7 @@ U_BOOT_CMD(
U_BOOT_CMD(
led, 4, 1, do_led,
"operate led(s)",
- "[all|led_name] [on|off|toggle] - sets or clears led(s)"
+ "[all|led_name] [on|off|toggle] - sets or clears led(s)\n"
+ "led list - list all led(s) can be operated"
);
#endif
--
2.7.4
next prev parent reply other threads:[~2017-03-27 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 14:38 [U-Boot] [PATCH 1/6] led: add get_status support for DM LED support techping.chan at gmail.com
2017-03-27 14:38 ` [U-Boot] [PATCH 2/6] led: gpio: add support for get_status function techping.chan at gmail.com
2017-04-01 4:23 ` Simon Glass
2017-03-27 14:38 ` [U-Boot] [PATCH 3/6] cmd: led: rename command enum value techping.chan at gmail.com
2017-04-01 4:22 ` Simon Glass
2017-03-27 14:38 ` [U-Boot] [PATCH 4/6] cmd: led: add enum led_cmd member to support error code return techping.chan at gmail.com
2017-04-01 4:22 ` Simon Glass
2017-03-27 14:38 ` [U-Boot] [PATCH 5/6] cmd: led: add DM-based implementation techping.chan at gmail.com
2017-04-01 4:22 ` Simon Glass
2017-04-05 13:24 ` Ziping Chen
2017-04-09 19:27 ` Simon Glass
2017-04-10 15:06 ` Ziping Chen
2017-04-10 17:35 ` Simon Glass
2017-03-27 14:38 ` techping.chan at gmail.com [this message]
2017-04-01 4:23 ` [U-Boot] [PATCH 1/6] led: add get_status support for DM LED support Simon Glass
2017-04-05 13:20 ` Ziping Chen
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=1490625523-11594-6-git-send-email-techping.chan@gmail.com \
--to=techping.chan@gmail.com \
--cc=u-boot@lists.denx.de \
/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