linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Jonathan Cameron <jic23@kernel.org>,
	Crestez Dan Leonard <leonard.crestez@intel.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Nick Vaccaro <nvaccaro@google.com>, Ge Gao <ggao@invensense.com>,
	Anna Si <asi@invensense.com>,
	Nathan Royer <nroyer@invensense.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Daniel Baluta <daniel.baluta@intel.com>,
	Gregor Boirie <gregor.boirie@parrot.com>,
	Peter Rosin <peda@axentia.se>
Subject: Re: [PATCH 2/2] iio: gyro: Add driver for the MPU-3050 gyroscope
Date: Thu, 25 Aug 2016 15:13:17 +0200	[thread overview]
Message-ID: <CACRpkdaAW2=taAED53kE9bQ3XSFXRaBAKye9msmtqa-rDZGkGA@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdY=Y56Uz90Z2SW+=eYJaH1zd8FM6Th2tgjkXVmz6fSScA@mail.gmail.com>

On Thu, Aug 25, 2016 at 2:37 PM, Linus Walleij <linus.walleij@linaro.org> wrote:

>>> I suspect some of the stuff I've done here should be carried
>>> over to the MPU-6050 driver in drivers/iio/imu/inv_mpu6050/*
>>
>> Which bits in particular?
>
> - Fetch and handle regulators for vdd and vddio (currently
>   totally missing).
>
> - Runtime PM, including getting rid of the horrible homebrewn
>   reference count in inv_mpu6050_set_power_itg()
>
> - Oh mpu6050 doesn't even seem to power the device down
>   on .remove() I think it's a bug actually

Oh and when it comes to the trigger interrupts in
drivers/iio/imu/inv_mpu6050/inv_mpu_trigger.c

- No active low handling (bit 7 reg 0x37)

- No open drain handling (bit 6 reg 0x37)

- No level interrupt support (bit 5 reg 0x37)

- No check of status register to return IRQ_NONE
  i.e. spurious IRQ handling is non-existent.

- Timestamping should preferably happen in top
  half.

All of this should probably happen more like it happens
in this MPU-3050 driver. Instead it assumes that the
interrupt assigned will be an edge, low-to-high transition,
and nothing else is supported.

Yours,
Linus Walleij

  reply	other threads:[~2016-08-25 13:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 18:38 [PATCH 2/2] iio: gyro: Add driver for the MPU-3050 gyroscope Linus Walleij
2016-08-21 18:32 ` Jonathan Cameron
2016-08-23  8:37   ` Peter Rosin
2016-08-23 14:38     ` jic23
2016-08-24  8:49       ` Peter Rosin
2016-08-24 11:50         ` Wolfram Sang
2016-08-25 12:44     ` Linus Walleij
2016-08-25 20:32       ` Peter Rosin
2016-08-25 22:52         ` Wolfram Sang
2016-08-26  7:39         ` Linus Walleij
2016-08-29 17:41           ` Jonathan Cameron
2016-08-25 12:37   ` Linus Walleij
2016-08-25 13:13     ` Linus Walleij [this message]
2016-08-29 17:49       ` Jonathan Cameron
2016-08-29 17:48     ` Jonathan Cameron
2016-08-31 12:36       ` Linus Walleij

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='CACRpkdaAW2=taAED53kE9bQ3XSFXRaBAKye9msmtqa-rDZGkGA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=asi@invensense.com \
    --cc=daniel.baluta@intel.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=ggao@invensense.com \
    --cc=gregor.boirie@parrot.com \
    --cc=jic23@kernel.org \
    --cc=leonard.crestez@intel.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=nroyer@invensense.com \
    --cc=nvaccaro@google.com \
    --cc=peda@axentia.se \
    /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).