From: Shubhrajyoti Datta <omaplinuxkernel@gmail.com>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org, Jonathan Cameron <jic23@cam.ac.uk>
Subject: Re: proximity sensor, input
Date: Tue, 10 Apr 2012 15:30:55 +0530 [thread overview]
Message-ID: <CAM=Q2csVsYXEvhN7v8SK4R=UpaEW2ELBmx42TcwpFMs_j6-5xg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1204101115470.17667@pmeerw.net>
Hi Peter,
Can you explain more about how your proximity device is?
How does it report through gpio / irq etc ?
Thanks,
Shubhro
On Tue, Apr 10, 2012 at 3:17 PM, Peter Meerwald <pmeerw@pmeerw.net> wrote:
> Hello,
>
> I am wondering how to support proximity sensors; goal is to trigger some
> application event when an object comes close (in that sense, the proximit=
y
> sensor is used like a button)
>
> there are several places in the kernel doing similar things:
> e.g. input/misc/gp2ap0002a00f.c
> e.g. drivers/misc/bh1770glc.c
> e.g. drivers/staging/iio/isl29018.c
>
> iio seems to be most active and has IIO_PROXIMITY, but I do not see how
> the application is easily notified: iio collects merely collects the
> sensor data
>
> drivers in misc just create some custom sysfs interface
>
> input/misc has just one driver dealing with proximity
>
> is there some advise where proximity driver support might best fit?
>
> thanks, regards, p.
>
> --
>
> Peter Meerwald
> +43-664-2444418 (mobile)
> --
> 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 =A0http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-04-10 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 9:47 proximity sensor, input Peter Meerwald
2012-04-10 10:00 ` Shubhrajyoti Datta [this message]
2012-04-10 10:22 ` Jonathan Cameron
2012-04-10 11:24 ` Peter Meerwald
2012-04-10 13:03 ` 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='CAM=Q2csVsYXEvhN7v8SK4R=UpaEW2ELBmx42TcwpFMs_j6-5xg@mail.gmail.com' \
--to=omaplinuxkernel@gmail.com \
--cc=jic23@cam.ac.uk \
--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).