All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Reid <preid@electromag.com.au>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: iio: Non multiplexed ADC Data
Date: Mon, 23 Nov 2015 16:31:01 +0800	[thread overview]
Message-ID: <5652CEC5.7080804@electromag.com.au> (raw)

I'm in th eprocess of writing a driver for a custom ADC controller.
It's an FPGA based ADC controller with multiple ADC channels with a built in DMA master.
All channels share some attributes, eg Sample rate, with other per channel attributes, eg Gain.
The DMA controller de-multiplexes the ADC data by having a separate target buffer for each channel.
Look at the libiio interface this configuration doesn't seem to be catered for.
eg: iio_device_create_buffer creates a single buffer for all enabled channels to share.

The best way I can see is to create an iio device per channel and have them share a common data block.
Not sure what interesting behaviour this may cause.

Or have I missed something obvious..

-- 
Regards
Phil Reid


             reply	other threads:[~2015-11-23  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23  8:31 Phil Reid [this message]
2015-11-23  9:15 ` iio: Non multiplexed ADC Data Lars-Peter Clausen
2015-11-24  0:17   ` Phil Reid

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=5652CEC5.7080804@electromag.com.au \
    --to=preid@electromag.com.au \
    --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.