From: Jonathan Cameron <jic23@kernel.org>
To: Robert Budai <robert.budai@analog.com>
Cc: Nuno Sa <nuno.sa@analog.com>,
Ramona Gradinariu <ramona.gradinariu@analog.com>,
Antoniu Miclaus <antoniu.miclaus@analog.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
"Rob Herring" <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>, <linux-iio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-doc@vger.kernel.org>
Subject: Re: [PATCH 2/7] iio: imu: adis: Add custom ops struct
Date: Sat, 30 Nov 2024 17:13:43 +0000 [thread overview]
Message-ID: <20241130171343.007eaffd@jic23-huawei> (raw)
In-Reply-To: <20241125133520.24328-3-robert.budai@analog.com>
On Mon, 25 Nov 2024 15:35:09 +0200
Robert Budai <robert.budai@analog.com> wrote:
> This patch introduces a custom ops struct letting users define
> custom read and write functions. Some adis devices might define
> a completely different spi protocol from the one used in the
> default implementation.
>
> Co-developed-by: Ramona Gradinariu <ramona.gradinariu@analog.com>
> Signed-off-by: Ramona Gradinariu <ramona.gradinariu@analog.com>
> Co-developed-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> Signed-off-by: Robert Budai <robert.budai@analog.com>
I assume that by the end of the series, adis_default_ops will be in
use, but until then I think this change breaks support for all devices
currently supported by not providing a working read / write.
Thanks,
Jonathan
> @@ -488,6 +488,11 @@ int adis_single_conversion(struct iio_dev *indio_dev,
> }
> EXPORT_SYMBOL_NS_GPL(adis_single_conversion, IIO_ADISLIB);
>
> +static const struct adis_ops adis_default_ops = {
Not yet used. So I'm guessing this patch breaks all existing drivers.
> + .read = __adis_read_reg,
> + .write = __adis_write_reg,
> +};
next prev parent reply other threads:[~2024-11-30 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 13:35 [PATCH 0/7] adis16550-v2 Robert Budai
2024-11-25 13:35 ` [PATCH 1/7] iio: imu: adis: Remove documented not used elements Robert Budai
2024-11-30 17:08 ` Jonathan Cameron
2024-11-25 13:35 ` [PATCH 2/7] iio: imu: adis: Add custom ops struct Robert Budai
2024-11-30 17:13 ` Jonathan Cameron [this message]
2024-11-25 13:35 ` [PATCH 3/7] iio: imu: adis: Add reset to custom ops Robert Budai
2024-11-30 17:12 ` Jonathan Cameron
2024-11-25 13:35 ` [PATCH 4/7] iio: imu: adis: Add DIAG_STAT register size Robert Budai
2024-11-25 13:35 ` [PATCH 5/7] dt-bindings: iio: Add adis16550 bindings Robert Budai
2024-11-25 13:46 ` Krzysztof Kozlowski
2024-11-25 13:35 ` [PATCH 6/7] iio: imu: adis16550: add adis16550 support Robert Budai
2024-11-25 13:47 ` Krzysztof Kozlowski
2024-11-30 17:31 ` Jonathan Cameron
2024-11-25 13:35 ` [PATCH 7/7] docs: iio: add documentation for adis16550 driver Robert Budai
2024-11-25 14:22 ` [PATCH 0/7] adis16550-v2 Budai, Robert
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=20241130171343.007eaffd@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=ramona.gradinariu@analog.com \
--cc=robert.budai@analog.com \
--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).