From: Vlad Dogaru <vlad.dogaru@intel.com>
To: linux-iio@vger.kernel.org
Subject: Re: [PATCH v3] iio: ensure scan index is unique at device register
Date: Mon, 29 Dec 2014 11:23:58 +0200 [thread overview]
Message-ID: <20141229092358.GC16917@vdogaru> (raw)
In-Reply-To: <1419844489-8890-1-git-send-email-vlad.dogaru@intel.com>
On Mon, Dec 29, 2014 at 11:14:49AM +0200, Vlad Dogaru wrote:
> Having two or more channels with the same positive scan_index field
> makes no sense. Prevent this situation by failing to register a device
> if two scan indexes are identical.
Please drop this, I will send an updated version shortly.
The current patch refuses to register the rather common situation where
a device doesn't support buffering and doesn't explicitly set scan_index
for its channels (thus defaulting to zero). Sorry for the noise.
> Signed-off-by: Vlad Dogaru <vlad.dogaru@intel.com>
> Reviewed-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
> Changes since v2:
> - rebase to latest togreg branch.
> Changes since v1:
> - remove redundant check for scan_index < 0 in the inner loop.
>
> drivers/iio/industrialio-core.c | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> index ee442ee..dad6163 100644
> --- a/drivers/iio/industrialio-core.c
> +++ b/drivers/iio/industrialio-core.c
> @@ -1135,6 +1135,26 @@ static const struct file_operations iio_buffer_fileops = {
> .compat_ioctl = iio_ioctl,
> };
>
> +static int iio_check_unique_scan_index(struct iio_dev *indio_dev)
> +{
> + int i, j;
> + const struct iio_chan_spec *channels = indio_dev->channels;
> +
> + for (i = 0; i < indio_dev->num_channels - 1; i++) {
> + if (channels[i].scan_index < 0)
> + continue;
> + for (j = i + 1; j < indio_dev->num_channels; j++)
> + if (channels[i].scan_index == channels[j].scan_index) {
> + dev_err(&indio_dev->dev,
> + "Duplicate scan index %d\n",
> + channels[i].scan_index);
> + return -EINVAL;
> + }
> + }
> +
> + return 0;
> +}
> +
> static const struct iio_buffer_setup_ops noop_ring_setup_ops;
>
> /**
> @@ -1149,6 +1169,10 @@ int iio_device_register(struct iio_dev *indio_dev)
> if (!indio_dev->dev.of_node && indio_dev->dev.parent)
> indio_dev->dev.of_node = indio_dev->dev.parent->of_node;
>
> + ret = iio_check_unique_scan_index(indio_dev);
> + if (ret < 0)
> + return ret;
> +
> /* configure elements for the chrdev */
> indio_dev->dev.devt = MKDEV(MAJOR(iio_devt), indio_dev->id);
>
> --
> 1.9.1
>
prev parent reply other threads:[~2014-12-29 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 9:14 [PATCH v3] iio: ensure scan index is unique at device register Vlad Dogaru
2014-12-29 9:23 ` Vlad Dogaru [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=20141229092358.GC16917@vdogaru \
--to=vlad.dogaru@intel.com \
--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