From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: Handle enumerated properties with gaps
Date: Sun, 10 Dec 2017 17:19:41 +0000 [thread overview]
Message-ID: <20171210171941.5740d639@archlinux> (raw)
In-Reply-To: <20171207094209.14748-1-lars@metafoo.de>
On Thu, 7 Dec 2017 10:42:09 +0100
Lars-Peter Clausen <lars@metafoo.de> wrote:
> Some enums might have gaps or reserved values in the middle of their value
> range. E.g. consider a 2-bit enum where the values 0, 1 and 3 have a
> meaning, but 2 is a reserved value and must not be used.
>
> Add support for such enums to the IIO enum helper functions. A reserved
> value is marked by setting its entry in the items array to NULL rather
> than the normal descriptive string value.
>
> Unfortunately that means we can no longer use __sysfs_match_string() since
> it treats a NULL entry as the array terminator. But the amount of
> boilerplate is manageable.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
> Open for suggestions on how to massage __sysfs_match_string() into handling
> this use-case.
In theory - that function should only use the null terminator in
the case of n == -1. Or so it's documentation implies...
However to make that actually the case, we would have
to be sure of causing no breakage which would be hard to do.
Mind you it's only used in a few places, so you could check them.
>From a quick scan over them it looks like you would fine to make
the change (the single non IIO user is clearly fine.)
> ---
> drivers/iio/industrialio-core.c | 21 +++++++++++++++------
> 1 file changed, 15 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> index 2e8e36f9da61..e69bef13d005 100644
> --- a/drivers/iio/industrialio-core.c
> +++ b/drivers/iio/industrialio-core.c
> @@ -446,8 +446,12 @@ ssize_t iio_enum_available_read(struct iio_dev *indio_dev,
> if (!e->num_items)
> return 0;
>
> - for (i = 0; i < e->num_items; ++i)
> + for (i = 0; i < e->num_items; ++i) {
> + if (!e->items[i])
> + continue;
> +
> len += scnprintf(buf + len, PAGE_SIZE - len, "%s ", e->items[i]);
> + }
>
> /* replace last space with a newline */
> buf[len - 1] = '\n';
> @@ -468,7 +472,7 @@ ssize_t iio_enum_read(struct iio_dev *indio_dev,
> i = e->get(indio_dev, chan);
> if (i < 0)
> return i;
> - else if (i >= e->num_items)
> + else if (i >= e->num_items || !e->items[i])
> return -EINVAL;
>
> return snprintf(buf, PAGE_SIZE, "%s\n", e->items[i]);
> @@ -480,16 +484,21 @@ ssize_t iio_enum_write(struct iio_dev *indio_dev,
> size_t len)
> {
> const struct iio_enum *e = (const struct iio_enum *)priv;
> + unsigned int i;
> int ret;
>
> if (!e->set)
> return -EINVAL;
>
> - ret = __sysfs_match_string(e->items, e->num_items, buf);
> - if (ret < 0)
> - return ret;
> + for (i = 0; i < e->num_items; i++) {
> + if (e->items[i] && sysfs_streq(buf, e->items[i]))
> + break;
> + }
> +
> + if (i == e->num_items)
> + return -EINVAL;
>
> - ret = e->set(indio_dev, chan, ret);
> + ret = e->set(indio_dev, chan, i);
> return ret ? ret : len;
> }
> EXPORT_SYMBOL_GPL(iio_enum_write);
next prev parent reply other threads:[~2017-12-10 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 9:42 [PATCH] iio: Handle enumerated properties with gaps Lars-Peter Clausen
2017-12-10 17:19 ` Jonathan Cameron [this message]
2017-12-11 8:09 ` Andy Shevchenko
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=20171210171941.5740d639@archlinux \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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.