[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120119172933.GI3178@opensource.wolfsonmicro.com>
Date: Thu, 19 Jan 2012 17:29:33 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: "AnilKumar, Chimata" <anilkumar@...com>,
Jonathan Cameron <jic23@....ac.uk>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"greg@...ah.com" <greg@...ah.com>,
"eric.piel@...mplin-utc.net" <eric.piel@...mplin-utc.net>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"Nori, Sekhar" <nsekhar@...com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: [PATCH] lis3lv02d: Add STMicroelectronics lis33ldlh digital
On Thu, Jan 19, 2012 at 05:10:45PM +0000, 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 it should absolutely not be handled by a user space
> HAL but instead inside of the kernel, using a common method for all
> available drivers.
The polling frequency thing isn't even accelerometer specific, there's a
general need for this on a wide range of other things like touchscreens
(where controlling the sample rate is interesting for power, there are
widely varying requirements depending on what the screen is doing).
--
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