I2C connector not functionnal on dragon board 410c


#1

Hi everybody,

I’m newby in the domain so it is little bit difficil for me.

I try to connect I2C NFC device (CLF board) on my dragon board but i have some problems on the driver probing.
I have already made similar operation with SPI connector with succes (Secure element device).
But i have problem with I2C :
pinctrlfile :
pmx_i2c_6 {
/* CLK, DATA /
qcom,pins = <&gp 22>, <&gp 23>;
qcom,num-grp-pins = <2>;
qcom,pin-func = <2>;
label = “pmx_i2c_6”;
/
active state /
i2c_6_active: i2c_6_active{
drive-strength = <2>; /
2 MA /
bias-disable; /
No PULL */
};
/*suspended state /
i2c_6_sleep: i2c_6_sleep {
drive-strength = <2>; /
2 MA /
bias-disable; /
No PULL */
};
};

device description :
i2c_6: i2c@78ba000 { /* BLSP1 QUP6 */
compatible = “qcom,i2c-qup”;
#address-cells=<1>;
#size-cells=<0>;
cell-index = <6>;
reg-names = “qup_phys_addr”;
reg = <0x78ba000 0x1000>;
interrupt-names = “qup_irq”;
interrupts = <0 100 0>;

	/*clock-names = "iface_clk", "core_clk";
	clocks = &lt;&amp;clock_gcc clk_gcc_blsp1_ahb_clk&gt;,
		 &lt;&amp;clock_gcc clk_gcc_blsp1_qup6_i2c_apps_clk&gt;;
	qcom,clk-freq-out = &lt;400000&gt;;
	qcom,clk-freq-in  = &lt;19200000&gt;;*/
	
	qcom,i2c-bus-freq = &lt;400000&gt;;
	qcom,i2c-src-freq = &lt;19200000&gt;;
	qcom,scl-gpio = &lt;&amp;msmgpio 23 0&gt;;
	qcom,sda-gpio = &lt;&amp;msmgpio 22 0&gt;;
	
	pinctrl-names = "i2c_active", "i2c_sleep";
	pinctrl-0 = &lt;&amp;i2c_6_active&gt;;
	pinctrl-1 = &lt;&amp;i2c_6_sleep&gt;;
	qcom,noise-rjct-scl = &lt;0&gt;;
	qcom,noise-rjct-sda = &lt;0&gt;;
	dmas = &lt;&amp;dma_blsp1 14 64 0x20000020 0x20&gt;,
		&lt;&amp;dma_blsp1 15 32 0x20000020 0x20&gt;;
	dma-names = "tx", "rx";
	qcom,master-id = &lt;86&gt;;
	xx_nfc@08 {
		compatible = "xx, xxnfc";
		reg = &lt;0x08&gt;;
		interrupt-parent = &lt;&amp;msm_gpio&gt;;
		interrupts = &lt;69 0x2&gt;;
		xx,reset_gpio = &lt;&amp;msm_gpio 13 0x00&gt;;
		xx,irq_gpio = &lt;&amp;msm_gpio 35 0x00&gt;;
	};
};

KMSG log at startup :
<6>[ 0.171779] i2c-msm-v2 78ba000.i2c: probing driver i2c-msm-v2
<3>[ 0.171893] i2c-msm-v2 78ba000.i2c: error on clk_get(core_clk):-517
<3>[ 0.171910] i2c-msm-v2 78ba000.i2c: error probe() failed with err:-517
<6>[ 0.171951] platform 78ba000.i2c: Driver i2c-msm-v2 requests probe deferral

I have tried this solution without succes : here

Some one can help me please ?


#2

Hi,

So when ever someone says the hardware is broken, it always goes back to validating it with something that is known to work. Unless you applied too high a voltage, I would go down the path of configuration.

Be sure you are not using an interface configured for another driver.

Can you post the diff of your changes, it’s easier to identify issues?

Joel


#3

Hi Joel,

First, Thank you for your queek answer.
i2c_6: i2c@78ba000 is just used for this device.

On kmsg log i can see all I2C device as same issue :
<6>[ 0.171779] i2c-msm-v2 78ba000.i2c: probing driver i2c-msm-v2
<3>[ 0.171893] i2c-msm-v2 78ba000.i2c: error on clk_get(core_clk):-517
<3>[ 0.171910] i2c-msm-v2 78ba000.i2c: error probe() failed with err:-517
<6>[ 0.171951] platform 78ba000.i2c: Driver i2c-msm-v2 requests probe deferral
<6>[ 0.172209] i2c-msm-v2 78b6000.i2c: probing driver i2c-msm-v2
<3>[ 0.172315] i2c-msm-v2 78b6000.i2c: error on clk_get(core_clk):-517
<3>[ 0.172330] i2c-msm-v2 78b6000.i2c: error probe() failed with err:-517
<6>[ 0.172367] platform 78b6000.i2c: Driver i2c-msm-v2 requests probe deferral
<6>[ 0.172666] i2c-msm-v2 78b8000.i2c: probing driver i2c-msm-v2
<3>[ 0.172765] i2c-msm-v2 78b8000.i2c: error on clk_get(core_clk):-517
<3>[ 0.172780] i2c-msm-v2 78b8000.i2c: error probe() failed with err:-517

Changes i made are comment “i2c_6: i2c@78ba000” already defined and add mine.

Thank you again.


#4

Hi,
No one can help me on this topic ?