2011/1/4 Alan Cox <[email protected]> > > > - Register the I²C bus as a kernel I²C bus when not being used by > > > the device (would allow sharing of standard I²C drivers for modules > > > like compasses off it > > > > In this driver, the part of accelerometer and compass collocates with > > core of gyroscope driver, because this is an auxiliary component for > > gyroscope, which needs this component to fix the drift of gyroscope. > > This architecture is designed for MPL. (Does this answer your > > question?) > > I don't think so. You have duplicate drivers for various devices and > ioctl interfaces for talking to the I²C bus on the device that are only > duplicate because the device doesn't expose that bus to the existing > drivers. I'd have thought doing that was in your interest and the > vendors as it would allow the bus to be used for other supported > devices as well ? > As far as I know, this basic architecture of driver came from the vendor. It owns two paths to access the components behind mpu3050. The one is the path MPL walks through; another is called bypass mode which allows to get raw data from the component via I²C bus. I think someone who is responsible for sensorfw could give a advice on this issue. Which interface is more suitable for sensorfw?
Jekyll _______________________________________________ MeeGo-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
