From: David Lechner <dlechner@baylibre.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Alisa-Dariana Roman" <alisadariana@gmail.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Alisa-Dariana Roman" <alisa.roman@analog.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>
Subject: Re: [PATCH v1 1/1] iio: adc: ad7192: Refactor filter config
Date: Thu, 1 May 2025 09:49:20 -0500 [thread overview]
Message-ID: <df11dff4-7641-46f8-a604-8727918629c3@baylibre.com> (raw)
In-Reply-To: <20250426133241.7d14c776@jic23-huawei>
On 4/26/25 7:32 AM, Jonathan Cameron wrote:
> On Fri, 25 Apr 2025 10:43:29 -0500
> David Lechner <dlechner@baylibre.com> wrote:
>
>> On 4/25/25 8:20 AM, Alisa-Dariana Roman wrote:
...
>>> +static const char *const ad7192_filter_modes_str[] = {
>>> + [AD7192_FILTER_SINC4] = "sinc4",
>>> + [AD7192_FILTER_SINC3] = "sinc3",
>>> + [AD7192_FILTER_SINC4_CHOP] = "sinc4+chop",
>
> Is chop really a filter? I had to look it up and to me at least it
> seems like it isn't even though one thing it does is remove
> some types of noise. It also removes linear offsets (some types
> of filter kind of do that, but the affect of chop smells more like
> a calibration tweak than a filter)
>
> Maybe we need a separate control for chop, rather than trying to
> force it through our already complex filter type attributes?
>
I was looking at the datasheet for another ADC that popped up on the mailing
list today. https://www.ti.com/lit/ds/symlink/ads1262.pdf
It also has a chop mode and filters very similar to this one. So perhaps another
reason to make chop a separate bool attribute that could considered a "standard"
attribute.
next prev parent reply other threads:[~2025-05-01 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 13:20 [PATCH v1 0/1] iio: adc: ad7192: Refactor filter config Alisa-Dariana Roman
2025-04-25 13:20 ` [PATCH v1 1/1] " Alisa-Dariana Roman
2025-04-25 15:43 ` David Lechner
2025-04-26 12:32 ` Jonathan Cameron
2025-05-01 14:49 ` David Lechner [this message]
2025-04-25 15:43 ` [PATCH v1 0/1] " 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=df11dff4-7641-46f8-a604-8727918629c3@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Hennerich@analog.com \
--cc=alisa.roman@analog.com \
--cc=alisadariana@gmail.com \
--cc=andy@kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--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