From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Charles-Antoine Couret <charles-antoine.couret@essensium.com>,
linux-iio@vger.kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH V3 2/2] doc:devicetree: Add AD7949 device tree bindings in documentation
Date: Sun, 28 Oct 2018 15:20:31 +0000 [thread overview]
Message-ID: <20181028152016.5b97cc80@archlinux> (raw)
In-Reply-To: <20181023154319.GA17996@bogus>
On Tue, 23 Oct 2018 10:43:19 -0500
Rob Herring <robh@kernel.org> wrote:
> On Mon, Oct 22, 2018 at 11:02:43PM +0200, Charles-Antoine Couret wrote:
> > Description how to invoke ad7949 driver from device tree file.
>
> Use subject prefixes that match the subsystem (i.e run git log --oneline
> <dir> to see). Something like this would be better:
>
> dt-bindings: iio: adc: Add Analog Devices AD7949, AD7682 and AD7689
I've modified this and changed as below in the interests of saving everyone
time that a V4 and it's review would take!
Thanks for the review Rob.
Applied to the togreg branch of iio.git and pushed out as testing for the
autobuilders to play with it.
Thanks,
Jonathan
>
> >
> > Signed-off-by: Charles-Antoine Couret <charles-antoine.couret@essensium.com>
> > ---
> > V1 to V3:
> > * Add prefix vendor
> > * Improve patch description
> >
> > .../devicetree/bindings/iio/adc/ad7949.txt | 18 ++++++++++++++++++
> > 1 file changed, 18 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/iio/adc/ad7949.txt
> >
> > diff --git a/Documentation/devicetree/bindings/iio/adc/ad7949.txt b/Documentation/devicetree/bindings/iio/adc/ad7949.txt
> > new file mode 100644
> > index 000000000000..f1c3af53f5cc
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/adc/ad7949.txt
> > @@ -0,0 +1,18 @@
> > +* Analog Devices AD7949/AD7682/AD7689
> > +
> > +Required properties:
> > + - compatible: Should be one of
> > + * "adi,ad7949"
> > + * "adi,ad7682"
> > + * "adi,ad7689"
> > + - 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 (< 33000000)
>
> This should be optional and only be needed if the frequency needs to be
> limited below what the host and device can support. IOW, a board
> limitation. The host and device drivers already need to know their
> maximum frequencies to validate this value.
I dropped this from the binding as it is generic anyway rather than
device specific.
>
> > +
> > +Example:
> > +adc@0 {
> > + compatible = "adi,ad7949";
> > + reg = <0>;
> > + vref-supply = <&vdd_supply>;
> > + spi-max-frequency = <200000>;
> > +};
> > --
> > 2.19.1
> >
next prev parent reply other threads:[~2018-10-29 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 21:02 [PATCH V3 1/2] iio:adc:ad7949: Add AD7949 ADC driver family Charles-Antoine Couret
2018-10-22 21:02 ` [PATCH V3 2/2] doc:devicetree: Add AD7949 device tree bindings in documentation Charles-Antoine Couret
2018-10-23 15:43 ` Rob Herring
2018-10-28 15:20 ` Jonathan Cameron [this message]
2018-10-28 15:13 ` [PATCH V3 1/2] iio:adc:ad7949: Add AD7949 ADC driver family Jonathan Cameron
2018-10-28 16:13 ` Couret Charles-Antoine
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=20181028152016.5b97cc80@archlinux \
--to=jic23@kernel.org \
--cc=charles-antoine.couret@essensium.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@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).