linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Baluta <daniel.baluta@intel.com>
To: jic23@kernel.org
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
	daniel.baluta@intel.com, matt.ranostay@intel.com,
	lucas.demarchi@intel.com, cmo@melexis.com,
	linux-iio@vger.kernel.org, ggao@invensense.com,
	srinivas.pandruvada@linux.intel.com, adi.reus@gmail.com
Subject: [PATCH 0/3] Introduce support for INV MPU6050 secondary I2C master
Date: Thu, 17 Mar 2016 18:32:43 +0200	[thread overview]
Message-ID: <1458232366-12773-1-git-send-email-daniel.baluta@intel.com> (raw)

This patch series adds support for attaching external sensors to INV MPU6050
secondary I2C interface (acting as an I2C bus).

First patch fixes a bug when using ACPI, the second one moves the interrupt out
of probe trigger code preparing the third patch which actually does $Subject.

I2C secondary bus can support up to 5 slaves. Slaves 0-3 have a common way
of operation while the 4 one is completely different. This patch series
only implements support for the 4th slave because it has a cleaner interface
(although less efficent for bulk transfer) and also provides a way of
signalling when data recevied from slave is available.

Ge,

In order to prepare support for slaves 0-3 we need to find the answer for
the following questions:
	* when doing a read transaction after preparing I2C address, I2C
        remote register, etc how do we know when to read for available data?
	* how can we benefit from INV MPU6050 FIFO in case of external sensors?
	(will look into in-kernel buffer consumers)

Daniel Baluta (3):
  iio: imu: mpu6050: Fix name/chip_id when using ACPI
  iio: imu: mpu6050: Request IRQ outside of probe trigger
  iio: imu: mpu6050: Add support for auxiliary I2C master

 drivers/iio/imu/inv_mpu6050/inv_mpu_core.c    | 139 ++++++++++++++++++++++++++
 drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c     |  29 +++++-
 drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h     |  38 +++++++
 drivers/iio/imu/inv_mpu6050/inv_mpu_trigger.c |   8 --
 4 files changed, 203 insertions(+), 11 deletions(-)

-- 
2.5.0


             reply	other threads:[~2016-03-17 16:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 16:32 Daniel Baluta [this message]
2016-03-17 16:32 ` [PATCH 1/3] iio: imu: mpu6050: Fix name/chip_id when using ACPI Daniel Baluta
2016-03-17 17:21   ` Matt Ranostay
2016-03-20 10:40     ` Jonathan Cameron
2016-03-21 10:16       ` Daniel Baluta
2016-03-21 18:58         ` Jonathan Cameron
2016-03-17 16:32 ` [PATCH 2/3] iio: imu: mpu6050: Move request IRQ outside of probe trigger Daniel Baluta
2016-03-17 17:24   ` Matt Ranostay
2016-03-17 16:32 ` [PATCH 3/3] iio: imu: mpu6050: Add support for auxiliary I2C master Daniel Baluta
2016-03-17 17:28   ` Matt Ranostay
2016-03-17 18:11     ` Ge Gao
2016-03-17 18:13       ` Matt Ranostay
2016-03-17 21:15       ` De Marchi, Lucas
2016-03-20 10:54       ` Jonathan Cameron
2016-03-20 10:47   ` Jonathan Cameron
2016-03-23 12:32     ` Daniel Baluta

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=1458232366-12773-1-git-send-email-daniel.baluta@intel.com \
    --to=daniel.baluta@intel.com \
    --cc=adi.reus@gmail.com \
    --cc=cmo@melexis.com \
    --cc=ggao@invensense.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matt.ranostay@intel.com \
    --cc=pmeerw@pmeerw.net \
    --cc=srinivas.pandruvada@linux.intel.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).