All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jassi Brar <jaswinder.singh@linaro.org>
Cc: linux-kernel@vger.kernel.org, lrg@ti.com
Subject: Re: [PATCH] regulator: Provide a check for dummy regulator
Date: Fri, 20 Apr 2012 23:04:50 +0100	[thread overview]
Message-ID: <20120420220450.GB3088@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJe_ZhcfcTGjmy-n1hrVjvQ-8+Si4VAWaCf18cpap3NW5b+M=g@mail.gmail.com>

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

On Sat, Apr 21, 2012 at 12:41:18AM +0530, Jassi Brar wrote:
> On 21 April 2012 00:18, Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:

> > In any case, the solution is very clear - just do proper regulator
> > support and turn off dummy regulators and everything is fine.

> You earlier said there are always going to be 'new' platforms that would
> need dummy enabled.

When I say "need" I mean either "are at the point where just booting is
massive success so who cares if there's the odd bit of breakage" or
"have been randomly broken and need investigation as to what went
wrong".

> Now just imagine if one of those platforms happen to share the consumer
> due to which you suggest disabling the dummy (omap_hsmmc in this case).
> If we re-enable dummy, then your's isn't really a solution.
> If we require that platform to come with full compliance, why can't we
> ask every platform to do the same?

We do ask every platform to do the same, but enough people run into
problems that it's been useful to provide a standard crutch people can
pick up to get their systems up and running.  The theory is that dummy
regulators are enabled to help keep things running and as a debugging
aid, they're not intended for ongoing use.  If nothing else the log
message that gets printed out whenever a dummy regulator is used can be
helpful in identifying what's missing from the board setup.

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

      reply	other threads:[~2012-04-20 22:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19  9:51 [PATCH] regulator: Provide a check for dummy regulator Jassi Brar
2012-04-19 12:42 ` Mark Brown
2012-04-19 14:05   ` Jassi Brar
2012-04-19 16:29     ` Mark Brown
2012-04-20  7:32       ` Jassi Brar
2012-04-20 11:46         ` Mark Brown
2012-04-20 12:29           ` Jassi Brar
2012-04-20 13:01             ` Mark Brown
2012-04-20 13:48               ` Jassi Brar
2012-04-20 14:13                 ` Jassi Brar
2012-04-20 14:42                 ` Mark Brown
2012-04-20 18:25                   ` Jassi Brar
2012-04-20 18:48                     ` Mark Brown
2012-04-20 19:11                       ` Jassi Brar
2012-04-20 22:04                         ` Mark Brown [this message]

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=20120420220450.GB3088@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=jaswinder.singh@linaro.org \
    --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.