[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190322221654.GG19425@atomide.com>
Date: Fri, 22 Mar 2019 15:16:54 -0700
From: Tony Lindgren <tony@...mide.com>
To: Dan Murphy <dmurphy@...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
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?
Regards,
Tony
Powered by blists - more mailing lists