> Just to field this quickly, since I've been playing with the hardware (Ditto) > Part of the reason I got started on the KXTF9 driver was to try and > understand how a normal kernel driver could cope with the "here and > gone again" behavior of being on the MPU's secondary bus. It's a hot pluggable bus - no different to an i2c bus on a hot pluggable device. I would guess however that if you knew the device was going to be used for the mpu3050 only you'd not add the "slave" devices in your platform data in the first place as well so they didn't bounce in and out and you'd probably teach the mpu3050 code to not create the bus if it was then going to destroy it again a moment later. > The other note that may not have been made explicit yet is that the > 3050 will happily provide unprocessed gyro and slave data without > firmware loaded. The firmware sets up some additional processing > capabilities of the chip, which are used by InvenSense's user-space > products. Yes - and the current mpu3050 driver provides just these interfaces. Of the other stuff the slave drivers seem to be no problem as standard i²c bus devices, the MPU mode may depend upon whether there is open documentation, applying the standards we apply to everything else. That is "can someone write their own tools to use that interface based upon the documentation/source code examples available". Eg for the ektf driver which is pending the interface is all documented and provides rectangles of pressure data but you'll have to go write your own gesture recognizer parts if you want to do clever stuff with it. Alan -- 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
