From: Dan Murphy <dmurphy@ti.com>
To: Milo Kim <milo.kim@ti.com>
Cc: j.anaszewski@samsung.com, linux-leds@vger.kernel.org
Subject: Re: [RFC] leds: lp8860: Support additional features
Date: Fri, 8 Jan 2016 12:33:06 -0600 [thread overview]
Message-ID: <569000E2.2010205@ti.com> (raw)
In-Reply-To: <568FE816.6020804@ti.com>
Milo
On 01/08/2016 10:47 AM, Dan Murphy wrote:
> <snip>
>> - MFD devices
>> lp8860-core will create MFD child devices based on EEPROM value.
>> LED_STRING_CONF[2:0] bits will be read.
>> mode 0: backlight
>> 1: backlight + LED
>> 2: backlight + LED 1, 2
>> 3: backlight + LED 1, 2, 3
>> 4: backlight 1, 2
>> 5: backlight
>> 6: backlight + LED 1, 2
>> 7: LED 1,2,3,4
>> (Please refer to the page 28 and 29 of LP8860 datasheet.
>> http://www.ti.com/lit/ds/symlink/lp8860-q1.pdf)
> Well is this something we can add to the DT and program the EEPROM on the fly for
> implementations that do not require TI firmware?
> Is loading the EEPROM firmware an absolute requirement? Can't the individuals just
> update the EEPROM values in the core file?
> Are all the EEPROM values 0x00? I am not seeing any default values in the TRM.
Ok I found a default table in the data sheet based on part value.
So there may be a need to use the default EEPROM values and adjust
during boot.
Dan
>
>> * Backlight (new)
>> - PWM control mode support
>> - Register backlight device
>>
>> * LED (will be modified)
>> - Unlock/lock EEPROM code will be moved to lp8860-core part
>> - Multiple LED output channels will be supported
>>
>> I'd like to have your opinion prior to creating patches.
>>
>> Jacek,
>> It would be best if you have better idea for this. Thanks!
>>
>> Best regards,
>> Milo
> Dan
>
--
------------------
Dan Murphy
next prev parent reply other threads:[~2016-01-08 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 7:08 [RFC] leds: lp8860: Support additional features Milo Kim
2016-01-08 16:47 ` Dan Murphy
2016-01-08 18:33 ` Dan Murphy [this message]
2016-01-11 0:21 ` Milo Kim
2016-01-12 15:20 ` Jacek Anaszewski
2016-01-12 23:18 ` Milo Kim
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=569000E2.2010205@ti.com \
--to=dmurphy@ti.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=milo.kim@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).