Quote:
Originally Posted by Renate
Hmm, looking into this more I see that there are drivers for things that aren't even supposed to be in there. I knocked out a little utility for scanning I²C and correlating that with whether there is stuff in sysfs for it.
My Poke3 again:
Code:
Poke3:/data/local/tmp # ./i2cscan
/dev/i2c-2
/dev/i2c-4
04 exists
05 exists
06 exists
07 exists
1f qcom,camera i2c_camera
38 exists focaltech (FocalTech touch screen controller) fts_ts
/dev/i2c-6
04 exists
05 exists
06 exists
07 exists
09 wacom (Wacom digitizer)
38 exists lm3630a (TI LED controller) lm3630a_bl
/dev/i2c-8
04 exists
05 exists
06 exists
07 exists
0b exists tc358762 (Toshiba display interface bridge) tc358762
68 tps6518x (TI Eink power management) tps6518x
So we can see that neither a camera, a Wacom or a TPS exists although the drivers are there. The stuff on addresses 4-7 are probably bus expanders or something.
If you want to try this (please), just ADB it somewhere (I like /data/local/tmp), chmod 755 it and run it. This is not a zip file (just named that for upload). Just rename it i2cscan, don't unzip it. |
This is the result:
Code:
/dev/i2c-2
04 exists
05 exists
06 exists
07 exists
60 exists
/dev/i2c-4
04 exists
05 exists
06 exists
07 exists
1f qcom,camera i2c_camera
24 exists tsc cyttsp5_i2c_adapter
34 exists aw881xx_smartpa aw881xx_smartpa
35 exists aw881xx_smartpa aw881xx_smartpa
/dev/i2c-6
00 exists
04 exists
05 exists
06 exists
07 exists
09 exists wacom (Wacom digitizer) wacom_ts
38 exists lm3630a (TI LED controller) lm3630a_bl
/dev/i2c-8
04 exists
05 exists
06 exists
07 exists
0b exists tc358762 (Toshiba display interface bridge) tc358762
48 exists max17135 max17135
IIRC the settings for which drivers should load on I²C are set in the devicetree in boot.img right?
Sorry for my late replies, my posts have to be checked by a mod beforehand...