Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: [PULL] Third set of IIO new stuff for the 4.5 cycle.
Date: Tue, 22 Dec 2015 19:04:06 +0000	[thread overview]
Message-ID: <56799EA6.1010909@kernel.org> (raw)

The following changes since commit c34c18195d30aa3b95f5ae1b4349875c45fdb8e4:

  iio/inkern.c Use list_for_each_entry_safe (2015-12-12 17:23:37 +0000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git tags/iio-for-4.5c

for you to fetch changes up to e8aab48b34d3bd069dfcf4ccb8f13ba8c98f7845:

  iio: adc: ina2xx: Fix incorrect report of data endianness to userspace. (2015-12-22 18:51:27 +0000)

----------------------------------------------------------------
Third set of new stuff for IIO in the 4.5 cycle.

New driver features
- us5182
  * Add interrupt support and rising / falling threshold events.

Cleanups / fixes to new stuff / minor additions
* Expose the IIO value formatting function for drivers to
  make use of internally.
- ina2xx
   * Fix wrong channel order
   * Fix incorrect reporting of endianness
   * Adding documentation of ABI unique to this device
- mma8452
  * Drop an unused register description
  * Use an enum for the channel index to aid readability
- sca3000
  * Use standard NULL comparison style
- us5182
  * fix an inconsistency in status of enable (a bug with no real effect until
    above patches are applied)
  * refactor the read_raw function to improve maintainability / readability.

----------------------------------------------------------------
Adriana Reus (3):
      iio: light: us5182d: Fix enable status inconcistency
      iio: light: us5182d: Add interrupt support and events
      iio: light: us5182d: Refactor read_raw function

Andrew F. Davis (1):
      iio: Make IIO value formating function globally available.

Bhaktipriya Shridhar (1):
      Staging: iio: accel: sca3000: Fixed NULL comparison style

Jonathan Cameron (1):
      iio: adc: ina2xx: Fix incorrect report of data endianness to userspace.

Marc Titinger (2):
      iio: ina2xx: fix channel order in software buffer
      iio: ina2xx: add ABI documentation entry sysfs-bus-iio-ina2xx-adc

Martin Kepplinger (2):
      iio: mma8452: remove unused register description
      iio: mma8452: use enum for channel index

 Documentation/ABI/testing/sysfs-bus-iio-ina2xx-adc |  24 ++
 drivers/iio/accel/mma8452.c                        |  40 +-
 drivers/iio/adc/ina2xx-adc.c                       |   6 +-
 drivers/iio/industrialio-core.c                    |   1 +
 drivers/iio/light/us5182d.c                        | 442 +++++++++++++++++----
 drivers/staging/iio/accel/sca3000_ring.c           |   2 +-
 include/linux/iio/iio.h                            |   2 +
 7 files changed, 414 insertions(+), 103 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-ina2xx-adc

             reply	other threads:[~2015-12-22 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 19:04 Jonathan Cameron [this message]
2015-12-27  1:06 ` [PULL] Third set of IIO new stuff for the 4.5 cycle Greg KH

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=56799EA6.1010909@kernel.org \
    --to=jic23@kernel.org \
    --cc=gregkh@linuxfoundation.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