From: Jonathan Cameron <jic23@kernel.org>
To: Artur Rojek <contact@artur-rojek.eu>
Cc: Paul Cercueil <paul@crapouillou.net>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Chris Morgan <macromorgan@hotmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-mips@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v2 1/2] iio/adc: ingenic: Fix channel offsets in buffer
Date: Sun, 28 May 2023 18:49:35 +0100 [thread overview]
Message-ID: <20230528184935.15dd91fa@jic23-huawei> (raw)
In-Reply-To: <20230521225901.388455-2-contact@artur-rojek.eu>
On Mon, 22 May 2023 00:59:00 +0200
Artur Rojek <contact@artur-rojek.eu> wrote:
> Consumers expect the buffer to only contain enabled channels. While
> preparing the buffer, the driver makes two mistakes:
> 1) It inserts empty data for disabled channels.
> 2) Each ADC readout contains samples for two 16-bit channels. If either
> of them is active, the whole 32-bit sample is pushed into the buffer
> as-is.
>
> Both of those issues cause the active channels to appear at the wrong
> offsets in the buffer. Fix the above by demuxing samples for active
> channels only.
>
> This has remained unnoticed, as all the consumers so far were only using
> channels 0 and 1, leaving them unaffected by changes introduced in this
> commit.
>
> Signed-off-by: Artur Rojek <contact@artur-rojek.eu>
> Tested-by: Paul Cercueil <paul@crapouillou.net>
Lazy me suggestions that, as we didn't notice this before, clearly the
vast majority of times the channels are both enabled.
As such you 'could' just set available_scan_masks and burn the overhead
of reading channels you don't want, instead letting the IIO core demux
deal with the data movement if needed.
> ---
>
> v2: - demux active channels from ADC readouts
> - clarify in the commit description that this patch doesn't impact
> existing consumers of this driver
>
> drivers/iio/adc/ingenic-adc.c | 20 +++++++++++++-------
> 1 file changed, 13 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/iio/adc/ingenic-adc.c b/drivers/iio/adc/ingenic-adc.c
> index a7325dbbb99a..093710a7ad4c 100644
> --- a/drivers/iio/adc/ingenic-adc.c
> +++ b/drivers/iio/adc/ingenic-adc.c
> @@ -802,13 +802,19 @@ static irqreturn_t ingenic_adc_irq(int irq, void *data)
> struct ingenic_adc *adc = iio_priv(iio_dev);
> unsigned long mask = iio_dev->active_scan_mask[0];
> unsigned int i;
> - u32 tdat[3];
> -
> - for (i = 0; i < ARRAY_SIZE(tdat); mask >>= 2, i++) {
> - if (mask & 0x3)
> - tdat[i] = readl(adc->base + JZ_ADC_REG_ADTCH);
> - else
> - tdat[i] = 0;
> + u16 tdat[6];
> + u32 val;
> +
> + memset(tdat, 0, ARRAY_SIZE(tdat));
> + for (i = 0; mask && i < ARRAY_SIZE(tdat); mask >>= 2) {
> + if (mask & 0x3) {
> + val = readl(adc->base + JZ_ADC_REG_ADTCH);
> + /* Two channels per sample. Demux active. */
> + if (mask & BIT(0))
> + tdat[i++] = val & 0xffff;
> + if (mask & BIT(1))
> + tdat[i++] = val >> 16;
> + }
> }
>
> iio_push_to_buffers(iio_dev, tdat);
next prev parent reply other threads:[~2023-05-28 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 22:58 [PATCH v2 0/2] iio/adc-joystick: buffer data parsing fixes Artur Rojek
2023-05-21 22:59 ` [PATCH v2 1/2] iio/adc: ingenic: Fix channel offsets in buffer Artur Rojek
2023-05-22 10:15 ` Andy Shevchenko
2023-05-22 10:18 ` Andy Shevchenko
2023-05-22 10:23 ` Paul Cercueil
2023-05-22 11:05 ` Andy Shevchenko
2023-05-22 11:35 ` Paul Cercueil
2023-05-22 19:05 ` Andy Shevchenko
2023-05-22 10:20 ` Paul Cercueil
2023-05-22 11:05 ` Andy Shevchenko
2023-05-28 17:49 ` Jonathan Cameron [this message]
2023-05-21 22:59 ` [PATCH v2 2/2] input: joystick: Fix buffer data parsing Artur Rojek
2023-05-22 10:58 ` 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=20230528184935.15dd91fa@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=contact@artur-rojek.eu \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macromorgan@hotmail.com \
--cc=paul@crapouillou.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox