From: Jonathan Cameron <jic23@kernel.org>
To: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
Cc: lars@metafoo.de, linux-iio@vger.kernel.org,
stable@vger.kernel.org, Fawzi Khaber <fawzi.khaber@tdk.com>,
Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Subject: Re: [PATCH v2] iio: fix iio_format_avail_range() printing for none IIO_VAL_INT
Date: Tue, 19 Jul 2022 09:31:52 +0100 [thread overview]
Message-ID: <20220719093152.5d3ac7d6@jic23-huawei> (raw)
In-Reply-To: <20220718130706.32571-1-jmaneyrol@invensense.com>
On Mon, 18 Jul 2022 15:07:06 +0200
Jean-Baptiste Maneyrol <jmaneyrol@invensense.com> wrote:
> From: Fawzi Khaber <fawzi.khaber@tdk.com>
>
> iio_format_avail_range() should print range as follow [min, step, max], so
> the function was previously calling iio_format_list() with length = 3,
> length variable refers to the array size of values not the number of
> elements. In case of non IIO_VAL_INT values each element has integer part
> and decimal part. With length = 3 this would cause premature end of loop
> and result in printing only one element.
>
> Signed-off-by: Fawzi Khaber <fawzi.khaber@tdk.com>
> Signed-off-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> Fixes: eda20ba1e25e ("iio: core: Consolidate iio_format_avail_{list,range}()")
As I'm hoping to sneak in a late pull request for the coming merge window
(as the cycle has been delayed), I've picked this on up on the togreg branch of iio.git.
+ marked for stable.
Thanks,
Jonathan
> ---
> drivers/iio/industrialio-core.c | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
> index 358b909298c0..0f4dbda3b9d3 100644
> --- a/drivers/iio/industrialio-core.c
> +++ b/drivers/iio/industrialio-core.c
> @@ -812,7 +812,23 @@ static ssize_t iio_format_avail_list(char *buf, const int *vals,
>
> static ssize_t iio_format_avail_range(char *buf, const int *vals, int type)
> {
> - return iio_format_list(buf, vals, type, 3, "[", "]");
> + int length;
> +
> + /*
> + * length refers to the array size , not the number of elements.
> + * The purpose is to print the range [min , step ,max] so length should
> + * be 3 in case of int, and 6 for other types.
> + */
> + switch (type) {
> + case IIO_VAL_INT:
> + length = 3;
> + break;
> + default:
> + length = 6;
> + break;
> + }
> +
> + return iio_format_list(buf, vals, type, length, "[", "]");
> }
>
> static ssize_t iio_read_channel_info_avail(struct device *dev,
prev parent reply other threads:[~2022-07-19 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 13:07 [PATCH v2] iio: fix iio_format_avail_range() printing for none IIO_VAL_INT Jean-Baptiste Maneyrol
2022-07-19 8:31 ` 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=20220719093152.5d3ac7d6@jic23-huawei \
--to=jic23@kernel.org \
--cc=fawzi.khaber@tdk.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jmaneyrol@invensense.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=stable@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