From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Hsu Subject: Re: Duplicated driver for LIS302-like device. Date: Mon, 14 Dec 2009 11:57:23 +0800 Message-ID: <4B25B7A3.6080607@0xlab.org> References: <4B21B40B.2010007@0xlab.org> <4B2241D0.3050504@cam.ac.uk> <4B224641.8050905@tremplin-utc.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B224641.8050905@tremplin-utc.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: lm-sensors-bounces@lm-sensors.org Errors-To: lm-sensors-bounces@lm-sensors.org To: =?ISO-8859-1?Q?=C9ric_Piel?= Cc: Samu Onkalo , dmitry.torokhov@gmail.com, LM Sensors , linux-input@vger.kernel.org List-Id: linux-input@vger.kernel.org > Hopefully, what you need is already there. Well, of course it depends > also on what interface you need in userspace for the hardware. Hi Eric, I poked series patches you mentioned above. These patches add the support of both interface. That's great work. Originally, it was my next TODO, integration both interfaces. Btw, here is the demo for this device. Just FYI. http://matthsu-abacus.blogspot.com/2009/12/motion-sensor-demo-on-beagleboard.html I will cherry pick the upstream patches when they are merged into 2.6.33. Cheers, Matt > There is > currently only position reporting (via joystick interface and sysfs > file), freefall detection (via a misc device) and selftest (via sysfs > file). Let me know if you have additional features in your > implementation, or some bug fixes, and we could incorporate them in the > lis3lv02d driver. > > See you, > Eric > _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors