From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Antoniu Miclaus <antoniu.miclaus@analog.com>,
robh+dt@kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v8 2/4] dt-bindings:iio:frequency: add admv1014 binding
Date: Sun, 20 Feb 2022 17:39:55 +0000 [thread overview]
Message-ID: <20220220173955.7e9804ae@jic23-huawei> (raw)
In-Reply-To: <c7e39902-c85a-c601-8b9c-b2292ffeb46d@canonical.com>
On Sun, 20 Feb 2022 13:16:41 +0100
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com> wrote:
> On 15/02/2022 09:12, Antoniu Miclaus wrote:
> > Add device tree bindings for the ADMV1014 Upconverter.
> >
> > Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> > Reviewed-by: Rob Herring <robh@kernel.org>
>
> Your subject seems still wrongly formatted.
> > ---
> > changes in v8:
> > - remove `clock-cells`
> > - rename device node to be more generic
> > - set 'maxItems' for clocks property
> > .../bindings/iio/frequency/adi,admv1014.yaml | 134 ++++++++++++++++++
> > 1 file changed, 134 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/iio/frequency/adi,admv1014.yaml
> >
> > diff --git a/Documentation/d
>
> (...)
>
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + spi {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + converter@0{
>
> Missing space after address... I thought you will correct it while
> changing node name.
Fixed up.
>
>
> > + compatible = "adi,admv1014";
> > + reg = <0>;
> > + spi-max-frequency = <1000000>;
> > + clocks = <&admv1014_lo>;
> > + clock-names = "lo_in";
> > + vcm-supply = <&vcm>;
> > + vcc-if-bb-supply = <&vcc_if_bb>;
> > + vcc-vga-supply = <&vcc_vga>;
> > + vcc-vva-supply = <&vcc_vva>;
> > + vcc-lna-3p3-supply = <&vcc_lna_3p3>;
> > + vcc-lna-1p5-supply = <&vcc_lna_1p5>;
> > + vcc-bg-supply = <&vcc_bg>;
> > + vcc-quad-supply = <&vcc_quad>;
> > + vcc-mixer-supply = <&vcc_mixer>;
> > + adi,quad-se-mode = "diff";
> > + adi,detector-enable;
> > + adi,p1db-compensation-enable;
> > + };
> > + };
> > +...
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2022-02-20 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 8:12 [PATCH v8 1/4] iio:frequency:admv1014: add support for ADMV1014 Antoniu Miclaus
2022-02-15 8:12 ` [PATCH v8 2/4] dt-bindings:iio:frequency: add admv1014 binding Antoniu Miclaus
2022-02-20 12:16 ` Krzysztof Kozlowski
2022-02-20 17:39 ` Jonathan Cameron [this message]
2022-02-15 8:12 ` [PATCH v8 3/4] Documentation:ABI:testing:admv1014: add ABI docs Antoniu Miclaus
2022-02-15 8:12 ` [PATCH v8 4/4] MAINTAINERS: add maintainer for ADMV1014 driver Antoniu Miclaus
2022-02-20 12:14 ` [PATCH v8 1/4] iio:frequency:admv1014: add support for ADMV1014 Jonathan Cameron
2022-03-25 11:57 ` Andy Shevchenko
2022-03-27 16:04 ` 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=20220220173955.7e9804ae@jic23-huawei \
--to=jic23@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).