From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "robh@kernel.org" <robh@kernel.org>
Cc: "jic23@kernel.org" <jic23@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH v3 6/8] dt-bindings: iio: adc: add bindings doc for AXI ADC driver
Date: Wed, 4 Mar 2020 07:55:11 +0000 [thread overview]
Message-ID: <e8075f2fc949b541ccc369bc0cc5d3726ea0a3bf.camel@analog.com> (raw)
In-Reply-To: <20200303165323.GA32472@bogus>
On Tue, 2020-03-03 at 10:53 -0600, Rob Herring wrote:
> On Thu, Feb 27, 2020 at 10:27:17AM +0200, Alexandru Ardelean wrote:
> > This change adds the bindings documentation for the AXI ADC driver.
> >
> > Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> > ---
> > .../bindings/iio/adc/adi-axi-adc.yaml | 69 +++++++++++++++++++
>
> Follow the compatible string: adi,axi-adc.yaml
ack
>
> > 1 file changed, 69 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/iio/adc/adi-axi-
> > adc.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/iio/adc/adi-axi-adc.yaml
> > b/Documentation/devicetree/bindings/iio/adc/adi-axi-adc.yaml
> > new file mode 100644
> > index 000000000000..d45d41f4f08e
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/adc/adi-axi-adc.yaml
> > @@ -0,0 +1,69 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/iio/adc/adi-axi-adc.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Analog Devices AXI ADC IP core
> > +
> > +maintainers:
> > + - Michael Hennerich <michael.hennerich@analog.com>
> > + - Alexandru Ardelean <alexandru.ardelean@analog.com>
> > +
> > +description: |
> > + Analog Devices Generic AXI ADC IP core for interfacing an ADC device
> > + with a high speed serial (JESD204B/C) or source synchronous parallel
> > + interface (LVDS/CMOS).
> > + Usually, some other interface type (i.e SPI) is used as a control
> > + interface for the actual ADC, while this IP core will interface
> > + to the data-lines of the ADC and handle the streaming of data into
> > + memory via DMA.
> > +
> > + https://wiki.analog.com/resources/fpga/docs/axi_adc_ip
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - adi,axi-adc-10.0.a
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + dmas:
> > + minItems: 1
> > + maxItems: 1
>
> Just maxItems is enough.
ack
>
> > +
> > + dma-names:
> > + maxItems: 1
> > + items:
> > + - const: rx
> > +
> > + adi-axi-adc-client:
>
> adi,axi-adc-client
>
> Though I think 'adi,adc-dev' would be better name.
works for me
one question though; this still gives:
CHKDT Documentation/devicetree/bindings/iio/adc/adi,axi-adc.yaml
/home/sandu/work/linux/upstream/Documentation/devicetree/bindings/iio/adc/adi,ax
i-adc.yaml: properties:adi,adc-dev: {'description': 'A reference to a the actual
ADC to which this FPGA ADC interfaces to.', 'maxItems': 1} is not valid under
any of the given schemas (Possible causes of the failure):
/home/sandu/work/linux/upstream/Documentation/devicetree/bindings/iio/ad
c/adi,axi-adc.yaml: properties:adi,adc-dev: 'not' is a required property
Any thoughts?
>
> > + description:
> > + A reference to a the actual ADC to which this FPGA ADC interfaces to.
> > + maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - dmas
> > + - reg
> > + - adi-axi-adc-client
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + fpga_axi {
>
> You can drop this node.
ack
>
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > +
> > + axi-adc@44a00000 {
> > + compatible = "adi,axi-adc-10.0.a";
> > + reg = <0x44a00000 0x10000>;
> > + dmas = <&rx_dma 0>;
> > + dma-names = "rx";
> > +
> > + adi-axi-adc-client = <&spi_adc>;
> > + };
> > + };
> > +...
> > --
> > 2.20.1
> >
next prev parent reply other threads:[~2020-03-04 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 8:27 [PATCH v3 0/8] ] iio: adi-axi-adc,ad9647: Add support for AD9467 ADC Alexandru Ardelean
2020-02-27 8:27 ` [PATCH v3 1/8] include: fpga: adi-axi-common.h: fixup whitespace tab -> space Alexandru Ardelean
2020-02-27 8:27 ` [PATCH v3 2/8] include: fpga: adi-axi-common.h: add version helper macros Alexandru Ardelean
2020-02-27 8:27 ` [PATCH v3 3/8] iio: buffer-dmaengine: use %zu specifier for sprintf(align) Alexandru Ardelean
2020-02-27 8:27 ` [PATCH v3 4/8] iio: buffer-dmaengine: add dev-managed calls for buffer alloc Alexandru Ardelean
2020-02-27 8:27 ` [PATCH v3 5/8] iio: adc: adi-axi-adc: add support for AXI ADC IP core Alexandru Ardelean
2020-02-27 8:27 ` [PATCH v3 6/8] dt-bindings: iio: adc: add bindings doc for AXI ADC driver Alexandru Ardelean
2020-03-03 16:53 ` Rob Herring
2020-03-04 7:55 ` Ardelean, Alexandru [this message]
2020-03-04 16:18 ` Rob Herring
2020-02-27 8:27 ` [PATCH v3 7/8] iio: adc: ad9467: add support AD9467 ADC Alexandru Ardelean
2020-02-27 8:27 ` [PATCH v3 8/8] dt-bindings: iio: adc: add bindings doc for " Alexandru Ardelean
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=e8075f2fc949b541ccc369bc0cc5d3726ea0a3bf.camel@analog.com \
--to=alexandru.ardelean@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).