From: "Andrew F. Davis" <afd@ti.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Question about differential muxing
Date: Fri, 15 Apr 2016 13:42:50 -0500 [thread overview]
Message-ID: <5711362A.1020700@ti.com> (raw)
Hello all,
I am currently working on a driver for a part similar to the AFE4300. I
was hoping to get some information on the recommended way to handle a
mux such as the one in the AFE4300 BCM front-end (page 13 of
http://www.ti.com/lit/ds/symlink/afe4300.pdf has a good image).
The top several pins are outputs that can be routed to the OP-AMP, but
only one at a time, because of this I'm not sure if they should be
exposed as output channels, or sysfs switches.
The other issue is with the input pins, I believe the standard way to
handle this is by exposing every mux setting as a separate channel, then
only allowing one bit set in the scan mask, but for this part, when all
differential combinations are exposed we have more than 100 channels,
and the other part I'm working on makes this several times worse.
Could someone point to any information, or an existing driver, that
explains the preferred way to handle this?
Thanks,
Andrew
next reply other threads:[~2016-04-15 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 18:42 Andrew F. Davis [this message]
2016-04-16 13:18 ` Question about differential muxing Jonathan Cameron
2016-04-17 18:44 ` Andrew F. Davis
2016-04-18 12:17 ` Lars-Peter Clausen
2016-04-18 12:05 ` Lars-Peter Clausen
2016-04-18 13:42 ` jic23
2016-04-18 14:25 ` Daniel Baluta
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=5711362A.1020700@ti.com \
--to=afd@ti.com \
--cc=jic23@kernel.org \
--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.