From: Jonathan Cameron <jic23@kernel.org>
To: <alexandru.tachici@analog.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/8] iio: adc: ad7124: Remove shift from scan_type
Date: Sat, 19 Mar 2022 15:38:41 +0000 [thread overview]
Message-ID: <20220319153841.2483194a@jic23-huawei> (raw)
In-Reply-To: <20220318162722.51215-2-alexandru.tachici@analog.com>
On Fri, 18 Mar 2022 18:27:15 +0200
<alexandru.tachici@analog.com> wrote:
> From: Alexandru Tachici <alexandru.tachici@analog.com>
>
> The 24 bits data is stored in 32 bits in BE. There
> is no need to shift it. This confuses user-space apps.
>
> Fixes: b3af341bbd966 ("iio: adc: Add ad7124 support")
> Signed-off-by: Alexandru Tachici <alexandru.tachici@analog.com>
Hi Alexandru,
Just to confirm my understanding (which gets a bit messy when endian
conversions are involved - and it occurs to me that our docs
are not great on how to handle endian conversions with shifts).
With a little endian cpu:
After userspace performs the 32bit big endian to little endian conversion
the value the shift would have previously dropped the bottom 8 bits
of the channel reading?
Looking at what ad_sigma_delta is doing it's documented as
leaving the upper 8 bits as 0 so this would make sense.
Have I understood the issue correctly?
I'll need to hold this one for now as I'll need to rebase the
fixes-togreg branch of iio.git after rc1 is available.
Thanks,
Jonathan
> ---
> drivers/iio/adc/ad7124.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/iio/adc/ad7124.c b/drivers/iio/adc/ad7124.c
> index 998a342d51a6..7249db2c4422 100644
> --- a/drivers/iio/adc/ad7124.c
> +++ b/drivers/iio/adc/ad7124.c
> @@ -188,7 +188,6 @@ static const struct iio_chan_spec ad7124_channel_template = {
> .sign = 'u',
> .realbits = 24,
> .storagebits = 32,
> - .shift = 8,
> .endianness = IIO_BE,
> },
> };
next prev parent reply other threads:[~2022-03-19 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 16:27 [PATCH v2 0/8] iio: adc: ad_sigma_delta: Add sequencer support alexandru.tachici
2022-03-18 16:27 ` [PATCH v2 1/8] iio: adc: ad7124: Remove shift from scan_type alexandru.tachici
2022-03-19 15:38 ` Jonathan Cameron [this message]
2022-03-18 16:27 ` [PATCH v2 2/8] iio: adc: ad7124: Add update_scan_mode alexandru.tachici
2022-03-19 15:45 ` Jonathan Cameron
2022-03-18 16:27 ` [PATCH v2 3/8] iio: adc: ad7192: " alexandru.tachici
2022-03-18 16:27 ` [PATCH v2 4/8] iio: adc: ad_sigma_delta: Add sequencer support alexandru.tachici
2022-03-19 16:03 ` Jonathan Cameron
2022-03-18 16:27 ` [PATCH v2 5/8] iio: adc: ad7124: add " alexandru.tachici
2022-03-19 16:09 ` Jonathan Cameron
2022-03-18 16:27 ` [PATCH v2 6/8] iio: adc: ad7192: " alexandru.tachici
2022-03-19 16:11 ` Jonathan Cameron
2022-03-18 16:27 ` [PATCH v2 7/8] iio: adc: ad7124: add disable_all() callback alexandru.tachici
2022-03-19 16:10 ` Jonathan Cameron
2022-03-18 16:27 ` [PATCH v2 8/8] iio: adc: ad7192: " alexandru.tachici
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=20220319153841.2483194a@jic23-huawei \
--to=jic23@kernel.org \
--cc=alexandru.tachici@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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