linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Rubini <rubini@gnudd.com>
To: jic23@kernel.org
Cc: linux-iio@vger.kernel.org, greg@kroah.com,
	linux-kernel@vger.kernel.org, federico.vaga@gmail.com,
	dcobas@cern.ch, siglesia@cern.ch, manohar.vanga@cern.ch
Subject: Re: [RFC PATCH 1/7] Documentation: add docs for drivers/zio
Date: Sat, 26 Nov 2011 23:53:32 +0100	[thread overview]
Message-ID: <20111126225332.GA17001@mail.gnudd.com> (raw)
In-Reply-To: <4ED1654D.8020702@kernel.org>

zio readme:
>> +    Ctrl: version 0.2, trigger timer, dev zzero, cset 0, chan 2
>> +    Ctrl: seq 102, n 4, size 1, bits 8, flags 01000001 (little-endian)
>> +    Ctrl: stamp 4066.519285605 (0)
>> +    Data: 60 61 62 63

Jonathan  Cameron:
> Interesting approach to meta data handling.  It's kind of 'partly' out
> of band as it can apply to large chunks of data.

Exactly. Then, you can ignore the metadata if you want. It's like
having a line of packed food, with detailed labels. You can read the
label before getting each content blob, or just read the blob and
discard the label.  Or you can pass everything to someone else, for
off-line handling.

We are aware there is a serious overhead if blocks are small, but the
use case is different, as said.

> How does it map if you have triggers causing single captures from each
> channel?  I would imagine you will then store a whole meta data set per
> sample?

Yes. Worse: csets are acquired (or output) concurrently, so there's
one control structure per channel (actually, gain and offset may be
different in each channel, so there's a reason).

But when blocks are acquired by a hardware card with 256MB of internal
memory and then transferred in a single DMA burst for offline
analysis, then the overhead is negligible and I see an advantage in
simplicity.

Actually, we are considering a buffer that reassembles samples,
returning bigger blocks on demand, so we get rid of some of the
overhead.  But that's more a stress-test for the buffer concept than
for real use cases.

Sure we lack any in-kernel users and don't want to have them in the
future, that's helping us a lot.

> I know this isn't your use case, but I'm currious to see where
> the overlap lies between this and IIO as you can imagine!

Yes, we are too. Federico has an ad7888 driver working, both for IIO
and ZIO (and Comedi, but that's out of the game already), and we are
going to write for a few more IIO-supported devices. In this way we
both validate (or not) our design and compare with IIO.

Thank you for your feedback, both here and in the off-list email.

/alessandro

  parent reply	other threads:[~2011-11-26 23:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26 17:30 [RFC PATCH 0/7] Introducing ZIO, a new I/O framework Alessandro Rubini
2011-11-26 17:30 ` [RFC PATCH 1/7] Documentation: add docs for drivers/zio Alessandro Rubini
2011-11-26 20:00   ` Greg KH
2011-11-26 21:48     ` Federico Vaga
2011-11-26 22:16   ` Jonathan Cameron
2011-11-26 22:53   ` Alessandro Rubini [this message]
2011-12-06  5:12   ` Randy Dunlap
2011-11-26 17:30 ` [RFC PATCH 2/7] include/linux: add headers " Alessandro Rubini
2011-11-26 20:02   ` Greg KH
2011-11-26 21:46     ` Federico Vaga
2011-11-27  9:32       ` Greg KH
2011-11-28 14:56         ` Federico Vaga
2011-11-30  6:21           ` Greg KH
2011-11-26 17:30 ` [RFC PATCH 3/7] drivers/zio: core files for the ZIO input/output Alessandro Rubini
2011-11-26 20:03   ` Greg KH
2011-11-26 22:58     ` Federico Vaga
2011-11-27  9:33       ` Greg KH
2011-11-28 14:59         ` Federico Vaga
2011-11-26 17:30 ` [RFC PATCH 4/7] drivers/zio: add triggers and buffers Alessandro Rubini
2011-11-26 17:31 ` [RFC PATCH 5/7] drivers/zio: add the zio-zero device driver Alessandro Rubini
2011-11-26 17:31 ` [RFC PATCH 6/7] drivers/zio: add user-space tool zio-dump Alessandro Rubini
2011-11-26 17:31 ` [RFC PATCH 7/7] zio: insert in Kbuild so it is actually compiled Alessandro Rubini
2011-11-26 18:09 ` [RFC PATCH 0/7] Introducing ZIO, a new I/O framework Lars-Peter Clausen
2011-11-26 19:11 ` Alessandro Rubini
2011-12-01 21:41   ` Linus Walleij

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=20111126225332.GA17001@mail.gnudd.com \
    --to=rubini@gnudd.com \
    --cc=dcobas@cern.ch \
    --cc=federico.vaga@gmail.com \
    --cc=greg@kroah.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manohar.vanga@cern.ch \
    --cc=siglesia@cern.ch \
    /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).