From: Urs Fleisch <urs.fleisch@gmail.com>
To: Guenter Roeck <guenter.roeck@ericsson.com>
Cc: Jonathan Cameron <jic23@cam.ac.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
LM Sensors <lm-sensors@lm-sensors.org>,
Jean Delvare <khali@linux-fr.org>
Subject: Re: [PATCH] hwmon: driver for Sensirion SHT21 humidity and temperature sensor
Date: Tue, 4 Jan 2011 20:00:01 +0100 [thread overview]
Message-ID: <20110104200001.3328dae3.urs.fleisch@gmail.com> (raw)
In-Reply-To: <20110104152837.GA32138@ericsson.com>
> Uses I know of are indeed more general environment monitoring.
> Not seen one of these in conventional hardware monitoring but could be wrong.
> I guess, Urs will have a better idea of where these tend to be used?
Mobile phones could be a promising market for humidity sensors in a Linux system. Fujitsu already sells a mobile phone with built-in temperature and humidity sensors. So we hope to see also Linux-based mobile phones (e.g. Android, MeGoo) with a humidity sensor. Such a sensor could be used to monitor environmental conditions, but there could be other applications too, some of them may not make sense and others can not be foreseen. The humidity sensor could also be used to monitor the hardware of the phone, in this situation, hwmon makes sense. If a sensor can be used for various application, there is probably not one true category. There may be other sensors in hwmon, which can be used for applications other than hardware monitoring. I chose the hwmon directory because the sht15 was already there.
> Highly unusual way of detecting and returning errors.
If this is a problem, I can alter the code. I could also drop all user-register related attributes if they cause problems with the ABI.
Regards,
Urs
next prev parent reply other threads:[~2011-01-04 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 12:45 [PATCH] hwmon: driver for Sensirion SHT21 humidity and temperature sensor Urs Fleisch
2010-12-31 15:02 ` Jonathan Cameron
2011-01-03 7:14 ` Urs Fleisch
2011-01-03 11:06 ` Jonathan Cameron
2011-01-03 14:01 ` [PATCH V3] " Urs Fleisch
2011-01-03 15:12 ` Guenter Roeck
2011-01-03 14:53 ` [PATCH] " Guenter Roeck
2011-01-03 18:09 ` Guenter Roeck
2011-01-04 12:13 ` Jonathan Cameron
2011-01-04 15:28 ` Guenter Roeck
2011-01-04 19:00 ` Urs Fleisch [this message]
2011-01-04 19:42 ` Guenter Roeck
2011-01-06 7:43 ` [PATCH V4] " Urs Fleisch
2011-01-06 10:58 ` Jonathan Cameron
2011-01-06 15:21 ` Guenter Roeck
2011-01-06 15:56 ` Guenter Roeck
2011-01-07 7:15 ` [PATCH V5] " Urs Fleisch
2011-01-07 11:55 ` Guenter Roeck
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=20110104200001.3328dae3.urs.fleisch@gmail.com \
--to=urs.fleisch@gmail.com \
--cc=guenter.roeck@ericsson.com \
--cc=jic23@cam.ac.uk \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
/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