[U-Boot] [PATCH 2/4] imx: mx6slevk: Add PMIC Pfuze support

[Li Ye-B37916]

Hi Przemyslaw,

On 11/4/2014 10:09 PM, Przemyslaw Marczak wrote:
> Hello Ye Li,
>
> On 11/04/2014 10:37 AM, Li Ye-B37916 wrote:
>>
>> Hi Przemyslaw,
>>
>> On 11/4/2014 5:24 PM, Li Ye-B37916 wrote:
>>> Hi Przemyslaw,
>>>
>>>
>>> On 10/30/2014 6:36 PM, Stefano Babic wrote:
>>>> Hi Ye,
>>>>
>>>> On 10/09/2014 11:08, Ye.Li wrote:
>>>>> Initialize the Pfuze on I2C1 at board late init. The mx6slevk board
>>>>> has Pfuze100 or Pfuze200, print the chip type by parsing the ID.
>>>>>
>>>>> Signed-off-by: Ye.Li <B37916 at freescale.com>
>>>>> ---
>>>> Slowly (sorry for that..) I am checking again all PMIC related patches
>>>> you sent last month. However, these patches do not fit very well in the
>>>> current development.
>>>>
>>>> In the last U-Boot mini summit we get the decision to post new PMIC
>>>> drivers according to the Device Model rules. Przemyslaw is the new
>>>> custodian for PMICs, and he will take care of all related issues
>>>> regarding power management.
>>> Can you share me more information about the new PMIC drivers development that Stefano mentioned above.
>>> 1. Have you completed the APIs define for new PMIC drivers?  If yes, where I can get them.
>>> 2. When will the new PMIC drivers deliver?
>>> 3. Will the PMIC devices already supported in current release stay supported by new PMIC drivers?
>>>
>
> The work on new PMIC framework was temporary on hold.
> Now I'm working on it, but the basic functionality is actually done.
> The first version you can check here:
> https://github.com/bobenstein/u-boot.git
> I need to make some rework, since the i2c is going to support the driver model.
>
> I can now focus on this work. And this will be merged through u-boot-dm - since i2c support is added.
>
> The plan is simple:
> 1) Add new drivers to the present PMIC framework - before merge the new one.
> 2) Add new PMIC framework as a separated piece of code.
> 3) Migrate old drivers and boards to the new framework.
> 4) Remove the old framework without any conflicts.
>
> So it's not a problem if you want add this driver, we add this to the current framework - the migration should be simple and will not cause conflicts.
>
> If you are interested in the new PMIC framework design, please read the doc file added by the patches from the link above.
>
> You can implement just one class(UCLASS_PMIC), and if you need user friendly interface it is welcome to implement also UCLASS_PMIC_REGULATOR.
>
> Please follow the list, maybe I will send the patches at the end of this week.
>
> ... [ snip ] ...
>
>
> Best regards,

My patches don't add any new PMIC driver. The PFUZE100 driver already exists in present u-boot.  We just call the driver to apply new settings for PFUZE100.
According to your plan, can you help to figure out which phase the PMIC development is at now?   I feel my patches won't conflict with your job before phase 3. 
If there is no conflict, I will continue the upstream.

Best regards,
Ye Li

.