LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org> To: Andy Shevchenko <andy.shevchenko@gmail.com> Cc: "Liam Beguin" <liambeguin@gmail.com>, "Lars-Peter Clausen" <lars@metafoo.de>, "Michael Hennerich" <Michael.Hennerich@analog.com>, "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: Sun, 29 Aug 2021 15:35:39 +0100 [thread overview] Message-ID: <20210829153539.3b2cf037@jic23-huawei> (raw) In-Reply-To: <CAHp75VcUhgpxUE4h3YgYaGAsvHstBzSo9QDwe+D4t264uj_21A@mail.gmail.com> On Mon, 16 Aug 2021 16:12:58 +0300 Andy Shevchenko <andy.shevchenko@gmail.com> wrote: > On Mon, Aug 16, 2021 at 4:07 PM Liam Beguin <liambeguin@gmail.com> wrote: > > On Mon Aug 16, 2021 at 8:48 AM EDT, Andy Shevchenko wrote: > > > On Mon, Aug 16, 2021 at 3:39 PM Liam Beguin <liambeguin@gmail.com> > > > wrote: > > > > 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: > > ... > > > > > > > + 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. > > > > > > Don't assign and don't check the error code of the API. As simply as > > > that. > > > > I'm not against getting rid of it, but I was asked to check for these > > errors in earlier revisions of the patch. > > Okay, I leave it to you, guys, to decide, just note that the usual > pattern for optional stuff > a) either check for (!ret); > b) or ignore the returned value completely. Hmm. My thinking (I suspect I asked for it to be checked, but can't remember :) was that I'd really like to know if a device tree contains a property but that property is invalid for some reason. The docs give a bunch of reasons beyond the property not existing (which is unhelpfully described as just 'invalid parameters'). I guess that's a bit far fetched. Let's drop the check as Andy suggests. Dropped that check and applied to the togreg branch of iio.git, initially pushed out as testing for 0-day to poke at it. + we are about to enter merge window so I don't want linux-next to pick it up just yet! Jonathan > > > > > > > + dev_err(dev, "invalid value for adi,internal-ref-microvolt\n"); > > > > > > + return ret; > > > > > > + } > >
next prev parent reply other threads:[~2021-08-29 14:32 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 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 [this message] 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=20210829153539.3b2cf037@jic23-huawei \ --to=jic23@kernel.org \ --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=lars@metafoo.de \ --cc=liambeguin@gmail.com \ --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: linkBe 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).