From: Haneen <hamohammed.sa@gmail.com>
To: jic23@kernel.org, daniel.baluta@intel.com
Cc: linux-iio@vger.kernel.org, lars@metafoo.de
Subject: Re: [PATCH] iio: Add ABI documentation for out_voltage scan_elements
Date: Sat, 28 Mar 2015 01:10:18 +0300 [thread overview]
Message-ID: <20150327221018.GA3568@haneen-vb> (raw)
In-Reply-To: <551158E0.7040401@metafoo.de>
On Tue, Mar 24, 2015 at 01:30:24PM +0100, Lars-Peter Clausen wrote:
> On 03/21/2015 01:00 PM, Jonathan Cameron wrote:
> >On 17/03/15 10:36, Haneen Mohammed wrote:
> >>This patch adds ABI documentation entries for out_voltageY_en,
> >>out_voltageY_type, and out_voltageY_index.
> >>At least one user for these is preset:
> >>AD8366 SPI Dual-Digital VGA.
> >>
> >>Signed-off-by: Haneen Mohammed <hamohammed.sa@gmail.com>
> >These aren't used in the mainline driver. We don't have buffered support
> >for output channels yet. Looking at Analog's tree I don't think they have
> >support for this driver doing buffered output either (I think they may have
> >some internal support or maybe it's just a plan on how to do it!)
>
> We do have support for output buffers in our tree, but obviously not
> for a VGA. I think we should add the upstream documentation for
> these attributes at the same time we add the infrastructure support.
>
> - Lars
Sorry my bad. I used the iio dummy to check that out, and I didn't
know I had to specify no buffer support through the scan_index since
the driver I checked didn't have that. I will be more carefull next
time!
Haneen
prev parent reply other threads:[~2015-03-27 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 10:36 [PATCH] iio: Add ABI documentation for out_voltage scan_elements Haneen Mohammed
2015-03-21 12:00 ` Jonathan Cameron
2015-03-24 12:30 ` Lars-Peter Clausen
2015-03-27 22:10 ` Haneen [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=20150327221018.GA3568@haneen-vb \
--to=hamohammed.sa@gmail.com \
--cc=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
/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).