linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Pavel Roskin <plroskin@gmail.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: Best practices for sending digital data
Date: Thu, 8 Feb 2018 18:51:52 +0100	[thread overview]
Message-ID: <df0652c1-80cf-bf69-252d-0859a7cff7c8@metafoo.de> (raw)
In-Reply-To: <20180208101837.00001c55@huawei.com>

On 02/08/2018 11:18 AM, Jonathan Cameron wrote:
> On Wed, 7 Feb 2018 14:15:30 -0800
> Pavel Roskin <plroskin@gmail.com> wrote:>>
>> I understand that the IIO layer tries to be helpful with
>> standardization, but I believe it's too restrictive.
>>
> So the question is what is the alternative to adding new channel types
> when they are needed?
> 
[...]
> 2) We add magic 'user defined types'.  The problem then is that
>    the primary purpose of not just throwing all the drivers in with
>    their own interfaces is gone.  There is no standardization at all and
>    every device needs it's own userspace code.

Just want to add that this is a 'misc' device and this option is still on
the table. If you think the standard IIO ABI is too restrictive and you'd
rather have a device specific ABI you can write a misc driver for your
device. Or directly write a userspace driver.

The preferred solution of course is to work with the IIO framework and come
up with solutions for the shortcomings.

  reply	other threads:[~2018-02-08 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 22:15 Best practices for sending digital data Pavel Roskin
2018-02-08 10:18 ` Jonathan Cameron
2018-02-08 17:51   ` Lars-Peter Clausen [this message]
2018-02-10 15:51     ` Jonathan Cameron

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=df0652c1-80cf-bf69-252d-0859a7cff7c8@metafoo.de \
    --to=lars@metafoo.de \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=plroskin@gmail.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).