From: Peter Rosin <peda@axentia.se>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: Reading ADC that comes from a multiplexer
Date: Wed, 22 Sep 2021 16:28:36 +0200 [thread overview]
Message-ID: <ee5d8cf0-591f-7296-28a8-d78159f5d6a2@axentia.se> (raw)
In-Reply-To: <CAOMZO5DtNkfqFAhFtzA4x+W5eEes_pHNGouX35tNL+8hfpq02g@mail.gmail.com>
On 2021-09-22 16:20, Fabio Estevam wrote:
> Hi Peter,
>
> On Wed, Sep 22, 2021 at 10:41 AM Fabio Estevam <festevam@gmail.com> wrote:
>
>> but still the parent channel cannot be found.
>>
>> So I don't have the DT properly describing the ADC to the mux relationship yet.
>
> It works fine now :-)
>
> The trick was to change it like this:
>
> - stmpe_adc {
> + adc0: stmpe_adc {
> compatible = "st,stmpe-adc";
> /* forbid to use ADC channels 3-0 (touch) */
> st,norequest-mask = <0x0F>;
> + #io-channel-cells = <1>;
> };
> };
>
> Thanks a lot!
>
Nice!
While I don't completely understand that iio-device node in the beaglebone
dts that didn't work for you, it looks like it's just a renumbering thing?
However, your version only remapped 4 channels, and in that case your new
iio-device only had those, i.e. 0-3. But the iio-mux was looking for the
missing channel 4. Maybe that was why that variant didn't work?
So, yeah, copying the exynos4412-p4note was simpler.
Cheers,
Peter
next prev parent reply other threads:[~2021-09-22 14:28 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 [this message]
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
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=ee5d8cf0-591f-7296-28a8-d78159f5d6a2@axentia.se \
--to=peda@axentia.se \
--cc=festevam@gmail.com \
--cc=linux-iio@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.