Hello,
On DM8168, the third I2C bus (i2c number 2, when counting from zero) is used by M3 core in Linux and the initialization is done by its firmware when it's loaded from /etc/init.d/load-hd-firmware.sh (the loader outputs "FIRMWARE: I2cInit will be done by M3" in this process). This is OK for the EVM because capture devices are located on the daughter board and connected to the mentioned I2C bus.
We have a custom DM8168-based board without capture devices, but there are some other non-video I2C devices connected to the third I2C bus. However, loading of M3 firmwares causes problems with accessing to those devices. They work fine if firmwares are not loaded and vpss module is not started, but then I lose the video/display functionality. I also tried changing '-i2c' argument in load-hd-firmware.sh from 1 to 0, but no effect (because obviosly M3 is trying to reinitialize I2C bus anyway). Finally, starting vpss module without M3 firmwares loaded doesn't work (as expected).
So I'm now in a situation where I must choose between video functionality and normal access to I2C devices on the third bus.
Since I really need the third I2C bus for other appliances, is it possible to make M3 firmwares to let go of the third bus, but to retain video capabilities (without capture, of course)? And is it possible to do that without firmware rebuilding, because the sources are not publicly available?
Regards,
Ivan
