devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>,
	jic23@kernel.org,  robh@kernel.org, conor+dt@kernel.org,
	linux-iio@vger.kernel.org,  devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,  linux-pwm@vger.kernel.org
Cc: David Lechner <dlechner@baylibre.com>
Subject: Re: [PATCH v10 3/8] iio: backend: add API for oversampling
Date: Fri, 17 Jan 2025 16:17:13 +0000	[thread overview]
Message-ID: <fb7fe85ad22d778bf462231e693285c7b3d33b98.camel@gmail.com> (raw)
In-Reply-To: <20250117130702.22588-4-antoniu.miclaus@analog.com>

On Fri, 2025-01-17 at 15:06 +0200, Antoniu Miclaus wrote:
> Add backend support for setting oversampling ratio.
> 
> Reviewed-by: David Lechner <dlechner@baylibre.com>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
> no changes in v10.
>  drivers/iio/industrialio-backend.c | 15 +++++++++++++++
>  include/linux/iio/backend.h        |  5 +++++
>  2 files changed, 20 insertions(+)
> 
> diff --git a/drivers/iio/industrialio-backend.c b/drivers/iio/industrialio-
> backend.c
> index 2088afa7a55c..d4ad36f54090 100644
> --- a/drivers/iio/industrialio-backend.c
> +++ b/drivers/iio/industrialio-backend.c
> @@ -681,6 +681,21 @@ int iio_backend_data_size_set(struct iio_backend *back,
> unsigned int size)
>  }
>  EXPORT_SYMBOL_NS_GPL(iio_backend_data_size_set, "IIO_BACKEND");
>  
> +/**
> + * iio_backend_oversampling_ratio_set - set the oversampling ratio
> + * @back: Backend device
> + * @ratio: The oversampling ratio - value 1 corresponds to no oversampling.
> + *
> + * Return:
> + * 0 on success, negative error number on failure.
> + */
> +int iio_backend_oversampling_ratio_set(struct iio_backend *back,
> +				       unsigned int ratio)
> +{
> +	return iio_backend_op_call(back, oversampling_ratio_set, ratio);
> +}
> +EXPORT_SYMBOL_NS_GPL(iio_backend_oversampling_ratio_set, "IIO_BACKEND");
> +

Hmm, I'm very late to the party so don't bother in sending another revision
unless you have too. But if you do, I would prefer to have this through a
write_raw() interface. Meaning we would only have write_raw() as a backend op
and  then you could add this as a convenient inline helper built on top of
write_raw(). So this would be inline with what happens with read_raw(). Anyways,
we can clean it up afterwards since we already have a .set_sample_rate() op that
could use a similar approach.

- Nuno Sá



  reply	other threads:[~2025-01-17 16:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 13:06 [PATCH v10 0/8] Add support for AD485x DAS Family Antoniu Miclaus
2025-01-17 13:06 ` [PATCH v10 1/8] iio: backend: add API for interface get Antoniu Miclaus
2025-01-17 16:08   ` Nuno Sá
2025-01-17 13:06 ` [PATCH v10 2/8] iio: backend: add support for data size set Antoniu Miclaus
2025-01-17 16:09   ` Nuno Sá
2025-01-17 13:06 ` [PATCH v10 3/8] iio: backend: add API for oversampling Antoniu Miclaus
2025-01-17 16:17   ` Nuno Sá [this message]
2025-01-18 16:42     ` Jonathan Cameron
2025-01-17 13:06 ` [PATCH v10 4/8] iio: adc: adi-axi-adc: add interface type Antoniu Miclaus
2025-01-17 16:18   ` Nuno Sá
2025-01-17 13:06 ` [PATCH v10 5/8] iio: adc: adi-axi-adc: set data format Antoniu Miclaus
2025-01-17 16:20   ` Nuno Sá
2025-01-17 17:50     ` David Lechner
2025-01-18 14:47       ` Nuno Sá
2025-01-17 13:07 ` [PATCH v10 6/8] iio: adc: adi-axi-adc: add oversampling Antoniu Miclaus
2025-01-17 16:22   ` Nuno Sá
2025-01-17 13:07 ` [PATCH v10 7/8] dt-bindings: iio: adc: add ad4851 Antoniu Miclaus
2025-01-17 13:07 ` [PATCH v10 8/8] iio: adc: ad4851: add ad485x driver Antoniu Miclaus
2025-01-17 21:45   ` David Lechner
2025-01-18 16:57     ` Jonathan Cameron
2025-01-18 17:09       ` David Lechner
2025-01-18 17:41         ` Jonathan Cameron
2025-01-20 12:37     ` Miclaus, Antoniu
2025-01-20 17:37       ` David Lechner
2025-01-21 10:24         ` Nuno Sá
2025-01-18 15:10   ` Nuno Sá
2025-01-18 17:37     ` David Lechner
2025-01-20  9:44       ` Nuno Sá

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=fb7fe85ad22d778bf462231e693285c7b3d33b98.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).