From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <mranostay@gmail.com>, linux-iio@vger.kernel.org
Subject: Re: [RFC v4 1/3] iio: buffer-callback: allow getting underlying iio_dev
Date: Sun, 21 Aug 2016 11:47:51 +0100 [thread overview]
Message-ID: <9d3f7821-1c9e-d8b2-27ba-fd6d73f683f6@kernel.org> (raw)
In-Reply-To: <1471663024-25623-2-git-send-email-mranostay@gmail.com>
On 20/08/16 04:17, Matt Ranostay wrote:
> Add iio_channel_cb_get_iio_dev function to allow getting the
> underlying iio_dev. This is useful for setting the trigger of the
> consumer ADC device.
>
> Signed-off-by: Matt Ranostay <mranostay@gmail.com>
Clearly going to be a necessary bit of infrastructure.
Applied to the togreg branch of iio.git - initially pushed out as
testing for the autobuilders to play with it.
Thanks,
Jonathan
> ---
> drivers/iio/buffer/industrialio-buffer-cb.c | 24 ++++++++++++++----------
> include/linux/iio/consumer.h | 12 ++++++++++++
> 2 files changed, 26 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/iio/buffer/industrialio-buffer-cb.c b/drivers/iio/buffer/industrialio-buffer-cb.c
> index 323079c3ccce..b8f550e47d3d 100644
> --- a/drivers/iio/buffer/industrialio-buffer-cb.c
> +++ b/drivers/iio/buffer/industrialio-buffer-cb.c
> @@ -18,6 +18,7 @@ struct iio_cb_buffer {
> int (*cb)(const void *data, void *private);
> void *private;
> struct iio_channel *channels;
> + struct iio_dev *indio_dev;
> };
>
> static struct iio_cb_buffer *buffer_to_cb_buffer(struct iio_buffer *buffer)
> @@ -52,7 +53,6 @@ struct iio_cb_buffer *iio_channel_get_all_cb(struct device *dev,
> {
> int ret;
> struct iio_cb_buffer *cb_buff;
> - struct iio_dev *indio_dev;
> struct iio_channel *chan;
>
> cb_buff = kzalloc(sizeof(*cb_buff), GFP_KERNEL);
> @@ -72,17 +72,17 @@ struct iio_cb_buffer *iio_channel_get_all_cb(struct device *dev,
> goto error_free_cb_buff;
> }
>
> - indio_dev = cb_buff->channels[0].indio_dev;
> + cb_buff->indio_dev = cb_buff->channels[0].indio_dev;
> cb_buff->buffer.scan_mask
> - = kcalloc(BITS_TO_LONGS(indio_dev->masklength), sizeof(long),
> - GFP_KERNEL);
> + = kcalloc(BITS_TO_LONGS(cb_buff->indio_dev->masklength),
> + sizeof(long), GFP_KERNEL);
> if (cb_buff->buffer.scan_mask == NULL) {
> ret = -ENOMEM;
> goto error_release_channels;
> }
> chan = &cb_buff->channels[0];
> while (chan->indio_dev) {
> - if (chan->indio_dev != indio_dev) {
> + if (chan->indio_dev != cb_buff->indio_dev) {
> ret = -EINVAL;
> goto error_free_scan_mask;
> }
> @@ -105,17 +105,14 @@ EXPORT_SYMBOL_GPL(iio_channel_get_all_cb);
>
> int iio_channel_start_all_cb(struct iio_cb_buffer *cb_buff)
> {
> - return iio_update_buffers(cb_buff->channels[0].indio_dev,
> - &cb_buff->buffer,
> + return iio_update_buffers(cb_buff->indio_dev, &cb_buff->buffer,
> NULL);
> }
> EXPORT_SYMBOL_GPL(iio_channel_start_all_cb);
>
> void iio_channel_stop_all_cb(struct iio_cb_buffer *cb_buff)
> {
> - iio_update_buffers(cb_buff->channels[0].indio_dev,
> - NULL,
> - &cb_buff->buffer);
> + iio_update_buffers(cb_buff->indio_dev, NULL, &cb_buff->buffer);
> }
> EXPORT_SYMBOL_GPL(iio_channel_stop_all_cb);
>
> @@ -133,6 +130,13 @@ struct iio_channel
> }
> EXPORT_SYMBOL_GPL(iio_channel_cb_get_channels);
>
> +struct iio_dev
> +*iio_channel_cb_get_iio_dev(const struct iio_cb_buffer *cb_buffer)
> +{
> + return cb_buffer->indio_dev;
> +}
> +EXPORT_SYMBOL_GPL(iio_channel_cb_get_iio_dev);
> +
> MODULE_AUTHOR("Jonathan Cameron <jic23@kernel.org>");
> MODULE_DESCRIPTION("Industrial I/O callback buffer");
> MODULE_LICENSE("GPL");
> diff --git a/include/linux/iio/consumer.h b/include/linux/iio/consumer.h
> index 3d672f72e7ec..9edccfba1ffb 100644
> --- a/include/linux/iio/consumer.h
> +++ b/include/linux/iio/consumer.h
> @@ -165,6 +165,18 @@ struct iio_channel
> *iio_channel_cb_get_channels(const struct iio_cb_buffer *cb_buffer);
>
> /**
> + * iio_channel_cb_get_iio_dev() - get access to the underlying device.
> + * @cb_buffer: The callback buffer from whom we want the device
> + * information.
> + *
> + * This function allows one to obtain information about the device.
> + * The primary aim is to allow drivers that are consuming a device to query
> + * things like current trigger.
> + */
> +struct iio_dev
> +*iio_channel_cb_get_iio_dev(const struct iio_cb_buffer *cb_buffer);
> +
> +/**
> * iio_read_channel_raw() - read from a given channel
> * @chan: The channel being queried.
> * @val: Value read back.
>
next prev parent reply other threads:[~2016-08-21 10:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-20 3:17 [RFC v4 0/3] iio: potentiostat: add LMP91000 support Matt Ranostay
2016-08-20 3:17 ` [RFC v4 1/3] iio: buffer-callback: allow getting underlying iio_dev Matt Ranostay
2016-08-21 10:47 ` Jonathan Cameron [this message]
2016-08-20 3:17 ` [RFC v4 2/3] iio: adc: ti-adc161s626: add support for TI 1-channel differential ADCs Matt Ranostay
2016-08-20 16:47 ` Marek Vasut
2016-08-21 10:51 ` Jonathan Cameron
2016-08-20 3:17 ` [RFC v4 3/3] iio: potentiostat: add LMP91000 support Matt Ranostay
2016-08-21 10:46 ` Jonathan Cameron
2016-08-26 3:09 ` Matt Ranostay
2016-08-29 17:38 ` Jonathan Cameron
2016-08-30 6:01 ` Matt Ranostay
2016-09-03 14:59 ` Jonathan Cameron
2016-09-04 4:56 ` Matt Ranostay
2016-09-06 1:58 ` Matt Ranostay
2016-09-10 14:18 ` 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=9d3f7821-1c9e-d8b2-27ba-fd6d73f683f6@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=mranostay@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;
as well as URLs for NNTP newsgroup(s).