From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/3] iio: Add data_available callback for buffers
Date: Sat, 30 Nov 2013 12:06:16 +0000 [thread overview]
Message-ID: <5299D4B8.3050701@kernel.org> (raw)
In-Reply-To: <1385391404-3112-1-git-send-email-lars@metafoo.de>
On 11/25/13 14:56, Lars-Peter Clausen wrote:
> This patch adds a new data_available() callback to the iio_buffer_access_funcs
> struct. The callback is used to indicate whether data is available in the buffer
> for reading. It is meant to replace the stufftoread flag from the iio_buffer
> struct. The reasoning for this is that the buffer implementation usually can
> determine whether data is available rather easily based on its state, on the
> other hand it can be rather tricky to update the stufftoread flag in a race free
> way.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
A sensible change - applied to the togreg branch of iio.git.
> ---
> drivers/iio/industrialio-buffer.c | 10 +++++++++-
> include/linux/iio/buffer.h | 3 +++
> 2 files changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/industrialio-buffer.c b/drivers/iio/industrialio-buffer.c
> index 7f9152c..4dcc3a0 100644
> --- a/drivers/iio/industrialio-buffer.c
> +++ b/drivers/iio/industrialio-buffer.c
> @@ -37,6 +37,14 @@ static bool iio_buffer_is_active(struct iio_buffer *buf)
> return !list_empty(&buf->buffer_list);
> }
>
> +static bool iio_buffer_data_available(struct iio_buffer *buf)
> +{
> + if (buf->access->data_available)
> + return buf->access->data_available(buf);
> +
> + return buf->stufftoread;
> +}
> +
> /**
> * iio_buffer_read_first_n_outer() - chrdev read for buffer access
> *
> @@ -70,7 +78,7 @@ unsigned int iio_buffer_poll(struct file *filp,
> return -ENODEV;
>
> poll_wait(filp, &rb->pollq, wait);
> - if (rb->stufftoread)
> + if (iio_buffer_data_available(rb))
> return POLLIN | POLLRDNORM;
> /* need a way of knowing if there may be enough data... */
> return 0;
> diff --git a/include/linux/iio/buffer.h b/include/linux/iio/buffer.h
> index 15607b4..5193927 100644
> --- a/include/linux/iio/buffer.h
> +++ b/include/linux/iio/buffer.h
> @@ -21,6 +21,8 @@ struct iio_buffer;
> * struct iio_buffer_access_funcs - access functions for buffers.
> * @store_to: actually store stuff to the buffer
> * @read_first_n: try to get a specified number of bytes (must exist)
> + * @data_available: indicates whether data for reading from the buffer is
> + * available.
> * @request_update: if a parameter change has been marked, update underlying
> * storage.
> * @get_bytes_per_datum:get current bytes per datum
> @@ -43,6 +45,7 @@ struct iio_buffer_access_funcs {
> int (*read_first_n)(struct iio_buffer *buffer,
> size_t n,
> char __user *buf);
> + bool (*data_available)(struct iio_buffer *buffer);
>
> int (*request_update)(struct iio_buffer *buffer);
>
>
prev parent reply other threads:[~2013-11-30 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 14:56 [PATCH 1/3] iio: Add data_available callback for buffers Lars-Peter Clausen
2013-11-25 14:56 ` [PATCH 2/3] iio: kfifo_buf: Implement data_available() callback Lars-Peter Clausen
2013-11-30 12:09 ` Jonathan Cameron
2013-11-25 14:56 ` [PATCH 3/3] iio: Add support for blocking IO on buffers Lars-Peter Clausen
2013-11-30 12:13 ` Jonathan Cameron
2013-11-30 12:06 ` Jonathan Cameron [this message]
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=5299D4B8.3050701@kernel.org \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--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).