pfuze100-regulator 1-0008: unrecognized pfuze chip ID!

[fulinux]

Dear community:

Hardware Platform:

Processor: Freescale i.MX6Q

Memory: DDR3 4GB

Flash: 32GB Managed Nand

Software Platform:

Kernel: linux 4.1.15

BSP: imx_4.1.15_1.0.0_ga

i add this in my dts file for pfuze100:

&i2c2 {

  clock-frequency = <100000>;

  pinctrl-names = "default";

  pinctrl-0 = <&pinctrl_i2c2>;

  status = "okay";

  pmic: pfuze100@08 {

  compatible = "fsl,pfuze100";

  reg = <0x08>;

  pinctrl-names = "default";

  pinctrl-0 = <&pinctrl_pfuze>;

  interrupt-parent = <&gpio7>;

  interrupts = <13 2>;

  regulators {

  sw1a_reg: sw1ab {

  regulator-min-microvolt = <300000>;

  regulator-max-microvolt = <1875000>;

  regulator-boot-on;

  regulator-always-on;

  regulator-ramp-delay = <6250>;

  };

  sw1c_reg: sw1c {

  regulator-min-microvolt = <300000>;

  regulator-max-microvolt = <1875000>;

  regulator-boot-on;

  regulator-always-on;

  regulator-ramp-delay = <6250>;

  };

  sw2_reg: sw2 {

  regulator-min-microvolt = <800000>;

  regulator-max-microvolt = <3300000>;

  regulator-boot-on;

  regulator-always-on;

  regulator-ramp-delay = <6250>;

  };

  sw3a_reg: sw3a {

  regulator-min-microvolt = <400000>;

  regulator-max-microvolt = <1975000>;

  regulator-boot-on;

  regulator-always-on;

  };

  sw3b_reg: sw3b {

  regulator-min-microvolt = <400000>;

  regulator-max-microvolt = <1975000>;

  regulator-boot-on;

  regulator-always-on;

  };

  sw4_reg: sw4 {

  regulator-min-microvolt = <800000>;

  regulator-max-microvolt = <3300000>;

  };

  swbst_reg: swbst {

  regulator-min-microvolt = <5000000>;

  regulator-max-microvolt = <5150000>;

  regulator-boot-on;

  regulator-always-on;

  };

  snvs_reg: vsnvs {

  regulator-min-microvolt = <1000000>;

  regulator-max-microvolt = <3000000>;

  regulator-boot-on;

  regulator-always-on;

  };

  vref_reg: vrefddr {

  regulator-boot-on;

  regulator-always-on;

  };

  vgen1_reg: vgen1 {

  regulator-min-microvolt = <800000>;

  regulator-max-microvolt = <1550000>;

  };

  vgen2_reg: vgen2 {

  regulator-min-microvolt = <800000>;

  regulator-max-microvolt = <1550000>;

  };

  vgen3_reg: vgen3 {

  regulator-min-microvolt = <1800000>;

  regulator-max-microvolt = <3300000>;

  };

  vgen4_reg: vgen4 {

  regulator-min-microvolt = <1800000>;

  regulator-max-microvolt = <3300000>;

  regulator-always-on;

  };

  vgen5_reg: vgen5 {

  regulator-min-microvolt = <1800000>;

  regulator-max-microvolt = <3300000>;

  regulator-always-on;

  };

  vgen6_reg: vgen6 {

  regulator-min-microvolt = <1800000>;

  regulator-max-microvolt = <3300000>;

  regulator-always-on;

  };

  };

  };

};

it shows some wrong in kernel log as follows:

pfuze100-regulator 1-0008: unrecognized pfuze chip ID!

pfuze100-regulator: probe of 1-0008 failed with error -5

what is wrong? @log file attached here

Original Attachment has been moved to: imx6q-klsw.dts.zip

Original Attachment has been moved to: dmesg.log.zip

[marcocavallini]

I had the same problem,

everything was fine using kernel 3.10.17 but then migrating to 4.1-2.0 it failed.

pfuze100-regulator 1-0008: unrecognized pfuze chip ID!
pfuze100-regulator: probe of 1-0008 failed with error -5

The solution was to set up the proper pinctrl-0 value

&i2c2 {
clock-frequency = <100000>;
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_i2c2_1>;
status = "okay";

Because setting the wrong set of MUXes would result in a I2C read/write bus failure.

This is the final result:

pfuze100-regulator 1-0008: Full layer: 2, Metal layer: 1
pfuze100-regulator 1-0008: FAB: 0, FIN: 0
pfuze100-regulator 1-0008: pfuze100 found.

Distinti Saluti / Best Regards
--
Marco Cavallini | KOAN sas | Bergamo - Italia
embedded software engineering
http://KoanSoftware.com

[yakovshaulov]

Hello Chen,

Have you solved this issue?

We have the same problem, except that our PMIC is PF3000 and we saw the same message appears at Kernel log:

pfuze100-regulator 0-0008: unrecognized pfuze chip ID!
pfuze100-regulator: probe of 0-0008 failed with error -110

Thanks.

[igorpadykov]

Hi

that message is printed from pfuze_identify() in

linux-2.6-imx.git - Freescale i.MX Linux Tree

so one can add additional  debug  printfs to identify problem.

What is MMPF0100 marking, is it detected correctly in uboot ?

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

[fulinux]

Hi igor,

     thank you for your feedback, our hardware has no problem, because kernel in imx_3.0.35_4.1.0 version can register and operate pfuze100, look at this:

do you need any information? pls tell me.

thank you,

fulinux.