From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Mohamed Ikbel Boulabiar <boulabiar@gmail.com>
Cc: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
Trilok Soni <soni.trilok@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Jonathan Cameron <jic23@cam.ac.uk>
Subject: Re: [RFC] Add Input IOCTL for accelerometer devices
Date: Sat, 16 May 2009 15:50:40 +0300 [thread overview]
Message-ID: <20090516125040.GA13146@nokia.com> (raw)
In-Reply-To: <45cc95260905152119l6d4e76d1k6a11af2b177219ef@mail.gmail.com>
Hi,
On Sat, May 16, 2009 at 06:19:33AM +0200, ext Mohamed Ikbel Boulabiar wrote:
> On Fri, May 15, 2009 at 9:02 PM, Felipe Balbi <felipe.balbi@nokia.com> wrote:
>
> > Yeah, let's try to define the best way to expose accelerometers with
> > linux kernel and avoid a sysfs hell. Better sooner than later.
>
> isn't the best way to add a thing like the one for battery for any input device
> /proc/acpi/battery/CMB0/state
> or even in /sys/input/devices/XXXX
>
> and let any userspace application do what she wants with information ?
This case is the other way around. We are trying to set proper
thresholding and other parameters depending on the user application
(gaming, screen rotation, etc).
> > Say we wanna use the accelerometer for both screen rotation and gaming,
> > that device isn't doing hw monitoring and still we _do_ want to set
> > different thresholds and irq requests/types for different use cases,
> > right ?
>
> Another reason for preparing the interface I just cited.
Yes, and the interface would be an input ioctl so that userland would
give us the parameters and the driver just sets them to proper
registers.
--
balbi
next prev parent reply other threads:[~2009-05-16 13:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090515131636.GE4443@nokia.com>
2009-05-15 18:06 ` [RFC] Add Input IOCTL for accelerometer devices Trilok Soni
2009-05-15 19:30 ` Mohamed Ikbel Boulabiar
2009-05-15 20:02 ` Felipe Balbi
2009-05-16 4:19 ` Mohamed Ikbel Boulabiar
2009-05-16 12:50 ` Felipe Balbi [this message]
2009-05-18 7:45 ` Kim Kyuwon
2009-05-18 9:12 ` Felipe Balbi
2009-05-18 10:11 ` Jonathan Cameron
2009-05-18 10:31 ` Felipe Balbi
2009-05-18 11:37 ` Jonathan Cameron
2009-05-19 6:32 ` Kim Kyuwon
2009-05-21 11:42 ` Jonathan Cameron
2009-05-22 8:21 ` Kim Kyuwon
2009-05-22 13:35 ` Jonathan Cameron
2009-05-25 8:15 ` Kim Kyuwon
2009-05-25 8:52 ` Mohamed Ikbel Boulabiar
2009-05-25 11:07 ` Jonathan Cameron
2009-05-19 2:41 ` Kim Kyuwon
2009-05-19 10:42 ` Felipe Balbi
2009-05-19 12:34 ` Mohamed Ikbel Boulabiar
2009-05-21 10:21 ` 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=20090516125040.GA13146@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=boulabiar@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jic23@cam.ac.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soni.trilok@gmail.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 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).