From: Jonathan Cameron <jic23@kernel.org>
To: Trevor Gamblin <tgamblin@baylibre.com>
Cc: "Michael Hennerich" <michael.hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] iio: adc: ad4695: add offload-based oversampling support
Date: Thu, 19 Dec 2024 16:13:01 +0000 [thread overview]
Message-ID: <20241219161301.3f708302@jic23-huawei> (raw)
In-Reply-To: <20241217-ad4695-oversampling-v1-1-0b045d835dac@baylibre.com>
On Tue, 17 Dec 2024 16:47:28 -0500
Trevor Gamblin <tgamblin@baylibre.com> wrote:
> Add support for the ad4695's oversampling feature when SPI offload is
> available. This allows the ad4695 to set oversampling ratios on a
> per-channel basis, raising the effective-number-of-bits from 16
> (OSR == 1) to 17 (4), 18 (16), or 19 (64) for a given sample (i.e. one
> full cycle through the auto-sequencer). The logic for reading and
> writing sampling frequency for a given channel is also adjusted based on
> the current oversampling ratio.
>
> The non-offload case isn't supported as there isn't a good way to
> trigger the CNV pin in this mode. Support could be added in the future
> if a use-case arises.
>
> Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Hi Trevor,
The clamping fun of get_calibbias seems overkill. If this isn't going to ever
overflow an s64 maybe just use the high precision to do it the easy way.
I'm not sure you can't just fit it in an s32 for that matter. I've just
not done the maths to check.
Jonathan
> +static unsigned int ad4695_get_calibbias(int val, int val2, int osr)
> +{
> + unsigned int reg_val;
> +
> + switch (osr) {
> + case 4:
> + if (val2 >= 0 && val > S16_MAX / 2)
> + reg_val = S16_MAX;
> + else if ((val2 < 0 ? -val : val) < S16_MIN / 2)
It has been a while, but IIRC if val2 < 0 then val == 0 as otherwise
we carry the sign in the val part. Sometimes we generalize that to
make life easier for driver writers but I think you can use that here
to simplify things.
(for background look at __iio_str_to_fixpoint() - it's a bit of a hack
to deal with integers have no negative 0)
if (val > S16_MAX / 2)
...
else if (val < S16_MIN / 2)
...
else if (val2 < 0) etc
You may feel it is better to keep the code considering the val2 < 0 when
val != 0 case and I don't mind that as it's not wrong, just overly complex!
If you can easily clamp the overall range you can just do some maths
with enough precision to get one number (probably a s64) and clamp that.
Easy to sanity check for overflow based on val to ensure no overflows.
> + reg_val = S16_MIN;
> + else if (val2 < 0)
> + reg_val = clamp_t(int,
> + -(val * 2 + -val2 * 2 / MICRO),
> + S16_MIN, S16_MAX);
> + else if (val < 0)
> + reg_val = clamp_t(int,
> + val * 2 - val2 * 2 / MICRO,
> + S16_MIN, S16_MAX);
> + else
> + reg_val = clamp_t(int,
> + val * 2 + val2 * 2 / MICRO,
> + S16_MIN, S16_MAX);
> + return reg_val;
> + case 16:
> + if (val2 >= 0 && val > S16_MAX)
> + reg_val = S16_MAX;
> + else if ((val2 < 0 ? -val : val) < S16_MIN)
> + reg_val = S16_MIN;
> + else if (val2 < 0)
> + reg_val = clamp_t(int,
> + -(val + -val2 / MICRO),
> + S16_MIN, S16_MAX);
> + else if (val < 0)
> + reg_val = clamp_t(int,
> + val - val2 / MICRO,
> + S16_MIN, S16_MAX);
> + else
> + reg_val = clamp_t(int,
> + val + val2 / MICRO,
> + S16_MIN, S16_MAX);
> + return reg_val;
> + case 64:
> + if (val2 >= 0 && val > S16_MAX * 2)
> + reg_val = S16_MAX;
> + else if ((val2 < 0 ? -val : val) < S16_MIN * 2)
> + reg_val = S16_MIN;
> + else if (val2 < 0)
> + reg_val = clamp_t(int,
> + -(val / 2 + -val2 / 2 / MICRO),
> + S16_MIN, S16_MAX);
> + else if (val < 0)
> + reg_val = clamp_t(int,
> + val / 2 - val2 / 2 / MICRO,
> + S16_MIN, S16_MAX);
> + else
> + reg_val = clamp_t(int,
> + val / 2 + val2 / 2 / MICRO,
> + S16_MIN, S16_MAX);
> + return reg_val;
> + default:
> + if (val2 >= 0 && val > S16_MAX / 4)
> + reg_val = S16_MAX;
> + else if ((val2 < 0 ? -val : val) < S16_MIN / 4)
> + reg_val = S16_MIN;
> + else if (val2 < 0)
> + reg_val = clamp_t(int,
> + -(val * 4 + -val2 * 4 / MICRO),
> + S16_MIN, S16_MAX);
> + else if (val < 0)
> + reg_val = clamp_t(int,
> + val * 4 - val2 * 4 / MICRO,
> + S16_MIN, S16_MAX);
> + else
> + reg_val = clamp_t(int,
> + val * 4 + val2 * 4 / MICRO,
> + S16_MIN, S16_MAX);
> + return reg_val;
> + }
> +}
> +
next prev parent reply other threads:[~2024-12-19 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 21:47 [PATCH 0/2] iio: adc: ad4695: add oversampling support Trevor Gamblin
2024-12-17 21:47 ` [PATCH 1/2] iio: adc: ad4695: add offload-based " Trevor Gamblin
2024-12-19 16:13 ` Jonathan Cameron [this message]
2024-12-23 16:33 ` Trevor Gamblin
2025-01-02 18:19 ` Trevor Gamblin
2025-01-04 12:30 ` Jonathan Cameron
2025-01-07 20:21 ` Trevor Gamblin
2025-01-07 21:02 ` David Lechner
2025-01-08 19:54 ` Trevor Gamblin
2025-01-08 20:39 ` David Lechner
2024-12-17 21:47 ` [PATCH 2/2] doc: iio: ad4695: describe " Trevor Gamblin
2024-12-19 15:53 ` Jonathan Cameron
2024-12-19 15:46 ` [PATCH 0/2] iio: adc: ad4695: add " Jonathan Cameron
2025-01-09 18:09 ` Trevor Gamblin
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=20241219161301.3f708302@jic23-huawei \
--to=jic23@kernel.org \
--cc=corbet@lwn.net \
--cc=dlechner@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
--cc=tgamblin@baylibre.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