From: Alan Cox <alan@linux.intel.com>
To: simon@mungewell.org
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Add a driver to support InvenSense mpu3050 gyroscope chip.
Date: Wed, 13 Apr 2011 15:54:08 +0100 [thread overview]
Message-ID: <20110413155408.2a1cf73a@bob.linux.org.uk> (raw)
In-Reply-To: <9bf2cf8dbd98b3e026d79af99277db63.squirrel@host171.canaca.com>
> Without a detailed datasheet for the MPU3050 I can't say for certain;
> but usually there is another register which is set when a measurement
> is taken. This can be cleared before and accessed after reading the
> XYZ values to confirm that they have not been corrupted.
I don't believe the datasheet for the MPU3050 is public, but it's a
smart device rather than a simple interface.
> Also some I2C hosts (such as the Intel SCH) don't support I2C block
> read/writes, and thus the access will be broken into separate
> reads/writes and be much slower.
Yes - but for those that can do it in one, it's a win to do so.
> Hope I'm not speaking out of turn
Nope - all good points to double check.
Alan
next prev parent reply other threads:[~2011-04-13 15:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 9:51 [PATCH] Add a driver to support InvenSense mpu3050 gyroscope chip Alan Cox
2011-04-13 10:30 ` Jonathan Cameron
2011-04-13 13:07 ` Alan Cox
2011-04-13 14:21 ` Jonathan Cameron
2011-04-13 14:30 ` Hennerich, Michael
2011-04-13 14:46 ` Alan Cox
2011-04-13 15:03 ` simon
2011-04-13 14:54 ` Alan Cox [this message]
2011-04-13 15:21 ` simon
-- strict thread matches above, loose matches on Subject: below --
2011-05-04 9:02 Alan Cox
2011-04-13 14:58 Alan Cox
2011-04-13 15:54 ` Jonathan Cameron
2011-04-13 14:55 Alan Cox
2011-04-06 12:38 Alan Cox
2011-03-09 13:47 Alan Cox
2011-03-14 15:39 ` Jonathan Cameron
2011-03-14 18:24 ` Alan Cox
2011-03-14 19:29 ` Jonathan Cameron
2011-03-14 20:14 ` Alan Cox
2011-03-15 6:02 ` Dmitry Torokhov
2011-03-15 11:59 ` Jonathan Cameron
2011-03-15 12:58 ` Alan Cox
2011-03-16 6:30 ` Dmitry Torokhov
2011-03-16 21:07 ` Rafael J. Wysocki
2011-03-15 9:44 ` Shubhrajyoti
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=20110413155408.2a1cf73a@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=linux-input@vger.kernel.org \
--cc=simon@mungewell.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.