All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:20:58 +0100	[thread overview]
Message-ID: <20120618162058.GT3974@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1206181755370.23884@axis700.grange>

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

On Mon, Jun 18, 2012 at 05:57:24PM +0200, Guennadi Liakhovetski wrote:
> Currently regulator_register_fixed() uses a constant name to register a
> fixed dummy regulator. This is sufficient in principle, since there is no
> reason to register multiple such regulators. The user can simply supply all
> consumers in one array and use it to initialise such a regulator. However,
> in some cases it can be convenient to register multiple such regulators.
> This is also easy to achieve by appending the device ID to the name. It is

None of this seems terribly obvious to me.  Once we're getting into
allowing the user to specify a voltage (and possibly other parameters)
for the regulator it's hopefully going to refer to an actual thing we
can point at on the board rather than a virtual thing we've got to
satisfy software so giving it a useful name seems more useful (like a
name correspoding to the relevant supply on the schematic).  

There's also the fact that there shouldn't be any need for unique
regulator names internally so if it really doesn't matter we should be
able to give everything the same name happily enough.

> also consistent with the current behaviour of the code, that fixes a name
> itself without giving the user a possibility to provide a custom one.

This is done on the basis that it's an entirely virtual regulator which
doesn't have any meaningful mapping into the hardware.  If it's got a
voltage then that's no longer true.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-06-18 16:21 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             ` Mark Brown [this message]
2012-06-18 16:30               ` [PATCH 1/2 v2] regulator: support multiple dummy fixed regulators Guennadi Liakhovetski
2012-06-18 16:37                 ` Mark Brown
2012-06-18 17:13                   ` Guennadi Liakhovetski
2012-06-18 17:28                     ` Mark Brown
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=20120618162058.GT3974@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.