From: Mark Rutland <mark.rutland@arm.com>
To: Paul Cercueil <paul.cercueil@analog.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCHv2 1/3] Documentation: ad5064: Added devicetree bindings documentation
Date: Mon, 12 Oct 2015 16:18:57 +0100 [thread overview]
Message-ID: <20151012151857.GC7452@leverpostej> (raw)
In-Reply-To: <1444650634-12025-1-git-send-email-paul.cercueil@analog.com>
On Mon, Oct 12, 2015 at 01:50:32PM +0200, Paul Cercueil wrote:
> Signed-off-by: Paul Cercueil <paul.cercueil@analog.com>
> ---
> .../devicetree/bindings/iio/dac/ad5064.txt | 48 ++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/dac/ad5064.txt
>
> v2: No change in this patch
>
> diff --git a/Documentation/devicetree/bindings/iio/dac/ad5064.txt b/Documentation/devicetree/bindings/iio/dac/ad5064.txt
> new file mode 100644
> index 0000000..fa2d328
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/dac/ad5064.txt
> @@ -0,0 +1,48 @@
> +Analog Devices AD5064 DAC device driver
> +
> +Required properties:
> + - compatible: Must be one of:
> + * "adi,ad5024"
> + * "adi,ad5025"
> + * "adi,ad5044"
> + * "adi,ad5045"
> + * "adi,ad5064"
> + * "adi,ad5064-1"
> + * "adi,ad5065"
> + * "adi,ad5628-1"
> + * "adi,ad5628-2"
> + * "adi,ad5648-1"
> + * "adi,ad5648-2"
> + * "adi,ad5666-1"
> + * "adi,ad5666-2"
> + * "adi,ad5668-1"
> + * "adi,ad5668-2"
> + * "adi,ad5668-3"
> + - reg: SPI chip select number for the device
> + - spi-max-frequency: Max SPI frequency to use (< 30000000)
> + - vrefA-supply, vrefB-supply: phandles to external reference voltage
> + supplies for channels 0 and 1 respectively.
> + This property must be present for ad5024, ad5025, ad5044, ad5045,
> + ad5064, ad5065.
> + - vrefC-supply, vrefD-supply: phandles to external reference voltage
> + supplies for channels 2 and 3 respectively.
> + This property must be present for ad5024, ad5044, ad5064.
Nit: please don't use CamelCase property names. just have vref-a-supply
and so on.
> +
> +Optional properties:
> + - vref-supply: phandle to the external reference voltage supply.
> + This should only be set if there is an external reference voltage
> + connected to the vref or vref[A-D] pins.
I don't understand. Surely the latter case means you're describing the
same supply twice (as it should already be in vref*-supply)?
What vref pins does the HW actually have?
> + If the property is not set, the internal reference voltage supply
> + is used if present.
> + This property can be used with ad5064-1, ad5628-1, ad5628-2, ad5648-1,
> + ad5648-2, ad5666-1, ad5666-2, ad5668-1, ad5668-2, ad5668-3.
> +
> +Example:
> +
> + ad5668-2@4 {
> + compatible = "adi,ad5668-2";
> + reg = <4>;
> + spi-max-frequency = <10000000>;
> + adi,use-external-reference;
This is undocumented (and unused by the driver?).
Thanks,
Mark.
next prev parent reply other threads:[~2015-10-12 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 11:50 [PATCHv2 1/3] Documentation: ad5064: Added devicetree bindings documentation Paul Cercueil
2015-10-12 11:50 ` [PATCHv2 2/3] iio: ad5064: Explicitly configure whether to use external supply Paul Cercueil
2015-10-12 11:50 ` [PATCHv2 3/3] iio: ad5064: Always use external vref if there is no internal vref Paul Cercueil
2015-10-12 15:18 ` Mark Rutland [this message]
2015-10-13 11:11 ` [PATCHv2 1/3] Documentation: ad5064: Added devicetree bindings documentation Lars-Peter Clausen
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=20151012151857.GC7452@leverpostej \
--to=mark.rutland@arm.com \
--cc=Michael.Hennerich@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.cercueil@analog.com \
--cc=pawel.moll@arm.com \
--cc=pmeerw@pmeerw.net \
--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