From: Jonathan Cameron <jic23@cam.ac.uk>
To: LKML <linux-kernel@vger.kernel.org>
Cc: lrg@slimlogic.co.uk, broonie@opensource.wolfsonmicro.com
Subject: [RFC] Regulator: Possibility of passing notifications of non alarm events.
Date: Sat, 03 Jan 2009 21:11:10 +0000 [thread overview]
Message-ID: <495FD46E.8040208@cam.ac.uk> (raw)
Dear All,
I am in the process of writing an hwmon driver for the Sensiron SHT15 humidity
sensor.
In common (I assume) with lots of other devices, the formula for converting
the outputs of this chip to real units involves the supply voltage.
Unfortunately the chip doesn't itself have any means of measuring this.
Obviously this can be supplied via a board config if it is constant.
As I have it connected to a DA9030 pmic I can register it as a consumer
and hence query what the pmic thinks it is supplying.
Unfortunately this regulator is shared with a number of other chips and so
there is no guarantee that this voltage won't be changed (within the bounds
supported by the SHT15). I'd like to avoid querying the regulator voltage
every time I do a conversion.
As the regulator framework already allows you to register to receive events
such as under voltage detections, it seems to me that it would also make sense
to allow registrations of handlers for events that occur during normal
operation such as voltage changes.
What do people think to adding this functionality?
Thanks
--
Jonathan Cameron
next reply other threads:[~2009-01-03 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 21:11 Jonathan Cameron [this message]
2009-01-04 10:31 ` [RFC] Regulator: Possibility of passing notifications of non alarm events Liam Girdwood
2009-01-18 18:47 ` [RFC] Regulator: Add a voltage changed event to notify consumers Jonathan Cameron
2009-01-19 15:29 ` Mark Brown
2009-01-19 16:57 ` Jonathan Cameron
2009-01-19 18:08 ` Jonathan Cameron
2009-01-19 18:20 ` [RFC] Regulator: Push lock out of _notifier_call_chain + add voltage change event Jonathan Cameron
2009-01-20 20:09 ` Liam Girdwood
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=495FD46E.8040208@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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