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>,
Alex Lanzano <lanzano.alex@gmail.com>,
Shen Jianping <Jianping.Shen@de.bosch.com>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<robi_budai@yahoo.com>
Subject: Re: [PATCH v3 3/7] iio: imu: adis: Add reset to custom ops
Date: Thu, 19 Dec 2024 17:20:13 +0000 [thread overview]
Message-ID: <20241219172013.73e6eebc@jic23-huawei> (raw)
In-Reply-To: <20241216144818.25344-4-robert.budai@analog.com>
On Mon, 16 Dec 2024 16:48:09 +0200
Robert Budai <robert.budai@analog.com> wrote:
> This patch allows the custom definition of reset funcitonality
functionality
> for adis object. It is useful in cases where the reset does not
> need to sleep after the reset since it is handled by the library.
reset does not need to sleep? Driver I assume?
>
> 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>
> ---
>
> v3:
> - added reset to default ops and used the allowed custom ops definition in case all read/write and reset are defined
>
> drivers/iio/imu/adis.c | 7 ++++---
> include/linux/iio/imu/adis.h | 3 +++
> 2 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/imu/adis.c b/drivers/iio/imu/adis.c
> index 54915c7a3e76..9e4113473dc4 100644
> --- a/drivers/iio/imu/adis.c
> +++ b/drivers/iio/imu/adis.c
> @@ -340,7 +340,7 @@ int __adis_reset(struct adis *adis)
> const struct adis_timeout *timeouts = adis->data->timeouts;
>
> ret = __adis_write_reg_8(adis, adis->data->glob_cmd_reg,
> - ADIS_GLOB_CMD_SW_RESET);
> + ADIS_GLOB_CMD_SW_RESET);
> if (ret) {
> dev_err(&adis->spi->dev, "Failed to reset device: %d\n", ret);
> return ret;
> @@ -491,6 +491,7 @@ EXPORT_SYMBOL_NS_GPL(adis_single_conversion, "IIO_ADISLIB");
> static const struct adis_ops adis_default_ops = {
> .read = __adis_read_reg,
> .write = __adis_write_reg,
> + .reset = __adis_reset,
> };
>
> /**
> @@ -522,9 +523,9 @@ int adis_init(struct adis *adis, struct iio_dev *indio_dev,
>
> adis->spi = spi;
> adis->data = data;
> - if (!adis->ops->write && !adis->ops->read)
> + if (!adis->ops->write && !adis->ops->read && !adis->ops->reset)
> adis->ops = &adis_default_ops;
> - else if (!adis->ops->write || !adis->ops->read)
> + else if (!adis->ops->write || !adis->ops->read || !adis->ops->reset)
> return -EINVAL;
>
> iio_device_set_drvdata(indio_dev, adis);
> diff --git a/include/linux/iio/imu/adis.h b/include/linux/iio/imu/adis.h
> index 89cfa75ae9ea..52652f51db2e 100644
> --- a/include/linux/iio/imu/adis.h
> +++ b/include/linux/iio/imu/adis.h
> @@ -98,12 +98,15 @@ struct adis_data {
> * struct adis_ops: Custom ops for adis devices.
> * @write: Custom spi write implementation.
> * @read: Custom spi read implementation.
> + * @reset: Custom sw reset implementation. The custom implementation does not
> + * need to sleep after the reset. It's done by the library already.
> */
> struct adis_ops {
> int (*write)(struct adis *adis, unsigned int reg, unsigned int value,
> unsigned int size);
> int (*read)(struct adis *adis, unsigned int reg, unsigned int *value,
> unsigned int size);
> + int (*reset)(struct adis *adis);
> };
>
> /**
next prev parent reply other threads:[~2024-12-19 17:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 14:48 [PATCH v3 0/7] Add support for ADIS16550 and ADIS16550W Robert Budai
2024-12-16 14:48 ` [PATCH v3 1/7] iio: imu: adis: Remove documented not used elements Robert Budai
2024-12-19 17:18 ` Jonathan Cameron
2024-12-16 14:48 ` [PATCH v3 2/7] iio: imu: adis: Add custom ops struct Robert Budai
2024-12-16 14:48 ` [PATCH v3 3/7] iio: imu: adis: Add reset to custom ops Robert Budai
2024-12-19 17:20 ` Jonathan Cameron [this message]
2024-12-16 14:48 ` [PATCH v3 4/7] iio: imu: adis: Add DIAG_STAT register size Robert Budai
2024-12-16 14:48 ` [PATCH v3 5/7] dt-bindings: iio: Add adis16550 bindings Robert Budai
2024-12-16 16:20 ` Rob Herring (Arm)
2024-12-19 17:25 ` Jonathan Cameron
2024-12-16 14:48 ` [PATCH v3 6/7] iio: imu: adis16550: add adis16550 support Robert Budai
2024-12-17 10:29 ` Nuno Sá
2024-12-19 17:36 ` Jonathan Cameron
2024-12-16 14:48 ` [PATCH v3 7/7] docs: iio: add documentation for adis16550 driver Robert Budai
2024-12-19 17:39 ` Jonathan Cameron
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=20241219172013.73e6eebc@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jianping.Shen@de.bosch.com \
--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=lanzano.alex@gmail.com \
--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 \
--cc=robi_budai@yahoo.com \
/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