From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
cooloney@gmail.com, jogo@openwrt.org, f.fainelli@gmail.com,
cernekee@gmail.com, j.anaszewski@samsung.com
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: [PATCH v2 0/2] BCM6358 LED driver
Date: Thu, 21 May 2015 19:11:08 +0200 [thread overview]
Message-ID: <1432228270-21891-1-git-send-email-noltari@gmail.com> (raw)
In-Reply-To: <1432055578-14089-1-git-send-email-noltari@gmail.com>
These patches add support and documentation for the BCM6358 LED driver, which is present on BCM6358 and BCM6368.
In these SoCs there are Serial LEDs (LEDs connected to a 74hc controller), which can either be controlled by software (exporting the 74hc as spi-gpio) or hardware using this driver.
v1->v2: Introduce changes suggested by Jacek.
Álvaro Fernández Rojas (2):
leds: add DT binding for BCM6358 LED controller
leds: add BCM6358 LED driver
.../devicetree/bindings/leds/leds-bcm6358.txt | 145 ++++++++++++
drivers/leds/Kconfig | 8 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-bcm6358.c | 243 +++++++++++++++++++++
4 files changed, 397 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/leds-bcm6358.txt
create mode 100644 drivers/leds/leds-bcm6358.c
--
1.9.1
next prev parent reply other threads:[~2015-05-21 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 17:12 [PATCH 0/2] BCM6358 LED driver Álvaro Fernández Rojas
2015-05-19 17:12 ` [PATCH 1/2] leds: add DT binding for BCM6358 LED controller Álvaro Fernández Rojas
2015-05-21 11:01 ` Jacek Anaszewski
2015-05-19 17:12 ` [PATCH 2/2] leds: add BCM6358 LED driver Álvaro Fernández Rojas
2015-05-21 10:58 ` Jacek Anaszewski
2015-05-21 17:11 ` Álvaro Fernández Rojas [this message]
2015-05-21 17:11 ` [PATCH v2 1/2] leds: add DT binding for BCM6358 LED controller Álvaro Fernández Rojas
2015-05-22 15:08 ` Jacek Anaszewski
2015-05-22 22:32 ` Bryan Wu
2015-05-21 17:11 ` [PATCH v2 2/2] leds: add BCM6358 LED driver Álvaro Fernández Rojas
2015-05-22 15:10 ` Jacek Anaszewski
2015-05-22 22:34 ` Bryan Wu
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=1432228270-21891-1-git-send-email-noltari@gmail.com \
--to=noltari@gmail.com \
--cc=cernekee@gmail.com \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=jogo@openwrt.org \
--cc=linux-leds@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).