From: Daniel Baluta <daniel.baluta@intel.com>
To: nroyer@invensense.com, ggao@invensense.com
Cc: linux-iio@vger.kernel.org
Subject: Invensense MPU6500 driver with Digital Motion Processor (DMP)
Date: Fri, 19 Sep 2014 18:08:16 +0300 [thread overview]
Message-ID: <541C46E0.7030704@intel.com> (raw)
Hi Nathan/Ge,
I'm playing with Invensense MPU6500 device but I'm having problems
receiving data when the DPM is enabled.
I've rebased the code from 3.4 [1] on top of the latest iio git
tree. Without DMP enabled, I see interrupts arriving and I can
read data from /dev/iio:device0.
I'm using the following sequence for test:
sysfs_dev=/sys/bus/iio/devices/iio:device0
#Write dmp fw
fw_loaded=`cat ${sysfs_dev}/firmware_loaded`
if [ $fw_loaded -eq 0 ]; then
fwtool write /bin/fw.bin
fi
#Enable accel
echo 0 > ${sysfs_dev}/buffer/enable
echo 200 > ${sysfs_dev}/sampling_frequency
echo 1 > ${sysfs_dev}/accel_fifo_enable
echo 1 > ${sysfs_dev}/accel_enable
echo 1 > ${sysfs_dev}/gyro_fifo_enable
echo 1 > ${sysfs_dev}/gyro_enable
#echo 1 > ${sysfs_dev}/master_enable
#Enable DMP
echo 1 > ${sysfs_dev}/dmp_on
echo 1 > ${sysfs_dev}/dmp_int_on
echo 1 > ${sysfs_dev}/dmp_event_int_on
echo 1 > ${sysfs_dev}/buffer/enable
cat /dev/iio\:device0
Now, the problem is that there is not interrupt triggered. Have you
faced similar issues? Is there something wrong with the above sequence?
thanks,
Daniel.
[1]
https://android.googlesource.com/kernel/msm/+/android-msm-hammerhead-3.4-kk-fr2/drivers/staging/iio/imu/inv_mpu
reply other threads:[~2014-09-19 15:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=541C46E0.7030704@intel.com \
--to=daniel.baluta@intel.com \
--cc=ggao@invensense.com \
--cc=linux-iio@vger.kernel.org \
--cc=nroyer@invensense.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).