linux-kernel - Re: Voltage/current/sensor monitoring interface and Wiegand

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 10 Sep 2010 20:47:13 +0000 (UTC)
From:	Guenter Roeck <guenter.roeck@...csson.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Voltage/current/sensor monitoring interface and Wiegand

Stuart Longland <redhatter <at> gentoo.org> writes:

> 
> On Thu, Sep 09, 2010 at 02:48:26PM +1200, Ryan Mallon wrote:
> > On 09/09/2010 12:02 PM, Stuart Longland wrote:
> > > 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.
> 
> Ahh okay, I'll have a look there..  The temperature isn't related to the
> power supply, so I might continue a searchfor its rightful place, but
> that class of devices seems like a good fit.

For voltage, current, and temperature monitoring, you should really look into
using using hwmon. The power supply class doesn't make sense to me, unless you
are actually monitoring a power supply and not a voltage. For multi-function
devices, you might also want to look into mfd for higher level access control.

If you have problems understanding what needs to be done, feel free to get in
touch. If the sysfs ABI is insufficient for your needs, just drop an e-mail to
the lm-sensors mailing list. Easier to extend an existing ABI than to write a
new one.

Guenter


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/