From: Jonathan Cameron <jic23@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Tomas Novotny <tomas@novotny.cz>,
devicetree@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] dt-bindings:iio:dac:microchip,mcp4725: fix properties for mcp4726
Date: Tue, 29 Dec 2020 17:46:40 +0000 [thread overview]
Message-ID: <20201229174640.11079e45@archlinux> (raw)
In-Reply-To: <20201221192738.GA407457@robh.at.kernel.org>
On Mon, 21 Dec 2020 12:27:38 -0700
Rob Herring <robh@kernel.org> wrote:
> On Wed, 16 Dec 2020 11:13:16 +0100, Tomas Novotny wrote:
> > The vdd-supply property is optional if vref-supply is provided for
> > mcp4726.
> >
> > Also the microchip,vref-buffered makes sense only if vref-supply is
> > specified.
> >
> > Spotted by Jonathan during conversion to yaml.
> >
> > Reported-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > Signed-off-by: Tomas Novotny <tomas@novotny.cz>
I'm taking this this slow way as we are just providing slightly more flexible
conditions rather than allowing anything we suspect anyone is already using.
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to probably ignore it ;)
Thanks for tidying this up.
Jonathan
> > ---
> > .../bindings/iio/dac/microchip,mcp4725.yaml | 31 +++++++++++++++----
> > 1 file changed, 25 insertions(+), 6 deletions(-)
> >
>
> Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2020-12-29 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 10:13 [PATCH] dt-bindings:iio:dac:microchip,mcp4725: fix properties for mcp4726 Tomas Novotny
2020-12-21 19:27 ` Rob Herring
2020-12-29 17:46 ` Jonathan Cameron [this message]
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=20201229174640.11079e45@archlinux \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tomas@novotny.cz \
/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).