From: Lars-Peter Clausen <lars@metafoo.de>
To: mfornero@gmail.com, jic23@kernel.org
Cc: linux-iio@vger.kernel.org, Matt Fornero <matt.fornero@mathworks.com>
Subject: Re: [PATCH v2] iio: buffer: Expose data available
Date: Wed, 6 Dec 2017 13:10:53 +0100 [thread overview]
Message-ID: <e4f1d159-d0b2-ce1b-4468-fc6f1b9e0601@metafoo.de> (raw)
In-Reply-To: <1512507416-21856-1-git-send-email-mfornero@gmail.com>
On 12/05/2017 09:56 PM, mfornero@gmail.com wrote:
> From: Matt Fornero <matt.fornero@mathworks.com>
>
> Add a sysfs attribute that exposes buffer data available to userspace.
> This attribute can be checked at runtime to determine the overall buffer
> fill level (across all allocated buffers).
>
> Signed-off-by: Matt Fornero <matt.fornero@mathworks.com>
Looks sensible to me. I think we need an update to the ABI documentation as
well for this in Documentation/ABI/testing/sysfs-bus-iio
> ---
> v1 -> v2:
> - Use iio_buffer_data_available() for all buffers instead
> of only DMA buffers
>
> drivers/iio/industrialio-buffer.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/iio/industrialio-buffer.c b/drivers/iio/industrialio-buffer.c
> index d80f830..e7bdfa3 100644
> --- a/drivers/iio/industrialio-buffer.c
> +++ b/drivers/iio/industrialio-buffer.c
> @@ -1121,6 +1121,18 @@ static ssize_t iio_buffer_store_watermark(struct device *dev,
> return ret ? ret : len;
> }
>
> +static ssize_t iio_dma_show_data_available(struct device *dev,
> + struct device_attribute *attr,
> + char *buf)
> +{
> + struct iio_dev *indio_dev = dev_to_iio_dev(dev);
> + size_t bytes;
> +
> + bytes = iio_buffer_data_available(indio_dev->buffer);
> +
> + return sprintf(buf, "%llu\n", (unsigned long long)bytes);
Since this is the kernel we shouldn't need those MSVC workarounds ;)
"%zu" should work
> +}
[..]
next prev parent reply other threads:[~2017-12-06 12:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 20:46 [PATCH] iio: buffer-dma: Expose data available mfornero
2017-12-02 11:52 ` Jonathan Cameron
2017-12-05 9:32 ` Lars-Peter Clausen
2017-12-05 18:01 ` Matthew Fornero
2017-12-05 18:08 ` Lars-Peter Clausen
2017-12-05 18:11 ` Matthew Fornero
2017-12-05 18:38 ` Lars-Peter Clausen
2017-12-05 18:05 ` Matthew Fornero
2017-12-05 20:56 ` [PATCH v2] iio: buffer: " mfornero
2017-12-06 12:10 ` Lars-Peter Clausen [this message]
2017-12-06 19:43 ` [PATCH v3] " mfornero
2017-12-10 16:21 ` 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=e4f1d159-d0b2-ce1b-4468-fc6f1b9e0601@metafoo.de \
--to=lars@metafoo.de \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=matt.fornero@mathworks.com \
--cc=mfornero@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.