From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: iio: vcnl4000 ALS/proximity driver
Date: Mon, 11 Jun 2012 19:14:56 +0100 [thread overview]
Message-ID: <4FD635A0.7050507@kernel.org> (raw)
In-Reply-To: <1339367961-22456-1-git-send-email-pmeerw@pmeerw.net>
On 06/10/2012 11:39 PM, Peter Meerwald wrote:
> I'm submitting a minimal, work-in-progress driver for the
> Vishay VCNL4000 combined ambient light/proximity sensor to -staging
>
> the driver is missing a way to adjust the IR current determining
> the range for proximity sensing
>
> is scale/calibscale desirable?
> 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!)
scale is applied in userspace to convert to SI units.
>
> ultimately, periodic proximity sensing and thresholding with event
> handling should be implemented... I do have a misc/input driver for
> that but want to built upon IIO
cool.
>
> --
> 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-11 18:14 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 ` Jonathan Cameron [this message]
2012-06-11 21:35 ` iio: vcnl4000 ALS/proximity driver Peter Meerwald
2012-06-12 5:49 ` Jonathan Cameron
2012-06-12 7:49 ` Jonathan Cameron
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=4FD635A0.7050507@kernel.org \
--to=jic23@kernel.org \
--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).