From: "Liam Beguin" <liambeguin@gmail.com>
To: "Andy Shevchenko" <andy.shevchenko@gmail.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Charles-Antoine Couret" <charles-antoine.couret@essensium.com>,
"Nuno Sá" <Nuno.Sa@analog.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-iio <linux-iio@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>
Subject: Re: [PATCH v6 3/5] iio: adc: ad7949: add vref selection support
Date: Mon, 16 Aug 2021 08:39:30 -0400 [thread overview]
Message-ID: <CDKXZBW1JDOD.1ZXIT12Y3WK5B@shaak> (raw)
In-Reply-To: <CAHp75Vd-AfmwMyYyy5ygwmvGfwZLh9VwvBEzSwW3fc99jxFpnQ@mail.gmail.com>
On Mon Aug 16, 2021 at 4:04 AM EDT, Andy Shevchenko wrote:
> On Mon, Aug 16, 2021 at 12:35 AM Liam Beguin <liambeguin@gmail.com>
> wrote:
> >
> > From: Liam Beguin <lvb@xiphos.com>
> >
> > Add support for selecting the voltage reference from the devicetree.
> >
> > This change is required to get valid readings with all three
> > vref hardware configurations supported by the ADC.
> >
> > For instance if the ADC isn't provided with an external reference,
> > the sample request must specify an internal voltage reference to get a
> > valid reading.
>
> ...
>
> > + /* Setup internal voltage reference */
> > + tmp = 4096000;
> > + ret = device_property_read_u32(dev, "adi,internal-ref-microvolt", &tmp);
>
> > + if (ret < 0 && ret != -EINVAL) {
Hi Andy,
>
> What does this check (second part) is supposed to mean?
> The first part will make it mandatory, is it the goal?
>
device_property_read_u32() will return -EINVAL if the property isn't
found in the devicetree.
This checks for errors when the property is defined while keeping it
optional.
Liam
> > + dev_err(dev, "invalid value for adi,internal-ref-microvolt\n");
> > + return ret;
> > + }
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2021-08-16 12:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 21:33 [PATCH v6 0/5] AD7949 Fixes Liam Beguin
2021-08-15 21:33 ` [PATCH v6 1/5] iio: adc: ad7949: define and use bitfield names Liam Beguin
2021-08-15 21:33 ` [PATCH v6 2/5] iio: adc: ad7949: fix spi messages on non 14-bit controllers Liam Beguin
2021-08-29 14:33 ` Jonathan Cameron
2021-08-29 16:43 ` Liam Beguin
2021-08-15 21:33 ` [PATCH v6 3/5] iio: adc: ad7949: add vref selection support Liam Beguin
2021-08-16 8:04 ` Andy Shevchenko
2021-08-16 12:39 ` Liam Beguin [this message]
2021-08-16 12:48 ` Andy Shevchenko
2021-08-16 13:07 ` Liam Beguin
2021-08-16 13:12 ` Andy Shevchenko
2021-08-29 14:35 ` Jonathan Cameron
2021-08-29 16:40 ` Liam Beguin
2021-08-15 21:33 ` [PATCH v6 4/5] dt-bindings: iio: adc: ad7949: update voltage reference bindings Liam Beguin
2021-08-17 22:16 ` Rob Herring
2021-08-15 21:33 ` [PATCH v6 5/5] iio: adc: ad7949: use devm managed functions Liam Beguin
2021-08-16 8:08 ` [PATCH v6 0/5] AD7949 Fixes Andy Shevchenko
2021-08-16 12:59 ` Liam Beguin
2021-08-29 14:38 ` 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=CDKXZBW1JDOD.1ZXIT12Y3WK5B@shaak \
--to=liambeguin@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=Nuno.Sa@analog.com \
--cc=andy.shevchenko@gmail.com \
--cc=charles-antoine.couret@essensium.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.