linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Jingoo Han <jingoohan1@gmail.com>,
	Lee Jones <lee.jones@linaro.org>
Cc: linux-leds@vger.kernel.org, linux-fbdev@vger.kernel.org,
	Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCHv4 0/3] backlight: led-backlight driver
Date: Thu, 08 Oct 2015 10:09:17 +0000	[thread overview]
Message-ID: <561640CD.8070901@samsung.com> (raw)
In-Reply-To: <561638F2.2010003@ti.com>

On 10/08/2015 11:35 AM, Tomi Valkeinen wrote:
> Hi,
>
> On 30/09/15 12:31, Tomi Valkeinen wrote:
>> This series aims to add a led-backlight driver, similar to pwm-backlight, but
>> using a LED class device underneath.
>>
>> LED framework has no support for DT or getting a LED class driver from another
>> kernel driver, so I added minimal functionality to led-class to get
>> led-backlight working.
>>
>> Changes to v3:
>> - Change a comment to refer to of_led_get()
>>
>> Changes to v2:
>> - power supply is now optional
>> - cosmetic changes
>> - no-op function for led_put() when !CONFIG_LEDS_CLASS
>>
>> Changes to v1:
>> - Split LED OF parts into separate .h and .c files
>> - Check for CONFIG_OF and CONFIG_LEDS_CLASS where relevant to leave unused code
>>    out.
>> - Improved error prints and comments a bit
>> - Added put_device() into led_put(), as the device was gotten from
>>    class_find_device() which requires a put_device() call.
>>
>>   Tomi
>>
>> Tomi Valkeinen (3):
>>    leds: Add of_led_get() and led_put()
>>    backlight: add led-backlight driver
>>    devicetree: Add led-backlight binding
>>
>>   .../bindings/video/backlight/led-backlight.txt     |  30 +++
>>   drivers/leds/Makefile                              |   6 +-
>>   drivers/leds/led-class.c                           |  13 +-
>>   drivers/leds/led-of.c                              |  85 +++++++
>>   drivers/leds/leds.h                                |   1 +
>>   drivers/video/backlight/Kconfig                    |   7 +
>>   drivers/video/backlight/Makefile                   |   1 +
>>   drivers/video/backlight/led_bl.c                   | 246 +++++++++++++++++++++
>>   include/linux/leds.h                               |  10 +
>>   include/linux/of_leds.h                            |  26 +++
>>   10 files changed, 423 insertions(+), 2 deletions(-)
>>   create mode 100644 Documentation/devicetree/bindings/video/backlight/led-backlight.txt
>>   create mode 100644 drivers/leds/led-of.c
>>   create mode 100644 drivers/video/backlight/led_bl.c
>>   create mode 100644 include/linux/of_leds.h
>
> There's been no more comments on this. Should this be merged via led or
> backlight trees?
>
> Possible conflicts probably happen on the led side, as this changes the
> led core files, so perhaps that's easier way?

Yes, it would be better to merge it via LED tree, also because the
driver being added depends on drivers/leds/led-of.c which is introduced
in this set. Obviously I need backlight maintainer's ack. Jingoo, Lee,
are you ok with this changes?

-- 
Best Regards,
Jacek Anaszewski

      reply	other threads:[~2015-10-08 10:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  9:31 [PATCHv4 0/3] backlight: led-backlight driver Tomi Valkeinen
2015-09-30  9:32 ` [PATCHv4 1/3] leds: Add of_led_get() and led_put() Tomi Valkeinen
2015-09-30 14:29   ` Jacek Anaszewski
2015-09-30  9:32 ` [PATCHv4 2/3] backlight: add led-backlight driver Tomi Valkeinen
2015-10-13  8:43   ` Lee Jones
2015-09-30  9:32 ` [PATCHv4 3/3] devicetree: Add led-backlight binding Tomi Valkeinen
2015-10-13  8:42   ` Lee Jones
2015-10-13 14:21   ` Rob Herring
2015-10-15 12:17     ` Tomi Valkeinen
2015-10-15 13:46       ` Rob Herring
2015-10-15 14:46         ` Tomi Valkeinen
2015-10-15 18:55           ` Rob Herring
2015-10-16 11:42             ` Tomi Valkeinen
2015-10-08  9:35 ` [PATCHv4 0/3] backlight: led-backlight driver Tomi Valkeinen
2015-10-08 10:09   ` 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=561640CD.8070901@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=andrew@lunn.ch \
    --cc=jingoohan1@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).