From: Jonathan Cameron <jic23@kernel.org>
To: Sam Winchenbach <sam.winchenbach@framepointer.org>
Cc: linux-kernel@vger.kernel.org, lars@metafoo.de,
Michael.Hennerich@analog.com, antoniu.miclaus@analog.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
bpellegrino@arka.org, Sam Winchenbach <swinchenbach@arka.org>
Subject: Re: [PATCH v8 0/6] Update auto corner freq calculation
Date: Sun, 30 Mar 2025 16:23:00 +0100 [thread overview]
Message-ID: <20250330162300.4c318897@jic23-huawei> (raw)
In-Reply-To: <20250328174831.227202-1-sam.winchenbach@framepointer.org>
On Fri, 28 Mar 2025 13:48:25 -0400
Sam Winchenbach <sam.winchenbach@framepointer.org> wrote:
> From: Sam Winchenbach <swinchenbach@arka.org>
>
> v1: Initial submission
> v2: Cleaned up wording of commit message
> v3: Add DTS properties to control corner frequency margins
> v4: Fixed wrapping
> Added maintainers to CC
> v5: Remove magic numbers
> Break out patches into features
> Small coding style fixes
> v6: Converted dts property from hz to mhz
> Removed blank lines in dts binding documentation
> v7: Updated author/sign-off address
> fixed patch path description
> v8: Added missing Reviewed-By tag in v7
>
> Brian Pellegrino (1):
> iio: filter: admv8818: Support frequencies >= 2^32
Applied to the togreg branch of iio.git and initially pushed out as testing.
I thought about splitting off the fixes and sending them a faster path, but that
last fix is rather large for that so I haven't.
Shout if you think I should try to get the fixes upstream quickly and
I can move them to my fixes branch.
Jonathan
>
> Sam Winchenbach (5):
> dt-bindings: iio: filter: Add lpf/hpf freq margins
> iio: filter: admv8818: fix band 4, state 15
> iio: filter: admv8818: fix integer overflow
> iio: filter: admv8818: fix range calculation
> iio: core: Add support for writing 64 bit attrs
>
> .../bindings/iio/filter/adi,admv8818.yaml | 20 ++
> drivers/iio/filter/admv8818.c | 224 +++++++++++++-----
> drivers/iio/industrialio-core.c | 12 +
> 3 files changed, 202 insertions(+), 54 deletions(-)
>
next prev parent reply other threads:[~2025-03-30 15:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 17:48 [PATCH v8 0/6] Update auto corner freq calculation Sam Winchenbach
2025-03-28 17:48 ` [PATCH v8 1/6] dt-bindings: iio: filter: Add lpf/hpf freq margins Sam Winchenbach
2025-03-28 17:48 ` [PATCH v8 2/6] iio: filter: admv8818: fix band 4, state 15 Sam Winchenbach
2025-03-28 17:48 ` [PATCH v8 3/6] iio: filter: admv8818: fix integer overflow Sam Winchenbach
2025-03-28 17:48 ` [PATCH v8 4/6] iio: filter: admv8818: fix range calculation Sam Winchenbach
2025-03-28 17:48 ` [PATCH v8 5/6] iio: core: Add support for writing 64 bit attrs Sam Winchenbach
2025-03-30 15:17 ` Jonathan Cameron
2025-03-30 15:20 ` Jonathan Cameron
2025-03-28 17:48 ` [PATCH v8 6/6] iio: filter: admv8818: Support frequencies >= 2^32 Sam Winchenbach
2025-03-30 15:23 ` Jonathan Cameron [this message]
2025-03-31 19:30 ` [PATCH v8 0/6] Update auto corner freq calculation Sam Winchenbach
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=20250330162300.4c318897@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=antoniu.miclaus@analog.com \
--cc=bpellegrino@arka.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sam.winchenbach@framepointer.org \
--cc=swinchenbach@arka.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