public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dan Murphy <dmurphy@ti.com>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	robh+dt@kernel.org, mark.rutland@arm.com, rpurdie@rpsys.net,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-leds@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
	Daniel Thompson <daniel.thompson@linaro.org>,
	Jingoo Han <jingoohan1@gmail.com>
Subject: Re: [PATCH v3 1/2] dt: bindings: lm3692x: Add bindings for lm3692x LED driver
Date: Wed, 15 Nov 2017 23:23:25 +0100	[thread overview]
Message-ID: <20171115222323.GA18290@amd> (raw)
In-Reply-To: <0a78c883-f074-cc19-3c0c-fc05607400e9@ti.com>

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

Hi!

> > Shouldn't the driver be targeted for backlight subsystem then?
> > 
> > Adding backlight maintainers.
> > 
> 
> Great point!  I was not aware of the backlight subsystem.
> 
> Looks like I need to create a back light version as well.
> 
> Like the lp8788 did since this can be used as a LED driver beyond
> display back lighting.

No, definitely not two drivers for lp8788 hardware.

If that does not yet exist... you want to create glue layer to be able
to use LED as a display backlight. (It may already exist, no idea).

...

Actually or maybe a LED trigger. Just set LED's trigger to "this is
display backlight".

Other solutions are acceptable, but not two hardware drivers.

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-11-15 22:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 19:42 [PATCH v3 1/2] dt: bindings: lm3692x: Add bindings for lm3692x LED driver Dan Murphy
2017-11-15 19:42 ` [PATCH v3 2/2] leds: lm3692x: Introduce LM3692x dual string driver Dan Murphy
2017-11-15 21:12   ` Pavel Machek
2017-11-15 21:25     ` Dan Murphy
2017-11-18 14:19   ` Jacek Anaszewski
2017-11-28 12:53     ` Dan Murphy
2017-11-15 20:15 ` [PATCH v3 1/2] dt: bindings: lm3692x: Add bindings for lm3692x LED driver Jacek Anaszewski
2017-11-15 20:31   ` Dan Murphy
2017-11-15 22:23     ` Pavel Machek [this message]
2017-11-16 20:14       ` Jacek Anaszewski
2017-11-16 21:42         ` Dan Murphy
2017-11-17  2:19           ` Jingoo Han
2017-11-17 11:20           ` Pavel Machek
2017-11-17 16:30             ` Jingoo Han
2017-11-17 18:02               ` Dan Murphy
2017-11-17 23:58                 ` Pavel Machek
2017-11-28 17:27                   ` Dan Murphy
2017-11-16 15:41 ` Rob Herring
2017-11-16 15:45   ` Dan Murphy
2017-11-16 15:58     ` Rob Herring
2017-11-16 20:11     ` dts: fun with chip names " Pavel Machek
2017-11-16 20:36       ` Rob Herring
2017-11-16 21:40         ` Dan Murphy
2017-11-18 14:19 ` 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=20171115222323.GA18290@amd \
    --to=pavel@ucw.cz \
    --cc=daniel.thompson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=jingoohan1@gmail.com \
    --cc=lee.jones@linaro.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 \
    /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