From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Chris Ball <cjb@laptop.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] mmc: core: Quieten "could not set regulator OCR" error.
Date: Thu, 30 Aug 2012 10:30:57 -0700 [thread overview]
Message-ID: <20120830173055.GF4356@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <873934qok9.fsf@octavius.laptop.org>
On Thu, Aug 30, 2012 at 01:25:58PM -0400, Chris Ball wrote:
> On Thu, Aug 30 2012, Mark Brown wrote:
> > Conversely there is nothing stopping other regulator drivers having
> > similar properties to the dummy driver, or constraints stopping them
> > implementing things. If the MMC framework wants to silently accept
> > regulators that don't allow the voltage to be set then the MMC framework
> > should enumerate the range of voltages which can be set using the
> > regulator it has and then take appropriate action.
> I didn't do this because I don't want to silently accept real regulators
> with insufficient voltage ranges, because that would make it harder to
> debug real MMC failures.
> Sounds like my response to the bug reports should be "persuade your
> distro kernel maintainers to turn off CONFIG_REGULATOR" -- I'll try
> doing that.
Or alternatively persuade someone to provide the appropriate fixed
voltage regulators as part of instantiating the MMC device on these
systems.
prev parent reply other threads:[~2012-08-30 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 23:33 [PATCH] mmc: core: Quieten "could not set regulator OCR" error Chris Ball
2012-08-29 12:09 ` Ulf Hansson
2012-08-29 13:08 ` Chris Ball
2012-08-30 17:12 ` Mark Brown
2012-08-30 17:25 ` Chris Ball
2012-08-30 17:30 ` 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=20120830173055.GF4356@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lrg@ti.com \
--cc=ulf.hansson@linaro.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 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.