From: Lars-Peter Clausen <lars@metafoo.de>
To: "Andrew F. Davis" <afd@ti.com>, Jonathan Cameron <jic23@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Question about differential muxing
Date: Mon, 18 Apr 2016 14:17:36 +0200 [thread overview]
Message-ID: <5714D060.2000209@metafoo.de> (raw)
In-Reply-To: <5713D9A7.4060106@ti.com>
On 04/17/2016 08:44 PM, Andrew F. Davis wrote:
[...]
>
> What about for buffered reads, active_scan_mask seems to be sent as bits
> in a 64bit variable, does this then lead to a hard limitation of 64
> channels?
It's a bitmask constructed from an array of 64-bit words. It's only limited
by the memory your system has.
next prev parent reply other threads:[~2016-04-18 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 18:42 Question about differential muxing Andrew F. Davis
2016-04-16 13:18 ` Jonathan Cameron
2016-04-17 18:44 ` Andrew F. Davis
2016-04-18 12:17 ` Lars-Peter Clausen [this message]
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=5714D060.2000209@metafoo.de \
--to=lars@metafoo.de \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).