From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: Voltage/current/sensor monitoring interface and Wiegand
Date: Thu, 09 Sep 2010 14:48:26 +1200 [thread overview]
Message-ID: <4C884AFA.20604@bluewatersys.com> (raw)
In-Reply-To: <20100909000245.GK14056@atomos.longlandclan.yi.org>
On 09/09/2010 12:02 PM, Stuart Longland wrote:
> Hi all,
>
> I'm currently writing a driver for an in-house developed sensor
> controller device. This device communicates via I?C, and functions as a
> multi-function device incorporating:
>
> - Touchscreen controller
> - Keypad/Button controller
> - LED driver
> - Voltage/current monitor
> - Temperature sensor monitor
> - Light sensor monitor
> - PIR (motion) detection monitor
> - Communications interface (for slow serial links like Wiegand)
> How are voltage *monitors* normally written? (note, not voltage
> *regulators*... this thing does not alter the voltage rails.) I tried
> to make sense of lm-sensors, but that seems very ad-hoc (maybe I missed
> some document that explains it) to me. It's hard to be clear on what is
> the *right* way to report a voltage or current reading to userspace.
Depending on your particular application it might make sense to use the
power supply class (see Documentation/power/power_supply_class.txt) for
the voltage/current monitoring. If the temperature sensor is related to
a power supply monitor, then it could also go there.
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan at bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
next prev parent reply other threads:[~2010-09-09 2:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 0:02 Voltage/current/sensor monitoring interface and Wiegand Stuart Longland
2010-09-09 2:48 ` Ryan Mallon [this message]
2010-09-09 5:01 ` Stuart Longland
2010-09-09 8:29 ` Mark Brown
2010-09-09 12:43 ` Jonathan Cameron
2010-09-09 22:46 ` Stuart Longland
2010-09-10 6:32 ` Dmitry Torokhov
2010-09-13 1:13 ` Stuart Longland
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=4C884AFA.20604@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).