All of lore.kernel.org
 help / color / mirror / Atom feed
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 14:44:45 +0200	[thread overview]
Message-ID: <799fc96d-b09f-be3b-9c7c-8e1365f3afb2@axentia.se> (raw)
In-Reply-To: <CAOMZO5Bhs3qLwgqGYHO7Oswr1qvarkzmNFyWQi3-_geZTj3BVA@mail.gmail.com>

On 2021-09-22 13:37, Fabio Estevam wrote:
> Hi Peter,
> 
> On Wed, Sep 22, 2021 at 4:27 AM Peter Rosin <peda@axentia.se> wrote:
> 
>> Basically, the whole point is that you simply don't. The iio-mux exposes
>> the channels as 8 new ADCs, and whenever you read a value from one of
>> them, the iio-mux operates the gpios for you, giving you the impression
>> that you have 8 independet ADCs. They are of course not independent, but...
> 
> Thanks for the clarification. It was helpful.
> 
>> That's exposed to user-space as:
>>
>> $ ls "/sys/bus/iio/devices/iio:device3"
>> in_altvoltage2_compare_interval  in_altvoltage5_scale
>> in_altvoltage2_invert            in_altvoltage6_compare_interval
>> in_altvoltage2_raw               in_altvoltage6_invert
>> in_altvoltage2_scale             in_altvoltage6_raw
>> in_altvoltage3_compare_interval  in_altvoltage6_scale
>> in_altvoltage3_invert            in_altvoltage7_compare_interval
>> in_altvoltage3_raw               in_altvoltage7_invert
>> in_altvoltage3_scale             in_altvoltage7_raw
>> in_altvoltage4_compare_interval  in_altvoltage7_scale
>> in_altvoltage4_invert            name
>> in_altvoltage4_raw               of_node
>> in_altvoltage4_scale             power
>> in_altvoltage5_compare_interval  subsystem
>> in_altvoltage5_invert            uevent
>> in_altvoltage5_raw
>> $ cat "/sys/bus/iio/devices/iio:device3/name"
>> envelope-detector-mux
> 
> Ah, so that's my issue then. I don't see a new device inside
> /sys/bus/iio/devices/.
> 
> I only see the original stmpe ADC:
> 
> ls "/sys/bus/iio/devices/iio:device0"
> dev              in_voltage5_raw  in_voltage_scale  power
> in_temp8_input   in_voltage6_raw  name              subsystem
> in_voltage4_raw  in_voltage7_raw  of_node           uevent
> 
> Maybe my dts is not correct to make the mux appear under
> /sys/bus/iio/devices/iio:device1.
> 
> Here is my dts that shows more context with the STMPE811 ADC:
> https://pastebin.com/raw/7Nn2aAtN
> 
> stmpe811 is an mfd device that can be used as a touchscreen and as a normal adc.
> 
> I only use the adc functionality.
> 
> Any suggestions are welcome.

Don't you get any output from the iio-mux driver during probe? I'd expect
a "failed to get parent channel" or something like that?

I don't know, but looking around a bit makes me think you should
investigate /arch/arm/boot/dts/am5729-beagleboneai.dts and/or
/arch/arm/boot/dts/exynos4412-p4note.dtsi.

I think you need to move the adc: label in the dts to the stmpe_adc child
node, or something like that?

Cheers,
Peter

      parent reply	other threads:[~2021-09-22 12:44 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
2021-09-22 12:44     ` Peter Rosin [this message]

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=799fc96d-b09f-be3b-9c7c-8e1365f3afb2@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.