* Freescale PFUZE100 PMIC
@ 2014-03-12 0:41 John Tobias
2014-03-12 1:05 ` Fabio Estevam
2014-03-12 1:41 ` Yibin Gong
0 siblings, 2 replies; 10+ messages in thread
From: John Tobias @ 2014-03-12 0:41 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Freescale PFUZE100 PMIC
2014-03-12 0:41 Freescale PFUZE100 PMIC John Tobias
@ 2014-03-12 1:05 ` Fabio Estevam
2014-03-12 1:41 ` Yibin Gong
1 sibling, 0 replies; 10+ messages in thread
From: Fabio Estevam @ 2014-03-12 1:05 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Mar 11, 2014 at 9:41 PM, John Tobias <john.tobias.ph@gmail.com> wrote:
> After loading the driver, I was getting an error:
> pfuze100-regulator 0-0008: unrecognized pfuze chip ID!
Double check the IOMUX settings for the I2C pins.
You can take a look at imx6sl-evk.dts from linux-next as we do support
pfuze100 there.
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 10+ messages in thread
* Freescale PFUZE100 PMIC
2014-03-12 0:41 Freescale PFUZE100 PMIC John Tobias
2014-03-12 1:05 ` Fabio Estevam
@ 2014-03-12 1:41 ` Yibin Gong
2014-03-12 2:00 ` John Tobias
1 sibling, 1 reply; 10+ messages in thread
From: Yibin Gong @ 2014-03-12 1:41 UTC (permalink / raw)
To: linux-arm-kernel
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@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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Freescale PFUZE100 PMIC
2014-03-12 1:41 ` Yibin Gong
@ 2014-03-12 2:00 ` John Tobias
2014-03-12 2:11 ` Yibin Gong
0 siblings, 1 reply; 10+ messages in thread
From: John Tobias @ 2014-03-12 2:00 UTC (permalink / raw)
To: linux-arm-kernel
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@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@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
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Freescale PFUZE100 PMIC
2014-03-12 2:00 ` John Tobias
@ 2014-03-12 2:11 ` Yibin Gong
2014-03-12 2:23 ` John Tobias
0 siblings, 1 reply; 10+ messages in thread
From: Yibin Gong @ 2014-03-12 2:11 UTC (permalink / raw)
To: linux-arm-kernel
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@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@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@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
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Freescale PFUZE100 PMIC
2014-03-12 2:11 ` Yibin Gong
@ 2014-03-12 2:23 ` John Tobias
2014-03-12 2:30 ` John Tobias
2014-03-12 2:31 ` Yibin Gong
0 siblings, 2 replies; 10+ messages in thread
From: John Tobias @ 2014-03-12 2:23 UTC (permalink / raw)
To: linux-arm-kernel
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@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@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@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@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
>>
>>
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Freescale PFUZE100 PMIC
2014-03-12 2:23 ` John Tobias
@ 2014-03-12 2:30 ` John Tobias
2014-03-12 7:24 ` Robert Schwebel
2014-03-12 2:31 ` Yibin Gong
1 sibling, 1 reply; 10+ messages in thread
From: John Tobias @ 2014-03-12 2:30 UTC (permalink / raw)
To: linux-arm-kernel
Hi Yibin,
I got it working now... thanks.
Regards,
john
On Tue, Mar 11, 2014 at 7:23 PM, John Tobias <john.tobias.ph@gmail.com> wrote:
> 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@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@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@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@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
>>>
>>>
>>
>>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Freescale PFUZE100 PMIC
2014-03-12 2:23 ` John Tobias
2014-03-12 2:30 ` John Tobias
@ 2014-03-12 2:31 ` Yibin Gong
1 sibling, 0 replies; 10+ messages in thread
From: Yibin Gong @ 2014-03-12 2:31 UTC (permalink / raw)
To: linux-arm-kernel
>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@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@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@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@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@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
>>
>>
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Freescale PFUZE100 PMIC
2014-03-12 2:30 ` John Tobias
@ 2014-03-12 7:24 ` Robert Schwebel
2014-03-12 18:11 ` John Tobias
0 siblings, 1 reply; 10+ messages in thread
From: Robert Schwebel @ 2014-03-12 7:24 UTC (permalink / raw)
To: linux-arm-kernel
On Tue, Mar 11, 2014 at 07:30:48PM -0700, John Tobias wrote:
> I got it working now... thanks.
For the record: what did you do to fix it?
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
^ permalink raw reply [flat|nested] 10+ messages in thread
* Freescale PFUZE100 PMIC
2014-03-12 7:24 ` Robert Schwebel
@ 2014-03-12 18:11 ` John Tobias
0 siblings, 0 replies; 10+ messages in thread
From: John Tobias @ 2014-03-12 18:11 UTC (permalink / raw)
To: linux-arm-kernel
It's a mistake on my part. I overlook at the i2c bus in schematic, my
mapping was incorrect.
Regards,
john
On Wed, Mar 12, 2014 at 12:24 AM, Robert Schwebel
<r.schwebel@pengutronix.de> wrote:
> On Tue, Mar 11, 2014 at 07:30:48PM -0700, John Tobias wrote:
>> I got it working now... thanks.
>
> For the record: what did you do to fix it?
>
> rsc
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2014-03-12 18:11 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-12 0:41 Freescale PFUZE100 PMIC John Tobias
2014-03-12 1:05 ` Fabio Estevam
2014-03-12 1:41 ` Yibin Gong
2014-03-12 2:00 ` John Tobias
2014-03-12 2:11 ` Yibin Gong
2014-03-12 2:23 ` John Tobias
2014-03-12 2:30 ` John Tobias
2014-03-12 7:24 ` Robert Schwebel
2014-03-12 18:11 ` John Tobias
2014-03-12 2:31 ` Yibin Gong
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).