From: Sebastian Reichel <sre@kernel.org>
To: Milo Kim <milo.kim@ti.com>
Cc: Lee Jones <lee.jones@linaro.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] backlight: Add TI LMU backlight driver
Date: Mon, 20 Mar 2017 07:54:53 +0100 [thread overview]
Message-ID: <20170320065453.lzof5jxiz2mt2e7c@earth> (raw)
In-Reply-To: <20170320022104.6448-1-milo.kim@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]
Hi,
On Mon, Mar 20, 2017 at 11:21:04AM +0900, Milo Kim wrote:
> This is consolidated driver which supports backlight devices below.
> LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697.
>
> Structure
> ---------
> It consists of two parts - core and data.
>
> Core part supports features below.
> - Backlight subsystem control
> - Channel configuration from DT properties
> - Light dimming effect control: ramp up and down.
> - LMU fault monitor notifier handling
> - PWM brightness control
>
> Data part describes device specific data.
> - Register value configuration for each LMU device
> : initialization, channel configuration, control mode, enable and
> brightness.
> - PWM action configuration
> - Light dimming effect table
> - Option for LMU fault monitor support
>
> Macros for register data
> ------------------------
> All LMU devices have 8-bit based registers. LMU_BL_REG() creates 24-bit
> register value in data part. It consists of address, mask and value.
> On the other hand, register value should be parsed when the driver
> reads/writes data from/to I2C registers. Driver uses LMU_BL_GET_ADDR(),
> LMU_BL_GET_MASK() and LMU_BL_GET_VAL() for this purpose.
>
> Data structure
> --------------
> ti_lmu_bl: Backlight output channel data
> ti_lmu_bl_chip: Backlight device data. One device can have multiple
> backlight channel data.
> ti_lmu_bl_reg: Backlight device register data
> ti_lmu_bl_cfg: Backlight configuration data for each LMU device
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Sebastian Reichel <sre@kernel.org>
> Cc: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Milo Kim <milo.kim@ti.com>
Works on Droid 4:
Tested-by: Sebastian Reichel <sre@kernel.org>
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-20 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 2:21 Milo Kim
2017-03-20 6:54 ` Sebastian Reichel [this message]
2017-03-20 12:03 ` Daniel Thompson
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=20170320065453.lzof5jxiz2mt2e7c@earth \
--to=sre@kernel.org \
--cc=daniel.thompson@linaro.org \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milo.kim@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®