[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dc24b66c-658e-41aa-c869-42c4a7e812a8@ti.com>
Date: Mon, 25 Mar 2019 07:35:38 -0500
From: Dan Murphy <dmurphy@...com>
To: Tony Lindgren <tony@...mide.com>
CC: <robh+dt@...nel.org>, <jacek.anaszewski@...il.com>, <pavel@....cz>,
<lee.jones@...aro.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-leds@...r.kernel.org>,
Sebastian Reichel <sre@...nel.org>
Subject: Re: [PATCH 4/4] leds: lm3532: Introduce the lm3532 LED driver
Tony
On 3/22/19 5:16 PM, Tony Lindgren wrote:
> Hi,
>
> * Dan Murphy <dmurphy@...com> [190321 14:29]:
>> Introduce the Texas Instruments LM3532 White LED driver.
>> The driver supports ALS configurability or manual brightness
>> control.
>>
>> The driver also supports associating LED strings with specific
>> control banks in a group or as individually controlled strings.
>
> Thanks for getting this driver done. I need help a bit using
> this though.. What's the glue to the drm driver?
>
> I can control the backlight brightness just fine via /sys, and
> backlight shows up as the trigger in /sys/class/leds/lm3532:backlight,
> but /sys/class/backlight is empty and looks like drm can't find it.
>
> Do I need to enable some additional driver(s) to get this to work
> with the drm driver?
>
Can you dump or point to the defconfig?
Dan
> Regards,
>
> Tony
>
--
------------------
Dan Murphy
Powered by blists - more mailing lists