From: "Nuno Sá" <noname.nuno@gmail.com>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>,
jic23@kernel.org, robh@kernel.org, conor+dt@kernel.org,
dlechner@baylibre.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH v6 3/8] iio: backend: add API for oversampling
Date: Mon, 11 Nov 2024 16:41:02 +0100 [thread overview]
Message-ID: <e683ce92267ec4cafa825cdf1767939d922b04ea.camel@gmail.com> (raw)
In-Reply-To: <20241111121203.3699-4-antoniu.miclaus@analog.com>
On Mon, 2024-11-11 at 14:11 +0200, Antoniu Miclaus wrote:
> Add backend support for enabling/disabling oversampling.
>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
> changes in v6:
> - add iio backend commit for oversampling enable/disable
> drivers/iio/industrialio-backend.c | 14 ++++++++++++++
> include/linux/iio/backend.h | 3 +++
> 2 files changed, 17 insertions(+)
>
> diff --git a/drivers/iio/industrialio-backend.c b/drivers/iio/industrialio-
> backend.c
> index ea184fc2c838..6ba445ba3dd0 100644
> --- a/drivers/iio/industrialio-backend.c
> +++ b/drivers/iio/industrialio-backend.c
> @@ -681,6 +681,20 @@ 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_en - set the data width/size in the data bus.
Seems unrelated?
> + * @back: Backend device
> + * @en: oversampling enabled/disabled.
> + *
> + * Return:
> + * 0 on success, negative error number on failure.
> + */
> +int iio_backend_oversampling_en(struct iio_backend *back, bool en)
> +{
> + return iio_backend_op_call(back, oversampling_en, en);
> +}
> +EXPORT_SYMBOL_NS_GPL(iio_backend_oversampling_en, IIO_BACKEND);
> +
There was some discussion around having APIs with a boolean parameter (actually
even improving - in terms of callbacks - further with some generic
getter/setter's) or having two callbacks:
iio_backend_oversampling_enable()
iio_backend_oversampling_disable()
I'm guessing you don't really want to do any major conversion/refactoring at
this point in your series so I have a slight preference for just keeping the
current style of dedicated enable and disable APIs (irrespective of being the
better approach or not). Please consider it, if you have to re-spin the series.
- Nuno Sá
next prev parent reply other threads:[~2024-11-11 15:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 12:11 [PATCH v6 0/8] *** Add support for AD485x DAS Family *** Antoniu Miclaus
2024-11-11 12:11 ` [PATCH v6 1/8] iio: backend: add API for interface get Antoniu Miclaus
2024-11-11 12:11 ` [PATCH v6 2/8] iio: backend: add support for data size set Antoniu Miclaus
2024-11-11 12:11 ` [PATCH v6 3/8] iio: backend: add API for oversampling Antoniu Miclaus
2024-11-11 15:41 ` Nuno Sá [this message]
2024-11-23 16:02 ` Jonathan Cameron
2024-11-23 16:05 ` Jonathan Cameron
2024-11-11 12:11 ` [PATCH v6 4/8] iio: adc: adi-axi-adc: add interface type Antoniu Miclaus
2024-11-11 12:12 ` [PATCH v6 5/8] iio: adc: adi-axi-adc: set data format Antoniu Miclaus
2024-11-12 20:11 ` David Lechner
2024-11-11 12:12 ` [PATCH v6 6/8] iio: adc: adi-axi-adc: add oversampling Antoniu Miclaus
2024-11-12 20:12 ` David Lechner
2024-11-23 16:04 ` Jonathan Cameron
2024-11-11 12:12 ` [PATCH v6 7/8] dt-bindings: iio: adc: add ad4851 Antoniu Miclaus
2024-11-11 12:12 ` [PATCH v6 8/8] iio: adc: ad4851: add ad485x driver Antoniu Miclaus
2024-11-12 20:02 ` David Lechner
2024-11-14 10:39 ` Miclaus, Antoniu
2024-11-14 14:47 ` David Lechner
2024-11-15 10:59 ` Miclaus, Antoniu
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=e683ce92267ec4cafa825cdf1767939d922b04ea.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