From: NeilBrown <neilb@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-serial@vger.kernel.org, linux-pm@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Question: How to power-manage UART-attached devices.
Date: Wed, 2 May 2012 09:15:16 +1000 [thread overview]
Message-ID: <20120502091516.20d87fc8@notabene.brown> (raw)
In-Reply-To: <20120501163303.GA4089@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
On Tue, 1 May 2012 17:33:03 +0100 Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Tue, May 01, 2012 at 09:35:59AM +1000, NeilBrown wrote:
> > On Mon, 30 Apr 2012 23:33:22 +0100 Mark Brown
> > > On Tue, May 01, 2012 at 08:22:09AM +1000, NeilBrown wrote:
>
> > > The userspace consumer was added for users like this that live entirely
> > > in userspace.
>
> > I assume you mean REGULATOR_VIRTUAL_CONSUMER (drivers/regulator/virtual.c)?
>
> No, that's just for testing drivers in development. I mean the
> userspace consumer which is hidden away in userspace-consumer.c.
Ahhh, of course. What a cunning hiding place! :-)
However it doesn't suit my need - I want something more abstracted.
I can see there may well be a place for a simple on/off switch for some
components, but then I would prefer to see it as
/sys/class/power-switch/$devicename/state
rather than
/sys/devices/platform/reg-userspace-consumer.X/{name,state}
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-01 23:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 22:22 Question: How to power-manage UART-attached devices NeilBrown
2012-04-30 22:33 ` Mark Brown
2012-04-30 23:35 ` NeilBrown
2012-05-01 16:33 ` Mark Brown
2012-05-01 23:15 ` NeilBrown [this message]
2012-05-02 9:02 ` Mark Brown
2012-04-30 22:51 ` H. Peter Anvin
2012-04-30 23:34 ` Alan Cox
2012-05-01 0:12 ` NeilBrown
2012-04-30 23:47 ` NeilBrown
2012-04-30 23:50 ` H. Peter Anvin
2012-05-01 0:27 ` NeilBrown
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=20120502091516.20d87fc8@notabene.brown \
--to=neilb@suse.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-serial@vger.kernel.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).