From: Lars-Peter Clausen <lars@metafoo.de>
To: Phil Reid <preid@electromag.com.au>, linux-iio@vger.kernel.org
Subject: Re: IIO and high speed
Date: Thu, 17 Dec 2015 15:45:19 +0100 [thread overview]
Message-ID: <5672CA7F.1030707@metafoo.de> (raw)
In-Reply-To: <5670E151.7000909@electromag.com.au>
On 12/16/2015 04:58 AM, Phil Reid wrote:
> G'day All,
>
> I'm just enquiring what the status / plans are for the IIO high speed
> interface.
>
> This code is present in libiio to do zero copy operations using IIO_BLOCK*
> ioctls.
> EG: I get a warning when running iio_readdev about high speed not being
> enabled.
>
> However corresponding code is not in the mainline kernel, I did find
> something at:
> https://github.com/analogdevicesinc/linux.git
>
> Or has this line of development been discontinued in favour of another plan.
> It looks to be a few years old.
Phase 1, which is DMA buffer support, of the high-speed support was merged
recently. Phase 2, which is mmap and IOCTL support, will follow soon-ish. It
will see some rework first though, support for multiple data planes,
metadata buffers, etc.
- Lars
prev parent reply other threads:[~2015-12-17 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 3:58 IIO and high speed Phil Reid
2015-12-17 14:45 ` Lars-Peter Clausen [this message]
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=5672CA7F.1030707@metafoo.de \
--to=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=preid@electromag.com.au \
/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