From: Jonathan Cameron <jic23@kernel.org>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>,
wsa+renesas@sang-engineering.com, magnus.damm@gmail.com,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
marek.vasut@gmail.com, geert@linux-m68k.org,
mark.rutland@arm.com
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <Mark.Rutland@arm.com>"devicetree@vger.kernel.org"
<devicetree@vger.kernel.org>
Subject: Re: [PATCHv5 2/2] dt-bindings: iio: document MAX11100 ADC
Date: Sat, 21 Jan 2017 13:22:03 +0000 [thread overview]
Message-ID: <ff915715-98c4-9792-eae7-9f466d5fa459@kernel.org> (raw)
In-Reply-To: <1484757053-7102-3-git-send-email-jacopo+renesas@jmondi.org>
On 18/01/17 16:30, Jacopo Mondi wrote:
> Add device tree bindings documentation for Maxim MAX11100 single-channel
> ADC
>
> Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Simple enough I'm happy to take it without bothering Rob or Mark.
However, any device tree bindings at all should be cc'd to them and to the devicetree
list.
Done in case anyone wants to comment.
> ---
> .../devicetree/bindings/iio/adc/max11100.txt | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/adc/max11100.txt
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/max11100.txt b/Documentation/devicetree/bindings/iio/adc/max11100.txt
> new file mode 100644
> index 0000000..ad0bc31
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/max11100.txt
> @@ -0,0 +1,19 @@
> +* Maxim max11100 Analog to Digital Converter (ADC)
> +
> +Required properties:
> + - compatible: Should be "maxim,max11100"
> + - reg: the adc unit address
> + - vref-supply: phandle to the regulator that provides reference voltage
> +
> +Optional properties:
> + - spi-max-frequency: SPI maximum frequency
> +
> +Example:
> +
> +max11100: adc@0 {
> + compatible = "maxim,max11100";
> + reg = <0>;
> + vref-supply = <&adc0_vref>;
> + spi-max-frequency = <240000>;
> +};
> +
>
next prev parent reply other threads:[~2017-01-21 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 16:30 [PATCH v5 0/2] iio: adc: Add Maxim MAX11100 driver Jacopo Mondi
[not found] ` <1484757053-7102-1-git-send-email-jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org>
2017-01-18 16:30 ` [PATCHv5 1/2] " Jacopo Mondi
2017-01-18 16:30 ` [PATCHv5 2/2] dt-bindings: iio: document MAX11100 ADC Jacopo Mondi
2017-01-21 13:22 ` Jonathan Cameron [this message]
[not found] ` <ff915715-98c4-9792-eae7-9f466d5fa459-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-01-21 13:33 ` Jonathan Cameron
[not found] ` <1484757053-7102-3-git-send-email-jacopo+renesas-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org>
2017-01-21 20:33 ` Rob Herring
2017-01-22 13:21 ` 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=ff915715-98c4-9792-eae7-9f466d5fa459@kernel.org \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=jacopo+renesas@jmondi.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).