Dear Andy:
I list the testing result of motion sensor in our DM1 hardware
verification process:
[SENSOR] start test
Init
LIS302DL
value :
7
who_am_i :
3b
1 OUT X :
1
1 OUT Y :
-5
1 OUT Z :
-62
2 OUT X :
-6
2 OUT Y :
2
2 OUT Z :
-56
value :
57
pass!!
first check : no interrupt
!!
first check : interrupt
!!
first check : no interrupt
!!
first check : interrupt
!!
value :
7
who_am_i :
3b
1 OUT X :
-1
1 OUT Y :
-3
1 OUT Z : -52
2 OUT X :
-7
2 OUT Y :
3
2 OUT Z :
-44
value :
57
pass!!
first check : no interrupt
!!
first check : interrupt
!!
first check : no interrupt
!!
first check : interrupt !!
[SENSOR] end test
Best Regards,
--Miles--
Neng-Yu Tu (Tony Tu) wrote:
Dear Andy:
Attachment is the u-boot code for motion sensor could detect motion
sensor separately. This code used in our DM1 hardware verification
process.
Code was written by willie/miles.
Regards,
Tony Tu
Andy Green ??:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Somebody in the thread at some point said:
Current, we don't have plan on motion sensor driver implementation
also.
Hi Tony -
Starting working in this area I see that Harald has left us what seems
to be a /dev/input event-based usermode interface, so maybe this end
will be okay. It seems to know about 3 axes fine. But it can't have
been tested...
- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHlz6eOjLpvpq7dMoRAnRyAKCTL0yUG7hZacWh0COSrfUQ99AY3gCeI9bM
usw3wqpOMlM7mgA8ipXPVGM=
=1O9n
-----END PGP SIGNATURE-----
