Hi Gregor,
Actually if you look for the code of atmel_mxt_ts - all actions are in probe.
Also simple experimental like:
echo maxtouch 0x48 > /sys/bus/i2c/i2c-4/new_device
you got the same as in my case with modified your driver:
Mar 02 18:51:39 archiso kernel: device: '4-0048': device_add
Mar 02 18:51:39 archiso kernel: bus: 'i2c': add device 4-0048
Mar 02 18:51:39 archiso kernel: PM: Adding info for i2c:4-0048
Mar 02 18:51:39 archiso kernel: i2c i2c-4: new_device: Instantiated
device maxtouch at 0x48
Mar 02 18:51:39 archiso kernel: bus: 'i2c': add driver atmel_mxt_ts
Mar 02 18:51:39 archiso kernel: bus: 'i2c': driver_probe_device:
matched device 4-0048 with driver atmel_mxt_ts
Mar 02 18:51:39 archiso kernel: bus: 'i2c': really_probe: probing
driver atmel_mxt_ts with device 4-0048
Mar 02 18:51:39 archiso kernel: atmel_mxt_ts 4-0048: no default pinctrl state
Mar 02 18:51:39 archiso kernel: devices_kset: Moving 4-0048 to end of list
Mar 02 18:51:39 archiso kernel: atmel_mxt_ts 4-0048: No platform data specified
Mar 02 18:51:39 archiso kernel: atmel_mxt_ts: probe of 4-0048 faile
Regards,
Serge Kolotylo.
PS: it will be really good if here will be someone who is fluent in
Chinese and could directly read spec for Chipone and translate it to
us.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
