devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Vaussard <florian.vaussard@gmail.com>
To: devicetree@vger.kernel.org, Richard Purdie <rpurdie@rpsys.net>,
	Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>, Pavel Machek <pavel@ucw.cz>,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
	Florian Vaussard <florian.vaussard@heig-vd.ch>
Subject: [PATCH v2 0/2] leds: Add driver for NCP5623 3-channel I2C LED driver
Date: Mon, 27 Jun 2016 09:03:08 +0200	[thread overview]
Message-ID: <1467010990-28070-1-git-send-email-florian.vaussard@heig-vd.ch> (raw)

Hello,

This series add a new driver for On Semiconductor NCP5623, a 3-channel I2C
LED driver. It is used in our design to drive a RGB LED.

The first patch introduces the device tree binding, while the second patch
adds the driver itself.

Best regards,
Florian

---
Jacek: I did not addressed your request about dynamic allocation,
as discussed by Pavel and me in the previous thread. Tell me if
you are fine like this. Otherwise I will do the necessary changes.
---
Since v1:
- Adapted the DT binding (led-max-microamp for each LED node)
- Removed underscores from node names in the example
- Use brightness_set_blocking to avoid workqueue
- Introduced LED_to_CMD macro to avoid switch statement
- Various other fixes

Florian Vaussard (2):
  leds: ncp5623: Add device tree binding documentation
  leds: Add driver for NCP5623 3-channel I2C LED driver

 .../devicetree/bindings/leds/leds-ncp5623.txt      |  60 +++++
 drivers/leds/Kconfig                               |  11 +
 drivers/leds/Makefile                              |   1 +
 drivers/leds/leds-ncp5623.c                        | 269 +++++++++++++++++++++
 4 files changed, 341 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/leds/leds-ncp5623.txt
 create mode 100644 drivers/leds/leds-ncp5623.c

-- 
2.5.5

             reply	other threads:[~2016-06-27  7:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27  7:03 Florian Vaussard [this message]
2016-06-27  7:03 ` [PATCH v2 1/2] leds: ncp5623: Add device tree binding documentation Florian Vaussard
2016-06-27  8:11   ` Jacek Anaszewski
2016-06-27  8:30     ` Florian Vaussard
2016-06-27  8:33       ` Jacek Anaszewski
     [not found]         ` <5770E4EB.4040609-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-06-27  8:59           ` Florian Vaussard
2016-06-28 20:56     ` Rob Herring
2016-06-27  7:03 ` [PATCH v2 2/2] leds: Add driver for NCP5623 3-channel I2C LED driver Florian Vaussard
2016-06-27  8:14   ` Jacek Anaszewski
2016-06-27  8:54     ` Florian Vaussard
     [not found]       ` <a16b7031-87db-dcd3-57d2-412e6f707970-EWQkb/GNqlFyDzI6CaY1VQ@public.gmane.org>
2016-06-27  9:12         ` Jacek Anaszewski

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=1467010990-28070-1-git-send-email-florian.vaussard@heig-vd.ch \
    --to=florian.vaussard@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.vaussard@heig-vd.ch \
    --cc=j.anaszewski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=rpurdie@rpsys.net \
    /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).