From: Mike Rapoport <mike@compulab.co.il>
To: broonie@opensource.wolfsonmicro.com
Cc: lrg@slimlogic.co.uk, linux-kernel@vger.kernel.org,
Mike Rapoport <mike@compulab.co.il>
Subject: [PATCH 0/2] regulator: add userspace-consumer driver
Date: Sun, 26 Apr 2009 12:17:21 +0300 [thread overview]
Message-ID: <cover.1240736991.git.mike@compulab.co.il> (raw)
The userspace-consumer driver allows control of voltage and current
regulator state from userspace. This is required for fine-grained power
management of devices that are completely controller by userspace
applications, e.g. a GPS transciever connected to a serial port.
The first patch in the serie reorginases the way structs are defined in
the regulator framework headers so that regulator_consumer_supply can be
used without need to include include/linux/regulator/machine.h
The second patch is actully userspace-consumer driver implementation.
Mike Rapoport (2):
regulator: move regulator_consumer_supply from machine.h to
consumer.h
regulator: add userspace-consumer driver
drivers/regulator/Kconfig | 10 ++
drivers/regulator/Makefile | 1 +
drivers/regulator/userspace-consumer.c | 213 ++++++++++++++++++++++++++
include/linux/regulator/consumer.h | 13 ++
include/linux/regulator/machine.h | 14 +--
include/linux/regulator/userspace-consumer.h | 25 +++
6 files changed, 263 insertions(+), 13 deletions(-)
create mode 100644 drivers/regulator/userspace-consumer.c
create mode 100644 include/linux/regulator/userspace-consumer.h
next reply other threads:[~2009-04-26 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 9:17 Mike Rapoport [this message]
2009-04-26 9:17 ` [PATCH 1/2] regulator: move regulator_consumer_supply from machine.h to consumer.h Mike Rapoport
2009-04-26 9:17 ` [PATCH 2/2] regulator: add userspace-consumer driver Mike Rapoport
2009-04-26 10:02 ` Mark Brown
2009-04-26 11:47 ` Mike Rapoport
2009-04-26 12:00 ` Mark Brown
2009-04-26 13:05 ` Mike Rapoport
2009-04-26 13:49 ` [PATCH] " Mike Rapoport
2009-04-27 11:43 ` Mark Brown
2009-04-27 12:30 ` Liam Girdwood
2009-04-27 12:29 ` 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=cover.1240736991.git.mike@compulab.co.il \
--to=mike@compulab.co.il \
--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