From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Subject: Re: Accelerometer, Gyros and ADC's etc within the kernel. Date: Wed, 21 May 2008 17:52:15 -0700 Message-ID: <200805211752.15670.david-b@pacbell.net> References: <4832A211.4040206@gmail.com> <20080520132817.03fb74ea@hyperion.delvare> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Jonathan Cameron , LM Sensors , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Dmitry Torokhov To: Jean Delvare Return-path: In-Reply-To: <20080520132817.03fb74ea-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: spi-devel-general-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: spi-devel-general-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-spi.vger.kernel.org On Tuesday 20 May 2008, Jean Delvare wrote: > This all sounds quite different from our hwmon drivers. Our hwmon > drivers read all the sensor values at once and cache the readings for a > couple seconds, so you can't get an instant reading at any time, and > they also don't support interrupts in general. That's something of an issue when the hardware monitor triggers alarms though, right? I couldn't figure out how to get a TMP75 alert out to any userspace code that would care, to pick one example, even after teaching the i2c core how to handle SMBus alerts. ;) I suppose this just emphasizes the point made by Hans that we kind of need (industrial) "control" components (or "data acquisition"?) not just "monitoring" ones. Such alarms are of course different from the "data ready" signals of an accelerometer. - Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Thu, 22 May 2008 00:52:15 +0000 Subject: Re: [lm-sensors] Accelerometer, Message-Id: <200805211752.15670.david-b@pacbell.net> List-Id: References: <4832A211.4040206@gmail.com> <20080520132817.03fb74ea@hyperion.delvare> In-Reply-To: <20080520132817.03fb74ea@hyperion.delvare> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jean Delvare Cc: spi-devel-general@lists.sourceforge.net, Jonathan Cameron , Dmitry Torokhov , linux-kernel@vger.kernel.org, LM Sensors On Tuesday 20 May 2008, Jean Delvare wrote: > This all sounds quite different from our hwmon drivers. Our hwmon > drivers read all the sensor values at once and cache the readings for a > couple seconds, so you can't get an instant reading at any time, and > they also don't support interrupts in general. That's something of an issue when the hardware monitor triggers alarms though, right? I couldn't figure out how to get a TMP75 alert out to any userspace code that would care, to pick one example, even after teaching the i2c core how to handle SMBus alerts. ;) I suppose this just emphasizes the point made by Hans that we kind of need (industrial) "control" components (or "data acquisition"?) not just "monitoring" ones. Such alarms are of course different from the "data ready" signals of an accelerometer. - Dave _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758436AbYEVDjQ (ORCPT ); Wed, 21 May 2008 23:39:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757590AbYEVDi2 (ORCPT ); Wed, 21 May 2008 23:38:28 -0400 Received: from smtp105.sbc.mail.mud.yahoo.com ([68.142.198.204]:36097 "HELO smtp105.sbc.mail.mud.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1757214AbYEVDi1 (ORCPT ); Wed, 21 May 2008 23:38:27 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=pacbell.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Disposition:Message-Id:Content-Type:Content-Transfer-Encoding; b=c0lp/VN+KKgaMNJyIBA+WnIIbc4c+vZHg1VltUewFD8SXxQRP3TvDKVa27UmZYv8qzAasbvUORXcEAmfZ/O5vpg/GmjqWwwt9iJ4HialpHWsCtnY5GBqJbRjuh748E71J1jTKJc0ri91vdAAesL4yJ+fg1aeGH3J7yQhx+zWeqk= ; X-YMail-OSG: T_ir7VQVM1nCtGCxF8X9cXIpyG56Gj2pnzcxqZ1QBOGqzcQATbd.J4sSD5hI1ObjAJ3K_H8zthkDmGvpABq_HQa4EGdiZCQdEKuMn1JYxM50Q7joh.5b3e56Rbbo7SJ9yrU- X-Yahoo-Newman-Property: ymail-3 From: David Brownell To: Jean Delvare Subject: Re: Accelerometer, Gyros and ADC's etc within the kernel. Date: Wed, 21 May 2008 17:52:15 -0700 User-Agent: KMail/1.9.9 Cc: spi-devel-general@lists.sourceforge.net, Jonathan Cameron , Dmitry Torokhov , linux-kernel@vger.kernel.org, LM Sensors References: <4832A211.4040206@gmail.com> <20080520132817.03fb74ea@hyperion.delvare> In-Reply-To: <20080520132817.03fb74ea@hyperion.delvare> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200805211752.15670.david-b@pacbell.net> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 20 May 2008, Jean Delvare wrote: > This all sounds quite different from our hwmon drivers. Our hwmon > drivers read all the sensor values at once and cache the readings for a > couple seconds, so you can't get an instant reading at any time, and > they also don't support interrupts in general. That's something of an issue when the hardware monitor triggers alarms though, right? I couldn't figure out how to get a TMP75 alert out to any userspace code that would care, to pick one example, even after teaching the i2c core how to handle SMBus alerts. ;) I suppose this just emphasizes the point made by Hans that we kind of need (industrial) "control" components (or "data acquisition"?) not just "monitoring" ones. Such alarms are of course different from the "data ready" signals of an accelerometer. - Dave