From: Paul Cercueil <paul@crapouillou.net>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Artur Rojek <contact@artur-rojek.eu>
Cc: Jonathan Cameron <jic23@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Chris Morgan <macromorgan@hotmail.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: Mon, 22 May 2023 12:23:43 +0200 [thread overview]
Message-ID: <2fc0874ce8a802aeb98e553b15e27fb4d4b75a1c.camel@crapouillou.net> (raw)
In-Reply-To: <CAHp75VedgVOA4qTJFeVuabKXBaB=y4Ss0fLu7a7J9GGgWFPqQg@mail.gmail.com>
Hi Andy,
Le lundi 22 mai 2023 à 13:18 +0300, Andy Shevchenko a écrit :
> On Mon, May 22, 2023 at 1:15 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Mon, May 22, 2023 at 1:59 AM Artur Rojek
> > <contact@artur-rojek.eu> wrote:
>
> ...
>
> > > + u16 tdat[6];
> > > + u32 val;
> > > +
> > > + memset(tdat, 0, ARRAY_SIZE(tdat));
> >
> > Yeah, as LKP tells us this should be sizeof() instead of
> > ARRAY_SIZE().
> >
> > > + for (i = 0; mask && i < ARRAY_SIZE(tdat); mask >>= 2) {
> > > + if (mask & 0x3) {
> >
> > (for the consistency it has to be GENMASK(), but see below)
> >
> > First of all, strictly speaking we should use the full mask without
> > limiting it to the 0 element in the array (I'm talking about
> > active_scan_mask).
> >
> > That said, we may actually use bit operations here in a better way,
> > i.e.
> >
> > unsigned long mask = active_scan_mask[0] & (active_scan_mask[0] -
> > 1);
> >
> > j = 0;
> > for_each_set_bit(i, active_scan_mask, ...) {
> > val = readl(...);
> > /* Two channels per sample. Demux active. */
> > tdat[j++] = val >> (16 * (i % 2));
>
> Alternatively
>
> /* Two channels per sample. Demux active. */
> if (i % 2)
> tdat[j++] = upper_16_bits(val);
> else
> tdat[j++] = lower_16_bits(val);
>
> which may be better to read.
It's not if/else though. You would check (i % 2) for the upper 16 bits,
and (i % 1) for the lower 16 bits. Both can be valid at the same time.
Cheers,
-Paul
>
> > }
> >
> > > + 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;
> > > + }
> > > }
>
>
next prev parent reply other threads:[~2023-05-22 10:23 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 [this message]
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
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=2fc0874ce8a802aeb98e553b15e27fb4d4b75a1c.camel@crapouillou.net \
--to=paul@crapouillou.net \
--cc=andy.shevchenko@gmail.com \
--cc=contact@artur-rojek.eu \
--cc=dmitry.torokhov@gmail.com \
--cc=jic23@kernel.org \
--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 \
/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