From: Jonathan Cameron <jic23@cam.ac.uk>
To: David Brownell <david-b@pacbell.net>
Cc: Jean Delvare <khali@linux-fr.org>,
spi-devel-general@lists.sourceforge.net,
Jonathan Cameron <Jonathan.Cameron@gmail.com>,
LM Sensors <lm-sensors@lm-sensors.org>,
linux-kernel@vger.kernel.org, Dmitry Torokhov <dtor@mail.ru>
Subject: Re: [spi-devel-general] Accelerometer, Gyros and ADC's etc within the kernel.
Date: Thu, 22 May 2008 10:35:01 +0100 [thread overview]
Message-ID: <48353E45.2080903@cam.ac.uk> (raw)
In-Reply-To: <200805211752.15670.david-b@pacbell.net>
Hi David,
> 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.
I get the feeling even the name is going to evolve for some time to come,
getting broader as and when we add more classes of device.
> Such alarms are of course different from the "data
> ready" signals of an accelerometer.
Whilst this is true, most accelerometers also have "alarm" triggers, for example
the ST LIS3L02DQ will raise a pin on configurable conditions such as thresholds
and even a double click detector (though I've never tried them!). I suppose we
will ideally support this functionality as well.
--
Jonathan Cameron
next prev parent reply other threads:[~2008-05-22 9:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 10:04 Accelerometer, Gyros and ADC's etc within the kernel Jonathan Cameron
2008-05-20 11:28 ` Jean Delvare
2008-05-20 21:40 ` Hans J. Koch
2008-05-21 10:04 ` Jonathan Cameron
2008-05-21 13:20 ` Jean Delvare
2008-05-21 13:49 ` Dmitry Torokhov
2008-05-21 14:09 ` Henrique de Moraes Holschuh
2008-05-27 17:16 ` [spi-devel-general] " Ben Dooks
2008-05-27 19:01 ` Dmitry Torokhov
2008-05-22 0:52 ` David Brownell
2008-05-22 9:35 ` Jonathan Cameron [this message]
2008-05-26 16:23 ` [spi-devel-general] " Jonathan Cameron
2008-06-26 18:01 ` Accelerometer etc subsystem (Update on progress) Jonathan Cameron
2008-06-26 18:26 ` Jonathan Cameron
2008-06-27 2:39 ` Randy Dunlap
2008-06-27 3:29 ` Ben Nizette
2008-06-27 9:45 ` [lm-sensors] " Jonathan Cameron
2008-06-28 8:34 ` Ben Nizette
2008-06-28 15:34 ` Jonathan Cameron
2008-05-20 17:50 ` Accelerometer, Gyros and ADC's etc within the kernel mark gross
2008-05-21 9:40 ` [spi-devel-general] " Jonathan Cameron
2008-05-27 15:43 ` mark gross
2008-05-29 11:57 ` Jonathan Cameron
2008-05-22 0:53 ` David Brownell
2008-05-27 15:56 ` mark gross
2008-05-27 23:42 ` David Brownell
2008-05-27 16:44 ` [spi-devel-general] " Anton Vorontsov
2008-05-27 16:50 ` Ben Dooks
2008-05-27 17:01 ` Anton Vorontsov
2008-05-27 18:00 ` Jonathan Cameron
2008-05-27 18:12 ` Ben Dooks
2008-05-27 17:59 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48353E45.2080903@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Jonathan.Cameron@gmail.com \
--cc=david-b@pacbell.net \
--cc=dtor@mail.ru \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=spi-devel-general@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox