Hi Arnd,
On Thu, Jan 19, 2012 at 22:40:45, Arnd Bergmann wrote:
On Thursday 19 January 2012, AnilKumar, Chimata wrote:
Android userspace running on TI AM335x EVM is using the interface
provided by lis3lv02d. They were asking some more interfaces from
lis3lvo2d driver.
There are
On Wednesday 18 January 2012, Andi wrote:
What do you mean with kernel-wide policy for accelerometer drivers?
As far as I know, accelerometer drivers are written between the i2c driver
and the
input driver.
The input driver provides already some accelerometer specific event types,
ABS_X,
On Thursday 19 January 2012, AnilKumar, Chimata wrote:
Android userspace running on TI AM335x EVM is using the interface
provided by lis3lv02d. They were asking some more interfaces from
lis3lvo2d driver.
There are multiple ways we can interface accelerometer to Android layers,
which is
Arnd Bergmann a...@arndb.de wrote:
On Wednesday 18 January 2012, Andi wrote:
What do you mean with kernel-wide policy for accelerometer drivers?
As far as I know, accelerometer drivers are written between the i2c
driver and the
input driver.
The input driver provides already some
On Thu, Jan 19, 2012 at 05:10:45PM +, Arnd Bergmann wrote:
Having custom user interfaces inside an input driver however is very
bad. I'm sure that other accelerometers will have the same requirements
regarding polling frequency and enable/disable in android as well as
anytwhere else and
On Tuesday 17 January 2012, AnilKumar, Chimata wrote:
Hi All,
Recalling the patch, provide the comments if there are any if not please
include
this patch to v3.3 kernel.
As Mark and Greg said, 3.4 would be appropriate.
+static ssize_t lis3lv02d_range_set(struct device *dev,
+
Hi Arnd and all,
The lis3lv02d driver was moved outside of drivers/hwmon to make it
clear that we (hwmon/lm-sensors people) are not involved in maintaining
this driver in any way. So please remove the lm-sensors list (and
myself) from this discussion.
Thanks,
--
Jean Delvare
--
To unsubscribe
On Wednesday 18 January 2012, Jean Delvare wrote:
Hi Arnd and all,
The lis3lv02d driver was moved outside of drivers/hwmon to make it
clear that we (hwmon/lm-sensors people) are not involved in maintaining
this driver in any way. So please remove the lm-sensors list (and
myself) from this
On Wed, 18 Jan 2012 14:49:35 +, Arnd Bergmann wrote:
On Wednesday 18 January 2012, Jean Delvare wrote:
Hi Arnd and all,
The lis3lv02d driver was moved outside of drivers/hwmon to make it
clear that we (hwmon/lm-sensors people) are not involved in maintaining
this driver in any way.
Arnd Bergmann a...@arndb.de wrote:
On Tuesday 17 January 2012, AnilKumar, Chimata wrote:
Hi All,
Recalling the patch, provide the comments if there are any if not
please include
this patch to v3.3 kernel.
As Mark and Greg said, 3.4 would be appropriate.
+static ssize_t
On Wednesday 18 January 2012, Jonathan Cameron wrote:
Arnd Bergmann a...@arndb.de wrote:
Any opinions where they should live? input, iio or a new subsystem?
Personal thought is that straight 3d devices very directed at input
should go there. Iio has a few wrinkles left for the in kernel
Hi Arnd,
What do you mean with kernel-wide policy for accelerometer drivers?
As far as I know, accelerometer drivers are written between the i2c driver and
the
input driver.
The input driver provides already some accelerometer specific event types,
ABS_X, ABS_Y, ABS_Z,
in your opinion isn't
Hi Arnd,
On Wed, Jan 18, 2012 at 22:41:15, Arnd Bergmann wrote:
On Wednesday 18 January 2012, Jonathan Cameron wrote:
Arnd Bergmann a...@arndb.de wrote:
Any opinions where they should live? input, iio or a new subsystem?
Personal thought is that straight 3d devices very directed at
On Tue, Jan 17, 2012 at 07:32:47AM +, AnilKumar, Chimata wrote:
Recalling the patch, provide the comments if there are any if not please
include
this patch to v3.3 kernel.
There's no way this is going to make it into the 3.3 kernel at this
point, we're almost at the end of the merge
On Tue, Jan 17, 2012 at 10:54:42AM +, Mark Brown wrote:
On Tue, Jan 17, 2012 at 07:32:47AM +, AnilKumar, Chimata wrote:
Recalling the patch, provide the comments if there are any if not please
include
this patch to v3.3 kernel.
There's no way this is going to make it into the
On Tue, 17 Jan 2012 07:32:47 +
AnilKumar, Chimata anilku...@ti.com wrote:
Hi All,
Recalling the patch, provide the comments if there are any if not please
include
this patch to v3.3 kernel.
The patch is all mangled by someone's email client. Wordwrapping, mime
crap which my MUA can't
Thanks Greg
On Tue, Jan 17, 2012 at 21:33:35, g...@kroah.com wrote:
On Tue, Jan 17, 2012 at 10:54:42AM +, Mark Brown wrote:
On Tue, Jan 17, 2012 at 07:32:47AM +, AnilKumar, Chimata wrote:
Recalling the patch, provide the comments if there are any if not please
include
this
Hi Andrew,
Thanks for reviewing the patch
On Wed, Jan 18, 2012 at 05:17:02, Andrew Morton wrote:
On Tue, 17 Jan 2012 07:32:47 +
AnilKumar, Chimata anilku...@ti.com wrote:
Hi All,
Recalling the patch, provide the comments if there are any if not please
include
this patch to
Hi All,
Recalling the patch, provide the comments if there are any if not please include
this patch to v3.3 kernel.
-Original Message-
From: AnilKumar, Chimata
Sent: Friday, December 23, 2011 10:55 AM
To: a...@arndb.de; g...@kroah.com; eric.p...@tremplin-utc.net;
Hi Mark,
On Fri, Dec 23, 2011 at 16:48:08, Mark Brown wrote:
On Fri, Dec 23, 2011 at 10:54:52AM +0530, AnilKumar Ch wrote:
This patch adds support for lis33ldlh digital accelerometer to the
lis3lv02d driver family. Adds ID field for detecting the lis33ldlh
module, based on this ID field
On Fri, Dec 23, 2011 at 10:54:52AM +0530, AnilKumar Ch wrote:
This patch adds support for lis33ldlh digital accelerometer to the
lis3lv02d driver family. Adds ID field for detecting the lis33ldlh
module, based on this ID field lis3lv02d driver will export the
lis33ldlh module functionality.
21 matches
Mail list logo
