From: Daniel Gorsulowski <Daniel.Gorsulowski@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] at91: Add command to control up to 3 GPIO LEDs from the console
Date: Fri, 08 May 2009 07:28:09 +0200 [thread overview]
Message-ID: <4A03C2E9.1010501@esd.eu> (raw)
In-Reply-To: <200905070832.01278.sr@denx.de>
Hi Stefan,
Stefan Roese wrote:
> Hi Daniel,
>
> On Wednesday 06 May 2009, Daniel Gorsulowski wrote:
>> This patch allows any at91 board, implementing the GPIO LED API,
>> to control the LEDs from the console.
>>
>> led [ 1 | 2 | 3 | all ] [ on | off ]
>
> Why limit this to a max of 3 LED's? If this is a generic command (which I like
> btw) then we should support a user/board defined number of LED's. In your case
> it's 3, but the infrastructure should support any number.
>
> More comments below.
>
> <snip>
>
...
>
> I suggest to use something like this here:
>
> led_nr = simple_strtoul(argv[1], NULL, 10);
> if (led_nr > CONFIG_LED_MAX) {
> printf ("Usage:\n%s\n", cmdtp->usage);
> return 1;
> }
>
> if (strcmp(argv[2], "off") == 0) {
> on = 1;
> } else if (strcmp(argv[2], "on") == 0) {
> on = 0;
> } else {
> printf ("Usage:\n%s\n", cmdtp->usage);
> return 1;
> }
>
> user_led(led_nr, on);
>
> No ugly #ifdef's in this case. What do you think?
>
> Best regards,
> Stefan
>
I agree with you.
Please give me some days, to implement your basic approaches.
I've many other things to do and it's not that easy (for me)
to create a tidy patch.
Best regards,
Daniel
next prev parent reply other threads:[~2009-05-08 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 14:21 [U-Boot] [PATCH 1/1] at91: Add command to control up to 3 GPIO LEDs from the console Daniel Gorsulowski
2009-05-06 20:37 ` Wolfgang Denk
2009-05-06 20:40 ` Mike Frysinger
2009-05-07 6:01 ` Daniel Gorsulowski
2009-05-07 7:32 ` Wolfgang Denk
2009-05-08 5:37 ` Daniel Gorsulowski
2009-05-07 6:31 ` Stefan Roese
2009-05-08 5:28 ` Daniel Gorsulowski [this message]
2009-05-08 6:21 ` Stefan Roese
2009-05-14 8:49 ` Daniel Gorsulowski
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=4A03C2E9.1010501@esd.eu \
--to=daniel.gorsulowski@esd.eu \
--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