> > [ 2.105938] i2c /dev entries driver > [ 2.114206] config i2c gpio with gpio_config api > [ 2.122210] incomplete xfer (0x20) > [ 2.129422] axp_mfd 0-0034: failed reading at 0x03 > [ 2.137781] [AXP20-MFD] try to read chip id failed! > [ 2.147226] axp_mfd: probe of 0-0034 failed with error -70 > [ 2.156546] i2c i2c-0: Invalid probe address 0x00 > [ 2.164426] I2C: i2c-0: AW16XX I2C adapter > [ 2.173834] i2c i2c-1: Invalid probe address 0x00 > [ 2.181672] hub 1-1:1.0: USB hub found > [ 2.188584] I2C: i2c-1: AW16XX I2C adapter > [ 2.196185] hub 1-1:1.0: 4 ports detected > [ 2.204120] i2c i2c-2: Invalid probe address 0x00 > [ 2.211998] I2C: i2c-2: AW16XX I2C adapter > [ 2.219840] [ccu-err] clk_enable: invalid handle > [ 2.228848] i2c i2c-3: Invalid probe address 0x00 > [ 2.236737] I2C: i2c-3: AW16XX I2C adapter > [ 2.244633] [ccu-err] clk_enable: invalid handle > [ 2.254376] i2c i2c-4: Invalid probe address 0x00 > [ 2.262184] I2C: i2c-4: AW16XX I2C adapter
Yes, that is rather interesting, AXP fails in your log. You have something wrong with I2C bus, are you sure that you have everything right in script.bin? I'm talking about these parameters, I2C muxing https://github.com/linux-sunxi/sunxi-boards/blob/master/sys_config/a20/cubieboard2.fex#L122 addr/id for AXP https://github.com/linux-sunxi/sunxi-boards/blob/master/sys_config/a20/cubieboard2.fex#L895 Also, CSI driver wants these parameters of AXP to be working: https://github.com/linux-sunxi/sunxi-boards/blob/master/sys_config/a20/cubieboard2.fex#L516 Thats why it throws error. I'm linking cubieboard because it is in known working state, as I understand, you have your own custom board. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
