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 2/8] iio: backend: add support for data size set
Date: Fri, 17 Jan 2025 16:09:52 +0000 [thread overview]
Message-ID: <94461f6e33b25427495b59b133377a0269d73b29.camel@gmail.com> (raw)
In-Reply-To: <20250117130702.22588-3-antoniu.miclaus@analog.com>
On Fri, 2025-01-17 at 15:06 +0200, Antoniu Miclaus wrote:
> Add backend support for setting the data size used.
> This setting can be adjusted within the IP cores interfacing devices.
>
> Reviewed-by: David Lechner <dlechner@baylibre.com>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
Reviewed-by: Nuno Sa <nuno.sa@analog.com>
> no changes in v10.
> drivers/iio/industrialio-backend.c | 21 +++++++++++++++++++++
> include/linux/iio/backend.h | 3 +++
> 2 files changed, 24 insertions(+)
>
> diff --git a/drivers/iio/industrialio-backend.c b/drivers/iio/industrialio-
> backend.c
> index 8bf3d570da1b..2088afa7a55c 100644
> --- a/drivers/iio/industrialio-backend.c
> +++ b/drivers/iio/industrialio-backend.c
> @@ -660,6 +660,27 @@ int iio_backend_interface_type_get(struct iio_backend
> *back,
> }
> EXPORT_SYMBOL_NS_GPL(iio_backend_interface_type_get, "IIO_BACKEND");
>
> +/**
> + * iio_backend_data_size_set - set the data width/size in the data bus.
> + * @back: Backend device
> + * @size: Size in bits
> + *
> + * Some frontend devices can dynamically control the word/data size on the
> + * interface/data bus. Hence, the backend device needs to be aware of it so
> + * data can be correctly transferred.
> + *
> + * Return:
> + * 0 on success, negative error number on failure.
> + */
> +int iio_backend_data_size_set(struct iio_backend *back, unsigned int size)
> +{
> + if (!size)
> + return -EINVAL;
> +
> + return iio_backend_op_call(back, data_size_set, size);
> +}
> +EXPORT_SYMBOL_NS_GPL(iio_backend_data_size_set, "IIO_BACKEND");
> +
> /**
> * iio_backend_extend_chan_spec - Extend an IIO channel
> * @back: Backend device
> diff --git a/include/linux/iio/backend.h b/include/linux/iio/backend.h
> index a0ea6c29d7ba..9ae861a21472 100644
> --- a/include/linux/iio/backend.h
> +++ b/include/linux/iio/backend.h
> @@ -95,6 +95,7 @@ enum iio_backend_interface_type {
> * @ext_info_set: Extended info setter.
> * @ext_info_get: Extended info getter.
> * @interface_type_get: Interface type.
> + * @data_size_set: Data size.
> * @read_raw: Read a channel attribute from a backend device
> * @debugfs_print_chan_status: Print channel status into a buffer.
> * @debugfs_reg_access: Read or write register value of backend.
> @@ -137,6 +138,7 @@ struct iio_backend_ops {
> const struct iio_chan_spec *chan, char *buf);
> int (*interface_type_get)(struct iio_backend *back,
> enum iio_backend_interface_type *type);
> + int (*data_size_set)(struct iio_backend *back, unsigned int size);
> int (*read_raw)(struct iio_backend *back,
> struct iio_chan_spec const *chan, int *val, int
> *val2,
> long mask);
> @@ -197,6 +199,7 @@ ssize_t iio_backend_ext_info_get(struct iio_dev
> *indio_dev, uintptr_t private,
> const struct iio_chan_spec *chan, char
> *buf);
> int iio_backend_interface_type_get(struct iio_backend *back,
> enum iio_backend_interface_type *type);
> +int iio_backend_data_size_set(struct iio_backend *back, unsigned int size);
> int iio_backend_read_raw(struct iio_backend *back,
> struct iio_chan_spec const *chan, int *val, int
> *val2,
> long mask);
next prev parent reply other threads:[~2025-01-17 16:09 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á [this message]
2025-01-17 13:06 ` [PATCH v10 3/8] iio: backend: add API for oversampling Antoniu Miclaus
2025-01-17 16:17 ` Nuno Sá
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=94461f6e33b25427495b59b133377a0269d73b29.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).