linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Harald Geyer <harald@ccbib.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Question about regulator API
Date: Fri, 16 Dec 2016 16:53:48 +0000	[thread overview]
Message-ID: <20161216165348.mha6d3faucxdript@sirena.org.uk> (raw)
In-Reply-To: <E1cHslb-0000g0-0V@stardust.g4.wien.funkfeuer.at>

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

On Fri, Dec 16, 2016 at 02:41:42PM +0100, Harald Geyer wrote:
> Mark Brown writes:
> > On Wed, Dec 14, 2016 at 03:52:54PM +0100, Harald Geyer wrote:

> > This doesn't feel like a regulator API problem exactly, a lot of what
> > you're talking about here seems like you really need the devices to
> > coopereate with each other and know what they're doing in order to work
> > well together.

> I was hoping, that I somehow could get the necessary coordination from
> the regulator framework. If the best I can get ATM is notifications, then
> I'll try it and see what kind of code falls out of this.

> It still seems a bit of a limitation to me, that the only way to really
> switch off a regulator is with regulator_force_disable(), which is quite
> a hard hammer.

I really have no idea what sort of communication you're envisaging here
- powering supplies down when other devices are trying to use them is a
really serious thing with very substantial consequences for userspace,
if the devices aren't cooperating at a level higher than the regulator
API level it's unlikely to go well.

> This only works as long as every consumer of the supply is cooperating
> (which is my personal use case but doesn't look very future proof). I guess
> there has to be some pain for using quirky, unreliable HW... ;)

That's going to be the case no matter what I think.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2016-12-16 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 14:52 Question about regulator API Harald Geyer
2016-12-14 18:14 ` Mark Brown
2016-12-16 13:41   ` Harald Geyer
2016-12-16 16:53     ` Mark Brown [this message]
2016-12-16 22:00       ` Harald Geyer
2016-12-19 11:09         ` Mark Brown

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=20161216165348.mha6d3faucxdript@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=harald@ccbib.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@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).