[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e8f24c10-1d88-139c-d0ee-500473ecbe53@ti.com>
Date: Fri, 5 Jul 2019 13:34:45 +0200
From: Jean-Jacques Hiblot <jjhiblot@...com>
To: Pavel Machek <pavel@....cz>
CC: <jacek.anaszewski@...il.com>, <robh+dt@...nel.org>,
<mark.rutland@....com>, <lee.jones@...aro.org>,
<daniel.thompson@...aro.org>, <jingoohan1@...il.com>,
<dmurphy@...com>, <linux-leds@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
<tomi.valkeinen@...com>
Subject: Re: [PATCH 0/4] Add a generic driver for LED-based backlight
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
>
Powered by blists - more mailing lists