linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: jic23@kernel.org
Cc: linux-iio@vger.kernel.org,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH v3 0/2] iio:gyro:bmg160 Gyro Sensor driver
Date: Tue,  5 Aug 2014 14:57:32 -0700	[thread overview]
Message-ID: <1407275854-29083-1-git-send-email-srinivas.pandruvada@linux.intel.com> (raw)

v3
- Suport Only Runtime PM no fallback method. Driver will still work but
chip will be in power on mode.
- Add comment for enable disable trigger/event sequence, how they work
in reverse order using runtime pm calls

v2:
- Add device id in any-motion trigger
- Removed string comparison for trigger name to identify trigger source
- Prevent disabling any motion interrupts when both any motion trigger
and events are on, but any one of them is disabled via sysfs
- Switch on chan->type
- Created new function to raw read axis
- Explanation why need to power on for changing sampling freq and scale

v1:
- Runtime PM: Removed module parameter for delay configuration
Use RTPM autosuspend delay feature. This allows sysfs configuration of
autosuspend time.

- Trigger
As suggested, there are two triggers:
- data_ready : Trigger which will allow all gyro periodic sampled data to
be received by user space
- any-motion: When used, will configure the chipset so that data is
pushed only when there is any motion, allowing system to enter deeper idle
power states

- Events
ROC type events will send direction instead of either.
Also both events and data triggers can be enabled together.

- Addition of unbuffered TEMP read interface

- Misc error message corrections as suggested by Peter Meerwald

TBD: Add sysfs attribute to trigger to configure thresholds.
Currently the triggers don't have feature to add sysfs attributes
unlike IIO device. But this has to be a RFC patch on top. 

v0:
Base version for review

Srinivas Pandruvada (2):
  iio:gyro:bmg160 Gyro Sensor driver
  iio:gyro:bmg160 documentation

 .../ABI/testing/sysfs-bus-iio-gyro-bmg160          |    7 +
 drivers/iio/gyro/Kconfig                           |   11 +
 drivers/iio/gyro/Makefile                          |    1 +
 drivers/iio/gyro/bmg160.c                          | 1211 ++++++++++++++++++++
 4 files changed, 1230 insertions(+)
 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-gyro-bmg160
 create mode 100644 drivers/iio/gyro/bmg160.c

-- 
1.7.11.7


             reply	other threads:[~2014-08-05 21:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 21:57 Srinivas Pandruvada [this message]
2014-08-05 21:57 ` [PATCH v3 1/2] iio:gyro:bmg160 Gyro Sensor driver Srinivas Pandruvada
2014-08-07 10:39   ` Jonathan Cameron
2014-08-08  2:47     ` Srinivas Pandruvada
2014-08-12 19:06     ` Srinivas Pandruvada
2014-08-19 19:51       ` Jonathan Cameron
2014-08-26 17:37         ` Jonathan Cameron
2014-08-05 21:57 ` [PATCH v3 2/2] iio:gyro:bmg160 documentation Srinivas Pandruvada

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=1407275854-29083-1-git-send-email-srinivas.pandruvada@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.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 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).