From: Jonathan Santos <jonath4nns@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Andy Shevchenko <andy@kernel.org>,
Jonathan Santos <Jonathan.Santos@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.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, dlechner@baylibre.com
Subject: Re: [PATCH v8 08/11] iio: adc: ad7768-1: add support for Synchronization over SPI
Date: Fri, 23 May 2025 21:00:17 -0300 [thread overview]
Message-ID: <aDEMEWQvu0r9stCh@JSANTO12-L01.ad.analog.com> (raw)
In-Reply-To: <20250518175832.77b8d670@jic23-huawei>
On 05/18, Jonathan Cameron wrote:
> On Fri, 16 May 2025 12:29:02 +0300
> Andy Shevchenko <andy@kernel.org> wrote:
>
> > On Thu, May 15, 2025 at 06:13:56PM -0300, Jonathan Santos 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 the SYNC_IN pin.
> > >
> > > Use trigger-sources property to enable device synchronization over SPI
> > > and multi-device synchronization while replacing sync-in-gpios property.
> Given some discussion in here I'll not (yet) pick up this series.
>
> It's almost certainly just missed the coming merge window anyway so
> we have time.
>
> >
> > ...
> >
> > > +static int ad7768_trigger_sources_get_sync(struct device *dev,
> > > + struct ad7768_state *st)
> > > +{
> > > + struct fwnode_reference_args args;
> > > + struct fwnode_handle *fwnode = dev_fwnode(dev);
> > > + 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 (!fwnode_property_present(fwnode, "trigger-sources")) {
> >
> > I'm wondering if you can split the below to a separate function and do something like
> >
> > if (fwnode_property_present(...))
> > return setup_trigger_source(...);
> >
> > ...
> > en_spi_sync = true;
> > return 0;
> >
> > > + /*
> > > + * 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(fwnode,
> > > + "trigger-sources",
> > > + "#trigger-source-cells",
> > > + 0,
> > > + AD7768_TRIGGER_SOURCE_SYNC_IDX,
> > > + &args);
> >
> >
> > __free(fwnode_handle) ?
>
> For args.fwnode?
>
> That's fiddly to do and needs a different local variable to...
>
>
>
> >
> > > + if (ret)
> > > + return ret;
> > > +
> > > + fwnode = args.fwnode;
>
> this one.
>
> You could wrap it up in a function to make that works cleanly.
> So something similar to fwnode_find_reference() but with the
> rest of the arguments. Is there appetite for such a wrapper
> in the generic property code?
>
you mean like:
fwnode_find_reference_args(const struct fwnode_handle *fwnode,
const char *name, const char *nargs_prop,
unsigned int nargs, unsigned int index,
struct fwnode_reference_args *args)
I don't know if it helps that much and since we are not handling
arguments right know, I think fwnode_find_reference() would work (or not?).
In that case maybe we add some note or TODO to explain why.
>
> > > + /* First, try getting the GPIO trigger source */
> > > + if (fwnode_device_is_compatible(fwnode, "gpio-trigger")) {
> > > + st->gpio_sync_in = devm_fwnode_gpiod_get_index(dev, fwnode,
> > > + NULL,
> > > + 0,
> > > + GPIOD_OUT_LOW,
> > > + "sync-in");
> > > + ret = PTR_ERR_OR_ZERO(st->gpio_sync_in);
> > > + goto out_put_node;
> > > + }
> > > +
> > > + /*
> > > + * TODO: Support the other cases when we have a trigger subsystem to
> > > + * reliably handle other types of devices as trigger sources.
> > > + *
> > > + * For now, return an error message. For self triggering, omit the
> > > + * trigger-sources property.
> > > + */
> > > + ret = dev_err_probe(dev, -EOPNOTSUPP, "Invalid synchronization trigger source\n");
> > > +
> > > +out_put_node:
> >
> > The above will allow to get rid of this label.
> >
> > > + fwnode_handle_put(args.fwnode);
> > > + return ret;
> > > +}
> >
>
next prev parent reply other threads:[~2025-05-24 0:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 21:11 [PATCH v8 00/11] iio: adc: ad7768-1: Add features, improvements, and fixes Jonathan Santos
2025-05-15 21:12 ` [PATCH v8 01/11] dt-bindings: trigger-source: add generic GPIO trigger source Jonathan Santos
2025-05-15 21:12 ` [PATCH v8 02/11] dt-bindings: iio: adc: ad7768-1: add trigger-sources property Jonathan Santos
2025-05-15 21:12 ` [PATCH v8 03/11] dt-bindings: iio: adc: ad7768-1: Document GPIO controller Jonathan Santos
2025-05-15 21:13 ` [PATCH v8 04/11] dt-bindings: iio: adc: ad7768-1: document regulator provider property Jonathan Santos
2025-05-15 21:13 ` [PATCH v8 05/11] iio: adc: ad7768-1: add regulator to control VCM output Jonathan Santos
2025-05-15 21:13 ` [PATCH v8 06/11] iio: adc: ad7768-1: Add GPIO controller support Jonathan Santos
2025-05-15 21:13 ` [PATCH v8 07/11] iio: adc: ad7768-1: add multiple scan types to support 16-bits mode Jonathan Santos
2025-05-16 9:24 ` Andy Shevchenko
2025-05-15 21:13 ` [PATCH v8 08/11] iio: adc: ad7768-1: add support for Synchronization over SPI Jonathan Santos
2025-05-15 22:46 ` David Lechner
2025-05-16 9:29 ` Andy Shevchenko
2025-05-18 16:58 ` Jonathan Cameron
2025-05-24 0:00 ` Jonathan Santos [this message]
2025-05-25 9:41 ` Jonathan Cameron
2025-05-15 21:14 ` [PATCH v8 09/11] iio: adc: ad7768-1: replace manual attribute declaration Jonathan Santos
2025-05-15 21:14 ` [PATCH v8 10/11] iio: adc: ad7768-1: add filter type and oversampling ratio attributes Jonathan Santos
2025-05-16 9:34 ` Andy Shevchenko
2025-05-18 17:03 ` Jonathan Cameron
2025-05-19 17:13 ` Jonathan Santos
2025-05-19 20:15 ` David Lechner
2025-05-19 22:31 ` Jonathan Santos
2025-05-25 9:44 ` Jonathan Cameron
2025-05-15 21:14 ` [PATCH v8 11/11] iio: adc: ad7768-1: add low pass -3dB cutoff attribute Jonathan Santos
2025-05-16 9:38 ` Andy Shevchenko
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=aDEMEWQvu0r9stCh@JSANTO12-L01.ad.analog.com \
--to=jonath4nns@gmail.com \
--cc=20250518175832.77b8d670@jic23-huawei \
--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=jic23@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.