From: Slawomir Stepien <sst@poczta.fm>
To: Peter Rosin <peda@axentia.se>
Cc: Daniel Baluta <daniel.baluta@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Devicetree List <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 1/8] iio:core: add a callback to allow drivers to provide _available attributes
Date: Mon, 7 Nov 2016 17:46:41 +0100 [thread overview]
Message-ID: <20161107164641.GA29162@x220.localdomain> (raw)
In-Reply-To: <62f150ba-abc0-8e45-1355-8a61354ee3e1@axentia.se>
On Nov 07, 2016 12:57, Peter Rosin wrote:
> On 2016-11-07 12:37, Daniel Baluta wrote:
> > On Mon, Oct 24, 2016 at 1:39 AM, Peter Rosin <peda@axentia.se> wrote:
> >> From: Jonathan Cameron <jic23@kernel.org>
> >>
> >> A large number of attributes can only take a limited range of values.
> >> Currently in IIO this is handled by directly registering additional
> >> *_available attributes thus providing this information to userspace.
> >>
> >> It is desirable to provide this information via the core for much the same
> >> reason this was done for the actual channel information attributes in the
> >> first place. If it isn't there, then it can only really be accessed from
> >> userspace. Other in kernel IIO consumers have no access to what valid
> >> parameters are.
> >>
> >> Two forms are currently supported:
> >> * list of values in one particular IIO_VAL_* format.
> >> e.g. 1.300000 1.500000 1.730000
> >> * range specification with a step size:
> >> e.g. [1.000000 0.500000 2.500000]
> >> equivalent to 1.000000 1.5000000 2.000000 2.500000
> >
> > Is there any driver using this format? :)
>
> Yes, soon. Hopefully. See patch 3/8
> iio: mcp4531: provide range of available raw values
> https://patchwork.kernel.org/patch/9391283/
I would also like to add this to mcp4131.c and ds1803.c.
--
Slawomir Stepien
next prev parent reply other threads:[~2016-11-07 16:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 22:39 [PATCH v3 0/8] IIO wrapper drivers, dpot-dac and envelope-detector Peter Rosin
[not found] ` <1477262381-7800-1-git-send-email-peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-10-23 22:39 ` [PATCH v3 1/8] iio:core: add a callback to allow drivers to provide _available attributes Peter Rosin
[not found] ` <1477262381-7800-2-git-send-email-peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-10-30 13:11 ` Jonathan Cameron
2016-11-07 11:37 ` Daniel Baluta
[not found] ` <CAEnQRZDgF-x6rNiS1Uv9Evdt1sVfUu9pMF98Z4=r-vKP52C1kA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-07 11:57 ` Peter Rosin
[not found] ` <62f150ba-abc0-8e45-1355-8a61354ee3e1-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-11-07 12:18 ` Daniel Baluta
2016-11-07 16:46 ` Slawomir Stepien [this message]
2016-10-23 22:39 ` [PATCH v3 2/8] iio: inkern: add helpers to query available values from channels Peter Rosin
2016-10-30 13:21 ` Jonathan Cameron
2016-10-30 15:23 ` Peter Meerwald-Stadler
[not found] ` <alpine.DEB.2.02.1610301611070.32031-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>
2016-10-30 21:12 ` Peter Rosin
2016-10-23 22:39 ` [PATCH v3 3/8] iio: mcp4531: provide range of available raw values Peter Rosin
[not found] ` <1477262381-7800-4-git-send-email-peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-10-30 13:26 ` Jonathan Cameron
2016-10-23 22:39 ` [PATCH v3 4/8] dt-bindings: add axentia to vendor-prefixes Peter Rosin
2016-10-30 20:41 ` Rob Herring
2016-10-23 22:39 ` [PATCH v3 6/8] iio: dpot-dac: DAC driver based on a digital potentiometer Peter Rosin
2016-10-30 13:33 ` Jonathan Cameron
[not found] ` <301ab064-cd90-d99d-a05a-8a50ba759c62-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-10-30 14:24 ` Peter Rosin
2016-10-30 15:32 ` Peter Meerwald-Stadler
[not found] ` <alpine.DEB.2.02.1610301628400.32031-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>
2016-10-30 18:36 ` Peter Rosin
2016-10-23 22:39 ` [PATCH v3 7/8] dt-bindings: iio: document envelope-detector bindings Peter Rosin
2016-10-30 13:35 ` Jonathan Cameron
[not found] ` <1477262381-7800-8-git-send-email-peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-10-30 20:41 ` Rob Herring
2016-10-23 22:39 ` [PATCH v3 8/8] iio: envelope-detector: ADC driver based on a DAC and a comparator Peter Rosin
[not found] ` <1477262381-7800-9-git-send-email-peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-10-30 13:44 ` Jonathan Cameron
[not found] ` <61cd873a-b6ff-50d5-1161-e9b1ad90af88-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-10-30 14:26 ` Peter Rosin
2016-10-23 22:39 ` [PATCH v3 5/8] dt-bindings: iio: document dpot-dac bindings Peter Rosin
[not found] ` <1477262381-7800-6-git-send-email-peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-10-30 13:28 ` Jonathan Cameron
2016-10-30 20:41 ` Rob Herring
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=20161107164641.GA29162@x220.localdomain \
--to=sst@poczta.fm \
--cc=daniel.baluta@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@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).