From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] BeagleBoard: Added LED driver
Date: Sun, 07 Nov 2010 22:38:45 +0100 [thread overview]
Message-ID: <20101107213845.69AC81524F3@gemini.denx.de> (raw)
In-Reply-To: <AANLkTim71JeaAkjbHNHfv8FqDvcc5L=ES1XFbwLBmt8r@mail.gmail.com>
Dear Jason Kridner,
In message <AANLkTim71JeaAkjbHNHfv8FqDvcc5L=ES1XFbwLBmt8r@mail.gmail.com> you wrote:
>
> > [sp] I see too many ifdef blocks in the code above. The also seems to be
> > repetitive.
> >
> > Is user really expected to change the u-boot config for each LED > bit/color?
>
> This is the existing architecture in status_led.h. I want to make
> sure this code compiles no matter which of the defines have been set.
>
> > Can this be simplified by one function that takes an argument?
>
> Do you mean set vs. toggle? I think that would be great too, but
> again following an existing definition.
Please don;t stick with bad examples just because they exist.
Please feel free to come up ith an improvement.
If you have time and resources, please feel free to clean up the
status_led code as well.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Don't panic.
next prev parent reply other threads:[~2010-11-07 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 5:53 [U-Boot] [PATCH] BeagleBoard: Added LED driver Jason Kridner
2010-11-05 12:02 ` Premi, Sanjeev
2010-11-05 17:32 ` Jason Kridner
2010-11-07 21:38 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-01 21:02 Jason Kridner
2011-03-02 1:47 ` Thomas Chou
2011-04-18 21:32 ` Paulraj, Sandeep
2011-04-20 22:08 ` Wolfgang Denk
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=20101107213845.69AC81524F3@gemini.denx.de \
--to=wd@denx.de \
--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