From: "Stefan Brüns" <stefan.bruens@rwth-aachen.de>
To: <linux-iio@vger.kernel.org>
Cc: <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>
Subject: [PATCH v2 0/4] iio: light: vl6180: Several fixes and enhancements
Date: Sun, 24 Sep 2017 00:58:20 +0200 [thread overview]
Message-ID: <20170923225824.8435-1-stefan.bruens@rwth-aachen.de> (raw)
Currently, the vl6180 driver reports bogus in_illuminance_scale values
when the integration time or hardware gain are changed from its default
value, i.e. it always reports a fixed value.
To avoid readback of the register values in case integration time, gain
or scale is queried, save the register values. Use the saved values
to report the correct scale value.
v2: removed redundant parenthesis, add missing spaces
Stefan Brüns (4):
iio: light: vl6180: Move range check to integration time setter,
cleanup
iio: light: vl6180: Avoid readback of integration time register
iio: light: vl6180: Cleanup als_gain lookup, avoid register readback
iio: light: vl6180: Correct ALS scale for non-default gain/integration
time
drivers/iio/light/vl6180.c | 125 +++++++++++++++++++++++++--------------------
1 file changed, 69 insertions(+), 56 deletions(-)
--
2.14.1
next reply other threads:[~2017-09-23 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 22:58 Stefan Brüns [this message]
2017-09-23 22:58 ` [PATCH v2 1/4] iio: light: vl6180: Move range check to integration time setter, cleanup Stefan Brüns
2017-09-23 22:58 ` [PATCH v2 2/4] iio: light: vl6180: Avoid readback of integration time register Stefan Brüns
2017-09-23 22:58 ` [PATCH v2 3/4] iio: light: vl6180: Cleanup als_gain lookup, avoid register readback Stefan Brüns
2017-09-23 22:58 ` [PATCH v2 4/4] iio: light: vl6180: Correct ALS scale for non-default gain/integration time Stefan Brüns
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=20170923225824.8435-1-stefan.bruens@rwth-aachen.de \
--to=stefan.bruens@rwth-aachen.de \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.