Comment 80 for bug 1949394

There was something going with this on
https://lkml.org/lkml/2012/7/4/292

Do You have CONFIG_I2C_HID enabled?

Some such driver is written
http://lxr.free-electrons.com/source/drivers/hid/i2c-hid/i2c-hid.c

We must be a bit cautious because the BIOS EEPROM may be connected to the i2c bus and we must not try to drive it as a touchpad because it may modify its contents.

This is also interesting
http://msdn.microsoft.com/en-us/library/windows/hardware/jj191738%28v=vs.85%29.aspx

This also looks sensibly:
"This combined support for I2C over HID in the inbox driver, allows hardware manufactures to get their devices running quickly on windows without imposing the need to create a driver."

Give me Your /proc/interrupts when the touchpad is working.

Boot with hid.debug=1 and gimme dmesg when the toucpad is working.

I hope that YOu have CONFIG_PRINTK on