Motion Sensor reg dump

Andy Green andy at
Wed Jan 23 19:24:39 CET 2008

Hash: SHA1

Somebody in the thread at some point said:
> Andy Green wrote:
>> Therefore I guess there is some variance of that device from the
>> description in the datasheet, for example the address of
>> LIS302DL_REG_CTRL3 given in there is wrong.
> Sounds like we need to do A6 then.

No too early to worry about that yet.

 - INT synchronous with new samples isn't working

Didn't finish meddling with it yet, we didn't ask ST for support yet
either.  If it can't work but everything else does, we can still come
and poll it ourselves asynchronously and get what should be reasonable
if not ideal behaviour.  I have a trick in my back pocket that will
enable us to do that nicely if we have to.

 - There is a danger communication can get corrupted between the two

This seems to be real but it can only happen under very specific
circumstances that we probably never generate, also strobing the
disabled device CS inbetween clocks might ensure the disabled device
never sees enough I2C clocks to do anything.

So we need to meddle on... after tea :-)

- -Andy
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora -


More information about the openmoko-kernel mailing list