linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Octavian Purdila <octavian.purdila@intel.com>
To: linux-iio@vger.kernel.org
Cc: srinivas.pandruvada@linux.intel.com,
	Octavian Purdila <octavian.purdila@intel.com>
Subject: [PATCH v4 0/3] iio: bmc150: refactoring in preparation for hardware fifo support
Date: Tue,  3 Mar 2015 18:17:55 +0200	[thread overview]
Message-ID: <1425399478-5464-1-git-send-email-octavian.purdila@intel.com> (raw)

Hi Jonathan,

Here is a new version for the remaining bmc150 refactor patches that
were not merged. I've also added to this set a fix from Sathya which
has been sitting in our tree.

As you requested, I've split the refactoring series from the hardware
fifo series. I will send the v4 hwfifo series shortly.

Thanks,
Tavi

Changes since v3:

* added enums for interrupts and triggers

* added fix from Sathya



Octavian Purdila (2):
  iio: bmc150: introduce bmc150_accel_interrupt
  iio: bmc150: introduce bmc150_accel_trigger

Sathyanarayanan Kuppuswamy (1):
  iio: bmc150: change sampling frequency

 drivers/iio/accel/bmc150-accel.c | 294 ++++++++++++++++++++++++---------------
 1 file changed, 178 insertions(+), 116 deletions(-)

-- 
1.9.1


             reply	other threads:[~2015-03-03 16:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 16:17 Octavian Purdila [this message]
2015-03-03 16:17 ` [PATCH v4 1/3] iio: bmc150: change sampling frequency Octavian Purdila
2015-03-08 11:17   ` Jonathan Cameron
2015-03-08 14:56     ` Octavian Purdila
2015-03-03 16:17 ` [PATCH v4 2/3] iio: bmc150: introduce bmc150_accel_interrupt Octavian Purdila
2015-03-08 11:22   ` Jonathan Cameron
2015-03-09 20:40     ` Srinivas Pandruvada
2015-03-14 18:39       ` Jonathan Cameron
2015-03-03 16:17 ` [PATCH v4 3/3] iio: bmc150: introduce bmc150_accel_trigger Octavian Purdila
2015-03-14 18:40   ` Jonathan Cameron

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=1425399478-5464-1-git-send-email-octavian.purdila@intel.com \
    --to=octavian.purdila@intel.com \
    --cc=linux-iio@vger.kernel.org \
    --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).