From: "Paller, Kim Seer" <KimSeer.Paller@analog.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "jic23@kernel.org" <jic23@kernel.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzysztof.kozlowski@linaro.org" <krzysztof.kozlowski@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: RE: [PATCH v6 2/2] iio: adc: max14001: New driver
Date: Wed, 14 Jun 2023 10:43:00 +0000 [thread overview]
Message-ID: <a6488485909d40b3810ad15787cd2100@analog.com> (raw)
In-Reply-To: <CAHp75VcTXsZZ4JsKWS0RuccPKRLO9ci+87b538BT9V9ZZ_WACg@mail.gmail.com>
> -----Original Message-----
> From: Andy Shevchenko <andy.shevchenko@gmail.com>
> Sent: Wednesday, June 14, 2023 5:12 PM
> To: Paller, Kim Seer <KimSeer.Paller@analog.com>
> Cc: jic23@kernel.org; lars@metafoo.de; lgirdwood@gmail.com;
> broonie@kernel.org; Hennerich, Michael <Michael.Hennerich@analog.com>;
> robh@kernel.org; krzysztof.kozlowski@linaro.org; conor+dt@kernel.org; linux-
> iio@vger.kernel.org; linux-kernel@vger.kernel.org; devicetree@vger.kernel.org
> Subject: Re: [PATCH v6 2/2] iio: adc: max14001: New driver
>
> [External]
>
> On Wed, Jun 14, 2023 at 3:49 AM Kim Seer Paller
> <kimseer.paller@analog.com> wrote:
> >
> > The MAX14001 is configurable, isolated 10-bit ADCs for multi-range
> > binary inputs.
>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com> One question
> below.
>
> > Signed-off-by: Kim Seer Paller <kimseer.paller@analog.com>
> > ---
...
> > + /* select external voltage reference source for the ADC */
> > + ret = max14001_reg_update(st, MAX14001_CFG,
> > + MAX14001_CFG_EXRF, 1);
> > +
> > + ret = regulator_get_voltage(vref);
> > + if (ret < 0)
> > + return dev_err_probe(dev, ret,
> > + "Failed to get vref\n");
>
> Is it important to choose the external reference source _before_ getting the
> voltage of the regulator? If not, I would swap these calls, otherwise the
> comment is needed to explain why the sequence is important in the way it's
> written.
It is not important. These calls can be swap without any issues.
Best regards,
Kim Seer Paller
next prev parent reply other threads:[~2023-06-14 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 0:48 [PATCH v6 1/2] dt-bindings: iio: adc: add max14001 Kim Seer Paller
2023-06-14 0:48 ` [PATCH v6 2/2] iio: adc: max14001: New driver Kim Seer Paller
2023-06-14 9:11 ` Andy Shevchenko
2023-06-14 10:43 ` Paller, Kim Seer [this message]
2023-06-14 11:53 ` Andy Shevchenko
2023-06-17 18:34 ` Jonathan Cameron
2023-06-17 18:37 ` Jonathan Cameron
2023-06-17 18:30 ` Jonathan Cameron
2023-06-17 18:43 ` Jonathan Cameron
2023-06-14 6:30 ` [PATCH v6 1/2] dt-bindings: iio: adc: add max14001 Krzysztof Kozlowski
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=a6488485909d40b3810ad15787cd2100@analog.com \
--to=kimseer.paller@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--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