From: Lars-Peter Clausen <lars@metafoo.de>
To: Roland Stigge <stigge@antcom.de>
Cc: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/3] staging:iio:dac:max517: Convert to channel spec
Date: Sun, 13 May 2012 09:25:03 +0200 [thread overview]
Message-ID: <4FAF61CF.6070509@metafoo.de> (raw)
In-Reply-To: <4FAED9AD.4020803@antcom.de>
On 05/12/2012 11:44 PM, Roland Stigge wrote:
> Hi,
>
> On 12/05/12 20:51, Jonathan Cameron wrote:
>> On 05/11/2012 06:04 PM, Lars-Peter Clausen wrote:
>>> Convert the max517 driver to channel spec. As part of the conversion the
>>> "out_voltage_1&2_raw" property, which updates both channel 1 and 2
>>> simultaneously with the same value, is lost, since this is not really covered by
>>> the IIO spec.
>> We'll have to introduce a buffered option for output at somepoint to
>> cover the equivalent of that out_voltage_1&2_raw attribute.
>>
>> Roland, how vital was that to you?
>
> I'm generally fine with the proposed changes and can ack it. However, we
> should provide a replacement for the old "1&2" attribute. It supports a
> certain hardware feature of this chip. No need to sacrifice it.
I don't think it makes sense to keep it in it's current form. First of all this
isn't really covered by the IIO spec to have one attribute which changes two
(or more) output at once and secondly it is artificially limited to setting the
same value on both outputs, while the chip doesn't have this limitations and
you can set different values on both outputs at once. So I'm not so sure how
useful it even is in it's current form.
The proper solution for this is to implement buffered support for output
devices and I do have some experimental code for that. But I'd like to move the
DACs out of staging. And this driver is sort of the main blocker right now. If
you insist on keeping the "1&2" attribute, I guess it's best to just leave the
max517 in staging for now, while we move the other DAC drivers out.
- Lars
next prev parent reply other threads:[~2012-05-13 7:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 17:04 [PATCH 1/3] staging:iio:dac: Remove unused dac.h includes Lars-Peter Clausen
2012-05-11 17:04 ` [PATCH 2/3] staging:iio:dac:max517: Convert to channel spec Lars-Peter Clausen
2012-05-12 18:51 ` Jonathan Cameron
2012-05-12 21:44 ` Roland Stigge
2012-05-13 7:25 ` Lars-Peter Clausen [this message]
2012-05-13 9:06 ` Roland Stigge
2012-05-13 9:20 ` Lars-Peter Clausen
2012-05-13 9:41 ` Roland Stigge
2012-05-13 15:03 ` Lars-Peter Clausen
2012-05-14 14:31 ` Lars-Peter Clausen
2012-05-14 14:39 ` Jonathan Cameron
2012-05-11 17:04 ` [PATCH 3/3] staging:iio:dac: Remove dac.h Lars-Peter Clausen
2012-05-12 18:52 ` Jonathan Cameron
2012-05-12 18:20 ` [PATCH 1/3] staging:iio:dac: Remove unused dac.h includes 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=4FAF61CF.6070509@metafoo.de \
--to=lars@metafoo.de \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=stigge@antcom.de \
/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).