From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Charles-Antoine Couret <charles-antoine.couret@essensium.com>
Cc: linux-iio@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] Add ti,dac7311 device tree bindings in documentation
Date: Sun, 21 Oct 2018 15:58:24 +0100 [thread overview]
Message-ID: <20181021155811.0530ec23@archlinux> (raw)
In-Reply-To: <20181017203738.13477-2-charles-antoine.couret@essensium.com>
On Wed, 17 Oct 2018 22:37:38 +0200
Charles-Antoine Couret <charles-antoine.couret@essensium.com> wrote:
Would be good to have a small amount of description here + it seems you didn't
sign off on this patch so we can't apply it to the kernel.
Please cc devicetree list and maintainers for any devicetree bindings.
+cc Rob, Mark and list.
Thanks,
Jonathan
> ---
> .../bindings/iio/dac/ti,dac7311.txt | 20 +++++++++++++++++++
> 1 file changed, 20 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/dac/ti,dac7311.txt
>
> diff --git a/Documentation/devicetree/bindings/iio/dac/ti,dac7311.txt b/Documentation/devicetree/bindings/iio/dac/ti,dac7311.txt
> new file mode 100644
> index 000000000000..771414024cd0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/dac/ti,dac7311.txt
> @@ -0,0 +1,20 @@
> +TI DAC7311 device tree bindings
> +
> +Required properties:
> +
> +- compatible: Must be set to "ti,dac7311", "ti,dac6311" or "ti,dac5311"
> +- reg: spi chip select number for the device
> +- vref-supply: The regulator supply for ADC reference voltage
> +- spi-max-frequency: Max SPI frequency to use (< 50000000)
> +
> +Example:
> +
> + spi_master {
> + dac7311: dac7311@0 {
Not sure why you need the pre colon bit here.
Also I'd imagine the standard naming for a dac is probably
dac@0
(I haven't checked the devicetree spec to see if they actually
have that one in there as I'm on a train with dodgy wifi).
Jonathan
> + compatible = "ti,dac7311";
> + reg = <0>; /* CS0 */
> + spi-max-frequency = <1000000>;
> + vref-supply = <&vdd_supply>;
> + };
> + };
> +
next prev parent reply other threads:[~2018-10-21 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 20:37 [PATCH 1/2] Add driver for Texas Instrument DAC7311 It is a driver for Texas Instruments 8/10/12-bit 1-channel compatible with DAC6311 and DAC5311 chips Charles-Antoine Couret
2018-10-17 20:37 ` [PATCH 2/2] Add ti,dac7311 device tree bindings in documentation Charles-Antoine Couret
2018-10-21 14:58 ` Jonathan Cameron [this message]
2018-10-21 15:07 ` [PATCH 1/2] Add driver for Texas Instrument DAC7311 It is a driver for Texas Instruments 8/10/12-bit 1-channel compatible with DAC6311 and DAC5311 chips Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2018-10-06 20:31 Charles-Antoine Couret
2018-10-06 20:31 ` [PATCH 2/2] Add ti,dac7311 device tree bindings in documentation Charles-Antoine Couret
2018-10-07 16:38 ` 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=20181021155811.0530ec23@archlinux \
--to=jic23@jic23.retrosnub.co.uk \
--cc=charles-antoine.couret@essensium.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.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).