From: Lars-Peter Clausen <lars@metafoo.de>
To: Daniel Baluta <daniel.baluta@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: Add I/Q modifiers
Date: Fri, 22 May 2015 14:36:53 +0200 [thread overview]
Message-ID: <555F22E5.3020600@metafoo.de> (raw)
In-Reply-To: <CAEnQRZBbA95fUm8mhhstWwbqaeLj0H63AwV2MU2TphtqywHM-Q@mail.gmail.com>
On 05/20/2015 12:22 PM, Daniel Baluta wrote:
> On Wed, May 20, 2015 at 10:47 AM, Lars-Peter Clausen <lars@metafoo.de> wrote:
>> On 05/20/2015 07:57 AM, Daniel Baluta wrote:
>>>
>>> On Tue, May 19, 2015 at 7:26 PM, Lars-Peter Clausen <lars@metafoo.de>
>>> wrote:
>>>>
>>>> I/Q modifiers can be used to denote signals which are represented by a
>>>> in-phase and a quadrature component.
>>>>
>>>> The ABI documentation describes the I and Q modifiers for current and
>>>> voltage channels for now as those will be the most likely users.
>>>>
>>>
>>> Hi Lars,
>>>
>>> Is there a driver exposing this ABI?
>>
>>
>> There is a driver. It is not yet upstream though.
>
> In this case we should try to upstream that driver too. Or at least,
> add an example
> entry in our IIO dummy driver.
The driver will go upstream eventually, but there are a quite a few
infrastructure dependencies, both in IIO and other parts of the kernel, that
need to go upstream first. Sometimes it makes sense to split things into
smaller parts and submit those things that are simple and ready rather than
accumulating a patch-bomb of 50+ patches.
>
> It does make any sense to expose an ABI if no one is using it.
I'm using it :)
next prev parent reply other threads:[~2015-05-22 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 16:26 [PATCH] iio: Add I/Q modifiers Lars-Peter Clausen
2015-05-19 17:32 ` Peter Meerwald
2015-05-20 5:57 ` Daniel Baluta
2015-05-20 7:47 ` Lars-Peter Clausen
2015-05-20 10:22 ` Daniel Baluta
2015-05-22 12:36 ` Lars-Peter Clausen [this message]
2015-05-22 12:50 ` Daniel Baluta
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=555F22E5.3020600@metafoo.de \
--to=lars@metafoo.de \
--cc=daniel.baluta@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.