Freescale PFUZE100 PMIC

[Yibin Gong]

>From 'i2cget -y 1 0x8 0', it return the right value on pfuze100 and it should be probed successfully if dts setting is ok, can you double check the dts?

-----Original Message-----
From: John Tobias [mailto:john.tobias.ph at gmail.com] 
Sent: Wednesday, March 12, 2014 10:24 AM
To: Gong Yibin-B38343
Cc: <linux-arm-kernel at lists.infradead.org>; Shawn Guo
Subject: Re: Freescale PFUZE100 PMIC

That is weird... That was the actual log.

But, if I run i2cdetect:

# i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- 11 -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --


# i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- 08 -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --


# i2cget -y 1 0x8 0
0x10

Regards,

john

On Tue, Mar 11, 2014 at 7:11 PM, Yibin Gong <yibin.gong at freescale.com> wrote:
> Ok, but how can we explain the print log?  You mean the below log is not the true?
> pfuze100-regulator 0-0008: unrecognized pfuze chip ID!
>
> -----Original Message-----
> From: John Tobias [mailto:john.tobias.ph at gmail.com]
> Sent: Wednesday, March 12, 2014 10:00 AM
> To: Gong Yibin-B38343
> Cc: <linux-arm-kernel at lists.infradead.org>; Shawn Guo
> Subject: Re: Freescale PFUZE100 PMIC
>
> Hi Yibin,
>
> Sorry for the confusion (I forgot to mention). I was using a custom board where the PMIC is connected to i2c2. The i2c2 bus has 3 slave devices, the two were running Ok. I was running 400000 freq. clock and tried the 100000 as well.
>
> Regards,
>
> john
>
>
> On Tue, Mar 11, 2014 at 6:41 PM, Yibin Gong <yibin.gong at freescale.com> wrote:
>> Hi John,
>>         I'm little confused by your print log  and dts setting about I2C:
>> From your print log "pfuze100-regulator 0-0008:" we can know this i2c device pfuze should be connected in i2c1. But in your dts setting, you put pfuze in i2c2. Please make sure which i2c interface connected with pfuze and make correct setting in dts.
>>
>> -----Original Message-----
>> From: John Tobias [mailto:john.tobias.ph at gmail.com]
>> Sent: Wednesday, March 12, 2014 8:41 AM
>> To: <linux-arm-kernel at lists.infradead.org>; Gong Yibin-B38343; Shawn 
>> Guo
>> Subject: Freescale PFUZE100 PMIC
>>
>> Hi All,
>>
>> I was trying to enable the PFUZE100 regulator driver
>> (pfuze100-regulator) on linux 3.13.0. The PMIC is connected to the
>> i2c2 bus.
>>
>> &i2c2 {
>>    .....
>>    pmic: pfuze100 at 08 {
>>           compatible = "fsl,pfuze100";
>>           reg = <0x08>;
>>
>>           regulators {
>>                  ......
>>           };
>>    };
>> }
>>
>> After loading the driver, I was getting an error:
>> pfuze100-regulator 0-0008: unrecognized pfuze chip ID!
>>
>> Then, I printed the return value of i2c_transfer function and got -5.
>>
>>
>> Is there anything that I forgot?. I tried to use the i2cget in userspace and I was able to communicate it to the device.
>>
>> Regards,
>>
>> john
>>
>>
>
>