From: Jonathan Cameron <jic23@kernel.org>
To: Bryan Freed <bfreed@chromium.org>
Cc: jbrenner@taosinc.com, linux-iio@vger.kernel.org, jic23@cam.ac.uk,
gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: light sensor: Improve granularity of tsl2583 lux values.
Date: Sun, 04 Dec 2011 17:23:11 +0000 [thread overview]
Message-ID: <4EDBAC7F.50001@kernel.org> (raw)
In-Reply-To: <1322864370-15126-1-git-send-email-bfreed@chromium.org>
On 12/02/2011 10:19 PM, Bryan Freed wrote:
> When illuminance0_calibbias gets 4000 (for a 4x multiplier), we see lux
> granularity of 4. Reversing the order of the right shift and multiplication
> retains the precision of the unadjusted lux value.
Looks sensible to me, but having said that, Greg, please leave a little
while for Jon Brenner to get to it as he clearly knows this driver
a lot better than me!
>
> Signed-off-by: Bryan Freed <bfreed@chromium.org>
Acked-by: Jonathan Cameron <jic23@kernel.org>
> ---
> drivers/staging/iio/light/tsl2583.c | 17 ++++++++++++++---
> 1 files changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/iio/light/tsl2583.c b/drivers/staging/iio/light/tsl2583.c
> index 80f77cf..25f4c1d 100644
> --- a/drivers/staging/iio/light/tsl2583.c
> +++ b/drivers/staging/iio/light/tsl2583.c
> @@ -194,6 +194,7 @@ static int taos_get_lux(struct iio_dev *indio_dev)
> {
> u16 ch0, ch1; /* separated ch0/ch1 data from device */
> u32 lux; /* raw lux calculated from device data */
> + u64 lux64;
> u32 ratio;
> u8 buf[5];
> struct taos_lux *p;
> @@ -297,9 +298,19 @@ static int taos_get_lux(struct iio_dev *indio_dev)
> lux = (lux + (chip->als_time_scale >> 1)) /
> chip->als_time_scale;
>
> - /* adjust for active gain scale */
> - lux >>= 13; /* tables have factor of 8192 builtin for accuracy */
> - lux = (lux * chip->taos_settings.als_gain_trim + 500) / 1000;
> + /* Adjust for active gain scale.
> + * The taos_device_lux tables above have a factor of 8192 built in,
> + * so we need to shift right.
> + * User-specified gain provides a multiplier.
> + * Apply user-specified gain before shifting right to retain precision.
> + * Use 64 bits to avoid overflow on multiplication.
> + * Then go back to 32 bits before division to avoid using div_u64().
> + */
> + lux64 = lux;
> + lux64 = lux64 * chip->taos_settings.als_gain_trim;
> + lux64 >>= 13;
> + lux = lux64;
> + lux = (lux + 500) / 1000;
> if (lux > TSL258X_LUX_CALC_OVER_FLOW) { /* check for overflow */
> return_max:
> lux = TSL258X_LUX_CALC_OVER_FLOW;
next prev parent reply other threads:[~2011-12-04 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 22:19 [PATCH v2] iio: light sensor: Improve granularity of tsl2583 lux values Bryan Freed
2011-12-04 17:23 ` Jonathan Cameron [this message]
2011-12-09 16:29 ` 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=4EDBAC7F.50001@kernel.org \
--to=jic23@kernel.org \
--cc=bfreed@chromium.org \
--cc=gregkh@suse.de \
--cc=jbrenner@taosinc.com \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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).