From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] iio: adc: ad7124: add filter support
Date: Sun, 7 Sep 2025 11:22:14 +0100 [thread overview]
Message-ID: <20250907112214.36b8564a@jic23-huawei> (raw)
In-Reply-To: <20250905-iio-adc-ad7124-add-filter-support-v1-5-aee3834be6a9@baylibre.com>
On Fri, 05 Sep 2025 13:12:00 -0500
David Lechner <dlechner@baylibre.com> wrote:
> Add support to the ad7124 driver for selecting the filter type.
>
> The filter type has an influence on the effective sampling frequency of
> each channel. For sinc3+pf{1,2,3,4}, the sampling frequency is fixed.
> For sinc{3,4} (without post filter), there is a factor of 3 or 4
> depending on the filter type. For the extra +sinc1, there is an extra
> averaging factor that depends on the power mode.
>
> In order to select the closest sampling frequency for each filter type,
> we keep a copy of the requested sampling frequency. This way, if the
> user sets the sampling frequency first and then selects the filter type,
> the sampling frequency will still be as close as possible to the
> requested value.
>
> Since we always either have the SINGLE_CYCLE bit set or have more than
> one channel enabled, the sampling frequency is always using the
> "zero-latency" calculation from the data sheet. This is only documented
> for the basic sinc{3,4} filters, so the other filter types had to be
> inferred and confirmed through testing.
>
> Since the flat filter type list consists of multiple register fields,
> the struct ad7124_channel_config::filter_type field is changed to the
> enum ad7124_filter_type type to avoid nested switch statements in a
> lot of places.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
One really trivial comment inline. Not worth a v2 for just that.
However, this is complex enough code I'd like to keep this on list anyway
for a little longer to see if anyone else has review comments.
Jonathan
> -static void ad7124_set_channel_odr(struct ad7124_state *st, unsigned int channel,
> - unsigned int odr, unsigned int odr_micro)
> +static void ad7124_set_channel_odr(struct ad7124_state *st, unsigned int channel)
> {
> + struct ad7124_channel_config *cfg = &st->channels[channel].cfg;
> unsigned int fclk, factor, odr_sel_bits;
>
> fclk = ad7124_get_fclk_hz(st);
> + factor = ad7124_get_fs_factor(st, channel);
>
> /*
> * FS[10:0] = fCLK / (fADC x 32 * N) where:
> @@ -310,9 +362,9 @@ static void ad7124_set_channel_odr(struct ad7124_state *st, unsigned int channel
> * FS[10:0] are the bits in the filter register
> * FS[10:0] can have a value from 1 to 2047
> */
> - factor = 32 * 4; /* N = 4 for default sinc4 filter. */
> - odr_sel_bits = DIV_ROUND_CLOSEST(fclk, odr * factor +
> - odr_micro * factor / MICRO);
> + odr_sel_bits = DIV_ROUND_CLOSEST(fclk, cfg->requested_odr * factor +
> + cfg->requested_odr_micro *
> + factor / MICRO);
This second parameter is getting complex enough, perhaps worth introducing
a local variable?
divisor = cfg->requested_odr * factor +
cfg->requested_odr_micro * factor / MICRO;
perhaps, or local variables for odr and odr_micro to keep this unchanged in this path.
> odr_sel_bits = clamp(odr_sel_bits, 1, 2047);
>
> if (odr_sel_bits != st->channels[channel].cfg.odr_sel_bits)
next prev parent reply other threads:[~2025-09-07 10:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 18:11 [PATCH 0/6] iio: adc: ad7124: add filter support David Lechner
2025-09-05 18:11 ` [PATCH 1/6] iio: adc: ad7124: use clamp() David Lechner
2025-09-07 10:02 ` Jonathan Cameron
2025-09-05 18:11 ` [PATCH 2/6] iio: adc: ad7124: use read_avail() for scale_available David Lechner
2025-09-07 10:04 ` Jonathan Cameron
2025-09-05 18:11 ` [PATCH 3/6] iio: adc: ad7124: use guard(mutex) to simplify return paths David Lechner
2025-09-07 10:06 ` Jonathan Cameron
2025-09-10 16:27 ` Jonathan Cameron
2025-09-05 18:11 ` [PATCH 4/6] iio: adc: ad7124: support fractional sampling_frequency David Lechner
2025-09-05 18:12 ` [PATCH 5/6] iio: adc: ad7124: add filter support David Lechner
2025-09-07 10:22 ` Jonathan Cameron [this message]
2025-09-10 16:29 ` Jonathan Cameron
2025-09-05 18:12 ` [PATCH 6/6] iio: ABI: document "sinc4+rej60" filter_type David Lechner
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=20250907112214.36b8564a@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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