From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Peter Meerwald <pmeerw@pmeerw.net>, linux-iio@vger.kernel.org
Subject: Re: iio: vcnl4000 ALS/proximity driver
Date: Tue, 12 Jun 2012 08:49:11 +0100 [thread overview]
Message-ID: <4FD6F477.9030506@kernel.org> (raw)
In-Reply-To: <3a7abb16-df44-4b5b-9651-d0399659c4af@email.android.com>
On 6/12/2012 6:49 AM, Jonathan Cameron wrote:
>
> Peter Meerwald<pmeerw@pmeerw.net> wrote:
>
>> Hello Jonathan,
>>
>>>> I am lost with the meaning and use of IIO modifiers...
>>> Quick and dirty summary.
>>> Calibscale is internally applied within the hardware (or occasionally
>>> software but looks like it was in the hardware from point of view
>>> of userspace!)
>> thank you for clarification
>>
>> Am I missing documentation somewhere?
>>
> Documentation/ABI/testing/sysfs-bus-iio.
+ drivers/staging/iio/documentation/sysfs-* for other bits and bobs.
Mostly it
should be fairly obvious how stuff lines up.
>
>> some comments in iio/types.h iio/iio.h would avoid guesswork...
>>
>> enum iio_chan_type {
>> /* real channel types */
>> are there unreal channels also? :)
ah, there were. That comment is out of date. This sort of thing is why
we try to keep minimal commenting in there unless absolutely necessary.
I suppose we could put a reference to say see the docs files...
>> what is IIO_ANGL_VEL vs. IIO_ANGL? VOLTAGE vs. ALTVOLTAGE?
Those should be pretty obvious and line up with the documentation.
Angl_vel is the angular velocity. angl is the the angle. Voltage is a
dc voltage,
altvoltage is an alternating voltage. (this can mater as some 'interesting'
parts can sample the instantaneous voltage and also provide the rms voltage
under the assumption that it's a sinusoid.).
>>
>> what is LIGHT_BOTH?
Visible + infrared (agreed that one is not good. We've talked about
changing that, but nothing has happened about it yet...)
>>
>> it would be helpful what IIO_CHAN_INFO_SHARED_BIT vs
>> IIO_CHAN_INFO_SEPARATE_BIT relates to?
Maybe that one needs a comment..
Shared is across a channel type. E.g. in_accel_scale
vs separate which is per channel in_accel_x_scale.
>>
>> IIO_CHAN_INFO_SAMP_FREQ vs IIO_CHAN_INFO_FREQUENCY?
That should be in the sysfs docs. samping frequency refers to sampling
whereas frequency refers to the frequency of the thing being measured
or (more typically) output.
>>
>> thanks, regards, p.
>>
>> --
>>
>> Peter Meerwald
>> +43-664-2444418 (mobile)
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-06-12 7:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 22:39 iio: vcnl4000 ALS/proximity driver Peter Meerwald
2012-06-10 22:39 ` [PATCH] iio: add vcnl4000 combined ALS and proximity sensor Peter Meerwald
2012-06-11 11:13 ` Lars-Peter Clausen
2012-06-11 18:13 ` Jonathan Cameron
2012-06-11 18:14 ` iio: vcnl4000 ALS/proximity driver Jonathan Cameron
2012-06-11 21:35 ` Peter Meerwald
2012-06-12 5:49 ` Jonathan Cameron
2012-06-12 7:49 ` Jonathan Cameron [this message]
2012-06-12 9:48 ` Peter Meerwald
2012-06-12 11:01 ` Jonathan Cameron
2012-06-12 11:04 ` Jonathan Cameron
2012-06-12 12:12 ` Peter Meerwald
2012-06-12 12:20 ` 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=4FD6F477.9030506@kernel.org \
--to=jic23@kernel.org \
--cc=jic23@cam.ac.uk \
--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 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).