From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Marco Felsch <m.felsch@pengutronix.de>,
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>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] dt-bindings: iio: adc: add missing vref-supply
Date: Fri, 03 Feb 2023 08:03:18 +0100 [thread overview]
Message-ID: <1922814.PYKUYFuaPT@steina-w> (raw)
In-Reply-To: <20230202171052.502ec666@jic23-huawei>
Hi,
Am Donnerstag, 2. Februar 2023, 18:10:52 CET schrieb Jonathan Cameron:
> On Wed, 1 Feb 2023 13:13:43 +0100
>
> Marco Felsch <m.felsch@pengutronix.de> wrote:
> > Hi Alexander,
> >
> > On 23-01-31, Alexander Stein wrote:
> > > Hi Marco,
> > >
> > > thanks for the feedback.
> > >
> > > Am Dienstag, 31. Januar 2023, 11:48:16 CET schrieb Marco Felsch:
> > > > Hi Alexander,
> > > >
> > > > On 23-01-31, Alexander Stein 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>
> > > > > ---
> > > > >
> > > > > .../devicetree/bindings/iio/adc/nxp,imx8qxp-adc.yaml | 4
> > > > > ++++
> > > > > 1 file changed, 4 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..879768af0303 100644
> > > > > --- a/Documentation/devicetree/bindings/iio/adc/nxp,imx8qxp-adc.yaml
> > > > > +++ b/Documentation/devicetree/bindings/iio/adc/nxp,imx8qxp-adc.yaml
> > > > >
> > > > > @@ -39,6 +39,9 @@ properties:
> > > > > power-domains:
> > > > > maxItems: 1
> > > > >
> > > > > + vref-supply:
> > > > > + description: External ADC reference voltage supply on VREFH
> > > > > pad.
> > > >
> > > > Please add it to the list of required properties, we can remove it as
> > > > soon as the driver has support for the internal reference voltages.
> > >
> > > I was thinking in doing so before as well. But DT describes the
> > > hardware, and this ADC apparently would be functioning without a
> > > reference voltage on that pad, using a different one. What the driver
> > > actual does is a different matter.>
> > I have also thought about it first but than I checked the RM which says
> > that "multi-reference selection" is chip dependent.
Nice for pointing this out. I wasn't aware that there are differences.
> Oh goody. So is it detectable?
That's my problem. I didn't find any source of information which chips do
support multiple references and which don't.
Marco, do you have some information on this?
> If we are going to stick to a single compatible rather than adding them for
> the variants with and without this feature, should probably add a note at
> least to say it is required for some parts.
That's a good idea. I'm okay with that, until there is more information
available.
Best regards
Alexander
> Also, link if public would be good for purposes of discussion as my google
> fu didn't find relevant doc. (assuming it's public)
>
>
> Jonathan
>
> > Regards,
> >
> > Marco
> >
> > > Best regards,
> > > Alexander
> > >
> > > > Regards,
> > > >
> > > > Marco
> > > >
> > > > > +
> > > > >
> > > > > "#io-channel-cells":
> > > > > const: 1
> > > > >
> > > > > @@ -72,6 +75,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>;
> > > > >
> > > > > };
> > > > >
> > > > > };
next prev parent reply other threads:[~2023-02-03 7:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 10:13 [PATCH 1/1] dt-bindings: iio: adc: add missing vref-supply Alexander Stein
2023-01-31 10:48 ` Marco Felsch
2023-01-31 12:14 ` Alexander Stein
2023-02-01 12:13 ` Marco Felsch
2023-02-02 17:10 ` Jonathan Cameron
2023-02-03 7:03 ` Alexander Stein [this message]
2023-02-03 14:12 ` Marco Felsch
2023-02-03 14:20 ` Alexander Stein
2023-02-04 0:13 ` Marco Felsch
2023-02-06 11:54 ` Alexander Stein
2023-01-31 12:16 ` Fabio Estevam
2023-01-31 13:20 ` Alexander Stein
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=1922814.PYKUYFuaPT@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).