From: Jonathan Cameron <jic23@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Peter Rosin <peda@axentia.se>,
linux-iio@vger.kernel.org
Subject: Re: Reading ADC that comes from a multiplexer
Date: Sat, 25 Sep 2021 15:32:51 +0100 [thread overview]
Message-ID: <20210925153251.20776333@jic23-huawei> (raw)
In-Reply-To: <CAOMZO5D1gt6tFhHzTALGFAs8Zt3aBbanw0Sz93AmWHwcnCvHSQ@mail.gmail.com>
On Fri, 24 Sep 2021 11:41:38 -0300
Fabio Estevam <festevam@gmail.com> wrote:
> Hi Jonathan,
>
> On Thu, Sep 23, 2021 at 7:29 AM Jonathan Cameron
> <Jonathan.Cameron@huawei.com> wrote:
>
> > > The beaglebone dts uses some undocumented properties such as:
> > > iio-channels and iio-channel-names.
> >
> > Some of this comes from the dts-schema repo. We haven't been strict in
> > adding the entries to individual ADCs until they actually use them - which
> > has the advantage it gives us a window to think about the of_xlate (see below)
> >
> > https://github.com/devicetree-org/dt-schema/blob/main/meta-schemas/iio.yaml
>
> On this document, we have "io-channels" and "io-channel-names.
>
> What I wanted to say is that in
> arch/arm/boot/dts/am5729-beagleboneai.dts we have:
>
> "iio-channels" and "iio-channel-names" (Note the 'iio' versus 'io').
>
> This is what I mentioned as undocumented properties.
>
> Maybe I can send a patch fixing it.
Ah! Got you. That definitely seems wrong so a fix would be welcome.
Thanks,
Jonathan
>
> On my imx6 board all is working fine now.
>
> Thanks,
>
> Fabio Estevam
next prev parent reply other threads:[~2021-09-25 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 2:18 Reading ADC that comes from a multiplexer Fabio Estevam
2021-09-22 7:27 ` Peter Rosin
2021-09-22 11:37 ` Fabio Estevam
2021-09-22 12:44 ` Fabio Estevam
2021-09-22 12:53 ` Peter Rosin
2021-09-22 13:41 ` Fabio Estevam
2021-09-22 14:20 ` Fabio Estevam
2021-09-22 14:28 ` Peter Rosin
2021-09-22 14:50 ` Fabio Estevam
2021-09-23 10:28 ` Jonathan Cameron
2021-09-24 14:41 ` Fabio Estevam
2021-09-25 14:32 ` Jonathan Cameron [this message]
2021-09-22 12:44 ` Peter Rosin
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=20210925153251.20776333@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=festevam@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=peda@axentia.se \
/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