From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Cai Huoqing <cai.huoqing@linux.dev>,
Haibo Chen <haibo.chen@nxp.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Marco Felsch <m.felsch@pengutronix.de>
Subject: Re: [PATCH v2 1/1] dt-bindings: iio: imx8qxp-adc: add missing vref-supply
Date: Tue, 02 May 2023 08:34:12 +0200 [thread overview]
Message-ID: <5671528.DvuYhMxLoT@steina-w> (raw)
In-Reply-To: <20230430181558.7614cbfc@jic23-huawei>
Am Sonntag, 30. April 2023, 19:15:58 CEST schrieb Jonathan Cameron:
> On Mon, 24 Apr 2023 11:23:12 +0200
>
> Alexander Stein <alexander.stein@ew.tq-group.com> wrote:
> > Although this property is used right now for IIO_CHAN_INFO_SCALE,
> > this ADC has two internal reference voltages, which the driver currently
> > doesn't make use of.
> >
> > Fixes: db73419d8c06 ("dt-bindings: iio: adc: Add binding documentation for
> > NXP IMX8QXP ADC") Signed-off-by: Alexander Stein
> > <alexander.stein@ew.tq-group.com>
>
> Interesting that we are talking her only about vrefh, what about vrefp?
> I guess the assumption is that will be wired to 0V?
What's vrefp? The only other signal related to ADC is vrefl.
> The first reference I found didn't seem to imply that was necessarily the
> case. https://www.mouser.com/pdfDocs/IMX8QXPAEC.pdf
Assuming you are talking about vrefh and vrefl, how is this a problem? Even if
vrefl is not 0V, the voltage difference is what the ADC uses as reference
voltage, so this should be supplied in the DT then.
Best regards
Alexander
> Jonathan
>
> > ---
> > Thanks for your inputs. This improved descritpion should make it clear
> > that this property is only about the external reference voltage, not
> > about the optional, internal voltages.
> >
> > Changes in v2:
> > * Improved commit message subject as suggested
> > * Add hint about feature flag regarding multiple, internal, reference
> >
> > voltages
> >
> > .../devicetree/bindings/iio/adc/nxp,imx8qxp-adc.yaml | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/iio/adc/nxp,imx8qxp-adc.yaml
> > b/Documentation/devicetree/bindings/iio/adc/nxp,imx8qxp-adc.yaml index
> > 63369ba388e4..878e67054d7c 100644
> > --- a/Documentation/devicetree/bindings/iio/adc/nxp,imx8qxp-adc.yaml
> > +++ b/Documentation/devicetree/bindings/iio/adc/nxp,imx8qxp-adc.yaml
> >
> > @@ -39,6 +39,12 @@ properties:
> > power-domains:
> > maxItems: 1
> >
> > + vref-supply:
> > + description: |
> > + External ADC reference voltage supply on VREFH pad. If VERID[MVI]
> > is
> > + set, there are additional, internal reference voltages selectable.
> > + VREFH1 is always from VREFH pad.
> > +
> >
> > "#io-channel-cells":
> > const: 1
> >
> > @@ -72,6 +78,7 @@ examples:
> > assigned-clocks = <&clk IMX_SC_R_ADC_0>;
> > assigned-clock-rates = <24000000>;
> > power-domains = <&pd IMX_SC_R_ADC_0>;
> >
> > + vref-supply = <®_1v8>;
> >
> > #io-channel-cells = <1>;
> >
> > };
> >
> > };
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2023-05-02 6:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 9:23 [PATCH v2 1/1] dt-bindings: iio: imx8qxp-adc: add missing vref-supply Alexander Stein
2023-04-24 10:09 ` Krzysztof Kozlowski
2023-04-25 3:29 ` Bough Chen
2023-04-30 17:15 ` Jonathan Cameron
2023-05-02 6:34 ` Alexander Stein [this message]
2023-05-07 14:00 ` 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=5671528.DvuYhMxLoT@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=cai.huoqing@linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=m.felsch@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).