From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 1/2 v2] regulator: support multiple dummy fixed regulators
Date: Mon, 18 Jun 2012 18:28:09 +0100 [thread overview]
Message-ID: <20120618172808.GX3974@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1206181850280.23884@axis700.grange>
[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]
On Mon, Jun 18, 2012 at 07:13:06PM +0200, Guennadi Liakhovetski wrote:
> On Mon, 18 Jun 2012, Mark Brown wrote:
> > It's for cases where people can't be bothered to specify the supply
> > properly but want to just put something in there to satisfy the sofware
> > without providing any useful information. There will be one or more
> > physical supplies but the software is being non-committal about them.
> Ok, but for that purpose I thought we already have the dummy regulator...
The dummy regulator isn't supposed to be used in production whereas this
is - dummy will get substituted in for *any* missing supply as a crutch
to get things working while this is added where needed. Having dummy on
can break things.
> So, what's the proper way to describe board common voltage rails?
Fixed voltage regulators should be described with the fixed voltage
regulator driver.
> Obviously you don't want to disable and enable them. Of course, there are
> real physical regulators, that provide that voltage, but what does it
> change, whether we specify the real name of that device or just say - yes,
> we have 3.3V on this board? So, it IS just a fixed regulator with a fixed
> voltage with no way to control it. The only action you can perform with it
> is query the voltage.
The name is mainly useful for allowing people to associate the code with
the schematic, by putting the name used in the schematic into the code
we make things much easier when people want to map between the two.
> > Meh, yes. I did try to make them readable. But then making up the
> > names in this fashion does rather defeat the point there...
> Ok, what shall we do with this? You want the user to supply a name for
> these fixed voltage always-on regulators? Or you're against these changes
Supply a name I think, the use case is totally sensible so it's
definitely totally reasonable to do something.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-18 17:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 8:19 [PATCH] regulator: extend the fixed voltage regulator to accept voltage Guennadi Liakhovetski
2012-06-18 9:41 ` Mark Brown
2012-06-18 9:52 ` Guennadi Liakhovetski
2012-06-18 10:06 ` Mark Brown
2012-06-18 10:13 ` Guennadi Liakhovetski
2012-06-18 11:57 ` Mark Brown
2012-06-18 15:57 ` [PATCH 1/2 v2] regulator: support multiple dummy fixed regulators Guennadi Liakhovetski
2012-06-18 15:57 ` [PATCH 2/2 v2] regulator: extend the fixed dummy voltage regulator to accept voltage Guennadi Liakhovetski
2012-06-18 16:20 ` [PATCH 1/2 v2] regulator: support multiple dummy fixed regulators Mark Brown
2012-06-18 16:30 ` Guennadi Liakhovetski
2012-06-18 16:37 ` Mark Brown
2012-06-18 17:13 ` Guennadi Liakhovetski
2012-06-18 17:28 ` Mark Brown [this message]
2012-06-19 15:43 ` [PATCH 1/2 v3] " Guennadi Liakhovetski
2012-06-19 15:44 ` [PATCH 2/2 v3] regulator: extend the fixed dummy voltage regulator to accept voltage Guennadi Liakhovetski
2012-06-19 22:28 ` [PATCH 1/2 v3] regulator: support multiple dummy fixed regulators 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=20120618172808.GX3974@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
/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).