linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org, Jon Brenner <jon.brenner@ams.com>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 1/2] iio: add INT_TIME (integration time) channel info attribute
Date: Sun, 01 Sep 2013 19:33:26 +0100	[thread overview]
Message-ID: <52238876.4030308@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.01.1308182319000.4146@pmeerw.net>

On 08/18/13 22:30, Peter Meerwald wrote:
> Hello,
> 
>>> integration time is in seconds; it controls the measurement
>>> time and influences the gain of a sensor
>>>
>>> used by adjd_s311, tsl4531
>>> the following drivers have similar controls:
>>> * tsl2563 (integration time is controlled via CALIBSCALE among other things)
>>> * tsl2583 (has integration_time device_attr, but driver doesn't use channels yet)
>>> * tsl2x7x (has integration_time attr)
> 
>> I know this has come up before (and I'm not actually expressing oposition
>> to this going into info_mask) but could you sumarise the arguments for why
>> this property cannot be covered by calibscale or scale?
>> I'd like to have a little stronger argument for the patch description in Git.
> 
> sounds good; I'd add:
> 
>> There are two typical ways that scaling is implemented in a device:
>> 1) input amplifier
>> 2) reference to the ADC is changed.
>> These both result in the accuracy of the ADC varying (by applying it's
>> sampling over ta more relevant range).
>>
>> Integration time is a way of dealing with noise inherent in the analog
>> sensor itself.  In this case a mixture of Photon noise and device specific
>> noise.  Photon noise is dealt with by either improving the efficiency of
>> the sensor, (more photons actually captured) which is not easily varied dynamically,
>> or by integrating the measurement over a longer time period.  Note that this
>> can also be thought of as an averaging of a number of individual samples
>> and is infact sometimes implemented this way.
> 
> altering integration time implies that the duration of a 
> measurement changes and the user of the device may be interested
>  
>> Hence it makes sense to distinguish between integration time and simple
>> scale. In some devices both types of control are present and whilst they
>> will have similar effects on the amplitude of the reading, their effect
>> on the noise on the measurements will differ considerably.
> 
> integration time may or may not have an impact on the range of values
> measured
> 
> both characteristics cannot be expressed with scale/calibscale in a 
> satisfying way
> 
> let's see if further comments come up, and I'll repost
Not much come out of the wood work so something like what you propose will do nicely!

I would also like a short description in the documentation file so we don't have
to keep refering people back to the original patch.

Jon, you still out there?  Not heard anything from you for a while and your input
on this sort of thing is always valued!

Jonathan
> 
> please note that there is a fix for the adjd_s311 driver posted which you 
> may want to fast-feed to Greg
> 
> thanks, regards, p.
> 

  reply	other threads:[~2013-09-01 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18 13:00 [PATCH 1/2] iio: add INT_TIME (integration time) channel info attribute Peter Meerwald
2013-08-18 13:00 ` [PATCH 2/2] iio: adjd_s311: Use INT_TIME channel info Peter Meerwald
2013-08-18 21:12 ` [PATCH 1/2] iio: add INT_TIME (integration time) channel info attribute Jonathan Cameron
2013-08-18 21:30   ` Peter Meerwald
2013-09-01 18:33     ` Jonathan Cameron [this message]
2013-09-03  4:23       ` Jon Brenner

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=52238876.4030308@kernel.org \
    --to=jic23@kernel.org \
    --cc=jon.brenner@ams.com \
    --cc=lars@metafoo.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 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).