Linux Documentation
 help / color / mirror / Atom feed
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 v2 1/2] iio: adc: ad4695: add offload-based oversampling support
Date: Sun, 12 Jan 2025 15:31:59 +0000	[thread overview]
Message-ID: <20250112153159.5169b164@jic23-huawei> (raw)
In-Reply-To: <20250109-ad4695-oversampling-v2-1-a46ac487082c@baylibre.com>

On Thu, 09 Jan 2025 13:47:23 -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>
LGTM
Assuming no requests for changes otherwise feel free to poke me when
the dependency is available upstream. I'll keep it live in patchwork
but I tend only to loop back over outstanding stuff once or twice a cycle
and maybe that will be long after needed for this one!

Jonathan

  reply	other threads:[~2025-01-12 15:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 18:47 [PATCH v2 0/2] iio: adc: ad4695: add oversampling support Trevor Gamblin
2025-01-09 18:47 ` [PATCH v2 1/2] iio: adc: ad4695: add offload-based " Trevor Gamblin
2025-01-12 15:31   ` Jonathan Cameron [this message]
2025-01-13 14:35   ` Nuno Sá
2025-01-13 16:49     ` Trevor Gamblin
2025-02-10 19:03       ` Jonathan Cameron
2025-02-10 20:41         ` Trevor Gamblin
2025-01-09 18:47 ` [PATCH v2 2/2] doc: iio: ad4695: describe " Trevor Gamblin
2025-02-10 20:51 ` [PATCH v2 0/2] iio: adc: ad4695: add " 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=20250112153159.5169b164@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