linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: [PATCH 0/3] iio: Hardware buffer improvements
Date: Fri, 29 May 2015 18:14:19 +0200	[thread overview]
Message-ID: <1432916062-15195-1-git-send-email-lars@metafoo.de> (raw)

Hi,

This series has a few small improvements for hardware buffer support.

The first patch makes sure that we always compute the masklength for the
scanmask, even if the driver does not register a userspace accessable
buffer. This makes it possible to support cases where the data of the
device can not be accessed by software but is directly passed to a
different device which can then register a in kernel consumer to control
the buffer of the device.

The second patch adds support for specifying the supported buffer modes for
each buffer type. This makes sure that the correct mode is chosen when a
device driver support multiple types, e.g. both software and hardware
buffers and also makes sure that we can attach buffers which are not
supported by the device (e.g. callback buffer to sca3000).

The last patch makes sure that when running in hardware mode the scan mask
matching is strict since there is no software demuxer in that case.

- Lars

Lars-Peter Clausen (3):
  iio: Always compute masklength
  iio: Specify supported modes for buffers
  iio: Require strict scan mask matching in hardware mode

 drivers/iio/buffer_cb.c                  |  2 ++
 drivers/iio/industrialio-buffer.c        | 58 ++++++++++++++++++++++++--------
 drivers/iio/kfifo_buf.c                  |  2 ++
 drivers/staging/iio/accel/sca3000_ring.c |  2 ++
 include/linux/iio/buffer.h               |  3 ++
 5 files changed, 53 insertions(+), 14 deletions(-)

-- 
2.1.4


             reply	other threads:[~2015-05-29 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 16:14 Lars-Peter Clausen [this message]
2015-05-29 16:14 ` [PATCH 1/3] iio: Always compute masklength Lars-Peter Clausen
2015-06-01 10:28   ` Jonathan Cameron
2015-05-29 16:14 ` [PATCH 2/3] iio: Specify supported modes for buffers Lars-Peter Clausen
2015-06-01 10:31   ` Jonathan Cameron
2016-01-01 17:50   ` Jonathan Cameron
2015-05-29 16:14 ` [PATCH 3/3] iio: Require strict scan mask matching in hardware mode Lars-Peter Clausen
2015-06-01 10:34   ` Jonathan Cameron
2015-06-03 17:19     ` Lars-Peter Clausen
2015-06-06 21:07       ` 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=1432916062-15195-1-git-send-email-lars@metafoo.de \
    --to=lars@metafoo.de \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).