Issue with i2c-3

Hi, I want to control a device connected to camera connector pins I2C_PM_CLK and I2C_PM_DAT.
However, it seems that I2C-3 (i2c@7000c700) bus is not working at all.

i2cdetect -y -r 3
produces following dumps to dmesg:

[  187.171055] tegra-i2c 7000c700.i2c: --- register dump for debugging ----
[  187.177913] tegra-i2c 7000c700.i2c: I2C_CNFG - 0x22c00
[  187.185767] tegra-i2c 7000c700.i2c: I2C_PACKET_TRANSFER_STATUS - 0x10001
[  187.195663] tegra-i2c 7000c700.i2c: I2C_FIFO_CONTROL - 0xe0
[  187.201264] tegra-i2c 7000c700.i2c: I2C_FIFO_STATUS - 0x800080
[  187.207126] tegra-i2c 7000c700.i2c: I2C_INT_MASK - 0xed
[  187.212488] tegra-i2c 7000c700.i2c: I2C_INT_STATUS - 0x2
[  187.217912] tegra-i2c 7000c700.i2c: msg->len - 1
[  187.222661] tegra-i2c 7000c700.i2c: is_msg_write - 0
[  187.228497] tegra-i2c 7000c700.i2c: buf_remaining - 1
[  187.233582] tegra-i2c 7000c700.i2c: i2c transfer timed out, addr 0x0003, data 0x00

This happens even without anything plugged into the camera connector.
I’m running L4T R24.2.1.

Hope someone can help me get this bus working.

This message tell the device no ack it’s not a error message. You need to make sure you device if working correctly first.

When I run the same command for other I2C buses e.g.
i2cdetect -y -r 4
dmesg shows a totally different kind of message for no ack condition:

[65235.939587] tegra-i2c 7000d000.i2c: no acknowledge from address 0x3

So there is definitely something different happening on bus 3.

I would like to say there’s no problem with i2c-3, we have a internal camera sensor use this bus and working well.

Maybe there is some configuration change needed on top of L4T R24.2.1?
I have disconnected all my devices from devkit and measuring I2C_PM_CLK and I2C_PM_DAT with an oscilloscope shows flat 1.8V for both signals when scanning the bus.

I got the same message while run the i2cdetect, however the sensor connect to this bus is working well.

Should it work directly with R24.2.1 or do I need to make some configuration changes?
At least it seems the pinmux is correct as is.

Did you work on customize carrier board ?

No, I’m using the development carrier board.

OK, TK1 have another i2c bus wire out to carrier board. If you have suspect this bus have problem you can try another one.