From: Markus Elfring <Markus.Elfring@web.de>
To: Jonathan Cameron <jic23@kernel.org>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Marcelo Schmitt <marcelo.schmitt@analog.com>,
linux-iio@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"Andy Shevchenko" <andy@kernel.org>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"David Lechner" <dlechner@baylibre.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Marcelo Schmitt" <marcelo.schmitt1@gmail.com>,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>
Subject: Re: [PATCH v2] iio: adc: ad4170-4: Correctly update filter_fs after filter type change
Date: Thu, 24 Jul 2025 15:29:15 +0200 [thread overview]
Message-ID: <fb69f55e-de06-4513-8126-e73cc51c086f@web.de> (raw)
In-Reply-To: <20250724135125.5dabddb1@jic23-huawei>
>>> Previously, the driver was directly using the filter type value to update
>>> the filter frequency (filter_fs) configuration. That caused the driver to
>>> switch to the lowest filter_fs configuration (highest sampling frequency)
>>> on every update to the filter type. Correct the filter_fs collateral update
>>> by clamping it to the range of supported values instead of mistakenly
>>> using the filter type to update the filter_fs.
…> I picked up v1 and made that a closes tag. Links to email threads are fine
> (there was a question in v1 on this).
>
> Applied to the fixes-togreg-for-6.17 branch.
Would you like to avoid typos anyhow for the final commit message?
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?h=fixes-togreg-for-6.17&id=e4d9886ad25adae72f38f2b12f41649b101581ae
Regards,
Markus
prev parent reply other threads:[~2025-07-24 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 15:37 [PATCH v2 1/1] " Marcelo Schmitt
2025-07-21 9:21 ` Nuno Sá
2025-07-21 11:43 ` Andy Shevchenko
2025-07-24 12:51 ` Jonathan Cameron
2025-07-24 13:29 ` Markus Elfring [this message]
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=fb69f55e-de06-4513-8126-e73cc51c086f@web.de \
--to=markus.elfring@web.de \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@analog.com \
--cc=michael.hennerich@analog.com \
--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
all inboxes | Powered by JetHome®