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

On 21 April 2012 00:18, Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:

Going for the closure.
I have a last nail. Don't know whose coffin is it for ;)

>
> 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.
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?

Thanks,
-Jassi

  reply	other threads:[~2012-04-20 19:11 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 [this message]
2012-04-20 22:04                         ` 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='CAJe_ZhcfcTGjmy-n1hrVjvQ-8+Si4VAWaCf18cpap3NW5b+M=g@mail.gmail.com' \
    --to=jaswinder.singh@linaro.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --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.