From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] dm: led: add BCM6358 led driver
Date: Thu, 4 May 2017 10:51:15 -0600 [thread overview]
Message-ID: <CAPnjgZ3zbUnZGgq+VYKvUjkQgesuLEE2Sn0faKYMjWwc9nxo4g@mail.gmail.com> (raw)
In-Reply-To: <1493816961-30595-2-git-send-email-noltari@gmail.com>
On 3 May 2017 at 07:09, Álvaro Fernández Rojas <noltari@gmail.com> wrote:
> This driver is a simplified version of linux/drivers/leds/leds-bcm6358.c
>
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> ---
> drivers/led/Kconfig | 7 ++
> drivers/led/Makefile | 1 +
> drivers/led/led_bcm6358.c | 227 ++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 235 insertions(+)
> create mode 100644 drivers/led/led_bcm6358.c
Similar comments to the earlier LED driver.
Reviewed-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2017-05-04 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 13:09 [U-Boot] [PATCH 0/3] dm: led: add BCM6358 serial leds support Álvaro Fernández Rojas
2017-05-03 13:09 ` [U-Boot] [PATCH 1/3] dm: led: add BCM6358 led driver Álvaro Fernández Rojas
2017-05-04 16:51 ` Simon Glass [this message]
2017-05-03 13:09 ` [U-Boot] [PATCH 2/3] mips: bmips: add bcm6358-led driver support for BCM6358 Álvaro Fernández Rojas
2017-05-04 16:51 ` Simon Glass
2017-05-03 13:09 ` [U-Boot] [PATCH 3/3] mips: bmips: add NeufBox 4 (Sercomm) board Álvaro Fernández Rojas
2017-05-04 16:51 ` Simon Glass
2017-05-07 18:11 ` [U-Boot] [PATCH v2 0/3] dm: led: add BCM6358 serial leds support Álvaro Fernández Rojas
2017-05-07 18:11 ` [U-Boot] [PATCH v2 1/3] dm: led: add BCM6358 led driver Álvaro Fernández Rojas
2017-05-07 18:11 ` [U-Boot] [PATCH v2 2/3] mips: bmips: add bcm6358-led driver support for BCM6358 Álvaro Fernández Rojas
2017-05-07 18:11 ` [U-Boot] [PATCH v2 3/3] mips: bmips: add NeufBox 4 (Sercomm) board Álvaro Fernández Rojas
2017-05-10 14:19 ` [U-Boot] [PATCH 0/3] dm: led: add BCM6358 serial leds support Daniel Schwierzeck
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=CAPnjgZ3zbUnZGgq+VYKvUjkQgesuLEE2Sn0faKYMjWwc9nxo4g@mail.gmail.com \
--to=sjg@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.