devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: <marius.cristea@microchip.com>
Cc: <lars@metafoo.de>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
	<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: adc: adding MCP3564 ADC
Date: Sat, 5 Aug 2023 18:39:06 +0100	[thread overview]
Message-ID: <20230805183906.521c90b0@jic23-huawei> (raw)
In-Reply-To: <20230804142820.89593-2-marius.cristea@microchip.com>

On Fri, 4 Aug 2023 17:28:19 +0300
<marius.cristea@microchip.com> wrote:

> From: Marius Cristea <marius.cristea@microchip.com>
> 
> This is the device tree schema for iio driver for
> Microchip family of 153.6 ksps, Low-Noise 16/24-Bit
> Delta-Sigma ADCs with an SPI interface (Microchip's
> MCP3461, MCP3462, MCP3464, MCP3461R, MCP3462R,
> MCP3464R, MCP3561, MCP3562, MCP3564, MCP3561R,
> MCP3562R and MCP3564R analog to digital converters).
> 
> Signed-off-by: Marius Cristea <marius.cristea@microchip.com>

Given driver handles the channel label binding, nice to have
that in the example here.


> +
> +examples:
> +  - |
> +    spi {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        adc@0 {
> +            compatible = "microchip,mcp3564r";
> +            reg = <0>;
> +            vref-supply = <&vref_reg>;
> +            spi-cpha;
> +            spi-cpol;
> +            spi-max-frequency = <10000000>;
> +            microchip,hw-device-address = <1>;
> +
> +            #address-cells = <1>;
> +            #size-cells = <0>;
> +
> +            channel@0 {
> +                /* CH0 to AGND */
> +                reg = <0>;
> +            };
> +
> +            channel@1 {
> +                /* CH1 to AGND */
> +                reg = <1>;
> +            };
> +
> +            /* diff-channels */
> +            channel@11 {
> +                reg = <11>;
> +
> +                /* CN0, CN1 */
> +                diff-channels = <0 1>;
> +            };
> +
> +            channel@22 {
> +                reg = <0x22>;
> +
> +                /* CN1, CN2 */
> +                diff-channels = <1 2>;
> +            };
> +
> +            channel@23 {
> +                reg = <0x23>;
> +
> +                /* CN1, CN3 */
> +                diff-channels = <1 3>;
> +            };
> +        };
> +    };
> +...


  reply	other threads:[~2023-08-05 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 14:28 [PATCH v3 0/2] Adding support for Microchip MCP3564 ADC family marius.cristea
2023-08-04 14:28 ` [PATCH v3 1/2] dt-bindings: iio: adc: adding MCP3564 ADC marius.cristea
2023-08-05 17:39   ` Jonathan Cameron [this message]
2023-08-04 14:28 ` [PATCH v3 2/2] iio: adc: adding support for " marius.cristea
2023-08-05 17:59   ` Jonathan Cameron
2023-08-18 16:29     ` Marius.Cristea
2023-08-28 13:48       ` Jonathan Cameron
2023-08-04 15:28 ` [PATCH v3 0/2] Adding support for Microchip MCP3564 ADC family Conor Dooley
2023-08-05 17:08 ` Jonathan Cameron

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=20230805183906.521c90b0@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marius.cristea@microchip.com \
    --cc=robh+dt@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).