Linux IIO development
 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:53:35 +0200	[thread overview]
Message-ID: <73d0ede5-8a35-7e3e-e685-235f39ea28e7@axentia.se> (raw)
In-Reply-To: <CAOMZO5A0a20_+JHmCMYXLuZYCE04GDTqt0x_GXtVxA5Q4MSAog@mail.gmail.com>

On 2021-09-22 14:44, Fabio Estevam wrote:
> Just realized that iio-mux.c does not get probed.
> 
> In mux_probe():
> 
> parent = devm_iio_channel_get(dev, "parent");
> 
> is always returning -EPROBE_DEFER, even though I passed:
> 
>         io-channel-names = "parent";
> 

I think that's because the "parent" channel (i.e. <&adc 4> in your case)
is referring to a node that is not providing any iio channels at all.

Just because you added "#io-channel-cells = <1>;" to that node, does not
make it so. The driver has to support it as well.

Cheers,
Peter

  reply	other threads:[~2021-09-22 12:53 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 [this message]
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

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=73d0ede5-8a35-7e3e-e685-235f39ea28e7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox