From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Santos <Jonathan.Santos@analog.com>
Cc: <linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<andy@kernel.org>, <nuno.sa@analog.com>,
<Michael.Hennerich@analog.com>, <marcelo.schmitt@analog.com>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<marcelo.schmitt1@gmail.com>, <linus.walleij@linaro.org>,
<brgl@bgdev.pl>, <lgirdwood@gmail.com>, <broonie@kernel.org>,
<jonath4nns@gmail.com>, <dlechner@baylibre.com>
Subject: Re: [PATCH v6 08/11] iio: adc: ad7768-1: add support for Synchronization over SPI
Date: Mon, 5 May 2025 16:59:53 +0100 [thread overview]
Message-ID: <20250505165953.15958d58@jic23-huawei> (raw)
In-Reply-To: <c5a5376a6ffbb571d7874218494b04fd20015ee9.1745605382.git.Jonathan.Santos@analog.com>
On Sun, 27 Apr 2025 21:13:47 -0300
Jonathan Santos <Jonathan.Santos@analog.com> wrote:
> The synchronization method using GPIO requires the generated pulse to be
> truly synchronous with the base MCLK signal. When it is not possible to
> do that in hardware, the datasheet recommends using synchronization over
> SPI, where the generated pulse is already synchronous with MCLK. This
> requires the SYNC_OUT pin to be connected to SYNC_IN pin.
>
> Use trigger-sources property to enable device synchronization over SPI
> and multi-device synchronization, as an alternative to adi,sync-in-gpios
> property.
>
> +static int ad7768_trigger_sources_get_sync(struct device *dev,
> + struct ad7768_state *st)
> +{
> + struct fwnode_reference_args args;
> + struct fwnode_handle *fwnode = NULL;
> + int ret;
> +
> + /*
> + * The AD7768-1 allows two primary methods for driving the SYNC_IN pin
> + * to synchronize one or more devices:
> + * 1. Using an external GPIO.
> + * 2. Using a SPI command, where the SYNC_OUT pin generates a
> + * synchronization pulse that drives the SYNC_IN pin.
> + */
> + if (!device_property_present(dev, "trigger-sources")) {
> + /*
> + * In the absence of trigger-sources property, enable self
> + * synchronization over SPI (SYNC_OUT).
> + */
> + st->en_spi_sync = true;
> + return 0;
> + }
> +
> + ret = fwnode_property_get_reference_args(dev_fwnode(dev),
> + "trigger-sources",
> + "#trigger-source-cells",
> + 0,
> + AD7768_TRIGGER_SOURCE_SYNC_IDX,
> + &args);
> + if (ret)
> + return ret;
> +
> + fwnode = args.fwnode;
> + /*
> + * First, try getting the GPIO trigger source and fallback to
> + * synchronization over SPI in case of failure.
> + */
> + st->gpio_sync_in = ad7768_trigger_source_get_gpio(dev, fwnode);
> + if (IS_ERR(st->gpio_sync_in)) {
> + /*
> + * For this case, it requires one argument, which indicates the
> + * output pin referenced.
> + */
> + if (args.nargs < 1)
> + goto err_not_supp;
> +
> + if (args.args[0] != AD7768_TRIGGER_SOURCE_SYNC_OUT)
> + goto err_not_supp;
> +
> + /*
> + * Only self trigger is supported for now, i.e.,
> + * external SYNC_OUT is not allowed.
> + */
> + if (fwnode->dev == dev) {
> + st->en_spi_sync = true;
> + goto out_put_node;
> + }
> +
> + goto err_not_supp;
> + }
> +
> + goto out_put_node;
> +
> +err_not_supp:
Split the good and bad paths here so we don't have good paths jumping to
mid way through the block. If the good paths need to jump then I'd
suggest factoring out the stuff with the node held into a separate function.
Superficially it just looks like one condition flip and you are refactoring
this anyway based on other feedback so maybe this comment becomes irrelevant!
> + ret = dev_err_probe(dev, -EOPNOTSUPP,
> + "Invalid synchronization trigger source");
> +out_put_node:
> + fwnode_handle_put(args.fwnode);
> + return ret;
> +}
> +
next prev parent reply other threads:[~2025-05-05 16:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 0:11 [PATCH v6 00/11] iio: adc: ad7768-1: Add features, improvements, and fixes Jonathan Santos
2025-04-28 0:12 ` [PATCH v6 01/11] dt-bindings: trigger-source: add generic GPIO trigger source Jonathan Santos
2025-05-05 15:44 ` Jonathan Cameron
2025-05-05 15:56 ` David Lechner
2025-05-13 9:32 ` Linus Walleij
2025-04-28 0:12 ` [PATCH v6 02/11] dt-bindings: iio: adc: ad7768-1: add trigger-sources property Jonathan Santos
2025-04-30 18:46 ` David Lechner
2025-05-05 15:39 ` Jonathan Cameron
2025-05-06 19:16 ` Jonathan Santos
2025-05-07 19:50 ` Jonathan Cameron
2025-04-28 0:12 ` [PATCH v6 03/11] dt-bindings: iio: adc: ad7768-1: Document GPIO controller Jonathan Santos
2025-04-28 0:12 ` [PATCH v6 04/11] dt-bindings: iio: adc: ad7768-1: document regulator provider property Jonathan Santos
2025-04-28 0:13 ` [PATCH v6 05/11] iio: adc: ad7768-1: add regulator to control VCM output Jonathan Santos
2025-04-28 6:42 ` Andy Shevchenko
2025-04-30 23:24 ` Jonathan Santos
2025-04-30 18:43 ` David Lechner
2025-04-28 0:13 ` [PATCH v6 06/11] iio: adc: ad7768-1: Add GPIO controller support Jonathan Santos
2025-04-28 6:50 ` Andy Shevchenko
2025-04-30 23:37 ` Jonathan Santos
2025-04-28 0:13 ` [PATCH v6 07/11] iio: adc: ad7768-1: add multiple scan types to support 16-bits mode Jonathan Santos
2025-04-28 6:55 ` Andy Shevchenko
2025-05-05 15:52 ` Jonathan Cameron
2025-05-02 14:30 ` Marcelo Schmitt
2025-04-28 0:13 ` [PATCH v6 08/11] iio: adc: ad7768-1: add support for Synchronization over SPI Jonathan Santos
2025-04-28 7:04 ` Andy Shevchenko
2025-05-01 0:03 ` Jonathan Santos
2025-04-30 19:07 ` David Lechner
2025-05-05 15:59 ` Jonathan Cameron [this message]
2025-04-28 0:14 ` [PATCH v6 09/11] iio: adc: ad7768-1: replace manual attribute declaration Jonathan Santos
2025-04-28 7:10 ` Andy Shevchenko
2025-04-28 0:14 ` [PATCH v6 10/11] iio: adc: ad7768-1: add filter type and oversampling ratio attributes Jonathan Santos
2025-04-29 22:40 ` Andy Shevchenko
2025-05-05 16:09 ` Jonathan Cameron
2025-05-06 19:03 ` Jonathan Santos
2025-05-06 19:10 ` David Lechner
2025-04-28 0:14 ` [PATCH v6 11/11] iio: adc: ad7768-1: add low pass -3dB cutoff attribute Jonathan Santos
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=20250505165953.15958d58@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Santos@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jonath4nns@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@analog.com \
--cc=nuno.sa@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