linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 3/3] iio: Require strict scan mask matching in hardware mode
Date: Sat, 06 Jun 2015 22:07:12 +0100	[thread overview]
Message-ID: <55736100.9090408@kernel.org> (raw)
In-Reply-To: <556F3720.80504@metafoo.de>



On 06/03/2015 06:19 PM, Lars-Peter Clausen wrote:
> On 06/01/2015 12:34 PM, Jonathan Cameron wrote:
>> On 29/05/15 17:14, Lars-Peter Clausen wrote:
>>> In hardware mode we can not use the software demuxer, this means that
>>> the
>>> selected scan mask needs to match one of the available scan masks
>>> exactly.
>>>
>>> It also means that all attached buffers need to use the same scan mask.
>>> Given that when operating in hardware mode there is typically only a
>>> single
>>> buffer attached to the device this not an issue. Add a sanity check
>>> to make
>>> sure that only a single buffer is attached in hardware mode
>>> nevertheless.
>>>
>> That pretty much sums up why devices supporting only hardware buffers
>> are probably not going to be a long term feature!
>> Mind you for fast devices we may want to allow forced bypassing of the
>> demux (i.e. a hardware buffer).
>>
>> Out of curiosity is this series a precursor to another hardware buffered
>> device or just a useful intellectual exercise?
>
> It's all for real hardware and I'm already using it in some projects.
> E.g. one thing I'm working on is adding optional DMA support for some of
> the converters, if DMA is available it will use hardware mode. If no DMA
> is available or the consumer wants to run in software triggered mode
> fallback to software triggered mode.
Cool.  Looking forward to seeing the use cases!
>
> - Lars
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2015-06-06 20:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 16:14 [PATCH 0/3] iio: Hardware buffer improvements Lars-Peter Clausen
2015-05-29 16:14 ` [PATCH 1/3] iio: Always compute masklength Lars-Peter Clausen
2015-06-01 10:28   ` Jonathan Cameron
2015-05-29 16:14 ` [PATCH 2/3] iio: Specify supported modes for buffers Lars-Peter Clausen
2015-06-01 10:31   ` Jonathan Cameron
2016-01-01 17:50   ` Jonathan Cameron
2015-05-29 16:14 ` [PATCH 3/3] iio: Require strict scan mask matching in hardware mode Lars-Peter Clausen
2015-06-01 10:34   ` Jonathan Cameron
2015-06-03 17:19     ` Lars-Peter Clausen
2015-06-06 21:07       ` Jonathan Cameron [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=55736100.9090408@kernel.org \
    --to=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).