From: "Esteban Blanc" <eblanc@baylibre.com>
To: "Esteban Blanc" <eblanc@baylibre.com>,
"Jonathan Cameron" <jic23@kernel.org>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Nuno Sa" <nuno.sa@analog.com>,
"Jonathan Corbet" <corbet@lwn.net>, <linux-iio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
<linux-doc@vger.kernel.org>
Subject: Re: [PATCH 4/6] iio: adc: ad4030: add support for ad4630-24 and ad4630-16
Date: Mon, 16 Sep 2024 13:03:08 +0000 [thread overview]
Message-ID: <D47Q9E5EW08V.2JP0X6EFQMFBT@baylibre.com> (raw)
In-Reply-To: <D452E2M75XCM.13OQGAPJ7JJ4A@baylibre.com>
On Fri Sep 13, 2024 at 9:55 AM UTC, Esteban Blanc wrote:
> On Mon Aug 26, 2024 at 9:27 AM UTC, Jonathan Cameron wrote:
> > On Thu, 22 Aug 2024 14:45:20 +0200
> > Esteban Blanc <eblanc@baylibre.com> wrote:
> > > @@ -460,12 +517,21 @@ static int ad4030_conversion(struct ad4030_state *st,
> > > if (ret)
> > > return ret;
> > >
> > > - if (st->mode != AD4030_OUT_DATA_MD_24_DIFF_8_COM)
> > > + if (st->chip->num_channels == 2)
> > > + ad4030_extract_interleaved(st->rx_data.raw,
> > > + &st->rx_data.diff[0],
> > > + &st->rx_data.diff[1]);
> > > +
> > > + if (st->mode != AD4030_OUT_DATA_MD_16_DIFF_8_COM &&
> > > + st->mode != AD4030_OUT_DATA_MD_24_DIFF_8_COM)
> > > return 0;
> > >
> > > byte_index = BITS_TO_BYTES(chan->scan_type.realbits);
> > > - for (i = 0; i < st->chip->num_channels; i++)
> > > - st->rx_data.buffered[i].common = ((u8 *)&st->rx_data.buffered[i].val)[byte_index];
> > > + /* Doing it backward to avoid overlap when reordering */
> > > + for (i = st->chip->num_channels - 1; i > 0; i--) {
> > > + st->rx_data.buffered_common[i].diff = st->rx_data.diff[i];
> > > + st->rx_data.buffered_common[i].common = ((u8 *)&st->rx_data.diff[i])[byte_index];
> > > + }
> >
> > I wonder if doing it in place is actually worthwhile. Maybe unpack into a second
> > array? That is still fairly small and may make code easier to read.
>
> Okay sure
Actually I can't consolidate the differential only mode and the common
byte mode without having to create a bunch of if/else or having a
memcpy. The best I can do is this, but I don't like it:
```
static int ad4030_conversion(struct ad4030_state *st,
const struct iio_chan_spec *chan)
{
...
u32 tmp[AD4030_MAX_HARDWARE_CHANNEL_NB];
u32 *diff;
...
if (st->mode != AD4030_OUT_DATA_MD_16_DIFF_8_COM &&
st->mode != AD4030_OUT_DATA_MD_24_DIFF_8_COM) {
if (st->chip->num_voltage_inputs == 2)
ad4030_extract_interleaved(st->rx_data.raw,
&st->rx_data.diff[0],
&st->rx_data.diff[1]);
return 0;
}
if (st->chip->num_voltage_inputs == 2) {
ad4030_extract_interleaved(st->rx_data.raw,
&tmp[0],
&tmp[1]);
diff = tmp;
} else {
diff = st->rx_data.diff;
}
common_byte_mask = BITS_TO_BYTES(chan->scan_type.realbits);
for (i = 0; i < st->chip->num_voltage_inputs; i++) {
st->rx_data.buffered[i].val = diff[i];
st->rx_data.buffered[i].common =
((u8 *)(diff + i))[common_byte_mask];
}
return 0;
```
The root cause is that when we are in a differential only mode we are
leaving before the for loop and we want the data to be in the rx_data.
It fells clunky and brain consuming IMAO, I prefer a reversed loop with
a good comment (the one we have now is not explicit enough, I will
update it).
next prev parent reply other threads:[~2024-09-16 13:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 12:45 [PATCH 0/6] iio: adc: ad4030: new driver for AD4030 and similar ADCs Esteban Blanc
2024-08-22 12:45 ` [PATCH 1/6] dt-bindings: iio: adc: add ADI ad4030, ad4630 and ad4632 Esteban Blanc
2024-08-22 15:56 ` Conor Dooley
2024-08-26 8:36 ` Krzysztof Kozlowski
2024-08-22 12:45 ` [PATCH 2/6] iio: adc: ad4030: add driver for ad4030-24 Esteban Blanc
2024-08-22 19:39 ` David Lechner
2024-08-24 10:40 ` Jonathan Cameron
2024-09-13 10:22 ` Nuno Sá
2024-09-13 12:04 ` Esteban Blanc
2024-08-24 11:21 ` Jonathan Cameron
2024-08-27 16:45 ` Esteban Blanc
2024-08-28 13:34 ` Jonathan Cameron
2024-08-22 12:45 ` [PATCH 3/6] iio: adc: ad4030: add averaging support Esteban Blanc
2024-08-22 19:41 ` David Lechner
2024-08-22 12:45 ` [PATCH 4/6] iio: adc: ad4030: add support for ad4630-24 and ad4630-16 Esteban Blanc
2024-08-22 19:43 ` David Lechner
2024-08-26 9:27 ` Jonathan Cameron
2024-09-13 9:55 ` Esteban Blanc
2024-09-13 10:18 ` Nuno Sá
2024-09-13 12:55 ` Esteban Blanc
2024-09-13 13:46 ` Nuno Sá
2024-09-14 11:25 ` Jonathan Cameron
2024-09-16 6:12 ` Nuno Sá
2024-09-17 11:21 ` Jonathan Cameron
2024-09-17 11:19 ` Jonathan Cameron
2024-09-16 9:19 ` Esteban Blanc
2024-09-17 11:21 ` Jonathan Cameron
2024-09-16 13:03 ` Esteban Blanc [this message]
2024-08-22 12:45 ` [PATCH 5/6] iio: adc: ad4030: add support for ad4632-16 and ad4632-24 Esteban Blanc
2024-08-26 9:29 ` Jonathan Cameron
2024-08-22 12:45 ` [PATCH 6/6] docs: iio: ad4030: add documentation Esteban Blanc
2024-08-22 19:43 ` David Lechner
2024-08-22 15:54 ` [PATCH 0/6] iio: adc: ad4030: new driver for AD4030 and similar ADCs Conor Dooley
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=D47Q9E5EW08V.2JP0X6EFQMFBT@baylibre.com \
--to=eblanc@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@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