public inbox for devicetree@vger.kernel.org
 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
Subject: Re: [PATCH v4 02/10] iio: backend: add support for data alignment
Date: Fri, 02 May 2025 16:26:19 +0100	[thread overview]
Message-ID: <0ebaa8bc80dc8dcbad6b55beb7e9e59d4eac48a4.camel@gmail.com> (raw)
In-Reply-To: <20250502085905.24926-3-antoniu.miclaus@analog.com>

On Fri, 2025-05-02 at 11:58 +0300, Antoniu Miclaus wrote:
> Add backend support for staring the capture synchronization.
> When activated, it initates a proccess that aligns the sample's most
> significant bit (MSB) based solely on the captured data, without
> considering any other external signals.
> 
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---

Couple of notes from me...

> changes in v4:
>  - implement iio_backend_interface_data_align with timeout parameter.
>  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 038c9e1e2857..b7cbbc7a8fcd 100644
> --- a/drivers/iio/industrialio-backend.c
> +++ b/drivers/iio/industrialio-backend.c
> @@ -796,6 +796,20 @@ int iio_backend_filter_type_set(struct iio_backend *back,
>  }
>  EXPORT_SYMBOL_NS_GPL(iio_backend_filter_type_set, "IIO_BACKEND");
>  
> +/**
> + * iio_backend_data_align - Perform the data alignment process.
> + * @back: Backend device
> + * @timeout: Timeout value.
> + *

dData align is not a straightforward thing so a description is definitely
helpful here. Please add one
> + * RETURNS:
> + * 0 on success, negative error number on failure.
> + */
> +int iio_backend_interface_data_align(struct iio_backend *back, u32 timeout)

It would be nice to have a suffix in the time parameter. I would do timeout_us.
We should also document/define what happens if 0 is passed. Should we accept it?
Should we block indefinitely? For starters, I would likely not accept 0.
 
> +{
> +	return iio_backend_op_call(back, interface_data_align, timeout);
> +}
> +EXPORT_SYMBOL_NS_GPL(iio_backend_interface_data_align, "IIO_BACKEND");
> +
>  /**
>   * iio_backend_ddr_enable - Enable interface DDR (Double Data Rate) mode
>   * @back: Backend device
> diff --git a/include/linux/iio/backend.h b/include/linux/iio/backend.h
> index 5526800f5d4a..452cb2838dad 100644
> --- a/include/linux/iio/backend.h
> +++ b/include/linux/iio/backend.h
> @@ -109,6 +109,7 @@ enum iio_backend_filter_type {
>   * @debugfs_print_chan_status: Print channel status into a buffer.
>   * @debugfs_reg_access: Read or write register value of backend.
>   * @filter_type_set: Set filter type.
> + * @interface_data_align: Perform the data alignment process.
>   * @ddr_enable: Enable interface DDR (Double Data Rate) mode.
>   * @ddr_disable: Disable interface DDR (Double Data Rate) mode.
>   * @data_stream_enable: Enable data stream.
> @@ -161,6 +162,7 @@ struct iio_backend_ops {
>  				  unsigned int writeval, unsigned int
> *readval);
>  	int (*filter_type_set)(struct iio_backend *back,
>  			       enum iio_backend_filter_type type);
> +	int (*interface_data_align)(struct iio_backend *back, u32 timeout);
>  	int (*ddr_enable)(struct iio_backend *back);
>  	int (*ddr_disable)(struct iio_backend *back);
>  	int (*data_stream_enable)(struct iio_backend *back);
> @@ -203,6 +205,7 @@ int devm_iio_backend_request_buffer(struct device *dev,
>  				    struct iio_dev *indio_dev);
>  int iio_backend_filter_type_set(struct iio_backend *back,
>  				enum iio_backend_filter_type type);
> +int iio_backend_interface_data_align(struct iio_backend *back, u32 timeout);
>  int iio_backend_ddr_enable(struct iio_backend *back);
>  int iio_backend_ddr_disable(struct iio_backend *back);
>  int iio_backend_data_stream_enable(struct iio_backend *back);

  reply	other threads:[~2025-05-02 15:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02  8:58 [PATCH v4 00/10] Add support for AD4080 ADC Antoniu Miclaus
2025-05-02  8:58 ` [PATCH v4 01/10] iio: backend: add support for filter config Antoniu Miclaus
2025-05-02  8:58 ` [PATCH v4 02/10] iio: backend: add support for data alignment Antoniu Miclaus
2025-05-02 15:26   ` Nuno Sá [this message]
2025-05-02  8:58 ` [PATCH v4 03/10] iio: backend: add support for number of lanes Antoniu Miclaus
2025-05-02  8:58 ` [PATCH v4 04/10] dt-bindings: iio: adc: add ad408x axi variant Antoniu Miclaus
2025-05-02  8:59 ` [PATCH v4 05/10] iio: adc: adi-axi-adc: add filter type config Antoniu Miclaus
2025-05-02 15:20   ` Nuno Sá
2025-05-02  8:59 ` [PATCH v4 06/10] iio: adc: adi-axi-adc: add data align process Antoniu Miclaus
2025-05-02 15:27   ` Nuno Sá
2025-05-02  8:59 ` [PATCH v4 07/10] iio: adc: adi-axi-adc: add num lanes support Antoniu Miclaus
2025-05-02  8:59 ` [PATCH v4 08/10] dt-bindings: iio: adc: add ad4080 Antoniu Miclaus
2025-05-02  8:59 ` [PATCH v4 09/10] iio: adc: ad4080: add driver support Antoniu Miclaus
2025-05-02 15:37   ` Nuno Sá
2025-05-04 15:40   ` Jonathan Cameron
2025-05-02  8:59 ` [PATCH v4 10/10] Documetation: ABI: add sinc1 and sinc5+pf1 filter Antoniu Miclaus

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=0ebaa8bc80dc8dcbad6b55beb7e9e59d4eac48a4.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@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