From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot,1/2] add generic stubs for GPIO LEDs
Date: Sat, 24 Oct 2015 17:14:51 -0400 [thread overview]
Message-ID: <20151024211451.GG23893@bill-the-cat> (raw)
In-Reply-To: <1440162801-27754-2-git-send-email-bernhard.nortmann@web.de>
On Fri, Aug 21, 2015 at 03:13:20PM +0200, Bernhard Nortmann wrote:
> For boards that support LEDs driven via GPIO (CONFIG_GPIO_LED),
> it may be useful to have some generic stubs (wrapper functions)
> for the "colored" LEDs.
>
> This allows defining STATUS_LED_* values directly to GPIO numbers,
> e.g.: #define STATUS_LED_GREEN 248 /* = PH24 */
>
> To keep those optional, it's probably best to introduce an additional
> configuration setting. I've chosen CONFIG_GPIO_LED_STUBS for that.
> Placing the code in drivers/misc/gpio_led.c also ensures that it
> automatically depends on CONFIG_GPIO_LED too.
>
> Signed-off-by: Bernhard Nortmann <bernhard.nortmann@web.de>
> Reviewed-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151024/2bac70ab/attachment.sig>
next prev parent reply other threads:[~2015-10-24 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 13:13 [U-Boot] [PATCH 0/2] GPIO LED improvements (resend) Bernhard Nortmann
2015-08-21 13:13 ` [U-Boot] [PATCH 1/2] add generic stubs for GPIO LEDs Bernhard Nortmann
2015-08-23 21:21 ` Simon Glass
2015-08-24 9:51 ` Bernhard Nortmann
2015-08-28 15:00 ` Tom Rini
2015-09-01 17:37 ` Bernhard Nortmann
2015-10-24 21:14 ` Tom Rini [this message]
2015-08-21 13:13 ` [U-Boot] [PATCH 2/2] allow LED initialization without STATUS_LED_BOOT Bernhard Nortmann
2015-10-24 21:14 ` [U-Boot] [U-Boot, " Tom Rini
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=20151024211451.GG23893@bill-the-cat \
--to=trini@konsulko.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