From: Jonathan Santos <jonath4nns@gmail.com>
To: Andy Shevchenko <andy@kernel.org>
Cc: 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,
linux-acpi@vger.kernel.org, nuno.sa@analog.com,
Michael.Hennerich@analog.com, marcelo.schmitt@analog.com,
jic23@kernel.org, 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, rafael@kernel.org,
djrscally@gmail.com
Subject: Re: [PATCH v9 09/12] iio: adc: ad7768-1: add support for Synchronization over SPI
Date: Mon, 2 Jun 2025 14:15:23 -0300 [thread overview]
Message-ID: <aD3cK5PioN7Rw3pP@JSANTO12-L01.ad.analog.com> (raw)
In-Reply-To: <aDnuvAdkcTAP2tMt@smile.fi.intel.com>
On 05/30, Andy Shevchenko wrote:
> On Thu, May 29, 2025 at 07:50:29PM -0300, Jonathan Santos wrote:
> > +static int ad7768_trigger_sources_sync_setup(struct device *dev,
> > + struct fwnode_handle *dev_fwnode,
> > + struct ad7768_state *st)
> > +{
> > + struct fwnode_reference_args args;
> > +
> > + struct fwnode_handle *fwnode __free(fwnode_handle) =
> > + fwnode_find_reference_args(dev_fwnode, "trigger-sources",
> > + "#trigger-source-cells", 0,
> > + AD7768_TRIGGER_SOURCE_SYNC_IDX, &args);
>
> I don't see how args are being used. This puts in doubt the need of the first
> patch.
>
If the wrapper is the issue, maybe it is better doing this instead?
static int ad7768_trigger_sources_sync_setup(struct device *dev,
struct fwnode_handle *dev_fwnode,
struct ad7768_state *st)
{
struct fwnode_reference_args args;
struct fwnode_handle *fwnode __free(fwnode_handle) = NULL;
int ret;
ret = fwnode_property_get_reference_args(dev_fwnode, "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 */
> > + 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");
> > + return PTR_ERR_OR_ZERO(st->gpio_sync_in);
> > + }
> > +
> > + /*
> > + * 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.
> > + */
> > + return dev_err_probe(dev, -EOPNOTSUPP, "Invalid synchronization trigger source\n");
> > +}
Then we can get rid of the first patch.
Regards,
Jonathan S.
next prev parent reply other threads:[~2025-06-02 17:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 22:47 [PATCH v9 00/12] iio: adc: ad7768-1: Add features, improvements, and fixes Jonathan Santos
2025-05-29 22:48 ` [PATCH v9 01/12] device property: add fwnode_find_reference_args() Jonathan Santos
2025-05-30 17:48 ` Andy Shevchenko
2025-05-31 17:43 ` Jonathan Cameron
2025-05-29 22:48 ` [PATCH v9 02/12] dt-bindings: trigger-source: add generic GPIO trigger source Jonathan Santos
2025-05-29 22:48 ` [PATCH v9 03/12] dt-bindings: iio: adc: ad7768-1: add trigger-sources property Jonathan Santos
2025-05-29 22:49 ` [PATCH v9 04/12] dt-bindings: iio: adc: ad7768-1: Document GPIO controller Jonathan Santos
2025-05-29 22:49 ` [PATCH v9 05/12] dt-bindings: iio: adc: ad7768-1: document regulator provider property Jonathan Santos
2025-05-29 22:49 ` [PATCH v9 06/12] iio: adc: ad7768-1: add regulator to control VCM output Jonathan Santos
2025-05-29 22:49 ` [PATCH v9 07/12] iio: adc: ad7768-1: Add GPIO controller support Jonathan Santos
2025-05-29 22:50 ` [PATCH v9 08/12] iio: adc: ad7768-1: add multiple scan types to support 16-bits mode Jonathan Santos
2025-05-29 22:50 ` [PATCH v9 09/12] iio: adc: ad7768-1: add support for Synchronization over SPI Jonathan Santos
2025-05-30 16:09 ` Jonathan Cameron
2025-05-30 17:45 ` Andy Shevchenko
2025-05-31 17:42 ` Jonathan Cameron
2025-06-02 17:15 ` Jonathan Santos [this message]
2025-06-02 21:25 ` Andy Shevchenko
2025-06-07 12:19 ` Jonathan Cameron
2025-05-29 22:50 ` [PATCH v9 10/12] iio: adc: ad7768-1: replace manual attribute declaration Jonathan Santos
2025-05-29 22:51 ` [PATCH v9 11/12] iio: adc: ad7768-1: add filter type and oversampling ratio attributes Jonathan Santos
2025-05-29 22:51 ` [PATCH v9 12/12] iio: adc: ad7768-1: add low pass -3dB cutoff attribute Jonathan Santos
2025-05-30 16:19 ` [PATCH v9 00/12] iio: adc: ad7768-1: Add features, improvements, and fixes Jonathan Cameron
2025-05-30 17:49 ` 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=aD3cK5PioN7Rw3pP@JSANTO12-L01.ad.analog.com \
--to=jonath4nns@gmail.com \
--cc=Jonathan.Santos@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=aDnuvAdkcTAP2tMt@smile.fi.intel.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.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=rafael@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).