[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090516125040.GA13146@nokia.com>
Date: Sat, 16 May 2009 15:50:40 +0300
From: Felipe Balbi <felipe.balbi@...ia.com>
To: ext Mohamed Ikbel Boulabiar <boulabiar@...il.com>
Cc: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@...ia.com>,
Trilok Soni <soni.trilok@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
Jonathan Cameron <jic23@....ac.uk>
Subject: Re: [RFC] Add Input IOCTL for accelerometer devices
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@...ia.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists