From: Karol Wrona <k.wrona@samsung.com>
To: Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-kernel@vger.kernel.org
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Karol Wrona <wrona.vy@gmail.com>,
Karol Wrona <k.wrona@samsung.com>
Subject: [PATCH 0/2] iio: Add no-triggered buffer helper functions
Date: Thu, 08 Jan 2015 17:40:25 +0100 [thread overview]
Message-ID: <1420735227-21091-1-git-send-email-k.wrona@samsung.com> (raw)
Hello,
This small patchset introduces helpers for iio kfifo which are useful when
IIO_HARDWARE/SOFTWARE_BUFFER is used. I decided to do it similar to Lars'
industrialio-triggered-buffer as a separate module what can be considered
as overkill but there is some risk that this source file will grow as new
needs will appear. Also it gives some flexibility with buffer handling choice.
Second patch deselect IIO_TRIGGER for iio kfifo. I think that there is no need
to use triggers always when iio kfifo is used and IIO_TRIGGERED_BUFFER also
selects IIO_KFIFO_BUF. I need some comments for this one to be sure if I do not
missed something. TI's AM335X ADC driver uses kfifo directly but without
triggered buffer/trigger in its sources so I hope there should be no problem
with that.
Thanks,
Karol
Karol Wrona (2):
iio: Add no-triggered buffer helper functions
iio: Deselect IIO_TRIGGER for IIO_KFIFO_BUF
drivers/iio/Kconfig | 7 ++-
drivers/iio/Makefile | 1 +
drivers/iio/industrialio-notriggered-buffer.c | 72 +++++++++++++++++++++++++
include/linux/iio/notriggered-buffer.h | 11 ++++
4 files changed, 90 insertions(+), 1 deletion(-)
create mode 100644 drivers/iio/industrialio-notriggered-buffer.c
create mode 100644 include/linux/iio/notriggered-buffer.h
--
1.7.9.5
next reply other threads:[~2015-01-08 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 16:40 Karol Wrona [this message]
2015-01-08 16:40 ` [PATCH 1/2] " Karol Wrona
2015-01-10 11:10 ` Lars-Peter Clausen
2015-01-10 18:22 ` Jonathan Cameron
2015-01-12 9:31 ` Karol Wrona
2015-01-08 16:40 ` [PATCH 2/2] iio: Deselect IIO_TRIGGER for IIO_KFIFO_BUF Karol Wrona
2015-01-10 11:11 ` Lars-Peter Clausen
2015-01-10 18:19 ` 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=1420735227-21091-1-git-send-email-k.wrona@samsung.com \
--to=k.wrona@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=kyungmin.park@samsung.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=wrona.vy@gmail.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
all inboxes | Powered by JetHome®