linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Barry Song <21cnbao@gmail.com>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Towards a IIO in kernel push interface.
Date: Thu, 20 Oct 2011 17:44:45 +0100	[thread overview]
Message-ID: <4EA04FFD.9080708@cam.ac.uk> (raw)

Route plan based on initial messing around today.


This will all be in staging for now as no where
near enough infrastructure is available in the initial
proposed move out of staging. Right now boring though
it is, if anyone has review time please look at those
patches first.

1) We now have basic demux functionality.

2) Need to stop timestamps being special so as to simplify
code paths.

3) Need to support multiple buffers (again - thought they
never really worked before).

4) Bring the inkernel pull interfaces across to staging tree (quick)

5) Create pass through buffer type

6) Interfaces for drivers to instantiate such a pass through.

7) Work out stop and restart for other devices changing the
scan being done.  (fiddly to get right and test).

8) Lots of interface pinning down so clients can query what they
are going to get in response to their channel requests.

So lots of fun to come.  Oh dear.

ps. cc list is drawn from the various threads of the last day or
so that touch on this. 

p.p.s. I'll probably push the demuxer up stream just as soon
as the timestamp issue is sorted as it shouldn't break anything
not explicitly calling it.

                 reply	other threads:[~2011-10-20 16:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4EA04FFD.9080708@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=21cnbao@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=thomas.petazzoni@free-electrons.com \
    /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).