public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Richard Purdie <rpurdie@rpsys.net>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-leds@vger.kernel.org
Subject: Re: [PATCH V2 0/3] leds: add SN3218 LED driver
Date: Fri, 05 Feb 2016 09:15:34 +0100	[thread overview]
Message-ID: <56B45A26.1060002@samsung.com> (raw)
In-Reply-To: <1454612167-8680-1-git-send-email-stefan.wahren@i2se.com>

Hi Stefan,

Patch set applied to the for-next branch of linux-leds.git.

Thanks,
Jacek Anaszewski

On 02/04/2016 07:56 PM, Stefan Wahren wrote:
> This patch series implements support for the Si-En SN3218
> 18 Channel LED Driver connected through I2C. The SN3218
> doesn't support reading so the LED states are cached in a
> regmap.
>
> The driver has been tested on a Raspberry Pi B.
>
> Changes since V1:
>    * add shutdown handler
>    * use defines for modes
>    * remove empty line at the end of binding doc
>    * make sn3218_led_init static
>    * skip setting default max brightness
>    * fix fail sn3218_init
>
> Changes since RFC:
>    * using regmap instead of direct I2C
>    * add new function to init single LED
>    * add module name to Kconfig help
>    * replace of_get_property() with of_property_read_string()
>    * remove lock, leds_state and name from priv structure
>    * drop sn3218 LED name prefix
>    * don't use led_info and led_platform_data
>    * abort probing if no SN3218 is connected or DT invalid
>    * fix some style and text issues
>    * fix license
>    * move i2c_device_id and of_device_id at the end of file
>    * use devm_* calls
>    * use device function as node name in DT binding
>
> Stefan Wahren (3):
>    of: Add vendor prefix for Si-En Technology
>    DT: add binding for SN3218 LED driver
>    leds: add SN3218 LED driver
>
>   .../devicetree/bindings/leds/leds-sn3218.txt       |   41 +++
>   .../devicetree/bindings/vendor-prefixes.txt        |    1 +
>   drivers/leds/Kconfig                               |   12 +
>   drivers/leds/Makefile                              |    1 +
>   drivers/leds/leds-sn3218.c                         |  306 ++++++++++++++++++++
>   5 files changed, 361 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/leds/leds-sn3218.txt
>   create mode 100644 drivers/leds/leds-sn3218.c
>

      parent reply	other threads:[~2016-02-05  8:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 18:56 [PATCH V2 0/3] leds: add SN3218 LED driver Stefan Wahren
2016-02-04 18:56 ` [PATCH V2 1/3] of: Add vendor prefix for Si-En Technology Stefan Wahren
2016-02-04 18:56 ` [PATCH V2 2/3] DT: add binding for SN3218 LED driver Stefan Wahren
2016-02-04 18:56 ` [PATCH V2 3/3] leds: add " Stefan Wahren
2016-02-05  8:15 ` Jacek Anaszewski [this message]

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=56B45A26.1060002@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=stefan.wahren@i2se.com \
    /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