[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240817160900.01224c80@jic23-huawei>
Date: Sat, 17 Aug 2024 16:09:10 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Guillaume Stols <gstols@...libre.com>
Cc: Uwe Kleine-König <ukleinek@...nel.org>, Lars-Peter
Clausen <lars@...afoo.de>, Michael Hennerich
<Michael.Hennerich@...log.com>, Rob Herring <robh@...nel.org>, Krzysztof
Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Greg
Kroah-Hartman <gregkh@...uxfoundation.org>, "Rafael J. Wysocki"
<rafael@...nel.org>, Jonathan Corbet <corbet@....net>,
linux-pwm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fbdev@...r.kernel.org, linux-iio@...r.kernel.org,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
aardelean@...libre.com
Subject: Re: [PATCH 2/8] dt-bindings: iio: adc: ad7606: Add iio backend
bindings
On Thu, 15 Aug 2024 12:11:56 +0000
Guillaume Stols <gstols@...libre.com> wrote:
> Add the required properties for iio-backend support, as well as an
> example and the conditions to mutually exclude interruption and
> conversion trigger with iio-backend.
> The iio-backend's function is to controls the communication, and thus the
> interruption pin won't be available anymore.
> As a consequence, the conversion pin must be controlled externally since
> we will miss information about when every single conversion cycle (i.e
> conversion + data transfert) ends, hence a PWM is introduced to trigger
transfer
> the conversions.
>
> Signed-off-by: Guillaume Stols <gstols@...libre.com>
> ---
> .../devicetree/bindings/iio/adc/adi,ad7606.yaml | 75 +++++++++++++++++++++-
> 1 file changed, 72 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7606.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad7606.yaml
> index c0008d36320f..4b324f7e3207 100644
> --- a/Documentation/devicetree/bindings/iio/adc/adi,ad7606.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/adi,ad7606.yaml
> @@ -114,13 +114,28 @@ properties:
> assumed that the pins are hardwired to VDD.
> type: boolean
>
> + pwms:
> + description:
> + In case the conversion is triggered by a PWM instead of a GPIO plugged to
> + the CONVST pin, the PWM must be referenced.
> + minItems: 1
> + maxItems: 2
> +
> + pwm-names:
> + minItems: 1
> + maxItems: 2
> +
> + io-backends:
> + description:
> + A reference to the iio-backend, which is responsible handling the BUSY
> + pin's falling edge and communication.
> + An example of backend can be found at
> + http://analogdevicesinc.github.io/hdl/library/axi_ad7606x/index.html
> +
> required:
> - compatible
> - - reg
I think we still want a reg, but only to differentiate multiple instances
perhaps.
> - avcc-supply
> - vdrive-supply
Powered by blists - more mailing lists