From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>, Vlad Dogaru <vlad.dogaru@intel.com>
Cc: linux-iio@vger.kernel.org, mranostay@gmail.com
Subject: Re: [PATCH 0/2] iio: driver for Semtech SX9500
Date: Tue, 18 Nov 2014 22:02:41 +0000 [thread overview]
Message-ID: <546BC201.10405@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1411171622140.3424@pmeerw.net>
On 17/11/14 15:25, Peter Meerwald wrote:
>
>> The device does not estimate distance, it only outputs a single bit which
>> indicates proximity. We use 0 to mean that an object is close and 1 otherwise,
>> sort of an uncalibrated distance. From what I understand in the ABI
>> specification, this is allowed.
>
> perhaps the input subsystem would be a better fit for this driver/device?
> what is it typically used for?
>
> regards, p.
>
Hi Peter,
Whilst it may be the case that this particular one might have a reasonable
home in input, these are often integrated with ambient light sensors
and as such we already have a quite a few proximity sensors in IIO...
Interestingly there is one obvious proximity sensor in input and that
is a dual ambient light/ proximity part though I can't see any way
of reading the light side of it. Interesting...
Jonathan
next prev parent reply other threads:[~2014-11-18 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 15:12 [PATCH 0/2] iio: driver for Semtech SX9500 Vlad Dogaru
2014-11-17 15:12 ` [PATCH 1/2] iio: rename proximity sensors in kernel config Vlad Dogaru
2014-11-22 10:39 ` Jonathan Cameron
2014-11-17 15:12 ` [PATCH 2/2] iio: driver for Semtech SX9500 proximity solution Vlad Dogaru
2014-11-17 15:25 ` [PATCH 0/2] iio: driver for Semtech SX9500 Peter Meerwald
2014-11-18 22:02 ` Jonathan Cameron [this message]
2014-11-18 22:12 ` Jonathan Cameron
2014-11-19 8:31 ` Peter Meerwald
2014-11-19 13:57 ` Vlad Dogaru
2014-11-20 10:07 ` Vlad Dogaru
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=546BC201.10405@kernel.org \
--to=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=mranostay@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=vlad.dogaru@intel.com \
/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.