From: Conor Dooley <conor@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
linux-iio@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alisa-Dariana Roman <alisa.roman@analog.com>,
Renato Lui Geh <renatogeh@gmail.com>,
Ceclan Dumitru <dumitru.ceclan@analog.com>,
devicetree@vger.kernel.org, Nuno Sa <nuno.sa@analog.com>,
David Lechner <dlechner@baylibre.com>,
Alexandru Ardelean <aardelean@baylibre.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Trevor Gamblin <tgamblin@baylibre.com>
Subject: Re: [PATCH v5 03/10] dt-bindings: iio: adc: adi,ad7{124,173,192,780}: Allow specifications of a gpio for irq line
Date: Tue, 3 Dec 2024 16:21:55 +0000 [thread overview]
Message-ID: <20241203-endanger-dwindle-a0b38ba38d4a@spud> (raw)
In-Reply-To: <20241203110019.1520071-15-u.kleine-koenig@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
On Tue, Dec 03, 2024 at 12:00:23PM +0100, Uwe Kleine-König wrote:
> For the AD7124 chip and some of its cousins the logical irq line (̅R̅D̅Y)
> is physically on the same pin as the spi MISO output (DOUT) and so
> reading a register might trigger an interrupt. For correct operation
> it's critical that the actual state of the pin can be read to judge if
> an interrupt event is a real one or just a spurious one triggered by
> toggling the line in its MISO mode.
>
> Allow specification of an "rdy-gpios" property that references a GPIO
> that can be used for that purpose. While this is typically the same GPIO
> also used (implicitly) as interrupt source, it is still supposed that
> the interrupt is specified as before and usual.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-12-03 16:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 11:00 [PATCH v5 00/10] iio: adc: ad7124: Various fixes Uwe Kleine-König
2024-12-03 11:00 ` [PATCH v5 01/10] iio: adc: ad7124: Don't create more channels than the driver can handle Uwe Kleine-König
2024-12-03 11:00 ` [PATCH v5 02/10] iio: adc: ad7124: Refuse invalid input specifiers Uwe Kleine-König
2024-12-03 11:00 ` [PATCH v5 03/10] dt-bindings: iio: adc: adi,ad7{124,173,192,780}: Allow specifications of a gpio for irq line Uwe Kleine-König
2024-12-03 16:21 ` Conor Dooley [this message]
2024-12-03 11:00 ` [PATCH v5 04/10] iio: adc: ad_sigma_delta: Add support for reading irq status using a GPIO Uwe Kleine-König
2024-12-03 11:00 ` [PATCH v5 05/10] iio: adc: ad_sigma_delta: Handle CS assertion as intended in ad_sd_read_reg_raw() Uwe Kleine-König
2024-12-03 11:00 ` [PATCH v5 06/10] iio: adc: ad_sigma_delta: Fix a race condition Uwe Kleine-König
2024-12-03 11:00 ` [PATCH v5 07/10] iio: adc: ad_sigma_delta: Store information about reset sequence length Uwe Kleine-König
2024-12-03 11:00 ` [PATCH v5 08/10] iio: adc: ad_sigma_delta: Check for previous ready signals Uwe Kleine-König
2024-12-03 13:10 ` Andy Shevchenko
2024-12-03 16:15 ` Uwe Kleine-König
2024-12-03 17:47 ` Andy Shevchenko
2024-12-03 18:47 ` Uwe Kleine-König
2024-12-03 18:53 ` Andy Shevchenko
2024-12-03 11:00 ` [PATCH v5 09/10] iio: adc: ad7124: Add error reporting during probe Uwe Kleine-König
2024-12-03 11:00 ` [PATCH v5 10/10] iio: adc: ad7124: Implement temperature measurement Uwe Kleine-König
2024-12-05 18:31 ` [PATCH v5 00/10] iio: adc: ad7124: Various fixes Uwe Kleine-König
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=20241203-endanger-dwindle-a0b38ba38d4a@spud \
--to=conor@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=aardelean@baylibre.com \
--cc=alisa.roman@analog.com \
--cc=andy.shevchenko@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=dumitru.ceclan@analog.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=renatogeh@gmail.com \
--cc=robh@kernel.org \
--cc=tgamblin@baylibre.com \
--cc=u.kleine-koenig@baylibre.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