From: Jean-Jacques Hiblot <jjhiblot@ti.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: mark.rutland@arm.com, daniel.thompson@linaro.org,
jingoohan1@gmail.com, tomi.valkeinen@ti.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
robh+dt@kernel.org, jacek.anaszewski@gmail.com,
lee.jones@linaro.org, linux-leds@vger.kernel.org, dmurphy@ti.com
Subject: Re: [PATCH 0/4] Add a generic driver for LED-based backlight
Date: Fri, 5 Jul 2019 13:34:45 +0200 [thread overview]
Message-ID: <e8f24c10-1d88-139c-d0ee-500473ecbe53@ti.com> (raw)
In-Reply-To: <20190705101434.fw5rpctnqt6dwg6e@devuan>
On 05/07/2019 12:14, Pavel Machek wrote:
> On Mon 2019-07-01 17:14:19, Jean-Jacques Hiblot wrote:
>>
>> This series takes it from there and implements the binding that was
>> discussed in https://patchwork.kernel.org/patch/7293991/. In this new
>> binding the backlight device is a child of the LED controller instead of
>> being another platform device that uses a phandle to reference a LED.
> Other option would be to have backlight trigger. What are
> advantages/disadvantages relative to that?
I don't know how this would fit in the model where multiple panels are
used, each with its own backlight.
Also the notification is only about blanking.
> Pavel
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Jacques Hiblot <jjhiblot@ti.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: <jacek.anaszewski@gmail.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <lee.jones@linaro.org>,
<daniel.thompson@linaro.org>, <jingoohan1@gmail.com>,
<dmurphy@ti.com>, <linux-leds@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<tomi.valkeinen@ti.com>
Subject: Re: [PATCH 0/4] Add a generic driver for LED-based backlight
Date: Fri, 5 Jul 2019 13:34:45 +0200 [thread overview]
Message-ID: <e8f24c10-1d88-139c-d0ee-500473ecbe53@ti.com> (raw)
Message-ID: <20190705113445.c6qKxLENhqchUkGVqsUFb5q0ySbJ76iKwGeqOuYpx7E@z> (raw)
In-Reply-To: <20190705101434.fw5rpctnqt6dwg6e@devuan>
On 05/07/2019 12:14, Pavel Machek wrote:
> On Mon 2019-07-01 17:14:19, Jean-Jacques Hiblot wrote:
>>
>> This series takes it from there and implements the binding that was
>> discussed in https://patchwork.kernel.org/patch/7293991/. In this new
>> binding the backlight device is a child of the LED controller instead of
>> being another platform device that uses a phandle to reference a LED.
> Other option would be to have backlight trigger. What are
> advantages/disadvantages relative to that?
I don't know how this would fit in the model where multiple panels are
used, each with its own backlight.
Also the notification is only about blanking.
> Pavel
>
next prev parent reply other threads:[~2019-07-05 11:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 15:14 [PATCH 0/4] Add a generic driver for LED-based backlight Jean-Jacques Hiblot
2019-07-01 15:14 ` [PATCH 1/4] leds: of: create a child device if the LED node contains a "compatible" string Jean-Jacques Hiblot
2019-07-01 15:14 ` [PATCH 2/4] devicetree: Update led binding Jean-Jacques Hiblot
2019-07-01 15:20 ` Dan Murphy
2019-07-01 15:14 ` [PATCH 3/4] backlight: add led-backlight driver Jean-Jacques Hiblot
2019-07-02 9:54 ` Daniel Thompson
2019-07-02 10:59 ` Jean-Jacques Hiblot
2019-07-02 13:04 ` Daniel Thompson
2019-07-02 15:17 ` Jean-Jacques Hiblot
2019-07-03 9:44 ` Daniel Thompson
2019-07-03 10:02 ` Jean-Jacques Hiblot
2019-07-05 10:08 ` Pavel Machek
2019-07-05 10:08 ` Pavel Machek
2019-07-05 10:33 ` Jean-Jacques Hiblot
2019-07-05 10:33 ` Jean-Jacques Hiblot
2019-07-01 15:14 ` [PATCH 4/4] devicetree: Add led-backlight binding Jean-Jacques Hiblot
2019-07-02 9:58 ` Daniel Thompson
2019-07-02 11:11 ` Jean-Jacques Hiblot
2019-07-05 10:11 ` Pavel Machek
2019-07-05 10:11 ` Pavel Machek
2019-07-05 10:14 ` [PATCH 0/4] Add a generic driver for LED-based backlight Pavel Machek
2019-07-05 10:14 ` Pavel Machek
2019-07-05 10:29 ` Daniel Thompson
2019-07-05 10:29 ` Daniel Thompson
2019-07-05 11:34 ` Jean-Jacques Hiblot [this message]
2019-07-05 11:34 ` Jean-Jacques Hiblot
2019-07-05 23:23 ` Sebastian Reichel
2019-07-05 23:23 ` Sebastian Reichel
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=e8f24c10-1d88-139c-d0ee-500473ecbe53@ti.com \
--to=jjhiblot@ti.com \
--cc=daniel.thompson@linaro.org \
--cc=dmurphy@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--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=pavel@ucw.cz \
--cc=robh+dt@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).